I can’t get mysql to run. I think it might be due to to a failed upgrade process. Here are the logs etc…
systemctl status mysql.service
mysql.service - LSB: Start the MySQL database server
Loaded: loaded (/etc/init.d/mysql)
Active: failed (Result: exit-code) since Mon, 2013-06-10 14:39:16 BST; 14min ago
Process: 10002 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/mysql.service
Jun 10 14:39:14 tippingpoint mysql[10002]: mysql.time_zone_leap_second OK
Jun 10 14:39:14 tippingpoint mysql[10002]: mysql.time_zone_name OK
Jun 10 14:39:14 tippingpoint mysql[10002]: mysql.time_zone_transition OK
Jun 10 14:39:14 tippingpoint mysql[10002]: mysql.time_zone_transition_type OK
Jun 10 14:39:14 tippingpoint mysql[10002]: mysql.user OK
Jun 10 14:39:14 tippingpoint mysql[10002]: Running 'mysql_fix_privilege_tables'...
Jun 10 14:39:14 tippingpoint mysql[10002]: Running 'mysqlcheck' with connection arguments: '--socket=/var/tmp/mysql....sock'
Jun 10 14:39:14 tippingpoint mysql[10002]: ..failed
Jun 10 14:39:16 tippingpoint systemd[1]: Failed to start LSB: Start the MySQL database server.
Jun 10 14:39:16 tippingpoint systemd[1]: Unit mysql.service entered failed state
/var/log/mysql/mysqld-upgrade.log
Mon Jun 10 14:39:04 BST 2013 - upgrading MySQL...
Will update MySQL now, if you encounter any problems, please read following file:
/usr/share/doc/packages/mysql-community-server_57/README.SuSE
Running protected MySQL...
Upgrading MySQL...
Looking for 'mysql' as: /usr/bin/mysql
Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Running 'mysqlcheck' with connection arguments: '--socket=/var/tmp/mysql-protected.7gFrxo/mysql.sock'
Running 'mysqlcheck' with connection arguments: '--socket=/var/tmp/mysql-protected.7gFrxo/mysql.sock'
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.general_log OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.innodb_index_stats OK
mysql.innodb_table_stats OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.servers OK
mysql.slave_master_info OK
mysql.slave_relay_log_info OK
mysql.slave_worker_info OK
mysql.slow_log OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
Running 'mysql_fix_privilege_tables'...
Running 'mysqlcheck' with connection arguments: '--socket=/var/tmp/mysql-protected.7gFrxo/mysql.sock'
/var/log/mysql/mysqld-upgrade-run.log
130610 14:39:05 mysqld_safe Starting mysqld daemon with databases from /home/mysql
2013-06-10 14:39:05 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2013-06-10 14:39:05 10366 [Note] Plugin 'FEDERATED' is disabled.
2013-06-10 14:39:05 10366 [Note] InnoDB: The InnoDB memory heap is disabled
2013-06-10 14:39:05 10366 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2013-06-10 14:39:05 10366 [Note] InnoDB: Compressed tables use zlib 1.2.7
2013-06-10 14:39:05 10366 [Note] InnoDB: Using Linux native AIO
2013-06-10 14:39:05 10366 [Note] InnoDB: Using CPU crc32 instructions
2013-06-10 14:39:05 10366 [Note] InnoDB: Initializing buffer pool, total size = 1.6G, instances = 8
2013-06-10 14:39:05 10366 [Note] InnoDB: Completed initialization of buffer pool
2013-06-10 14:39:05 10366 [Note] InnoDB: Highest supported file format is Barracuda.
2013-06-10 14:39:05 10366 [Note] InnoDB: Creating shared tablespace for temporary tables
2013-06-10 14:39:05 10366 [Note] InnoDB: Setting file "./ibtmp1" size to 12 MB
2013-06-10 14:39:05 10366 [Note] InnoDB: Database physically writes the file full: wait ...
2013-06-10 14:39:05 10366 [Note] InnoDB: 128 rollback segment(s) are active.
2013-06-10 14:39:05 10366 [Note] InnoDB: Waiting for purge to start
2013-06-10 14:39:05 10366 [Note] InnoDB: 5.7.1 started; log sequence number 487279825
2013-06-10 14:39:05 10366 [Note] RSA private key file not found: /home/mysql//private_key.pem. Some authentication plugins will not work.
2013-06-10 14:39:05 10366 [Note] RSA public key file not found: /home/mysql//public_key.pem. Some authentication plugins will not work.
2013-06-10 14:39:05 10366 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.1-m11' socket: '/var/tmp/mysql-protected.7gFrxo/mysql.sock' port: 0 openSUSE package
2013-06-10 14:39:14 10366 [Note] /usr/sbin/mysqld: Normal shutdown
2013-06-10 14:39:14 10366 [Note] Giving 0 client threads a chance to die gracefully
2013-06-10 14:39:14 10366 [Note] Shutting down slave threads
2013-06-10 14:39:14 10366 [Note] Forcefully disconnecting 0 remaining clients
2013-06-10 14:39:14 10366 [Note] Binlog end
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'partition'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'ARCHIVE'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'BLACKHOLE'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_METRICS'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_CMPMEM'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_CMP'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_LOCKS'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'INNODB_TRX'
2013-06-10 14:39:14 10366 [Note] Shutting down plugin 'InnoDB'
2013-06-10 14:39:14 10366 [Note] InnoDB: FTS optimize thread exiting.
2013-06-10 14:39:14 10366 [Note] InnoDB: Starting shutdown...
2013-06-10 14:39:16 10366 [Note] InnoDB: Shutdown completed; log sequence number 487280829
2013-06-10 14:39:16 10366 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2013-06-10 14:39:16 10366 [Note] Shutting down plugin 'MRG_MYISAM'
2013-06-10 14:39:16 10366 [Note] Shutting down plugin 'MEMORY'
2013-06-10 14:39:16 10366 [Note] Shutting down plugin 'CSV'
2013-06-10 14:39:16 10366 [Note] Shutting down plugin 'MyISAM'
2013-06-10 14:39:16 10366 [Note] Shutting down plugin 'sha256_password'
2013-06-10 14:39:16 10366 [Note] Shutting down plugin 'mysql_old_password'
2013-06-10 14:39:16 10366 [Note] Shutting down plugin 'mysql_native_password'
2013-06-10 14:39:16 10366 [Note] Shutting down plugin 'binlog'
2013-06-10 14:39:16 10366 [Note] /usr/sbin/mysqld: Shutdown complete
130610 14:39:16 mysqld_safe mysqld from pid file /var/tmp/mysql-protected.7gFrxo/mysqld.pid ended
It seems to get to Running ‘mysql_fix_privilege_tables’… and then just stops and shuts down. Very strange I can find anyother errors. I have reinstalled, upgraded and downgraded. Always that same.
I cannot find “mysql_fix_privilege_tables” on the system, its is supposed to be installed?
Oh please, please! Allways start telling whichversion of openSUSE you use. And that should also trigger you to tell those things we can know and that might be of interest to those who try to help you.
Opensuse 12.3 (kernel: 3.7.10-1.11-desktop #1 SMP PREEMPT Thu May 16 20:27:27 UTC 2013)
I have tried installing the following versions of mysql
5.7.1-3.1x86_64
5.6.12-2.1x86_64
5.5.32-2.1x86_64
All fail with either the same of similar problem.
I have also emptied the mysql dir to see if it would rebuild… same problem.
The problem appeared after running an update to the system, which didn’t produce any errors. Now when I try to start it I get output to the upgrade.log and upgrade-run.log (as above). That is all I have to go on. Its very odd.
So I reinstalled from the standard repro and now everything works as normal…
I can’t be sure that there is a problem with the openSUSE BuildService - Database repro as it is possible that I missed something during the previous installs. Anyway, it works now.
Next time, please mention from the very begining that you are deviating from the standard openSUSE release and use the software from some other repo. Please make it as easy as possible for your potential helpers to understand your situation.
mysql_upgrade only upgrades the databases to the new mysql version, not mysql itself.
It is part of the mysql-community-server package and runs automatically when you install/upgrade the package.
On 2013-06-11 00:36, wolfi323 wrote:
>
> Knurpht;2563921 Wrote:
>> AFAICS the OP did not use zypper or Yast, but ran mysql_upgrade.
> He did install mysql with zypper or YaST.
>
> mysql_upgrade only upgrades the databases to the new mysql version, not
> mysql itself.
> It is part of the mysql-community-server package and runs automatically
> when you install/upgrade the package.
You upgrade the entire system, or just mysql, then you have to run that
to update the databases themselves.
If he did upgrade the entire system and how, or just mysql, is important
to know.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
No. The important thing to know is if he installed mysql from openSUSE rpms or from elsewhere.
mysql_upgrade is called automatically by openSUSE’s mysql startup script. (have a look at /usr/sbin/rcmysql if you don’t believe me )
And the OP already said, that he had installed mysql from the openSUSE BuildService - Database repo, which didn’t work for him.
The packages from the Oss repo do work for him now.
So IMHO the only question that remains here is, if the packages from that repo have a problem. (maybe the upgrade process doesn’t work reliably?)
> So IMHO the only question that remains here is, if the packages from
> that repo have a problem. (maybe the upgrade process doesn’t work
> reliably?)
Which is why I want to know the details of that upgrade process
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
The problem was caused during a zypper up process, i.e. it was just part of my normal update routine and I wasn’t specifically trying to upgrade mysql. Another server needs updating that is almost identically configured I will report if that has issues.
What I found strange was that there wasn’t much in the way of errors to go on. The mysql server came up during the upgrade process (as indicated in logs) and then just shutdown before it was completed. Not see that before, maybe I should have upped the debug level to see if that would have hinted as to what was going on.
try “mysql_safe” or “mysqld_safe” this also happened to me and I am in the process of finding out whats happened… I would advise that you check your email client if you use kmail as my kmail doesnt work now either I was just checking the forums to see if anyone had the same issue and it looks like they do…
That’s a different problem. The current akonadi version (to be more precise, the included mysql config file) is incompatible with the latest mysql versions. But this is already fixed upstream. See https://bugs.kde.org/show_bug.cgi?id=319016
To get your Akonadi/Kmail running again, edit ~/.local/share/akonadi/mysql.conf and replace “table_cache” with “table_open_cache”.
Hi Wolfi, you are officially a star.
However I use webmin to start and stop services & for some reason mysqld wouldnt start so i checked the error code that was given and did a bit of googles your friend… at which point I found mysqld_safe. this started mysql
at the moment It doesnt bother me it just means I need to ssh into the machine to manually start mysql when the machine is rebooted…
Many thanks for your very quick and reply and sorry prgarnett for jumping on your thread…
Well, akonadi by default starts its own private mysql server, that’s why it has its own config (but you can configure it to use an existing one as well, even on a remote host).
So is akonadi working for you now? Then your problem with the global mysql server must be related to the config…
Or was your akonadi problem on a different machine?
Ssh into the machine (as root) and try to start mysql with “systemctl start mysql.service”. What output do you get?
What’s the output of “systemctl status mysql.service” afterwards?
Oh, and btw. on openSUSE the standard mysql init script DOES start the server with “mysqld_safe”.
So I guess “systemctl start mysql.service” will work for you anyway. That would be a bug/incompatibility in webmin then.
You can automatically run mysqld on boot by executing “systemctl enable mysql.service”.
So apparently there IS a problem with the mysql packages in server:database and therefore also in Factory.
(server:database is the devel project for mysql in Factory)
)