While upgrading from erlang-R13B-04.6.fc12.i686 to erlang-R13B-04.10.fc12.i686 (via yum upgrade), the rabbitmq-server application stopped working. I traced it down to a bug in the erlang-os_mon-R13B-04.10.fc12.i686 package.


Version-Release number of selected component (if applicable):
erlang-R13B-04.10.fc12.i686
erlang-os_mon-R13B-04.10.fc12.i686

How reproducible:
With rabbitmq-server, erlang-R13B-04.6.fc12.i686 and the whole erlang-* family of RPMs installed, do `/etc/init.d/rabbitmq-server start` and it works.

With erlang-R13B-04.10.fc12.i686 and the associated erlang-* family of RPMs, it fails.


Steps to Reproduce:
1. yum install -a rabbitmq-server
2. /etc/init.d/rabbitmq-server start
 
Actual results:
The server doesn't start and spits out the following to the /var/log/rabbitmq/startup_log file:

{"init terminating in do_boot",{{nocatch,{error,{cannot_start_application,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{undef,[{nteventlog,module_info,[attributes]},{rabbit,'-boot_steps/0-fun-0-',1},{lists,flatmap,2},{lists,flatmap,2},{rabbit,boot_steps,0},{rabbit,start,2},{application_master,start_it_old,4}]}}}}}}},[{init,start_it,1},{init,start_em,1}]}}

Expected results:
The server should start running.

Additional info:
I traced it down to the lack of the nteventlog module, which is reffered to in /usr/lib/erlang/lib/os_mon-2.2.5/ebin/os_mon.app which, in turn, is provided by erlang-os_mon-R13B-04.10.fc12.i686.

I could not downgrade because only the erlang RPM itself knows how to, all the other erlang-* ones don't know how to, so this is a no-return situation (shy from uninstalling and then installing the old RPMs by hand).