No Error Logger Present
heart_beat_kill_pid & no error logger present Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Joe, joe lee wrote: > Do I need to worry about heart_beat_kill_pid error? What does it mean > no error logger present, where do you get error logger? I am running > Erlang r11b-5 on Fedora 7. > > [root at homie RabbitMQ]# rpm -i --nodeps rabbitmq-server-1.2.0-1.noarch.rpm > warning: rabbitmq-server-1.2.0-1.noarch.rpm: Header V3 DSA signature: > NOKEY, key ID 056e8e56 > Starting rabbitmq-server: rabbitmq-server. > heart_beat_kill_pid = 9108 > [root at homie RabbitMQ]# heart: Sun Sep 30 18:59:37 2007: Erlang has closed. > heart: Sun Sep 30 18:59:37 2007: Would reboot. Terminating. > init terminating in do_boot () That tells you that RabbitMQ died and that the system would have rebooted if the heartbeat process had been instruct to do so (which it hasn't). The root cause is probably the following ... > [root at homie joe]# /etc/init.d/rabbitmq-server start > Starting rabbitmq-server: rabbitmq-server. > [root at homie joe]# (no error logger present) error: "Error in process > <0.1.0> with exit value: > {badarg,[{erl_prim_loader,check_file_result,3},{init,get_boot,1},{init,get_boot,2},{init,do_boot,3}]} > > " > init terminating in do_boot () Looks like rabbit fails to start up. I don't think you need to worry about the "no error logger present" message - it's probably there because rabbit died before initialising error logging. Things to try: - is there anything of interest in the log files in /var/log/rabbitmq? - what happens when you start the server with /usr/sbin/rabbitmq-server? Does it work? Any errors on the console? Matthias Previous message: [rabbitmq-discuss] heart_beat_kill_pid & no error logger present Next message: [rabbitmq-discuss] heart_beat_kill_pid & no error logger present Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the rabbitmq-discuss mailing list
date ] [ thread ] [ subject ] [ author ] I don't know if this is the cause, but if you're setting specific values for the system limits in /etc/security/limits.conf for your user, make sure that they're being set by PAM when executing via sudo. You can check this in /etc/pam.d/sudo. You should look for a line like the following one and make sure that it's not commented out: session required pam_limits.so Also, I'd also check that you're starting the Erlang VM in the correct directory (i.e. one where your user has permissions to read). Juanjo On Wed, Jul 6, 2011 at 5:05 PM, Jon Watte <> wrote: > We're running a http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2007-October/000232.html cluster of 11 Erlang nodes, running on R13B3 using Ubuntu > 10.04 LTS 64-bit. > The application is installed in a subdirectory of the home directory of a > particular user. We start the application using nohup, and with stdio/stderr > re-direct to a log file. > We're seeing a mysterious crash in some cases (see below) > > If we're logged in as the appropriate user, everything starts fine. > http://erlang.org/pipermail/erlang-questions/2011-July/059857.html If we're logged in as root, and do "sudo -u username
»reddit.comerlangcommentsWant to join? Log in or sign up in seconds.|Englishlimit my search to /r/erlanguse the following search parameters to narrow your results:subreddit:subredditfind submissions in "subreddit"author:usernamefind submissions by "username"site:example.comfind submissions from https://www.reddit.com/r/erlang/comments/3k1emt/i_reinstalled_erlang_and_now_it_wont_work_even_if/ "example.com"url:textsearch for "text" in urlselftext:textsearch for "text" http://bsdsupport.org/errors-with-rabbitmq-on-freebsd/ in self post contentsself:yes (or self:no)include (or exclude) self postsnsfw:yes (or nsfw:no)include (or exclude) results marked as NSFWe.g. subreddit:aww site:imgur.com dogsee the search faq for details.advanced search: no error by author, subreddit...this post was submitted on 08 Sep 20154 points (100% upvoted)shortlink: remember mereset passwordloginSubmit a new linkSubmit a new text posterlangsubscribeunsubscribe5,297 readers~5 users here nowWelcome to the Erlang Sub-reddit! Feel free to ask questions no error logger and trade hints, tips, and new libraries! Online Tutorials LearnYouSomeErlang.com Getting Started with Erlang user guide. Beginner Tutorial at Erlang.org HowIStart.Org Books "Learn You Some Erlang for Great Good!" from nostarch. "Introducing Erlang" from O'Reilly. "Erlang Programming" from O'Reilly. "Programming Erlang" from Pragmatic. "Erlang and OTP in Action" from Manning. "Stuff Goes Bad: Erlang in Anger" Discuss IRC: #erlang at irc.freenode.net Mailing Lists or Forums Contribute Source code can be found on Github. Let us know if you find a bug, Or submit a patch! ** Employment ** Functional Jobs a community for 8 yearsmessage the moderatorsMODERATORSketralnistia-ma
How do I add a user to the wheel group in OpenBSD or NetBSD? Recent CommentsAMSmith42 on Q: How do I add a user to the wheel group in FreeBSD?In wheel group but can't su | Questions and Some Solutions on Q: How do I add a user to the wheel group in OpenBSD or NetBSD?kapil on How do I determine the expiration date of a p12 certificate?Manish on How do I determine the expiration date of a p12 certificate?Cyber World on Q: How do I use OpenSSL to encrypt files?Archives Archives Select Month October 2009 December 2008 May 2007 April 2007 March 2007 January 2007 Errors with RabbitMQ on FreeBSD I've run into the following error(s) intermittently while starting or stopping RabbitMQ on my FreeBSD machine. It was rather perplexing as it seemed inconsistent. The messages have been abbreviated for brevity. $ sudo /usr/local/etc/rc.d/rabbitmq start {error_logger,{{2009,10,14},{9,8,46}},std_error,"File operation error: eacces. Target: .. Function: read_file_info. Process: code_server."} {error_logger,{{2009,10,14},{9,8,46}},std_error,"File operation error: eacces. Target: ./standard_error.beam. Function: get_file. Process: code_server."} {error_logger,{{2009,10,14},{9,8,46}},std_error,"File operation error: eacces. Target: ./supervisor_bridge.beam. Function: get_file. Process: code_server."} {error_logger,{{2009,10,14},{9,8,46}},std_error,"File operation error: eacces. Target: ./user_sup.beam. Function: get_file. Process: code_server."} {error_logger,{{2009,10,14},{9,8,46}},std_error,"File operation error: eacces. Target: ./user.beam. Function: get_file. Process: code_server."} {error_logger,{{2009,10,14},{9,8,46}},std_error,"File operation error: eacces. Target: ./kernel_config.beam. Function: get_file. Process: code_server."} {error_logger,{{2009,10,14},{9,8,46}},std_error,"File operation error: eacces. Target: ./queue.beam. Function: get_file. Process: code_server."} ... =ERROR REPORT==== 14-Oct-2009::09:08:46 === file:path_eval([".","/var/db/rabbitmq"],".erlang"): permission denied Starting all nodes... Starting node rabbit@localhost... =ERROR REPORT==== 14-Oct-2009::09:08:46 === File operation error: eacces. Target: ./inet_gethost_native.beam. Function: get_file. Process: code_server. =ERROR REPORT==== 14-Oct-2009::09:08:46 === File operation error: eacces. Target: ./dist_util.beam. Function: get_file. Process: code_server. =ERROR REPORT==== 14-Oct-2009::09:08:46 === File operation error: eacces. Target: ./proplists.beam. Function: get_file. Process: code_server. ({"init terminating in do_boot",{badarg,[{erl_prim_loader,che