Hallo,
In de nacht van zaterdag op zondag is een virtuele machine (DC01) uitgevallen met volgende meldingen in vmware:
Error message on DC01 - 10.10.100.100 on wks-16-08-069.gonnijlen.be in ha-datacenter: We will respond on the basis of your support entitlement.
DC01 - 10.10.100.100 on wks-16-08-069.gonnijlen.be in ha-datacenter is powered off
Gelukkig konden we hem vanmorgen wel gewoon terug opzetten, na power on klikken en enkele minuten stond hij terug aan. Daarna zijn we op zoek gegaan naar de oorzaak, event viewer gaf niets merkwaardig aan, konden alleen uit opmaken dat de machine onverwacht is afgesloten.
In de vmware log kwam ik wel volgende "panic" fout tegen: vcpu-0| E105: PANIC: MXUserAllocSerialNumber: too many locks!
In bijlage enkele extra regels log, ik merk op dat de fout "uit het niets" komt omdat laatste data daarvoor enkele dagen scheelt.
Volgens dit KB artikel zou het opgelost zijn in onze huidige versie vsphere 6.5 maar is er blijkbaar toch door gekomen, heeft het zin de workaround nog te doen? Verder nog ideeën om dit in de toekomst te vermijden?
Mvg,
Kristof
Hello GithoNijlen,
I translated and identified that the VM is crashing
2017-05-21T01:29:05.845Z| vcpu-0| I125: SymBacktrace[19] 0000003fbf71cd68 rip=0000000000000000
2017-05-21T01:29:05.845Z| vcpu-0| I125: Msg_Post: Error
2017-05-21T01:29:05.845Z| vcpu-0| I125: [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (vcpu-0)
2017-05-21T01:29:05.845Z| vcpu-0| I125+ MXUserAllocSerialNumber: too many locks!
2017-05-21T01:29:05.845Z| vcpu-0| I125: [msg.panic.haveLog] A log file is available in "/vmfs/volumes/589474ea-2a9e3a4d-31dd-3ca82ae487a8/DC01 - 10.10.100.100/vmware.log".
2017-05-21T01:29:05.845Z| vcpu-0| I125: [msg.panic.requestSupport.withoutLog] You can request support.
2017-05-21T01:29:05.845Z| vcpu-0| I125: [msg.panic.requestSupport.vmSupport.vmx86]
2017-05-21T01:29:05.845Z| vcpu-0| I125+ To collect data to submit to VMware technical support, run "vm-support".
2017-05-21T01:29:05.845Z| vcpu-0| I125: [msg.panic.response] We will respond on the basis of your support entitlement.
2017-05-21T01:29:05.845Z| vcpu-0| I125: ----------------------------------------
This issue is not fixed yet as per the below KB. Please find the workaround on this
VM's PANIC: MXUserAllocSerialNumber: too many locks (2149941) | VMware KB
Hello GithoNijlen,
I translated and identified that the VM is crashing
2017-05-21T01:29:05.845Z| vcpu-0| I125: SymBacktrace[19] 0000003fbf71cd68 rip=0000000000000000
2017-05-21T01:29:05.845Z| vcpu-0| I125: Msg_Post: Error
2017-05-21T01:29:05.845Z| vcpu-0| I125: [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (vcpu-0)
2017-05-21T01:29:05.845Z| vcpu-0| I125+ MXUserAllocSerialNumber: too many locks!
2017-05-21T01:29:05.845Z| vcpu-0| I125: [msg.panic.haveLog] A log file is available in "/vmfs/volumes/589474ea-2a9e3a4d-31dd-3ca82ae487a8/DC01 - 10.10.100.100/vmware.log".
2017-05-21T01:29:05.845Z| vcpu-0| I125: [msg.panic.requestSupport.withoutLog] You can request support.
2017-05-21T01:29:05.845Z| vcpu-0| I125: [msg.panic.requestSupport.vmSupport.vmx86]
2017-05-21T01:29:05.845Z| vcpu-0| I125+ To collect data to submit to VMware technical support, run "vm-support".
2017-05-21T01:29:05.845Z| vcpu-0| I125: [msg.panic.response] We will respond on the basis of your support entitlement.
2017-05-21T01:29:05.845Z| vcpu-0| I125: ----------------------------------------
This issue is not fixed yet as per the below KB. Please find the workaround on this
VM's PANIC: MXUserAllocSerialNumber: too many locks (2149941) | VMware KB
HI,
Thanks for taking the time to translate and respond, I thought this would be a dutch only forum as everything is displayed in that language for me.
Anyway we implemented the workaround on the affected machine and also preempavly modified the setting on some other critical machines.
Kind regards