Ξ welcome to cryptostorm's member forums ~ you don't have to be a cryptostorm member to post here Ξ
Ξ any OpenVPN configs found on the forum are likely outdated. For the latest, visit here or GitHub Ξ
Ξ If you're looking for tutorials/guides, check out the new https://cryptostorm.is/#section6 Ξ

Forum instability of late

Post a reply

:
In an effort to prevent automatic submissions, we require that you enter the letters that are written in red.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek: :angel: :clap: :crazy: :eh: :lolno: :problem: :shh: :shifty: :sick: :silent: :think: :thumbdown: :thumbup: :wave: :wtf: :yawn:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

If you wish to attach one or more files enter the details below.

Expand view Topic review: Forum instability of late

Re: Forum instability of late update.

Post by rwilcher » Tue Aug 04, 2015 7:21 pm

Got things to work by changing to us - west endpoint in the widget.
Dont really know why the one I have been using won't authenticate any more.

Re: Forum instability of late

Post by rwilcher » Tue Aug 04, 2015 4:18 pm

Anyone experiencing logins problems into cstorm? Was fine
yesterday but hangs at logging into darknet. Retries after
60 secs.

Re: Forum instability of late

Post by df » Sun Aug 02, 2015 10:34 pm

We could put it in a jail/chroot, but the cPanel problems will continue.
Better to just move it off onto a proper VM.

Re: Forum instability of late

Post by parityboy » Sun Aug 02, 2015 9:37 pm

@df

Thanks for the update. Question: how is cPanel related to phpBB? Since you have root access to the server, could you not simply place phpBB in a jail along with its attendant web server (nginx?) and DB and administer it separately?

Oh, and PJ: you are hereby ordered to self-flagellate as an atonement for your naked transgression(s). :P

Forum instability of late

Post by df » Sun Aug 02, 2015 9:10 pm

Just wanted to reassure everyone that the recent SQL errors some people have noticed on the forum is NOT an attack against the website.

The error:
Table ‘phpbb_sessions’ is marked as crashed and should be repaired

Is caused by a change cPanel made to the MySQL database structure when we moved everything from the old Datacell server to this new Leaseweb.de one. On the old server we forced cPanel not to update because it was doing too many things we didn't like, and we are planning to get rid of cPanel anyways. So on the new server the structure on most databases got pretty screwed up. I've tried to manually fix most of it, but there's still some residual problems.

Eventually we'll move off of this Leaseweb server to somewhere else (without cPanel), which isn't as easy as it sounds. cPanel likes to put a strangle hold on almost every service, making moves to a non-cPanel server a little harder. The final setup after the next move will probably involve VMs (KVM), having things like the websites and the email servers separated for security, also because it will make it easier to do live migrations of a single service (like email) to another network.

Also, I added a script to cronjob (runs every minute) that will notify us when another one of these forum errors pops up, so we don't have to wait for someone to tell us the forum is down. For the curious, the script is:

Code: Select all

#!/bin/bash
if wget -SO- cryptostorm.org 2>&1|grep "General Error"; then
 if wget -SO- cryptostorm.org 2>&1|grep "marked as crashed and should be repaired"; then
  mysql csorg_phpbb -e'REPAIR TABLE phpbb_sessions'
 else
  echo "Forum is spitting out SQL errors, and it's not the phpbb_sessions thing" | mail -s "Forum is screwed up" df@cryptostorm.is
 fi
fi

EDIT: Added more code to the above script to make it check for the mysql.sock error that was on the forum earlier today, but that error causes the website to respond with "HTTP/1.1 503 Service Unavailable" instead of the normal "HTTP/1.1 200 OK". Problem is that the autofixing script uses wget, and wget stops trying to read the webpage if it gets anything but "HTTP/1.1 200 OK". So gotta modify the above a bit...

Oh and as for the mysql.sock error earlier this morning, PJ did that, so feel free blame him :-P

Top

Nothing to display.

Login