I've been having random issues, which I haven't been able to completely
track down and eradicate. What I did was write a shell script that runs
once a minute via crontab that checks to see if everything is OK with
ASSP. If not, the script reboots the server. I've had to tweak it a few
times, but this version has been very good at making sure that ASSP is
running. May not be the most elegant solution, but it keeps things
working and comments are welcome! Note this is running under Ubuntu
16.04 LTS. Note that I put a two minute delay on the shutdown in case I
was logged in working on something.
#!/bin/bash
upSeconds="$(cat /proc/uptime | grep -o '^[0-9]\+')"
upMins=$((${upSeconds} / 60))
if [ "${upMins}" -gt "5" ]
then
if busctl get-property org.freedesktop.login1
/org/freedesktop/login1 org.freedesktop.login1.Manager ScheduledShutdown
| grep reboot
then
echo Reboot pending
else
if tail -5 /usr/share/assp/logs/maillog.txt | grep "main\
exception\:\ error"
then
date +"exception error - %Y-%m-%d %H:%M:%S %Z" >>
/home/farokh/assp-bad.txt
shutdown -r 2 ASSP down...
exit 1
fi
if tail -5 /usr/share/assp/logs/maillog.txt | grep "\[Shutdown\]
ASSP finished work"
then
date +"shutdown stuck - %Y-%m-%d %H:%M:%S %Z" >>
/home/farokh/assp-bad.txt
shutdown -r 2 ASSP down...
exit 1
fi
if netstat -plnt | grep 55555
then
echo netstat good
else
date +"netstat - %Y-%m-%d %H:%M:%S %Z" >> /home/farokh/assp-bad.txt
shutdown -r 2 ASSP down...
exit 1
fi
if service assp status | grep "active (running)"
then
echo status good
else
date +"bad not running - %Y-%m-%d %H:%M:%S %Z" >>
/home/farokh/assp-bad.txt
shutdown -r 2 ASSP down...
fi
fi
else
echo "Up five minutes or less"
fi
exit 0
Farokh
----------------------------------------------------------------------------
Best Tech Service, LLC- When only the Best will do...
For all your technology needs including hosting solutions.
Cell: 914-262-1594
Like us on Facebook: https://www.facebook.com/besttechsvc
marka...@gmx.de wrote on 8/1/19 03:46:
I'm seeing this error, too. In an earlier reply, you mentioned a fix
for this, which should be included in assp 2.6.2 *Fortress* build
18107. You said: "version 7.49 fixes this problem". Which component
should have this version?
I'm running ASSP version 2.6.3 **SPAM-Evaporator** build 19169 on
Ubuntu 18.04.2, all modules are up-to-date. And the problem persist.
The limit for open files is already set to 65535.
Any hints?
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user
