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
YPBIND(8)							     ypbind-mt								 YPBIND(8)

NAME
ypbind - NIS binding process SYNOPSIS
ypbind [-broadcast | -ypset | -ypsetme] [-c] [-f configfile] [-no-ping] [-broken-server] [-local-only] [-i | -ping-interval ping-interval] [-r | -rebind-interval rebind-interval] [-d | -debug] [-v | -verbose] [-n | -foreground] [-p port] [-log log-options] [-no-dbus] ypbind --version ypbind --help DESCRIPTION
ypbind finds the server for NIS domains and maintains the NIS binding information. The client (normally the NIS routines in the standard C library) could get the information over RPC from ypbind or read the binding files. The binding files resides in the directory /var/yp/binding and are conventionally named [domainname].[version]. The supported versions are 1 and 2. There could be several such files since it is possible for an NIS client to be bound to more than one domain. After a binding has been established, ypbind will send YPPROC_DOMAIN requests to the current NIS server at 20 seconds intervals. If it doesn't get an response or the NIS server reports that he doesn't have this domain any longer, ypbind will search for a new NIS server. All 15 minutes ypbind will check to see if the current NIS server is the fastest. If it find a server which answers faster, it will switch to this server. You could tell ypbind to use network broadcasts to find a new server, what is insecure, or you could give it a list of known secure servers. In this case ypbind will send a ping to all servers and binds to first one which answers. Unless the option -debug is used, ypbind detaches itself from the controlling terminal and puts itself into background. ypbind uses syslog(3) for logging errors and warnings. At startup or when receiving signal SIGHUP, ypbind parses the file /etc/yp.conf and tries to use the entries for its initial binding. A broadcast entry in the configuration file will overwrite a ypserver/server entry and a ypserver/server entry broadcast. If all given server are down, ypbind will not switch to use broadcast. ypbind will try at first /etc/hosts and then DNS for resolving the hosts names from /etc/yp.conf. If ypbind couldn't reconfigure the search order, it will use only DNS. If DNS isn't available, you could only use IP-addresses in /etc/hosts. ypbind could only reconfigure the search order with glibc 2.x. If the -broadcast option is specified, ypbind will ignore the configuration file. If the file does not exist or if there are no valid entries, ypbind exit. This ypbind version listens for DBUS messages from NetworkManager. If no NetworkManager is running at startup, ypbind will behave as usual and assumes there is a working network connection. If NetworkManager is running on the system, ypbind will only search and provide NIS informations, if NetworkManager tells that a network connection is available. If NetworkManager establishes a connection, ypbind will reread all configuration files, registers at the local portmapper and try to search NIS servers. If NetworkManager drops a connection, ypbind will unregister from portmapper. In Fedora we use systemd for starting services. We need to finish starting process of ypbind service not before service is fully started, which means ypbind daemon is prepared to answer. There is a test script /usr/libexec/ypbind-post-waitbind used in ypbind.service, that waits for ypbind daemon to be fully connected to NIS server and waits by default up to 45s. Sometimes this is not enough, because network set up can take longer than 45s during boot, so starting ypbind.service fails. User can increase the timeout by setting an environment variable NISTIMEOUT in /etc/sysconfig/ypbind. For example NISTIMEOUT=180 means ypbind will wait up to 180 seconds for binding to a NIS server. Another option is to enable NetworkManager-wait-online.service and add an ordering rule into ypbind.service, ideally by creating /etc/systemd/system/ypbind.service with the following content: .include /lib/systemd/system/ypbind.service [Service] After=NetworkManager-wait-online.service OPTIONS
-broadcast Send a broadcast to request the information needed to bind to a specific NIS server. With this option, /etc/yp.conf will be ignored. -ypset Allow root from any remote machine to change the binding for a domain via the ypset(8) command. By default, no one can change the binding. This option is really insecure. If you change a binding for a domain, all the current known servers for this domain will be forgotten. If the new server goes down, ypbind will use the old searchlist. -ypsetme The same as -ypset, but only root on the local machine is allowed to change the binding. Such requests are only allowed from loopback. -c ypbind only checks if the config file has syntax errors and exits. -d, -debug starts ypbind in debug mode. ypbind will not put itself into background, and error messages and debug output are written to standard error. -n, -foreground ypbind will not put itself into backgroun. -v, -verbose Causes ypbind to syslog(2) any and all changes in the server its bound to. -broken-server Lets ypbind accept answers from servers running on an illegal port number. This should usually be avoided, but is required by some ypserv(8) versions. -no-ping ypbind will not check if the binding is alive. This option is for use with dialup connections to prevent ypbind from keeping the connection unnecessarily open or causing auto-dials. -f configfile ypbind will use configfile and not /etc/yp.conf -local-only ypbind will only bind to the loopback device and is not reachable from a remote network. -p port Lets ypbind listen on a specified port number, rather than asking portmapper to assing a port for it. -i, -ping-interval ping-interval The default value for ypbind to check, if a NIS server is still reachable, is 20 seconds. With this options another frequency in seconds can be specified. -r, -rebind-interval rebind-interval The default value for ypbind to search for the fastest NIS server is 900 seconds (15 minutes). With this options another frequency in seconds can be specified. -log log-options Allows to log special events. log-options is a logical sum of values for particular events - 1 for logging rpc calls, 2 for logging broken server calls, 4 for logging server changes. -no-dbus Disables DBUS support if compiled in. --version Prints the version number FILES
/etc/yp.conf configuration file. /var/yp/binding/[domainname].[version] binding file containing information about each NIS domain. /var/run/ypbind.pid contains the process id of the currently running ypbind master process. SEE ALSO
syslog(3), domainname(1), yp.conf(5), ypdomainname(8), ypwhich(1), ypserv(8), ypset(8) AUTHOR
ypbind-mt was written by Thorsten Kukuk <kukuk@thkukuk.de>. ypbind-mt 04/09/2013 YPBIND(8)
All times are GMT -4. The time now is 08:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy