SMF Support > SMF 1.1.x Support

Error log table becomes massive (SMF 1.1.16)

<< < (4/4)

MrPhil:
How about the default theme's *.english.php files? Are they damaged or missing those $txt[] entries? SMF should be falling back to the default Theme's language files if none are provided with the theme you're using. You haven't said so, but I'm assuming you're using English language. Are there other languages installed and in use?


--- Quote ---My web host has confirmed that the software they are running is fully compatible with SMF requirements.
--- End quote ---
That means nothing. Of course they'll tell you that everything's fine on their end. Exactly what level of PHP are you running? Have you looked for other error logs ("error_log" files or the like in your SMF directories, and system/server Error Log) to see if there are any other reports of errors that might give a clue?

Did your host update/upgrade anything around the time the problems started? If so, it's possible that they changed an include path or something, but then you should be getting PHP errors indicating that it can't find some files.

A reinstall of 1.1.16 might help, if there's damage to files that you're overlooking. Take the Large Update package and overwrite all your SMF files (except Settings.php and Settings_bak.php). Do you find any files (except for attachments and avatars) that you can't account for (added by a hacker)? You will need to reinstall any mods you were using. 1.1.16 should be compatible with current server software levels, but I won't swear that it's PHP 5.4 compatible. There's probably no advantage at this point in going to SMF 2.0.2, at least until you can figure out what's wrong with the current installation.

irmurray:
Hi again,

The default english.php looks OK, and I'm using English only. There is a main error log, but it contains only 6 errors dating back two years, and they look like temporary file faults.

I was getting prepared to do the re-install, but meantime I had a look at the SQL back end in more detail, and realised that I've been rather silly ...
the forum is using a database called new with tables called smf_*
the errors were occurring in a database called smf with tables called smf_*

I didn't realise that I was in the wrong database due to the similar names - I have now deleted all the tables in the database smf which by definition has cured my problem, and my forum continues to run correctly. I do not know where the smf database came from - the smf_messages table in it was full of marketing rubbish.

So looks like my problem is solved, but I feel a bit of a twit, and am sorry for wasting the time of you folks who have offered your help. I hang my head in shame and put it down to inexperience with the workings of SMF.  :-[ :-[ :-[

Regards,


Iain.

MrPhil:
(slap, slap). That's the sound of your back being flogged with a wet noodle!

Any idea how you ended up in this state? I wonder if you were hacked. Do you have a "free" host that reserves the right to alter your code? (and screwed it up) Or did your host attempt to helpfully fix a problem and messed it up? How did you end up with a whole new database? How did you end up running SMF with the wrong database, if that was in fact the cause? Why aren't you getting lots of errors that the "smf" database is now empty or gone? This all seems very strange. However, if you're running cleanly now, that's 90% of the battle.

irmurray:
Hi again,

Some hacking must have been involved, as the "other" database was full of adware messages and links. My host is commercial.

I previously (years ago) had a PHPBB forum on the site, and the fact that the current SMF one is called "new" suggests that the "smf" database was my first attempt - the databases for these out-of-date forums were still sitting there. I have now deleted all the tables in them and renamed them (I can't see how to actually delete the database).

Nothing new in the main site of forum error logs - as I've deleted the error_log table that was filling up, it's not filling up any more.

Thanks again,


Iain.

Navigation

[0] Message Index

[*] Previous page