Hello Why my probe (id 2598, Firmware Version: 4280) rebooting several times a day? My routers and uplinks connections works correctly and stable. Internet Address: Connect at: Disconnect at: Up time: Down time (until next connection): 2001:1a68:a::56 2012-02-22 08:56:46 UTC (still connected) 0d, 3h, 59m (still connected) 2001:1a68:a::56 2012-02-22 07:48:06 UTC 2012-02-22 08:53:05 UTC 0d, 1h, 4m 0d, 0h, 3m 2001:1a68:a::56 2012-02-22 03:50:31 UTC 2012-02-22 07:44:41 UTC 0d, 3h, 54m 0d, 0h, 3m 2001:1a68:a::56 2012-02-21 17:04:30 UTC 2012-02-22 03:47:02 UTC 0d, 10h, 42m 0d, 0h, 3m 2001:1a68:a::56 2012-02-21 07:33:19 UTC 2012-02-21 16:57:49 UTC 0d, 9h, 24m 0d, 0h, 6m 2001:1a68:a::56 2012-02-21 04:42:18 UTC 2012-02-21 07:29:42 UTC 0d, 2h, 47m 0d, 0h, 3m 2001:1a68:a::56 2012-02-20 10:35:17 UTC 2012-02-21 04:35:13 UTC 0d, 17h, 59m 0d, 0h, 7m 2001:1a68:a::56 2012-02-19 14:55:21 UTC 2012-02-20 10:31:40 UTC 0d, 19h, 36m 0d, 0h, 3m 2001:1a68:a::56 2012-02-19 10:34:47 UTC 2012-02-19 14:51:58 UTC 0d, 4h, 17m 0d, 0h, 3m 2001:1a68:a::56 2012-02-19 04:35:15 UTC 2012-02-19 10:31:17 UTC 0d, 5h, 56m 0d, 0h, 3m 2001:1a68:a::56 2012-02-19 01:05:26 UTC 2012-02-19 04:31:43 UTC 0d, 3h, 26m 0d, 0h, 3m 2001:1a68:a::56 2012-02-18 23:54:45 UTC 2012-02-19 01:01:59 UTC 0d, 1h, 7m 0d, 0h, 3m 2001:1a68:a::56 2012-02-18 23:02:20 UTC 2012-02-18 23:51:06 UTC 0d, 0h, 48m 0d, 0h, 3m 2001:1a68:a::56 2012-02-18 22:23:42 UTC 2012-02-18 22:52:58 UTC 0d, 0h, 29m 0d, 0h, 9m 2001:1a68:a::56 2012-02-18 18:55:25 UTC 2012-02-18 22:13:36 UTC 0d, 3h, 18m 0d, 0h, 10m 2001:1a68:a::56 2012-02-18 02:50:04 UTC 2012-02-18 18:51:44 UTC 0d, 16h, 1m 0d, 0h, 3m 2001:1a68:a::56 2012-02-18 01:02:47 UTC 2012-02-18 02:46:09 UTC 0d, 1h, 43m 0d, 0h, 3m 2001:1a68:a::56 2012-02-17 19:34:11 UTC 2012-02-18 00:59:04 UTC 0d, 5h, 24m 0d, 0h, 3m 2001:1a68:a::56 2012-02-17 14:08:25 UTC 2012-02-17 19:30:28 UTC 0d, 5h, 22m 0d, 0h, 3m 2001:1a68:a::56 2012-02-17 13:14:37 UTC 2012-02-17 14:04:52 UTC 0d, 0h, 50m 0d, 0h, 3m
On Wed, 22 Feb 2012 14:08:31 +0100 Lukasz Trabinski <lukasz@wsisiz.edu.pl> wrote:
Hello
Why my probe (id 2598, Firmware Version: 4280) rebooting several times a day? My routers and uplinks connections works correctly and stable.
Only a random stab in the dark, but what USB port is it powered by? Could the device supplying the power be going into a power-saving mode and shutting down power to that port? -- David Precious ("bigpresh") <davidp@preshweb.co.uk> http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook www.preshweb.co.uk/cpan www.preshweb.co.uk/github
Good point David. I had similar issue during 1st two days when I was hosting via my laptop. No issues after I attached it to external USB adapter. On Wed, Feb 22, 2012 at 7:02 PM, David Precious <davidp@preshweb.co.uk>wrote:
On Wed, 22 Feb 2012 14:08:31 +0100 Lukasz Trabinski <lukasz@wsisiz.edu.pl> wrote:
Hello
Why my probe (id 2598, Firmware Version: 4280) rebooting several times a day? My routers and uplinks connections works correctly and stable.
Only a random stab in the dark, but what USB port is it powered by? Could the device supplying the power be going into a power-saving mode and shutting down power to that port?
-- David Precious ("bigpresh") <davidp@preshweb.co.uk> http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook www.preshweb.co.uk/cpan www.preshweb.co.uk/github
-- Anurag Bhatia anuragbhatia.com or simply - http://[2001:470:26:78f::5] if you are on IPv6 connected network! Twitter: @anurag_bhatia <https://twitter.com/#!/anurag_bhatia> Linkedin: http://linkedin.anuragbhatia.com
2012/2/22 David Precious <davidp@preshweb.co.uk>:
On Wed, 22 Feb 2012 14:08:31 +0100 Lukasz Trabinski <lukasz@wsisiz.edu.pl> wrote:
Why my probe (id 2598, Firmware Version: 4280) rebooting several times a day? My routers and uplinks connections works correctly and stable.
Only a random stab in the dark, but what USB port is it powered by? Could the device supplying the power be going into a power-saving mode and shutting down power to that port?
It's connected to USB port in PC router (Linux, FC16, with Quagga). I know that probe send and recive packets all the time. (sniffing packets by tcpdump) In my opinion usb port shouldn't go into sleep or power-saving mode. I dont's see any action related with that usb port in my logs files but on switch where probe is connected I observe flap port (down/up).
On 2/22/12 14:47 , Lukasz Trabinski wrote:
On Wed, 22 Feb 2012 14:08:31 +0100 Lukasz Trabinski<lukasz@wsisiz.edu.pl> wrote:
Why my probe (id 2598, Firmware Version: 4280) rebooting several times a day? My routers and uplinks connections works correctly and stable. Only a random stab in the dark, but what USB port is it powered by? Could the device supplying the power be going into a power-saving mode and shutting down power to that port? It's connected to USB port in PC router (Linux, FC16, with Quagga). I know that probe send and recive packets all the time. (sniffing
2012/2/22 David Precious<davidp@preshweb.co.uk>: packets by tcpdump) In my opinion usb port shouldn't go into sleep or power-saving mode. I dont's see any action related with that usb port in my logs files but on switch where probe is connected I observe flap port (down/up).
I can see from the logs that it does reboot (as opposed to just losing the connection to the controller). But I have no clue why it does that.
On 2012.02.22. 14:47, Lukasz Trabinski wrote:
2012/2/22 David Precious <davidp@preshweb.co.uk>:
On Wed, 22 Feb 2012 14:08:31 +0100 Lukasz Trabinski <lukasz@wsisiz.edu.pl> wrote:
Why my probe (id 2598, Firmware Version: 4280) rebooting several times a day? My routers and uplinks connections works correctly and stable.
Only a random stab in the dark, but what USB port is it powered by? Could the device supplying the power be going into a power-saving mode and shutting down power to that port?
It's connected to USB port in PC router (Linux, FC16, with Quagga). I know that probe send and recive packets all the time. (sniffing packets by tcpdump) In my opinion usb port shouldn't go into sleep or power-saving mode. I dont's see any action related with that usb port in my logs files but on switch where probe is connected I observe flap port (down/up).
The reference to USB power source issues is an interesting one -- we haven't seen that as a "structural" reason for disconnection before. Having said that, the fact that the probe is up for hours at a time suggests that the local network and power conditions are fine. Please keep in mind that our definition of "up" is when the probe is connected to us, ie. a permanent TCP connection to one of our servers is maintained. This connection may be broken for a number of reasons, including local (transient) network problems at either end. Also, the probe continues its measurements even if it's disconnected, and submits all the data once it reconnects. In short: it's not a big deal if a probe disconnects, as long as it can reconnect in a reasonable time. Regards, Robert
In short: it's not a big deal if a probe disconnects, as long as it can reconnect in a reasonable time.
Newbie light question How does one make sure the probe is using the up to date firmware. I have not seen this change since installed last week. Probe ID: 2317 Firmware Version: None MAC Address: 00:20:4A:E0:24:F7 Colin
On 2/22/12 15:07 , Colin Johnston wrote:
In short: it's not a big deal if a probe disconnects, as long as it can reconnect in a reasonable time.
Newbie light question
How does one make sure the probe is using the up to date firmware. I have not seen this change since installed last week.
Probes will update themselves. Just this morning a new firmware was released, so it should update itself within the next couple of days.
2012/2/22 Robert Kisteleki <robert@ripe.net>:
Also, the probe continues its measurements even if it's disconnected, and submits all the data once it reconnects.
In short: it's not a big deal if a probe disconnects, as long as it can reconnect in a reasonable time.
Thank's. Anyway I will try buy for 1 euro external usb power supply for my probe :)
On 2012.02.22. 15:23, Lukasz Trabinski wrote:
2012/2/22 Robert Kisteleki <robert@ripe.net>:
Also, the probe continues its measurements even if it's disconnected, and submits all the data once it reconnects.
In short: it's not a big deal if a probe disconnects, as long as it can reconnect in a reasonable time.
Thank's. Anyway I will try buy for 1 euro external usb power supply for my probe :)
We can give you one if you come to the next RIPE meeting :-) Robert
On Wed, 22 Feb 2012 15:23:58 +0100 Lukasz Trabinski <lukasz@trabinski.net> wrote:
Thank's. Anyway I will try buy for 1 euro external usb power supply for my probe :)
That's probably the easiest and most reliable way :) In the meantime, you could always check whether your USB ports are set to automatic power management: [davidp@columbia:~]$ cat /sys/bus/usb/devices/usb*/power/level auto auto If you get "auto", you could try forcing them to stay on - e.g. as root: echo on > /sys/bus/usb/devices/usb1/power/level Worth a try at least, if you're interested. Of course, you'd need to figure out which "usb$n" to use, depending on which port it's connected to - or just set them all to on: for file in /sys/bus/usb/devices/usb*/power/level; \ do echo "on" > $file; done Whether the above will actually make a difference, I don't know, but could be worth a try if you're curious. If you do, report back whether it helped, so everyone knows if that's a potential fix for anyone else who experiences the same problem :) -- David Precious ("bigpresh") <davidp@preshweb.co.uk> http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook www.preshweb.co.uk/cpan www.preshweb.co.uk/github
On Wed, Feb 22, 2012 at 4:16 PM, David Precious <davidp@preshweb.co.uk>wrote:
On Wed, 22 Feb 2012 15:23:58 +0100 Lukasz Trabinski <lukasz@trabinski.net> wrote:
Thank's. Anyway I will try buy for 1 euro external usb power supply for my probe :)
That's probably the easiest and most reliable way :)
In the meantime, you could always check whether your USB ports are set to automatic power management:
[davidp@columbia:~]$ cat /sys/bus/usb/devices/usb*/power/level auto auto
If you get "auto", you could try forcing them to stay on - e.g. as root:
echo on > /sys/bus/usb/devices/usb1/power/level
Worth a try at least, if you're interested.
Of course, you'd need to figure out which "usb$n" to use, depending on which port it's connected to - or just set them all to on:
for file in /sys/bus/usb/devices/usb*/power/level; \ do echo "on" > $file; done
Whether the above will actually make a difference, I don't know, but could be worth a try if you're curious. If you do, report back whether it helped, so everyone knows if that's a potential fix for anyone else who experiences the same problem :)
It may be worth to write down this tip on the Atlas FAQ, just in case other Linux users are experiencing random reboots and want to start troubleshooting bottom-up. Just my two cents Best,
-- David Precious ("bigpresh") <davidp@preshweb.co.uk> http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook www.preshweb.co.uk/cpan www.preshweb.co.uk/github
On Wed, 22 Feb 2012, Iñigo Ortiz de Urbina wrote:
Whether the above will actually make a difference, I don't know, but could be worth a try if you're curious. If you do, report back whether it helped, so everyone knows if that's a potential fix for anyone else who experiences the same problem :)
Thank You, I will try your soultions, I will report back if it solved problem with restart probe.
On Wed, 22 Feb 2012, Iñigo Ortiz de Urbina wrote:
Whether the above will actually make a difference, I don't know, but could be worth a try if you're curious. If you do, report back whether it helped, so everyone knows if that's a potential fix for anyone else who experiences the same problem :)
Thank You, I will try your soultions, I will report back if it solved problem with restart probe.
Yesterday I puted "on" to power/level on usb devices [root@voices ~]# cat /sys/bus/usb/devices/usb*/power/level on on on on on on on on But in logs I can see that probe rebooted last night nternet Address: Connect at: Disconnect at: Up time: Down time (until next connection): 2001:1a68:a::56 2012-02-23 05:34:18 UTC (still connected) 0d, 3h, 50m (still connected) 2001:1a68:a::56 2012-02-22 08:56:46 UTC 2012-02-23 05:30:37 UTC 0d, 20h, 33m 0d, 0h, 3m 2001:1a68:a::56 2012-02-22 07:48:06 UTC 2012-02-22 08:53:05 UTC 0d, 1h, 4m 0d, 0h, 3m
On 2012-02-23 05:31 wrote Lukasz Trabinski:
But in logs I can see that probe rebooted last night
nternet Address: Connect at: Disconnect at: Up time: Down time (until next connection): 2001:1a68:a::56 2012-02-23 05:34:18 UTC (still connected) 0d, 3h, 50m (still connected) 2001:1a68:a::56 2012-02-22 08:56:46 UTC 2012-02-23 05:30:37 UTC 0d, 20h, 33m 0d, 0h, 3m 2001:1a68:a::56 2012-02-22 07:48:06 UTC 2012-02-22 08:53:05 UTC 0d, 1h, 4m 0d, 0h, 3m
That does not necessarily mean that you probe rebooted. Often this would be related to the internet connection or your router/modem. BR Daniel AJ -- Follow me on twitter @newstik http://twitter.com/newstik
But in logs I can see that probe rebooted last night
nternet Address: Connect at: Disconnect at: Up time: Down time (until next connection): 2001:1a68:a::56 2012-02-23 05:34:18 UTC (still connected) 0d, 3h, 50m (still connected) 2001:1a68:a::56 2012-02-22 08:56:46 UTC 2012-02-23 05:30:37 UTC 0d, 20h, 33m 0d, 0h, 3m 2001:1a68:a::56 2012-02-22 07:48:06 UTC 2012-02-22 08:53:05 UTC 0d, 1h, 4m 0d, 0h, 3m That does not necessarily mean that you probe rebooted. Often this would be related to the internet connection or your router/modem. Or firmware upgrade. My probe apparently upgraded to v4310 last night.
Regards, Antoine
That does not necessarily mean that you probe rebooted. Often this would be related to the internet connection or your router/modem. Or firmware upgrade. My probe apparently upgraded to v4310 last night.
For firmware updates we're using a lazy approach: the probes only check for newer firmware when they reconnect. Of course we can request probes to upgrade, but we only use that if there's a good reason. If a probe is up an running happily, then we don't really want to disconnect it... :-) As an interesting data point: the top two probes in terms of continuous uptime are: ID 2197 (up since 2011-12-05 22:19:32 ~80 days) ID 917 (up since 2011-12-07 00:48:47 ~79 days) (Both are in France!) Regards, Robert
Only a random stab in the dark, but what USB port is it powered by? Could the device supplying the power be going into a power-saving mode and shutting down power to that port?
usb port on BT homehub works well :) Colin
participants (10)
-
Antoine Jacot-Descombes -
Anurag Bhatia -
Colin Johnston -
Daniel AJ Sokolov -
David Precious -
Iñigo Ortiz de Urbina -
Lukasz Trabinski -
Lukasz Trabinski -
Philip Homburg -
Robert Kisteleki