OpenSuse 11.0 and ejabberd ejabberd 2.0.5 - File operation error: eacces

Helo, masters!
I'm sorry for my english & my problem,
But I've install ejabberd 2.0.5-1.6 on Opensuse 11.0 and tried to configure it for using ldap authetification. But it wont work (i use PSI jabber client). I had no possible idea whats wrong, because i had not logs. But after restarting my system and #/etc/rc.d/ejabberd stop i've got this:

Shutting down ejabberd {error_logger,{{2009,9,20},{16,10,36}},std_error,"File operation error: eacces. Target: .. Function: read_file_info. Process: code_server."}
{error_logger,{{2009,9,20},{16,10,36}},std_error,"File operation error: eacces. Target: ./standard_error.beam. Function: get_file. Process: code_server."}
{error_logger,{{2009,9,20},{16,10,36}},std_error,"File operation error: eacces. Target: ./supervisor_bridge.beam. Function: get_file. Process: code_server."}
{error_logger,{{2009,9,20},{16,10,36}},std_error,"File operation error: eacces. Target: ./user_sup.beam. Function: get_file. Process: code_server."}
{error_logger,{{2009,9,20},{16,10,36}},std_error,"File operation error: eacces. Target: ./user.beam. Function: get_file. Process: code_server."}
{error_logger,{{2009,9,20},{16,10,36}},std_error,"File operation error: eacces. Target: ./kernel_config.beam. Function: get_file. Process: code_server."}
{error_logger,{{2009,9,20},{16,10,36}},std_error,"File operation error: eacces. Target: ./queue.beam. Function: get_file. Process: code_server."}

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: .. Function: read_file_info. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./standard_error.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./supervisor_bridge.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./user_sup.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./user.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./kernel_config.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./queue.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./error_logger_tty_h.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./io_lib.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./io_lib_format.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./io_lib_pretty.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./io.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./unicode.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./c.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./erl_eval.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./orddict.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./file_io_server.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./erl_posix_msg.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
file:path_eval([".","/var/lib/ejabberd"],".erlang"): permission denied

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./string.beam. Function: get_file. Process: code_server.

=ERROR REPORT==== 20-Sep-2009::16:10:36 ===
File operation error: eacces. Target: ./dist_util.beam. Function: get_file. Process: code_server.

As long as i understand, somebody haven't some rights to do something.. But who? I enter as root.
And i have logs like erl_crash_20090920-161036.dump in /var/log/ejabberd, that i have not stomaсh to understand.
Help me, please!

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

+

I've forgot to tell that i reininstall erlang and ejabberd to try default configure, but problem is the same.

I didn't change anything, but now, when i'm calling reload command the first time it sais:

Shutting down ejabberd RPC failed on the node ejabberd@localhost: nodedown

Commands to start an ejabberd node:
  start  Start an ejabberd node in server mode
  debug  Attach an interactive Erlang shell to a running ejabberd node
  live   Start an ejabberd node in live (interactive) mode

Optional parameters when starting an ejabberd node:
  --config file      Config file of ejabberd:    /etc/ejabberd/ejabberd.cfg
  --ctl-config file  Config file of ejabberdctl: /etc/ejabberd/ejabberdctl.cfg
  --logs dir         Directory for logs:         /var/log/ejabberd/
  --spool dir        Database spool dir:         /var/lib/ejabberd/db/ejabberd
  --node nodename    ejabberd node name:         ejabberd@localhost

                                                                      missing
Starting ejabberd                                                     done

without creating logs.
and

Shutting down ejabberd                                                done
Starting ejabberd                                                     done

with creating the log file kind of "erl_crash_20090920-173601.dump".
This doings are alternating.
What am i doing wrong?

find..

I've removed the ejabberd (by rpm -e --noscripts), manually deleted all ejabberd files and folders and i've deleted user/group ejabberd. After reinstalation it's starting successful.
But after restarting system this problem came back.

Now i spot, that it's starting to work after "find | grep sth"
Restarting - won't start again.. "find" - and it works! Interesting.

Syndicate content