Hello,

We are seeing some strange behavior with xCAT service -

Systemctl status xcatd return the following output -

s08:~ # systemctl status xcatd
● xcatd.service - LSB: xcatd
   Loaded: loaded (/etc/init.d/xcatd; bad; vendor preset: disabled)
   Active: failed (Result: timeout) since Tue 2017-06-06 19:12:36 CEST; 16h ago
     Docs: man:systemd-sysv-generator(8)
  Process: 30751 ExecStop=/etc/init.d/xcatd stop (code=exited, status=0/SUCCESS)
  Process: 7630 ExecStart=/etc/init.d/xcatd start (code=killed, signal=TERM)
    Tasks: 8 (limit: 512)
   CGroup: /system.slice/xcatd.service
           ├─23978 /usr/sbin/in.tftpd -v -l -s /tftpboot -m 
/etc/tftpmapfile4xcat.conf
           ├─28343 xcatd: SSL listener
           ├─28344 xcatd: DB Access
           ├─28345 xcatd: UDP listener
           ├─28346 xcatd: install monitor
           ├─28347 xcatd: Discovery worker
           ├─28348 xcatd: Command log writer
           └─28727 xcatd: DB Access


While xcatd is still running and operational (tabdump every other functionality 
seems to work).

Doing a systemctl restart xcatd immediately works and seems to fix the issue.

Any idea what could make the service thinks it failed? Anything we should look 
at?

THX!!
[http://lenovocentral.lenovo.com/marketing/branding/email_signature/images/gradient.gif]

Gilad Berman
HPC Architect
Lenovo EMEA

[Phone]+972-52-2554262
[Email]gber...@lenovo.com<mailto:gber...@lenovo.com>



Lenovo.com <http://www.lenovo.com/>
Twitter<http://twitter.com/lenovo> | Facebook<http://www.facebook.com/lenovo> | 
Instagram<https://instagram.com/lenovo> | Blogs<http://blog.lenovo.com/> | 
Forums<http://forums.lenovo.com/>


[DCG-Hardware]




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to