fails on boot when using mysql

[Johnathon]

I am using the package in lucid (2.2.8-2ubuntu4). I have jabberd2 correctly configured to use mysql, and if I load everything myself after the system has booted, jabberd2 works great. However, when jabberd2 tries to load on boot, c2s fails with this message in the log:

[info] loading 'mysql' authreg module
[error] mysql: connection to database failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
[error] failed to initialize auth module 'mysql'

It then never fully loads jabberd2 (only s2s and router are running on boot), until I manually do it.

From what I can tell, mysql (which now in lucid is loading through upstart) hasn't actually started yet. Once the system has fully loaded, I have verified that the mysql socket does indeed exist in that location. It would seem that either jabberd2 needs to be ported to use upstart, or have something set in its init to check for mysql.

[Scott James Remnant (Canonical) (canonical-scott)]

There's no evidence presented here that this is a bug in the Upstart upstream code

[Mystic-Mirage (mystic-mirage)]

I have the same problem. Is there any fix for this?

[Johnathon (outdooricon)]

Currently I have to run "sudo invoke-rc.d jabberd2 start" every time I boot up to get jabber running properly.

[Mystic-Mirage (mystic-mirage)]

I have solve the problem by adding 'sleep 5' to /etc/init.d/jabberd2
file in 'start' section:

...
case "$1" in
   start)
      sleep 5
      echo -n "Starting Jabber services:"
...

2010/11/7 Johnathon <email address hidden>:
> Currently I have to run "sudo invoke-rc.d jabberd2 start" every time I
> boot up to get jabber running properly.
>
> --
> fails on boot when using mysql
> https://bugs.launchpad.net/bugs/574575
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in JabberD XMPP server: New
> Status in NULL Project: Invalid
>
> Bug description:
> I am using the package in lucid (2.2.8-2ubuntu4). I have jabberd2 correctly configured to use mysql, and if I load everything myself after the system has booted, jabberd2 works great. However, when jabberd2 tries to load on boot, c2s fails with this message in the log:
>
> [info] loading 'mysql' authreg module
> [error] mysql: connection to database failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
> [error] failed to initialize auth module 'mysql'
>
> It then never fully loads jabberd2 (only s2s and router are running on boot), until I manually do it.
>
> >From what I can tell, mysql (which now in lucid is loading through upstart) hasn't actually started yet. Once the system has fully loaded, I have verified that the mysql socket does indeed exist in that location. It would seem that either jabberd2 needs to be ported to use upstart, or have something set in its init to check for mysql.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/jabberd2/+bug/574575/+subscribe
>

[Tomasz Sterna (smoku)]

My guess is that jabberd2 startup script needs mysql dependency of type 'uses'.

[Mystic-Mirage (mystic-mirage)]

Right but jabberd2 starts using init scripts and mysql uses upstart mechanism. Proper way is to convert jabberd2 autorun script to upstart.

[Tomasz Sterna (smoku)]

Agreed.
If the package maintainer is going to mess with init script, (s)he can as well convert it to upstart job.