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 1085477

Summary:	fcoemon: Failed to connect to lldpad
Product:	Red Hat Enterprise Linux 6	Reporter:	p3tr <psklenar>
Component:	fcoe-utils	Assignee:	Chris Leech <cleech>
Status:	CLOSED WONTFIX	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.6	CC:	bubrown, buhrt, cww, mhernon
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-04 18:30:44 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 p3tr 2014-04-08 17:02:15 UTC

Description of problem:
there is an error which is repeating each 10 seconds
fcoemon: Failed to connect to lldpad

Version-Release number of selected component (if applicable):
fcoe-utils-1.0.28-3.el6.i686
lldpad-0.9.46-2.el6.i686

How reproducible:
always with my machine

Steps to Reproduce:
1. defualt installation with desktop, no additional setting to fcoe
2. after few days of running there is such an 'error 111 Connection refused'

Actual results:
Apr  8 18:53:27 localhost fcoemon: error 111 Connection refused
Apr  8 18:53:27 localhost fcoemon: Failed to connect to lldpad
Apr  8 18:53:37 localhost fcoemon: error 111 Connection refused
Apr  8 18:53:37 localhost fcoemon: Failed to connect to lldpad
[root@localhost ~]# /etc/init.d/lldpad status
lldpad je zastaven
[root@localhost ~]# /etc/init.d/fcoe status
/usr/sbin/fcoemon -- RUNNING, pid=1444
No interfaces created.
[root@localhost ~]# rpm -qf /etc/init.d/fcoe 
fcoe-utils-1.0.28-3.el6.i686
[root@localhost ~]# /etc/init.d/lldpad status
lldpad je zastaven
[root@localhost ~]# rpm -qf /etc/init.d/lldpad
lldpad-0.9.46-2.el6.i686

[root@localhost ~]# cat  /var/log/messages | grep 'fcoemon: Failed to connect to lldpad' | wc -l
13559


Expected results:
no error each 10 seconds

Additional info:

Comment 2 Jeff Buhrt 2015-07-01 21:10:45 UTC

I see this now after upgrading to Fedora 22.

Try:
systemctl status lldpad.service

I get:
● lldpad.service - Link Layer Discovery Protocol Agent Daemon.
   Loaded: loaded (/usr/lib/systemd/system/lldpad.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Wed 2015-07-01 16:50:20 EDT; 14min ago
  Process: 1272 ExecStart=/usr/sbin/lldpad -t (code=exited, status=1/FAILURE)
 Main PID: 1272 (code=exited, status=1/FAILURE)

Jul 01 16:50:20 jtosh.aftinc.net systemd[1]: Started Link Layer Discovery Protocol Agent Daemon..
Jul 01 16:50:20 jtosh.aftinc.net systemd[1]: Starting Link Layer Discovery Protocol Agent Daemon....
Jul 01 16:50:20 jtosh.aftinc.net lldpad[1272]: error getting shm pid
Jul 01 16:50:20 jtosh.aftinc.net systemd[1]: lldpad.service: main process exited, code=exited, status=1/FAILURE
Jul 01 16:50:20 jtosh.aftinc.net systemd[1]: Unit lldpad.service entered failed state.
Jul 01 16:50:20 jtosh.aftinc.net systemd[1]: lldpad.service failed.
Jul 01 16:50:20 jtosh.aftinc.net systemd[1]: start request repeated too quickly for lldpad.service
Jul 01 16:50:20 jtosh.aftinc.net systemd[1]: Failed to start Link Layer Discovery Protocol Agent Daemon..
Jul 01 16:50:20 jtosh.aftinc.net systemd[1]: lldpad.service failed.

If so try:
# systemctl restart lldpad.service

I assume you will get a SELinux denial.

Try:
# setenforce 0
# systemctl restart lldpad.service
# setenforce 1
# journalctl -f
 (should now be silent until the next reboot or restart of lldpad)

If it is 'clean', please make a note on the ticket.

I logged a Fedora ticket:
https://bugzilla.redhat.com/show_bug.cgi?id=1236431

Comment 4 Chris Leech 2015-10-28 17:51:31 UTC

(In reply to Jeff Buhrt from comment #2)
> I see this now after upgrading to Fedora 22.

Thanks for that, I'll get Fedora updated to deal with the SELinux issue.

I don't think it's the same as the original issue here, which is that after some time lldpad seems to have exited for some reason while fcoemon is still running and trying to connect to it.

Comment 5 Chris Williams 2016-08-04 18:30:44 UTC

When Red Hat shipped 6.8 on May 10, 2016 RHEL 6 entered Production Phase 2. 
https://access.redhat.com/support/policy/updates/errata#Production_2_Phase
That means only "Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released"
This BZ is now going to be closed as it does not appear to meet Phase 2 criteria. 
If this BZ is deemed critical to the customer please open a support case in the Red Hat Customer Portal and ask that this BZ be re-opened.