Post: #51

(08-31-2013 12:10 PM)Menace Wrote:  Still had a shutdown on the hour.

This sounds like a rogue cron job on the server. Maybe it's restarting the mysql daemon every hour on the hour?

Post: #52

You might want to disable the automatic table repair until you figure out what is going on.

ACP -> Task Manager -> Tables Check -> Enable

Post: #53

How do you guys know this stuff??^^

Post: #54

(08-31-2013 03:08 PM)el mechanico Wrote:  How do you guys know this stuff??^^

I've been developing for years, it's actually how I plan to become location independent one day

Post: #55

(08-31-2013 07:14 AM)Roosh Wrote:  Every hour the forum runs a script to check the tables. It finds a problem and then automatically shut down the forum, and then I have to open the board back up. So now we must check what's causing this problem.

Wouldn't it be possible to shut off the hourly automatic script that the forum is running, until the server technician has a chance to troubleshoot the situation?

Edit: Woops: WWT already beat me to the punch.. with more specifics....

Post: #56

(08-31-2013 03:08 PM)el mechanico Wrote:  How do you guys know this stuff??^^

After you have been programming for some time, you develop pretty good problem solving skills.

This helps but not on macs.

http://lmgtfy.com/?q=how+do+you+know+that+stuff

Post: #57

Not sure if you installed a new version of mysql when you upgraded, but it could have a low number of maximum connections set in my.ini, which would explain both the error message and the intermittent occurrences. A similar possibility is that the maximum number of open files in the OS is set too low, also would cause the problems you are seeing.

Is it on dedicated server, or shared?

Post: #58

I had a IT guy over yesterday he said

I.T. = googling stuff

True?

Post: #59

Just now reading the rest of the pasted error messages. The "incorrect key file" error is often caused by a full or close-to-full disk on the server.

Post: #60

(08-31-2013 03:17 PM)el mechanico Wrote:  I had a IT guy over yesterday he said

I.T. = googling stuff

True?

Ha, it's about 70% of fixing problems. The more experience you gain, the less you have to google. I knew a 60 year old DBA that still googled 1 out of every 5 problems.

Post: #61

(08-31-2013 03:14 PM)worldwidetraveler Wrote:  

(08-31-2013 03:08 PM)el mechanico Wrote:  How do you guys know this stuff??^^

After you have been programming for some time, you develop pretty good problem solving skills.

This helps but not on macs.

http://lmgtfy.com/?q=how+do+you+know+that+stuff

Emech hasn't made the connection that computers, like cars, require training and experience to troubleshoot and maintain. He still thinks there's a making his computer work, and the cdrom is supposed to spit out pita bread.

Post: #62

I disabled two tasks that could be causing it "Hourly Cleanup" and "RSS 2 Post") at the times it goes down, but still the same result. It's not obvious that anything from the forum side is causing it at this point.

I looked into the cronjob hourly function, and the only thing I found was modsecparse.pl (Mod Security). I googled the file name and there seem to be problems with it and mysql. I don't think it was enabled before the upgrade. Maybe this is the cause?

I have WHM / Cpanel.

Post: #63

(08-31-2013 03:17 PM)el mechanico Wrote:  I had a IT guy over yesterday he said

I.T. = googling stuff

True?

For the most part, just type the error message and see the solutions. The one that best fits your computer processor/brand is the most reliable.

EDIT: About your monitor...(it's the 2013 mac mini right?)

http://www.squidoo.com/best-mac-monitors

Post: #64

(08-31-2013 03:19 PM)ryanf Wrote:  

(08-31-2013 03:17 PM)el mechanico Wrote:  I had a IT guy over yesterday he said

I.T. = googling stuff

True?

Ha, it's about 70% of fixing problems. The more experience you gain, the less you have to google. I knew a 60 year old DBA that still googled 1 out of every 5 problems.

Why can nobody answer my question of which third party monitor works best with Mac mini then here?

Post: #65

(08-31-2013 03:23 PM)el mechanico Wrote:  

(08-31-2013 03:19 PM)ryanf Wrote:  

(08-31-2013 03:17 PM)el mechanico Wrote:  I had a IT guy over yesterday he said

I.T. = googling stuff

True?

Ha, it's about 70% of fixing problems. The more experience you gain, the less you have to google. I knew a 60 year old DBA that still googled 1 out of every 5 problems.

Why can nobody answer my question of which third party monitor works best wit Mac mini then here?

Because you posted computer questions in the lifestyle section you damn hipster.

Post: #66

(08-31-2013 03:22 PM)Roosh Wrote:  I disabled two tasks that could be causing it "Hourly Cleanup" and "RSS 2 Post") at the times it goes down, but still the same result. It's not obvious that anything from the forum side is causing it at this point.

I looked into the cronjob hourly function, and the only thing I found was modsecparse.pl (Mod Security). I googled the file name and there seem to be problems with it and mysql. I don't think it was enabled before the upgrade. Maybe this is the cause?

I have WHM / Cpanel.

Is there a more specific error you are getting compared to what is showing on the forum?

Check the timout on mysql. If it is too short, it would error out.

Post: #67

(08-31-2013 03:22 PM)Roosh Wrote:  I disabled two tasks that could be causing it "Hourly Cleanup" and "RSS 2 Post") at the times it goes down, but still the same result. It's not obvious that anything from the forum side is causing it at this point.

I looked into the cronjob hourly function, and the only thing I found was modsecparse.pl (Mod Security). I googled the file name and there seem to be problems with it and mysql. I don't think it was enabled before the upgrade. Maybe this is the cause?

I have WHM / Cpanel.

That sounds very possible. I'm finding a lot of posts about similar issues online, poking around it now. Without knowing much about the server config, it will be a lot of guesswork on my part, so bear with me.

Post: #68

(08-31-2013 03:29 PM)worldwidetraveler Wrote:  

(08-31-2013 03:22 PM)Roosh Wrote:  I disabled two tasks that could be causing it "Hourly Cleanup" and "RSS 2 Post") at the times it goes down, but still the same result. It's not obvious that anything from the forum side is causing it at this point.

I looked into the cronjob hourly function, and the only thing I found was modsecparse.pl (Mod Security). I googled the file name and there seem to be problems with it and mysql. I don't think it was enabled before the upgrade. Maybe this is the cause?

I have WHM / Cpanel.

Is there a more specific error you are getting compared to what is showing on the forum?

The MYBB forum closes and just says "MyBB is automatically repairing a crashed table."

I don't know how to view error mysql error logs. I have a feeling this is it, because I remember mod_security was disabled at some point in the past.

Post: #69

(08-31-2013 03:32 PM)Roosh Wrote:  

(08-31-2013 03:29 PM)worldwidetraveler Wrote:  

(08-31-2013 03:22 PM)Roosh Wrote:  I disabled two tasks that could be causing it "Hourly Cleanup" and "RSS 2 Post") at the times it goes down, but still the same result. It's not obvious that anything from the forum side is causing it at this point.

I looked into the cronjob hourly function, and the only thing I found was modsecparse.pl (Mod Security). I googled the file name and there seem to be problems with it and mysql. I don't think it was enabled before the upgrade. Maybe this is the cause?

I have WHM / Cpanel.

Is there a more specific error you are getting compared to what is showing on the forum?

The MYBB forum closes and just says "MyBB is automatically repairing a crashed table."

I don't know how to view error mysql error logs. I have a feeling this is it, because I remember mod_security was disabled at some point in the past.

The mysql errors should be in /var/log/mysql/error.log. Is this problem easily reproducible? For example, if you were to disable mod_security, would you know pretty quickly if the issue was fixed?

Post: #70

There is no error.log in that directly.

I think I would know within an hour of disabling mod_security if it's the problem or not.

Post: #71

(08-31-2013 03:47 PM)Roosh Wrote:  There is no error.log in that directly.

I think I would know within an hour of disabling mod_security if it's the problem or not.

Hell, maybe your server guy turned it on without realizing it was originally disabled.

This is the second time I posted and the forum told me I already posted. It seems like there is a double post going on even though I only posted once.

Post: #72

It's possible. He rebuilt PHP and I see it is now enabled.

Post: #73

I say take a shot and disable it. It doeswell at locking down some common vulnerabilities (at least from what I've read, I've not actually used it though). If it wasn't in use before, you should be okay.

Post: #74

(08-31-2013 03:52 PM)ryanf Wrote:  I say take a shot and disable it. It doeswell at locking down some common vulnerabilities (at least from what I've read, I've not actually used it though). If it wasn't in use before, you should be okay.

Is there a way to disable it without having to rebuild php?

Post: #75

The forum is going to die in 52 minutes and stay that way for several hours. Sorry guys. After that just check back on Sunday afternoon.