Server Support Forum
Anzeige:


Zurück   Server Support Forum > Serverdienste > SQL


Antwort
 
LinkBack Themen-Optionen Bewertung: Bewertung: 2 Stimmen, 5,00 durchschnittlich.
  #196  
Alt 20.09.2010, 10:35
Benutzerbild von vampsm
Registered User
 
Registriert seit: 05.2009
Beiträge: 77
Frage

Hallo,

nach einiges an andere Arbeit etc. muß ich nun doch nochmal nachfragen.

Habe seit Start mit meinem Server einiges eingestellt und wesentliche Verbesserungen an der Performance bekommen, und doch bin ich noch nicht zufrieden da es immer noch einige Sekündchen vergehen bis eine Seite reagiert.

Ganz schlimm ist Wordpress
http://blog.s-kids.de/

hier mal top
Code:
top - 10:33:01 up 25 min,  2 users,  load average: 0.02, 0.21, 0.38
Tasks:  67 total,   2 running,  65 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.3%us,  0.3%sy,  0.0%ni, 99.3%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   4194304k total,   392076k used,  3802228k free,        0k buffers
Swap:        0k total,        0k used,        0k free,        0k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+   PPID TTY      P SWAP   TIME CODE DATA nDRT WCHAN     COMMAND
12053 root      15   0  2432 1108  856 R  0.3  0.0   0:00.09  1548 pts/0    0 1324   0:00   92  340    0 stext     top
    1 root      15   0  1008  380  324 S  0.0  0.0   0:00.76     0 ?        0  628   0:00  772  228    0 stext     init
 1448 root      16   0  9072 2568 2044 S  0.0  0.1   0:00.02 30708 ?        0 6504   0:00  448  468    0 stext     sshd
 1451 slbsmer   15   0  9224 1444  920 R  0.0  0.0   0:00.24  1448 ?        0 7780   0:00  448  620    0 stext     sshd
 1452 slbsmer   15   0  5504 2420 1676 S  0.0  0.1   0:00.08  1451 pts/0    0 3084   0:00  672 1056    0 wait      bash
 1488 root      16   0  7720 2140 1516 S  0.0  0.1   0:00.14  1452 pts/0    0 5580   0:00   28  644    0 wait      su
 1548 root      15   0  4940 2304 1588 S  0.0  0.1   0:00.22  1488 pts/0    0 2636   0:00  672  792    0 wait      bash
 3326 wwwrun    15   0 43388  17m 4956 S  0.0  0.4   0:04.55 32391 ?        0  24m   0:04  372  13m    0 semtimedo httpd2-prefork
 3371 wwwrun    15   0 67004  41m 5388 S  0.0  1.0   0:12.61 32391 ?        0  24m   0:12  372  36m    0 semtimedo httpd2-prefork
 3373 wwwrun    15   0 49400  23m 5196 S  0.0  0.6   0:09.93 32391 ?        0  24m   0:09  372  19m    0 semtimedo httpd2-prefork
 3376 wwwrun    15   0 49420  23m 5224 S  0.0  0.6   0:10.58 32391 ?        0  24m   0:10  372  19m    0 semtimedo httpd2-prefork
 3381 wwwrun    15   0 42512  16m 4944 S  0.0  0.4   0:06.53 32391 ?        0  24m   0:06  372  12m    0 semtimedo httpd2-prefork
 3383 wwwrun    15   0 41536  15m 5104 S  0.0  0.4   0:05.67 32391 ?        0  24m   0:05  372  11m    0 semtimedo httpd2-prefork
 5213 qmaild    18   0  3556  748  544 S  0.0  0.0   0:00.11 30716 ?        0 2808   0:00   52  140    0 stext     qmail-smtpd
 5217 wwwrun    15   0 42228  15m 4012 S  0.0  0.4   0:05.18 32391 ?        0  25m   0:05  372  12m    0 stext     httpd2-prefork
 5256 wwwrun    15   0 43464  18m 5096 S  0.0  0.4   0:06.11 32391 ?        0  24m   0:06  372  13m    0 semtimedo httpd2-prefork
 5261 wwwrun    15   0 42272  16m 4844 S  0.0  0.4   0:03.19 32391 ?        0  24m   0:03  372  12m    0 semtimedo httpd2-prefork
 9258 root      16   0  9072 2564 2044 S  0.0  0.1   0:00.02 30708 ?        0 6508   0:00  448  468    0 stext     sshd
 9262 slbsmer   15   0  9224 1452  920 S  0.0  0.0   0:00.14  9258 ?        0 7772   0:00  448  620    0 stext     sshd
 9263 slbsmer   15   0  5504 2424 1676 S  0.0  0.1   0:00.07  9262 pts/1    0 3080   0:00  672 1056    0 wait      bash
 9295 root      18   0  7724 2144 1516 S  0.0  0.1   0:00.14  9263 pts/1    0 5580   0:00   28  648    0 wait      su
 9303 root      17   0  4940 2300 1580 S  0.0  0.1   0:00.02  9295 pts/1    0 2640   0:00  672  792    0 stext     bash
28286 root      20  -4  2348  660  384 S  0.0  0.0   0:00.00     1 ?        0 1688   0:00  100  376    0 stext     udevd
29772 root      18   0 43564 1288  888 S  0.0  0.0   0:00.24     1 ?        0  41m   0:00  236  40m    0 stext     rsyslogd
30409 root      15   0 14436 9264 1956 S  0.0  0.2   0:00.02     1 ?        0 5172   0:00 2404 7276    0 stext     miniserv.pl
30431 root      18   0  5056  744  520 S  0.0  0.0   0:00.01     1 ?        0 4312   0:00   48  260    0 stext     couriertcpd
30433 root      20   0  3500  692  512 S  0.0  0.0   0:00.00     1 ?        0 2808   0:00   12  124    0 pipe_wait courierlogger
30442 root      25   0  5056  744  520 S  0.0  0.0   0:00.01     1 ?        0 4312   0:00   48  260    0 stext     couriertcpd
30444 root      25   0  3500  688  512 S  0.0  0.0   0:00.00     1 ?        0 2812   0:00   12  124    0 pipe_wait courierlogger
30451 root      18   0  5056  756  532 S  0.0  0.0   0:00.00     1 ?        0 4300   0:00   48  260    0 stext     couriertcpd
30458 root      18   0  3632  856  664 S  0.0  0.0   0:00.00     1 ?        0 2776   0:00   12  256    0 pipe_wait courierlogger
30461 root      25   0  5056  744  520 S  0.0  0.0   0:00.00     1 ?        0 4312   0:00   48  260    0 stext     couriertcpd
30463 root      25   0  3500  684  512 S  0.0  0.0   0:00.00     1 ?        0 2816   0:00   12  124    0 pipe_wait courierlogger
30708 root      15   0  6484 1088  660 S  0.0  0.0   0:00.00     1 ?        0 5396   0:00  448  468    0 stext     sshd
30716 root      15   0  2576  888  720 S  0.0  0.0   0:00.02     1 ?        0 1688   0:00  160  412    0 stext     xinetd
32094 sw-cp-se  15   0  4916 2208 1412 S  0.0  0.1   0:00.04     1 ?        0 2708   0:00  172  672    0 901002534 sw-cp-serverd
32100 root      18   0  2336  804  632 S  0.0  0.0   0:00.00     1 ?        0 1532   0:00   44  248    0 stext     cron
32151 named     18   0 45096 9232 2032 S  0.0  0.2   0:00.03     1 ?        0  35m   0:00  392  36m    0 rt_sigsus named
32178 root      25   0  2936 1296 1104 S  0.0  0.0   0:00.02     1 ?        0 1640   0:00  672  260    0 wait      mysqld_safe
32219 mysql     15   0  198m  66m 4392 S  0.0  1.6   0:08.02 32178 ?        0 132m   0:08 5984 189m    0 stext     mysqld
32233 root      15   0 32868  28m 3148 S  0.0  0.7   0:02.14     1 ?        0 3400   0:02 2404  25m    0 stext     spamd
32238 popuser   18   0 36240  31m 3020 S  0.0  0.8   0:03.09 32233 ?        0 3576   0:03 2404  29m    0 stext     spamd
32288 qmails    16   0  1824  416  328 S  0.0  0.0   0:00.02     1 ?        0 1408   0:00   48  260    0 stext     qmail-send
32289 qmaill    18   0  1776  484  416 S  0.0  0.0   0:00.00 32288 ?        0 1292   0:00    8  252    0 pipe_wait splogger
32290 root      15   0  1804  384  292 S  0.0  0.0   0:00.00 32288 ?        0 1420   0:00   16  272    0 stext     qmail-lspawn
32291 qmailr    18   0  1800  360  272 S  0.0  0.0   0:00.00 32288 ?        0 1440   0:00   12  272    0 stext     qmail-rspawn
32292 qmailq    18   0  1772  356  292 S  0.0  0.0   0:00.00 32288 ?        0 1416   0:00   12  244    0 pipe_wait qmail-clean
32391 root      18   0 38812  16m 8244 S  0.0  0.4   0:00.47     1 ?        0  21m   0:00  372 9408    0 stext     httpd2-prefork
32393 wwwrun    15   0 37832 7944  480 S  0.0  0.2   0:00.00 32391 ?        0  29m   0:00  372 8464    0 182766853 httpd2-prefork
32399 wwwrun    15   0 67544  41m 5320 S  0.0  1.0   0:10.99 32391 ?        0  24m   0:10  372  37m    0 semtimedo httpd2-prefork
32541 drweb     15   0 84760  78m  536 S  0.0  1.9   0:00.18     1 ?        0 4860   0:00 2348  77m    0 stext     drwebd.real
32542 drweb     15   0 84760  77m  340 S  0.0  1.9   0:00.00 32541 ?        0 5056   0:00 2348  77m    0 107564389 drwebd.real

ps free und vmstat

Code:
h1600184:/ # ps
  PID TTY          TIME CMD
 1488 pts/0    00:00:00 su
 1548 pts/0    00:00:00 bash
11940 pts/0    00:00:00 ps
h1600184:/ # free
             total       used       free     shared    buffers     cached
Mem:       4194304     391556    3802748          0          0          0
-/+ buffers/cache:     391556    3802748
Swap:            0          0          0
h1600184:/ # vms´tat
bash: vms´tat: command not found
h1600184:/ # vmstat
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa
 1  0      0 3802740      0      0    0    0 12071 28402    0 15462 12  3 84  1
h1600184:/ #

tuning-primer
Code:
h1600184:/usr/local/bin # ./tuning-primer.sh

        -- MYSQL PERFORMANCE TUNING PRIMER --
             - By: Matthew Montgomery -

MySQL Version 5.0.67-log i686

Uptime = 0 days 0 hrs 15 min 8 sec
Avg. qps = 7
Total Questions = 6873
Threads Connected = 1

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.0/en/server-system-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 enabled.
Current long_query_time = 2 sec.
You have 1 out of 6894 that take longer than 2 sec. to complete
Your long_query_time seems to be fine

BINARY UPDATE LOG
The binary update log is NOT enabled.
You will not be able to do point in time recovery
See http://dev.mysql.com/doc/refman/5.0/en/point-in-time-recovery.html

WORKER THREADS
Current thread_cache_size = 16384
Current threads_cached = 6
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine

MAX CONNECTIONS
Current max_connections = 50
Current threads_connected = 1
Historic max_used_connections = 7
The number of used connections is 14% of the configured maximum.
Your max_connections variable seems to be fine.

No InnoDB Support Enabled!

MEMORY USAGE
Max Memory Ever Allocated : 583 M
Configured Max Per-thread Buffers : 3.08 G
Configured Max Global Buffers : 141 M
Configured Max Memory Limit : 3.22 G
Physical Memory : 4.00 G
Max memory limit seem to be within acceptable norms

KEY BUFFER
Current MyISAM index space = 12 M
Current key_buffer_size = 15 M
Key cache miss rate is 1 : 30
Key buffer free ratio = 83 %
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is enabled
Current query_cache_size = 100 M
Current query_cache_used = 3 M
Current query_cache_limit = 3 M
Current Query cache Memory fill ratio = 3.78 %
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 = 5 M
Current read_rnd_buffer_size = 3 M
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 50.00 M
You have had 24 queries where a join could not use an index properly
join_buffer_size >= 4 M
This is not advised
You should enable "log-queries-not-using-indexes"
Then look for non indexed joins in the slow query log.

OPEN FILES LIMIT
Current open_files_limit = 65535 files
The open_files_limit should typically be set to at least 2x-3x
that of table_cache if you have heavy MyISAM usage.
Your open_files_limit value seems to be fine

TABLE CACHE
Current table_cache value = 212992 tables
You have a total of 3968 tables
You have 3976 open tables.
The table_cache value seems to be fine

TEMP TABLES
Current max_heap_table_size = 40 M
Current tmp_table_size = 40 M
Of 211 temp tables, 16% were created on disk
Created disk tmp tables ratio seems fine

TABLE SCANS
Current read_buffer_size = 5 M
Current table scan ratio = 74 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 0 : 7080
Your table locking seems to be fine

---> query_cache_size habe ich auf 50 M verringert



mysqltuner
Code:
h1600184:/usr/local/bin # ./mysqltuner.pl

 >>  MySQLTuner 1.0.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.0.67-log
[!!] Switch to 64-bit OS - MySQL cannot currently use all of your RAM

-------- Storage Engine Statistics -------------------------------------------
[--] Status: -Archive -BDB -Federated -InnoDB -ISAM -NDBCluster
[--] Data in MyISAM tables: 14M (Tables: 3941)
[--] Data in MEMORY tables: 0B (Tables: 10)
[!!] Total fragmented tables: 25

-------- Performance Metrics -------------------------------------------------
[--] Up for: 15m 31s (7K q [7.727 qps], 304 conn, TX: 10M, RX: 1M)
[--] Reads / Writes: 85% / 15%
[--] Total buffers: 181.0M global + 63.2M per thread (50 max threads)
[!!] Allocating > 2GB RAM on 32-bit systems can cause system instability
[!!] Maximum possible memory usage: 3.3G (81% of installed RAM)
[OK] Slow queries: 0% (2/7K)
[OK] Highest usage of available connections: 14% (7/50)
[OK] Key buffer size / total MyISAM indexes: 15.0M/12.7M
[OK] Key buffer hit rate: 96.8% (21K cached / 708 reads)
[OK] Query cache efficiency: 57.0% (3K cached / 5K selects)
[OK] Query cache prunes per day: 0
[OK] Sorts requiring temporary tables: 0% (0 temp sorts / 215 sorts)
[!!] Joins performed without indexes: 24
[OK] Temporary tables created on disk: 15% (41 on disk / 264 total)
[OK] Thread cache hit rate: 97% (7 created / 304 connections)
[OK] Table cache hit rate: 99% (3K open / 3K opened)
[OK] Open file limit used: 12% (7K/65K)
[OK] Table locks acquired immediately: 100% (3K immediate / 3K locks)

-------- Recommendations -----------------------------------------------------
General recommendations:
    Run OPTIMIZE TABLE to defragment tables for better performance
    MySQL started within last 24 hours - recommendations may be inaccurate
    Adjust your join queries to always utilize indexes
Variables to adjust:
    join_buffer_size (> 50.0M, or always use indexes with joins)

---> join_buffer_size habe ich danch auf 100 M gesetzt



ab2
Code:
h1600184:/ # ab2 -n 20 -c 2  http://www.s-kids.de/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking www.s-kids.de (be patient).....done


Server Software:        Apache/2.2.10
Server Hostname:        www.s-kids.de
Server Port:            80

Document Path:          /
Document Length:        4 bytes

Concurrency Level:      2
Time taken for tests:   15.565 seconds
Complete requests:      20
Failed requests:        0
Write errors:           0
Non-2xx responses:      20
Total transferred:      10580 bytes
HTML transferred:       80 bytes
Requests per second:    1.28 [#/sec] (mean)
Time per request:       1556.490 [ms] (mean)
Time per request:       778.245 [ms] (mean, across all concurrent requests)
Transfer rate:          0.66 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0  134 279.2      0     775
Processing:   605 1412 477.6   1481    2220
Waiting:        0 1105 747.9   1380    2219
Total:        724 1546 426.0   1584    2483

Percentage of the requests served within a certain time (ms)
  50%   1584
  66%   1758
  75%   1831
  80%   1862
  90%   2220
  95%   2483
  98%   2483
  99%   2483
 100%   2483 (longest request)

server-status
Code:
Apache Server Status for www.s-kids.de

Server Version: Apache/2.2.10 (Linux/SUSE) mod_ssl/2.2.10 OpenSSL/0.9.8h PHP/5.2.13 with Suhosin-Patch mod_python/3.3.1 Python/2.6 mod_perl/2.0.4 Perl/v5.10.0
Server Built: Apr 13 2010 16:26:03

Current Time: Monday, 20-Sep-2010 10:59:39 CEST
Restart Time: Monday, 20-Sep-2010 10:57:29 CEST
Parent Server Generation: 0
Server uptime: 2 minutes 10 seconds
1 requests currently being processed, 9 idle workers

___.____.._W_...................................................
................................................................
......................

Scoreboard Key:
"_" Waiting for Connection, "S" Starting up, "R" Reading Request,
"W" Sending Reply, "K" Keepalive (read), "D" DNS Lookup,
"C" Closing connection, "L" Logging, "G" Gracefully finishing,
"I" Idle cleanup of worker, "." Open slot with no current process

PID Key:

   1675 in state: _ ,   1676 in state: _ ,   1677 in state: _ 
   1691 in state: _ ,   3533 in state: _ ,   3121 in state: _ 
   3136 in state: _ ,   3150 in state: _ ,   3151 in state: W 
   3548 in state: _ ,

To obtain a full report with current status information you need to use the ExtendedStatus On directive.
SSL/TLS Session Cache Status:
cache type: SHMCB, shared memory: 512000 bytes, current sessions: 0
subcaches: 32, indexes per subcache: 133
index usage: 0%, cache usage: 0%
total sessions stored since starting: 0
total sessions expired since starting: 0
total (pre-expiry) sessions scrolled out of the cache: 0
total retrieves since starting: 0 hit, 0 miss
total removes since starting: 0 hit, 0 miss
Apache/2.2.10 (Linux/SUSE) Server at www.s-kids.de Port 80


die wahrscheinlich wichtigen Konfigurations-Dateien und Einstellungen darin

my.conf
Code:
###########################

key_buffer = 150M
key_buffer_size = 15M

table_cache = 212992

tmp_table_size = 41943040
max_heap_table_size = 41943040

open_files_limit = 65535
#max_open_files = 1048636

query_cache_limit = 3M
query_cache_size = 50M
query_cache_type = 1

thread_cache_size = 16384

join_buffer_size =  100M

max_allowed_packet = 25M

sort_buffer_size = 5M
net_buffer_length = 8K

read_buffer_size = 5M
read_rnd_buffer_size = 3M

myisam_sort_buffer_size = 5M

concurrent_insert = 1
max_connections = 50

long_query_time = 2
low_priority_updates = 1
log_slow_queries=/var/log/mysqld.slow.log
#log_queries_not_using_indexes = off

wait_timeout = 500
bulk_insert_buffer_size = 5M

#############################

#skip-networking

server-id    = 1

#server-id       = 2

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

skip-innodb
# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /var/lib/mysql/
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /var/lib/mysql/
innodb_log_arch_dir = /var/lib/mysql/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 16M
innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

# The safe_mysqld script
skip-bdb

[safe_mysqld]
log-error=/var/lib/mysql/mysqld.log

skip-bdb

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

[mysqld_multi]
mysqld     = /usr/bin/mysqld_safe
mysqladmin = /usr/bin/mysqladmin
log        = /var/log/mysqld_multi.log
# user       = multi_admin
# password   = secret

server-tuning.conf
Code:
# prefork MPM
<IfModule prefork.c>
    StartServers         3
    MinSpareServers      5
    MaxSpareServers     10
    ServerLimit       150
    MaxClients        256
    MaxRequestsPerChild  10000
</IfModule>

# worker MPM
<IfModule worker.c>
    StartServers         3
    MinSpareThreads     25
    MaxSpareThreads     75 
    ThreadLimit         64
    MaxClients        256
    ThreadsPerChild     50
    MaxRequestsPerChild  10000
</IfModule>

KeepAlive On
MaxKeepAliveRequests 150
KeepAliveTimeout 3


#EnableMMAP off
#EnableSendfile off
<IfModule mod_setenvif.c>

    BrowserMatch "Mozilla/2" nokeepalive
    BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
    BrowserMatch "RealPlayer 4\.0" force-response-1.0
    BrowserMatch "Java/1\.0" force-response-1.0
    BrowserMatch "JDK/1\.0" force-response-1.0


    BrowserMatch "Microsoft Data Access Internet Publishing Provider" redirect-carefully
    BrowserMatch "^WebDrive" redirect-carefully
    BrowserMatch "^WebDAVFS/1.[012]" redirect-carefully
    BrowserMatch "^gnome-vfs" redirect-carefully
</IfModule>

---> MaxClients habe ich verringert auf 150


Das ganze ist ein VServer
SuSE Linux 11.1
1 CPU
2 bzw. 4 GB RAM


Liegen die Schwächen an der "Hardware" (VServer ) oder kann ich mit der richtigen (besseren) Konfiguration noch einiges an Leistung heraus holen?

Bisher habe ich noch nicht den Traffic aber wenn meine anderen Joomla Projekte auf dem Server Online gehen, habe ich bedenken????

Vielen Vielen DANK an alle die immer wieder geniale Lösungen haben
Mit Zitat antworten

  #197  
Alt 20.09.2010, 11:23
Benutzerbild von Huschi
Moderator
 
Registriert seit: 09.2003
Ort: Nürnberg
Beiträge: 15.334
Blog-Einträge: 5

Zitat:
Zitat von vampsm Beitrag anzeigen
Warning: Server has not been running for at least 48hrs.
It may not be safe to use these recommendations
Du kannst noch so viele Fakten bringe. Aber dieser Teil ist essentiell. Die Statistik-Daten sagen immer nur etwas über die Zeit aus. Wenn keine Zeit verstrichen ist, sind diese Daten für den Lokus.

Zitat:
Liegen die Schwächen an der "Hardware" (VServer )
Grundsätzlich und meist definitiv: Ja!

Zitat:
Bisher habe ich noch nicht den Traffic aber wenn meine anderen Joomla Projekte auf dem Server Online gehen, habe ich bedenken????
Und genau das stößt Du aktuell auch mit der Optimierungsarbeit an die Grenzen:
Denn wenn keine "natürliche Last" drauf ist, kannst Du nur künstlich optimieren. Und das geht meistens schief.

huschi.
__________________
huschi.net - Linux-Server-Admin FAQ
Consult-N.de - kommerzieller Linux-Support
Mit Zitat antworten
  #198  
Alt 25.09.2010, 21:46
Registered User
 
Registriert seit: 08.2006
Beiträge: 169

Hallo,

habe im Moment leider auch ein Problem mit meinem mysql server.
Er kommt einfach nicht mehr mit den Anfragen hinterher.

Hier mal die Ausgabe vom Script:
Code:
        -- MYSQL PERFORMANCE TUNING PRIMER --
             - By: Matthew Montgomery -

MySQL Version 5.0.51a-24+lenny4-log i486

Uptime = 1 days 8 hrs 8 min 10 sec
Avg. qps = 65
Total Questions = 7598783
Threads Connected = 159

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.0/en/server-system-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 sec.
You have 19651 out of 7598810 that take longer than 10 sec. to complete
Your long_query_time seems to be fine

BINARY UPDATE LOG
The binary update log is NOT enabled.
You will not be able to do point in time recovery
See http://dev.mysql.com/doc/refman/5.0/en/point-in-time-recovery.html

WORKER THREADS
Current thread_cache_size = 8
Current threads_cached = 4
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine

MAX CONNECTIONS
Current max_connections = 10000
Current threads_connected = 159
Historic max_used_connections = 6144
The number of used connections is 61% of the configured maximum.
Your max_connections variable seems to be fine.

INNODB STATUS
Current InnoDB index space = 0 bytes
Current InnoDB data space = 0 bytes
Current InnoDB buffer pool free = 96 %
Current innodb_buffer_pool_size = 8 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 : 15.79 G
Configured Max Per-thread Buffers : 25.63 G
Configured Max Global Buffers : 42 M
Configured Max Memory Limit : 25.67 G
Physical Memory : 7.86 G

nMax memory limit exceeds 90% of physical memory

KEY BUFFER
Current MyISAM index space = 112 M
Current key_buffer_size = 16 M
Key cache miss rate is 1 : 101
Key buffer free ratio = 88 %
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is enabled
Current query_cache_size = 16 M
Current query_cache_used = 2 M
Current query_cache_limit = 10 M
Current Query cache Memory fill ratio = 17.74 %
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 = 2 M
Current read_rnd_buffer_size = 256 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 132.00 K
You have had 0 queries where a join could not use an index properly
Your joins seem to be using indexes properly

OPEN FILES LIMIT
Current open_files_limit = 50000 files
The open_files_limit should typically be set to at least 2x-3x
that of table_cache if you have heavy MyISAM usage.
Your open_files_limit value seems to be fine

TABLE CACHE
Current table_cache value = 192 tables
You have a total of 147 tables
You have 192 open tables.
Current table_cache hit rate is 0%
, while 100% of your table cache is in use
You should probably increase your table_cache

TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 32 M
Of 1077 temp tables, 3% were created on disk
Effective in-memory tmp_table_size is limited to max_heap_table_size.
Created disk tmp tables ratio seems fine

TABLE SCANS
Current read_buffer_size = 128 K
Current table scan ratio = 472 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 1 : 0
You may benefit from selective use of InnoDB.
If you have long running SELECT's against MyISAM tables and perform
frequent updates consider setting 'low_priority_updates=1'
If you have a high concurrency of inserts on Dynamic row-length tables
consider setting 'concurrent_insert=2'.
Top
Code:
top - 22:42:49 up 221 days,  6:34,  2 users,  load average: 13.62, 9.82, 9.09
Tasks: 350 total,   1 running, 348 sleeping,   0 stopped,   1 zombie
Cpu(s): 14.3%us,  9.6%sy,  0.0%ni, 76.0%id,  0.0%wa,  0.1%hi,  0.0%si,  0.0%st
Mem:   8245660k total,  2780744k used,  5464916k free,   306712k buffers
Swap:  1046960k total,    39232k used,  1007728k free,  1427696k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
10178 mysql     40   0  822m 455m 5408 S  188  5.7   1620:39 mysqld
25540 www-data  40   0 25340 8128 5724 S    0  0.1   0:00.05 php-cgi
28140 root      40   0  2512 1280  872 R    0  0.0   0:00.02 top
    1 root      40   0  1972  392  372 S    0  0.0   1:04.69 init
    2 root      40   0     0    0    0 S    0  0.0   0:00.00 kthreadd
    3 root      RT   0     0    0    0 S    0  0.0   0:05.34 migration/0
    4 root      20   0     0    0    0 S    0  0.0   8:44.32 ksoftirqd/0
    5 root      RT   0     0    0    0 S    0  0.0   0:06.11 migration/1
    6 root      20   0     0    0    0 S    0  0.0   4:52.90 ksoftirqd/1
    7 root      RT   0     0    0    0 S    0  0.0   0:06.28 migration/2
    8 root      20   0     0    0    0 S    0  0.0   4:14.17 ksoftirqd/2
    9 root      RT   0     0    0    0 S    0  0.0   0:06.47 migration/3
   10 root      20   0     0    0    0 S    0  0.0   3:36.26 ksoftirqd/3
   11 root      RT   0     0    0    0 S    0  0.0   0:12.90 migration/4
   12 root      20   0     0    0    0 S    0  0.0   5:46.04 ksoftirqd/4
   13 root      RT   0     0    0    0 S    0  0.0   0:17.50 migration/5
   14 root      20   0     0    0    0 S    0  0.0   2:07.78 ksoftirqd/5
   15 root      RT   0     0    0    0 S    0  0.0   0:19.65 migration/6
   16 root      20   0     0    0    0 S    0  0.0   1:15.82 ksoftirqd/6
   17 root      RT   0     0    0    0 S    0  0.0   0:22.11 migration/7
   18 root      20   0     0    0    0 S    0  0.0   1:09.22 ksoftirqd/7
   19 root      20   0     0    0    0 S    0  0.0   0:02.42 events/0
   20 root      20   0     0    0    0 S    0  0.0   2:38.54 events/1
   21 root      20   0     0    0    0 S    0  0.0   0:05.72 events/2
   22 root      20   0     0    0    0 S    0  0.0   0:04.72 events/3
   23 root      20   0     0    0    0 S    0  0.0   0:07.55 events/4
   24 root      20   0     0    0    0 S    0  0.0   0:04.10 events/5
   25 root      20   0     0    0    0 S    0  0.0   0:03.40 events/6
   26 root      20   0     0    0    0 S    0  0.0   0:06.28 events/7
   27 root      20   0     0    0    0 S    0  0.0   0:00.00 cpuset
   28 root      20   0     0    0    0 S    0  0.0   0:00.01 khelper
   34 root      20   0     0    0    0 S    0  0.0   0:00.00 async/mgr
  249 root      20   0     0    0    0 S    0  0.0   0:00.40 sync_supers
  251 root      20   0     0    0    0 S    0  0.0   0:00.28 bdi-default
  252 root      20   0     0    0    0 S    0  0.0   0:00.00 kintegrityd/0
  253 root      20   0     0    0    0 S    0  0.0   0:00.00 kintegrityd/1
  254 root      20   0     0    0    0 S    0  0.0   0:00.00 kintegrityd/2
  255 root      20   0     0    0    0 S    0  0.0   0:00.00 kintegrityd/3
  256 root      20   0     0    0    0 S    0  0.0   0:00.00 kintegrityd/4
  257 root      20   0     0    0    0 S    0  0.0   0:00.00 kintegrityd/5
  258 root      20   0     0    0    0 S    0  0.0   0:00.00 kintegrityd/6
  259 root      20   0     0    0    0 S    0  0.0   0:00.00 kintegrityd/7
  260 root      20   0     0    0    0 S    0  0.0   0:00.14 kblockd/0
  261 root      20   0     0    0    0 S    0  0.0   0:00.52 kblockd/1
  262 root      20   0     0    0    0 S    0  0.0   0:00.18 kblockd/2
mysqltuner
Code:
 >>  MySQLTuner 1.0.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.0.51a-24+lenny4-log
[!!] Switch to 64-bit OS - MySQL cannot currently use all of your RAM

-------- Storage Engine Statistics -------------------------------------------
[--] Status: +Archive -BDB -Federated +InnoDB -ISAM -NDBCluster
[--] Data in MyISAM tables: 377M (Tables: 130)
[!!] InnoDB is enabled but isn't being used
[!!] Total fragmented tables: 13

-------- Performance Metrics -------------------------------------------------
[--] Up for: 1d 8h 16m 25s (7M q [65.834 qps], 31M conn, TX: 604M, RX: 436M)
[--] Reads / Writes: 67% / 33%
[--] Total buffers: 58.0M global + 2.6M per thread (10000 max threads)
[!!] Allocating > 2GB RAM on 32-bit systems can cause system instability
[!!] Maximum possible memory usage: 25.7G (326% of installed RAM)
[OK] Slow queries: 0% (19K/7M)
[OK] Highest usage of available connections: 61% (6144/10000)
[OK] Key buffer size / total MyISAM indexes: 16.0M/112.5M
[OK] Key buffer hit rate: 99.0% (12M cached / 118K reads)
[OK] Query cache efficiency: 39.9% (1M cached / 3M 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: 3% (38 on disk / 1K total)
[OK] Thread cache hit rate: 99% (106K created / 31M connections)
[!!] Table cache hit rate: 0% (192 open / 131K opened)
[OK] Open file limit used: 0% (203/50K)
[!!] Table locks acquired immediately: 35%
[!!] Connections aborted: 96%

-------- Recommendations -----------------------------------------------------
General recommendations:
    Add skip-innodb to MySQL configuration to disable InnoDB
    Run OPTIMIZE TABLE to defragment tables for better performance
    Enable the slow query log to troubleshoot bad queries
    Increase table_cache gradually to avoid file descriptor limits
    Optimize queries and/or use InnoDB to reduce lock wait
    Your applications are not closing MySQL connections properly
Variables to adjust:
  *** MySQL's maximum memory usage is dangerously high ***
  *** Add RAM before increasing MySQL buffer variables ***
    table_cache (> 192)
vllt. kann mir jemand ein paar tipps geben was ich ändern soll?
Mit Zitat antworten
  #199  
Alt 26.09.2010, 20:01
Benutzerbild von Huschi
Moderator
 
Registriert seit: 09.2003
Ort: Nürnberg
Beiträge: 15.334
Blog-Einträge: 5

Grundsätzlich gehe ich davon aus, dass Du lesen kannst.
Daher solltest Du die Hinweise vom tuning-primer auch verstehen, oder?

Zitat:
Zitat von TAiS46 Beitrag anzeigen
Current long_query_time = 10 sec.
10 Sekunden sind extrem lang. Ich tendiere eher dahin schon 2 bis 3 Sekunden als "long" zu bezeichnen. Das lieferte Dir einen besseren statistischen Wert, wie viele Queries ggf. Andere blockieren.

Zitat:
Current max_connections = 10000
Current threads_connected = 159
Historic max_used_connections = 6144
Hier würde ich mal nachforschen. Dazu wäre Sinnvoll zu wissen, wie der Apache-Eingestellt ist.
Aber zusammen mit einer Ausgabe vom mysqltuner macht es Sinn:
Zitat:
[!!] Connections aborted: 96%
Ich tippe darauf, dass Dein MySQL von Außen zugänglich ist. Neben der Grundsätzlichen Unsicherheit ist dies natürlich auch noch der Performance abträglich.

Zitat:
Max Memory Ever Allocated : 15.79 G
Configured Max Memory Limit : 25.67 G
Physical Memory : 7.86 G
Das finde ich hierbei am Besten! Frei nach dem Motto "Swap ist doch nur Speicher" wundert man sich, wenn der Server schwächelt.

Zitat:
Current query_cache_size = 16 M
Current query_cache_used = 2 M
Current Query cache Memory fill ratio = 17.74 %
Hier ist die Frage, was für eine Datenbank liegt denn drauf? Wie wird sie genutzt?

Zitat:
Current read_rnd_buffer_size = 256 K
Alle Read-Buffers kannst Du getrost verdoppeln bis vervierfachen.

Zitat:
Current open_files_limit = 50000 files
The open_files_limit should typically be set to at least 2x-3x
Das muss ich wohl nicht übersetzten, oder?

Zitat:
Current table_cache value = 192 tables
You have a total of 147 tables
You have 192 open tables.
Current table_cache hit rate is 0%
Diese schlechte Hit-Rate zieht natürlich Performance. Der Table-Cache muss deutlich höher als total-tables sein. Diese Hit-Rate solltest Du auf bei einer so geringen Anzahl der Tablellen auf fast 100% bringen.

huschi.
__________________
huschi.net - Linux-Server-Admin FAQ
Consult-N.de - kommerzieller Linux-Support
Mit Zitat antworten
  #200  
Alt 26.09.2010, 20:32
Benutzerbild von vampsm
Registered User
 
Registriert seit: 05.2009
Beiträge: 77

Hallo Huschi,

noch mal zu meinem Setup und Problem.

Kann ich davon ausgehen, das meine Konfig so fast i.O. ist?

Ist mein V-Server so schlecht? oder sind kann eine andere Konfig/Setup eine Rolle Spielen (zu viele Prozesse Module etc.)



Was kannst du empfahlen?


MFG
Mit Zitat antworten
  #201  
Alt 26.09.2010, 21:39
Benutzerbild von Huschi
Moderator
 
Registriert seit: 09.2003
Ort: Nürnberg
Beiträge: 15.334
Blog-Einträge: 5

@vampsm
Hast Du meine Antwort auf Deinen Request von oben:
1. eigentlich gelesen?
2. und verstanden?

Wenn 1. Nein: dann nachholen!
Wenn 1. Ja: dann bitte 2. nachholen.
Wenn 2. dauerhaft Nein: Konkrete Nachfrage stellen.

huschi.
__________________
huschi.net - Linux-Server-Admin FAQ
Consult-N.de - kommerzieller Linux-Support
Mit Zitat antworten
  #202  
Alt 09.10.2010, 12:00
Registered User
 
Registriert seit: 12.2009
Beiträge: 4

Hallo,

Die Optimierung meines Sql-servers bereitet mir momentan Probleme, zumindest seit der Root gewechselt wurde. Nach vielen schlaflosen Nächten poste Ich hier mal meine .conf.

Zum Root:

Intel Atom mit Hyper Threating
2 x 1,6 Ghz
2 GB Ram
OS: Debian lenny mit Plesk

Apache conf

Code:
#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.2/ for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#
# The configuration directives are grouped into three basic sections:
#  1. Directives that control the operation of the Apache server process as a
#     whole (the 'global environment').
#  2. Directives that define the parameters of the 'main' or 'default' server,
#     which responds to requests that aren't handled by a virtual host.
#     These directives also provide default values for the settings
#     of all virtual hosts.
#  3. Settings for virtual hosts, which allow Web requests to be sent to
#     different IP addresses or hostnames and have them handled by the
#     same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "/var/log/apache2/foo.log"
# with ServerRoot set to "" will be interpreted by the
# server as "//var/log/apache2/foo.log".
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at <URL:http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#<IfModule !mpm_winnt.c>
#<IfModule !mpm_netware.c>
LockFile /var/lock/apache2/accept.lock
#</IfModule>
#</IfModule>

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 30

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 150

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 2

##
## Server-Pool Size Regulation (MPM specific)
## 

# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_prefork_module>
    StartServers          5
    MinSpareServers       5
    MaxSpareServers      10
    MaxClients          100
    MaxRequestsPerChild   0
</IfModule>

# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_worker_module>
    StartServers          2
    MaxClients          100
    MinSpareThreads      25
    MaxSpareThreads      75 
    ThreadsPerChild      25
    MaxRequestsPerChild   0
</IfModule>

# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#

AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
#
<Files ~ "^\.ht">
    Order allow,deny
    Deny from all
</Files>

#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain


#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog /var/log/apache2/error.log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

# Include module configuration:
Include /etc/apache2/mods-enabled/*.load
Include /etc/apache2/mods-enabled/*.conf

# Include all the user configurations:
Include /etc/apache2/httpd.conf

# Include ports listing
Include /etc/apache2/ports.conf

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
# If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

#
# Define an access log for VirtualHosts that don't define their own logfile
CustomLog /var/log/apache2/other_vhosts_access.log vhost_combined

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# Putting this all together, we can internationalize error responses.
#
# We use Alias to redirect any /error/HTTP_<error>.html.var response to
# our collection of by-error message multi-language collections.  We use 
# includes to substitute the appropriate text.
#
# You can modify the messages' appearance without changing any of the
# default HTTP_<error>.html.var files by adding the line:
#
#   Alias /error/include/ "/your/include/path/"
#
# which allows you to create your own set of files by starting with the
# /usr/share/apache2/error/include/ files and copying them to /your/include/path/, 
# even on a per-VirtualHost basis.  The default include files will display
# your Apache version number and your ServerAdmin email address regardless
# of the setting of ServerSignature.
#
# The internationalized error documents require mod_alias, mod_include
# and mod_negotiation.  To activate them, uncomment the following 30 lines.

#    Alias /error/ "/usr/share/apache2/error/"
#
#    <Directory "/usr/share/apache2/error">
#        AllowOverride None
#        Options IncludesNoExec
#        AddOutputFilter Includes html
#        AddHandler type-map var
#        Order allow,deny
#        Allow from all
#        LanguagePriority en cs de es fr it nl sv pt-br ro
#        ForceLanguagePriority Prefer Fallback
#    </Directory>
#
#    ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var
#    ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var
#    ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var
#    ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var
#    ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var
#    ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var
#    ErrorDocument 410 /error/HTTP_GONE.html.var
#    ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var
#    ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var
#    ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
#    ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var
#    ErrorDocument 415 /error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var
#    ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var
#    ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var
#    ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var
#    ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var
#    ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var



# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
Include /etc/apache2/conf.d/

# Include the virtual host configurations:
Include /etc/apache2/sites-enabled/
AddOutputFilter INCLUDES .shtml
AddType text/html .shtml
AddType application/x-httpd-php .php
AddType application/x-httpd-php-source .phps
my.conf

Code:
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
# 
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port        = 3306
socket        = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket        = /var/run/mysqld/mysqld.sock
nice        = 0

[mysqld]
#
# * Basic Settings
#
user        = mysql
pid-file    = /var/run/mysqld/mysqld.pid
socket        = /var/run/mysqld/mysqld.sock
port        = 3306
basedir        = /usr
datadir        = /var/lib/mysql
tmpdir        = /tmp
language    = /usr/share/mysql/english
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address        = 127.0.0.1
#
# * Fine Tuning
#
key_buffer        = 16M
max_allowed_packet    = 16M
thread_stack        = 192K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover         = BACKUP
#max_connections        = 100
#table_cache            = 64
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit    = 1M
query_cache_size        = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file        = /var/log/mysql/mysql.log
#general_log             = 1
#
# Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# Here you can see queries with especially long duration
#log_slow_queries    = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id        = 1
#log_bin            = /var/log/mysql/mysql-bin.log
expire_logs_days    = 10
max_binlog_size         = 100M
#binlog_do_db        = include_database_name
#binlog_ignore_db    = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * InnoDB plugin
# As of MySQL 5.1.38, the InnoDB plugin from Oracle is included in the MySQL source code.
# It has many improvements and better performances than the built-in InnoDB storage engine.
# Please read http://www.innodb.com/products/innodb_plugin/ for more information.
# Uncommenting the two following lines to use the InnoDB plugin.
#ignore_builtin_innodb
#plugin-load=innodb=ha_innodb_plugin.so
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet    = 16M

[mysql]
#no-auto-rehash    # faster start of mysql but no tab completition

[isamchk]
key_buffer        = 16M

#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/
tuning-primer.sh

Code:
n112h143:/usr/bin# tuning-primer.sh

        -- MYSQL PERFORMANCE TUNING PRIMER --
             - By: Matthew Montgomery -

MySQL Version 5.1.51-0.dotdeb.1 i486

Uptime = 1 days 22 hrs 57 min 23 sec
Avg. qps = 0
Total Questions = 134530
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.1/en/server-system-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 2 out of 134551 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 NOT enabled.
You will not be able to do point in time recovery
See http://dev.mysql.com/doc/refman/5.1/en/point-in-time-recovery.html

WORKER THREADS
Current thread_cache_size = 8
Current threads_cached = 7
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine

MAX CONNECTIONS
Current max_connections = 151
Current threads_connected = 2
Historic max_used_connections = 20
The number of used connections is 13% of the configured maximum.
Your max_connections variable seems to be fine.

INNODB STATUS
Current InnoDB index space = 3 M
Current InnoDB data space = 3 M
Current InnoDB buffer pool free = 13 %
Current innodb_buffer_pool_size = 8 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 : 95 M
Configured Max Per-thread Buffers : 405 M
Configured Max Global Buffers : 42 M
Configured Max Memory Limit : 447 M
Physical Memory : 1.97 G
Max memory limit seem to be within acceptable norms

KEY BUFFER
Current MyISAM index space = 46 M
Current key_buffer_size = 16 M
Key cache miss rate is 1 : 117
Key buffer free ratio = 88 %
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is enabled
Current query_cache_size = 16 M
Current query_cache_used = 15 M
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 99.34 %
Current query_cache_min_res_unit = 4 K
However, 6112 queries have been removed from the query cache due to lack of memory
Perhaps you should raise query_cache_size
MySQL won't cache query results that are larger than query_cache_limit in size

SORT OPERATIONS
Current sort_buffer_size = 2 M
Current read_rnd_buffer_size = 256 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 132.00 K
You have had 37 queries where a join could not use an index properly
You should enable "log-queries-not-using-indexes"
Then look for non indexed joins in the slow query log.
If you are unable to optimize your queries you may want to increase your
join_buffer_size to accommodate larger joins in one pass.

Note! This script will still suggest raising the join_buffer_size when
ANY joins not using indexes are found.

OPEN FILES LIMIT
Current open_files_limit = 1024 files
The open_files_limit should typically be set to at least 2x-3x
that of table_cache if you have heavy MyISAM usage.
Your open_files_limit value seems to be fine

TABLE CACHE
Current table_open_cache = 64 tables
Current table_definition_cache = 256 tables
You have a total of 864 tables
You have 64 open tables.
Current table_cache hit rate is 0%
, while 100% of your table cache is in use
You should probably increase your table_cache
You should probably increase your table_definition_cache value.

TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 16 M
Of 10174 temp tables, 29% were created on disk
Perhaps you should increase your tmp_table_size and/or max_heap_table_size
to reduce the number of disk-based temporary tables
Note! BLOB and TEXT columns are not allow in memory tables.
If you are using these columns raising these values might not impact your
ratio of on disk temp tables.

TABLE SCANS
Current read_buffer_size = 128 K
Current table scan ratio = 406 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 1 : 991
You may benefit from selective use of InnoDB.
If you have long running SELECT's against MyISAM tables and perform
frequent updates consider setting 'low_priority_updates=1'
If you have a high concurrency of inserts on Dynamic row-length tables
consider setting 'concurrent_insert=2'.
Lg Andi
Mit Zitat antworten
  #203  
Alt 10.10.2010, 19:51
Benutzerbild von Huschi
Moderator
 
Registriert seit: 09.2003
Ort: Nürnberg
Beiträge: 15.334
Blog-Einträge: 5

Zitat:
Zitat von andianden Beitrag anzeigen
Die Optimierung meines Sql-servers bereitet mir momentan Probleme
Heißt konkret?
Letztendlich kann ich nur sehen, dass Du alle Tipps aus dem tuning-primer-Script nicht umsetzt.

huschi.
__________________
huschi.net - Linux-Server-Admin FAQ
Consult-N.de - kommerzieller Linux-Support
Mit Zitat antworten
  #204  
Alt 11.10.2010, 14:26
Registered User
 
Registriert seit: 12.2009
Beiträge: 4

Hallo,

Ich hab jetz einiges aus den tuning-primer entnommen, wo bei Ich einiges wieder rausnehmen konnte da es zu Datenbankfehlern in meiner vbulletin Installation kam. Obwohl der Mysql ohne Fehler sich stoppen und starten liess.

my.conf

Code:
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
# 
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port        = 3306
socket        = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket        = /var/run/mysqld/mysqld.sock
nice        = 0

[mysqld]
#
# * Basic Settings
#
user        = mysql
pid-file    = /var/run/mysqld/mysqld.pid
socket        = /var/run/mysqld/mysqld.sock
port        = 3306
basedir        = /usr
datadir        = /var/lib/mysql
tmpdir        = /tmp
language    = /usr/share/mysql/english
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address        = 127.0.0.1
#
# * Fine Tuning
#
key_buffer        = 16M
max_allowed_packet    = 16M
thread_stack        = 192K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover         = BACKUP
max_connections        = 100
table_cache            = 1024
thread_concurrency     = 8
#
# * Query Cache Configuration
#
query_cache_limit    = 1M
query_cache_size        = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file        = /var/log/mysql/mysql.log
#general_log             = 1
#
# Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# Here you can see queries with especially long duration
log_slow_queries    = /var/log/mysql/mysql-slow.log
long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id        = 1
log_bin            = /var/log/mysql/mysql-bin.log
expire_logs_days    = 10
max_binlog_size         = 100M
#binlog_do_db        = include_database_name
#binlog_ignore_db    = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * InnoDB plugin
# As of MySQL 5.1.38, the InnoDB plugin from Oracle is included in the MySQL source code.
# It has many improvements and better performances than the built-in InnoDB storage engine.
# Please read http://www.innodb.com/products/innodb_plugin/ for more information.
# Uncommenting the two following lines to use the InnoDB plugin.
#ignore_builtin_innodb
#plugin-load=innodb=ha_innodb_plugin.so
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet    = 16M

[mysql]
#no-auto-rehash    # faster start of mysql but no tab completition

[isamchk]
key_buffer        = 16M

#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/
tuning-primer.sh

Code:
n112h143:/usr/bin# tuning-primer.sh

        -- MYSQL PERFORMANCE TUNING PRIMER --
             - By: Matthew Montgomery -

MySQL Version 5.1.51-0.dotdeb.1-log i486

Uptime = 0 days 0 hrs 6 min 21 sec
Avg. qps = 761
Total Questions = 290056
Threads Connected = 3

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.1/en/server-system-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 enabled.
Current long_query_time = 2.000000 sec.
You have 0 out of 290088 that take longer than 2.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 = 8
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 = 100
Current threads_connected = 3
Historic max_used_connections = 3
The number of used connections is 3% 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 = 3 M
Current InnoDB data space = 3 M
Current InnoDB buffer pool free = 19 %
Current innodb_buffer_pool_size = 8 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 : 50 M
Configured Max Per-thread Buffers : 271 M
Configured Max Global Buffers : 42 M
Configured Max Memory Limit : 313 M
Physical Memory : 1.97 G
Max memory limit seem to be within acceptable norms

KEY BUFFER
Current MyISAM index space = 44 M
Current key_buffer_size = 16 M
Key cache miss rate is 1 : 15766
Key buffer free ratio = 87 %
Your key_buffer_size seems to be too high.
Perhaps you can use these resources elsewhere

QUERY CACHE
Query cache is enabled
Current query_cache_size = 16 M
Current query_cache_used = 19 K
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = .12 %
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 = 2 M
Current read_rnd_buffer_size = 256 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 132.00 K
You have had 0 queries where a join could not use an index properly
Your joins seem to be using indexes properly

OPEN FILES LIMIT
Current open_files_limit = 2158 files
The open_files_limit should typically be set to at least 2x-3x
that of table_cache if you have heavy MyISAM usage.
Your open_files_limit value seems to be fine

TABLE CACHE
Current table_open_cache = 1024 tables
Current table_definition_cache = 256 tables
You have a total of 896 tables
You have 897 open tables.
The table_cache value seems to be fine
You should probably increase your table_definition_cache value.

TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 16 M
Of 580 temp tables, 12% were created on disk
Created disk tmp tables ratio seems fine

TABLE SCANS
Current read_buffer_size = 128 K
Current table scan ratio = 9 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 0 : 293384
Your table locking seems to be fine
Mit Zitat antworten
  #205  
Alt 11.10.2010, 15:34
Registered User
 
Registriert seit: 03.2006
Alter: 28
Beiträge: 774

Mich würde mal interessieren:
Zitat:
Temporary table size is already large - reduce result set size
Wie genau behebt man sowas denn?
Mit Zitat antworten
  #206  
Alt 12.10.2010, 06:55
Benutzerbild von Huschi
Moderator
 
Registriert seit: 09.2003
Ort: Nürnberg
Beiträge: 15.334
Blog-Einträge: 5

Zitat:
Zitat von andianden Beitrag anzeigen
da es zu Datenbankfehlern in meiner vbulletin Installation kam.
Jetzt frag ich schon zum zweiten Mal:
Was heißt das Konkret? Gibt es dazu Fakten?

Zitat:
Uptime = 0 days 0 hrs 6 min 21 sec
Nach 6 Minuten liefert das Script noch keine brauchbaren statistischen Werte.
Mit dem Output ist also noch nichts anzufangen.


@Voodoo:
Kommt drauf an, wo Du die Fehlermeldung bekommst.

huschi.
__________________
huschi.net - Linux-Server-Admin FAQ
Consult-N.de - kommerzieller Linux-Support
Mit Zitat antworten
  #207  
Alt 12.10.2010, 09:07
Registered User
 
Registriert seit: 03.2006
Alter: 28
Beiträge: 774

@Huschi
Im Mysql-Tuner (also nicht im Tuning-Primer):
http://mysqltuner.pl/mysqltuner.pl
Mit Zitat antworten
  #208  
Alt 12.10.2010, 13:18
Benutzerbild von Huschi
Moderator
 
Registriert seit: 09.2003
Ort: Nürnberg
Beiträge: 15.334
Blog-Einträge: 5

Mit ein bisschen Verständnis fürs Programmieren würde man die Meldung direkt im Source finden und erkennen, dass es ausgegeben wird sobald pct_temp_disk > 25 und max_tmp_table_size >= 256 ist. Vorher wird das Selbe nur mit einem anderen Wert für max_tmp_table_size < 256*1024*1024 abgefragt.
Nach Adam Riese und allgemeiner Logik folgt: Dein max_tmp_table_size übersteigt die 256 MiB.
Da dennoch über 25% der Temp-Tables auf Platte geschrieben werden, empfiehlt mysqltuner die Queries zu überarbeiten. (Du hast uns nämlich die zweite Zeile der Meldung unterschlagen: "Reduce your SELECT DISTINCT queries without LIMIT clauses")

Nochmal auf Deutsch und für Leute ohne Programmierkenntnisse:
Um diese Meldung weg zu bekommen, müssen die SQL-Queries verbessert werden.
Falls man das nicht kann, muss man eben damit leben.

huschi.
__________________
huschi.net - Linux-Server-Admin FAQ
Consult-N.de - kommerzieller Linux-Support
Mit Zitat antworten
  #209  
Alt 12.10.2010, 19:03
Registered User
 
Registriert seit: 12.2009
Beiträge: 4

Hallo Huschi,

Nachdem Ich laut tuning-primer Änderungen in der my.conf editiert hatte und danach den Mysql reaktiviert hatte.
Kam es in meiner vb Installation zu dauernden Datenbankfehler egal ob Ich mich durch das Forum oder durch das Admincp geklickt hatte. Aber komischerweise waren die fehler weg nachdem ich das Backup was Ich vor den Einstellungen gemacht hatte , wiedereingespielt hatte. Aber mir kommt gerade der Gedanke da Ich n meinen schicken Pleskpanel auf Mysql-client 5.0 komme und Mysql-server-5.1 sich befindet . Das darin womöglich der Fehler liegt.

Gebe Ich aptitude show mysql-client über shell ein kommt mysql-client-5.1 und gekennzeichnet ist er als manuell installiert.

MFG Andi
Mit Zitat antworten
  #210  
Alt 12.10.2010, 20:42
Registered User
 
Registriert seit: 03.2006
Alter: 28
Beiträge: 774

Zitat:
Zitat von Huschi Beitrag anzeigen
Um diese Meldung weg zu bekommen, müssen die SQL-Queries verbessert werden.
Falls man das nicht kann, muss man eben damit leben.
Dann muss ich wohl damit leben. In meinem vB und wBB schraube ich nichts drin rum.
Dachte ich's mir doch, dass es so ist und die Meldung an den Queries liegt.
Mit Zitat antworten
Antwort

Lesezeichen

Stichworte
primer, tuning


Themen-Optionen
Thema bewerten
Thema bewerten:

Forumregeln
Es ist dir nicht erlaubt, neue Themen zu verfassen.
Es ist dir nicht erlaubt, auf Beiträge zu antworten.
Es ist dir nicht erlaubt, Anhänge hochzuladen.
Es ist dir nicht erlaubt, deine Beiträge zu bearbeiten.

BB-Code ist an.
Smileys sind an.
[IMG] Code ist aus.
HTML-Code ist aus.
Trackbacks sind aus
Pingbacks sind aus
Refbacks sind aus


Ähnliche Themen
Thema Autor Forum Antworten Letzter Beitrag
Kann mir mahl jemand weiter helfen ktr453 Dedizierte Server 16 31.03.2008 21:52
MySQL kaputt PeterOG SQL 27 11.08.2007 15:17
Query failed : Table 'tbl_knowledgebase_qns' is read only disoft SQL 3 30.04.2007 13:03
Proftpd verbindet sich doppelt MF-Scripts FTP 0 31.03.2007 01:49





Powered by vBulletin® Version 3.8.8 Beta 4 (Deutsch)
Copyright ©2000 - 2014, vBulletin Solutions, Inc.
Content Relevant URLs by vBSEO ©2011, Crawlability, Inc.