First and most importantly
Very Best wishes, good health and prosperity to all at phpBB for 2011 !!
Tabitha, the server password issue is now fixed. It took some time and I've had a huge amount of work to do lately.
I have opened phpMyAdmin and this is what I found:
phpMyAdmin version: 188.8.131.52
MySQL client version: 4.0.21
used PHP extensions: mysql
Server 1 (my server)
server version: 5.0.77
Protocol version: 10
Server: Server 1 (Localhost via UNIX socket)
MySQL charset: UTF-8 Unicode
MySQL connection: utf8_unicode_ci
All that seems OK
However, my server is still at the point of crashing. Daily warnings: "the following partitions are nearly full: ./-95%"
I can not access the phpBB administration. This is the message:
Code: Select all
SQL ERROR [ mysql4 ]
Table './oxanabab_new/phpbb_log' is marked as crashed and should be repaired 
INSERT INTO phpbb_log (user_id, log_ip, log_time, log_operation, log_data, log_type) VALUES (2, '184.108.40.206', 1293884460, 'LOG_ADMIN_AUTH_SUCCESS', '', 0)
So I've checked the databases. There are 6:
- information schema (17)
- mysql (17)
. _forum (57)
. _new (62)
. _phpbbthree (63)
- oxanababy_ru_-_phpbb (58)
Am I right in thinking there are at least 3 too many databases?
Next I checked the red
tagged values, looking for anything that may be far too large. Here is some of what I found (I'll send a full report if needed):
The number of logical reads that InnoDB could not satisfy from buffer pool and had to do a single-page read.
Handler_read_rnd 535 k
The number of requests to read a row based on a fixed position. This is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly.
Handler_read_rnd_next 45 M !!!
The number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have
The number of temporary tables on disk created automatically by the server while executing statements. If Created_tmp_disk_tables is big, you may want to increase the tmp_table_size value to cause temporary tables to be memory-based instead of disk-based.
The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.
The number of times that a table lock could not be acquired immediately and a wait was needed. If this is high, and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.
So there does indeed seem to be a problem with databases / tables.
Back to your previous advice.... to repair phpbb_log table.
How can I make a database backup with no access to the forum admin?
Where can I find the REPAIR TABLE php_log ?
Can I get rid of unused databases (maybe after saving in case ever needed again)?
Any help will be most appreciated. Please bear in mind that I do not know much about running servers, so if possible explain things as fully and clearly as possible. Many thanks in advance!!!