PDA

View Full Version : Server Errors


RichieBoy67
08-22-2017, 07:51 PM
Hey,

Today one of my sites has had much more traffic than usual and I have had a couple crashes. I believe one was caused by redis caching with dbtech vboptimizer. I do not believe the issue is dbtech but rather redis service. I'm sorry but I do not have the log entry for that one as the outage was for only 2 minutes.

If anyone is familiar with redis let me know please. I installed it but I do not believe it is configured correctly. When ever we get a ton of traffic I have issues.

The other issue is current. I see this in the server log.

GET /clientscript/vbulletin_css/style00039l/forumbits.css,forumhome.css,widgets.css,sidebar.cs s,options.css,tagcloud.css

It is a 408 error.

I have turned off style theme file caching and tagging for the moment. I have many of these errors.

I know this forum is dead now but I could use some insight.

Thanks

snakes1100
08-26-2017, 11:35 AM
As we cant see your server setup or the config of redis, really hard to say with out you posting the details of redis & what you've done so far.

Run redis on numerous servers, everything from vb to wp.

RichieBoy67
08-26-2017, 12:57 PM
Can you give me any tips on running it? I only have issues under high traffic situations.

Server is the latest Centos..

Thanks

snakes1100
08-26-2017, 01:10 PM
There is really no tips, its a basic config file for setup, other than tweaking those settings, there is nothing special for "tips".

What errors did you get if any before the crash or have you checked logs?

RichieBoy67
09-09-2017, 01:46 PM
How about this?

Database error in vBulletin 4.2.5 Beta 4:

Invalid SQL:

SELECT *
FROM style
WHERE (styleid = 55)
OR styleid = 39
ORDER BY styleid DESC
LIMIT 1;

MySQL Error : MySQL server has gone away
Error Number : 2006
Request Date : Saturday, September 9th 2017 @ 04:09:57 AM
Error Date : Saturday, September 9th 2017 @ 04:11:10 AM
Script :/showthread.php?t=236920&page=19
Referrer : /showthread.php?t=236920&page=17
IP Address : ##########
Username : Unregistered
Classname : vB_Database_MySQLi
MySQL Version :
Server : ############
User Agent :

Stack Trace:

#0 vB_Database->halt() called in [path]/includes/class_core.php on line 1403
#1 vB_Database_MySQLi->execute_query() called in [path]/includes/class_core.php on line 505
#2 vB_Database->query_first() called in [path]/includes/class_core.php on line 536
#3 vB_Database->query_first_slave() called in [path]/includes/class_bootstrap.php on line 1008
#4 vB_Bootstrap->fetch_style_record() called in [path]/includes/class_bootstrap.php on line 201
#5 vB_Bootstrap->load_style() called in [path]/global.php on line 31
#6 require_once([path]/global.php) called in [path]/showthread.php on line 107

blind-eddie
09-09-2017, 02:59 PM
Hey Richie, The database server crashed, as your host why it is crashing. I used to get it alot.

RichieBoy67
09-09-2017, 07:06 PM
I have a dedicated server.

I believe it is this error causing the issue and it doesn't seem like a crash because the database is not actually going down.

Thanks bro

blind-eddie
09-10-2017, 12:12 AM
MySQL Error : MySQL server has gone away is a hiccup on the SQL server.
Dedicated servers host their own SQL also?

snakes1100
09-10-2017, 04:16 PM
server going away can be caused by a few things including sql's own settings, i doubt that is redis causing the issue, but wont be able to do much from the outside looking in.

did you raise ur timeouts in my.cnf or do a live view of sql & watch the queries?

CAG CheechDogg
09-10-2017, 11:27 PM
I used to get something similar to that and it was due to bots crawling my site and people doing to many searches at once ... it was a bunch of kids flooding my site ... had to block their ips and even ip ranges ...

RichieBoy67
09-12-2017, 04:43 PM
Ok Guys, thanks..

I know about the database going away and various things can cause it such as resource overload, time out, etc..

In this case though the errors I get are always basically the same:

Invalid SQL:

SELECT *
FROM style
WHERE (styleid = 39 AND userselect = 1)
OR styleid = 39
ORDER BY styleid ASC
LIMIT 1;

I believe there is something causing the issue that is making the database server go away related to this query. In other words, I do not believe it is the database going away that is causing this error. Hope this makes sense. lol

It only happens a couple times a day usually and I have tried to rearrange some cron tasks, back ups to make sure it is not a resource situation. It could be but I am not seeing any indication.

--------------- Added 1505241836 at 1505241836 ---------------

server going away can be caused by a few things including sql's own settings, i doubt that is redis causing the issue, but wont be able to do much from the outside looking in.

did you raise ur timeouts in my.cnf or do a live view of sql & watch the queries?

No, this is not related to the redis issue I was posting about before. I have stopped using dbtech optimizer and am no longer using redis.