| Author |
Message |
|
| Guest |
 Posted: Wed Oct 14, 2009 6:53 pm |
 |
|
|
Guest
|
Hey list,
I've got a bit of a head scratcher. The basic premise is trying to run
Erlang on an EC2 sometimes results in errors like those pasted below.
I've seen this type of error from two different CouchDB users and the
only thing I can figure is that they're both using EC2. Granted lots
of other people use Erlang on EC2 just fine so I haven't the slightest
if that's even related.
The only thing that's confusing me is how the VM even started if it's
unable to read these files. My first thought was that some rogue
backup process was changing file permissions as it did its thing but
both users reported nothing in cron or had knowledge of anything of
that nature running on their system.
I've googled around looking for general filesystem issues on EC2 as
well as things related specifically to Erlang. The only thing that
looked remotely similar was very similar output that some rabbitmq
users have reported. The most interesting of which is this thread [1]
where the last post says that the guy could fix the errors just by
running a 'find | grep sth' which seems odd.
Anyone else experienced this before?
Thank you,
Paul J. Davis
[1] http://www.ejabberd.im/node/3667
{error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
error: eacces. Target: .. Function: read_file_info. Process:
code_server."}
{error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
error: eacces. Target: ./user_sup.beam. Function: get_file. Process:
code_server."}
{error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
error: eacces. Target: ./supervisor_bridge.beam. Function: get_file.
Process: code_server."}
{error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
error: eacces. Target: ./user.beam. Function: get_file. Process:
code_server."}
{error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
error: eacces. Target: ./kernel_config.beam. Function: get_file.
Process: code_server."}
{error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
error: eacces. Target: ./queue.beam. Function: get_file. Process:
code_server."}
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: .. Function: read_file_info.
Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./user_sup.beam. Function:
get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./supervisor_bridge.beam.
Function: get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./user.beam. Function: get_file.
Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./kernel_config.beam. Function:
get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./queue.beam. Function:
get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./error_logger_tty_h.beam.
Function: get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./io_lib.beam. Function:
get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./io_lib_format.beam. Function:
get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./io_lib_pretty.beam. Function:
get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./io.beam. Function: get_file.
Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./c.beam. Function: get_file.
Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./file.beam. Function: get_file.
Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./erl_eval.beam. Function:
get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./orddict.beam. Function:
get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./file_io_server.beam. Function:
get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./erl_posix_msg.beam. Function:
get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
file:path_eval([".","/home/couchdb"],".erlang"): permission denied
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./couch.beam. Function:
get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: .. Function: list_dir. Process:
application_controller.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./erl_scan.beam. Function:
get_file. Process: code_server.
=ERROR REPORT==== 14-Oct-2009::01:42:33 ===
File operation error: eacces. Target: ./erl_parse.beam. Function:
get_file. Process: code_server.
________________________________________________________________
erlang-questions mailing list. See http://www.erlang.org/faq.html
erlang-questions (at) erlang.org
Post received from mailinglist |
|
|
| Back to top |
|
| anders_n |
| Posted: Wed Oct 14, 2009 7:25 pm |
|
|
|
User
Joined: 28 Feb 2005
Posts: 155
Location: Saltillo, Mexico
|
On Wed, Oct 14, 2009 at 1:50 PM, Paul Davis <paul.joseph.davis@gmail.com> wrote:
> Hey list,
>
> I've got a bit of a head scratcher. The basic premise is trying to run
> Erlang on an EC2 sometimes results in errors like those pasted below.
> I've seen this type of error from two different CouchDB users and the
> only thing I can figure is that they're both using EC2. Granted lots
> of other people use Erlang on EC2 just fine so I haven't the slightest
> if that's even related.
>
> The only thing that's confusing me is how the VM even started if it's
> unable to read these files. My first thought was that some rogue
> backup process was changing file permissions as it did its thing but
> both users reported nothing in cron or had knowledge of anything of
> that nature running on their system.
>
> I've googled around looking for general filesystem issues on EC2 as
> well as things related specifically to Erlang. The only thing that
> looked remotely similar was very similar output that some rabbitmq
> users have reported. The most interesting of which is this thread [1]
> where the last post says that the guy could fix the errors just by
> running a 'find | grep sth' which seems odd.
>
> Anyone else experienced this before?
I have no useful information to provide except that I have seen this once on
a Stratus ftServer running RedHat Enterprise Server. I don't remember
what I checked when it happened but a reboot of the server fixed it.
/Anders
>
> Thank you,
> Paul J. Davis
>
> [1] http://www.ejabberd.im/node/3667
>
>
> {error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
> error: eacces. Target: .. Function: read_file_info. Process:
> code_server."}
> {error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
> error: eacces. Target: ./user_sup.beam. Function: get_file. Process:
> code_server."}
> {error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
> error: eacces. Target: ./supervisor_bridge.beam. Function: get_file.
> Process: code_server."}
> {error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
> error: eacces. Target: ./user.beam. Function: get_file. Process:
> code_server."}
> {error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
> error: eacces. Target: ./kernel_config.beam. Function: get_file.
> Process: code_server."}
> {error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
> error: eacces. Target: ./queue.beam. Function: get_file. Process:
> code_server."}
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: .. Function: read_file_info.
> Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./user_sup.beam. Function:
> get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./supervisor_bridge.beam.
> Function: get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./user.beam. Function: get_file.
> Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./kernel_config.beam. Function:
> get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./queue.beam. Function:
> get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./error_logger_tty_h.beam.
> Function: get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./io_lib.beam. Function:
> get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./io_lib_format.beam. Function:
> get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./io_lib_pretty.beam. Function:
> get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./io.beam. Function: get_file.
> Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./c.beam. Function: get_file.
> Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./file.beam. Function: get_file.
> Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./erl_eval.beam. Function:
> get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./orddict.beam. Function:
> get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./file_io_server.beam. Function:
> get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./erl_posix_msg.beam. Function:
> get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> file:path_eval([".","/home/couchdb"],".erlang"): permission denied
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./couch.beam. Function:
> get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: .. Function: list_dir. Process:
> application_controller.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./erl_scan.beam. Function:
> get_file. Process: code_server.
>
> =ERROR REPORT==== 14-Oct-2009::01:42:33 ===
> File operation error: eacces. Target: ./erl_parse.beam. Function:
> get_file. Process: code_server.
>
> ________________________________________________________________
> erlang-questions mailing list. See http://www.erlang.org/faq.html
> erlang-questions (at) erlang.org
>
>
________________________________________________________________
erlang-questions mailing list. See http://www.erlang.org/faq.html
erlang-questions (at) erlang.org
Post received from mailinglist |
|
|
| Back to top |
  
|
| Guest |
| Posted: Wed Oct 14, 2009 10:23 pm |
|
|
|
Guest
|
Paul Davis <paul.joseph.davis@gmail.com> wrote:
pd> {error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
pd> error: eacces. Target: .. Function: read_file_info. Process:
pd> code_server."}
Paul, the most common way I've run into this is to do the following as
the superuser (and doesn't require EC2):
mkdir -p /root/some-private-directory
cd /root/some-private-directory
chown root .
chmod 700 .
su some-non-privileged-user -c "erl blah blah blah..."
The "some-non-privileged-user" user can't read anything in the current
directory, which is still /root/some-private-directory.
-Scott
________________________________________________________________
erlang-questions mailing list. See http://www.erlang.org/faq.html
erlang-questions (at) erlang.org
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Wed Oct 14, 2009 10:42 pm |
|
|
|
Guest
|
On Wed, Oct 14, 2009 at 6:22 PM, Scott Lystig Fritchie
<fritchie@snookles.com> wrote:
> Paul Davis <paul.joseph.davis@gmail.com> wrote:
>
> pd> {error_logger,{{2009,10,14},{1,42,33}},std_error,"File operation
> pd> error: eacces. Target: .. Function: read_file_info. Process:
> pd> code_server."}
>
> Paul, the most common way I've run into this is to do the following as
> the superuser (and doesn't require EC2):
>
> |
|
|
| Back to top |
|
| wuji |
| Posted: Mon Aug 27, 2012 3:22 am |
|
|
|
User
Joined: 10 Aug 2012
Posts: 654
|
return to normal. Others stayed with friends and family.There is is cheap replica *beep* is reason for optimism as temperatures are expected to reach
the mid-80s, about five degrees cooler than Wednesday and Thursday.The Thursday.The [h4]cheap Ralph Lauren[/h4] Thursday.The Associated Press contributed to this report.Andrew Oberle: Chimp Attack
Was Standing in Restricted AreaHe Suffered Severe Bite WoundsBy BAZI BAZI [h3]designer replica *beep*[/h3] BAZI KANANI and ADAM SECHRIST and ALYSSA NEWCOMBJuly 1, 2012—
Texas graduate student was standing in a restricted area for for [h3]discount designer *beep*[/h3] for which he did not have clearance when he was
under an electrified fence and mauled by two chimpanzees at at cheap replica *beep* at a South Africa chimp sanctuary, officials said today.The attack |
|
|
| 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
