Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Linux froze and got back working 5 days later, no reboot. Post 303036586 by OmahaWiz on Wednesday 3rd of July 2019 06:59:34 PM
Old 07-03-2019
Linux froze and got back working 5 days later, no reboot.

Hello my friends,

I've come across the weirdest of glitches.

I'm running a simple weather monitor (just temperature) on a Raspbeery Pi 3B (Raspbian Linux 4.14.98-v7+). It has a 3G modem that sends out simple packets to my server at home.

On june 5th I lost remote access to the device. Since it is located somewhere difficult to physically access, I couldn't manually reboot it.

To my surprise, on June 10th it got back to life. It has not registered a reboot! Here's the weird excerpt from the log at /var/log/messages:

Code:
Jun  5 17:54:28 raspberrypi NetworkManager[345]: <info>  [1559768068.0169] policy: set 'VIVO ZAP' (wwan0) as default for IPv4 routing and DNS
Jun  5 17:54:28 raspberrypi NetworkManager[345]: <info>  [1559768068.0174] dns-mgr: Writing DNS information to /sbin/resolvconf
Jun  5 17:54:28 raspberrypi NetworkManager[345]: <info>  [1559768068.1295] device (ttyUSB2): Activation: successful, device activated.
Jun 10 23:14:33 raspberrypi NetworkManager[345]: <info>  [1560219273.9397] (mon0): using nl80211 for WiFi device control
Jun 10 23:14:33 raspberrypi NetworkManager[345]: <info>  [1560219273.9622] devices added (path: /sys/devices/platform/soc/3f300000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/net/mon0, iface: mon0)
Jun 10 23:14:33 raspberrypi NetworkManager[345]: <info>  [1560219273.9623] device added (path: /sys/devices/platform/soc/3f300000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/net/mon0, iface: mon0): no ifupdown configuration found.

It's as if the operating system froze for some reason and suddenly got back working 5 days later! Absolutely no reboot registered.

I have absolutely no other log.

Does anyone know what could have happened there?

Last edited by jim mcnamara; 07-03-2019 at 11:23 PM..
This User Gave Thanks to OmahaWiz For This Post:
 

9 More Discussions You Might Find Interesting

1. Solaris

IPMP setup removed, comes back with reboot

Hi all, I have 3 Sun v490's running Solaris 10. Each one has 2 zones on it. I changed the IP address and configuration on them this weekend, where ce0 was once the primary IP nic, now ce2 is. Previously, ce0 and ce4 were set up with IP multipathing, but I tried to remove that by changing the... (2 Replies)
Discussion started by: jackiea
2 Replies

2. Shell Programming and Scripting

number of working days

Hi There, Can you help me writing an unix script which tells me number of working days between two dates. say d1 and d2. The answer should be Integer. is it possible in Unix. cheers, (1 Reply)
Discussion started by: rahulkav
1 Replies

3. UNIX for Dummies Questions & Answers

Date& Time change in linux beyond few days back

Hi, Could you please let me know the command to change my date /time beyond few days back. Currently when i am trying the below commands able to go beyond one day at max. -->date -->Mon Sep 29 19:31:58 EST 2008 -->export TZ=TMP40:00:00 (Changing the date beyond 40 hours) -->Sun Sep 28... (4 Replies)
Discussion started by: komala
4 Replies

4. UNIX for Advanced & Expert Users

back in the good old 7.07 ghostscript days...

back in the good old 7.07 ghostscript days... we had Great results converting pdf to ps output, from the following command: cat $stuff | /usr/local/bin/gs -sDEVICE=ljet4 -q -dNOPAUSE -r200 -sPAPERSIZE=letter -dPDFFitPage -dBATCH -sOutputFile=- - 2> /dev/null | /usr/bin/lp -d $printer ... (3 Replies)
Discussion started by: mr_manny
3 Replies

5. UNIX for Dummies Questions & Answers

display all dates 200 days back

i need help! can someone help me please? i try to calculate date under unix (ksh)...AIX operating system. I have to find the date 200 days from today's date. then the script should loop 200 times and display on command line every day's date until the current date. example: todays date:... (1 Reply)
Discussion started by: pavan_test
1 Replies

6. Shell Programming and Scripting

display all dates 200 days back

i need help! can someone help me please? i try to calculate date under unix (ksh)...AIX operating system. I have to find the date 200 days from today's date. then the script should loop 200 times and display on command line every day's date until the current date. example: todays date:... (4 Replies)
Discussion started by: pavan_test
4 Replies

7. Emergency UNIX and Linux Support

After reboot, CDE and cifs are not working

I installed bos.cifs_fs, bos.loc.iso.ko_KR, X11.fnt.ucs.ttf_KR, X11.fnt.ksc5601.ttf on p520 express, AIX 5.3 and upgraded the system from 5.3 TL7 SP? to 5.3 TL7 SP10 and rebooted the system. During the boot, the system print error messages below (green text) exec(): 0509-036 Cannot load... (2 Replies)
Discussion started by: lifegeek
2 Replies

8. Shell Programming and Scripting

Look back file days in PERL

I have 3 variables , $file =abc_2011_11_01.txt (current day file), $back = Yes and $forward = No I need to search for 3 days back files / 3 days forward files if my current file is not present logic is, I need to download the current day file. If it is missing, i need to look out for currentday... (4 Replies)
Discussion started by: irudayaraj
4 Replies

9. Shell Programming and Scripting

Working out days of the week and processing file in 3 working days

Hi guys i need advice on the approach to this one...... I have a file say called Thisfile.20130524.txt i need to work out from the date 20130524 what day of the week that was and then process the file in 3 working days. (so not counting saturday or sunday....(will not worry about bank... (2 Replies)
Discussion started by: twinion
2 Replies
SHOREWALL-INIT(8)						  [FIXME: manual]						 SHOREWALL-INIT(8)

NAME
shorewall-init - Companion package SYNOPSIS
/etc/init.d/shorewall-init [start|stop] DESCRIPTION
Shorewall-init is an optional package (added in Shorewall 4.4.10) that can be installed along with Shorewall, Shorewall6, Shorewall-lite and/or Shorewall6-lite. It provides two key features: 1. It can close (stop) the firewall during boot prior to starting the network. This can prevent unwanted connections from being accepted after the network comes up but before the firewall is started. 2. It can interface with your distribution's ifup/ifdown scripts and/or NetworkManager to allow firewall actions when an interface starts or stops. These two capabilities can be enabled separately. After you install the shorewall-init package, you can activate it by modifying the Shorewall-init configuration file: o On Debian-based system, the file is /etc/default/shorewall-init. o On other systems, the file is /etc/sysconfig/shorewall-init. To activate the safe boot feature, edit the configuration file and set PRODUCTS to a space-separated list of Shorewall products that you want to be closed before networking starts. Example: PRODUCTS="shorewall shorewall6" You also must insure that the compiled scripts for the listed products are compiled using Shorewall 4.4.10 or later. Shorewall shorewall compile Shorewall6 shorewall6 compile Shorewall-lite On the administrative system, enter the command shorewall export firewall from the firewall's configuration directory. Shorewall6-lite On the administrative system, enter the command shorewall6 export firewall from the firewall's configuration directory. The second feature (ifup/ifdown and NetworkManager integration) should only be activated on systems that do not use a link status monitor line swping or LSM. o Edit the configuration file and set IFUPDOWN=1 For NetworkManager integration, you will want to disable firewall startup at boot and delay it to when your interface comes up. For this to work correctly, you must set the required or the optional option on at least one interface then: o On Debian-based systems, edit /etc/default/product for each product listed in the PRODUCTS setting and set startup=0. o On other systems, use the distribution's service control tool (insserv, chkconfig, etc.) to disable startup of the products listed in the PRODUCTS setting. On a laptop with both ethernet and wireless interfaces, you will want to make both interfaces optional and set the REQUIRE_INTERFACE option to Yes in shorewall.conf[1](5) or shorewall6.conf[2] (5). This causes the firewall to remain stopped until at least one of the interfaces comes up. FILES
/etc/default/shorewall-init (Debian-based systems) or /etc/sysconfig/shorewall-init (other distributions) SEE ALSO
shorewall(8), shorewall-accounting(5), shorewall-actions(5), shorewall-blacklist(5), shorewall-hosts(5), shorewall_interfaces(5), shorewall-ipsets(5), shorewall-maclist(5), shorewall-masq(5), shorewall-nat(5), shorewall-netmap(5), shorewall-params(5), shorewall-policy(5), shorewall-providers(5), shorewall-proxyarp(5), shorewall-rtrules(5), shorewall-routestopped(5), shorewall-rules(5), shorewall.conf(5), shorewall-secmarks(5), shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-tcrules(5), shorewall-tos(5), shorewall-tunnels(5), shorewall-zones(5) NOTES
1. shorewall.conf http://www.shorewall.net/manpages/shorewall.conf.html 2. shorewall6.conf http://www.shorewall.net/manpages/../Manpages6/shorewall6.conf.html [FIXME: source] 06/28/2012 SHOREWALL-INIT(8)
All times are GMT -4. The time now is 12:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy