The discussion revolves around a Discourse forum issue where users are experiencing a blank page. staticinvocation reports that restarting the docker instance and rebuilding did not resolve the issue, with log files showing errors related to PostgreSQL and SSH. webb shares a similar issue after updating via the admin dashboard, but notes that the log errors predate the update.
After troubleshooting, webb discovers that the discourse-akismet plugin, updated along with the discourse-tagging plugin, is the cause of the issue. Removing the plugin resolves the problem. riking subsequently announces that the akismet change has been rolled back, making it safe to update again.
I’ve had a Discourse forum running for about a month now, but today I woke up with the forum returning a completely blank page. Restarting the docker instance did not fix the issue.
I tried running ./launcher rebuild which appeared to have worked, but when navigating to the page it works once, and then returns an empty page for every request thereafter.
I took a look in the log files and they are completely spammed up with entries like this:
2015-05-08 17:06:51 UTC [65-1] LOG: could not open temporary statistics file "/var/run/postgresql/9.3-main.pg_stat_tmp/global.tmp": No such file or directory
Missing privilege separation directory: /var/run/sshd
Anyone know what’s up? I tried entering the instance already and touching the postgre file with no result.
I just did an update via the admin dashboard, and now my pages are blank as well. Looking at the page source, looks like it’s all there, just nothing is rendering.
I have the same exact log errors, but they predate today’s update, so I think probably unrelated to the current issue.
Well I found my issue: the discourse-akismet plugin, which I also updated along with the discourse-tagging plugin.
I removed discourse-akismet, did a rebuild, and my site is accessible again. I can’t imagine that this wasn’t tested prior to pushing out the Discourse 1.3.0.beta7 update…
