Cross posted from /r/vmware... We did a vmotion of a sles postgresql server last night at 10:44, which looked like it completed successfully. Then, at 11:34, get a message saying that there is insufficient video RAM allocated, resolution is going to be limted, blah blah. Next message is saying there was a heartbeat failure, also at 11:34. On the sles box, the log stops at 11:25, with no error message, and picks up at 11:34 with the boot process. I'm not sure where to look at how this happened, and would appreciate some advice. BTW, this is the vmware kb about the video ram message, that I know doesn't matter much, but wanted to include it for my posterior: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1014593&sliceId=1&docTypeID=DT_KB_1_1&dialogID=323170428&stateId=1%200%20323178384 Edit to say that both hosts are 5.0.0, 1024429, running a little bit less cpu on the new host than the old, but not enough to notice.
No dump file was created because the kdump service wasn't running. Boo. /var/log/messages posts about postgres doing normal postgres stuff at 11:25, then 11:34 we have syslog starting up.
Where else can I look? Thanks
[link][6 comments]
