RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1712646 - [blkmapd] systemd: Can't open PID file /var/run/blkmapd.pid (yet?) after start: No such file or directory
Summary: [blkmapd] systemd: Can't open PID file /var/run/blkmapd.pid (yet?) after star...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nfs-utils
Version: 7.7
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Yongcheng Yang
URL:
Whiteboard:
Depends On:
Blocks: 1753828
TreeView+ depends on / blocked
 
Reported: 2019-05-22 03:10 UTC by Yongcheng Yang
Modified: 2021-03-15 07:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1753828 (view as bug list)
Environment:
Last Closed: 2021-03-15 07:36:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Yongcheng Yang 2019-05-22 03:10:10 UTC 
Description of problem:

Always get the following warning in rhel7 if restarting nfs-blkmap.service several times:
"
systemd: Can't open PID file /var/run/blkmapd.pid (yet?) after start: No such file or directory
"

Version-Release number of selected component (if applicable):
nfs-utils-1.3.0-0.63.el7
(This problem does *not* exist in rhel8)

How reproducible:
easy && always

Steps to Reproduce:
1. $ modprobe blocklayoutdriver
2. Repeats "systemctl restart nfs-blkmap"
3. $ systemctl status nfs-blkmap

Actual results:
[root@intel-s3e36-01 ~]# modprobe blocklayoutdriver
[root@intel-s3e36-01 ~]# systemctl start nfs-blkmap
[root@intel-s3e36-01 ~]# systemctl status nfs-blkmap
● nfs-blkmap.service - pNFS block layout mapping daemon
   Loaded: loaded (/usr/lib/systemd/system/nfs-blkmap.service; disabled; vendor preset: disabled)
   Active: active (running) since Tue 2019-05-21 06:23:27 EDT; 4s ago
  Process: 17348 ExecStart=/usr/sbin/blkmapd $BLKMAPDARGS (code=exited, status=0/SUCCESS)
 Main PID: 17349 (blkmapd)
   CGroup: /system.slice/nfs-blkmap.service
           └─17349 /usr/sbin/blkmapd

May 21 06:23:27 intel-s3e36-01.rhts.eng.nay.redhat.com systemd[1]: Starting pNFS block layout mapping daemon...
May 21 06:23:27 intel-s3e36-01.rhts.eng.nay.redhat.com systemd[1]: Started pNFS block layout mapping daemon.
[root@intel-s3e36-01 ~]# systemctl restart nfs-blkmap
[root@intel-s3e36-01 ~]# systemctl restart nfs-blkmap
[root@intel-s3e36-01 ~]# systemctl status nfs-blkmap
● nfs-blkmap.service - pNFS block layout mapping daemon
   Loaded: loaded (/usr/lib/systemd/system/nfs-blkmap.service; disabled; vendor preset: disabled)
   Active: active (running) since Tue 2019-05-21 06:23:40 EDT; 1s ago
  Process: 17375 ExecStart=/usr/sbin/blkmapd $BLKMAPDARGS (code=exited, status=0/SUCCESS)
 Main PID: 17364 (code=exited, status=1/FAILURE)
   CGroup: /system.slice/nfs-blkmap.service
           └─17376 /usr/sbin/blkmapd

May 21 06:23:40 intel-s3e36-01.rhts.eng.nay.redhat.com systemd[1]: Starting pNFS block layout mapping daemon...
May 21 06:23:40 intel-s3e36-01.rhts.eng.nay.redhat.com systemd[1]: Can't open PID file /var/run/blkmapd.pid (yet?) after start: No such file or directory
May 21 06:23:40 intel-s3e36-01.rhts.eng.nay.redhat.com systemd[1]: Started pNFS block layout mapping daemon.
[root@intel-s3e36-01 ~]# cat /var/run/blkmapd.pid
17376
[root@intel-s3e36-01 ~]# ps 17376
  PID TTY      STAT   TIME COMMAND
17376 ?        Ss     0:00 /usr/sbin/blkmapd
[root@intel-s3e36-01 ~]# systemctl restart nfs-blkmap
[root@intel-s3e36-01 ~]# systemctl status nfs-blkmap
● nfs-blkmap.service - pNFS block layout mapping daemon
   Loaded: loaded (/usr/lib/systemd/system/nfs-blkmap.service; disabled; vendor preset: disabled)
   Active: active (running) since Tue 2019-05-21 06:24:13 EDT; 2s ago
  Process: 17403 ExecStart=/usr/sbin/blkmapd $BLKMAPDARGS (code=exited, status=0/SUCCESS)
 Main PID: 17364 (code=exited, status=1/FAILURE)
   CGroup: /system.slice/nfs-blkmap.service
           └─17404 /usr/sbin/blkmapd

May 21 06:24:13 intel-s3e36-01.rhts.eng.nay.redhat.com systemd[1]: Starting pNFS block layout mapping daemon...
May 21 06:24:13 intel-s3e36-01.rhts.eng.nay.redhat.com systemd[1]: Can't open PID file /var/run/blkmapd.pid (yet?) after start: No such file or directory
May 21 06:24:13 intel-s3e36-01.rhts.eng.nay.redhat.com systemd[1]: Started pNFS block layout mapping daemon.
[root@intel-s3e36-01 ~]# ps `cat /var/run/blkmapd.pid`
  PID TTY      STAT   TIME COMMAND
17404 ?        Ss     0:00 /usr/sbin/blkmapd
[root@intel-s3e36-01 ~]# 
[root@intel-s3e36-01 ~]# rpm -q nfs-utils
nfs-utils-1.3.0-0.63.el7.x86_64


Expected results:
No warning


Additional info:

There're several patches in upstream for /nfs-utils/utils/blkmapd/device-discovery.c which are not in rhel7 yet.

E.g.

commit 03269547a85cadeed35994d8ef6ca75a92198458
Author: Steve Dickson <steved>
Date:   Tue Mar 6 13:47:04 2018 -0500

    Removed -Werror=unused-result warnings.

commit d4b2d066b0dac218fbd1471492b7575d55a413e5
Author: Kinglong Mee <kinglongmee>
Date:   Wed Jul 20 11:08:29 2016 -0400

    blkmapd: unlink pid file when error out
    
    Fix some error out without unlink pid file.

commit 6e79a74d7936fc1d1bbe20e2a7abd6def40c00ea
Author: Kinglong Mee <kinglongmee>
Date:   Wed Jul 20 11:02:03 2016 -0400

    blkmapd: Let running correctly when pid file exists
    
    Blkmapd cannot run until blkmapd.pid is unlinked.
    This patch lets checking exists based on lockf without stat.
Comment 3 Yongcheng Yang 2019-09-20 02:50:24 UTC 
(In reply to Yongcheng Yang from comment #0)
> ...
> Version-Release number of selected component (if applicable):
> nfs-utils-1.3.0-0.63.el7
> (This problem does *not* exist in rhel8)

Now scratch that ^^^^^^^^^ RHEL8 also has this warning.

I'm cloning this to rhel8 now.
Comment 4 Doug Wussler 2019-12-13 17:54:17 UTC 
We also get this message from systemd when starting tac_plus, an old code base from Shrubbery Networks, Inc.
Type=forking
PIDFile=/run/tac/tac_plus.pid

systemd[1]: Starting TACACS+ Daemon...
systemd[1]: Can't open PID file /run/tac/tac_plus.pid (yet?) after start: No such file or directory
systemd[1]: Started TACACS+ Daemon.


But we do not get the message when starting named, the most recent BIND code base from ISC.
Type=forking
PIDFile=/run/named/named.pid

systemd[1]: Starting Berkeley Internet Name Domain (DNS)...
systemd[1]: Started Berkeley Internet Name Domain (DNS).


If we comment out the PIDFile setting for tac_plus, the service will not start reliably.  It just fails to start and gives no error message.  With repeated attempts it will eventually start.

We are running RHEL 7.7 with all the most recent patches.
Comment 7 RHEL Program Management 2021-03-15 07:36:15 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.