From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id BCDD813838B for ; Tue, 14 Oct 2014 22:26:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 42D20E08EB; Tue, 14 Oct 2014 22:25:58 +0000 (UTC) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C5873E08C5 for ; Tue, 14 Oct 2014 22:25:56 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id h11so8124938wiw.1 for ; Tue, 14 Oct 2014 15:25:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=6mgoA6ikVxzkjAQBxCIA8EKhCXxEHMlgIFAowmXZcvU=; b=knjo3x064nd+LPGF580UEx+WyAi2gbbpZjzYHEFKagUyke2s3al3z3tGlUdEvmUpIF uahmNfSuP3rH8ZLhn/ywbbGpg10KVdcf7lnpLMk7XQsESztskKNDPLp9sj7gQ5zmOMlz ld6VZKWkMWZdTry5rYjUiy8VphD6EauUngJ1H+i5q63GjClYiexpEt+bLTx99POP96lo 1VCtmuAJ5R0lilILVEtsU5FAZaE1QYO9b3X6NaHAz5mRDsE/P5L8YNznm38izYgwpN5Y kmKA5FxYw0lBj7kyFQvfa3wXHP5lhtYqmuZkoHBrInXHK6VMztGDe6PVlVBphdzs8sD8 w6cA== X-Received: by 10.194.81.6 with SMTP id v6mr7885834wjx.39.1413325555294; Tue, 14 Oct 2014 15:25:55 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPSA id ic4sm17149588wid.19.2014.10.14.15.25.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 Oct 2014 15:25:54 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] [slightly O/T] mysql problems Date: Tue, 14 Oct 2014 23:25:34 +0100 User-Agent: KMail/1.13.7 (Linux/3.14.14-gentoo; KDE/4.12.5; x86_64; ; ) References: <201410141955.04196.michaelkintzios@gmail.com> <543D8474.6030309@fastmail.co.uk> In-Reply-To: <543D8474.6030309@fastmail.co.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7177779.62bnRkgNdT"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201410142325.35604.michaelkintzios@gmail.com> X-Archives-Salt: cbf757d6-ad88-4375-9ed8-c6e4f053ad25 X-Archives-Hash: 8c681da249378dead325c2b9f89116b7 --nextPart7177779.62bnRkgNdT Content-Type: multipart/mixed; boundary="Boundary-01=_fLaPUh20cIEb0eC" Content-Transfer-Encoding: 7bit --Boundary-01=_fLaPUh20cIEb0eC Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 14 Oct 2014 21:15:48 Kerin Millar wrote: > On 14/10/2014 19:54, Mick wrote: > > # Uncomment this to get FEDERATED engine support > > #plugin-load=3Dfederated=3Dha_federated.so > > loose-federated > >=20 > > As far as I recall this is a default setting. Should I change it? >=20 > No. I presume that you are not actively using the federated storage > engine but let's put that aside because there is more to this error than > meets the eye. >=20 > Check your MySQL error log and look for any anomalies from the point at > which MySQL is started. If you don't know where the log file is, execute > "SELECT @@log_error". 141014 19:41:37 [Warning] No argument was provided to --log-bin, and --log- bin-index was not used; so replication may break when this MySQL server act= s=20 as a master and has his hostname changed!! Please use '--log-bin=3Dmysqld-b= in'=20 to avoid this problem. 141014 19:41:37 InnoDB: The InnoDB memory heap is disabled 141014 19:41:37 InnoDB: Mutexes and rw_locks use GCC atomic builtins 141014 19:41:37 InnoDB: Compressed tables use zlib 1.2.8 141014 19:41:37 InnoDB: Using Linux native AIO 141014 19:41:37 InnoDB: Initializing buffer pool, size =3D 16.0M 141014 19:41:37 InnoDB: Completed initialization of buffer pool 141014 19:41:37 InnoDB: highest supported file format is Barracuda. 141014 19:41:37 InnoDB: Operating system error number 2 in a file operatio= n. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. 141014 19:41:37 InnoDB: Error: trying to open a table, but could not InnoDB: open the tablespace file './website1@002dnew/actions.ibd'! InnoDB: Have you moved InnoDB .ibd files around without using the InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? InnoDB: It is also possible that this is a temporary table #sql..., InnoDB: and MySQL removed the .ibd file for this. InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datad= ict.html > I have several questions: >=20 > * Have you started MySQL with skip-grant-tables in effect? Not knowingly. How do I find out? > * Have you upgraded MySQL recently without going through the > documented upgrade procedure? [1] I'm still on mysql-5.5.39 Installed versions: 5.5.39(16:42:22 08/09/14)(community perl ssl - bindist -cluster -debug -embedded -extraengine -jemalloc -latin1 -max-idx-1= 28=20 =2Dminimal -profiling -selinux -static -static-libs -systemtap -tcmalloc -t= est) > * Have you copied files into MySQL's data directory that originated > from a different version of MySQL? No, not manually. > * Have you otherwise removed or modified files in the data directory? Not as far as I know. I have suspicions of fs corruption though (it's been= =20 running out of space lately and I haven't yet found out why). > > 2. A particular database which I have imported locally from a live site > > gives me loads of this: > The wording here suggests a broader context that would be relevant. > Please be specific as to the circumstances. What procedure did you > employ in order to migrate and import the database? What do you mean by > "live site"? Which versions of MySQL are running at both source and > destination? How are they configured? mysql -u webadmin -h localhost -p website_test < website1_20141014.sql The server is on 5.5.36. website1 is the database name of the live site, and website_test is the loc= al=20 development database. The server is a shared server, so I'm getting its vanilla configuration wit= h=20 no choice on the matter. The local configuration is attached. > > Is this some error imported from the live site, or is it due to somethi= ng > > being wrong locally? >=20 > MySQL believes that an InnoDB table named > "webform_validation_rule_components" presently exists in a database > named "website1@002dnew" but the corresponding tablespace file does not > exist, relative to the MySQL datadir. The reason for this may become > clear if you answer the questions posed above. I'll check this when I get a minute and report back. Right now the machine is locked up - no space left on the root partition fo= r=20 some obscure reason. I need to start clearing stuff out. Thanks for your help! =2D-=20 Regards, Mick --Boundary-01=_fLaPUh20cIEb0eC Content-Type: text/plain; charset="UTF-8"; name="my.cnf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="my.cnf" # /etc/mysql/my.cnf: The global mysql configuration file. # $Header: /var/cvsroot/gentoo-x86/dev-db/mysql/files/my.cnf-5.5,v 1.3 2014= /04/25 00:43:46 jmbsvicetto Exp $ # The following options will be passed to all MySQL clients [client] #password =3D your_password port =3D 3306 socket =3D /var/run/mysqld/mysqld.= sock [mysql] character-sets-dir=3D/usr/share/mysql/charsets default-character-set=3Dutf8 [mysqladmin] character-sets-dir=3D/usr/share/mysql/charsets default-character-set=3Dutf8 [mysqlcheck] character-sets-dir=3D/usr/share/mysql/charsets default-character-set=3Dutf8 [mysqldump] character-sets-dir=3D/usr/share/mysql/charsets default-character-set=3Dutf8 [mysqlimport] character-sets-dir=3D/usr/share/mysql/charsets default-character-set=3Dutf8 [mysqlshow] character-sets-dir=3D/usr/share/mysql/charsets default-character-set=3Dutf8 [myisamchk] character-sets-dir=3D/usr/share/mysql/charsets [myisampack] character-sets-dir=3D/usr/share/mysql/charsets # use [safe_mysqld] with mysql-3 [mysqld_safe] err-log =3D /var/log/mysql/mysql.err # add a section [mysqld-4.1] or [mysqld-5.0] for specific configurations [mysqld] character-set-server =3D utf8 user =3D mysql port =3D 3306 socket =3D /var/run/mysqld/mysqld.= sock pid-file =3D /var/run/mysqld/mysqld.= pid log-error =3D /var/log/mysql/mysqld.e= rr basedir =3D /usr datadir =3D /var/lib/mysql skip-external-locking key_buffer_size =3D 16M max_allowed_packet =3D 16M table_open_cache =3D 64 sort_buffer_size =3D 512K net_buffer_length =3D 8K read_buffer_size =3D 256K read_rnd_buffer_size =3D 512K myisam_sort_buffer_size =3D 8M lc_messages_dir =3D /usr/share/mysql expire_logs_days =3D 90 #Set this to your desired error message language lc_messages =3D en_US # security: # using "localhost" in connects uses sockets by default # skip-networking bind-address =3D 127.0.0.1 log-bin server-id =3D 1 # point the following paths to different dedicated disks tmpdir =3D /tmp/ #log-update =3D /path-to-dedicated-directory/ho= stname # you need the debug USE flag enabled to use the following directives, # if needed, uncomment them, start the server and issue=20 # #tail -f /tmp/mysqld.sql /tmp/mysqld.trace # this will show you *exactly* what's happening in your server ;) #log =3D /tmp/mysqld.sql #gdb #debug =3D d:t:i:o,/tmp/mysqld.tra= ce #one-thread # the following is the InnoDB configuration # if you wish to disable innodb instead # uncomment just the next line #skip-innodb # # the rest of the innodb config follows: # don't eat too much memory, we're trying to be safe on 64Mb boxes # you might want to bump this up a bit on boxes with more RAM innodb_buffer_pool_size =3D 16M # this is the default, increase it if you have lots of tables innodb_additional_mem_pool_size =3D 2M # # i'd like to use /var/lib/mysql/innodb, but that is seen as a database :-( # and upstream wants things to be under /var/lib/mysql/, so that's the route # we have to take for the moment #innodb_data_home_dir =3D /var/lib/mysql/ #innodb_log_arch_dir =3D /var/lib/mysql/ #innodb_log_group_home_dir =3D /var/lib/mysql/ # you may wish to change this size to be more suitable for your system # the max is there to avoid run-away growth on your machine innodb_data_file_path =3D ibdata1:10M:autoextend:max:128M # we keep this at around 25% of of innodb_buffer_pool_size # sensible values range from 1MB to (1/innodb_log_files_in_group*innodb_buf= fer_pool_size) innodb_log_file_size =3D 5M # this is the default, increase it if you have very large transactions goin= g on innodb_log_buffer_size =3D 8M # this is the default and won't hurt you # you shouldn't need to tweak it innodb_log_files_in_group=3D2 # see the innodb config docs, the other options are not always safe innodb_flush_log_at_trx_commit =3D 1 innodb_lock_wait_timeout =3D 50 innodb_file_per_table # Uncomment this to get FEDERATED engine support #plugin-load=3Dfederated=3Dha_federated.so loose-federated [mysqldump] quick max_allowed_packet =3D 16M [mysql] # uncomment the next directive if you are not familiar with SQL #safe-updates [isamchk] key_buffer_size =3D 20M sort_buffer_size =3D 20M read_buffer =3D 2M write_buffer =3D 2M [myisamchk] key_buffer_size =3D 20M sort_buffer_size =3D 20M read_buffer_size =3D 2M write_buffer_size =3D 2M [mysqlhotcopy] interactive-timeout --Boundary-01=_fLaPUh20cIEb0eC-- --nextPart7177779.62bnRkgNdT Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJUPaLfAAoJELAdA+zwE4YeNhAH/iRb3x1rICBugx/zc1thKHDS wShAWgDM2VQ5VGnuH+GbTYEXjdi068kJPFbLwfqhPHoeSx75+aBRuhDwx7d/ukwf uihJpbi1X2DarBawopGPvIP4zDVycZq8zREuHvIDsHtT6xh7VJ1WG2111P8KUY/v AXrqKnFCvyaAhzo7fuqjE+JlbtsVNpGCd/c0mzLFsY4LHHx58aXIPHeiTTEsndDD cAIbWDujl4VJpMnuzX9SxP/QzPQkm3MK3ZajdaeLWC+anrEFeTs37u9yPo/Ex6tq QYVIEPZk0WsIbczlsi+VpuITatQk6JGllPbywSHQpbPWSqX9NYbsssfsu/5zuG0= =TffZ -----END PGP SIGNATURE----- --nextPart7177779.62bnRkgNdT--