[opensuse] zypper ps -> gmain
Hi I am still not comfortable with the systemd daemon, now I have a machine that after a update gives: rad0:~ # zypper ps The following running processes use deleted files: ______________________________ PID | PPID | UID | Login | Command | Service | Files ----+------+-----+-------+---------+---------+-------------- 528 | 1 | 0 | root | gmain | | /usr/lib64/libvmtools.so.0.0.0 | | | | | | /usr/lib64/open-vm-tools/plugins/common/libhgfsServer.so | | | | | | /usr/lib64/libhgfs.so.0.0.0 | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libguestInfo.so | | | | | | /usr/lib64/open-vm-tools/plugins/common/libvix.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libpowerOps.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libtimeSync.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libvmbackup.so | | | | | | /usr/bin/vmtoolsd (deleted) You may wish to restart these processes. ______________________________ I do, but how? systemctl restart vmtoolsd.service does not seem to help -- Thanks Klaus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Klaus Vink Slott said the following on 04/30/2013 09:06 AM:
Hi
I am still not comfortable with the systemd daemon, now I have a machine that after a update gives:
rad0:~ # zypper ps The following running processes use deleted files: ______________________________
PID | PPID | UID | Login | Command | Service | Files
----+------+-----+-------+---------+---------+-------------- 528 | 1 | 0 | root | gmain | | /usr/lib64/libvmtools.so.0.0.0 | | | | | | /usr/lib64/open-vm-tools/plugins/common/libhgfsServer.so | | | | | | /usr/lib64/libhgfs.so.0.0.0 | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libguestInfo.so | | | | | | /usr/lib64/open-vm-tools/plugins/common/libvix.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libpowerOps.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libtimeSync.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libvmbackup.so | | | | | | /usr/bin/vmtoolsd (deleted)
You may wish to restart these processes. ______________________________
I do, but how?
systemctl restart vmtoolsd.service
does not seem to help
Of course not. The process that needs to be restarted is pid=528, 'gmain'. That's the only process listed there. All the other things are libraries or helpers. Your confusion isn't with systemd, but with interpreting the 'zypper ps' report :-0 -- Flying is not dangerous; crashing is dangerous. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 30-04-2013 15:24, Anton Aylward wrote:
Klaus Vink Slott said the following on 04/30/2013 09:06 AM:
Hi
I am still not comfortable with the systemd daemon, now I have a machine that after a update gives:
rad0:~ # zypper ps The following running processes use deleted files: ______________________________
PID | PPID | UID | Login | Command | Service | Files
----+------+-----+-------+---------+---------+-------------- 528 | 1 | 0 | root | gmain | | /usr/lib64/libvmtools.so.0.0.0 | | | | | | /usr/lib64/open-vm-tools/plugins/common/libhgfsServer.so | | | | | | /usr/lib64/libhgfs.so.0.0.0 | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libguestInfo.so | | | | | | /usr/lib64/open-vm-tools/plugins/common/libvix.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libpowerOps.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libtimeSync.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libvmbackup.so | | | | | | /usr/bin/vmtoolsd (deleted)
You may wish to restart these processes. ______________________________
I do, but how?
systemctl restart vmtoolsd.service
does not seem to help
Of course not. The process that needs to be restarted is pid=528, 'gmain'. That's the only process listed there. All the other things are libraries or helpers.
Your confusion isn't with systemd, but with interpreting the 'zypper ps' report :-0
Sorry but I dont get your point. systemd is responsible for starting and stopping all daemons on this machine. At least I did not manually start gmain (whatever that is). My reason for going after vmtoolsd was, that it was listed as deleted in the output - and that vmtools is controlled by systemd -- Regards Klaus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Klaus Vink Slott said the following on 04/30/2013 09:50 AM:
On 30-04-2013 15:24, Anton Aylward wrote:
Klaus Vink Slott said the following on 04/30/2013 09:06 AM:
Hi
I am still not comfortable with the systemd daemon, now I have a machine that after a update gives:
rad0:~ # zypper ps The following running processes use deleted files: ______________________________
PID | PPID | UID | Login | Command | Service | Files
----+------+-----+-------+---------+---------+-------------- 528 | 1 | 0 | root | gmain | | /usr/lib64/libvmtools.so.0.0.0 | | | | | | /usr/lib64/open-vm-tools/plugins/common/libhgfsServer.so | | | | | | /usr/lib64/libhgfs.so.0.0.0 | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libguestInfo.so | | | | | | /usr/lib64/open-vm-tools/plugins/common/libvix.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libpowerOps.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libtimeSync.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libvmbackup.so | | | | | | /usr/bin/vmtoolsd (deleted)
You may wish to restart these processes. ______________________________
I do, but how?
systemctl restart vmtoolsd.service
does not seem to help
Of course not. The process that needs to be restarted is pid=528, 'gmain'. That's the only process listed there. All the other things are libraries or helpers.
Your confusion isn't with systemd, but with interpreting the 'zypper ps' report :-0
Sorry but I dont get your point. systemd is responsible for starting and stopping all daemons on this machine. At least I did not manually start gmain (whatever that is).
My reason for going after vmtoolsd was, that it was listed as deleted in the output - and that vmtools is controlled by systemd
Yes, you don't get my point. All that is listed are things that were started by gmain. Gmain is the only PID listed there. There is nothing else in the PID column. Is vmtools started directly by systemd or is it started by gmain IN THIS INSTANCE? The way your 'zypper ps' output reads make me think its started by gmain. I'm not saying that systemd isn't involved, I'm just going by what your 'zypper ps' said. That seems to be the *SOURCE* of your issue. You might also look at the syslog/journald for that time period to see what was stopped and started. Finally, there is the 'deleted' tag. That could mean that the running binary was deleted by an upgrade when you did the upgrade that preceded this. Perhaps it was replaced in the upgrade by a new instance of the same. Perhaps its simply not around any more. But my real point is that its not vmtoolsd that 'zypper ps' is telling you about. It is telling you that 'gmain' needs to be restarted. That's why there is only the gmain pid listed. All the rest are the 'why'. Do read the zypper man page for the section 'ps'. It tells you quite explicitly that it is the identified process - the one it supplies the pid and name for, is the one to be restarted. -- "Combinatorics -- how to count without counting." - Cassablanca -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/30/2013 7:19 AM, Anton Aylward wrote:
Klaus Vink Slott said the following on 04/30/2013 09:50 AM:
On 30-04-2013 15:24, Anton Aylward wrote:
Klaus Vink Slott said the following on 04/30/2013 09:06 AM:
Hi
I am still not comfortable with the systemd daemon, now I have a machine that after a update gives:
rad0:~ # zypper ps The following running processes use deleted files: ______________________________
PID | PPID | UID | Login | Command | Service | Files
----+------+-----+-------+---------+---------+-------------- 528 | 1 | 0 | root | gmain | | /usr/lib64/libvmtools.so.0.0.0 | | | | | | /usr/lib64/open-vm-tools/plugins/common/libhgfsServer.so | | | | | | /usr/lib64/libhgfs.so.0.0.0 | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libguestInfo.so | | | | | | /usr/lib64/open-vm-tools/plugins/common/libvix.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libpowerOps.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libtimeSync.so | | | | | | /usr/lib64/open-vm-tools/plugins/vmsvc/libvmbackup.so | | | | | | /usr/bin/vmtoolsd (deleted)
You may wish to restart these processes. ______________________________
I do, but how?
systemctl restart vmtoolsd.service
does not seem to help
Of course not. The process that needs to be restarted is pid=528, 'gmain'. That's the only process listed there. All the other things are libraries or helpers.
Your confusion isn't with systemd, but with interpreting the 'zypper ps' report :-0
Sorry but I dont get your point. systemd is responsible for starting and stopping all daemons on this machine. At least I did not manually start gmain (whatever that is).
My reason for going after vmtoolsd was, that it was listed as deleted in the output - and that vmtools is controlled by systemd
Yes, you don't get my point. All that is listed are things that were started by gmain. Gmain is the only PID listed there. There is nothing else in the PID column.
Is vmtools started directly by systemd or is it started by gmain IN THIS INSTANCE?
The way your 'zypper ps' output reads make me think its started by gmain.
I'm not saying that systemd isn't involved, I'm just going by what your 'zypper ps' said. That seems to be the *SOURCE* of your issue.
You might also look at the syslog/journald for that time period to see what was stopped and started.
Finally, there is the 'deleted' tag. That could mean that the running binary was deleted by an upgrade when you did the upgrade that preceded this. Perhaps it was replaced in the upgrade by a new instance of the same. Perhaps its simply not around any more.
But my real point is that its not vmtoolsd that 'zypper ps' is telling you about. It is telling you that 'gmain' needs to be restarted. That's why there is only the gmain pid listed. All the rest are the 'why'.
Do read the zypper man page for the section 'ps'. It tells you quite explicitly that it is the identified process - the one it supplies the pid and name for, is the one to be restarted.
Of for god sake just reboot. Digging around to find everything running on old binaries is seldom worth the time. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Sorry I even asked in this forum.
On 4/30/2013 7:19 AM, Anton Aylward wrote:
Of for god sake just reboot. Digging around to find everything running on old binaries is seldom worth the time.
This reminds me of an old joke: "Windows have detected that you have moved your mouse pointer. Please reboot for the changes to take effect" Is it time to s/Windows/Linux/g now? I dont tink so. And running machines serving 3000+ users, reboot is not an everyday option. -- Have a nice day. Klaus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Klaus Vink Slott said the following on 05/01/2013 04:24 AM:
Sorry I even asked in this forum.
On 4/30/2013 7:19 AM, Anton Aylward wrote:
Of for god sake just reboot. Digging around to find everything running on old binaries is seldom worth the time.
Thank you but it wasn't me that said that. -- Quality is free, but only for those who are willing to pay heavily for it. - Tom Demarco, "Peopleware" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 01 May 2013 10:24:27 +0200
Klaus Vink Slott
And running machines serving 3000+ users, reboot is not an everyday option.
The same is valid for updates that require only application restart, as some of those 3000+ may lose work and with Murphy's Law still in tact that will happen in the most inappropriate way (to the most important person, or the most time sensitive work :) A bit of redundancy in hardware and software, to cover situations like updates, or fallout of components is something that many system builders don't have in mind making a problem out of predictable maintenance tasks. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 5/1/2013 1:24 AM, Klaus Vink Slott wrote:
Sorry I even asked in this forum.
On 4/30/2013 7:19 AM, Anton Aylward wrote:
Of for god sake just reboot. Digging around to find everything running on old binaries is seldom worth the time.
This reminds me of an old joke: "Windows have detected that you have moved your mouse pointer. Please reboot for the changes to take effect" Is it time to s/Windows/Linux/g now? I dont tink so. And running machines serving 3000+ users, reboot is not an everyday option.
You didn't mention having 3000+ users on this machine, and the post was about VMware tools, and any version of Vmware would require massive hardware to serve vmware to 3000 users. Since the 3000 users on Vmware seemed unlikely, I presumed you were running a personal machine. But more to the point, anyone running a system with 3000 users would (should) know that there is no ill effect of having a process running a deleted module. The system is designed to do this. After every link (hard and soft) and open file handle to a module is erased the module will be finally gone. (Unreachable, but still on disk until those inodes are re-allocated.) Processes still running any module can continue to do so till they shut down, at which time, the last remaining link to that module is gone, and the space becomes reusable. This is perfectly normal way to operate and on any machine that serves many users, and it is a problem that takes care of itself. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday 01 May 2013, John Andersen wrote:
On 5/1/2013 1:24 AM, Klaus Vink Slott wrote:
Sorry I even asked in this forum.
On 4/30/2013 7:19 AM, Anton Aylward wrote:
Of for god sake just reboot. Digging around to find everything running on old binaries is seldom worth the time.
This reminds me of an old joke: "Windows have detected that you have moved your mouse pointer. Please reboot for the changes to take effect" Is it time to s/Windows/Linux/g now? I dont tink so. And running machines serving 3000+ users, reboot is not an everyday option.
You didn't mention having 3000+ users on this machine, and the post was about VMware tools, and any version of Vmware would require massive hardware to serve vmware to 3000 users. Since the 3000 users on Vmware seemed unlikely, I presumed you were running a personal machine.
But more to the point, anyone running a system with 3000 users would (should) know that there is no ill effect of having a process running a deleted module. The system is designed to do this.
Err, the deleted object was deleted because of a security update. So of course you should make sure that nobody is still using it ... specially on a system with 3000 users because the probability that one of them wants to do something nasty is much higher than on a single user system. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-04-30 at 15:50 +0200, Klaus Vink Slott wrote:
Sorry but I dont get your point. systemd is responsible for starting and stopping all daemons on this machine. At least I did not manually start gmain (whatever that is).
My reason for going after vmtoolsd was, that it was listed as deleted in the output - and that vmtools is controlled by systemd
I have just installed a test 12.3 system under vmplayer (thus I have vmtoolsd), but I don't see any "gmain" program, nor do I see it in the list of files in the entire installation DVD (it may be in the repos, though). So I would try to find out where your "gmain" comes from. rpm -q -f `which gmain` will tell you which rpm it comes from. Knowing what it is would be the first step in learning the "polite" way to restart it :-) - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGBH+EACgkQtTMYHG2NR9VuDACgiuDdjjCKcem04EjjDrpjkA5U ZK4AoIngatrev+8o6oPXhuu2OL89PD7T =zzZJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2013-05-01 at 15:59 +0200, Carlos E. R. wrote:
On Tuesday, 2013-04-30 at 15:50 +0200, Klaus Vink Slott wrote:
I have just installed a test 12.3 system under vmplayer (thus I have vmtoolsd), but I don't see any "gmain" program, nor do I see it in the list of files in the entire installation DVD (it may be in the repos, though).
I have downloaded the list of files in both oss and non-oss repos (42M compressed, 660M uncompressed text file), and there is no bin/gmain. So, what is it? Where did you got it from? - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGBJi8ACgkQtTMYHG2NR9U5HACdEEYRpqfyTi+BwALo1RzyLiGH zj0An114mpfqVUasYjkFJf+AiIJ0P81T =JMpZ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Tue, 30 Apr 2013 15:06:19 +0200
Klaus Vink Slott
Hi
I am still not comfortable with the systemd daemon, now I have a machine that after a update gives:
rad0:~ # zypper ps The following running processes use deleted files: ______________________________
PID | PPID | UID | Login | Command | Service | Files
----+------+-----+-------+---------+---------+-------------- 528 | 1 | 0 | root | gmain | | /usr/lib64/libvmtools.so.0.0.0
Please show output of ls -l /proc/528/exe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Andrey Borzenkov -
Anton Aylward -
Carlos E. R. -
John Andersen -
Klaus Vink Slott -
Rajko -
Ruediger Meier