Tracker item #2814131, was opened at 2009-06-29 10:20 Message generated for change (Comment added) made by mvanzin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2814131&group_id=204462
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: guestd Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: homebrew (barry-davis) Assigned to: Nobody/Anonymous (nobody) Summary: vmtoolsd logs fill drive Initial Comment: If left long enough vmtoolsd will fill the filesystem with its logs. I'm running on a ramdisk and have 64M set aside for logs. After leaving it for a few days with debug turned on it fills this. Is there a way of getting vmtoolsd to rotate its log? I assume its not compatible with 'logrotate' as it dies when sent a HUP. /root# cat /etc/vmware-tools/tools.conf [logging] vmsvc.handler=file vmsvc.level=debug vmsvc.data=/var/log/vmware-vmsvc.log vmusr.handler=file vmusr.level=debug vmusr.data=/var/log/vmware-vmsvc.log.user log=true level=debug [vmsvc] disable-tools-version=true ---------------------------------------------------------------------- >Comment By: Marcelo Vanzin (mvanzin) Date: 2009-06-29 15:51 Message: Thanks for that info, that is good to know. ---------------------------------------------------------------------- Comment By: homebrew (barry-davis) Date: 2009-06-29 14:41 Message: I don't ususally run with it set to debug, It was just to demonstrate the point over a short period of time. I have a box thats logging just warning messages now and has been up for 5 hours. /root# ls -l /var/log/vmware-vmsvc.log* -rw-r--r-- 1 root root 2.2M Jun 29 21:17 /var/log/vmware-vmsvc.log -rw-r--r-- 1 root root 93K Jun 29 21:17 /var/log/vmware-vmsvc.log.old Most of the output in /var/log/vmware-vmsvc.log is repeatadly complaining it can't open release and version files once every 30 seconds. For a custom distribution what is the minimal set of files that you need to stop these messages, and what does vmtoolsd expect to find in them? [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/redhat-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/redhat_version: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/sun-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/SuSE-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/novell-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/sles-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/debian_version: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/debian_release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/mandrake-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/mandriva-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/mandrakelinux-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/turbolinux-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/fedora-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/gentoo-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/nld-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/lsb-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/annvix-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/arch-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/arklinux-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/aurox-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/blackcat-release: 2 [Jun 29 15:59:46.682: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/cobalt-release: 2 [Jun 29 15:59:46.683: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/conectiva-release: 2 [Jun 29 15:59:46.683: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/immunix-release: 2 [Jun 29 15:59:46.683: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/knoppix_version: 2 [Jun 29 15:59:46.683: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/lfs-release: 2 [Jun 29 15:59:46.683: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/linuxppc-release: 2 [Jun 29 15:59:46.683: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/mklinux-release: 2 [Jun 29 15:59:46.683: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/pld-release: 2 [Jun 29 15:59:46.683: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/slackware-version: 2 [Jun 29 15:59:46.683: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/slackware-release: 2 [Jun 29 15:59:46.683: ] [ warning] [vmsvc] HostinfoReadDistroFile: could not open file/etc/e-smith-release: 2 ---------------------------------------------------------------------- Comment By: Marcelo Vanzin (mvanzin) Date: 2009-06-29 10:29 Message: vmtoolsd doesn't rotate logs yet; we only recommend enabling logs if you're actually trying to debug something or send data back to us so we can debug it. You can reduce the log spew by using a higher level (such as "warning") instead of "debug". At some point I'll look at adding log rotation (might also look at logrotate, thanks for the tip, although I don't think that helps us much with the Windows side of things), but don't hold your breath... :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=2814131&group_id=204462 ------------------------------------------------------------------------------ _______________________________________________ open-vm-tools-devel mailing list open-vm-tools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
