VMware Cloud Community
urahara
Contributor
Contributor

VM of Esxi 6 crash after too many TSE connexion (episode 2)

Hi guys,

My problem is back after 3 months !

Here the precedent ticket : https://communities.vmware.com/thread/514949

And the log file after the crash.

Nothing has been modified during this 3 months :smileyconfused:

The only weird thing is the 100% HDD activity (picture attached) that doen't go down.

any help would be very appreciated ! Thanks

2015-10-27T13:17:46.518Z| vcpu-0| I120: GuestMsg: Too many channels opened.

2015-10-27T13:17:46.518Z| vcpu-0| I120: GuestMsg: Too many channels opened.

2015-10-27T13:17:50.105Z| vmx| I120: GuestRpc: Too many RPCI vsocket channels opened.

2015-10-27T13:17:50Z[+0.000]| vmx| W110: Caught signal 11 -- tid 95060 (addr 26460D50)

2015-10-27T13:17:50Z[+0.000]| vmx| I120: SIGNAL: rip 0x251551f1 rsp 0x3ffd240c960 rbp 0x3ffd240c990

2015-10-27T13:17:50Z[+0.000]| vmx| I120: SIGNAL: rax 0x261e0d70 rbx 0x32510210 rcx 0x1 rdx 0x4fffb rsi 0x0 rdi 0x32000130

2015-10-27T13:17:50Z[+0.000]| vmx| I120:         r8 0x3ffd240c701 r9 0x204943505220796e r10 0x2074656b636f7376 r11 0x0 r12 0xffff r13 0xffff r14 0x1 r15 0x3ffd240ca2c

2015-10-27T13:17:50Z[+0.000]| vmx| I120: SIGNAL: stack 3FFD240C960 : 0x0000000000000000 0x0000000032606950

2015-10-27T13:17:50Z[+0.000]| vmx| I120: SIGNAL: stack 3FFD240C970 : 0x0000000032606ac8 0x0000000032606950

2015-10-27T13:17:50Z[+0.000]| vmx| I120: SIGNAL: stack 3FFD240C980 : 0x0000000032606ac8 0x000000003240ae80

2015-10-27T13:17:50Z[+0.000]| vmx| I120: SIGNAL: stack 3FFD240C990 : 0x000003ffd240c9e0 0x00000000252a7bd9

2015-10-27T13:17:50Z[+0.000]| vmx| I120: SIGNAL: stack 3FFD240C9A0 : 0x000003f700000000 0x00000000a64294ae

2015-10-27T13:17:50Z[+0.000]| vmx| I120: SIGNAL: stack 3FFD240C9B0 : 0x0000000032513000 0x000000003240c580

2015-10-27T13:17:50Z[+0.000]| vmx| I120: SIGNAL: stack 3FFD240C9C0 : 0x000003ffd240c9e0 0x000003ffd263c010

2015-10-27T13:17:50Z[+0.000]| vmx| I120: SIGNAL: stack 3FFD240C9D0 : 0x0000000000000000 0x00000000323d25c0

2015-10-27T13:17:50Z[+0.000]| vmx| I120: Backtrace:

2015-10-27T13:17:50Z[+0.002]| vmx| I120: Backtrace[0] 000003ffd240c480 rip=00000000255fc04e rbx=00000000255fbb30 rbp=000003ffd240c4a0 r12=0000000000000000 r13=000003ffd24118c0 r14=000003ffd240c9e0 r15=000000000000000b

2015-10-27T13:17:50Z[+0.002]| vmx| I120: Backtrace[1] 000003ffd240c4b0 rip=00000000256667bc rbx=000000000000000b rbp=000003ffd240c680 r12=0000000000000000 r13=000003ffd24118c0 r14=000003ffd240c9e0 r15=000000000000000b

2015-10-27T13:17:50Z[+0.002]| vmx| I120: Backtrace[2] 000003ffd240c690 rip=00000000003bd00f rbx=0000000032510210 rbp=000003ffd240c8d0 r12=000003ffd240c710 r13=000000000000ffff r14=0000000000000001 r15=000003ffd240ca2c

2015-10-27T13:17:50Z[+0.002]| vmx| I120: SymBacktrace[0] 000003ffd240c480 rip=00000000255fc04e in function (null) in object /bin/vmx loaded at 0000000024f0c000

2015-10-27T13:17:50Z[+0.002]| vmx| I120: SymBacktrace[1] 000003ffd240c4b0 rip=00000000256667bc in function (null) in object /bin/vmx loaded at 0000000024f0c000

2015-10-27T13:17:50Z[+0.002]| vmx| I120: SymBacktrace[2] 000003ffd240c690 rip=00000000003bd00f

2015-10-27T13:17:50Z[+0.002]| vmx| I120: Unexpected signal: 11.

2015-10-27T13:17:50Z[+94.555]| vmx| W110: A core file is available in "/vmfs/volumes/53dc319c-b50abf59-ed6b-9c8e99671274/SERVEUR2008/vmx-zdump.002"

2015-10-27T13:17:50Z[+94.555]| vmx| W110: Writing monitor corefile "/vmfs/volumes/53dc319c-b50abf59-ed6b-9c8e99671274/SERVEUR2008/vmmcores.gz"

2015-10-27T13:17:50Z[+94.761]| vmx| W110: Dumping core for vcpu-0

2015-10-27T13:17:50Z[+94.761]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-10-27T13:17:50Z[+94.761]| vmx| I120: VMK Stack for vcpu 0 is at 0x43945ab13000

2015-10-27T13:17:50Z[+94.761]| vmx| I120: Beginning monitor coredump

2015-10-27T13:17:50Z[+95.418]| vmx| I120: End monitor coredump

2015-10-27T13:17:50Z[+95.419]| vmx| W110: Dumping core for vcpu-1

2015-10-27T13:17:50Z[+95.419]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-10-27T13:17:50Z[+95.419]| vmx| I120: VMK Stack for vcpu 1 is at 0x43945ac13000

2015-10-27T13:17:50Z[+95.419]| vmx| I120: Beginning monitor coredump

2015-10-27T13:17:50Z[+96.042]| vmx| I120: End monitor coredump

2015-10-27T13:17:50Z[+96.042]| vmx| W110: Dumping core for vcpu-2

2015-10-27T13:17:50Z[+96.042]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-10-27T13:17:50Z[+96.042]| vmx| I120: VMK Stack for vcpu 2 is at 0x43945ac93000

2015-10-27T13:17:50Z[+96.042]| vmx| I120: Beginning monitor coredump

2015-10-27T13:17:50Z[+96.667]| vmx| I120: End monitor coredump

2015-10-27T13:17:50Z[+96.667]| vmx| W110: Dumping core for vcpu-3

2015-10-27T13:17:50Z[+96.667]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-10-27T13:17:50Z[+96.667]| vmx| I120: VMK Stack for vcpu 3 is at 0x43945ad13000

2015-10-27T13:17:50Z[+96.667]| vmx| I120: Beginning monitor coredump

2015-10-27T13:17:50Z[+97.292]| vmx| I120: End monitor coredump

2015-10-27T13:17:50Z[+97.293]| vmx| W110: Dumping core for vcpu-4

2015-10-27T13:17:50Z[+97.293]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-10-27T13:17:50Z[+97.293]| vmx| I120: VMK Stack for vcpu 4 is at 0x43945ad93000

2015-10-27T13:17:50Z[+97.293]| vmx| I120: Beginning monitor coredump

2015-10-27T13:17:50Z[+97.916]| vmx| I120: End monitor coredump

2015-10-27T13:17:50Z[+97.917]| vmx| W110: Dumping core for vcpu-5

2015-10-27T13:17:50Z[+97.917]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-10-27T13:17:50Z[+97.917]| vmx| I120: VMK Stack for vcpu 5 is at 0x43945ae13000

2015-10-27T13:17:50Z[+97.917]| vmx| I120: Beginning monitor coredump

2015-10-27T13:17:50Z[+98.544]| vmx| I120: End monitor coredump

2015-10-27T13:17:50Z[+98.545]| vmx| W110: Dumping core for vcpu-6

2015-10-27T13:17:50Z[+98.545]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-10-27T13:17:50Z[+98.545]| vmx| I120: VMK Stack for vcpu 6 is at 0x43945ae93000

2015-10-27T13:17:50Z[+98.545]| vmx| I120: Beginning monitor coredump

2015-10-27T13:17:50Z[+99.169]| vmx| I120: End monitor coredump

2015-10-27T13:17:50Z[+99.170]| vmx| W110: Dumping core for vcpu-7

2015-10-27T13:17:50Z[+99.170]| vmx| I120: CoreDump: dumping core with superuser privileges

2015-10-27T13:17:50Z[+99.170]| vmx| I120: VMK Stack for vcpu 7 is at 0x43945af13000

2015-10-27T13:17:50Z[+99.170]| vmx| I120: Beginning monitor coredump

2015-10-27T13:17:50Z[+99.796]| vmx| I120: End monitor coredump

2015-10-27T13:17:50Z[+107.351]| vmx| I120: Backtrace:

2015-10-27T13:17:50Z[+107.351]| vmx| I120: Backtrace[0] 000003ffd240bf80 rip=00000000255fc04e rbx=00000000255fbb30 rbp=000003ffd240bfa0 r12=0000000000000000 r13=000003ffd24118c0 r14=000003ffd240c9e0 r15=000000000000000b

2015-10-27T13:17:50Z[+107.351]| vmx| I120: Backtrace[1] 000003ffd240bfb0 rip=00000000250a98ba rbx=00000000262b1648 rbp=000003ffd240c4a0 r12=0000000000000001 r13=000003ffd24118c0 r14=000003ffd240c9e0 r15=000000000000000b

2015-10-27T13:17:50Z[+107.351]| vmx| I120: Backtrace[2] 000003ffd240c4b0 rip=0000000025666816 rbx=000000000000000b rbp=000003ffd240c680 r12=0000000000000000 r13=000003ffd24118c0 r14=000003ffd240c9e0 r15=000000000000000b

2015-10-27T13:17:50Z[+107.351]| vmx| I120: Backtrace[3] 000003ffd240c690 rip=00000000003bd00f rbx=0000000032510210 rbp=000003ffd240c8d0 r12=000003ffd240c710 r13=000000000000ffff r14=0000000000000001 r15=000003ffd240ca2c

2015-10-27T13:17:50Z[+107.351]| vmx| I120: SymBacktrace[0] 000003ffd240bf80 rip=00000000255fc04e in function (null) in object /bin/vmx loaded at 0000000024f0c000

2015-10-27T13:17:50Z[+107.351]| vmx| I120: SymBacktrace[1] 000003ffd240bfb0 rip=00000000250a98ba in function (null) in object /bin/vmx loaded at 0000000024f0c000

2015-10-27T13:17:50Z[+107.351]| vmx| I120: SymBacktrace[2] 000003ffd240c4b0 rip=0000000025666816 in function (null) in object /bin/vmx loaded at 0000000024f0c000

2015-10-27T13:17:50Z[+107.351]| vmx| I120: SymBacktrace[3] 000003ffd240c690 rip=00000000003bd00f

2015-10-27T13:17:50Z[+107.351]| vmx| I120: Msg_Post: Error

2015-10-27T13:17:50Z[+107.351]| vmx| I120: [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (vmx)

2015-10-27T13:17:50Z[+107.351]| vmx| I120+ Unexpected signal: 11.

2015-10-27T13:17:50Z[+107.351]| vmx| I120: [msg.panic.haveLog] A log file is available in "/vmfs/volumes/53dc319c-b50abf59-ed6b-9c8e99671274/SERVEUR2008/vmware.log". 

2015-10-27T13:17:50Z[+107.351]| vmx| I120: [msg.panic.requestSupport.withoutLog] You can request support. 

2015-10-27T13:17:50Z[+107.351]| vmx| I120: [msg.panic.requestSupport.vmSupport.vmx86]

2015-10-27T13:17:50Z[+107.351]| vmx| I120+ To collect data to submit to VMware technical support, run "vm-support".

2015-10-27T13:17:50Z[+107.351]| vmx| I120: [msg.panic.response] We will respond on the basis of your support entitlement.

2015-10-27T13:17:50Z[+107.351]| vmx| I120: ----------------------------------------

2015-10-27T13:17:50Z[+107.356]| vmx| I120: Vigor_MessageRevoke: message 'msg.panic.response' (seq 943865) is revoked

2015-10-27T13:17:50Z[+107.356]| vmx| I120: Exiting

Tags (3)
0 Kudos
0 Replies