Bug 1200946

Summary: Unknown lvalue 'RemoveOnStop' in section 'Socket' (dm-event.socket:10 and vm2-lvmetad.socket:9)
Product: Red Hat Enterprise Linux 7 Reporter: Robert Scheck <redhat-bugzilla>
Component: lvm2Assignee: Peter Rajnoha <prajnoha>
lvm2 sub component: Default / Unclassified QA Contact: cluster-qe <cluster-qe>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: agk, cmarthal, cristi.falcas, erik, Frodox, hartsjc, heinzm, jbrassow, mnavrati, msnitzer, mvermaes, nperic, pekkas, prajnoha, prockai, rabdelmassih, robert.scheck, vchepkov, zkabelac
Version: 7.1Keywords: Reopened
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.02.125-1.el7 Doc Type: Bug Fix
Doc Text:
Previously, the dm-event.socket and lvm2-lvmetad.socket systemd units incorrectly referenced the "RemoveOnStop" property, which was not available in the previous version of systemd. As a consequence, the "Unknown lvalue 'RemoveOnStop' in section 'Socket'" error occurred at boot time or when systemd reloaded its units. With this update, "RemoveOnStop" is recognized, so the dm-event.socket and lvm2-lvmetad.socket can reference this property, and the error message no longer occurs.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 12:46:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Robert Scheck 2015-03-11 17:02:50 UTC 
Description of problem:
Mar 11 17:52:36 tux yum[7093]: Installed: bacula-storage-5.2.13-18.el7.x86_64
Mar 11 17:52:36 tux systemd: Reloading.
Mar 11 17:52:36 tux systemd: [/usr/lib/systemd/system/dm-event.socket:10] Unknown lvalue 'RemoveOnStop' in section 'Socket'
Mar 11 17:52:36 tux systemd: [/usr/lib/systemd/system/lvm2-lvmetad.socket:9] Unknown lvalue 'RemoveOnStop' in section 'Socket'

Version-Release number of selected component (if applicable):
device-mapper-event-1.02.93-3.el7.x86_64
systemd-208-20.el7.x86_64

How reproducible:
Everytime, just install a package which causes a systemd unit-files reload
such as bacula-storage (by delivering a unit file).

Actual results:
Log lines with "Unknown lvalue 'RemoveOnStop' in section 'Socket'".

Expected results:
No log lines with "Unknown lvalue 'RemoveOnStop' in section 'Socket'".
Comment 1 Robert Scheck 2015-03-11 17:04:21 UTC 
Cross-filed case 01377445 on the Red Hat customer portal.
Comment 3 Peter Rajnoha 2015-03-12 08:07:01 UTC 
RemoveOnStop is recognized only in systemd >= 214. Its purpose is to do a proper cleanup and remove any existing sockets/fifos if the socket unit is stopped.

The system version in 7.1 is at 208. If there's an update for systemd in 7.2 which includes a rebase to that new version (214), this warning message will dissapear. If systemd is not updated to 214 or higher, I'll remove the RemoveOnStop option in 7.2 (in the dm-event.socket unit). I'll keep this bz open till then to decide.

As such, this should be harmless, just producing a warning message that the option in dm-event.socket systemd unit is not recognized and hence ignored by systemd.
Comment 4 Robert Scheck 2015-03-14 18:35:37 UTC 
Peter, I guess this applies for dm-event.socket and lvm2-lvmetad.socket,
even you just named dm-event.socket?
Comment 5 Peter Rajnoha 2015-03-16 09:47:26 UTC 
(In reply to Robert Scheck from comment #4)
> Peter, I guess this applies for dm-event.socket and lvm2-lvmetad.socket,
> even you just named dm-event.socket?

Yes, indeed! Thanks for reminding me.
Comment 6 Peter Rajnoha 2015-04-24 09:28:14 UTC 
OK, systemd-219-1.el7 (or higher) is currently prepared for 7.2. This version is recent enought to recognize the "RemoveOnStop" option. Marking this as resolved in current release.
Comment 7 Robert Scheck 2015-06-30 10:18:48 UTC 
Well, 7.2 != 7.1. The current available stable release is 7.1, so this is not 
fixed yet, reopening.
Comment 12 Erik Logtenberg 2015-08-10 15:12:17 UTC 
When is this fix scheduled for release?
Comment 13 Corey Marthaler 2015-10-08 16:48:21 UTC 
Fix verified in the latest rpms. No "Unknown lvalue..." messages when installing.



3.10.0-319.el7.x86_64
lvm2-2.02.130-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
lvm2-libs-2.02.130-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
lvm2-cluster-2.02.130-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
device-mapper-1.02.107-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
device-mapper-libs-1.02.107-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
device-mapper-event-1.02.107-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
device-mapper-event-libs-1.02.107-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
device-mapper-persistent-data-0.5.5-1.el7    BUILT: Thu Aug 13 09:58:10 CDT 2015
cmirror-2.02.130-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015
sanlock-3.2.4-1.el7    BUILT: Fri Jun 19 12:48:49 CDT 2015
sanlock-lib-3.2.4-1.el7    BUILT: Fri Jun 19 12:48:49 CDT 2015
lvm2-lockd-2.02.130-2.el7    BUILT: Tue Sep 15 07:15:40 CDT 2015



Oct  8 11:44:38 host-116 yum[12069]: Installed: bacula-libs-5.2.13-23.1.el7.x86_64
Oct  8 11:44:38 host-116 yum[12069]: Installed: bacula-common-5.2.13-23.1.el7.x86_64
Oct  8 11:44:39 host-116 yum[12069]: Installed: postgresql-libs-9.2.13-1.el7_1.x86_64
Oct  8 11:44:39 host-116 yum[12069]: Installed: bacula-libs-sql-5.2.13-23.1.el7.x86_64
Oct  8 11:44:40 host-116 systemd: Reloading.
Oct  8 11:44:40 host-116 systemd: Configuration file /usr/lib/systemd/system/beah-fwd-backend.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct  8 11:44:40 host-116 systemd: Configuration file /usr/lib/systemd/system/beah-beaker-backend.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct  8 11:44:40 host-116 systemd: Configuration file /usr/lib/systemd/system/beah-srv.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct  8 11:44:40 host-116 systemd: Configuration file /usr/lib/systemd/system/auditd.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Oct  8 11:44:40 host-116 systemd: Configuration file /usr/lib/systemd/system/wpa_supplicant.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct  8 11:44:40 host-116 yum[12069]: Installed: mt-st-1.1-14.el7.x86_64
Oct  8 11:44:40 host-116 systemd: Reloading.
Oct  8 11:44:40 host-116 systemd: Configuration file /usr/lib/systemd/system/beah-fwd-backend.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct  8 11:44:40 host-116 systemd: Configuration file /usr/lib/systemd/system/beah-beaker-backend.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct  8 11:44:40 host-116 systemd: Configuration file /usr/lib/systemd/system/beah-srv.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct  8 11:44:40 host-116 systemd: Configuration file /usr/lib/systemd/system/auditd.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Oct  8 11:44:40 host-116 systemd: Configuration file /usr/lib/systemd/system/wpa_supplicant.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Oct  8 11:44:40 host-116 yum[12069]: Installed: bacula-storage-5.2.13-23.1.el7.x86_64
Comment 14 errata-xmlrpc 2015-11-19 12:46:21 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2147.html