MySQL-Plugin: mysqld is not starting

Hi guys!

Since yesterday I got a problem with the MySQL-Plugin: mysqld is not starting automatically. Syslog is available via Pastebin.

Interesting part would be:

Sep  1 16:07:16 mediaserver mysqld: 140901 16:07:16 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address
Sep  1 16:07:16 mediaserver mysqld: 140901 16:07:16 [ERROR] Do you already have another mysqld server running on port: 3306 ?
Sep  1 16:07:16 mediaserver mysqld: 140901 16:07:16 [ERROR] Aborting

So I connected via SSH and typed in: mysqld - now MySQL is running.

I can't crosscheck it at this time. Maybe a nother MySQL-Server serving the needs of an OwnCloud-Installation (VM on PC). OwnCloud was running, when I was booting the mediaserver.

Question:
If it's my other MySQL-Server (who's just running temporarily) - can I change my port-number to a higher one and just change it in OMV-MySQL-Plugin, Autoshutdown and of course in XBMCs "advancedsettings.xml". Or did I miss something? Which port-number would you recommend?

I've to move OwnCloud too. But it's never a good idea to do many big things in just a tiny time-space. So let me first get a solution to this problem please. Don't make new once!

I don't want to move OwnCloud in the near future - because there is no need to hurry.

But guys:

Zitat

Question:
If it's my other MySQL-Server (who's just running temporarily) - can I change my port-number to a higher one and just change it in OMV-MySQL-Plugin, Autoshutdown and of course in XBMCs "advancedsettings.xml". Or did I miss something? Which port-number would you recommend?

Would someone please answer my Questions?

It was not a 2nd MySQL-Server. Just a second ago I started OMV - and MySQL was not started. My other PC is powered down, so it could not be my 2nd PC. So I started once again manually:

root@mediaserver:~# mysqld &
[1] 3437
root@mediaserver:~# 140902 15:34:49 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
140902 15:34:49 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140902 15:34:49 [Note] Plugin 'FEDERATED' is disabled.
140902 15:34:49 InnoDB: The InnoDB memory heap is disabled
140902 15:34:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140902 15:34:49 InnoDB: Compressed tables use zlib 1.2.7
140902 15:34:49 InnoDB: Using Linux native AIO
140902 15:34:49 InnoDB: Initializing buffer pool, size = 128.0M
140902 15:34:49 InnoDB: Completed initialization of buffer pool
140902 15:34:49 InnoDB: highest supported file format is Barracuda.
140902 15:34:49  InnoDB: Waiting for the background threads to start
140902 15:34:50 InnoDB: 5.5.38 started; log sequence number 13474005
140902 15:34:50 [Note] Server hostname (bind-address): '192.168.178.20'; port: 3306
140902 15:34:50 [Note]   - '192.168.178.20' resolves to '192.168.178.20';
140902 15:34:50 [Note] Server socket created on IP: '192.168.178.20'.
140902 15:34:50 [Note] Event Scheduler: Loaded 0 events
140902 15:34:50 [Note] mysqld: ready for connections.
Version: '5.5.38-0+wheezy1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)

Ideas where to look at? Can OMV run two instances in one Network???

Of course. Here you go.

Kodi-(aka. XMBC)-Wiki says, that you've to change that address to a static one. So my Mediaserver is connected via DHCP, but DHCP is always using 192.168.178.20 for my mediaserver. And so I set this to MySQL and, as said in the next Wiki-Article, the advanced.xml.

I'll give 0.0.0.0 a try tomorrow.
But did this could be a solution to my startup-problem? If yes: How??

It works. But can you explain this?

So, you can't...

You're welcome to check them. Could be a Bug.