Auf jedem Fall möchte ich jedem danken fürs Mitdenken und für alle Tipps. Ich hoffe das ich in kürze den Fehler finden werde.
Beiträge von klausdieter
-
-
hallo Ralf,
habe snitch installiert. Wie kan ich sehen welche Abfragen nicht OK sind? wonach muss ich suchen?
gr
klaus -
Hille, wie meinst du von 6 auf 7?
habe Debian 3.2.46-1 (schon einige Zeit, mache wohl so viel wie moeglich sicherheits usw updates) -
PHP Fatal error: Maximum execution time of 120 seconds
Holst du irgendwelche Inhalte über eine Socket-Verbindung? erhöhe einfach die ausführbare Zeit? Kann ja möglich sein, dass du SEO-Optimierung oder Tag-Wolken so erweiterst.[/QUOTE]Hallo r23,
das ist meine conf im Moment. Ich bekomme den error ja auch schon wen ich nur einen text auf de Seite verändere!
aber eben erst seit dem ich online bin.- Operating System Linux
- Server Apache/2.2.22 (Debian)
- Memory usage 29.15 MByte
- MYSQL Version 5.5.34-MariaDB-1~wheezy-log
- SQL Mode Not set
- PHP Version 5.4.4-14+deb7u7
- PHP Safe Mode Off
- PHP Allow URL fopen On
- PHP Memory Limit 256M
- PHP Max Upload Size 2M
- PHP Max Post Size 8M
- PHP Max Script Execute Time 30
- PHP Exif support Yes ( V1.4 )
- PHP IPTC support Yes
- PHP XML support Yes
- Site URL http://www.sdtours.net
- Home URL http://www.sdtours.net
- WordPress Version 3.7.1
- WordPress DB Version 25824
- Multisite No
- Active Theme Unite 2.2.1
Active Plugins- Akismet 2.5.9
- All In One SEO Pack 2.1
- Fast Secure Contact Form 4.0.18
- Google Analyticator 6.4.5
- Google XML Sitemaps 3.4
- Hupso Share Buttons for Twitter, Facebook & Google+ 3.9.23
- NextGEN Gallery 1.9.13
- qTranslate 2.5.38
- UpdraftPlus - Backup/Restore 1.8.2
- WordPress Importer 0.6.1
-
Sieht alles gut aus. Welche Apache Module hast du geladen?
Apache2.2.22-13
-
Hallo Hille, hier nochmal die Ausgaben:
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -
MySQL Version 5.5.34-MariaDB-1~wheezy-log x86_64
Uptime = 1 days 5 hrs 53 min 36 sec
Avg. qps = 9
Total Questions = 989271
Threads Connected = 2
Warning: Server has not been running for at least 48hrs.
It may not be safe to use these recommendations
To find out more information on how each of these
runtime variables effects performance visit:
http://dev.mysql.com/doc/refman/5.5…-variables.html
Visit http://www.mysql.com/products/enterprise/advisors.html
for info about MySQL's Enterprise Monitoring and Advisory Service
SLOW QUERIES
The slow query log is NOT enabled.
Current long_query_time = 10.000000 sec.
You have 6 out of 989449 that take longer than 10.000000 sec. to complete
Your long_query_time seems to be fine
BINARY UPDATE LOG
The binary update log is enabled
Binlog sync is not enabled, you could loose binlog records during a server crash
WORKER THREADS
Current thread_cache_size = 128
Current threads_cached = 0
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine
MAX CONNECTIONS
Current max_connections = 120
Current threads_connected = 2
Historic max_used_connections = 10
The number of used connections is 8% of the configured maximum.
You are using less than 10% of your configured max_connections.
Lowering max_connections could help to avoid an over-allocation of memory
See "MEMORY USAGE" section to make sure you are not over-allocating
INNODB STATUS
Current InnoDB index space = 256 K
Current InnoDB data space = 2 M
Current InnoDB buffer pool free = 96 %
Current innodb_buffer_pool_size = 256 M
Depending on how much space your innodb indexes take up it may be safe
to increase this value to up to 2 / 3 of total system memory
MEMORY USAGE
Max Memory Ever Allocated : 880 M
Configured Max Per-thread Buffers : 2.62 G
Configured Max Global Buffers : 656 M
Configured Max Memory Limit : 3.27 G
Physical Memory : 3.83 G
Max memory limit seem to be within acceptable norms
KEY BUFFER
Current MyISAM index space = 7 M
Current key_buffer_size = 128 M
Key cache miss rate is 1 : 9499
Key buffer free ratio = 81 %
Your key_buffer_size seems to be fine
QUERY CACHE
Query cache is enabled
Current query_cache_size = 256 M
Current query_cache_used = 1 M
Current query_cache_limit = 256 K
Current Query cache Memory fill ratio = .51 %
Current query_cache_min_res_unit = 4 K
Your query_cache_size seems to be too high.
Perhaps you can use these resources elsewhere
MySQL won't cache query results that are larger than query_cache_limit in size
SORT OPERATIONS
Current sort_buffer_size = 16 M
Current read_rnd_buffer_size = 2 M
Sort buffer seems to be fine
>> MySQLTuner 1.1.1 - Major Hayden <major@mhtx.net>
>> Bug reports, feature requests, and downloads at http://mysqltuner.com/
>> Run with '--help' for additional options and output filtering
-------- General Statistics --------------------------------------------------
[--] Skipped version check for MySQLTuner script
[OK] Currently running supported MySQL version 5.5.34-MariaDB-1~wheezy-log
[OK] Operating on 64-bit architecture
-------- Storage Engine Statistics -------------------------------------------
[--] Status: +Archive -BDB +Federated +InnoDB -ISAM -NDBCluster
[--] Data in MyISAM tables: 90M (Tables: 85)
[--] Data in InnoDB tables: 2M (Tables: 19)
[--] Data in PERFORMANCE_SCHEMA tables: 0B (Tables: 17)
[!!] Total fragmented tables: 25
-------- Security Recommendations -------------------------------------------
[OK] All database users have passwords assigned
-------- Performance Metrics -------------------------------------------------
[--] Up for: 1d 5h 56m 31s (1M q [10.322 qps], 3K conn, TX: 1B, RX: 1B)
[--] Reads / Writes: 3% / 97%
[--] Total buffers: 688.0M global + 22.4M per thread (120 max threads)
[OK] Maximum possible memory usage: 3.3G (85% of installed RAM)
[OK] Slow queries: 0% (8/1M)
[OK] Highest usage of available connections: 8% (10/120)
[OK] Key buffer size / total MyISAM indexes: 128.0M/7.4M
[OK] Key buffer hit rate: 100.0% (2M cached / 206 reads)
[OK] Query cache efficiency: 44.2% (31K cached / 72K selects)
[OK] Query cache prunes per day: 0
[OK] Sorts requiring temporary tables: 0% (0 temp sorts / 1K sorts)
[OK] Temporary tables created on disk: 19% (620 on disk / 3K total)
[OK] Thread cache hit rate: 60% (1K created / 3K connections)
[OK] Table cache hit rate: 69% (271 open / 390 opened)
[OK] Open file limit used: 32% (330/1K)
[OK] Table locks acquired immediately: 99% (1M immediate / 1M locks)
[OK] InnoDB data size / buffer pool: 2.8M/256.0M
-------- Recommendations -----------------------------------------------------
General recommendations:
Run OPTIMIZE TABLE to defragment tables for better performance
Enable the slow query log to troubleshoot bad queriesDanke schonmal.
-
komt in Ordnung! habe es leider zu zu spät gesehen das der server wenigstens 24 stunden uptime haben muss.
Poste die Ausgaben noch mal in 24h, sonst bringt das gar nichts. Du darfst vor der Ausgabe deinen MySQL-Server nicht neu starten.
-
ausgaben von mysqltuner:
-------- General Statistics
--------------------------------------------------
[--] Skipped version check for MySQLTuner script
[OK] Currently running supported MySQL version 5.5.34-MariaDB-1~wheezy-log
[OK] Operating on 64-bit architecture-------- Storage Engine Statistics
-------------------------------------------
[--] Status: +Archive -BDB +Federated +InnoDB -ISAM -NDBCluster
[--] Data in MyISAM tables: 90M (Tables: 85)
[--] Data in InnoDB tables: 2M (Tables: 19)
[--] Data in PERFORMANCE_SCHEMA tables: 0B (Tables: 17)
[!!] Total fragmented tables: 23-------- Security Recommendations
-------------------------------------------
[OK] All database users have passwords assigned-------- Performance Metrics
-------------------------------------------------
[--] Up for: 11s (342 q [31.091 qps], 118 conn, TX: 46K, RX: 23K)
[--] Reads / Writes: 100% / 0%
[--] Total buffers: 688.0M global + 22.4M per thread (120 max threads)
[OK] Maximum possible memory usage: 3.3G (85% of installed RAM)
[OK] Slow queries: 0% (0/342)
[OK] Highest usage of available connections: 0% (1/120)
[OK] Key buffer size / total MyISAM indexes: 128.0M/7.4M
[!!] Query cache efficiency: 0.0% (0 cached / 223 selects)
[OK] Query cache prunes per day: 0
[OK] Temporary tables created on disk: 12% (10 on disk / 77 total)
[OK] Thread cache hit rate: 93% (8 created / 118 connections)
[OK] Table cache hit rate: 51% (124 open / 243 opened)
[OK] Open file limit used: 21% (219/1K)
[OK] Table locks acquired immediately: 100% (144 immediate / 144 locks)
[OK] InnoDB data size / buffer pool: 2.8M/256.0M-------- Recommendations
-----------------------------------------------------
General recommendations:
Run OPTIMIZE TABLE to defragment tables for better performance
MySQL started within last 24 hours - recommendations may be inaccurate
Enable the slow query log to troubleshoot bad queries
Variables to adjust:
query_cache_limit (> 256K, or use smaller result sets)ausgaben von tuning-primer
INNODB STATUS
Current InnoDB index space = 256 K
Current InnoDB data space = 2 M
Current InnoDB buffer pool free = 96 %
Current innodb_buffer_pool_size = 256 M
Depending on how much space your innodb indexes take up it may be safe
to increase this value to up to 2 / 3 of total system memoryMEMORY USAGE
Max Memory Ever Allocated : 790 M
Configured Max Per-thread Buffers : 2.62 G
Configured Max Global Buffers : 656 M
Configured Max Memory Limit : 3.27 G
Physical Memory : 3.83 G
Max memory limit seem to be within acceptable normsKEY BUFFER
Current MyISAM index space = 7 M
Current key_buffer_size = 128 M
Key cache miss rate is 1 : 3
Key buffer free ratio = 81 %
Your key_buffer_size seems to be fineQUERY CACHE
Query cache is enabled
Current query_cache_size = 256 M
Current query_cache_used = 147 K
Current query_cache_limit = 256 K
Current Query cache Memory fill ratio = .05 %
Current query_cache_min_res_unit = 4 K
Your query_cache_size seems to be too high.
Perhaps you can use these resources elsewhere
MySQL won't cache query results that are larger than query_cache_limit
in sizeSORT OPERATIONS
Current sort_buffer_size = 16 M
Current read_rnd_buffer_size = 2 M
Sort buffer seems to be fineJOINS
./tuning-primer.sh: 401: local: 2097152: bad variable name -
Hallo Hille,
Habe root Rechte. Hatte heute morgen einen tail auf mysql.log, bekomme dort aber keine Fehlermeldung.Und auch auf die mysql.err - auch keine Meldung
-
Hallo Hille,
Habe root Rechte. Hatte heute morgen einen tail auf mysql.log, bekomme dort aber keine Fehlermeldung. -
Hallo,
Hat jemand noch eine Idee was ich machen kann um raus zu kriegen wo der Fehler herkommt? Oder bin ich verurteilt um mit dieser "Behinderung" weiter zu machen?
Auf jedem Fall danke f[size=10]ü[/SIZE]r die Hilfe bis jetzt! -
Guten Morgen,
Hatte das gerade getan. twentytwelve aktiviert. Es ging eben gut, aber nachdem ich 3 verschiedene Seiten einige male aktualisiert hatte, ist das selbe leider wieder passiert. (PHP Fatal error) ;( -
oder meinst Du damit "mit den default css dateien"? Wen das so ist, ja das habe ich auch getan. Hatte ja nur in der style-dafault.css ein paar Farben und Fonts verändert.
-
Standard-Theme auch getestet?
was meinst du den genau damit? -
Leider keine anderes Resultat. Habe alle plugins deaktiviert und beim nach dem 7en aktualisieren war es wieder soweit.
[Wed Dec 11 18:16:54 2013] [error] [client 213.204.207.140] PHP Fatal error: Maximum execution time of 120 seconds exceeded in /var/www/sdtours/wp-includes/cache.php on line 113, referer: http://www.sdtours.net/wp-admin/post.…458&action=edit -
Gut, das ist deutlich, wenn der Fehler aber ohne die Plugins auch auftritt kan ich natürlich alles sofort wieder aktivieren, oder? Dann soll es sicher eine andere Ursache haben.
-
OKe, werde ein backup machen und danach alle plugins deaktivien.
Soll ich dan probieren ob ich die gleichen errors bekomme?
Wenn es dan nicht mehr passiert, sicher die plugins einen nach dem anderen wieder aktivieren und ausprobieren? -
Das sind meine Plugins, (verliere ich die gemachten einstellungen wenn ich sie deaktiviere)
Akismet 2.5.9
All In One SEO Pack 2.1
Fast Secure Contact Form 4.0.18
Google Analyticator 6.4.5
Google XML Sitemaps 3.4
Hupso Share Buttons for Twitter, Facebook & Google+ 3.9.23
NextGEN Gallery 1.9.13
qTranslate 2.5.38
UpdraftPlus - Backup/Restore 1.8.1
WordPress Importer 0.6.1als thema habe ich Unite 2.2.1
-
-
Habe theme in Allgemeines geschoben. Ich denke ist dort besser auf seinem Platz!