-
Controller Version6.0.0.25 Describe Your Issue or QuestionAs the title says, I don't know if the WARN in the container logs is normal or if something went wrong. I should add that physically everything seems to be working fine. Expected BehaviorPlease explain or suggest what I should do. Steps to ReproduceBehavior noticed after migration from old hardware to new one How You're Launching the ContainerContainer LogsMongoDB LogsNo response Additional ContextThe MAC address indicates that it is an SG2008P switch: 01-06-2026 09:10:18.190 WARN [proxy-handler-thread-97] [] c.t.s.o.m.p.m.d.o.o(): Osw D8-44-89-C3-04-42 with omadac 2d5d3b302b4445e184b30f9fa959d61d ports or lags is null. 01-06-2026 09:20:07.963 WARN [scheduled-pool-6] [] c.t.s.o.m.d.d.m.s.i(): OmadacId(2d5d3b302b4445e184b30f9fa959d61d) device host not enable |
Beta Was this translation helpful? Give feedback.
Answered by
mbentley
Jan 6, 2026
Replies: 2 comments 2 replies
-
|
Yeah, in most cases, those are issues in the software. I have the same messages about For the Now I have not seen the But really the only people who can help with these sorts of logs would be TP-Link either via the forums or support since it's software related. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
So - colloquially speaking - as long as "nothing flashes red" and basically everything works normally, there is nothing to worry about? |
Beta Was this translation helpful? Give feedback.
-
|
Yup, I'm assuming the ports of lags is null is just a scenario where they added/changed a feature and they either forgot something in a database migration, setting defaults when a device is adopted, or the UI isn't setting a value when there is nothing set. In this case, it's probably not an issue because the setting is likely only used when the feature is enabled. Hard to say about the other one given that it's a bit cryptic and not descriptive but if nothing is broken, I wouldn't worry too much about it. If you really want, posting on the TP-Link forums might get a staff member's attention but you can always submit a support case to get their direct attention. |
Beta Was this translation helpful? Give feedback.
Answer selected by
mbentley
-
|
Matt (I apologize in advance for describing everything "in layman's terms"), I think I finally know what's going on with these strange logs – maybe I'm naive, but my theory makes sense. |
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
Yeah, in most cases, those are issues in the software. I have the same messages about
ports or lags is nulltoo happening regularly in my logs.For the
ports or lags is null, there are a few posts on the forums about that: Warnings in the logs every 30 seconds are driving me crazy & this portNow I have not seen the
device host not enablemessage anywhere.But really the only people who can help with these sorts of logs would be TP-Link either via the forums or support since it's software related.