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 768555 - lldpad initscript does not kill lldpad before starting it
Summary: lldpad initscript does not kill lldpad before starting it
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lldpad
Version: 6.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 6.3
Assignee: Petr Šabata
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 813952
Blocks: 820002 822377
TreeView+ depends on / blocked
 
Reported: 2011-12-17 00:56 UTC by Eric Multanen
Modified: 2012-07-23 22:59 UTC (History)
14 users (show)

Fixed In Version: lldpad-0.9.43-13.el6
Doc Type: Bug Fix
Doc Text:
The lldpad tool is initially invoked by initrd during the boot process to support Fibre Channel over Ethernet (FCoE) boot from a Storage Area Network (SAN). The runtime lldpad init script did not kill lldpad before restarting it after system boot. Consequently, lldpad could not be started normally after system boot. With this update, the lldpad init script now contains the "-k" option to terminate the first instance of lldpad that was started during system boot.
Clone Of:
Environment:
Last Closed: 2012-06-20 14:14:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Kill lldpad before starting it (266 bytes, patch)
2011-12-21 13:31 UTC, Petr Šabata 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0901 0 normal SHIPPED_LIVE lldpad bug fix and enhancement update 2012-06-19 20:47:01 UTC

Description Eric Multanen 2011-12-17 00:56:24 UTC 
Description of problem:
lldpad is initially invoked from initrd during boot to support FCoE boot from SAN.  The runtime initscript should kill this instance of lldpad by invoking 'lldpad -k' before starting up lldpad normally ('lldpad -d').  This functionality is present in the RHEL6.1 initscript but is not longer present in RHEL6.2.

How reproducible:
always

Steps to Reproduce:
1. Enable and Configure FCoE Boot Option Rom to Boot From LUN
2. Install RHEL6.2 on LUN
3. On successful boot, check status of lldpad service.

  
Actual results:
Something like the following will appear during startup:

Starting lldpad: bind(AF_LOCAL): Address already in use [FAILED]

Expected results:
Starting lldpad: [ OK ]

Additional info:
Comment 2 Petr Šabata 2011-12-21 13:31:46 UTC 
Created attachment 549025 [details]
Kill lldpad before starting it
Comment 5 Petr Šabata 2012-01-04 14:42:31 UTC 
Tagged as lldpad-0_9_43-13_el6
Comment 8 kavindya.s.deegala 2012-04-18 21:44:49 UTC 
RHEL 6.3 BZ 813952 blocks retesting this BZ with RHEL 6.3 Alpha.
Comment 9 Robert Love 2012-04-18 21:50:34 UTC 
Intel has not verified this BZ because we are blocked on 813952. Should we keep this in a VERIFIED state?
Comment 10 Robert Love 2012-05-16 16:34:20 UTC 
We were looking for this in 6.2. It's a problem for boot because the initrd lldpad isn't killed when the runtime one comes online by way of the init script. This is a problem for certifications that require us to test on hosts that are booted off of FCoE LUNs. Problems arise when there are two lldpad instances running and the certification suite requires lldp re-configuration. The system becomes unreliable becuase there are two lldpad daemons trying to manage the same system.
Comment 11 Robert Love 2012-05-16 16:36:24 UTC 
Just to be clear. I am requresting that we get this fix into 6.2.z because it blocks certification.
Comment 13 Eliska Slobodova 2012-05-28 11:22:07 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The lldpad tool is initially invoked by initrd during the boot process to support Fibre Channel over Ethernet (FCoE) boot from a Storage Area Network (SAN). The runtime lldpad init script did not kill lldpad before restarting it after system boot. Consequently, lldpad could not be started normally after system boot. With this update, the lldpad init script now contains the "-k" option to terminate the first instance of lldpad that was started during system boot.
Comment 14 errata-xmlrpc 2012-06-20 14:14:45 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.

http://rhn.redhat.com/errata/RHBA-2012-0901.html
Comment 15 kavindya.s.deegala 2012-07-23 22:59:20 UTC 
Verified by Intel.
Note You need to log in before you can comment on or make changes to this bug.