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
GDBUS(1)							   User Commands							  GDBUS(1)

NAME
gdbus - Tool for working with D-Bus objects SYNOPSIS
gdbus introspect [--system | --session | --address address] --dest bus_name --object-path /path/to/object [--xml] [--recurse] [--only-properties] gdbus monitor [--system | --session | --address address] --dest bus_name [--object-path /path/to/object] gdbus call [--system | --session | --address address] --dest bus_name --object-path /path/to/object --method org.project.InterfaceName.MethodName [--timeout seconds] ARG1 ARG2... gdbus emit [--system | --session | --address address] --object-path /path/to/object --signal org.project.InterfaceName.SignalName [--dest unique_bus_name] ARG1 ARG2... gdbus help DESCRIPTION
gdbus is a simple tool for working with D-Bus objects. COMMANDS
introspect Prints out interfaces and property values for a remote object. For this to work, the owner of the object needs to implement the org.freedesktop.DBus.Introspectable interface. If the --xml option is used, the returned introspection XML is printed, otherwise a parsed pretty representation is printed. The --recurse option can be used to introspect children (and their children and so on) and the --only-properties option can be used to only print the interfaces with properties. monitor Monitors one or all objects owned by the owner of bus_name. call Invokes a method on a remote object. Each argument to pass to the method must be specified as a serialized GVariant except that strings do not need explicit quotes. The return values are printed out as serialized GVariant values. emit Emits a signal. Each argument to include in the signal must be specified as a serialized GVariant except that strings do not need explicit quotes. help Prints help and exit. BASH COMPLETION
gdbus ships with a bash completion script to complete commands, destinations, bus names, object paths and interface/method names. EXAMPLES
This shows how to introspect an object - note that the value of each property is displayed: $ gdbus introspect --system --dest org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManager/Devices/0 node /org/freedesktop/NetworkManager/Devices/0 { interface org.freedesktop.DBus.Introspectable { methods: Introspect(out s data); }; interface org.freedesktop.DBus.Properties { methods: Get(in s interface, in s propname, out v value); Set(in s interface, in s propname, in v value); GetAll(in s interface, out a{sv} props); }; interface org.freedesktop.NetworkManager.Device.Wired { signals: PropertiesChanged(a{sv} arg_0); properties: readonly b Carrier = false; readonly u Speed = 0; readonly s HwAddress = '00:1D:72:88:BE:97'; }; interface org.freedesktop.NetworkManager.Device { methods: Disconnect(); signals: StateChanged(u arg_0, u arg_1, u arg_2); properties: readonly u DeviceType = 1; readonly b Managed = true; readwrite o Ip6Config = '/'; readwrite o Dhcp4Config = '/'; readwrite o Ip4Config = '/'; readonly u State = 2; readwrite u Ip4Address = 0; readonly u Capabilities = 3; readonly s Driver = 'e1000e'; readwrite s Interface = 'eth0'; readonly s Udi = '/sys/devices/pci0000:00/0000:00:19.0/net/eth0'; }; }; The --recurse and --only-properties options can be useful when wanting to inspect all objects owned by a particular process: $ gdbus introspect --system --dest org.freedesktop.UPower --object-path / --recurse --only-properties node / { node /org { node /org/freedesktop { node /org/freedesktop/UPower { interface org.freedesktop.UPower { properties: readonly b IsDocked = true; readonly b LidForceSleep = false; readonly b LidIsPresent = false; readonly b LidIsClosed = false; readonly b OnLowBattery = false; readonly b OnBattery = false; readonly b CanHibernate = true; readonly b CanSuspend = true; readonly s DaemonVersion = '0.9.10'; }; node /org/freedesktop/UPower/Policy { }; node /org/freedesktop/UPower/Wakeups { interface org.freedesktop.UPower.Wakeups { properties: readonly b HasCapability = true; }; }; }; }; }; }; In a similar fashion, the introspect command can be used to learn details about the Notify method: [...] interface org.freedesktop.Notifications { methods: GetServerInformation(out s return_name, out s return_vendor, out s return_version, out s return_spec_version); GetCapabilities(out as return_caps); CloseNotification(in u id); Notify(in s app_name, in u id, in s icon, in s summary, in s body, in as actions, in a{sv} hints, in i timeout, out u return_id); }; [...] With this information, it's easy to use the call command to display a notification $ gdbus call --session --dest org.freedesktop.Notifications --object-path /org/freedesktop/Notifications --method org.freedesktop.Notifications.Notify my_app_name 42 gtk-dialog-info "The Summary" "Here's the body of the notification" [] {} 5000 (uint32 12,) Monitoring all objects on a service: $ gdbus monitor --system --dest org.freedesktop.ConsoleKit Monitoring signals from all objects owned by org.freedesktop.ConsoleKit The name org.freedesktop.ConsoleKit is owned by :1.15 /org/freedesktop/ConsoleKit/Session2: org.freedesktop.ConsoleKit.Session.ActiveChanged (false,) /org/freedesktop/ConsoleKit/Seat1: org.freedesktop.ConsoleKit.Seat.ActiveSessionChanged ('',) /org/freedesktop/ConsoleKit/Session2: org.freedesktop.ConsoleKit.Session.ActiveChanged (true,) /org/freedesktop/ConsoleKit/Seat1: org.freedesktop.ConsoleKit.Seat.ActiveSessionChanged ('/org/freedesktop/ConsoleKit/Session2',) Monitoring a single object on a service: $ gdbus monitor --system --dest org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManager/AccessPoint/4141 Monitoring signals on object /org/freedesktop/NetworkManager/AccessPoint/4141 owned by org.freedesktop.NetworkManager The name org.freedesktop.NetworkManager is owned by :1.5 /org/freedesktop/NetworkManager/AccessPoint/4141: org.freedesktop.NetworkManager.AccessPoint.PropertiesChanged ({'Strength': <byte 0x5c>},) /org/freedesktop/NetworkManager/AccessPoint/4141: org.freedesktop.NetworkManager.AccessPoint.PropertiesChanged ({'Strength': <byte 0x64>},) /org/freedesktop/NetworkManager/AccessPoint/4141: org.freedesktop.NetworkManager.AccessPoint.PropertiesChanged ({'Strength': <byte 0x5e>},) /org/freedesktop/NetworkManager/AccessPoint/4141: org.freedesktop.NetworkManager.AccessPoint.PropertiesChanged ({'Strength': <byte 0x64>},) Emitting a signal: $ gdbus emit --session --object-path /foo --signal org.bar.Foo "['foo', 'bar', 'baz']" Emitting a signal to a specific process: $ gdbus emit --session --object-path /bar --signal org.bar.Bar someString --dest :1.42 BUGS
Please send bug reports to either the distribution bug tracker or the upstream bug tracker at https://bugzilla.gnome.org/enter_bug.cgi?product=glib. SEE ALSO
dbus-send(1) GIO
GDBUS(1)
All times are GMT -4. The time now is 03:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy