Current status: No update.
eJabberD won't start properly.
I checked the eJabberD log files, and found nothing of value to me,
so I wrote a ticket for our IT staff who administrates that server
at 10:14 today.
Now it's 8 hours later and I only got an automatic reply with a
ticket ID, but no actual response.
Ironically, today was monthly "maintenance day" in our department,
which was also the reason I rebooted the server today.
(If I hadn't rebooted the server, our staff would have done it
four hours later.)
At least them being busy could explain why I got no answer yet,
Although that's little comfort.
Just in case anyone has an idea, which I could then forward to our
IT staff, here is the ejabberd.log from the time around the reboot:
-----
2017-03-01 10:03:16.695 [info] <0.22809.2>@mod_muc_room:terminate:846 Stopping
MUC room saros-c...@conference.saros-con.imp.fu-berlin.de
2017-03-01 10:03:16.696 [info] <0.14581.30>@mod_muc_room:terminate:846 Stopping
MUC room saros_2011817...@conference.saros-con.imp.fu-berlin.de
2017-03-01 10:03:16.696 [info] <0.14287.30>@mod_muc_room:terminate:846 Stopping
MUC room saros_1534893...@conference.saros-con.imp.fu-berlin.de
2017-03-01 10:03:16.696 [info] <0.8708.30>@mod_muc_room:terminate:846 Stopping
MUC room saros_1313939...@conference.saros-con.imp.fu-berlin.de
2017-03-01 10:03:16.723 [info] <0.11645.29>@mod_muc_room:terminate:846 Stopping
MUC room saros_2111065...@conference.saros-con.imp.fu-berlin.de
2017-03-01 10:03:16.797 [error] <0.394.0> Supervisor
'ejabberd_mod_muc_sup_saros-con.imp.fu-berlin.de' had child undefined started
with mod_muc_room:start_link() at undefined exit with reason shutdown in
context shutdown_error
2017-03-01 10:04:36.116 [info] <0.7.0> Application lager started on node
'ejabb...@saros-con.imp.fu-berlin.de'
2017-03-01 10:04:36.116 [error] <0.38.0>@ejabberd_app:write_pid_file:219 Cannot
write PID file /run/ejabberd/ejabberd.pid
Reason: enoent
2017-03-01 10:04:36.116 [error] <0.37.0> CRASH REPORT Process <0.37.0> with 0
neighbours exited with reason: bad return value
{cannot_write_pid_file,"/run/ejabberd/ejabberd.pid",enoent} from
ejabberd_app:start(normal, []) in application_master:init/4 line 133
2017-03-01 10:04:36.117 [info] <0.7.0> Application ejabberd exited with reason:
bad return value {cannot_write_pid_file,"/run/ejabberd/ejabberd.pid",enoent}
from ejabberd_app:start(normal, [])
-----
The reboot happened between 10:03:16 and 10:04:36.
(And I apparently killed five running Saros sessions with it.)
Cheers,
Franz
-----Original Message-----
From: Zieris, Franz [mailto:franz.zie...@fu-berlin.de]
Sent: Wednesday, March 01, 2017 10:09 AM
To: dpp-devel@lists.sourceforge.net
Subject: Re: [DPP-Devel] Build server reboot: 2017-03-01 at 10:00 CET
Gerrit: up and running
Jenkins: up and running
SonarQube: up and running
eJabberD: not reachable
*Sigh*,
I'm on it.
Franz
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
