Cannot start Drizzle on an alternate port using init script

[m00dawg]

I am unable to start Drizzle when trying to specify a MySQL port via the config file:

root@mcp:~# cat /etc/drizzle/drizzled.cnf
datadir = /var/lib/drizzle
pid-file = /var/lib/drizzle/mcp.pid

#mysql-protocol.port=3307
[mysql-protocol]
port = 3307
bind-address = 127.0.0.1

root@mcp:~# /etc/init.d/drizzle-server start
 * Starting Drizzle database server drizzled
   ...done.
root@mcp:~# /etc/init.d/drizzle-server status
 * Drizzle is stopped.
root@mcp:~# tail -5 /var/log/drizzle/drizzled.log
Listening on :::4427
bind() failed with errno: 98
Do you already have another drizzled running?
Error getting file descriptorsAborting
/usr/sbin/drizzled: Shutdown complete

Starting drizzle up manually using the config file also fails:

root@mcp:~# drizzled --defaults-file=/etc/drizzle/drizzled.cnf
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins.
101004 19:30:44 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 180594
101004 19:30:44 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 180840
InnoDB: Last MySQL binlog file position 0 0, file name UNUSED
101004 19:30:44 InnoDB Plugin 1.0.4 started; log sequence number 180840
Listening on 0.0.0.0:4427
Listening on :::4427
bind() failed with errno: 98
Do you already have another drizzled running?
Error getting file descriptorsAborting
drizzled: Shutdown complete

Nothing is listening on 3307 currently:

root@mcp:~# netstat -nptl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2401/sshd
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 11367/apache2
tcp 0 0 0.0.0.0:3784 0.0.0.0:* LISTEN 10118/ventrilo_srv
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 27885/mysqld
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 11367/apache2
tcp 0 0 0.0.0.0:3312 0.0.0.0:* LISTEN 2620/searchd
tcp6 0 0 :::22 :::* LISTEN 2401/sshd

This is on Lucid (10.04) using nightly built PPA DEBs:

root@mcp:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Codename: lucid
root@mcp:~# cat /etc/apt/sources.list.d/drizzle.list
#deb http://ppa.launchpad.net/drizzle-developers/ppa/ubuntu lucid main
deb http://ppa.launchpad.net/drizzle-developers/trunk/ubuntu lucid main

[Monty Taylor (mordred)]

This _should_ be fixed in the current trunk - but I need to figure out how to add a test for it to the test system. Turns out there was a bug in boost in lucid.

Can you try it out and see if it's working now?

[Monty Taylor (mordred)]

Oh. Actually - wait. Don't bother - we're ALSO having issues uploading new trunk packages to the trunk PPA due to a launchpad bug - I'll ping you when that's fixed.

[Patrick Crews (patrick-crews)]

As far as a test goes, test-run doesn't provide a clean way to test this in
the main server, *but* one could possibly start another version of the
server within the test using an init script argument, then query that server
for certain expected variables?

Not ideal, but it seemed like a possibility.

On Thu, Oct 7, 2010 at 9:47 PM, Monty Taylor <email address hidden> wrote:

> Oh. Actually - wait. Don't bother - we're ALSO having issues uploading
> new trunk packages to the trunk PPA due to a launchpad bug - I'll ping
> you when that's fixed.
>
> --
> Cannot start Drizzle on an alternate port using init script
> https://bugs.launchpad.net/bugs/654781
> You received this bug notification because you are a member of Drizzle-
> developers, which is subscribed to Drizzle.
>
> Status in A Lightweight SQL Database for Cloud Infrastructure and Web
> Applications: New
> Status in Drizzle elliott series: Confirmed
>
> Bug description:
> I am unable to start Drizzle when trying to specify a MySQL port via the
> config file:
>
> root@mcp:~# cat /etc/drizzle/drizzled.cnf
> datadir = /var/lib/drizzle
> pid-file = /var/lib/drizzle/mcp.pid
>
> #mysql-protocol.port=3307
> [mysql-protocol]
> port = 3307
> bind-address = 127.0.0.1
>
> root@mcp:~# /etc/init.d/drizzle-server start
> * Starting Drizzle database server drizzled
> ...done.
> root@mcp:~# /etc/init.d/drizzle-server status
> * Drizzle is stopped.
> root@mcp:~# tail -5 /var/log/drizzle/drizzled.log
> Listening on :::4427
> bind() failed with errno: 98
> Do you already have another drizzled running?
> Error getting file descriptorsAborting
> /usr/sbin/drizzled: Shutdown complete
>
> Starting drizzle up manually using the config file also fails:
>
> root@mcp:~# drizzled --defaults-file=/etc/drizzle/drizzled.cnf
> InnoDB: The InnoDB memory heap is disabled
> InnoDB: Mutexes and rw_locks use GCC atomic builtins.
> 101004 19:30:44 InnoDB: highest supported file format is Barracuda.
> InnoDB: Log scan progressed past the checkpoint lsn 180594
> 101004 19:30:44 InnoDB: Database was not shut down normally!
> InnoDB: Starting crash recovery.
> InnoDB: Reading tablespace information from the .ibd files...
> InnoDB: Restoring possible half-written data pages from the doublewrite
> InnoDB: buffer...
> InnoDB: Doing recovery: scanned up to log sequence number 180840
> InnoDB: Last MySQL binlog file position 0 0, file name UNUSED
> 101004 19:30:44 InnoDB Plugin 1.0.4 started; log sequence number 180840
> Listening on 0.0.0.0:4427
> Listening on :::4427
> bind() failed with errno: 98
> Do you already have another drizzled running?
> Error getting file descriptorsAborting
> drizzled: Shutdown complete
>
> Nothing is listening on 3307 currently:
>
> root@mcp:~# netstat -nptl
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address Foreign Address State
> PID/Program name
> tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
> 2401/sshd
> tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN
> 11367/apache2
> tcp 0 0 0.0.0.0:3784 0.0.0.0:* LISTEN...

[m00dawg (tim-moocowproductions)]

Ah doh! Sounds good. Just lemmie know and I'll be sure to give it a spin!

On Oct 7, 2010, at 8:47 PM, Monty Taylor wrote:

> Oh. Actually - wait. Don't bother - we're ALSO having issues uploading
> new trunk packages to the trunk PPA due to a launchpad bug - I'll ping
> you when that's fixed.
>
> --
> Cannot start Drizzle on an alternate port using init script
> https://bugs.launchpad.net/bugs/654781
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications: New
> Status in Drizzle elliott series: Confirmed
>
> Bug description:
> I am unable to start Drizzle when trying to specify a MySQL port via the config file:
>
> root@mcp:~# cat /etc/drizzle/drizzled.cnf
> datadir = /var/lib/drizzle
> pid-file = /var/lib/drizzle/mcp.pid
>
> #mysql-protocol.port=3307
> [mysql-protocol]
> port = 3307
> bind-address = 127.0.0.1
>
> root@mcp:~# /etc/init.d/drizzle-server start
> * Starting Drizzle database server drizzled
> ...done.
> root@mcp:~# /etc/init.d/drizzle-server status
> * Drizzle is stopped.
> root@mcp:~# tail -5 /var/log/drizzle/drizzled.log
> Listening on :::4427
> bind() failed with errno: 98
> Do you already have another drizzled running?
> Error getting file descriptorsAborting
> /usr/sbin/drizzled: Shutdown complete
>
> Starting drizzle up manually using the config file also fails:
>
> root@mcp:~# drizzled --defaults-file=/etc/drizzle/drizzled.cnf
> InnoDB: The InnoDB memory heap is disabled
> InnoDB: Mutexes and rw_locks use GCC atomic builtins.
> 101004 19:30:44 InnoDB: highest supported file format is Barracuda.
> InnoDB: Log scan progressed past the checkpoint lsn 180594
> 101004 19:30:44 InnoDB: Database was not shut down normally!
> InnoDB: Starting crash recovery.
> InnoDB: Reading tablespace information from the .ibd files...
> InnoDB: Restoring possible half-written data pages from the doublewrite
> InnoDB: buffer...
> InnoDB: Doing recovery: scanned up to log sequence number 180840
> InnoDB: Last MySQL binlog file position 0 0, file name UNUSED
> 101004 19:30:44 InnoDB Plugin 1.0.4 started; log sequence number 180840
> Listening on 0.0.0.0:4427
> Listening on :::4427
> bind() failed with errno: 98
> Do you already have another drizzled running?
> Error getting file descriptorsAborting
> drizzled: Shutdown complete
>
> Nothing is listening on 3307 currently:
>
> root@mcp:~# netstat -nptl
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
> tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2401/sshd
> tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 11367/apache2
> tcp 0 0 0.0.0.0:3784 0.0.0.0:* LISTEN 10118/ventrilo_srv
> tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 27885/mysqld
> tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 11367/apache2
> tcp 0 0 0.0.0.0:3312 0.0.0...