[arm-allstar] Rpi 3B Lockup Problem

[Doug Crompton]

Jeff,

 Barring any other outside (network) issues I would say you have an
unstable system. It is rare for this to happen. The first thing I would do
is make sure you have good power to the Pi. Unstable power can cause all
kinds of problems. Try a different power source. Second it is very rare but
you could have bad hardware. If you have another Pi pop the SD card into it
and see if the same thing happens. If none of that fixes it then I would
say it is the SD card and you will need to burn a new image and re-setup.
We recommend Sandisk Ultra cards. You might also look at any changes you
made on the system just before this happened as a possible source of the
problem.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


On Thu, Mar 15, 2018 at 9:56 AM, "Jeffrey Lehman, KC8QCH via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Good Morning Everyone!
>
> Here's a fun for you.
>
> Last Friday/Saturday I flashed the (at the time) most recent Hamvoip image
> to my Rpi 3B. Over the last week everything ran great. Got everything
> configured the way I wanted and had no issues. At least until last
> night/today.
>
> Last Night I got home and noticed on Allmon that it could not connect to
> Asterisk Manager on my node. Ok, no big deal, so I tried to ssh in to
> restart asterisk and it wouldn't let me connect. So I checked a couple of
> other things (which I will note below in a second) and just pulled the
> power on the Pi and plugged it back in. It rebooted and everything looked
> ok.
>
> This morning I get into Allmon and it's again telling me that it can't
> connect. I try to ssh in and same thing. No dice. Unfortunately I am at
> work right now and my wife is not home till later so I can't unplug the Pi.
>
> After some checking both today and last night, here is where I stand:
>
> - I can't ssh into the Pi
> - The Node is not showing active on the Allstarlink status pages
> - It is however connected and showing active on Echolink
> - Zoiper is able to connect from my phone
> - Iaxrpt is able to connect from my pc
> - I can connect to Echolink nodes, but not to Allstar nodes.
>         - It seems it is logged into Echolink and not Allstar
> - APRS is not beaconing
> - From Zoiper/Iaxrpt I can send macro commands and connect commands (again
> only connecting to echolink nodes) and a few other random commands like ID
> and stuff, but I cannot get the time commands to work nor can I turn
> Autosky on or off for example.
> - I do not have a command setup yet to reboot the node from DTMF (Hadn't
> had a chance to get that setup yet)
>
> My setup
> - Raspberry Pi 3B
> - The (up until today) most recent Hamvoip image
> - It's a virtual Node with no radios or sound fobs connected.
> - running headless
> - I am not running broadcastify
>
> My gut says OS crash, but not a full crash so. I just hope there is not
> something running away on the Pi that will burn it out. I have a backup of
> my config files on my computer so if need be I can re-flash and go (which I
> may still do). I had not yet been able to image my SD card for a backup. I
> am just wondering what could be causing this so I can avoid it in the
> future.
>
> Any ideas? And go!
>
> Thanks in advance for any help and insight you all can share!
>
> Jeff, KC8QCH
>
> --
> Jeff Lehman, KC8QCH
> https://kc8qch.ddns.net
> kc8qch at gmail.com
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org