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: 3, Informative) by martyb on Sunday February 14 2021, @02:37PM (2 children)
Yes, I'd seen a couple reports of "CSS failing to load" on IRC. Whenever I tried to reproduce it, all my attempts loaded successfully with no issues. I inquired of others there, and someone else confirmed things were loading okay for them, too. I'd seen that happen a few times before, so figured whatever went sideways had somehow righted itself and gotten back in line.
That said, thanks for mentioning it here. I'm starting to see a pattern. Every CSS "burp" does not necessarily lead to non-updating counts, *but* it does seem that every incident of non-updating counts was preceded by CSS issues. Can't prove a negative, of course, but I'll add this idea to my bag-o-tricks. Thanks again for the report!
Wit is intellect, dancing.
(Score: 3, Informative) by The Mighty Buzzard on Sunday February 14 2021, @03:06PM (1 child)
I wouldn't necessarily connect those dots too quickly. For some reason dev has the slashd issues without ever having the CSS issues. It's not a mystery we couldn't look into and fix, it's just not a dire emergency if it's a thirty second fix less often than once a month.
My rights don't end where your fear begins.
(Score: 2) by martyb on Sunday February 14 2021, @04:13PM
Wit is intellect, dancing.