alarmdecoder.com

Just noticed that notification emails (which come to my text message, the whole reason for having this device) are no longer working. Not sure why either.

In several log files I'm seeing this;

Code: Select all

Jun  4 07:06:59 AlarmDecoder kernel: [  134.814093] random: crng init done
Jun  4 07:06:59 AlarmDecoder kernel: [  134.814101] random: 7 urandom warning(s) missed due to ratelimiting
pi@AlarmDecoder:/var/log $ sudo cat kern.log


Jun  4 07:06:59 AlarmDecoder kernel: [  134.814093] random: crng init done
Jun  4 07:06:59 AlarmDecoder kernel: [  134.814101] random: 7 urandom warning(s) missed due to ratelimiting
pi@AlarmDecoder:/var/log $ sudo cat messages

Further when I go into the webapp and hit save and test email I get this error in red on the page top;

Code: Select all

Error sending test notification: getrandom() initialization failed. (_ssl.c:661)

There have been ZERO changes to the configuration of Alarm decoder and other devices I have are able to send email from that email account I'm using so the problem definitely is in alarmdecoder. Alarmdecoder email worked last week. Apt is all up to date.



I think this is unrelated, but I get a lot of this in the logs;

Code: Select all

Jun  4 07:05:53 AlarmDecoder sm-msp-queue[578]: unable to qualify my own domain name (AlarmDecoder) -- using short name

I tried this but it didn't seem to help;
https://linuxconfig.org/sendmail-unqual ... d-hostname

I noticed I was three commits behind, updated and checked apt to see everything up to date there. Rebooted and still same problem.

So apparently this forum and product have been abandoned? We have spam posts that have stayed here for days and no answers. That's really sad.

I spent some time yesterday backing up my config, imaging a fresh SD card with the image posted here. Got it up and running, did all updates and restored my config. Email worked yesterday, today it did not with the same error. Noticed there were now some updates showing in the web app that didn't show yesterday, did those and email works again. I really don't know what to think here, seems I can't rely on this thing any more.

Sorry I have not been spending much time on the forums been busy trying to get new stuff added.

Not sure why you had that strange update issue. The latest update was big and likely your system failed on the old Raspbian 8 image due to expiring and old packages with so many SSL changes in the past year.

The latest image AFAIK is solid out of the box for email but maybe it was related to a new SSL issue that has twilio broken.

To fix twilio on the current image this so far has worked. I am testing a new image now with all of the latest patches and this fix I hope to have done in the next few days but I have lots of testing still to finish.

sudo pip uninstall python-cryptography
sudo pip install python-cryptography

As for forums spam is way to crazy I shut it down for signups. Now I have to approve everyone. Mostly I just see spam bots I reject every day or two.

I recommend people signup and then email ad2usb@support.nutech.com to be sure I activate it and that the person is human.

Best
SM

Maxburn,
I solved this by following the steps in this guide: https://www.howtoforge.com/helping-the- ... bian-lenny

Here are the steps:
1) Install rng-tools with this command
sudo apt-get install rng-tools
2) Edit the config file.
sudo nano /etc/default/rng-tools
3) Add the line "HRNGDEVICE=/dev/urandom" as shown here:

# Configuration for the rng-tools initscript
# $Id: rng-tools.default,v 1.1.2.5 2008-06-10 19:51:37 hmh Exp $

# This is a POSIX shell fragment

# Set to the input source for random data, leave undefined
# for the initscript to attempt auto-detection. Set to /dev/null
# for the viapadlock driver.
#HRNGDEVICE=/dev/hwrng
#HRNGDEVICE=/dev/null
HRNGDEVICE=/dev/urandom

# Additional options to send to rngd. See the rngd(8) manpage for
# more information. Do not specify -r/--rng-device here, use
# HRNGDEVICE for that instead.
#RNGDOPTIONS="--hrng=intelfwh --fill-watermark=90% --feed-interval=1"
#RNGDOPTIONS="--hrng=viakernel --fill-watermark=90% --feed-interval=1"
#RNGDOPTIONS="--hrng=viapadlock --fill-watermark=90% --feed-interval=1"

4) Start the tool with this command in case it doesn't start automatically:
sudo /etc/init.d/rng-tools start

Reboot the Pi with sudo reboot and now notifications should send emails again.

-Bill

Hmm, I never got notification of these replies. Also this morning when I encountered this problem again the whole alarmdecoder.com site was unreachable.

I want to reiterate that this had the same issue with a fresh install of the provided stretch 9 provided Pi image here on a fresh high endurance SD card, with all apt-get update && apt-get dist-upgrades done, and the updates within the web app done. Only thing I took from the old one was the backup which restored my config nicely, thanks for that. On this fresh install notifications were hit and miss, same as before I started with a fresh image.

Again searching the errors in the logs lead me to this post: https://www.reddit.com/r/Ubiquiti/comme ... pberry_pi/

A simple "sudo apt-get install haveged" seems to have fixed the issue, several restarts later and notifications worked consistently and the message log looks better. Does indeed look to be lack of entropy based issues.

Thanks! That is what I was looking for. I will continue my testing and "hopefully" get to a new image. It is just me and I am just a little under water currently so again thanks all the help is appreciated very much.

Installing haveged work perfectly for me. Thanks Maxburn!

Code: Select all

$ sudo apt-get install haveged

and then a

Code: Select all

sudo reboot

I do not know if the reboot is needed?

Installing haveged work perfectly for me. Thanks Maxburn!

Code: Select all

$ sudo apt-get install haveged

and then a

Code: Select all

$ sudo reboot

I do not know if the reboot is needed?