I've got it in GMT time, so that accounts for time disparity below. What the heck is notify_rc_start_webs_update, though? Is someone remotely causing a firmware update or something? That's kind of like what the behaviour appears to suggest...
Jun 3 22:36:23 rc_service: ntp 492:notify_rc restart_diskmon
Jun 3 22:36:23 disk_monitor: Finish
Jun 3 22:36:23 disk monitor: be idle
Jun 3 22:36:24 dhcp client: bound xxx.x.x.x/255.255.252.0 via x.1x.x.1 for 4907 seconds.
Jun 3 22:36:41 crond[350]: time disparity of 1621051 minutes detected
Jun 3 22:36:43 dnsmasq-dhcp[348]: DHCPDISCOVER(br0) 00:0e
b:44:3b:a8
Jun 3 22:36:43 dnsmasq-dhcp[348]: DHCPOFFER(br0) 192.168.0.45 00:0e b:44:3b:a8
Jun 3 22:36:43 dnsmasq-dhcp[348]: DHCPREQUEST(br0) 192.168.0.45 00:0e b:44:3b:a8
Jun 3 22:36:43 dnsmasq-dhcp[348]: DHCPACK(br0) 192.168.0.45 00:0e b:44:3b:a8 nazgul
Jun 3 22:40:25 rc_service: httpd 351:notify_rc start_webs_update
Edit history
Recommendations
0 members have recommended this reply (displayed in chronological order):
= new reply since forum marked as read