Raspberry Pi 2 Device offline


#1

Pi 2 Model B, Web dashboard

After 2 days Pi stops communicating…

pi@raspberrypi:~ $ sudo service myDevices status
● myDevices.service - myDevices service
Loaded: loaded (/etc/systemd/system/myDevices.service; enabled)
Active: active (running) since Wed 2017-02-15 09:06:02 UTC; 19h ago
Main PID: 433 (python3)
CGroup: /system.slice/myDevices.service
‣ 433 /usr/bin/python3 -m myDevices -P /var/run/myDevices.pid

Feb 15 09:06:02 raspberrypi systemd[1]: Starting myDevices service…
Feb 15 09:06:02 raspberrypi systemd[1]: Started myDevices service.
Feb 15 09:06:03 raspberrypi systemd[433]: pam_exec(login:session): conversation failed
Feb 15 09:06:03 raspberrypi systemd[433]: pam_unix(login:session): session opened for user root by (uid=0)
Feb 16 04:13:34 raspberrypi systemd[1]: Started myDevices service.

Services running
[ - ] alsa-utils
[ + ] avahi-daemon
[ + ] bluetooth
[ - ] bootlogs
[ - ] bootmisc.sh
[ - ] checkfs.sh
[ - ] checkroot-bootclean.sh
[ - ] checkroot.sh
[ + ] console-setup
[ + ] cron
[ + ] dbus
[ + ] dhcpcd
[ + ] dphys-swapfile
[ + ] fake-hwclock
[ + ] hdparm
[ - ] hostname.sh
[ - ] hwclock.sh
[ + ] kbd
[ + ] keyboard-setup
[ - ] killprocs
[ + ] kmod
[ + ] lightdm
[ - ] motd
[ - ] mountall-bootclean.sh
[ - ] mountall.sh
[ - ] mountdevsubfs.sh
[ - ] mountkernfs.sh
[ - ] mountnfs-bootclean.sh
[ - ] mountnfs.sh
[ + ] networking
[ - ] nfs-common
[ + ] ntp
[ - ] plymouth
[ - ] plymouth-log
[ + ] procps
[ + ] raspi-config
[ + ] rc.local
[ - ] rmnologin
[ - ] rpcbind
[ - ] rsync
[ + ] rsyslog
[ - ] sendsigs
[ + ] ssh
[ - ] sudo
[ + ] triggerhappy
[ + ] udev
[ + ] udev-finish
[ - ] umountfs
[ - ] umountnfs.sh
[ - ] umountroot
[ + ] urandom
[ - ] vncserver-virtuald
[ - ] vncserver-x11-serviced
[ + ] webiopi
[ - ] x11-common

pi@raspberrypi:~ $ ps axu | grep python
root 433 10.5 4.5 132344 20060 ? Ssl Feb15 120:59 /usr/bin/python3 -m myDevices -P /var/run/myDevices.pid
root 512 2.7 3.0 36120 13712 ? Sl Feb15 31:09 /usr/bin/python3 -m webiopi -l /var/log/webiopi -c /etc/webiopi/config
root 6347 1.0 0.2 1900 1200 ? S 04:15 0:00 /bin/sh -c python3 -m myDevices.os.getsysteminfo
root 6348 103 1.5 11492 7116 ? R 04:15 0:01 python3 -m myDevices.os.getsysteminfo
pi 6350 0.0 0.4 4272 2040 pts/0 S+ 04:15 0:00 grep --color=auto python


#2

Now the pi works? If you try to connect, the pi works?
Are you sure of your internet? If your lan goes down and after up, the pi is disconnected from Cayenne.


#3

pi works perfectly.

pi@raspberrypi:~ $ sudo ping google.com
PING google.com (74.125.232.226) 56(84) bytes of data.
64 bytes from 74.125.232.226: icmp_seq=1 ttl=49 time=79.6 ms
64 bytes from 74.125.232.226: icmp_seq=2 ttl=49 time=78.5 ms
64 bytes from 74.125.232.226: icmp_seq=3 ttl=49 time=75.5 ms
64 bytes from 74.125.232.226: icmp_seq=4 ttl=49 time=73.4 ms
64 bytes from 74.125.232.226: icmp_seq=5 ttl=49 time=81.3 ms


#4

@swanson2,

Just to get it out of the way because we’ve had bad behaviour due to power supplies with not enough wattage, what is the current output of the power supply you are using to power your pi?

Cheers,

Craig


#5

Craig, I’m using 2A. 5V.
Something strange had happened yesterday. Pi became online. Nothing was changed. May be really it a bad power cube…


#6

…or an intermittent connection.

I lose connection on my older PIs because my USB dongle is loose in the connector.