Description of problem: [root@storageqe-16 log]# systemctl start fcoe.service Job for fcoe.service failed because the control process exited with error code. See "systemctl status fcoe.service" and "journalctl -xe" for details. [root@storageqe-16 log]# systemctl status fcoe.service ● fcoe.service - Open-FCoE Inititator. Loaded: loaded (/usr/lib/systemd/system/fcoe.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2020-10-29 05:17:18 EDT; 12s ago Process: 9556 ExecStartPre=/sbin/modprobe -qa $SUPPORTED_DRIVERS (code=exited, status=0/SUCCESS) Process: 9557 ExecStart=/usr/sbin/fcoemon $FCOEMON_OPTS (code=exited, status=1/FAILURE) CPU: 6ms Oct 29 05:17:18 storageqe-16.sqe.lab.eng.bos.redhat.com fcoemon[9557]: Usage: fcoemon Oct 29 05:17:18 storageqe-16.sqe.lab.eng.bos.redhat.com fcoemon[9557]: [-f|--foreground] Oct 29 05:17:18 storageqe-16.sqe.lab.eng.bos.redhat.com fcoemon[9557]: [-d|--debug=yes|no] Oct 29 05:17:18 storageqe-16.sqe.lab.eng.bos.redhat.com fcoemon[9557]: [-l|--legacy] Oct 29 05:17:18 storageqe-16.sqe.lab.eng.bos.redhat.com fcoemon[9557]: [-s|--syslog=yes|no] Oct 29 05:17:18 storageqe-16.sqe.lab.eng.bos.redhat.com fcoemon[9557]: [-v|--version] Oct 29 05:17:18 storageqe-16.sqe.lab.eng.bos.redhat.com fcoemon[9557]: [-h|--help] Oct 29 05:17:18 storageqe-16.sqe.lab.eng.bos.redhat.com systemd[1]: fcoe.service: Control process exited, code=exited, status=1/FAILURE Oct 29 05:17:18 storageqe-16.sqe.lab.eng.bos.redhat.com systemd[1]: fcoe.service: Failed with result 'exit-code'. Oct 29 05:17:18 storageqe-16.sqe.lab.eng.bos.redhat.com systemd[1]: Failed to start Open-FCoE Inititator.. After I manually change the ExecStart line in /usr/lib/systemd/system/fcoe.service to ExecStart=/usr/sbin/fcoemon -l It will fails as follows: [root@storageqe-16 log]# systemctl status fcoe.service ● fcoe.service - Open-FCoE Inititator. Loaded: loaded (/usr/lib/systemd/system/fcoe.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2020-10-29 05:20:27 EDT; 37s ago Process: 9586 ExecStartPre=/sbin/modprobe -qa $SUPPORTED_DRIVERS (code=exited, status=0/SUCCESS) Process: 9587 ExecStart=/usr/sbin/fcoemon -l (code=exited, status=1/FAILURE) CPU: 5ms Oct 29 05:20:27 storageqe-16.sqe.lab.eng.bos.redhat.com systemd[1]: Starting Open-FCoE Inititator.... Oct 29 05:20:27 storageqe-16.sqe.lab.eng.bos.redhat.com fcoemon[9587]: fcoemon: error 98 Address already in use Oct 29 05:20:27 storageqe-16.sqe.lab.eng.bos.redhat.com fcoemon[9587]: fcoemon: Failed to bind socket Oct 29 05:20:27 storageqe-16.sqe.lab.eng.bos.redhat.com fcoemon[9587]: fcoemon: Daemon already running OR Failed to bind socket so exiting! Oct 29 05:20:27 storageqe-16.sqe.lab.eng.bos.redhat.com systemd[1]: fcoe.service: Control process exited, code=exited, status=1/FAILURE Oct 29 05:20:27 storageqe-16.sqe.lab.eng.bos.redhat.com systemd[1]: fcoe.service: Failed with result 'exit-code'. Oct 29 05:20:27 storageqe-16.sqe.lab.eng.bos.redhat.com systemd[1]: Failed to start Open-FCoE Inititator.. As a result,we can't perform installation on fcoe target. Version-Release number of selected component (if applicable): fcoe-utils-1.0.33-0.gitfe376de.fc34.x86_64 fcoe-utils-1.0.33-1.gitfe376de.fc34.x86_64 also fails How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
New update: I have checked Fedora-Rawhide-20201229.n.0(fcoe-utils-1.0.33-2.gitfe376de.fc34.x86_64), fcoe service could be started successfully afterI manually change the ExecStart line in /usr/lib/systemd/system/fcoe.service to ExecStart=/usr/sbin/fcoemon -l [root@storageqe-16 libsan]# systemctl status fcoe ● fcoe.service - Open-FCoE Inititator. Loaded: loaded (/usr/lib/systemd/system/fcoe.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2020-12-30 08:04:22 EST; 8min ago Process: 881 ExecStartPre=/sbin/modprobe -qa $SUPPORTED_DRIVERS (code=exited, status=0/SUCCESS) Process: 882 ExecStart=/usr/sbin/fcoemon -l (code=exited, status=0/SUCCESS) Main PID: 883 (fcoemon) Tasks: 1 (limit: 9294) Memory: 240.0K CPU: 231ms CGroup: /system.slice/fcoe.service └─883 /usr/sbin/fcoemon -l And fcoe instance can be created successfully: [root@storageqe-16 libsan]# fcoeadm -i Description: NetXtreme II BCM57810 10 Gigabit Ethernet Revision: 10 Manufacturer: Broadcom Inc. and subsidiaries Serial Number: 001018AD40C0 Driver: bnx2x Unknown Number of Ports: 1 Symbolic Name: bnx2fc (QLogic BCM57810) v2.12.13 over ens2f0.802-fcoe OS Device Name: host1 Node Name: 0x2000001018ad40c1 Port Name: 0x2001001018ad40c1 Fabric Name: 0x2322000573b27f01 Speed: 10 Gbit Supported Speed: 1 Gbit, 10 Gbit MaxFrameSize: 2048 bytes FC-ID (Port ID): 0x750081 State: Online This bug prevents fedora installation on fcoe servers(#1882893),which is a fedora blocker. Would you please have a look,and fix this?Thanks.
I thought the problem is systemd failed to load the EnvironmentFile specified in fcoe.service,but it's not, as fcoe-utils-1.0.32 works well on the same environment,where fcoe-utils-1.0.33 failed to work.
This bug is fixed in fcoe-utils-1.0.33-5.git848bcc6.fc34,thanks cleech for the new build