As you have noticed, our services were down for a long time. To reassure you, there was no hack or anything like that going on.
The main issue is that our server space is nearing its end, and we are having issues with WordPress clogging up server space with an exponential amount of logs, filling the limited space we have available.
The reason for the long outage had to do with the fact that none of us was near a computer for the past few hours, since most of us are enjoying holidays abroad. So, it was just a matter of Murphy’s law, and not a major technical issue.
The server is alright for now, and we are going to look for a new server very soon.
Speak for yourself, Uncle. I was beside myself for all the hours of down time (joking, I expected it to be up as soon as was feasible and wasn’t alarmed, just more fun to pretend I was fainting and sweating bullets).
I expected as much - Murphy raises his ugly little head especially when there’s no one around to mitigate.
Hopefully you are all still enjoying your time off!
I would rather a selective deletion campaign take place. I wish I could delete some of my old threads (can I?)? I wouldn’t expect to be able to delete others..but maybe mine?
Well, actually the forum itself shoudln’t need workpress at all, it just the website, discovery and the rest that relies upon it I guess. Just based upon the traffic, the forum may see the most impressions. And there are definitely some leaner alternatives than wordpress around nowadays.
But that might require some time, indeed.
Anyway, has been a nice day without reading the never-ending discussions about the current AUR situation
The issue is that the server’s storage capacity is almost at it’s end. When WordPress fills up the remaining space, there is no room left to keep the services up and reachable, regardless of the forum not using the WordPress services. It just shuts down.
I totally get that the forum goes down together with the host.
I’m not saying that this has to be addressed to deploy a clear seperation between wordpress and discourse.
One could inspect the wordpress logs if all the discourse page impressions are cluttering the logs of the wordpress service, i don’t have a clue if discourse is deployed via an wordpress plugin or not.
Essentially, from my point of view, a little downtime doesn’t hurt. And it’s your desicison which route to take to avoid such minor services interruptions, no need to start an fully fledged overhaul.
It is out of the question that moving onto a new server, clutter prevention within wordpress itself and / or a clear separation between wordpess and discourse on the server. Each one of those steps would involve some effort and if it is the most time efficient solution to settle for a new server to address the issue, so be it.
In essence, I only heard “wordpress” log and immediately thought - that’s not really the state of the art within commercial b2b solutions anymore… and thought that it could be addressed eventually with an workaround to prevent that exponential log clutter. No need for justifications from your side, at all.
Discourse and WordPress are separated from each other; the issue is that the disk on the server, which they both are running on, is almost full.
But we have found the culprit, and it needs time to address it, in addition to the fact that we need to migrate to another server with larger storage capacity.
BTW, @dbarronoss, removing threads within Discourse is a very laborious task. We then have to sift through seven years of threads and posts from every single user who is and was on our forum. And then there is also the issue of threads originally being part of another thread, which will cause dead redirections.
This happened right around the time I misplaced my phone after recieving a head injury (long story but I’m on the mend now), only just found it a few hours ago in the washing machine turned off.
