NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
6.1.5 and MySQL app
Hi, Since upgrading to 6.1.5 mysql will not start. I have no idea why at the mo. Any help appreciated. I'm getting : root@StudioReadyNAS:~# /etc/init.d/mysql start [....] Starting mysql (via s...
Ran journalctl while trying to start up mysql to see what I got. The IP of the machine has changed since the install of the app:
It was on a reserved DHCP address but the DHCP server seems to have started giving the MAC address 192.168.0.30 instead of 192.168.0.23. I'm using both network interfaces in a bonded pair in adaptive load balancing mode.
I rebooted the DHCP server and renewed the DHCP lease and everything is back to normal - but why is the installation tied to the IP that was assigned at the time of installing the app?
One other question: MySQL doesn't seem to start automatically on a reboot - how do I get it to do that?
Jan 02 16:07:52 StudioReadyNAS mysqld_safe[13078]: Starting mysqld daemon with databases from /var/lib/mysql
Jan 02 16:07:52 StudioReadyNAS mysqld[13082]: 140102 16:07:52 [Note] Plugin 'FEDERATED' is disabled.
Jan 02 16:07:52 StudioReadyNAS mysqld[13082]: 140102 16:07:52 InnoDB: The InnoDB memory heap is disabled
Jan 02 16:07:52 StudioReadyNAS mysqld[13082]: 140102 16:07:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jan 02 16:07:52 StudioReadyNAS mysqld[13082]: 140102 16:07:52 InnoDB: Compressed tables use zlib 1.2.7
Jan 02 16:07:52 StudioReadyNAS mysqld[13082]: 140102 16:07:52 InnoDB: Using Linux native AIO
Jan 02 16:07:52 StudioReadyNAS mysqld[13082]: 140102 16:07:52 InnoDB: Initializing buffer pool, size = 128.0M
Jan 02 16:07:52 StudioReadyNAS mysqld[13082]: 140102 16:07:52 InnoDB: Completed initialization of buffer pool
Jan 02 16:07:52 StudioReadyNAS mysqld[13082]: 140102 16:07:52 InnoDB: highest supported file format is Barracuda.
Jan 02 16:07:52 StudioReadyNAS mysqld[13082]: 140102 16:07:52 InnoDB: Waiting for the background threads to start
Jan 02 16:07:53 StudioReadyNAS mysqld[13082]: 140102 16:07:53 InnoDB: 5.5.31 started; log sequence number 58284487
Jan 02 16:07:53 StudioReadyNAS mysqld[13082]: 140102 16:07:53 [Note] Server hostname (bind-address): '192.168.0.... 3306
Jan 02 16:07:53 StudioReadyNAS mysqld[13082]: 140102 16:07:53 [Note] - '192.168.0.23' resolves to '192.168.0.23';
Jan 02 16:07:53 StudioReadyNAS mysqld[13082]: 140102 16:07:53 [Note] Server socket created on IP: '192.168.0.23'.
Jan 02 16:07:53 StudioReadyNAS mysqld[13082]: 140102 16:07:53 [ERROR] Can't start server: Bind on TCP/IP port: C...dress
Jan 02 16:07:53 StudioReadyNAS mysqld[13082]: 140102 16:07:53 [ERROR] Do you already have another mysqld server ...306 ?
Jan 02 16:07:53 StudioReadyNAS mysqld[13082]: 140102 16:07:53 [ERROR] Aborting
Jan 02 16:07:53 StudioReadyNAS mysqld[13082]:
Jan 02 16:07:53 StudioReadyNAS mysqld[13082]: 140102 16:07:53 InnoDB: Starting shutdown...
Jan 02 16:07:54 StudioReadyNAS mysqld[13082]: 140102 16:07:54 InnoDB: Shutdown completed; log sequence number 58284487
Jan 02 16:07:54 StudioReadyNAS mysqld[13082]: 140102 16:07:54 [Note] /usr/sbin/mysqld: Shutdown complete
Jan 02 16:07:54 StudioReadyNAS mysqld[13082]:
Jan 02 16:07:54 StudioReadyNAS mysqld_safe[13129]: mysqld from pid file /var/run/mysqld/mysqld.pid ended
It was on a reserved DHCP address but the DHCP server seems to have started giving the MAC address 192.168.0.30 instead of 192.168.0.23. I'm using both network interfaces in a bonded pair in adaptive load balancing mode.
I rebooted the DHCP server and renewed the DHCP lease and everything is back to normal - but why is the installation tied to the IP that was assigned at the time of installing the app?
One other question: MySQL doesn't seem to start automatically on a reboot - how do I get it to do that?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
