Seems the database got corrupted and wouldn't allow posting. I think it's repaired now.
Testing...
Looks good...
(P.S. Pull up your pants! Or spackle that thing shut!)
Up late too Dave
, I thought that was just the innernet as I also had slow and disappearing (404's) at that time too .
But just got this after clicking the post button
Connection Problems
Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later.
Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later.
That one, apparently for the last for the last 3 hours was due to the MySQL server being locked up. A database service reboot fixed it.
Hmm, all sorts of problems at the moment it seems. Had to reboot the MySQL server again, and there is a big load on the server. Something isn't right...
Hmm, all sorts of problems at the moment it seems. Had to reboot the MySQL server again, and there is a big load on the server. Something isn't right...
I remember having a similar issue with my company's web host. Maybe the physical server is starting to go. Any way to request a migration to a different machine?
I remember having a similar issue with my company's web host. Maybe the physical server is starting to go. Any way to request a migration to a different machine?
I've been thinking about that. No real evidence that's the case, but it can't hurt I guess, but does seem to have had more downtime/crashes/reboots than I'd expect. I can ask...
I remember having a similar issue with my company's web host. Maybe the physical server is starting to go. Any way to request a migration to a different machine?
I've been thinking about that. No real evidence that's the case, but it can't hurt I guess, but does seem to have had more downtime/crashes/reboots than I'd expect. I can ask...
Yes, but without knowing what the problem is it is equally likely it can't (won't) help either. If they are willing to migrate you to a different machine as a "goodwill" gesture, which is what it will be in the absence of any evidence of the cause of the problem, then they will become increasingly less willing in the event of a recurrence in future. They'll say no anyway, unless they can see a fault.
I suggest looking at the systems logs to see what messages are present. There may well be an answer there. Something has changed. It could be a server hardware fault. It could also be a capacity problem or a software upgrade has introduced a bug, either on the server itself or with another server it communicates with.
Do you think it could be something dns related? Intermittently pointing towards the website's old location? I don't know if an intermittent DNS problem is possible, just throwing out ideas.
More than posting, my problem just to access the site. I cannot recall but there was a three-letters acronym involved, something like MPS or similar and an error code, starting with 5, but not sure really.
I did not have to log on this evening as I could not log off early this morning as that message kept popping up .
The site behaves real snappy here atm , instantaneous practically ..
Had this happen a few times, somewhat randomly. Seems to come and go.
Tim
I have had 2 or 3 issues getting onto the EEVblog main site and the forum over the last few weeks.
I have had 2 or 3 issues getting onto the EEVblog main site and the forum over the last few weeks.
Me too. Seems reliability is an issue ATM.
Had this again this morning, though it seems all good now.
Connection Problems
Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later.
I have had 2 or 3 issues getting onto the EEVblog main site and the forum over the last few weeks.
Me too. Seems reliability is an issue ATM.
Had this again this morning, though it seems all good now.
Connection Problems
Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later.
The same here, several times today.
I also had problems Monday Oct 20 starting at 10AM and ongoing to 10:30AM MST. I tried later in the afternoon around 2PM MST and was able to get on.
I was able to ping
www.eevblog.com, but the forum and main page were down with the same error messages posted by others.
Yep, the server is having real problem at the moment, I need to speak with HostGator.
The database issues I'm pretty sure are caused by the server going down, and when it does, there is always a chance a database table can get corrupted.
Hi All,
I am sorry I have not been around to reply to any of this, I have been put out of action as I have been recovering from the whooping cough. I have suggested that Dave have all the RAM in the server replaced, the constant table crashes and now these major crashes point the finger at either RAM or HDD, but since the HDD is a RAID array and as far as I am aware is not reporting any issues, I would not expect this kind of crash (RAM is the easier to replace first too).
Would RAM errors not show up somewhere?
IIRC it's a Linux box, single bit ECC errors would show up in dmesg.
Hostgator are saying that it's the MySQL that is going down, and not the whole server. They are working on it...
With regards to RAM, It looks like the server may be overcommited, I have reduced the total ram that MySQL is allowed to use, but this does not explain why it is getting blown way out. It seems to occur when there is heavy load on the server, I am seeing oom errors that is killing MySQL and hundreds of PHP processes running at the same time. I am investigating what PHP is doing during these periods.
May be unrelated but the entire site was intermittent for me today from about 11.00am until 2.00PM GMT.
Doing some internal search's like 10 minutes ago a cupla times it came back > Database error/corruption retry later or something ..
May be unrelated but the entire site was intermittent for me today from about 11.00am until 2.00PM GMT.
It was related, logs show the database had crashed at that point.
Doing some internal search's like 10 minutes ago a cupla times it came back > Database error/corruption retry later or something ..
This may have occured while I was restarting the MySQL service to apply the memory changes.
Saw this earlier,
Table './eevblog_smp01/smf_members' is marked as crashed and should be repaired
Hope it's not hackers or something