1newuser's Posts

Update I was able to fix the issue from my firewall side. Thanks for help
Attached the vmkernel.log from the host earlier. The esxi host will reconnect itself without me doing anything. The disconnection happens when the backup software is trying to take snapshot of ... See more...
Attached the vmkernel.log from the host earlier. The esxi host will reconnect itself without me doing anything. The disconnection happens when the backup software is trying to take snapshot of the vm in that host or even me manually taking snapshots. 
/var/log # less vmkernel.log /var/log # less vmkernel.log | grep  SERVER1 2017-05-30T23:15:14.746Z cpu17:35804)World: vm 35807: 1466: Starting world vmm0: SERVER1 of type 8 2017-05-30T23:15:14... See more...
/var/log # less vmkernel.log /var/log # less vmkernel.log | grep  SERVER1 2017-05-30T23:15:14.746Z cpu17:35804)World: vm 35807: 1466: Starting world vmm0: SERVER1 of type 8 2017-05-30T23:15:14.746Z cpu17:35804)Sched: vm 35807: 6425: Adding world 'vmm0: SERVER1', group 'host/user', cpu: shares=-3 min=0 minLimit=-1 max=-1, mem: shares=-3 min=0 minLimit=-1 max=-1 2017-05-30T23:15:14.983Z cpu12:35804)World: vm 35809: 1466: Starting world vmm1: SERVER1 of type 8 2017-05-30T23:15:14.983Z cpu12:35804)World: vm 35810: 1466: Starting world vmm2: SERVER1 of type 8 2017-05-30T23:15:14.983Z cpu12:35804)World: vm 35811: 1466: Starting world vmm3: SERVER1 of type 8 2017-05-30T23:15:14.983Z cpu12:35804)World: vm 35812: 1466: Starting world vmm4: SERVER1 of type 8 2017-05-30T23:15:14.983Z cpu12:35804)World: vm 35813: 1466: Starting world vmm5: SERVER1 of type 8 2017-05-30T23:15:14.983Z cpu12:35804)World: vm 35814: 1466: Starting world vmm6: SERVER1 of type 8 2017-05-30T23:15:14.983Z cpu12:35804)World: vm 35815: 1466: Starting world vmm7: SERVER1 of type 8 2017-05-30T23:15:15.433Z cpu2:35820)Net: 2312: connected  SERVER1 eth0 to Data VM Network, portID 0x2000007 2017-05-30T23:16:26.180Z cpu0:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-30T23:16:26.180Z cpu0:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T15:12:20.525Z cpu1:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T15:12:20.525Z cpu1:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T15:12:20.526Z cpu1:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T15:22:24.947Z cpu6:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T15:22:24.947Z cpu6:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T15:22:24.948Z cpu6:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T15:22:27.734Z cpu2:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T15:22:27.734Z cpu2:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T15:22:27.735Z cpu2:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T15:22:29.583Z cpu8:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T15:22:29.583Z cpu8:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T15:22:29.584Z cpu8:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:00:28.491Z cpu1:214359)FSS: 5914: Failed to open file 'SERVER1_1-flat.vmdk'; Requested flags 0x1, world: 214359 [python] (Existing flags 0x4008, world: 35820 [vmx-vcpu-0: SERVER1]): Busy 2017-05-31T17:47:44.736Z cpu3:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:47:44.736Z cpu3:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:47:44.737Z cpu3:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:21.870Z cpu10:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:21.870Z cpu10:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:21.870Z cpu10:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:42.701Z cpu1:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:42.701Z cpu1:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:42.701Z cpu1:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:43.882Z cpu0:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:43.882Z cpu0:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:43.882Z cpu0:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:44.921Z cpu0:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:44.921Z cpu0:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:44.921Z cpu0:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:58.243Z cpu6:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:58.243Z cpu6:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy 2017-05-31T17:50:58.243Z cpu6:35820)etherswitch: L2Sec_EnforcePortCompliance:155: client  SERVER1 requested promiscuous mode on port 0x2000007, disallowed by vswitch policy
Multiple vm's. Unfortunately I only have 1 host at that site.Created a new vm, was able to take snapshot and delete snapshots without the host disconnecting
When creating a snapshot or deleting a snapshot exsi hosts keeps disconnecting from vcenter server. It will reconnect itself. Updated the host to the latest version exsi 5.5.0               523... See more...
When creating a snapshot or deleting a snapshot exsi hosts keeps disconnecting from vcenter server. It will reconnect itself. Updated the host to the latest version exsi 5.5.0               5230635. The vcenter server has been running the latest version 5.5.0.30500         4180648 for some time. When ssh’d into the host I see “client server requested promiscuous mode on port 0x2000007, disallowed by vswitch policy” I tried I tried turning on the under host- configuration- networking- properties- find the configuration- edit- security  Promiscuous Mode Accept. And tried creating snapshot. Still same issue. BTW: The snapshot creation/deletion does work in the host itself. It just keeps disconnecting from  vcenter server
Off course I'm logged in as root. Copied the DB again, tried both from /dev and root directory. Still same issue.
KB 2111236 https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2111236&sliceId=1&docTypeID=DT_KB_1_1&dialogID=456534559&stateId=0 0 456542155 Step 5. star... See more...
KB 2111236 https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2111236&sliceId=1&docTypeID=DT_KB_1_1&dialogID=456534559&stateId=0 0 456542155 Step 5. start the database from the new location using this command: sudo -u postgres /opt/vmware/vpostgres/1.0/bin/pg_ctl -D /storage/sdc/vpostgres start I'm getting this error "pg_ctl: could not open PID file "/storage/sdc/vpostgres/postmaster.pid": Permission denied