#17564: syslog: We have an error talking to the kernel
--------------------------+------------------------
Reporter: anonymous | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone:
Component: base system | Version: Trunk
Resolution: | Keywords: syslog
--------------------------+------------------------
Comment (by anonymous):
I was too quick to blame syslog/ubus (because of the ubus errors I see on
a x86 VM). Here's a complete log booting CC trunk r42165 on ar71xx (TL-
WDR3600) :
{{{
Fri Aug 15 21:33:55 2014 daemon.notice netifd: Bridge 'br-lan' link is up
Fri Aug 15 21:33:55 2014 daemon.notice netifd: Interface 'lan' has link
connectivity
Fri Aug 15 21:33:55 2014 daemon.notice netifd: Network device 'lo' link is
up
Fri Aug 15 21:33:55 2014 daemon.notice netifd: Interface 'loopback' has
link connectivity
Fri Aug 15 21:33:55 2014 daemon.notice netifd: VLAN 'eth0.2' link is down
Fri Aug 15 21:33:55 2014 daemon.notice netifd: Interface 'wan' has link
connectivity loss
Fri Aug 15 21:33:55 2014 daemon.notice netifd: VLAN 'eth0.2' link is up
Fri Aug 15 21:33:55 2014 daemon.notice netifd: Interface 'wan' has link
connectivity
Fri Aug 15 21:33:55 2014 daemon.notice netifd: VLAN 'eth0.3' link is down
Fri Aug 15 21:33:55 2014 daemon.notice netifd: Interface 'wan2' has link
connectivity loss
Fri Aug 15 21:33:55 2014 daemon.notice netifd: VLAN 'eth0.3' link is up
Fri Aug 15 21:33:55 2014 daemon.notice netifd: Interface 'wan2' has link
connectivity
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: No such
file or directory
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: No such
file or directory
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: No such
file or directory
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: No such
file or directory
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: No such
file or directory
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: No such
file or directory
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: Invalid
argument
Fri Aug 15 21:33:56 2014 user.emerg syslog: We have an error talking to
the kernel
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: Invalid
argument
Fri Aug 15 21:33:56 2014 user.emerg syslog: We have an error talking to
the kernel
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: Invalid
argument
Fri Aug 15 21:33:56 2014 user.emerg syslog: We have an error talking to
the kernel
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: Invalid
argument
Fri Aug 15 21:33:56 2014 user.emerg syslog: We have an error talking to
the kernel
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: Invalid
argument
Fri Aug 15 21:33:56 2014 user.emerg syslog: We have an error talking to
the kernel
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: Invalid
argument
Fri Aug 15 21:33:56 2014 user.emerg syslog: We have an error talking to
the kernel
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: Invalid
argument
Fri Aug 15 21:33:56 2014 user.emerg syslog: We have an error talking to
the kernel
Fri Aug 15 21:33:56 2014 user.emerg syslog: RTNETLINK answers: Invalid
argument
Fri Aug 15 21:33:56 2014 user.emerg syslog: We have an error talking to
the kernel
Fri Aug 15 21:33:56 2014 daemon.notice netifd: wan2 (1831): udhcpc
(v1.22.1) started
Fri Aug 15 21:33:56 2014 daemon.notice netifd: wan (1825): udhcpc
(v1.22.1) started
Fri Aug 15 21:33:56 2014 daemon.notice netifd: wan2 (1831): Sending
discover...
...
}}}
--
Ticket URL: <https://dev.openwrt.org/ticket/17564#comment:1>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
