| Author |
Message |
< RabbitMQ mailing list ~ File operation error: eacces. Target: ... |
| Guest |
 Posted: Wed Aug 26, 2009 2:05 pm |
 |
|
|
Guest
|
We have rabbit running on a managed host that did the setup for us and runs rabbit under the user rabbitmq-server. Everything works great from our client end but when we log on to the server directly and do a list_queues command on rabbitmqctl we get all these errors. Note that the queues do get listed but after a big long list of "File operation error"s. Are these something to worry about? If so, what i can tell the team to fix?
[rabbitmq-server@xxxx bwhitman]$ /opt/rabbitmq/rabbitmq-server/scripts/rabbitmqctl list_queues
{error_logger,{{2009,8,26},{9,1,55}},std_error,"File operation error: eacces. Target: .. Function: read_file_info. Process: code_server."}
{error_logger,{{2009,8,26},{9,1,55}},std_error,"File operation error: eacces. Target: ./standard_error.beam. Function: get_file. Process: code_server."}
{error_logger,{{2009,8,26},{9,1,55}},std_error,"File operation error: eacces. Target: ./supervisor_bridge.beam. Function: get_file. Process: code_server."}
{error_logger,{{2009,8,26},{9,1,55}},std_error,"File operation error: eacces. Target: ./user_sup.beam. Function: get_file. Process: code_server."}
{error_logger,{{2009,8,26},{9,1,55}},std_error,"File operation error: eacces. Target: ./user.beam. Function: get_file. Process: code_server."}
{error_logger,{{2009,8,26},{9,1,55}},std_error,"File operation error: eacces. Target: ./kernel_config.beam. Function: get_file. Process: code_server."}
{error_logger,{{2009,8,26},{9,1,55}},std_error,"File operation error: eacces. Target: ./queue.beam. Function: get_file. Process: code_server."}
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: .. Function: read_file_info. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./standard_error.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./supervisor_bridge.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./user_sup.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./user.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./kernel_config.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./queue.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./error_logger_tty_h.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./io_lib.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./io_lib_format.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./io_lib_pretty.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./io.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./unicode.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./c.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./erl_eval.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./orddict.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./file_io_server.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./erl_posix_msg.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
file:path_eval([".","/home/rabbitmq-server"],".erlang"): permission denied
Listing queues ...
=ERROR REPORT==== 26-Aug-2009::09:01:55 ===
File operation error: eacces. Target: ./dist_util.beam. Function: get_file. Process: code_server.
xy_queue |
|
|
| Back to top |
|
| 0x6e6562 |
| Posted: Wed Aug 26, 2009 8:42 pm |
|
|
|
User
Joined: 12 Jul 2007
Posts: 250
|
Brian,
On Wed, Aug 26, 2009 at 3:04 PM, Brian Whitman<brian@echonest.com> wrote:
> We have rabbit running on a managed host that did the setup for us and runs
> rabbit under the user rabbitmq-server. Everything works great from our
> client end but when we log on to the server directly and do a list_queues
> command on rabbitmqctl we get all these errors. Note that the queues do get
> listed but after a big long list of "File operation error"s. Are these
> something to worry about? If so, what i can tell the team to fix?
Basically it's a privilege issue with the user that is executing the
script. Whether or not it is something to worry about depends on
whether you are parsing the output of the script. Certainly it doesn't
look nice, so it would be nice to tweak the packaging so that it just
works without complaining for any user, but off the top of my head I
don't know the implications of doing this. We'd have to take a closer
look.
Ben
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
 
|
| wuji |
| Posted: Thu Sep 06, 2012 7:26 am |
|
|
|
User
Joined: 10 Aug 2012
Posts: 654
|
industry has sprung up to help save you from your your cheap designer *beep* your own gaffes: advice books, software, online tools and
web-monitoring/ web-scrubbing services aimed at helping to undo whatever it it replica designer bags for sale it is you regret having said or done.So pervasive is
desire to wipe their online slates clean, that the new new cheap replica *beep* new Batman movie imagines a program called Clean Slate that
exactly that.The Seattle Times, in an article about this phenomenon, phenomenon, replica designer *beep* phenomenon, says media consulting firm DIA/Kelsey estimates that $2.2 billion
be spent in 2012 on so-called reputation management tools, including including [h3]cheap polo shirts[/h3] including ones that heal self-inflicted wounds.The Times also cites some |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
