[rabbitmq-discuss] Crashes - init terminating?

Tue Jul 31 12:22:00 BST 2012

Don,

Since our last conversation the latest release has become 2.8.4.

>> Did you run `sudo port load rabbitmq-server` which starts the service in
>> the background?
> No - and I've never had to before.

Well, you don't have to, but if you don't you need to start the server
yourself (`sudo rabbitmq-server` or `sudo rabbitmq-server -detached`)
before running rabbitmqctl etc. Did you? If you didn't then you have an
old version still running -- this may be scuppered because of an Erlang
upgrade during the rabbitmq-server install. So...

I think your problems are probably caused by having two installations
interfering (or possibly an old Erlang version).

If you haven't installed rabbitmq-server or Erlang by any other means
than macports then the following sequence will probably get you working.

(If you have, please ensure that the other installations are correctly
removed (including any plugin directories, environment variable
settings, &c.) before proceeding.)

Execute the following steps:

1) obtain the latest macports version `sudo port selfupdate` (Macports
   2.1.2 is what I get today.)

2) perform `sudo port upgrade outdated` (this might cure everything, but
   just in case...)

3) uninstall all previous versions of rabbitmq-server (`sudo port
   uninstall rabbitmq-server` should do it) check these are all gone:
   `sudo port installed rabbitmq-*`

4) clean up: `sudo port -u -v uninstall` will remove any debris from the
   macports repository

5) check your Erlang version: `sudo port installed erlang*` (should be
   active) upgrade this is it old (should have been done already above)

6) perform a clean install: `sudo port install rabbitmq-server` (check
   what version you get)

7) OBSERVE the instructions issued during this install about `sudo port
   load rabbitmq-server`. You might want to start rabbitmq in the
   background this way, or start it the normal way if you want. But
   start it.

Now everything should work. Come back here if it doesn't. In
particular, the output from when you start the server and the first
rabbitmqctl command.

Hope all goes smoothly for you.

Steve Powell  (a happy bunny)
----------yet more definitions from the SPD----------
corrugate (n.) T.V. soap scandal.
olympic (n.) A camp road-digger.
jamboree (n.) A conserve made from French cheese.

On 31 Jul 2012, at 11:56, Steve Powell wrote:

> Dan,
> Reposting on Discuss.  Please continue correspondence on ths rabbitmq-discuss mailing list.
> 
> From: 	Dan Dart <dan at canddi.com>
> Subject: 	Re: [rabbitmq-discuss] Crashes - init terminating?
> Date: 	30 July 2012 18:07:05 GMT+01:00
> To: 	Steve Powell <steve at rabbitmq.com>
> 
>> Did you run `sudo port load rabbitmq-server` which starts the service in
>> the background?
> No - and I've never had to before.
> 
>> 
>> Now accessing the rabbitmqctl and rabbitmq-server scripts from the
>> command line requires that you issue them as root, done with sudo:
>> 
>>    sudo rabbitmqctl status
>> 
>> This should give a reasonable response.
> 
> Doesn't look reasonable to me:
> {"init terminating in
> do_boot",{undef,[{rabbit_control,start,[]},{init,start_it,1},{init,start_em,1}]}}
> 
> Crash dump was written to: erl_crash.dump
> init terminating in do_boot ()
> 
>> To see if the server has problems you should look in the log directory
>> (/opt/local/var/log/rabbitmq/*) where you should have two logs for each
>> rabbitmq node you run. (By default this is rabbit@<hostname>.log and
>> -sasl.log.) I suspect there will be nothing untoward there.
> 
> Getting lots of connection_closed_abruptly - although I suspect this is normal.
> And nothing in the sasl log.
> 
>> I cannot reproduce your symptoms unless I disable the -pa option on the
>> (eventual) erl command, so it looks as though you have an environment
>> problem. Please check the following directory:
>> 
>>    /opt/local/lib/rabbitmq/lib/rabbitmq_server-2.8.2/
>> 
>> and see if the scripts are in sbin/, and there are a lot of beam files
>> in ebin/.
> [Dan-Darts-iMac:lib/rabbitmq_server-2.8.2/sbin] DanDart% ls
> rabbitmq-defaults	rabbitmq-env		rabbitmq-plugins	rabbitmq-server		rabbitmqctl
> 
> [Dan-Darts-iMac:lib/rabbitmq_server-2.8.2/ebin] DanDart% ls
> credit_flow.beam
> [...snip...]
> 
>> PS:
>> [You might be using a non-standard prefix for macport install
>> files -- if so, the /opt/local in this directory path might be something
>> different for you -- and we may have a bug, since we are supposed to
>> cope with that.]
> 
> Nope - it's the same. I just used a standard "port install
> rabbitmq-server" and don't remember doing anything that would break
> it.
> 
> Is that any help?
> 
> Regards
> Dan
> 
> Steve Powell  (a happy bunny)
> ----------yet more definitions from the SPD----------
> corrugate (n.) T.V. soap scandal.
> olympic (n.) A camp road-digger.
> jamboree (n.) A conserve made from French cheese.
> 
> On 19 Jun 2012, at 14:04, Steve Powell wrote:
> 
>> Hi Dan,
>> 
>> The Erlang crash dumps for rabbitmq-server and rabbitmqctl are because
>> of failures to run these Erlang programs (actually a prelaunch program
>> in the former case). They should not affect the rabbitmq-server service
>> if it is already running (which it appears to be since you say sending
>> and receiving messages are fine).
>> 
>> I assume that by the latest version of rabbitmq you are running
>> rabbitmq-server 2.8.2, and Erlang R15B, which is what I get from my
>> macports (on OS X 10.6.8, macports 2.1.1). You should check that any
>> earlier version(s) is(are) uninstalled.
>> 
>> Did you run `sudo port load rabbitmq-server` which starts the service in
>> the background?
>> 
>> Now accessing the rabbitmqctl and rabbitmq-server scripts from the
>> command line requires that you issue them as root, done with sudo:
>> 
>>    sudo rabbitmqctl status
>> 
>> This should give a reasonable response.
>> 
>> To see if the server has problems you should look in the log directory
>> (/opt/local/var/log/rabbitmq/*) where you should have two logs for each
>> rabbitmq node you run. (By default this is rabbit@<hostname>.log and
>> -sasl.log.) I suspect there will be nothing untoward there.
>> 
>> I cannot reproduce your symptoms unless I disable the -pa option on the
>> (eventual) erl command, so it looks as though you have an environment
>> problem. Please check the following directory:
>> 
>>    /opt/local/lib/rabbitmq/lib/rabbitmq_server-2.8.2/
>> 
>> and see if the scripts are in sbin/, and there are a lot of beam files
>> in ebin/.
>> 
>> PS: 
>> [You might be using a non-standard prefix for macport install
>> files -- if so, the /opt/local in this directory path might be something
>> different for you -- and we may have a bug, since we are supposed to
>> cope with that.]
>> 
>> Steve Powell  (a happy bunny)
>> ----------yet more definitions from the SPD----------
>> corrugate (n.) T.V. soap scandal.
>> olympic (n.) A camp road-digger.
>> jamboree (n.) A conserve made from French cheese.
>> 
>> On 19 Jun 2012, at 10:44, Dan Dart wrote:
>> 
>>> Hi,
>>> 
>>> I'm having a problem in that sending and receiving messages is fine,
>>> but doing either of these commands:
>>> 
>>> rabbitmqctl list_exchanges
>>> rabbitmqctl list_queues
>>> rabbitmqctl list_bindings
>>> rabbitmqctl delete_user
>>> rabbitmqctl add_user
>>> rabbitmqctl delete_vhost
>>> rabbitmqctl add_vhost
>>> rabbitmqctl set_permissions
>>> rabbitmqctl stop
>>> 
>>> echoes the following to stderr:
>>> 
>>> {"init terminating in
>>> do_boot",{undef,[{rabbit_control,start,[]},{init,start_it,1},{init,start_em,1}]}}
>>> 
>>> Crash dump was written to: erl_crash.dump
>>> init terminating in do_boot ()
>>> 
>>> and rabbitmq-server results in:
>>> 
>>> {"init terminating in
>>> do_boot",{undef,[{rabbit_prelaunch,start,[]},{init,start_it,1},{init,start_em,1}]}}
>>> 
>>> Crash dump was written to: erl_crash.dump
>>> init terminating in do_boot ()
>>> 
>>> My Rabbit version is the latest from MacPorts on OSX 10.6 (and will
>>> not tell me itself).
>>> 
>>> My erl_crash.dump:
>>> https://gist.github.com/2953290
>>> 
>>> Cheers
>>> Dan
>>> _______________________________________________
>>> rabbitmq-discuss mailing list
>>> rabbitmq-discuss at lists.rabbitmq.com
>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>> 
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120731/8450ffda/attachment.htm>