From: dobr <dobr@iop.kiev.ua>
To: "ALT Linux sysadmins' discussion" <sysadmins@lists.altlinux.org>
Subject: Re: [Sysadmins] ejabberd
Date: Sat, 08 Feb 2014 18:07:42 +0200
Message-ID: <52F6564E.9040502@iop.kiev.ua> (raw)
In-Reply-To: <52F654AC.6080109@iop.kiev.ua>
On 02/08/2014 06:00 PM, dobr wrote:
> Всем привет,
> Столкнулся с трудностями при запуске ejabberd из p7.
> Установлены:
> ejabberd-2.1.10-alt1
> erlang-R15B.2-alt3
> erlang-otp-bin-R15B.2-alt3
> В конфиге изменил
> {hosts, ["jabber.iop.kiev.ua"]}.
> а в /etc/sysconfig/ejabberd
> INET_DIST_INTERFACE={0,0,0,0}
> ERLANG_NODE=ejabberd@jabber.iop.kiev.ua
> проблема в том, что сервер не запускается. Согласно отчетам.
> А админка работает. Веб адрес откликается и просит дать логин/пароль.
> А поскольку ejabberdctl не может создать пользователя, не могу и
> залогиниться.
> Что у нас надо ещё крутить чтоб запустить ejabberd?
>
> ejabberdctl status
> Failed RPC connection to the node 'ejabberd@jabber.iop.kiev.ua': 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-dir dir Config ejabberd: /etc/ejabberd
> --config file Config ejabberd: /etc/ejabberd/ejabberd.cfg
> --ctl-config file Config ejabberdctl: /etc/sysconfig/ejabberd
> --logs dir Directory for logs: /var/log/ejabberd
> --spool dir Database spool dir: /var/lib/ejabberd
> --node nodename ejabberd node name: ejabberd@jabber.iop.kiev.ua
> В логе ничего не вижу криминального.
> Последние записи:
> =INFO REPORT==== 2014-02-08 17:44:57 ===
> I(<0.539.0>:ejabberd_s2s_out:892) : Closing connection with gmail.com:
> timeout
>
> =INFO REPORT==== 2014-02-08 17:48:16 ===
> I(<0.544.0>:ejabberd_s2s_out:892) : Closing connection with jabber.ru:
> timeout
>
> Как будто сервер работает. Но кучка креш-дампов рядом с логами наводит
> на мысли об обратном...
> Эрланг в процессах есть.
>
> Андрей
>
>
Feb 8 15:23:29 first apt-shell: ejabberd-2.1.10-alt1 installed
Feb 8 16:31:52 first ejabberd: Starting ejabberd service: succeeded
Feb 8 16:52:37 first epmd: epmd: node name already occupied ejabberd
Feb 8 16:53:49 first epmd: epmd: node name already occupied ejabberd
Feb 8 16:57:39 first epmd: epmd: node name already occupied ejabberd
Feb 8 17:03:59 first ejabberdctl: Failed RPC connection to the node
ejabberd@first: nodedown
Feb 8 17:03:59 first ejabberdctl: Commands to start an ejabberd node:
Feb 8 17:03:59 first ejabberdctl: start Start an ejabberd node in
server mode
Feb 8 17:03:59 first ejabberdctl: debug Attach an interactive Erlang
shell to a running ejabberd node
Feb 8 17:03:59 first ejabberdctl: live Start an ejabberd node in
live (interactive) mode
Feb 8 17:03:59 first ejabberdctl: Optional parameters when starting an
ejabberd node:
Feb 8 17:03:59 first ejabberdctl: --config-dir dir Config
ejabberd: /etc/ejabberd
Feb 8 17:03:59 first ejabberdctl: --config file Config
ejabberd: /etc/ejabberd/ejabberd.cfg
Feb 8 17:03:59 first ejabberdctl: --ctl-config file Config
ejabberdctl: /etc/sysconfig/ejabberd
Feb 8 17:03:59 first ejabberdctl: --logs dir Directory for
logs: /var/log/ejabberd
Feb 8 17:03:59 first ejabberdctl: --spool dir Database spool
dir: /var/lib/ejabberd
Feb 8 17:03:59 first ejabberdctl: --node nodename ejabberd node
name: ejabberd
Feb 8 17:03:59 first ejabberd: Stopping ejabberd service: failed
Feb 8 17:12:10 first ejabberdctl: Failed RPC connection to the node
ejabberd@first: nodedown
Feb 8 17:12:10 first ejabberdctl: Commands to start an ejabberd node:
Feb 8 17:12:10 first ejabberdctl: start Start an ejabberd node in
server mode
Feb 8 17:12:10 first ejabberdctl: debug Attach an interactive Erlang
shell to a running ejabberd node
Feb 8 17:12:10 first ejabberdctl: live Start an ejabberd node in
live (interactive) mode
Feb 8 17:12:10 first ejabberdctl: Optional parameters when starting an
ejabberd node:
Feb 8 17:12:10 first ejabberdctl: --config-dir dir Config
ejabberd: /etc/ejabberd
Feb 8 17:12:10 first ejabberdctl: --config file Config
ejabberd: /etc/ejabberd/ejabberd.cfg
Feb 8 17:12:10 first ejabberdctl: --ctl-config file Config
ejabberdctl: /etc/sysconfig/ejabberd
Feb 8 17:12:10 first ejabberdctl: --logs dir Directory for
logs: /var/log/ejabberd
Feb 8 17:12:10 first ejabberdctl: --spool dir Database spool
dir: /var/lib/ejabberd
Feb 8 17:12:10 first ejabberdctl: --node nodename ejabberd node
name: ejabberd
Feb 8 17:12:10 first ejabberd: Stopping ejabberd service: failed
Feb 8 17:13:34 first ejabberdctl: Failed RPC connection to the node
ejabberd@first: nodedown
Feb 8 17:13:34 first ejabberdctl: Commands to start an ejabberd node:
Feb 8 17:13:34 first ejabberdctl: start Start an ejabberd node in
server mode
Feb 8 17:13:34 first ejabberdctl: debug Attach an interactive Erlang
shell to a running ejabberd node
Feb 8 17:13:34 first ejabberdctl: live Start an ejabberd node in
live (interactive) mode
Feb 8 17:13:34 first ejabberdctl: Optional parameters when starting an
ejabberd node:
Feb 8 17:13:34 first ejabberdctl: --config-dir dir Config
ejabberd: /etc/ejabberd
Feb 8 17:13:34 first ejabberdctl: --config file Config
ejabberd: /etc/ejabberd/ejabberd.cfg
Feb 8 17:13:34 first ejabberdctl: --ctl-config file Config
ejabberdctl: /etc/sysconfig/ejabberd
Feb 8 17:13:34 first ejabberdctl: --logs dir Directory for
logs: /var/log/ejabberd
Feb 8 17:13:34 first ejabberdctl: --spool dir Database spool
dir: /var/lib/ejabberd
Feb 8 17:13:34 first ejabberdctl: --node nodename ejabberd node
name: ejabberd
Feb 8 17:13:34 first ejabberd: Stopping ejabberd service: failed
Feb 8 17:13:56 first ejabberd: Starting ejabberd service: succeeded
Feb 8 17:37:06 first ejabberd: Starting ejabberd service: succeeded
Feb 8 17:49:03 first epmd: epmd: node name already occupied ejabberd
Feb 8 17:54:04 first epmd: epmd: node name already occupied ejabberd
выжимка из лога....
Как понимать ситуацию? Почему нода занята а связи нет?
Или пока эрланг крутится сервер реально не остановлен? Почему ни разу не
удалось остановить сервер?
next prev parent reply other threads:[~2014-02-08 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 16:00 dobr
2014-02-08 16:07 ` dobr [this message]
2014-02-08 16:28 ` dobr
2014-02-08 16:49 ` dobr
2014-02-08 17:28 ` Dmitriy Kruglikov
2014-02-08 17:29 ` Anton Gorlov
2014-02-10 13:14 ` Andrii Dobrovol`s`kii
2014-02-10 13:25 ` Dmitriy Kruglikov
2014-02-10 19:54 ` Anton Gorlov
2014-02-19 6:48 ` Вадим Илларионов
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52F6564E.9040502@iop.kiev.ua \
--to=dobr@iop.kiev.ua \
--cc=sysadmins@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux sysadmins discussion
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sysadmins/0 sysadmins/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 sysadmins sysadmins/ http://lore.altlinux.org/sysadmins \
sysadmins@lists.altlinux.org sysadmins@lists.altlinux.ru sysadmins@lists.altlinux.com
public-inbox-index sysadmins
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sysadmins
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git