Major Error In SMF 2.0.1

Started by ArticleProductions, October 26, 2011, 09:36:22 AM

Previous topic - Next topic

ArticleProductions

 Just checked my server and noticed a error log file that is 14.7MB and the forum is not that old. I am getting 2 errors.

1. PHP Warning:  mysql_real_escape_string() expects parameter 2 to be resource,
boolean given in /home/XXXXXXXX/public_html/Sources/Subs-Db-mysql.php on line 132


2. [21-Oct-2011 19:06:52] PHP Notice:  Undefined index: utf8 in
/home/XXXXXXX/public_html/Sources/Subs-Post.php on line 369

The line number on the 2 error keeps changing.

Any idea how to fix these ? The error log file at 14.7mb is a little unreal especially since the forum was installed on 10/13


ArticleProductions

Any help ? Error log file is now 44MB

Shambles

Re: error #1

There was some discussion of this earlier this year (in this longish thread)

Have a read and see if it relates in some way ..


luuuciano

Wich hosting company are you using? hostgator? shared?
No me agradan los foros que no te dejan borrar TU PROPIO usuario, como por ejemplo smfsimple.com.
E incluso te mandan emails no solicitados, de los cuales, quizá, no puedas escapar porque NO te dejan posibilidad a deshabilitarlos (a menos que NO te tengan en su lista negra).

ArticleProductions

I do not use hostgator was with them for 7 years and paid over $20,000 until they screwed me over.

I have a dedicated server, not vps or shared but dedicated.

luuuciano

Quote from: Spuds on October 27, 2011, 07:40:34 PM
The patch that is in the other thread will stop the creation of the large error log .... thats your best bet ATM

Wich is the right code to use in that thread? (as  there are many, mixed, etc...)
It would work on 2.0.1?

Why smf devs do not add it to core files? :( :-/
No me agradan los foros que no te dejan borrar TU PROPIO usuario, como por ejemplo smfsimple.com.
E incluso te mandan emails no solicitados, de los cuales, quizá, no puedas escapar porque NO te dejan posibilidad a deshabilitarlos (a menos que NO te tengan en su lista negra).

Illori

Quote from: luuuciano on November 03, 2011, 10:29:22 AM
Why smf devs do not add it to core files? :( :-/

2.0 is feature locked and not everyone faces this issue so it may not be in the best interest to fix this in the core.

Maxtor

ive got 600mb logs of this error . :/

searchgr

So, what is the solution for this problem? Any official update?

luuuciano

There is no problem, just bad luck.

oh, and smf trying to log something to a db down... is a feature (?)
No me agradan los foros que no te dejan borrar TU PROPIO usuario, como por ejemplo smfsimple.com.
E incluso te mandan emails no solicitados, de los cuales, quizá, no puedas escapar porque NO te dejan posibilidad a deshabilitarlos (a menos que NO te tengan en su lista negra).

searchgr

The problem is that the error log file is getting bigger and bigger.

I tried the following but i don't know what is doing.

Quote from: Spuds on November 03, 2011, 02:15:25 PM
Subs-Db-mysql.php

Code (find) Select
list ($values, $connection) = $db_callback;

Code (add after) Select
if (!is_resource($connection))
    db_fatal_error();


Advertisement: