Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#32699 - [open-vm-tools] vmtoolsd does not close on poweroff/reboot

Attached to Project: Community Packages
Opened by Christian (Watnuss) - Friday, 16 November 2012, 08:52 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 28 February 2013, 15:16 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Description:
Everytime I poweroff or reboot the system it holds for a minute at the sequence "Stopped target Remote File Systems."

Looking to journalctl give following hint:
"
Nov 15 11:45:01 warch systemd[1]: Stopped target Remote File Systems.
Nov 15 11:46:06 warch systemd[1]: vmtoolsd.service stopping timed out. Killing.
Nov 15 11:46:06 warch systemd[1]: vmtoolsd.service: main process exited,code=killed, status=9/KILL
Nov 15 11:46:06 warch systemd[1]: Stopped Open Virtual Machine Tools (VMwareTools).
Nov 15 11:46:06 warch systemd[1]: Unit vmtoolsd.service entered failed state
"
So it looks like the service could not be closed as it should.
If you need any further logs or any checks I can offer them to you. Just tell me what you need. I did not find anything else by myself.

Additional info:
I am running Linux kernel 3.6.6 with open-vm-tools 9.2.0.-2 and open-vm-tools-modules 9.2.2-3. Oviously inside VMWare.
I created a Bug report at vmtools' upstream but I was told that the systemd integration was done by ArchLinux [https://sourceforge.net/tracker/?func=detail&aid=3587492&group_id=204462&atid=989708]

Steps to reproduce:
Reboot ArchLinux as a VMWare guest system
This task depends upon

Closed by  Sergej Pupykin (sergej)
Thursday, 28 February 2013, 15:16 GMT
Reason for closing:  Upstream
Additional comments about closing:  upstream notified, workaround available.
Comment by Sergej Pupykin (sergej) - Wednesday, 30 January 2013, 11:14 GMT
Can it be closed with killall vmtoolsd ?

It looks like it does not handle SIGTERM signal.

As workaround you may add
TimeoutStopSec=5s
to service file
Comment by Christian (Watnuss) - Wednesday, 30 January 2013, 11:39 GMT
if I use:
$ sudo killall vmtoolsd
$ echo $?
it returns 0. But ps ef|grep vmtoolsd says it is still running. Is it just restarted immediately?

If I use
$ sudo killall vmtoolsd
again and grep ps it still has the same pid.

The verbose output:
Killed vmtoolsd(267) with signal 15
Killed vmtoolsd(380) with signal 15


Thanks for the hint with the reduced timeout time. This will help a lot until the issue is resolved.

Do you need more information?
Comment by Christian Hesse (eworm) - Monday, 04 February 2013, 12:49 GMT
Looks like this is an upstream bug report for our issue: https://sourceforge.net/tracker/?func=detail&aid=3601728&group_id=204462&atid=989708

Loading...