Crash after shutdown/restart

2014-01-14 Thread Jørn Dahl-Stamnes
Hello,

Got a test server with version 5.5.20. I wanted to unmount/mount the disk 
where the innodb files was located, so I did a shutdown followed by unmount, 
then a mount before I tried to start the MySQL server. But it did not work as 
shown in the log below.

I wanted to unmount the disk since I wanted to change the 'defaults' 
in /etc/fstab with 
'defaults,noatime,data=writeback,barrier=0,nobh,errors=remount-ro'.

What could cause this? Guess I have to recreate the files and start all over 
again?

# Older message from the error file showing the version.
Version: '5.5.20-log'  socket: '/tmp/mysql.sock'  port: 3306  Source 
distribution

# Shutdown messages
140114 18:14:53 [Note] Event Scheduler: Purging the queue. 0 events
140114 18:14:53  InnoDB: Starting shutdown...
140114 18:17:58  InnoDB: Shutdown completed; log sequence number 2230197670580
140114 18:17:58 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete

# Restart after umount/mount.
140114 18:17:59 mysqld_safe mysqld from pid 
file /usr/local/mysql/data/hostname.pid ended
140114 18:20:05 mysqld_safe Starting mysqld daemon with databases 
from /usr/local/mysql/data
140114 18:20:05 InnoDB: The InnoDB memory heap is disabled
140114 18:20:05 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140114 18:20:05 InnoDB: Compressed tables use zlib 1.2.5
140114 18:20:05 InnoDB: Initializing buffer pool, size = 25.0G
140114 18:20:08 InnoDB: Completed initialization of buffer pool
140114 18:20:08 InnoDB: Error: data file /data/mysql/data/ibdata3 uses page 
size 1024,
140114 18:20:08 InnoDB: but the only supported page size in this release 
is=16384
140114 18:20:08 InnoDB: Could not open or create data files.
140114 18:20:08 InnoDB: If you tried to add new data files, and it failed 
here,
140114 18:20:08 InnoDB: you should now edit innodb_data_file_path in my.cnf 
back
140114 18:20:08 InnoDB: to what it was, and remove the new ibdata files InnoDB 
created
140114 18:20:08 InnoDB: in this failed attempt. InnoDB only wrote those files 
full of
140114 18:20:08 InnoDB: zeros, but did not yet use them in any way. But be 
careful: do not
140114 18:20:08 InnoDB: remove old data files which contain your precious 
data!
140114 18:20:08 [ERROR] Plugin 'InnoDB' init function returned error.
140114 18:20:08 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE 
failed.
140114 18:20:08 [ERROR] Unknown/unsupported storage engine: InnoDB
140114 18:20:08 [ERROR] Aborting

-- 
Jørn Dahl-Stamnes
homepage: http://photo.dahl-stamnes.net/

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



Re: Access denied for user 'root'@'localhost' (using password: YES) on mysql admin

2014-01-14 Thread Érico
 yes it is ...

  also , the eclipse is also local ...

  in both ... mysql-admin php application , plus inside eclispe plugin ...

  same behavior in both


2014/1/13 Reindl Harald h.rei...@thelounge.net

 i doubt that the webserver is running on the same
 machine as your mysql command shell

 Am 13.01.2014 23:59, schrieb Érico:
  true
 
  but please check this out :
 
  mysql Select user, host, password from mysql.user;
 
 +--+--+---+
  | user | host | password
  |
 
 +--+--+---+
  | root | localhost|
 *E85DC00A0137C6171923BE35EDD809573FB3AB4F |
  | root | ericomtxmacbookpro.local |
 *E85DC00A0137C6171923BE35EDD809573FB3AB4F |
  | root | 127.0.0.1|
 *E85DC00A0137C6171923BE35EDD809573FB3AB4F |
  | root | ::1  |
   |
  |  | ericomtxmacbookpro.local |
 *E85DC00A0137C6171923BE35EDD809573FB3AB4F |
 
 +--+--+---+
  5 rows in set (0.00 sec)
 
  all passwords are filled in the db ...
 
  also ... I can connect through command line
 
  what I can't do is :
  1. connect or even ping inside eclipse using jconnector
 
  2. connect from a php app (mysql adim) with or with out pwd ...
  providing the error
 
 
Access denied for user 'root'@'localhost' (using password: YES)
 
 
Access denied for user 'root'@'localhost' (using password: NO)
 
 
  2.1 when I use 127.0.0.1 on mysql admin url ... I get a connection closed
 
  so ... my point is :
 
  in both cases  when using 127.0.0.1 or localhost ...
 
  can the OS be blocking the connection ?
 
  if so , how could I check this ?
 
  Regards
  Érico
 
 
  2014/1/13 Reindl Harald h.rei...@thelounge.net mailto:
 h.rei...@thelounge.net
 
  WTF - we are talking about *database connections* and *not*
 http-URL's
  the webserver is only the *messenger*
 
  Am 13.01.2014 18:54, schrieb Érico:
   using both urls I get the same error :
  
   http://localhost/mysql/index.php
   http://127.0.0.1/mysql/index.php
  
   in 127.0.0.1... after I submit the index.php ... it redirects to
 localhost
   too ..
  
   2014/1/13 Reindl Harald h.rei...@thelounge.net mailto:
 h.rei...@thelounge.net
  
  
  
   Am 13.01.2014 18:28, schrieb Érico:
   ericomtxmacbookpro:bin ericomtx$ ./mysql -u root -p mysql-admin
   Enter password:
   Welcome to the MySQL monitor.  Commands end with ; or \g.
   Your MySQL connection id is 31
   Server version: 5.6.15 MySQL Community Server (GPL)
  
   but in the browser I get the error :
  
   Access denied for user 'root'@'localhost' (using password: YES)
  
   I can't find any information in error log and access log
  
   is there any command parameter that I should use when starting
 mysql so
   this doesn't happen?
  
   are you using localhost or 127.0.0.1 in the web-application
   root@localhost != root@127.0.0.1 mailto:root@127.0.0.1 =
 different users
  
   localhost: Unix-Socket
   127.0.0.1 http://127.0.0.1: TCP
 
 

 --

 Reindl Harald
 the lounge interactive design GmbH
 A-1060 Vienna, Hofmühlgasse 17
 CTO / CISO / Software-Development
 m: +43 (676) 40 221 40, p: +43 (1) 595 3999 33
 icq: 154546673, http://www.thelounge.net/

 http://www.thelounge.net/signature.asc.what.htm




Re: Crash after shutdown/restart

2014-01-14 Thread Jesper Wisborg Krogh

Hi Jørn,

On 15/01/2014 04:36, Jørn Dahl-Stamnes wrote:

140114 18:20:08 InnoDB: Error: data file /data/mysql/data/ibdata3 uses page
size 1024,
140114 18:20:08 InnoDB: but the only supported page size in this release
is=16384
140114 18:20:08 InnoDB: Could not open or create data files.


That error is typical for bug http://bugs.mysql.com/bug.php?id=64160 
which was present in 5.5.20 and 5.5.21 (see also 
http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-22.html).
So try to upgrade to 5.5.22 or later (I'll recommend 5.5.35) and see if 
that fixes the issue.


Best regards,
Jesper Krogh
MySQL Support

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql