i know there has been posts about issues with poll.bsy hanging. so
instead of sticking with the most recent version, i backed down to the most recent stable version and still see poll.bsy hanging a few times a week!
anyway, i am running pi 32 bit and wondering if anyone has a solution or work-around for the ongoing issue.
i know there has been posts about issues with poll.bsy hanging. so
instead of sticking with the most recent version, i backed down to the most recent stable version and still see poll.bsy hanging a few times a week!
hi all
i know there has been posts about issues with poll.bsy hanging. so
instead of sticking with the most recent version, i backed down to the most recent stable version and still see poll.bsy hanging a few times a week!
i know there has been posts about issues with poll.bsy hanging. so instead of sticking with the most recent version, i backed down to th most recent stable version and still see poll.bsy hanging a few times week!
anyway, i am running pi 32 bit and wondering if anyone has a solution work-around for the ongoing issue.
I wrote a script that *I* trust. Please review it for yourself, I could
be an idiot and all...
-----
$ cat bsy.sh
#!/usr/bin/env bash
# Mystic BBS software .bsy file manager
# At times, Mystic leaves a poll.bsy, mutil.bsy, or mis.bsy file when it should # NOT be present. This script checks if fidopoll or mutil is running; if neither
# process is running (meaning those .bsy files should NOT be present) -
it then # checks for any .bsy files that have been present for longer
than 60 minutes # and removes them if found. This helps prevent stale or orphaned .bsy files # from causing issues with the system.
# Set the working directory to the Mystic installation directory WDIR="/home/pi/mystic"
# Change to the working directory
cd $WDIR
# Check if the 'mis poll' or 'mutil' is running.
# The \ps command ensures that we use the system's ps command, bypassing any # aliases. If either are running, set output to "RUNNING", otherwise set it to # "NOT RUNNING".
F=$(\ps -ef | grep "mis poll" | grep -v grep >/dev/null; [ $? -gt 0 ] && echo "NOT RUNNING" || echo "RUNNING")
M=$(pidof mutil; [ $? -gt 0 ] && echo "NOT RUNNING" || echo "RUNNING")
# Find all .bsy files related to Mystic that have been modified more
than 60 # minutes ago. The -mmin +60 option filters for files older than 60 minutes. B=$(find . -type f -name "*.bsy" -mmin +60 | grep echomail | wc -l)
# Display the status of fidopoll and mutil processes and the number of
old .bsy # files found.
cat << EOF
Fidopoll pidof result: $F
Mutil pidof result: $M
Number of BSY files (older than 60 min): $B
EOF
# If there are any .bsy files older than 60 minutes, and neither
fidopoll nor i # mutil is running, it means these .bsy files are likely orphaned and can be # safely removed.
if [[ $B -gt 0 && ($F == "NOT RUNNING" && $M == "NOT RUNNING") ]]; then
# Inform the user that orphaned .bsy files are being cleared.
echo -e "\nClearing $B orphaned BSY files (older than 60 min)..."
# Loop through each .bsy file found and remove it.
for F in $(find . -type f -name "*.bsy" -mmin +60 | grep echomail); do
echo "Removing: $F"; rm $F
done
# Run the mailout process using mutil to ensure any queued mail is processed. ./mutil mailout
# Force a fidopoll to make sure the system is synchronized with other nodes. ./mis poll force
fi
-----
i know there has been posts about issues with poll.bsy hanging. so instead of sticking with the most recent version, i backed down to th most recent stable version and still see poll.bsy hanging a few times week!
I want to say I have a nightly script that clears out the bsy files.
Maybe a script for now?
i know there has been posts about issues with poll.bsy hanging. so instead of sticking with the most recent version, i backed down to th most recent stable version and still see poll.bsy hanging a few times week!
I know it goes against the proper way of doing things, but I added an event to kill poll.bsy hourly. It tries to remove and if it is there it removes it if not just gives an error 1.
I know it goes against the proper way of doing things, but I added an event to kill poll.bsy hourly. It tries to remove and if it is there removes it if not just gives an error 1.
yes i fear that might do harm, but worth a try.
I wrote a script that *I* trust. Please review it for yourself, I could
be an idiot and all...
On 19 Oct 2024, paulie420 said the following...
I wrote a script that *I* trust. Please review it for yourself, I cou be an idiot and all...
That looks just like mine! =)
I wrote a script that *I* trust. Please review it for yourself, I cou be an idiot and all...
That looks just like mine! =)
I wrote a script that *I* trust. Please review it for yourself, I could
be an idiot and all...
I wrote a script that *I* trust. Please review it for yourself, I cou be an idiot and all...
hey,i haven't been able to get the script to work and i get a syntax error. is the script run from /mystic or somewhere else
MeaTLoTioN mentioned that it is HIS script, so maybe grab it from his github to make sure there were no syntax errors from the Mystic MSG post???
https://github.com/christiansacks/chk_orph_bsy
MeaTLoTioN mentioned that it is HIS script, so maybe grab it from his github to make sure there were no syntax errors from the Mystic MSG post???
https://github.com/christiansacks/chk_orph_bsy
I thought it was one I made w/ ChatGPT but was wrong. That being said, I can't say for sure it will work on your setup!!
| Sysop: | Tetrazocine |
|---|---|
| Location: | Melbourne, VIC, Australia |
| Users: | 4 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 189:05:07 |
| Calls: | 62 |
| Files: | 21,500 |
| Messages: | 70,927 |