Dit staat er in de error log:
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
| 120612 21:37:30 [Note] Event Scheduler: Purging the queue. 0 events
120612 21:37:30 InnoDB: Starting shutdown...
120612 21:37:32 InnoDB: Shutdown completed; log sequence number 0 32458868
120612 21:37:32 [Note] /usr/sbin/mysqld: Shutdown complete
120612 21:37:32 [Note] Plugin 'FEDERATED' is disabled.
120612 21:37:33 InnoDB: Started; log sequence number 0 32458868
120612 21:37:33 [Note] Event Scheduler: Loaded 0 events
120612 21:37:33 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12.10' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
120612 21:46:40 [Note] /usr/sbin/mysqld: Normal shutdown
120612 21:46:40 [Note] Event Scheduler: Purging the queue. 0 events
120612 21:46:40 InnoDB: Starting shutdown...
120612 21:46:42 InnoDB: Shutdown completed; log sequence number 0 32460108
120612 21:46:42 [Note] /usr/sbin/mysqld: Shutdown complete
120612 21:46:42 [Note] Plugin 'FEDERATED' is disabled.
120612 21:46:43 InnoDB: Started; log sequence number 0 32460108
120612 21:46:43 [Note] Event Scheduler: Loaded 0 events
120612 21:46:43 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12.10' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) |
Dit lijken mij geen errors die ontstaan zijn tijden het bezoeken van de pagina's maar tijdens het herstarten van het mysql proces aan de tijd te zien.
Als ik google op "[Note] Plugin 'FEDERATED' is disabled" kom op problemen uit waarbij er een fout in myslq.cnf file zou kunnen zitten. Echter zie ik er niets verkeerd in zo 1 2 3:
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
| # 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]
local-infile=0
#
# * Basic Settings
#
# * IMPORTANT
# If you make changes to these settings and your system uses apparmor, you may
# also need to also adjust /etc/apparmor.d/usr.sbin.mysqld.
#
user = mysql
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
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
log_error = /var/log/mysql/error.log
# 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!
#
# * 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/ |
Het zou ook kunnen zijn dat de mysql database waar ik het mee ben begonnen (lokaal) een andere versie is vergeleken met de mysql database op de server maar dat is ook niet het geval. Beide versie 5.1 en ik heb ook al geprobeerd een database via de VPS te maken dmv schone install wordpress op een leeg domein. Dus dat kan het ook niet zijn.
edit:
slow log aangezet maar zo te zien is alleen het log bestand aangemaakt en is er geen query in geplaatst
code:
1
2
3
| /usr/sbin/mysqld, Version: 5.1.41-3ubuntu12.10-log ((Ubuntu)). started with:
Tcp port: 3306 Unix socket: /var/run/mysqld/mysqld.sock
Time Id Command Argument |
edit 2:
long_query_time op 5 seconden gezet maar ook dan staat er niks in het log bestand
edit 3:
Zojuist nog eens slow-query log bestand bekeken en toen kwam ik dit tegen. Ik heb een apt-get update uitgevoerd en server restart.
code:
1
2
3
4
5
6
7
8
9
10
11
12
| # Time: 120613 13:46:42
# User@Host: debian-sys-maint[debian-sys-maint] @ localhost []
# Query_time: 6.569856 Lock_time: 0.001626 Rows_sent: 253 Rows_examined: 505
SET timestamp=1339588002;
select concat('select count(*) into @discard from `',
TABLE_SCHEMA, '`.`', TABLE_NAME, '`')
from information_schema.TABLES where ENGINE='MyISAM';
# Time: 120613 13:46:52
# User@Host: debian-sys-maint[debian-sys-maint] @ localhost []
# Query_time: 6.732629 Lock_time: 0.000794 Rows_sent: 0 Rows_examined: 505
SET timestamp=1339588012;
select count(*) into @discard from `information_schema`.`PARTITIONS`; |
Google resultaten laat zien dat debian-sys-maint zorgt voor afsluien en opstarten van mysql?
[
Voor 8% gewijzigd door
Nyxium op 13-06-2012 14:01
]