Bug 1555257
| Summary: | lldpad.socket service inactive after restart the service | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | jiachen zhang <jiaczhan> | ||||
| Component: | rhev-hypervisor-ng | Assignee: | Ryan Barry <rbarry> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | jiachen zhang <jiaczhan> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.1.10 | CC: | cshao, dfediuck, huzhao, jiaczhan, qiyuan, rbarry, sbonazzo, weiwang, yaniwang, ycui, yturgema, yzhao | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-03-14 14:24:56 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Please don't try to restart sockets. systemd sockets are effective a thin layer which says "systemd will listen on the given port. If a connection is received, hold it open, start the associated service, then close it". Restarting is not expected Is lldpad.service running? Can it be restarted? (In reply to Ryan Barry from comment #1) > Please don't try to restart sockets. systemd sockets are effective a thin > layer which says "systemd will listen on the given port. If a connection is > received, hold it open, start the associated service, then close it". > Restarting is not expected > > Is lldpad.service running? Can it be restarted? Yes,the lldpad.service running and it can be restarted. (In reply to jiachen zhang from comment #2) > (In reply to Ryan Barry from comment #1) > > Please don't try to restart sockets. systemd sockets are effective a thin > > layer which says "systemd will listen on the given port. If a connection is > > received, hold it open, start the associated service, then close it". > > Restarting is not expected > > > > Is lldpad.service running? Can it be restarted? > > Yes,the lldpad.service running and it can be restarted. But why I can restart the service successfully in RHVH 7.5 build? (In reply to jiachen zhang from comment #3) > (In reply to jiachen zhang from comment #2) > > (In reply to Ryan Barry from comment #1) > > > Please don't try to restart sockets. systemd sockets are effective a thin > > > layer which says "systemd will listen on the given port. If a connection is > > > received, hold it open, start the associated service, then close it". > > > Restarting is not expected > > > > > > Is lldpad.service running? Can it be restarted? > > > > Yes,the lldpad.service running and it can be restarted. > > But why I can restart the service successfully in RHVH 7.5 build? Sorry, I understood. I forgot the service is failed on RHVH 7.5 build so the socket can be restarted.Thanks. Actually, it's not a bug. BZ<2>Jira Resync |
Created attachment 1407891 [details] /var/log /tmp sosreport Description of problem: Running the command "systemctl status lldpad.service", the service status is active. After running the command "systemctl restart lldpad.socket", the service cannot be restart succeffully. Then run "systemctl status lldpad.service" again, the service is inactive. Version-Release number of selected component (if applicable): redhat-virtualization-host-4.1-20180313.0 imgbased-0.9.54-0.1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Install RHVH-4.1, configure network successful. 2. Add RHVH to RHEV-M. 3. Check the service use "systemctl status lldpad.socket". the status is active. 4. Restart the service "systemctl restart lldpad.socket". 5. Check the service again use "systemctl status lldpad.socket". the status is inactive. Actual results: 1. After step 4, lldpad.socket should be restarted successfully. 2. After step 5, the service status is active. Expected results: 1. After step 3, lldpad.socket cannot be restarted. 2. After step 5, the service status is inactive. Additional info: [root@dhcp-9-70 ~]# systemctl status lldpad.socket ● lldpad.socket Loaded: loaded (/usr/lib/systemd/system/lldpad.socket; enabled; vendor preset: disabled) Active: active (running) since Wed 2018-03-14 05:16:31 EDT; 2min 40s ago Listen: @/com/intel/lldpad (Datagram) [root@dhcp-9-70 ~]# systemctl restart lldpad.socket Job for lldpad.socket failed. See "systemctl status lldpad.socket" and "journalctl -xe" for details. [root@dhcp-9-70 ~]# systemctl status lldpad.socket ● lldpad.socket Loaded: loaded (/usr/lib/systemd/system/lldpad.socket; enabled; vendor preset: disabled) Active: inactive (dead) since Wed 2018-03-14 05:21:28 EDT; 5s ago Listen: @/com/intel/lldpad (Datagram) Mar 14 05:16:31 localhost.localdomain systemd[1]: Listening on lldpad.socket. Mar 14 05:16:31 localhost.localdomain systemd[1]: Starting lldpad.socket. Mar 14 05:21:28 dhcp-9-70.nay.redhat.com systemd[1]: Stopping lldpad.socket. Mar 14 05:21:28 dhcp-9-70.nay.redhat.com systemd[1]: Socket service lldpad.service already active, refusing. Mar 14 05:21:28 dhcp-9-70.nay.redhat.com systemd[1]: Failed to listen on lldpad.socket. This issue only occurs on RHVH 7.4 build.