It wanted pegasus to be lower case.
[r...@zesx2 zsus]# service pegasus restart
Stopping Pegasus CIMOM (cimserver)... [ OK ]
Starting Pegasus CIMOM (cimserver)... [ OK ]
That yields the following:
Apr 8 14:29:43 zesx2 watchdog-cimserver: Terminating watchdog with PID 1984
Apr 8 14:29:44 zesx2 watchdog-cimserver: [1984] Signal received:
exiting the watchdog
Apr 8 14:29:50 zesx2 pegasus: cimserver shutdown succeeded
Apr 8 14:29:50 zesx2 watchdog-cimserver: PID file
/var/run/vmware/watchdog-cimserver.PID not found
Apr 8 14:29:50 zesx2 pegasus: succeeded
Apr 8 14:29:50 zesx2 watchdog-cimserver: [17451] Begin
'/var/pegasus/bin/cimserver daemon=false', min-uptime = 60,
max-quick-failures = 5, max-total-failures = 1000000
Apr 8 14:29:50 zesx2 watchdog-cimserver: Executing
'/var/pegasus/bin/cimserver daemon=false'
Apr 8 14:29:58 zesx2 cimserver: trying to popen /sbin/modprobe edd 2>&1
Apr 8 14:29:59 zesx2 last message repeated 2 times
Apr 8 14:29:59 zesx2 vmware-hostd[21436]: Accepted password for user
root from 127.0.0.1
Apr 8 14:30:00 zesx2 cimserver: trying to popen /sbin/modprobe edd 2>&1
Apr 8 14:30:00 zesx2 cimserver: trying to popen /sbin/modprobe edd 2>&1
Apr 8 14:30:01 zesx2 cimserver: created VICimInstanceBuilder
Apr 8 14:30:01 zesx2 cimserver: created VICimMethodMgr
Apr 8 14:30:12 zesx2 cimserver: trying to popen /sbin/modprobe edd 2>&1
Apr 8 14:30:12 zesx2 cimserver: trying to popen /sbin/modprobe edd 2>&1
Apr 8 14:30:13 zesx2 cimserver: storelib-Failed to get pd infor for
ctrl 0, dev 1
Apr 8 14:30:13 zesx2 cimserver: Cannot get information from
controller 0 phy device 1
Apr 8 14:30:13 zesx2 cimserver:
storelib-GetLDList-ProcessLibCommandCall failed; rval = 0x8017
Apr 8 14:30:13 zesx2 cimserver: Volume Cannot get logical disk data
from controller 0
Apr 8 14:30:13 zesx2 cimserver:
storelib-GetLDList-ProcessLibCommandCall failed; rval = 0x8017
Apr 8 14:30:13 zesx2 cimserver: Volume Cannot get logical disk data
from controller 0
Apr 8 14:30:13 zesx2 cimserver: storelib-Read config failed 0
Apr 8 14:30:13 zesx2 cimserver: Cannot get information from
controller 0 phy device 1
On Thu, Apr 8, 2010 at 14:19, Damien Solodow
<[email protected]> wrote:
> Try this then: "service Pegasus restart"
> This will not down the guests, but might shutdown the Dell hardware agents if
> you have them installed..
>
> -----Original Message-----
> From: Kurt Buff [mailto:[email protected]]
> Sent: Thursday, April 08, 2010 5:17 PM
> To: NT System Admin Issues
> Subject: Re: OTish: ESX 3.5 guest won't boot
>
> BTW: I've got a 'tail -f' going on /var/log/messages, and I'm seeing more and
> more of this kind of stuff:
>
> Apr 8 14:16:09 zesx2 cimserver: storelib-Failed to get pd infor for ctrl 0,
> dev 1 Apr 8 14:16:09 zesx2 cimserver: Cannot get information from controller
> 0 phy device 1 Apr 8 14:16:09 zesx2 cimserver: storelib-Failed to get pd
> infor for ctrl 0, dev 2 Apr 8 14:16:09 zesx2 cimserver: Cannot get
> information from controller 0 phy device 2 Apr 8 14:16:09 zesx2 cimserver:
> storelib- GetPDInLD-ProcessLibCommandCall failed ; rval = 0x8017
>
> It's happening every minute or two now.
>
> Kurt
>
> On Thu, Apr 8, 2010 at 14:13, Kurt Buff <[email protected]> wrote:
>> Do you mean in the Events display on the VI client? If so, then what I
>> see isn't much. Just the following couplet several times:
>>
>> Message on sus on esx2.mycompany.com in ha-datacenter: Could not
>> power on VM: Metadata write error. Failed to power on VM
>>
>> and
>>
>> Failed to power on sus on esx2.mycompany.com in ha-datacenter: A
>> general system error occurred.
>>
>> Kurt
>>
>> On Thu, Apr 8, 2010 at 14:01, Klint Price <[email protected]> wrote:
>>> Because there is some cimserver errors in your logs you posted, and there
>>> is a known bug in ESX 3.5 U2 through U4 regarding a memory leak in
>>> cimserver which can consume your swap, can you restart the cimserver
>>> process, and try powering on your VM again?
>>>
>>> -----Original Message-----
>>> From: Kurt Buff [mailto:[email protected]]
>>> Sent: Thursday, April 08, 2010 1:58 PM
>>> To: NT System Admin Issues
>>> Subject: Re: OTish: ESX 3.5 guest won't boot
>>>
>>> [r...@esx2 root]# ps -lf -C cimserver F S UID PID PPID C PRI
>>> NI ADDR SZ WCHAN STIME TTY
>>> TIME CMD
>>> 0 S root 1991 1984 99 75 0 - 80493 schedu Apr07 ?
>>> 3-11:31:10 /var/pegasus/bin/cimserver daemon=false
>>>
>>>
>>> Kurt
>>>
>>> On Thu, Apr 8, 2010 at 13:55, Klint Price <[email protected]> wrote:
>>>> Can you run this command and tell me what the results are:
>>>>
>>>> ps -lf -C cimserver
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Kurt Buff [mailto:[email protected]]
>>>> Sent: Thursday, April 08, 2010 1:49 PM
>>>> To: NT System Admin Issues
>>>> Subject: Re: OTish: ESX 3.5 guest won't boot
>>>>
>>>> It's a Dell 2950, with a pair of 500gb SATA drives in a RAID1 array.
>>>>
>>>> According to the Dell site it's a
>>>>
>>>> CR679 Assembly, Card, SAS6IR, Integrated, Sled
>>>>
>>>> Kurt
>>>>
>>>> On Thu, Apr 8, 2010 at 13:36, Klint Price <[email protected]> wrote:
>>>>> What model controller is this disk attached to? Disk type? Server model?
>>>>>
>>>>> -----Original Message-----
>>>>> From: Kurt Buff [mailto:[email protected]]
>>>>> Sent: Thursday, April 08, 2010 1:34 PM
>>>>> To: NT System Admin Issues
>>>>> Subject: Re: OTish: ESX 3.5 guest won't boot
>>>>>
>>>>> Yuck:
>>>>>
>>>>> [r...@zesx2 root]# vmkfstools -P
>>>>> /vmfs/volumes/esx2\:storage1/sus/sus.vmdk
>>>>> Could not get volume attributes (rv -1)
>>>>> Error: Connection timed out
>>>>>
>>>>> On Thu, Apr 8, 2010 at 13:28, Damien Solodow
>>>>> <[email protected]> wrote:
>>>>>> That's a positive sign.
>>>>>> Try this: "vmkfstools -P /vmfs/volumes/esx2\:storage1\sus\sus.vmdk"
>>>>>> This will query the disk information.
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Kurt Buff [mailto:[email protected]]
>>>>>> Sent: Thursday, April 08, 2010 4:14 PM
>>>>>> To: NT System Admin Issues
>>>>>> Subject: Re: OTish: ESX 3.5 guest won't boot
>>>>>>
>>>>>> [r...@esx2 root]# vmware-cmd
>>>>>> /vmfs/volumes/esx2\:storage1/sus/sus.vmx getstate
>>>>>> getstate() = off
>>>>>>
>>>>>> Kurt
>>>>>>
>>>>>> On Thu, Apr 8, 2010 at 13:10, Damien Solodow
>>>>>> <[email protected]> wrote:
>>>>>>> From the ESX host run "vmware-cmd
>>>>>>> /vmfs/volumes/VOLNAME/VMNAME/VMNAME.vmx getstate" and reply with the
>>>>>>> result.
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Kurt Buff [mailto:[email protected]]
>>>>>>> Sent: Thursday, April 08, 2010 4:03 PM
>>>>>>> To: NT System Admin Issues
>>>>>>> Subject: Re: OTish: ESX 3.5 guest won't boot
>>>>>>>
>>>>>>> Some are on the SAN, some are direct attached, I haven't seen issues
>>>>>>> with any of the other VMs yet.
>>>>>>>
>>>>>>> Kurt
>>>>>>>
>>>>>>> On Thu, Apr 8, 2010 at 12:57, Damien Solodow
>>>>>>> <[email protected]> wrote:
>>>>>>>> Do you have other guests on the same storage as the misbehaving guest?
>>>>>>>> Are they working ok?
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Kurt Buff [mailto:[email protected]]
>>>>>>>> Sent: Thursday, April 08, 2010 3:54 PM
>>>>>>>> To: NT System Admin Issues
>>>>>>>> Subject: OTish: ESX 3.5 guest won't boot
>>>>>>>>
>>>>>>>> I'm googling like mad, and not finding a lot. Our ESX
>>>>>>>> infrastructure is primitive - it's two purely standard (not
>>>>>>>> enterprise, so no vmotion, etc.) ESX boxes running a number of
>>>>>>>> guests, some of which are on a SAN, some of which are on direct
>>>>>>>> attached (internal) disk.
>>>>>>>>
>>>>>>>> ESX is Version 3.5.0 Build 133630 - the VI client is 2.5.0
>>>>>>>> 103672
>>>>>>>>
>>>>>>>> The guest that's misbehaving is our Win2k3 R2 SP2 WSUS server
>>>>>>>> (also running our VIPRE enterprise console), and it's on direct
>>>>>>>> attached disk. It started hanging, so I initiated a shutdown.
>>>>>>>> After 15 minutes at the 'shutting down' dialog box without any
>>>>>>>> movement, I asked ESX to power the box down.
>>>>>>>>
>>>>>>>> I then tried to start it, and got a popup from the VI client
>>>>>>>> saying
>>>>>>>>
>>>>>>>> Error: Could not power on VM : Metadata write error.
>>>>>>>> Failed to power on VM.
>>>>>>>>
>>>>>>>> I also tried starting it from the command line, and got the following
>>>>>>>> error:
>>>>>>>>
>>>>>>>> VMControl error -999: Unknown error: The poweron
>>>>>>>> operation failed unexpectedly.
>>>>>>>>
>>>>>>>> The ESX host contains a number of production machines, so I
>>>>>>>> can't simply reboot in the middle of the day.
>>>>>>>>
>>>>>>>> I've cruised through /var/log/messages, and found messages like this:
>>>>>>>>
>>>>>>>> Apr 7 15:16:35 zesx2 cimserver: storelib-Failed to get pd infor
>>>>>>>> for ctrl 0, dev 1 Apr 7 15:16:35 zesx2 cimserver: Cannot get
>>>>>>>> information from controller 0 phy device 1 Apr 7 21:03:01 zesx2
>>>>>>>> cimserver:
>>>>>>>> storelib-GetLDList-ProcessLibCommandCall failed; rval = 0x8017
>>>>>>>> Apr 7
>>>>>>>> 21:03:01 zesx2 cimserver: Volume Cannot get logical disk data
>>>>>>>> from controller 0 Apr 7 21:03:01 zesx2 cimserver:
>>>>>>>> storelib-Failed to get pd infor for ctrl 0, dev 1 Apr 7
>>>>>>>> 21:03:01 zesx2 cimserver: Cannot get information from controller
>>>>>>>> 0 phy device 1 Apr 7 21:03:01 zesx2
>>>>>>>> cimserver: storelib-Failed to get pd infor for ctrl 0, dev 2 Apr
>>>>>>>> 7
>>>>>>>> 21:03:01 zesx2 cimserver: Cannot get information from controller
>>>>>>>> 0 phy device 2 Apr 8 07:03:00 zesx2 cimserver: storelib-Read
>>>>>>>> config failed
>>>>>>>> 0 Apr 8 07:03:00 zesx2 cimserver: Cannot get information from
>>>>>>>> controller 0 phy device 2 Apr 8 07:03:00 zesx2 cimserver:
>>>>>>>> storelib-Failed to get pd infor for ctrl 0, dev 1 Apr 8
>>>>>>>> 07:03:00
>>>>>>>> zesx2 cimserver: Cannot get information from controller 0 phy
>>>>>>>> device
>>>>>>>> 1 Apr 8 11:22:04 zesx2 cimserver: storelib-Failed to get pd
>>>>>>>> infor for ctrl 0, dev 0 Apr 8 11:22:04 zesx2 cimserver: Cannot
>>>>>>>> get information from controller 0 logical device 0 Apr 8 11:22:04
>>>>>>>> zesx2 cimserver:
>>>>>>>> storelib-Failed to get pd infor for ctrl 0, dev 2 Apr 8
>>>>>>>> 11:22:04
>>>>>>>> zesx2 cimserver: Cannot get information from controller 0 phy
>>>>>>>> device
>>>>>>>> 2 Apr 8 11:22:04 zesx2 cimserver: storelib-Failed to get pd
>>>>>>>> infor for ctrl 0, dev 1 Apr 8 11:22:04 zesx2 cimserver: Cannot
>>>>>>>> get information from controller 0 phy device 1 Apr 8 11:22:04 zesx2
>>>>>>>> cimserver:
>>>>>>>> storelib-Failed to get pd infor for ctrl 0, dev 2 Apr 8
>>>>>>>> 11:22:04
>>>>>>>> zesx2 cimserver: Cannot get information from controller 0 phy
>>>>>>>> device
>>>>>>>> 2
>>>>>>>>
>>>>>>>> Any thoughts and pointers much appreciated.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Kurt
>>>>>>>>
>>>>>>>> ~ Finally, powerful endpoint security that ISN'T a resource hog!
>>>>>>>> ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>
>>>>>>>> ~
>>>>>>>>
>>>>>>>> ~ Finally, powerful endpoint security that ISN'T a resource hog!
>>>>>>>> ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>
>>>>>>>> ~
>>>>>>>
>>>>>>> ~ Finally, powerful endpoint security that ISN'T a resource hog!
>>>>>>> ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>
>>>>>>> ~
>>>>>>>
>>>>>>>
>>>>>>> ~ Finally, powerful endpoint security that ISN'T a resource hog!
>>>>>>> ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>
>>>>>>> ~
>>>>>>
>>>>>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
>>>>>> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
>>>>>>
>>>>>>
>>>>>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
>>>>>> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
>>>>>
>>>>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
>>>>> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
>>>>>
>>>>>
>>>>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
>>>>> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
>>>>
>>>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~
>>>> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
>>>>
>>>>
>>>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~
>>>> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
>>>
>>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~
>>> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
>>>
>>>
>>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~
>>> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
>>
>> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~
>> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
>>
>>
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~
> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
>
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
