[rabbitmq-discuss] apt-get install rabbitmq-server for 1.5.4 fails even though it succeeds (/etc/init.d/rabbitmq start doesn't daemonize)

Robert J Berger rberger at ibd.com
Fri May 1 04:20:55 BST 2009

On a fresh install of rabbitmq-server 1.5.4 on ubuntu 8.10 server the  
install fails after trying to start rabbitmq-server. It looks like  
when the install finishes installing and then trys to do an /etc/ 
init.d/rabbitmq-server start, the process starts ok, but it doesn't  
daemonize. Eventually the install times out and says it fails:

Starting rabbitmq-server:
[... long wait... ]
FAILED - check /var/log/rabbitmq/startup_log, _err
invoke-rc.d: initscript rabbitmq-server, action "start" failed.
dpkg: error processing rabbitmq-server (--configure):
subprocess post-installation script returned error exit status 1
ps shows that it is running:

29782 ?        Ssl    0:00 /usr/lib/erlang/erts-5.5.5/bin/beam -W w -K  
true -A30 -- -root /usr/lib/erlang -progname erl -- -home /var/lib/ 
rabbitmq -pa /usr/lib/rabbitmq/bin/../ebin -noshell -noinput -s rabbit  
-sname rabbit -boot start_sasl -kernel inet_default_listen_options  
[{nodelay,true},{sndbuf,16384},{recbuf,4096}] -kernel  
inet_default_connect_options [{nodelay,true}] -rabbit tcp_listeners  
[{"", 5672}] -sasl errlog_type error -kernel error_logger  
{file,"/var/log/rabbitmq/rabbit.log"} -sasl sasl_error_logger {file,"/ 
var/log/rabbitmq/rabbit-sasl.log"} -os_mon start_cpu_sup true -os_mon  
start_disksup false -os_mon start_memsup false -os_mon start_os_sup  
false -os_mon memsup_system_only true -os_mon  
system_memory_high_watermark 0.95 -mnesia dir "/var/lib/rabbitmq/ 
mnesia/rabbit" -noshell -noinput
If I look at the startup_log it looks like it started fine:

Starting all nodes...
Starting node rabbit at dashboard...
RabbitMQ 1.5.4 (AMQP 8-0)
Copyright (C) 2007-2009 LShift Ltd., Cohesive Financial Technologies  
LLC., and Rabbit Technologies Ltd.
Licensed under the MPL.  See http://www.rabbitmq.com/
Logging to "/var/log/rabbitmq/rabbit.log"
SASL logging to "/var/log/rabbitmq/rabbit-sasl.log"
starting database ...done
starting core processes ...done
starting recovery ...done
starting persister ...done
starting guid generator ...done
starting builtin applications ...done
starting TCP listeners ...done broker

running startup_err does have this:
Error: cannot_get_pid
It does the same thing if I manually run /etc/initd./rabbitmq-server  
start except it just never returns from the command (ie the process  
doesn't daemonize) Is this normal (my pre 1.5.3 installs on other  
systems didn't have this problem) Or am I forgetting to do something?  

Robert J Berger - CTO
(Our name has been changed from Cinch to Runa)
520 San Antonio Rd Suite 210, Mountain View, CA 94040
+1 408-838-8896
http://blog.ibd.com / http://www.runa.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090430/efc78c46/attachment.htm 

More information about the rabbitmq-discuss mailing list