JesseR's Posts

Oh, right on. Unfortunately I am not using that
Well, one of the hosts is right, another i checked had restrict 127.0.0.1 restrict default kod nomodify notrap server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org driftfil... See more...
Well, one of the hosts is right, another i checked had restrict 127.0.0.1 restrict default kod nomodify notrap server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org driftfile /var/lib/ntp/drift
I don't have a problem logging into VC or any of the hosts, I can get in just fine. What I want to know is #1 what is this #2 what is the impact and #3 how is it fixed......
Troy, Checked another and it is also displaying the same thing: vmware-authd(pam_unix)[16817]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root Jan ... See more...
Troy, Checked another and it is also displaying the same thing: vmware-authd(pam_unix)[16817]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root Jan 12 08:12:34 sfwesx02 vmware-hostd[16817]: Rejected password for user root from 127.0.0.1 Jan 12 08:17:32 sfwesx02 vmware-authd(pam_unix)[16817]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root Jan 12 08:17:35 sfwesx02 vmware-hostd[16817]: Rejected password for user root from 127.0.0.1 Jan 12 08:17:59 sfwesx02 ntpd[836]: can't open /var/lib/ntp.drift.TEMP: Permission denied
Root password has definately not been changed. Just migrated all the hosts from VC 2.1 server to a new VC 2.5 server. There is nothing I knwo of that connects as root....
Interesting, I logged into one of my hosts and checked the /var/log/messages file and its full of invalid root login attempts. There is a cimservera process running it seems......but from your KB... See more...
Interesting, I logged into one of my hosts and checked the /var/log/messages file and its full of invalid root login attempts. There is a cimservera process running it seems......but from your KB article, it does not exhibit the issue stated in the article: vmware-authd(pam_unix)[1209]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root Jan 12 08:52:35 sfwesx01 vmware-hostd[1209]: Rejected password for user root from 127.0.0.1 Jan 12 08:57:32 sfwesx01 vmware-authd(pam_unix)[1209]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root Jan 12 08:57:35 sfwesx01 vmware-hostd[1209]: Rejected password for user root from 127.0.0.1 Jan 12 09:02:32 sfwesx01 vmware-authd(pam_unix)[1209]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root Jan 12 09:02:34 sfwesx01 vmware-hostd[1209]: Rejected password for user root from 127.0.0.1 Jan 12 09:07:32 sfwesx01 vmware-authd(pam_unix)[1209]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root Jan 12 09:07:35 sfwesx01 vmware-hostd[1209]: Rejected password for user root from 127.0.0.1 Jan 12 09:12:32 sfwesx01 vmware-authd(pam_unix)[1209]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root Jan 12 09:12:35 sfwesx01 vmware-hostd[1209]: Rejected password for user root from 127.0.0.1
This is written about 8 times in a row, and repeats every 5-6 minutes or so it seems. Anybody know what can cause this? Nothing unusual in the VC log files......
I ran your printperm script and it did report back the information, however, it errored out with error: Can't call method "isa" on unblessed reference at C:/Program Files/VMware/VMware ... See more...
I ran your printperm script and it did report back the information, however, it errored out with error: Can't call method "isa" on unblessed reference at C:/Program Files/VMware/VMware VI Perl Toolkit/Perl/lib/VMware/VICommon.pm line 887. It did give back some information but I do not know if it reported back ALL information before it errored out. What is causing the error?
I do not want to upgrade at this point because these systems are in production and going through our change process is very timely and do not want to change something that is not broke. When I ad... See more...
I do not want to upgrade at this point because these systems are in production and going through our change process is very timely and do not want to change something that is not broke. When I added the extra licenses to the license file and re-read, as I stated it showed 22 of 22. When I checked the log this is what I saw. 12:16:32 (VMWARELM) DENIED: "VC_ESXHOST" SYSTEM@usartoolrig (2 licenses) (Feature removed during lmreread, or wrong SERVER line hostid. (-92,395)) 12:16:32 (VMWARELM) UNSUPPORTED: "VC_ESXHOST" (1F29 A4E1 707E 7985 ) SYSTEM@usartoolrig (2 licenses) (License server system does not support this feature. (-18,327)) 12:16:32 (VMWARELM) UNSUPPORTED: "VC_ESXHOST" (09FB 9EF5 D89F F63B ) SYSTEM@usartoolrig (2 licenses) (License server system does not support this feature. (-18,327)) 12:16:32 (VMWARELM) UNSUPPORTED: "VC_ESXHOST" (1CF2 1607 511A 6FA1 ) SYSTEM@usartoolrig (2 licenses) (License server system does not support this feature. (-18,327)) 12:16:32 (VMWARELM) UNSUPPORTED: "VC_ESXHOST" (1D92 67A2 33CE ADD7 ) SYSTEM@usartoolrig (2 licenses) (License server system does not support this feature. (-18,327)) 12:16:32 (VMWARELM) UNSUPPORTED: "VC_ESXHOST" (1343 A0B5 C4A3 D725 ) SYSTEM@usartoolrig (2 licenses) (License server system does not support this feature. (-18,327)) 12:16:32 (VMWARELM) UNSUPPORTED: "VC_ESXHOST" (025B 0CFE C95F 16D3 ) SYSTEM@usartoolrig (2 licenses) (License server system does not support this feature. (-18,327)) 12:16:32 (VMWARELM) UNSUPPORTED: "VC_ESXHOST" (0A87 8F7F 4CAF 9E45 ) SYSTEM@usartoolrig (2 licenses) (License server system does not support this feature. (-18,327)) 12:16:32 (VMWARELM) OUT: "VC_ESXHOST" SYSTEM@usartoolrig (2 licenses) 12:16:32 (VMWARELM) DENIED: "VC_DAS" SYSTEM@usartoolrig (2 licenses) (Feature removed during lmreread, or wrong SERVER line hostid. (-92,395)) As I did not think this was a good error, I put the original license file back for the time being until I figure out what is causing this. Any ideas?
Currently I have 16 ESX hosts in production and we have added 2 more hosts. Currently VC is showing the correct license usage but when I add the new licenses using the cut&paste method to the cur... See more...
Currently I have 16 ESX hosts in production and we have added 2 more hosts. Currently VC is showing the correct license usage but when I add the new licenses using the cut&paste method to the currently used vmware.lic file, it now shows that there are 22 remaining and 22 unused. Should I be concerned that the license usuage resets when I do this? As of now I reverted back to the original license file just till I found out if that is what it is supposed to show.