1030 - Got error 1 from storage engine

Installatie lukt niet? Plotseling een foutmelding. Of weet je niet hoe iets werkt. Problemen met phpBB2 kun je in dit archief opzoeken.
Forumregels

Sinds 1 januari 2009 wordt phpBB2 niet meer ondersteund.
Onderstaande informatie is verouderd en dient uitsluitend als archief.
phpBB2.0.x
Gesloten
arthurk
Berichten: 12
Lid geworden op: 10 dec 2006, 23:49

1030 - Got error 1 from storage engine

Bericht door arthurk » 08 jan 2007, 13:38

Support Template
  • Appalachia2
    Wat is het probleem? 1030 - Got error 1 from storage engine
    Wanneer ontstond het probleem? Na ddos attack op provider
    Adres van je forum: http://www.zrhaaglanden.nl
    Modifications op je forum: album mod
    Huidige stijl: Appalachia2
    phpBB versie: 2.0.22
    Waar is je forum gehost: http://www.e-craetive.nl
    Heb je onlangs iets verandert aan je forum? nieuwe installatie
Overige opmerkingen:Na ddos attack op provider deze storing in msql dbase, er is geen bewerking meer te doen, ook niet via myadmin, zelfs verwijderen lukt niet.
Nieuwe msql dbase aangemaakt en forum weer werkend gekregen, na 3 dagen weer deze error en dbase weer niets mee te doen.
Kan dit te maken hebben met een hack of is dit probleem te wijten aan de provider?
Kwam ergens op het net een bericht tegen dat er een partitie probleem zou kunnen zijn, echter de error die daarbij hoorde was niet exact hetzelfde als deze error #1030 - Got error 1 from storage engine.
Zoeken op deze error geeft geen resultaat.

Wie helpt mij uit de brand, effe een nieuwe dbase maken is geen probleem maar als het inderdaad een hack van buitenaf is dan moet ik over 3 dagen weer een nieuwe maken enz. enz.

Arthur
Laatst gewijzigd door arthurk op 08 jan 2007, 15:38, 1 keer totaal gewijzigd.

arthurk
Berichten: 12
Lid geworden op: 10 dec 2006, 23:49

1030 error

Bericht door arthurk » 08 jan 2007, 15:26

Heb net de sql runtime gelezen in myadmin, lijkt op een attack (van binnen uit? verkeer 0 per uur), zie ook bij "deze onderstaande waarde!

Code: Selecteer alles

 localhost 
databases
 SQL
 Status
 Variabelen
 Karaktersets
 Engines
 Processen
 Exporteer
 Import
 

Runtime Informatie 
Vernieuw Reset MySQL - Documentatie 
Deze MySQL server draait inmiddels 0 dagen, 2 uren, 48 minuten en 10 seconden. Hij is gestart op 08 Jan 2007 om 12:33. 

Handler Query cache Threads Binaire log Temporary data Delayed inserts Key cache Joins Replication Sorting Tabellen 
Server verkeer: Deze tabellen geven statistieken weer van het verkeer van deze MySQL server vanaf het moment dat hij is gestart
Verkeer  ø per uur 
Ontvangen 55 MB 20 MB 
Verzonden 243 MB 87 MB 
Totaal 298 MB 106 MB 
Connecties ø per uur % 
max. concurrent connections 12  ---  ---  
Mislukte pogingen 9  3,21  0,08% 
Afgehaakte 46  16,41  0,41% 
Totaal 11 k 3.971,06  100,00% 

--------------------------------------------------------------------------------

Query statistieken: Sinds het opstarten zijn er, 392.301 queries gestuurd naar de server.
Totaal ø per uur ø per minuut ø per seconde 
392 k 139,97 k 2,33 k 38,88  

Query type ø per uur % 
admin commands 624  222,64  0,16% 
alter db 0  0,00  0,00% 
alter table 90  32,11  0,02% 
analyze 0  0,00  0,00% 
backup table 0  0,00  0,00% 
begin 40  14,27  0,01% 
change db 13 k 4.479,48  3,29% 
change master 0  0,00  0,00% 
check 0  0,00  0,00% 
checksum 0  0,00  0,00% 
commit 40  14,27  0,01% 
create db 1  0,36  0,00% 
create function 0  0,00  0,00% 
create index 0  0,00  0,00% 
create table 125  44,60  0,03% 
delete 20 k 7.167,53  5,27% 
delete multi 0  0,00  0,00% 
do 0  0,00  0,00% 
drop db 1  0,36  0,00% 
drop function 0  0,00  0,00% 
drop index 0  0,00  0,00% 
drop table 189  67,43  0,05% 
drop user 0  0,00  0,00% 
flush 0  0,00  0,00% 
grant 0  0,00  0,00% 
ha close 0  0,00  0,00% 
ha open 0  0,00  0,00% 
ha read 0  0,00  0,00% 
help 0  0,00  0,00% 
insert 26 k 9.279,37  6,82% 
insert select 92  32,82  0,02% 
kill 0  0,00  0,00% 
load 0  0,00  0,00% 
load master data 0  0,00  0,00% 
load master table 0  0,00  0,00% 
lock tables 47  16,77  0,01% 
optimize 0  0,00  0,00% 
preload keys 0  0,00  0,00% 
purge 0  0,00  0,00% 
purge before date 0  0,00  0,00% 
rename table 0  0,00  0,00% 
repair 0  0,00  0,00% 
replace 49  17,48  0,01% 
replace select 0  0,00  0,00% 
reset 0  0,00  0,00% 
Query type ø per uur % 
restore table 0  0,00  0,00% 
revoke 0  0,00  0,00% 
revoke all 0  0,00  0,00% 
rollback 0  0,00  0,00% 
savepoint 0  0,00  0,00% 
select 51 k 18,33 k 13,48% 
set option 746  266,16  0,20% 
show binlog events 0  0,00  0,00% 
show binlogs 12  4,28  0,00% 
show charsets 55  19,62  0,01% 
show collations 377  134,51  0,10% 
show column types 0  0,00  0,00% 
show create db 1  0,36  0,00% 
show create table 14  5,00  0,00% 
show databases 13  4,64  0,00% 
show errors 0  0,00  0,00% 
show fields 33  11,77  0,01% 
show grants 19  6,78  0,00% 
show innodb status 0  0,00  0,00% 
show keys 12  4,28  0,00% 
show logs 0  0,00  0,00% 
show master status 0  0,00  0,00% 
show ndb status 0  0,00  0,00% 
show new master 0  0,00  0,00% 
show open tables 0  0,00  0,00% 
show privileges 0  0,00  0,00% 
show processlist 0  0,00  0,00% 
show slave hosts 0  0,00  0,00% 
show slave status 0  0,00  0,00% 
show status 1  0,36  0,00% 
show storage engines 1  0,36  0,00% 
show tables 183  65,29  0,05% 
show variables 445  158,77  0,12% 
show warnings 0  0,00  0,00% 
slave start 0  0,00  0,00% 
slave stop 0  0,00  0,00% 
stmt close 0  0,00  0,00% 
stmt execute 0  0,00  0,00% 
stmt prepare 0  0,00  0,00% 
stmt reset 0  0,00  0,00% 
stmt send long data 0  0,00  0,00% 
truncate 0  0,00  0,00% 
unlock tables 47  16,77  0,01% 
update 21 k 7.550,72  5,55% 
update multi 2  0,71  0,00% 
Begin   Variabelen Waarde Beschrijving 
Flush_commands 1  The number of executed FLUSH statements.  
Slow_queries 21  The number of queries that have taken more than long_query_time seconds. MySQL - Documentatie  
Begin  Handler  Variabelen Waarde Beschrijving 
Handler_commit 58  The number of internal COMMIT statements.  
Handler_delete 24 k The number of times a row was deleted from a table.  
Handler_discover 0  The MySQL server can ask the NDB Cluster storage engine if it knows about a table with a given name. This is called discovery. Handler_discover indicates the number of time tables have been discovered.  
Handler_read_first 8.258  The number of times the first entry was read from an index. If this is high, it suggests that the server is doing a lot of full index scans; for example, SELECT col1 FROM foo, assuming that col1 is indexed.  


***************************************
DEZE ONDERSTAANDE WAARDE???

Handler_read_key 14 M The number of requests to read a row based on a key. If this is high, it is a good indication that your queries and tables are properly indexed.  
Handler_read_next 68 M The number of requests to read the next row in key order. This is incremented if you are querying an index column with a range constraint or if you are doing an index scan.  


Handler_read_prev 15 k The number of requests to read the previous row in key order. This read method is mainly used to optimize ORDER BY ... DESC.  
Handler_read_rnd 381 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 151 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.  
Handler_rollback 1.033  The number of internal ROLLBACK statements.  
Handler_update 248 k The number of requests to update a row in a table.  


Handler_write 26 M The number of requests to insert a row in a table.  
Begin  Query cache  Variabelen Waarde Beschrijving 
Flush query cache MySQL - Documentatie  
Qcache_free_blocks 166  The number of free memory blocks in query cache.  
Qcache_free_memory 37 M The amount of free memory for query cache.  

***********************************************************

Qcache_hits 247 k The number of cache hits.  
Qcache_inserts 48 k The number of queries added to the cache.  
Qcache_lowmem_prunes 0  The number of queries that have been removed from the cache to free up memory for caching new queries. This information can help you tune the query cache size. The query cache uses a least recently used (LRU) strategy to decide which queries to remove from the cache.  
Qcache_not_cached 3.111  The number of non-cached queries (not cachable, or not cached due to the query_cache_type setting).  
Qcache_queries_in_cache 23 k The number of queries registered in the cache.  
Qcache_total_blocks 47 k The total number of blocks in the query cache.  
Begin  Threads  Variabelen Waarde Beschrijving 
Laat processen zien MySQL - Documentatie  
Slow_launch_threads 0  The number of threads that have taken more than slow_launch_time seconds to create.  
Threads_cached 8  The number of threads in the thread cache. The cache hit rate can be calculated as Threads_created/Connections. If this value is red you should raise your thread_cache_size.  
Threads_connected 4  The number of currently open connections.  
Threads_created 12  The number of threads created to handle connections. If Threads_created is big, you may want to increase the thread_cache_size value. (Normally this doesn't give a notable performance improvement if you have a good thread implementation.)  
Threads_running 1  The number of threads that are not sleeping.  
Threads_cache_hitrate_% 99,89 %  
Begin  Binaire log  Variabelen Waarde Beschrijving 
MySQL - Documentatie  
Binlog_cache_disk_use 0  The number of transactions that used the temporary binary log cache but that exceeded the value of binlog_cache_size and used a temporary file to store statements from the transaction.  
Binlog_cache_use 0  The number of transactions that used the temporary binary log cache.  
Begin  Temporary data  Variabelen Waarde Beschrijving 
Created_tmp_disk_tables 426  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.  
Created_tmp_files 2.153  How many temporary files mysqld has created.  
Created_tmp_tables 4.572  The number of in-memory temporary tables created automatically by the server while executing statements.  
Begin  Delayed inserts  Variabelen Waarde Beschrijving 
Delayed_errors 0  The number of rows written with INSERT DELAYED for which some error occurred (probably duplicate key).  
Delayed_insert_threads 0  The number of INSERT DELAYED handler threads in use. Every different table on which one uses INSERT DELAYED gets its own thread.  
Delayed_writes 0  The number of INSERT DELAYED rows written.  
Not_flushed_delayed_rows 0  The number of rows waiting to be written in INSERT DELAY queues.  
Begin  Key cache  Variabelen Waarde Beschrijving 
MySQL - Documentatie  
Key_blocks_not_flushed 0  The number of key blocks in the key cache that have changed but haven't yet been flushed to disk. It used to be known as Not_flushed_key_blocks.  
Key_blocks_unused 84 k The number of unused blocks in the key cache. You can use this value to determine how much of the key cache is in use.  
Key_blocks_used 2.162  The number of used blocks in the key cache. This value is a high-water mark that indicates the maximum number of blocks that have ever been in use at one time.  
Key_read_requests 40 M The number of requests to read a key block from the cache.  
Key_reads 14 k The number of physical reads of a key block from disk. If Key_reads is big, then your key_buffer_size value is probably too small. The cache miss rate can be calculated as Key_reads/Key_read_requests.  
Key_write_requests 80 k The number of requests to write a key block to the cache.  
Key_writes 43 k The number of physical writes of a key block to disk.  
Key_buffer_fraction_% 14,11 %  
Begin  Joins  Variabelen Waarde Beschrijving 
Select_full_join 605  The number of joins that do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.  
Select_full_range_join 3  The number of joins that used a range search on a reference table.  
Select_range 3.323  The number of joins that used ranges on the first table. (It's normally not critical even if this is big.)  
Select_range_check 4  The number of joins without keys that check for key usage after each row. (If this is not 0, you should carefully check the indexes of your tables.)  
Select_scan 14 k The number of joins that did a full scan of the first table.  
Begin  Replication  Variabelen Waarde Beschrijving 
Show slave hosts Show slave status MySQL - Documentatie  
Rpl_status NULL The status of failsafe replication (not yet implemented).  
Slave_open_temp_tables 0  The number of temporary tables currently open by the slave SQL thread.  
Slave_retried_transactions 0  Total (since startup) number of times the replication slave SQL thread has retried transactions.  
Slave_running OFF This is ON if this server is a slave that is connected to a master.  
Begin  Sorting  Variabelen Waarde Beschrijving 
Sort_merge_passes 1.111  The number of merge passes the sort algorithm has had to do. If this value is large, you should consider increasing the value of the sort_buffer_size system variable.  
Sort_range 6.524  The number of sorts that were done with ranges.  
Sort_rows 708 k The number of sorted rows.  
Sort_scan 5.330  The number of sorts that were done by scanning the table.  
Begin  Tabellen  Variabelen Waarde Beschrijving 
Flush (close) all tables Show open tables  
Open_tables 264  The number of tables that are open.  
Opened_tables 3.237  The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.  
Table_locks_immediate 144 k The number of times that a table lock was acquired immediately.  
Table_locks_waited 20  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.  
Begin   Variabelen Waarde Beschrijving 
Open_files 480  The number of files that are open.  
Open_streams 0  The number of streams that are open (used mainly for logging).  

 

Gesloten