Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 861088

Summary: [autofs] Some times its impossible to access /net mounts
Product: Red Hat Enterprise Linux 6 Reporter: Kiril Nesenko <knesenko>
Component: autofsAssignee: Ian Kent <ikent>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: high    
Version: 6.3CC: dfediuck, ikent, slipcon
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-22 08:54:58 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:
Attachments:
Description Flags
logs none

Description Kiril Nesenko 2012-09-27 13:32:36 UTC
Created attachment 618069 [details]
logs

Description of problem:
Some times autofs service fails and its impossible to access /net mounts.

Sep 27 11:57:36 vm-17-158 engine-service[27970]: Started engine process 27971.
Sep 27 12:10:57 vm-17-158 automount[29006]: rpc_get_exports_proto
Sep 27 12:10:57 vm-17-158 kernel: automount[29116]: segfault at 28 ip 00007f59f0500862 sp 00007f59f3ffe960 error 4 in lookup_hosts.so[7f59f04f7000+1c000]
Sep 27 12:18:34 vm-17-158 automount[29635]: rpc_get_exports_proto
Sep 27 12:18:34 vm-17-158 kernel: automount[29647]: segfault at 28 ip 00007f34a49f5862 sp 00007f34a84f3960 error 4 in lookup_hosts.so[7f34a49ec000+1c000]
Sep 27 12:19:21 vm-17-158 automount[29693]: rpc_get_exports_proto
Sep 27 12:19:21 vm-17-158 kernel: automount[29711]: segfault at 28 ip 00007f25c13d1862 sp 00007f25c4ecf960 error 4 in lookup_hosts.so[7f25c13c8000+1c000]
Sep 27 12:42:07 vm-17-158 puppet-agent[30874]: Reopening log files
Sep 27 12:42:25 vm-17-158 puppet-agent[30874]: (/Stage[main]/Autofs::Service/Service[autofs]/ensure) ensure changed 'stopped' to 'running'
Sep 27 12:42:27 vm-17-158 puppet-agent[30874]: Finished catalog run in 15.42 seconds
Sep 27 12:54:02 vm-17-158 puppet-agent[31974]: Reopening log files
Sep 27 12:54:20 vm-17-158 puppet-agent[31974]: Finished catalog run in 13.03 seconds
Sep 27 13:00:13 vm-17-158 automount[31273]: rpc_get_exports_proto
Sep 27 13:00:20 vm-17-158 engine-service[32671]: Waiting up to 10 seconds for engine process 27971 to finish.
Sep 27 13:00:21 vm-17-158 engine-service[32671]: Stopped engine process 27971.
Sep 27 13:00:34 vm-17-158 automount[31273]: rpc_get_exports_proto


Version-Release number of selected component (if applicable):
[root@jenkins-automation-rpm-vm02 ~]# rpm -q autofs
autofs-5.0.5-54.el6.x86_64
[root@jenkins-automation-rpm-vm02 ~]# uname -a 
Linux jenkins-automation-rpm-vm02.eng.lab.tlv.redhat.com 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
[root@jenkins-automation-rpm-vm02 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.3 (Santiago)
[root@jenkins-automation-rpm-vm02 ~]# 


How reproducible:
Some times

Steps to Reproduce:
1. 
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Ian Kent 2012-09-27 14:50:29 UTC
I believe that the package at:
http://people.redhat.com/~ikent/autofs-5.0.5-55.el6
will resolve your problem, please test it and let me know how
it goes.

Comment 3 RHEL Program Management 2012-12-14 07:43:27 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 4 Ian Kent 2013-02-22 08:54:58 UTC
(In reply to comment #2)
> I believe that the package at:
> http://people.redhat.com/~ikent/autofs-5.0.5-55.el6
> will resolve your problem, please test it and let me know how
> it goes.

The change in this package has been included in RHEL-6.4.
It should resolve the problem described here.
If that isn't the case then re-open this bug.