Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 502361
Summary: | ejabberd init scripts fail to start ejabberd properly | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Benjamin KwiecieĊ <eatinglemur> |
Component: | ejabberd | Assignee: | Peter Lemenkov <lemenkov> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | lemenkov, silfreed |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.0.5-6.el5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-06 20:41:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Benjamin KwiecieĊ
2009-05-24 12:59:53 UTC
(In reply to comment #0) > Description of problem: > How reproducible: > > > Steps to Reproduce: > 1. Specify a hostname and domain other than localhost.localdomain in the Fedora > installer > 2. Install ejabberd (the default config file should be adequate just to load > the server) > 3. Attempt to start ejabberd using the init script Cannot reproduce - I'm able to start ejabberd from init-script and stop it using ejabberdctl and vise versa. And my domainname (hostname -s) is not a simple localhost. However, the idea, to rely in init-script on ejabberdctl completely, sounds interesting - at least we'll clean up things a little. I'll try to remove all direct erlang invocations in init-script. ejabberd-2.0.5-6.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/ejabberd-2.0.5-6.el5 ejabberd-2.0.5-6.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/ejabberd-2.0.5-6.fc10 ejabberd-2.0.5-6.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/ejabberd-2.0.5-6.fc11 ejabberd-2.0.5-6.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update ejabberd'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/EL-5/FEDORA-EPEL-2009-0351 ejabberd-2.0.5-6.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update ejabberd'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-9021 ejabberd-2.0.5-6.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update ejabberd'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-9037 ejabberd-2.0.5-6.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. ejabberd-2.0.5-6.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. ejabberd-2.0.5-6.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report. |