Bug 596686

Summary:	service ejabberd stop doesn't kill epmd which prevents new start of ejabberd
Product:	[Fedora] Fedora EPEL	Reporter:	Matěj Cepl <mcepl>
Component:	ejabberd	Assignee:	Peter Lemenkov <lemenkov>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	el5	CC:	lemenkov, mcepl, mmahut
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	ejabberd-2.1.4-1.el5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-07-21 20:00:16 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 Matěj Cepl 2010-05-27 10:09:42 UTC

Description of problem:
[root@luther ~]# service ejabberd stop
[root@luther ~]# pgrep -f -l erl
19870 /usr/lib/erlang/erts-5.6.5/bin/epmd -daemon
[root@luther ~]# 

Version-Release number of selected component (if applicable):
ejabberd-2.1.2-4.el5

How reproducible:
100%

Comment 1 Peter Lemenkov 2010-06-12 14:19:54 UTC

Could you, please, try with latest ejabberd:

https://admin.fedoraproject.org/updates/ejabberd-2.1.4-1.el5

In fact, ejabberd shouldn't kill epmd (because there may be other erlang applications running, which are using epmd), but it should cleanly unregister itself.

Comment 2 Matěj Cepl 2010-06-12 15:09:43 UTC

(In reply to comment #1)
> In fact, ejabberd shouldn't kill epmd (because there may be other erlang
> applications running, which are using epmd), but it should cleanly unregister
> itself.

Sure, I don't anything against poor epmd, except that it prevents (prevented) my ejabberd from running.

Comment 3 Matěj Cepl 2010-06-12 15:29:35 UTC

Looks good:

[root@luther ~]# service ejabberd restart
Shutting down ejabberd:                                    [  OK  ]
Starting ejabberd:                                         [  OK  ]
[root@luther ~]# service ejabberd status
The node ejabberd@luther is started with status: started
ejabberd 2.1.4 is running in that node
[root@luther ~]# 

Thank you!

Comment 4 Fedora Update System 2010-06-12 15:35:41 UTC

ejabberd-2.1.4-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/ejabberd-2.1.4-1.fc13

Comment 5 Fedora Update System 2010-06-12 15:35:48 UTC

ejabberd-2.1.4-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/ejabberd-2.1.4-1.fc12

Comment 6 Fedora Update System 2010-06-12 15:36:01 UTC

ejabberd-2.1.4-1.el5 has been submitted as an update for Fedora EPEL 5.
http://admin.fedoraproject.org/updates/ejabberd-2.1.4-1.el5

Comment 7 Fedora Update System 2010-06-14 21:53:33 UTC

ejabberd-2.1.4-1.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/ejabberd-2.1.4-1.el5

Comment 8 Fedora Update System 2010-07-14 22:59:47 UTC

ejabberd-2.1.4-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2010-07-14 23:05:19 UTC

ejabberd-2.1.4-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2010-07-21 20:00:11 UTC

ejabberd-2.1.4-1.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.