Reboot at night - why?

Software SW help
#1

my omnia was restarted tonight. I wonder why, since I have installed no packages. Does it reboot periodically?
I only see this in syslog at that time:

Dec  6 02:31:01 turris crond[32681]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
Dec  6 02:32:01 turris crond[32749]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
Dec  6 03:33:54 turris syslog-ng[5024]: syslog-ng starting up; version='3.29.1'
Dec  6 03:33:54 turris kernel: [    0.000000] Booting Linux on physical CPU 0x0

no updates were installed due to issue 21 - I don’t know if it’s related.

#2

Are your eMMC fine? Try to check it.

#3

Why is this my post flagged as offensive, abusive, or a violation?

#4

I hope so. I bought the omnia half year ago, and I try not to overload eMMC by unnecessary writes.

#5

But your logs are apparently persistent. Do you save them to some kind of external drive?

#6

A power outage maybe?

#7

yes, just for thissimilar case I have set up syslog-ng to save logs on usb stick.

#8

My NAS is up for 54 days, so no.

But thanks - I didn’t think of the hint, I’ll set up nut to log UPS status. my UPS is already connected to the router since it’s the only device 24/7 on

#9

Wasn’t there some internet outage? My Omnia’s kernel regularly segfaults when there is WAN outage (VDSL). I’m working on it with support, it looks like some memory corruption caused by the mvneta driver.

#10

Just a note … I have like two unexpected reboot, due incoming HDO signal (nightly el.power tarif). So no real el.power outage, that hdo was somehow so strong, it shutted down also my main computer (while others were stil up and running).

#11

Internet outage shouldn’t cause router reboot.

this happened at 03:33, while after packages update router reboots as 03:30. While no packages were updatet, maybe the issue 21 can cause router reboot even without update happening.

#12

Yes, it shouldn’t, but at least in my case it does.

My router also affected by issue 21 (with update approvals still configured) does not reboot spuriously.

#13

By default, if you have the router set to automatically install updates, it will reboot by itself in a few days, unless you reboot it yourself, if the update requires restarting (usually when the kernel is updated). Mine’s set, for instance, to reboot in 3 days at 3:30am.
I know there was an update to 5.1.4 a few days ago which required a reboot; might’ve been that.

Note, I’ve no clue if you can configure that in reForis, but in Forius you definitely can.

Personally, I set updates to “approval needed” and have the router send me an email notifications; that way, I’m never caught by surprise.

#14

I set updates to “approve manually” (can do in both foris and reforis).

However no updates were done last week, but the reboot happened about the time it’s usually done after kernel update.

#15

well, I get disconnected by ISP after 24 hours, so teoretically it could cause that. But it won’t explain why it happened once in half year I own omnia…

#16

As far as we got with the kernel crash investigations, it seems that it might be caused by the ethernet driver unable to allocate memory… At first,this seemed odd to me because there were usually 100-200 MB free RAM,but then we found out that the memory is pretty fragmented and the driver asks for a larger chunk than is available. You can watch the number of free chunks of memory in /proc/buddyinfo - it contains a list of numbers denoting the number of free blocks of sizes starting with 4 kiB and doubling with each entry… Given this way of reasoning, it could explain why it only happened now - it’s just pretty much dependent on how long has the router been running and how much did its free memory get fragmented.

#17

that could help - do you know anything available as opkg that monitors that info?
internet search colletcl that seems not to be available

#18

I’d go just with a simple background script that saves the data to some persistent storage. E.g. something like:

while true; do cat /proc/buddyinfo >> /srv/buddyinfo; sleep 5; done

Be aware that /srv should be some other memory than the internal drive (mmcblk0). It can even be a flash drive in USB.

#19

happened today again. Happened in the afternoon, about the time ISP was going to disconnect me after 24 hours (we’ve had power outage 3 weeks ago, power went on ~13:00
That indicated the problem appears after disconnect.

unfortunately, USB flash decided to fail yesterday and seems to be empty (dd from flash shows only zeroes).

#20

That would really point towards a similar problem I have with the crashes on wan outage… @mbehun ?