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
reboot(1M)																reboot(1M)

NAME
reboot - restart the operating system SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments] The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel. Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending loss of service. See shutdown(1M) for details. The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On systems, reboot may also update the boot archive as needed to ensure a successful reboot. The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present. Normally, the system reboots itself at power-up or after crashes. The following options are supported: -d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps. -l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot. -n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to sync filesystems. -q Quick. Reboot quickly and ungracefully, without shutting down running processes first. The following operands are supported: boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot argument list. Example 1: Passing the -r and -v Arguments to boot In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M). example# reboot -dl -- -rv Example 2: Rebooting Using a Specific Disk and Kernel The following example reboots using a specific disk and kernel. example# reboot disk1 kernel.test/unix /var/adm/wtmpx login accounting file See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2), reboot(3C), attributes(5) The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown of system services, use shutdown(1M) or init(1M) to reboot a Solaris system. 11 Apr 2005 reboot(1M)
All times are GMT -4. The time now is 04:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy