| 1 |
On Tuesday 14 Oct 2014 21:15:48 Kerin Millar wrote: |
| 2 |
> On 14/10/2014 19:54, Mick wrote: |
| 3 |
|
| 4 |
> > # Uncomment this to get FEDERATED engine support |
| 5 |
> > #plugin-load=federated=ha_federated.so |
| 6 |
> > loose-federated |
| 7 |
> > |
| 8 |
> > As far as I recall this is a default setting. Should I change it? |
| 9 |
> |
| 10 |
> No. I presume that you are not actively using the federated storage |
| 11 |
> engine but let's put that aside because there is more to this error than |
| 12 |
> meets the eye. |
| 13 |
> |
| 14 |
> Check your MySQL error log and look for any anomalies from the point at |
| 15 |
> which MySQL is started. If you don't know where the log file is, execute |
| 16 |
> "SELECT @@log_error". |
| 17 |
|
| 18 |
|
| 19 |
141014 19:41:37 [Warning] No argument was provided to --log-bin, and --log- |
| 20 |
bin-index was not used; so replication may break when this MySQL server acts |
| 21 |
as a master and has his hostname changed!! Please use '--log-bin=mysqld-bin' |
| 22 |
to avoid this problem. |
| 23 |
141014 19:41:37 InnoDB: The InnoDB memory heap is disabled |
| 24 |
141014 19:41:37 InnoDB: Mutexes and rw_locks use GCC atomic builtins |
| 25 |
141014 19:41:37 InnoDB: Compressed tables use zlib 1.2.8 |
| 26 |
141014 19:41:37 InnoDB: Using Linux native AIO |
| 27 |
141014 19:41:37 InnoDB: Initializing buffer pool, size = 16.0M |
| 28 |
141014 19:41:37 InnoDB: Completed initialization of buffer pool |
| 29 |
141014 19:41:37 InnoDB: highest supported file format is Barracuda. |
| 30 |
141014 19:41:37 InnoDB: Operating system error number 2 in a file operation. |
| 31 |
InnoDB: The error means the system cannot find the path specified. |
| 32 |
InnoDB: If you are installing InnoDB, remember that you must create |
| 33 |
InnoDB: directories yourself, InnoDB does not create them. |
| 34 |
141014 19:41:37 InnoDB: Error: trying to open a table, but could not |
| 35 |
InnoDB: open the tablespace file './website1@002dnew/actions.ibd'! |
| 36 |
InnoDB: Have you moved InnoDB .ibd files around without using the |
| 37 |
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE? |
| 38 |
InnoDB: It is also possible that this is a temporary table #sql..., |
| 39 |
InnoDB: and MySQL removed the .ibd file for this. |
| 40 |
InnoDB: Please refer to |
| 41 |
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html |
| 42 |
|
| 43 |
> I have several questions: |
| 44 |
> |
| 45 |
> * Have you started MySQL with skip-grant-tables in effect? |
| 46 |
|
| 47 |
Not knowingly. How do I find out? |
| 48 |
|
| 49 |
|
| 50 |
> * Have you upgraded MySQL recently without going through the |
| 51 |
> documented upgrade procedure? [1] |
| 52 |
|
| 53 |
I'm still on mysql-5.5.39 |
| 54 |
|
| 55 |
Installed versions: 5.5.39(16:42:22 08/09/14)(community perl ssl - |
| 56 |
bindist -cluster -debug -embedded -extraengine -jemalloc -latin1 -max-idx-128 |
| 57 |
-minimal -profiling -selinux -static -static-libs -systemtap -tcmalloc -test) |
| 58 |
|
| 59 |
|
| 60 |
> * Have you copied files into MySQL's data directory that originated |
| 61 |
> from a different version of MySQL? |
| 62 |
|
| 63 |
No, not manually. |
| 64 |
|
| 65 |
|
| 66 |
> * Have you otherwise removed or modified files in the data directory? |
| 67 |
|
| 68 |
Not as far as I know. I have suspicions of fs corruption though (it's been |
| 69 |
running out of space lately and I haven't yet found out why). |
| 70 |
|
| 71 |
|
| 72 |
> > 2. A particular database which I have imported locally from a live site |
| 73 |
> > gives me loads of this: |
| 74 |
> The wording here suggests a broader context that would be relevant. |
| 75 |
> Please be specific as to the circumstances. What procedure did you |
| 76 |
> employ in order to migrate and import the database? What do you mean by |
| 77 |
> "live site"? Which versions of MySQL are running at both source and |
| 78 |
> destination? How are they configured? |
| 79 |
|
| 80 |
mysql -u webadmin -h localhost -p website_test < website1_20141014.sql |
| 81 |
|
| 82 |
The server is on 5.5.36. |
| 83 |
|
| 84 |
website1 is the database name of the live site, and website_test is the local |
| 85 |
development database. |
| 86 |
|
| 87 |
The server is a shared server, so I'm getting its vanilla configuration with |
| 88 |
no choice on the matter. The local configuration is attached. |
| 89 |
|
| 90 |
|
| 91 |
> > Is this some error imported from the live site, or is it due to something |
| 92 |
> > being wrong locally? |
| 93 |
> |
| 94 |
> MySQL believes that an InnoDB table named |
| 95 |
> "webform_validation_rule_components" presently exists in a database |
| 96 |
> named "website1@002dnew" but the corresponding tablespace file does not |
| 97 |
> exist, relative to the MySQL datadir. The reason for this may become |
| 98 |
> clear if you answer the questions posed above. |
| 99 |
|
| 100 |
I'll check this when I get a minute and report back. |
| 101 |
|
| 102 |
Right now the machine is locked up - no space left on the root partition for |
| 103 |
some obscure reason. I need to start clearing stuff out. |
| 104 |
|
| 105 |
Thanks for your help! |
| 106 |
|
| 107 |
-- |
| 108 |
Regards, |
| 109 |
Mick |
Archives