SoylentNews is people
SoylentNews
from the Constants-aren't-and-variables-won't dept.
[2021-02-14 15:53:00 UTC: UPDATE added need to check apache log before doing a slash -restart]
We seem to have experienced some difficulties with the SoylentNews site.
I've noticed that both the number of hits and comments for each story do not seem to be updating.
Corrective measures taken:
- "Bounce" the Servers I doubted it would help, but it causes no harm to try it, so why not? And, as expected, it did not help, either.:This is my personal "bounce" script:
cat ~/bin/bounce#!/bin/bash
servers='hydrogen fluorine'
for server in ${servers} ; do echo Accessing: ${server} && rsh ${server} /home/bob/bin/bounce ; doneWhich, in turn, runs the following script on each of the above servers:
cat /home/bob/bin/bounce
#!/bin/bash
sudo /etc/init.d/varnish restart
sudo -u slash /srv/soylentnews.org/apache/bin/apachectl -k restart - Restart slash For those who are unaware, slash has its own internal implementation of what is, effectively, cron. It periodically fires off tasks that support the site's operations. But, this potentially has side-effects, so first need to check the apache error_log.
# Go to the appropriate server:
ssh fluorine
# Ensure the apache log is not showing issues: tail -f /srv/soylentnews.org/apache/logs/error_log
# Restart slash:
sudo /etc/init.d/slash restart
>> slashd slash has no PID file
>> Sleeping 10 seconds in a probably futile attempt to be clean: ok.
>> Starting slashd slash: ok PID = 3274NB: this failed to run to a successful conclusion when I originally tried it a few hour ago. I gave it one more try while writing this story... it seemed to run okay this time?!
Things appears to be running okay, now. Please reply in the comments if anything else is amiss. Alternatively, mention it in the #dev channel on IRC (Internet Relay Chat, or send an email to admin (at) soylentnews (dot) org.
We now return you to the ongoing discussion of: teco or ed?
(Score: 0) by Anonymous Coward on Sunday February 14 2021, @09:29AM (4 children)
If slash seems to require restarting a few times a year, does there seem to be any pattern of how many days before that seems to happen? Or is it completely random? Because if it is the former, maybe some preventative scheduled reboot would be in order. But you've probably already thought of that.
(Score: 0) by Anonymous Coward on Sunday February 14 2021, @11:04AM (3 children)
I've suggested various watchdogs in the past but the hiccups seem to be too random and far between to be worth the trouble.
(Score: 3, Interesting) by The Mighty Buzzard on Sunday February 14 2021, @11:32AM (2 children)
Bingo. The "a couple times a year" is on average. I don't remember having to restart it in 2019 at all aside from it being restarted on server reboots.
My rights don't end where your fear begins.
(Score: 2) by RS3 on Sunday February 14 2021, @12:06PM (1 child)
cron.monthly job? Maybe with a file that contains a countdown variable so the restart only happens every so many months?
Hate those kinds of workarounds though. If I had time I'd look into the code...
(Score: 3, Interesting) by The Mighty Buzzard on Sunday February 14 2021, @02:16PM
Don't know that the issue is time-based but it wouldn't hurt anything to restart it once in a while.
My rights don't end where your fear begins.