An unexpected database error occurred please try again later xenforo

XF 1.2 An unexpected database error occurred. Please try again later

Qaseem

Member

Hello
Having a problem, an error message while browsing Forum
(An unexpected database error occurred. Please try again later.)

Note: The Forum is working on a program previously vbulletin
Then been Conversion / Jump to xenforo a recently
This problem were not present when the forum was runs the Fbolten software

Please help
Thanks in advance

Attachments

Brogan

XenForo moderator

View the page source, there may be more details.

Errors such as this are usually related to incorrect database or config.php details.

Qaseem

Member

View the page source, there may be more details.

Errors such as this are usually related to incorrect database or config.php details.

Dear @Brogan
Sorry for the delay, I was waiting for the emergence of the problem again so I can answer your question
Prefer:

Brogan

XenForo moderator

You have exceeded the limit imposed by your host.

You will need to change your hosting account or move to another host.

Qaseem

Member

You have exceeded the limit imposed by your host.

You will need to change your hosting account or move to another host.

Jeremy

in memoriam 1991-2020

Tracy Perry

Well-known member

Dear @Brogan
Sorry for the delay, I was waiting for the emergence of the problem again so I can answer your question
Prefer:

Qaseem

Member

@Brogan @King Kovifor @Tracy Perry
Thank you very much for your follow-up

There are those who differ with you to solve the problem
For more advice, I emailed the hosting company, and offered them the problem
Has answered employee Linux Systems Administration (ATX)
This is his answer:

After reviewing your forum’s database and queries, I’ve noticed that your queries do get delayed do to the number of rows in your forum, you may be able to optimize your database by creating indexes for your MySQL tables that contain thousands of rows:

=======================================================
+—————————————+———-+————+
+—————————————+———-+————+
160 rows in set.
Database: ***** _XenForo | Tables | Columns | Total Rows |
| xf_conversation_master | 15 | 26658 |
| xf_conversation_message | 8 | 26830 |
| xf_template_phrase | 2 | 35975 |
| xf_thread_watch | 3 | 36428 |
| xf_conversation_user | 9 | 37884 |
| xf_conversation_recipient | 4 | 57836 |
| xf_user_field_value | 3 | 66749 |
| xf_thread | 19 | 80424 |
| xf_post | 17 | 1052490 |
| xf_search_index | 8 | 1090140 |
| xf_import_log | 3 | 1199527 |
=======================================================

Also, I’d recommend optimizing your tables as well. I’ve also reconfigured your my.cnf to run more efficiently on your dedicated server and made a backup of your previous configuration file to /etc/my.cnf.2013-08-18.bak

Also, mailman was using 25% of your server’s ram and I restarted the service to alleviate the stale process.

Источник

XF 1.3 An unexpected database error occurred. Please try again later.

XBones

Member

Yesterday my site went down and all it says is «An unexpected database error occurred. Please try again later».

I have done nothing to the site except install 1.3 a few weeks ago and the site has been running perfectly since then until yesterday morning. I contacted my host and they said the server was running fine. So finally they restored the database back one day and finally the site came back.

Now this morning after posting the same error is back.

I am not a technical person and have absolutely no idea how to trouble shoot this. Host says all PHP is up-to-date so I am at a complete loss. I have searched to see if others have experienced this error and while they have there doesn’t seem to be anything specific that I am able to do since like I said I am not technically inclined and don’t understand all the inter workings of the software and PHP.

Can somebody point me in the right direction? In fact if there is a Webmaster reading this that can help on a paid basis please let me know.

Brogan

XenForo moderator

Here’s your problem:

You should contact your host to determine why the table is missing.

Tables don’t disappear on their own so you will need to investigate whether it’s an add-on, malicious activity, or server/host related.

XBones

Member

I saw that error yesterday but the host always seems to point back to us. So restoring the database back to Tuesday corrected the problem temporarily which to me means something has probably has been done maliciously to remove that table. How would the hosting company be responsible for the table being removed? Like I said I am a complete neophyte regarding these sorts of issues and can’t really discuss the ins and outs with the technical people.

Like I mentioned, there are no add-ons installed. It’s a stock install. What possible server/host related things could cause this kind of porblem?

Brogan

XenForo moderator

If there are no add-ons installed then the next thing is to check the server logs and see who accessed the server, etc.

Your host should be able to help with that.

XBones

Member

XBones

Member

@Brogan Well I talked to the hosting company and of course they claim nothing is wrong on their end. Clearly I didn’t remove any table since I wouldn’t even know how.

They did restore the DB yesterday back to Tuesday and the site came back but as soon as people started posting messages this morning the same error came up and the site has been down ever since.

So I am assuming at this point that the site (DB) was hacked and somebody somehow put some malicious code in the DB that is deleting the table. I had a similar experience before where somebody placed some code in the DB that was causing redirects. I hired a security company to find and remove the code which they did successfully and the site has been running fine since November until now. So would you agree that the hosting company’s security isn’t what they claim?

Is there a way for me to put this table back in? Sorry for the stupid questions but I have no idea how that would be accomplished. This is why if there is a webmaster I can contact to help me fix this I would appreciate a name or referral.

I’d like to get it fixed and then move the site to a new hosting company. There is no sense moving it right now because the issue will just move to the new host. Or, so it seems.

Anybody else who would like to point me in the direction of a solution pleawe feel free to chime in.

Источник

Unexpected Database Errors

ting.mike

Member

So after a few months of smooth sailing with XenForo, this few days I’ve seen the forum went down a few times with the error message » An unexpected database error occurred. Please try again later.»

I would reboot the server and it would go back up, only to have the same problem reoccurring after a few hours. Also during this period when the forum is online, sometimes trying to open certain threads return the same » An unexpected database error occurred. Please try again later.»

Any clue what to look for?

Jake Bunce

Well-known member

ting.mike

Member

MattW

Well-known member

That is telling you that the partition which is holding your MySQL install is full, hence MySQL isn’t starting (why you can’t access your ACP).

When you log into the server, what is the output of

ting.mike

Member

Looks like I’m out of hard disk space?

MattW

Well-known member

ting.mike

Member

MattW

Well-known member

ting.mike

Member

ting.mike

Member

Here is the error this time:

That’s weird because mysqld.pid apparently exists!

MattW

Well-known member

ting.mike

Member

THanks, Matt.
This is the error I got:

MattW

Well-known member

Do you have an error log configured? Should be something in your my.cnf file like so:

If you do, what is being written to the error log when trying to start MySQL?

ting.mike

Member

Do you have an error log configured? Should be something in your my.cnf file like so:

If you do, what is being written to the error log when trying to start MySQL?

I have just tried enabling the error log using this guide (below). Afterwards, trying to restart mysql yield another failed. I opened the log on /var/log/mysql.log and found only a blank file. I also noticed that while monitoring the folder /var/run/mysqld/ folder, the file mysqld.pid file would come and go with no apparent reason.

To debug applications which use a mysql database, it comes in handy to enable the query log to get all SQL queries that were sent to the database. Open the MySQL configuration file (my.cnf)
vi /etc/mysql/my.cnf
and add the line:
log=/var/log/mysql.log
in the [mysql] section of the file. Depending on the Linux distribution that you use, the my.cnf file can be /etc/my.cnf or /etc/mysql/my.cnf.
Afterwards restart mysql to apply the new the configuration:
/etc/init.d/mysql restart

ting.mike

Member

Just got this error message when I tried starting mysql again:

root@www:/var/log# /etc/init.d/mysql start
Starting MySQL database server: mysqld . . . . . . . . . . . . . ..
Checking for corrupt, not cleanly closed and upgrade needing tables..
root@www:/var/log# ERROR 2013 (HY000): Lost connection to MySQL server at ‘reading initial communication packet’, system error: 0

Still nothing on the mysql.log file

Jake Bunce

Well-known member

I searched Google and found a few posts blaming the hosts file:

ting.mike

Member

Finally got some error logs on var/log/mysql/mysql.log:

Tried to restarted it again and got the same error message (three times):

/usr/sbin/mysqld, Version: 5.1.63-0+squeeze1-log ((Debian)). started with:
Tcp port: 3306 Unix socket: /var/run/mysqld/mysqld.sock
Time Id Command Argument
/usr/sbin/mysqld, Version: 5.1.63-0+squeeze1-log ((Debian)). started with:
Tcp port: 3306 Unix socket: /var/run/mysqld/mysqld.sock
Time Id Command Argument
/usr/sbin/mysqld, Version: 5.1.63-0+squeeze1-log ((Debian)). started with:
Tcp port: 3306 Unix socket: /var/run/mysqld/mysqld.sock
Time Id Command Argument

ting.mike

Member

I searched Google and found a few posts blaming the hosts file:

ting.mike

Member

ting.mike

Member

More errors upon calling the command mysqld:

# mysqld
121225 10:14:31 [Note] Failed to execute my_stat on file ‘/var/log/mysql/mysql-bin.000001’
121225 10:14:31 [Note] Plugin ‘FEDERATED’ is disabled.
121225 10:14:31 InnoDB: Initializing buffer pool, size = 8.0M
121225 10:14:31 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
121225 10:14:31 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files.
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer.
121225 10:14:31 InnoDB: ERROR: We were only able to scan the log up to
InnoDB: 0 620322816, but a checkpoint was at 0 620322958.
InnoDB: It is possible that the database is now corrupt!
121225 10:14:31 InnoDB: Error: page 2837 log sequence number 0 620379562
InnoDB: is in the future! Current system log sequence number 0 620322958.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
121225 10:14:31 InnoDB: Error: page 446720 log sequence number 0 620379870
InnoDB: is in the future! Current system log sequence number 0 620322958.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 0 3519744
121225 10:14:31 InnoDB: Error: page 0 log sequence number 0 620416774
InnoDB: is in the future! Current system log sequence number 0 620322958.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: Starting in background the rollback of uncommitted transactions
121225 10:14:31 InnoDB: Rolling back trx with id 0 3519312, 1 rows to undo
121225 10:14:31 InnoDB: Started; log sequence number 0 620322958

InnoDB: Rolling back of trx id 0 3519312 completed
121225 10:14:31 InnoDB: Rolling back trx with id 0 3519272, 0 rows to undo
121225 10:14:31 InnoDB: Error: page 390555 log sequence number 0 620379942
InnoDB: is in the future! Current system log sequence number 0 620323144.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
121225 10:14:31 InnoDB: Error: page 342 log sequence number 0 620416774
InnoDB: is in the future! Current system log sequence number 0 620323144.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
121225 10:14:31 InnoDB: Error: page 442368 log sequence number 0 620683394
InnoDB: is in the future! Current system log sequence number 0 620323144.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: Dump of the tablespace extent descriptor: len 40; hex 00000000000018cd0006c0000bb60006c0000b1600000001ffffffffffffffffffffffffffffffff; asc ;
InnoDB: Serious error! InnoDB is trying to free page 446720
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
121225 10:14:31 InnoDB: Assertion failure in thread 140460301485824 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3034
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
10:14:31 UTC — mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346521 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.

Источник