[Help]: My docker based controller broke after recent ubuntu update... i've probably made it worse!
#458
-
Controller Version5.14 Describe Your Issue or QuestionSorry i have only very basic docker/linux skills - i have no idea how i got my controller running a couple of years ago and it lasted this long! After a recent batch of ubuntu updates i rebooted, then my omada controller wouldn't start... i can't say i got much useful detail out of the logs, i went to "bull in a chinashop" mode and tried getting it to work through various means. Good news is that i have copies of the autobackup directory! I have alos copied off the data and logs directory I have been trying to start from scratch, but it comes up with alerts saying i don't have the log/data file. Can anyone advise me on the best way to clear everything down so i can create a new controller/container from scratch and restore to one of the autobackups please? This is the compose file i have been trying to work with.... help please? `version: "3.1" services: volumes: Expected BehaviorContainer to start Steps to Reproducedeleted data and logs file under /var/lib/docker/volumes/omada_omada-data and /var/lib/docker/volumes/omada_omada-logs How You're Launching the ContainerContainer LogsMongoDB LogsNo response Additional ContextAny help would be greatly appreciated please! |
Beta Was this translation helpful? Give feedback.
Answered by
adsgsy
Aug 12, 2024
Replies: 8 comments 5 replies
-
|
So i have just found the article on 5.14 being a bit dodgy... not sure i can revert with the mess and lost container i have, but it would be good to understand how to recreate it please |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
So - i have managed to get it to start, but i cannot access the controller webinterface...
Any further hints please? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I think i have it back! While i had yet to have a response (it hadn't been long!) by submitting the issue on here helped me to resolve it myself. Thank you! |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
I went to look at this discussion last night and saw the email thread where there had been multiple responses and thought, "oh good, someone stopped by to help" and I now realize it was yourself :) Glad you were able to get it sorted. |
Beta Was this translation helpful? Give feedback.
-
|
Hey! I am having the same issue - how did you solve this? |
Beta Was this translation helpful? Give feedback.
Answer selected by
mbentley
-
|
Thumbs up! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thank you Matt! Also for the continued support with the Omada images! Great
work!
…On Tue, 13 Aug 2024 at 10:33, Matt Bentley ***@***.***> wrote:
I went to look at this discussion last night and saw the email thread
where there had been multiple responses and thought, "oh good, someone
stopped by to help" and I now realize it was yourself :) Glad you were able
to get it sorted.
—
Reply to this email directly, view it on GitHub
<#458 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKPQCGYTTEN2THS5RQNGKLDZRHHGDAVCNFSM6AAAAABMMQO3XKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZSGM3TEMA>
.
You are receiving this because you modified the open/close state.Message
ID:
<mbentley/docker-omada-controller/repo-discussions/458/comments/10323720@
github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I used the 5.13 image instead
…On Wed, 14 Aug 2024 at 15:42, Chris ***@***.***> wrote:
Hey! I am having the same issue - how did you solve this?
—
Reply to this email directly, view it on GitHub
<#458 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKPQCG7UCKZLUZMZDMEWVSDZRNUHFAVCNFSM6AAAAABMMQO3XKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZTHAZTKNI>
.
You are receiving this because you modified the open/close state.Message
ID:
<mbentley/docker-omada-controller/repo-discussions/458/comments/10338355@
github.com>
|
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Ah. I'll do that for now, but I wonder if @mbentley can pipe in as well for a proper fix? |
Beta Was this translation helpful? Give feedback.
-
|
There is a pinned issue (#418) which has workaround details in the first post, assuming it is the circular dependency startup issue that you're facing. |
Beta Was this translation helpful? Give feedback.
-
|
I can understand it is more of a TPLink issue than Matt’s, but perhaps
there is an option to revoke 5.14 as being the “latest” version off the
image?
Cheers
…On Wed, 14 Aug 2024 at 15:56, Chris ***@***.***> wrote:
Ah. I'll do that for now, but I wonder if @mbentley
<https://github.com/mbentley> can pipe in as well for a proper fix?
—
Reply to this email directly, view it on GitHub
<#458 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKPQCGYXXHPM5KUG5HH5JITZRNVYVAVCNFSM6AAAAABMMQO3XKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZTHA2DSMY>
.
You are receiving this because you modified the open/close state.Message
ID:
<mbentley/docker-omada-controller/repo-discussions/458/comments/10338493@
github.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Unfortunately I can't do that because 5.14 does work for some people and changing I can only suggest that people stop using |
Beta Was this translation helpful? Give feedback.
-
|
Fair point, thanks Matt!
…On Wed, 14 Aug 2024 at 16:10, Matt Bentley ***@***.***> wrote:
Unfortunately I can't do that because 5.14 does work for some people and
changing latest back to a 5.13 image will break more people's working
deployments than those that are impacted by the 5.13 issues.
I can only suggest that people stop using latest and use a specific
major.minor tag. There is a reason that all of the examples in the docs
use specific tags instead of latest but as it turns out, there are tons of
people who use the image from places like Synology (and other vendor)
container marketplaces and the people who authored those seem to use
latest.
—
Reply to this email directly, view it on GitHub
<#458 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKPQCGYSRZ2YXMZMOSNUWYTZRNXMVAVCNFSM6AAAAABMMQO3XKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZTHA3DKNA>
.
You are receiving this because you modified the open/close state.Message
ID:
<mbentley/docker-omada-controller/repo-discussions/458/comments/10338654@
github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think i have it back!
While i had yet to have a response (it hadn't been long!) by submitting the issue on here helped me to resolve it myself.
Thank you!