VMware Cloud Community
DavoudTeimouri
Virtuoso
Virtuoso
‎12-22-2014 04:46 AM

transport (VMDB) error-14: pipe connection has been broken

Hello,

I got this error: "transport (VMDB) error-14: pipe connection has been broken"  on some of my virtual machines and the virtual machines were restarted by HA.

Some restart tasks were unsuccessful.

Do you have any same experiences?

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
0 Kudos
6 Replies
jlutomski
Contributor
Contributor
‎11-23-2015 10:49 AM

Did you ever find a solution or workaround for this issue?

0 Kudos
rockyridge
Contributor
Contributor
‎10-10-2019 08:31 AM

Same here -  none of my VM's work

0 Kudos
jensmartens
Contributor
Contributor
‎10-15-2019 01:24 AM

exactly the same problem here. i guess the only thing we can do is snapshotting like crazy ...

had a few problems like this in the last weeks. but neither reinstall/reboots etc. helped

0 Kudos
jensmartens
Contributor
Contributor
‎10-15-2019 01:31 AM

i was not sure but i had the impression it has something to do with my monitor setup. i have just a usb-c philips, not more, connected. but when checking the logs i found this ...

(before last line...)

2019-10-15T10:28:43.019+01:00| vmx| I125: [7FFF4DBA9000-7FFF4DBB2000): /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib

2019-10-15T10:28:43.019+01:00| vmx| I125: [7FFF6EB3F000-7FFF6EC38000): /usr/lib/libcrypto.35.dylib

2019-10-15T10:28:43.019+01:00| vmx| I125: [7FFF6C173000-7FFF6C175000): /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent

2019-10-15T10:28:43.019+01:00| vmx| I125: [114079000-11407E000): /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn

2019-10-15T10:28:43.019+01:00| vmx| I125: [7FFF4F2FF000-7FFF4F30A000): /System/Library/Frameworks/PCSC.framework/Versions/A/PCSC

2019-10-15T10:28:43.019+01:00| vmx| I125: End printing loaded objects

2019-10-15T10:28:43.019+01:00| vmx| I125: Panic: monitor not available, skipping monitor coredump.

2019-10-15T10:28:43.019+01:00| vmx| I125: Exiting

0 Kudos
birend1988
Hot Shot
Hot Shot
‎10-15-2019 02:12 AM

This could be one of the reason,

disconnected iSCSI storage which crashed the storage stack.

Remove the software iSCSI storage dynamic targets and other configuration data and reboot the host.

VCIX, NCAP
0 Kudos
jensmartens
Contributor
Contributor
‎10-15-2019 02:52 AM

omg. .. powering off the vm did the trick. suspending the vm while having or not having external stuff like monitors etc. confused the boot process

0 Kudos