[Bug 1117450] New: needs network-online.target instead of network.target
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1117450
Bug ID: 1117450
Summary: needs network-online.target instead of network.target
Product: Fedora
Version: 20
Component: ejabberd
Assignee: lemenkov(a)gmail.com
Reporter: benfell(a)parts-unknown.org
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, jkaluza(a)redhat.com,
lemenkov(a)gmail.com, martin(a)laptop.org
Description of problem: silently fails to open assigned interface
Version-Release number of selected component (if applicable): 2.1.13-7.fc20
How reproducible: 100%
Steps to Reproduce:
1. reboot system with ejabberd enabled
2.
3.
Actual results: systemctl sees ejabberd as having successfully started, but it
is inaccessible to clients.
Expected results: clients are able to connect to ejabberd
Additional info: This appears to be of similar origin to bug #116538 (postfix).
I am working around the problem with the following lines in ejabberd.service:
Requires=network-online.target
After=network-online.target
This problem also afflicts nsd, but nsd fails in a way that systemctl
recognizes and reports. To my knowledge, ejabberd, nsd, and postfix are the
only services affected on my server.
This is a server using static addresses. It does not use NetworkManager.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 8 months
[Bug 1036359] New: ejabberd logs not reopened after rotation
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1036359
Bug ID: 1036359
Summary: ejabberd logs not reopened after rotation
Product: Fedora
Version: 20
Component: ejabberd
Assignee: lemenkov(a)gmail.com
Reporter: redhat(a)subs.maneos.org
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, jkaluza(a)redhat.com,
lemenkov(a)gmail.com, martin(a)laptop.org
Description of problem:
Version-Release number of selected component (if applicable):
ejabberd-2.1.13-7.fc20.x86_64
How reproducible:
Steps to Reproduce:
1. Make sure ejabberd is running and logrotate is enabled.
2. Wait until logrotate runs.
3. Check contents of /var/log/ejabberd/ejabberd.log.
Actual results:
0 size file that never gets updated.
Expected results:
File containing log entries for events as they occur.
Additional info:
/etc/logrotate.d/ejabberd is trying to run /usr/sbin/ejabberdctl, but
ejabberdctl is installed in /usr/bin now.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 8 months