Bug 968212 - Fdora19:Alpha: dmeventd Child exited with code 1
Summary: Fdora19:Alpha: dmeventd Child exited with code 1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lvm2
Version: 19
Hardware: ppc64
OS: All
unspecified
medium
Target Milestone: ---
Assignee: Peter Rajnoha
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-29 08:40 UTC by IBM Bug Proxy
Modified: 2013-10-18 14:42 UTC (History)
13 users (show)

Fixed In Version: lvm2-2.02.98-12.fc19
Clone Of:
Environment:
Last Closed: 2013-08-23 00:34:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmeventd -V exist status correction. (wrong diff , reattaching the patch) Ignore previous patch ( attachment 79957 ) (432 bytes, text/plain)
2013-05-29 08:40 UTC, IBM Bug Proxy
no flags Details


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 94057 0 None None None Never

Description IBM Bug Proxy 2013-05-29 08:40:35 UTC
== Comment: #0 - MANAS K. NAYAK <maknayak.com> - 2013-05-27 04:15:57 ==
Executing "dmeventd -d " from terminal on Fedora 19 P7 installed LPAR, noticed child gets exited with code 1.
Last command exit status also shows 1.

[root@miz12 ~]# dmeventd -d
Child exited with code 1
[root@miz12 ~]# echo $?
1
[root@miz12 ~]# dmeventd -ddd
Child exited with code 1
[root@miz12 ~]# echo $?
1

Even if for checking version , exit status shows 1.
[root@miz12 ~]# dmeventd -V
dmeventd version: 1.02.77 (2012-10-15)
[root@miz12 ~]# echo $?
1


[root@miz12 ~]# uname -a
Linux miz12.austin.ibm.com 3.9.2-301.fc19.ppc64p7 #1 SMP Mon May 13 09:20:53 MST 2013 ppc64 ppc64 ppc64 GNU/Linux

== Comment: #2 - Onkar N. Mahajan <onmahaja.com> - 2013-05-27 04:34:15 ==
OBSERVATION :
=========

# dmeventd -d
Child exited with code 1
# ps -elf | grep dmeventd | grep -v grep 
5 S root     18044     1  0  80   0 -  7619 poll_s 13:47 ?        00:00:00 dmeventd -d
# kill -9 18044
# dmeventd -d
# ps -elf | grep dmeventd | grep -v grep 
5 S root     18201     1  0  80   0 -  7619 poll_s 14:03 ?        00:00:00 dmeventd -d
# dmeventd -d
Child exited with code 1
# 

Regards,
Onkar

== Comment: #4 - Onkar N. Mahajan <onmahaja.com> - 2013-05-29 04:09:50 ==


== Comment: #5 - Onkar N. Mahajan <onmahaja.com> - 2013-05-29 04:10:47 ==
Hi Manas, 

# daemons/dmeventd/dmeventd -d
# ps -elf | grep dmeventd 
5 S root     28149     1  0  80   0 -   137 poll_s 00:55 ?        00:00:00 daemons/dmeventd/dmeventd -d
0 S root     28151  3018  0  80   0 -  1739 pipe_w 00:55 pts/0    00:00:00 grep --color=auto dmeventd
# daemons/dmeventd/dmeventd -V
dmeventd version: 1.02.77 (2012-10-15)
# echo $?
0
# kill -9 28149
# daemons/dmeventd/dmeventd -V
dmeventd version: 1.02.77 (2012-10-15)
# echo $?
0
# 


I think - the 'dmeventd -d' o/p run the second time must exit with exit status 1. Please correct me here. 
Why would anyone like to run 'dmeventd -d' when there is already a 'dmeventd -d' running ? 

Now, I agree with you that  dmeventd -V must  *always* return exist status 0 - and it does so (see above results) irrespective of the fact that the dmeventd daemon is running/not running.  Please find the patch attached for these results.

Please let me know if these results are acceptable.

Regards, 
Onkar

== Comment: #11 - Onkar N. Mahajan <onmahaja.com> - 2013-05-29 04:32:30 ==

Comment 1 IBM Bug Proxy 2013-05-29 08:40:52 UTC
Created attachment 754262 [details]
dmeventd -V exist status correction. (wrong diff , reattaching the patch) Ignore previous patch ( attachment  79957 )

Comment 2 Peter Rajnoha 2013-05-29 10:56:20 UTC
(In reply to IBM Bug Proxy from comment #0)
> I think - the 'dmeventd -d' o/p run the second time must exit with exit
> status 1. Please correct me here. 

Yes, that must return 1 to indicate failure here as only one instance should be running at a time.

> Now, I agree with you that  dmeventd -V must  *always* return exist status 0
> - and it does so (see above results) irrespective of the fact that the
> dmeventd daemon is running/not running.  Please find the patch attached for
> these results.
> 
> Please let me know if these results are acceptable.
>

Yes, that should be return 0. Thanks for spotting this! Committed upstream.

https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=6ad17fd7129dc7f50c0623181681157faea806a1

Comment 3 Fedora Update System 2013-08-21 08:42:30 UTC
lvm2-2.02.98-12.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/lvm2-2.02.98-12.fc19

Comment 4 Fedora Update System 2013-08-22 00:44:40 UTC
Package lvm2-2.02.98-12.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lvm2-2.02.98-12.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-15098/lvm2-2.02.98-12.fc19
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-08-23 00:34:19 UTC
lvm2-2.02.98-12.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 IBM Bug Proxy 2013-10-18 09:20:34 UTC
------- Comment From rragipal.com 2013-10-18 09:19 EDT-------
This behaviour is working fine in Fedora20 Alpha.

[root@juno-ioxc1-lp3 ras]# uname -a
Linux juno-ioxc1-lp3.austin.ibm.com 3.11.4-301.fc20.ppc64p7 #1 SMP Thu Oct 10 11:24:10 MST 2013 ppc64 ppc64 ppc64 GNU/Linux
[root@juno-ioxc1-lp3 ras]# dmeventd -V ; echo $?
dmeventd version: 1.02.81 (2013-09-23)
[root@juno-ioxc1-lp3 ras]# dmeventd -d ; echo $?
[root@juno-ioxc1-lp3 ras]# ps -ef | grep dmev
root     25147     1  0 04:15 ?        00:00:00 dmeventd -d
root     25149 23938  0 04:15 pts/1    00:00:00 grep --color=auto dmev
[root@juno-ioxc1-lp3 ras]# rpm -qa | grep lvm2
lvm2-libs-2.02.102-1.fc20.ppc64
lvm2-2.02.102-1.fc20.ppc64
[root@juno-ioxc1-lp3 ras]#

Comment 7 IBM Bug Proxy 2013-10-18 14:42:01 UTC
------- Comment From shubgoya.com 2013-10-18 14:32 EDT-------
Closed per comment 21...


Note You need to log in before you can comment on or make changes to this bug.