Hi There, since 4.2 we had the problem that kamailio did not start after a reboot. A "/etc/init.d/kamailio restart" fixxed it. The problem is quite obvious: kamailio-loglile => Kamailio can't connect to mysqlDB 13:33:44 Oct 29 13:33:44 kamailio-test /usr/sbin/kamailio[1063]: DEBUG: db_mysql [km_my_con.c:94]: db_mysql_new_connection(): opening connection: mysql://xxxx:xxxx@localhost/routing Oct 29 13:33:44 kamailio-test /usr/sbin/kamailio[1063]: ERROR: db_mysql [km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Oct 29 13:33:44 kamailio-test /usr/sbin/kamailio[1063]: ERROR: <core> [db.c:322]: db_do_init2(): could not add connection to the pool mysql-logfile => ready for connections 13:33:45 141029 13:33:45 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.40-0ubuntu0.12.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) So simply mysql is not ready for connnections when kamailio is ready. I "fixxed" this with a "sleep 5;" in the initfile. But this is not what I call a clean solution. Anyone else had the same problem and fixxed it a little cleaner? Maybe converted the init- to a upstart-script? regards, moritz -- Moritz Graf, M.Sc. Betrieb NGN-Plattform