The message you would see is "OpenRG is going for reboot by IPC command" or something similar.

In reply to a post by Oliver341:

The message you would see is "OpenRG is going for reboot by IPC command" or something similar.

Nope I haven't seen any of those at all, what I always get when it reaches about 2 weeks is lines like the following (from bottom upwards):

05:17:09, 23 Jan. (1068783.850000) CHAP Receive Challenge
05:17:09, 23 Jan. (1068783.830000) Starting CHAP authentication with peer
05:17:09, 23 Jan. (1068783.830000) PPP LCP Send Configuration ACK
05:17:09, 23 Jan. (1068783.830000) PPP LCP Receive Configuration Request
05:17:09, 23 Jan. (1068783.770000) PPP LCP Receive Configuration ACK
05:17:09, 23 Jan. (1068783.750000) PPP LCP Send Configuration Request
05:17:06, 23 Jan. (1068780.770000) PPP LCP Receive Configuration ACK
05:17:06, 23 Jan. (1068780.750000) PPP LCP Send Configuration Request
05:17:06, 23 Jan. (1068780.750000) PPP LCP Receive Configuration Reject
05:17:06, 23 Jan. (1068780.600000) PPP LCP Send Configuration Request
05:16:40, 23 Jan. (1068753.970000) CWMP: session closed due to error: Could not resolve host
05:16:38, 23 Jan. (1068751.970000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
05:16:38, 23 Jan. (1068751.960000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
05:16:36, 23 Jan. (1068750.620000) CWMP: Initializing transaction for event code 4 VALUE CHANGE
05:16:33, 23 Jan. (1068747.900000) PPPoA is down after 17810 minutes uptime [Disconnected]
23:41:33, 22 Jan. (1048647.070000) Admin login successful by 192.168.2.72 on HTTP

The Admin login was me due to slow speed where I just checked the logs.

Actually that's a lie, I just saw some of those IPC lines in the System Logs:

02:26:35, 07 Jan. ( 40.460000) The system is UP!
02:25:32, 07 Jan. (1262312.660000) The system is going DOWN for reboot.
02:25:32, 07 Jan. (1262312.660000) OpenRG is going for reboot by IPC command
02:25:27, 07 Jan. (1262307.660000) OpenRG will go down for reboot in 5 seconds
11:47:22, 23 Dec. ( 38.390000) The system is UP!
11:46:22, 23 Dec. (1211146.960000) The system is going DOWN for reboot.
11:46:22, 23 Dec. (1211146.960000) OpenRG is going for reboot by IPC command
11:46:17, 23 Dec. (1211141.960000) OpenRG will go down for reboot in 5 seconds

And that was the latest one that we have in the logs, and if you do the maths you will see 14 days between remote reboots.

And like I have said we don't loose sync to the exchange, but we do loose connection to the BT Network.
It is strange that we have never had a stable connection to BT's Network for longer than 2 weeks where as with our last ISP (Zen) we hardly had any reconnects and would be connected up for several months, but the current issues are probably down to all the bad weather we are having lately.

The only time we have lost connection and the HH4 reboots was when I asked for our SNR to be reset back to 6.0 dB due to the rain causes our SNR to rise and rise until it just fails to sync. BT are aware of this and are happy to reset our SNR and is probably why our PCP cabinet is currently being re-installed.

Paul

In reply to a post by PaulKirby:

And that was the latest one that we have in the logs, and if you do the maths you will see 14 days between remote reboots.

Apparently, it's not a remote reboot, but a local one.

In reply to a post by PaulKirby:

And like I have said we don't loose sync to the exchange, but we do loose connection to the BT Network.

The IPC reboot command reboots the router, so you must be losing sync at that point.

IPC stands for Inter-Process Communication. The communication is a message sent from one process to another. It suggests here a message somehow sent from the DSL hardware driver to the Linux kernel requesting that reboot. Though not clear why the driver should need to request a reboot. Poor system design, maybe? Poor coding meaning a reboot is the only way to get the device back to a trusted state; periodically clearing the variables, flushing the buffers and whatnot from the previous sync? Just speculation.

http://en.wikipedia.org/wiki/Inter-process_communica...

Edited by deleted (Sun 25-Jan-15 19:16:04)

To force the IP Profile to update as a result of a resync?

My old home hub literally never rebooted, so when I got my new one this 14 day behaviour bothered me. I honestly assumed my hub was faulty - apparently not, it's a thing.

The only reason I can think they are doing this is because the new hubs aren't stable enough to run for months on end without a reboot. It has made me seriously dislike the HomeHub.

As far as I can tell it does it with the modem and without the modem.
The only solution would be to use the modem and your own router (something I am probably going to do).

In reply to a post by Oliver341:

In reply to a post by PaulKirby:

And that was the latest one that we have in the logs, and if you do the maths you will see 14 days between remote reboots.

Apparently, it's not a remote reboot, but a local one.

Agreed.

In reply to a post by Oliver341:

In reply to a post by PaulKirby:

And like I have said we don't loose sync to the exchange, but we do loose connection to the BT Network.

The IPC reboot command reboots the router, so you must be losing sync at that point.

Sorry that comment was for the first lot of logs, I added the second log in after I wrote the rest of the post.
But yes, those IPC Reboots do seem to loose sync due to rebooting the entire device.

Paul