You are not logged in.

#1 2008-03-27 12:11:14

peque
Member
From: Denmark - Møn
Registered: 2005-06-26
Posts: 441

Machines suddenly not responding!!! in a periode

Hey Forum.

Iat work I've setup an server with Vmware - for testusage.
I'll like to have a machine for testing new things. The problem here is that the machine are not responding for a minute or two, while using the machine.
The host are not responding on SSH - and not using Vmware console.
I'm able to ping the host - and able to scan using nmap and see that the ports are opened! But still just getting - connection refused.

after the minut are passed by - I'm suddenly able to log in again on both VMware and SSH --> What can that be for a problem.
I've checked my logfiles  and are not able to find anything that should force this error. Here's some different logfiles from a periode whenm it brakes down:

/var/log/syslog:

Mar 27 11:17:54 Archie syslog-ng[3227]: syslog-ng starting up; version='2.0.6'
Mar 27 12:45:22 Archie syslog-ng[3253]: syslog-ng starting up; version='2.0.6'

dmesg:

tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
/dev/vmnet: open called by PID 3403 (vmnet-netifup)
/dev/vmnet: hub 1 does not exist, allocating memory.
/dev/vmnet: port on hub 1 successfully opened
/dev/vmnet: open called by PID 3404 (vmnet-netifup)
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 3427 (vmnet-dhcpd)
/dev/vmnet: port on hub 1 successfully opened
/dev/vmnet: open called by PID 3428 (vmnet-dhcpd)
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 3443 (vmware-vmx)
device eth0 entered promiscuous mode
bridge-eth0: enabled promiscuous mode
/dev/vmnet: port on hub 0 successfully opened
[3455]: host clock rate change request 0 -> 19
[3455]: host clock rate change request 19 -> 0
[3455]: host clock rate change request 0 -> 100
[3455]: host clock rate change request 100 -> 0
[3455]: host clock rate change request 0 -> 411
[3455]: host clock rate change request 411 -> 511
[3455]: host clock rate change request 511 -> 0
[3455]: host clock rate change request 0 -> 62
[3455]: host clock rate change request 62 -> 68

/var/log/messages:

Mar 27 12:45:29 Archie vmnet-dhcpd: Recving on     VNet/vmnet8/172.16.16.0
Mar 27 12:45:29 Archie vmnet-dhcpd: Sending on     VNet/vmnet8/172.16.16.0
Mar 27 12:46:39 Archie device eth0 entered promiscuous mode
Mar 27 12:46:39 Archie bridge-eth0: enabled promiscuous mode

/var/log/errors:

Mar 27 12:06:03 Archie vmware-authd[4317]: pam_unix2(vmware-authd:setcred): Unknown option: `shadow'
Mar 27 12:45:22 Archie pnpacpi: exceeded the max number of IO resources: 40 
Mar 27 12:46:13 Archie vmware-authd[3437]: pam_unix2(vmware-authd:auth): Unknown option: `shadow'
Mar 27 12:46:13 Archie vmware-authd[3437]: pam_unix2(vmware-authd:setcred): Unknown option: `shadow'
Mar 27 12:46:39 Archie vmware-authd[3459]: pam_unix2(vmware-authd:auth): Unknown option: `shadow'
Mar 27 12:46:39 Archie vmware-authd[3459]: pam_unix2(vmware-authd:setcred): Unknown option: `shadow'

/var/log/everything: (same as syslog)

Mar 27 12:46:39 Archie bridge-eth0: enabled promiscuous mode
Mar 27 12:46:39 Archie /dev/vmnet: port on hub 0 successfully opened
Mar 27 12:46:39 Archie [3455]: host clock rate change request 0 -> 19
Mar 27 12:46:51 Archie [3455]: host clock rate change request 19 -> 0
Mar 27 12:46:51 Archie [3455]: host clock rate change request 0 -> 100
Mar 27 12:47:06 Archie [3455]: host clock rate change request 100 -> 0
Mar 27 12:47:06 Archie [3455]: host clock rate change request 0 -> 411

/var/log/vmware/vmware-serverd.log

Mar 27 12:46:38: app| VMServerdConnect: connecting to /data/Ubuntu/Ubuntu.vmx
Mar 27 12:46:39: app| Connected to /data/Ubuntu/Ubuntu.vmx
Mar 27 12:46:39: app| SP: Retrieved username: root
Mar 27 12:46:39: app| Trimming event log for /data/Ubuntu/Ubuntu.vmx by 2 lines...
Mar 27 12:46:39: app| VM suddenly changed state: poweredOn.
Mar 27 12:46:39: app| SP: Retrieved username: root
Mar 27 12:46:39: app| SP: Retrieved username: root
Mar 27 12:46:40: app| cleanup: cleaned up 2 objects
Mar 27 12:47:25: app| VmsdRegister: Config file has changed: /data/Ubuntu/Ubuntu.vmx
Mar 27 13:05:15: app| OvlHostStartIo: errno 104
Mar 27 13:05:15: app| vmdbPipe_Streams: Couldn't read
Mar 27 13:05:15: app| SP: Deleting user session: 0 username: root

So what is happening here - and can I do something about it - Carse having a server - which several times each hour are bnot responding - is no use for anybody.
So waiting for your answer on this one???
Thanks
P


Just getting better .... All the time

Offline

#2 2008-03-28 09:09:26

Sin.citadel
Member
Registered: 2008-01-22
Posts: 267

Re: Machines suddenly not responding!!! in a periode

ur saying that, once u start the VM, the machine doesnt respond to all attemps to using vmware console (i dont know that much bout SSH), when u start the vm, do u still see the the output in the vmware machine window, also check if ur system is not using most of its CPU cycles before starting virtual machine. also, is the VM not responding only happens at the beginning of the vm startup, or is it random.

Offline

Board footer

Powered by FluxBB