What's new

System logs: already exist in UDB, can't add it

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

peter

New Around Here
In system logs I can see this repeating message. What does it mean and How can I remove it? I do not know that my device has this IP.

Jan 9 23:17:15 kernel: 192.168.1.221 already exist in UDB, can't add it
Jan 9 23:17:15 kernel: 192.168.1.235 already exist in UDB, can't add it
Jan 9 23:18:29 kernel: 192.168.1.221 already exist in UDB, can't add it
Jan 9 23:18:29 kernel: 192.168.1.221 already exist in UDB, can't add it
Jan 9 23:18:29 kernel: 192.168.1.235 already exist in UDB, can't add it
 
In system logs I can see this repeating message. What does it mean and How can I remove it? I do not know that my device has this IP.

Jan 9 23:17:15 kernel: 192.168.1.221 already exist in UDB, can't add it
Jan 9 23:17:15 kernel: 192.168.1.235 already exist in UDB, can't add it
Jan 9 23:18:29 kernel: 192.168.1.221 already exist in UDB, can't add it
Jan 9 23:18:29 kernel: 192.168.1.221 already exist in UDB, can't add it
Jan 9 23:18:29 kernel: 192.168.1.235 already exist in UDB, can't add it
Same here. I think it started after upgrading to 386.4 :-(
Not yet ready to do a factory reset and rebuild from scratch ...
 
Do you use AiMesh? One of my networks is AiMesh of a few Asus routers and access points and when AiMesh is on I see the exact same log entries while as soon as I disable AiMesh those are gone.

Appears, and I am speculating here because I am not 100%sure, that the built-into kernel UDB db thinks that IP address is already given out to a device while it is very possible it is not. Why do I say possibly it is not? Well, I found when searching that none of my devices had the IP address log showed/reported, but it appears as a bug in the kernel code that there is not a complete sync between meshed devices and one of the nodes thinks that the IP is already given as it likely was in the past to a device and that the device with the specific IP is still present on the net but UDB for to me unknown reasons remembered it and keeps a hold of it. Also noticed, if I reboot all meshed devices the system log then shows another IP address....very confusing and so far I have not found any useful explanation by anyone, not Asus forums of any kind nor Asuswrt-merlin development community or users. :(
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top