Robert121281 Tracker

VDS uplink ports (VLAN Trunking) - Enforced?

Robert121281 — Thu, 14 Jan 2021 20:52:21 GMT

Hi,

I am running a VDS version 7.0. In my uplink port-group, there are 2 ports. Let's say on my physical switches I allow VLAN 100-200. My uplink port-group should be configured as well with 100-200, so the allowed VLANs match on on both ends

I figured out that even if I would only allow VLAN 100 on the VDS, I can still reach everything in other VLANs behind my VDS. Does this VLAN allowed list have any effect on the VDS side? Looks like whatever I configure there, it just makes no difference. I get traffic for those VLANs in (they obviously need to be allowed on the physical side).

Thanks for your help.

Regards,

Robert

DVS - ERSPAN - Egress Direction on Trunk not working

Robert121281 — Mon, 11 Jan 2021 19:41:45 GMT

Hi Guys,

Running: VMware ESXi, 7.0.1, 17119627

I have setup ERSPAN on the DVS, works basically. However, I get ingress/egress traffic only for non-trunk ports (access in a particular VLAN). If I have ERSPAN ingress/egress enabled on a trunk port (VLAN 0-4095), I only receive ingress traffic (traffic coming form the VM to the DVS).

Is this a known limitation? A bug? Can I somehow get the egress direction spanned to IPv4 destination?

Thanks + Best regards,

Robert

VCSA update to 7.0.0.10300 (build 16189094) - vCenter still informs "New vCenter server updates are available"

Robert121281 — Fri, 22 May 2020 12:50:48 GMT

Hello,

I have upgraded vCenter from GA to 7.0.0.10300 (build 16189094). vCenter Management summary tab tells:

- Version: 7.0.0.10300

- Build number: 16189094

VCSA has been rebooted as well (even though upgrade did not ask for that).

When I log into vCenter i get the message: New vCenter server updates are available -> View Updates

In vCenter itself it tells me about version 7.0.0 (Updates Available), build 16189207.

Does anybody have this issue as well? Any idea how to fix it?

Thanks,

Robert

ESXi670-202004001.zip - [StatelessError] - The transaction is not supported: VIB VMware_bootbank_esx-base_6.7.0-3.94.15820472 cannot be live installed

Robert121281 — Thu, 16 Apr 2020 14:41:21 GMT

Hi!

I am trying to install the patch ESXi670-202004001.zip. Current version:

esxcli system version get

Product: VMware ESXi

Version: 6.7.0

Build: Releasebuild-15160138

Update: 3

Patch: 89

esxcli software vib update -d "/vmfs/volumes/DS-SHARED-01/01-ESXi-Patches/ESXi670-202004001.zip"

[StatelessError]

The transaction is not supported: VIB VMware_bootbank_esx-base_6.7.0-3.94.15820472 cannot be live installed. VIB VMware_bootbank_vsan_6.7.0-3.94.15736744 cannot be live installed. VIB VMware_bootbank_esx-update_6.7.0-3.94.15820472 cannot be live installed. VIB VMware_bootbank_esx-base_6.7.0-3.89.15160138 cannot be removed live. VIB VMware_bootbank_vsan_6.7.0-3.89.14840357 cannot be removed live. VIB VMware_bootbank_esx-update_6.7.0-3.89.15160138 cannot be removed live.

Please refer to the log file for more details.

Yes, the host is in maintenance mode. I rebooted it as well like all people say. And put it out and back in maintenance mode. No change. ESXi ist installed on a 8 GB Fibre Channel volume. The file is fine, checked MD5. Path is good.

Not sure about the size required. Does not seem to be much free space on certain mounts. However, the main one has 3.9 GB free. When I installed ESXi, there was as well some datastore created, which I have deleted. The patch is in a remote datastore (via FC). If I do copy it to a local directory, same issue.

Filesystem Size Used Available Use% Mounted on

VMFS-6 3.6T 3.4T 206.3G 94% /vmfs/volumes/SHARED

vfat 4.0G 51.1M 3.9G 1% /vmfs/volumes/5c83e940-194e4730-deac-0025b5aa0000

vfat 249.7M 149.1M 100.7M 60% /vmfs/volumes/d9ed827c-8e09d1db-579e-5a41a1f021c7

vfat 249.7M 149.1M 100.7M 60% /vmfs/volumes/418f6471-ef7fdaa3-c3fd-eededdb4a122

vfat 285.8M 195.8M 90.1M 68% /vmfs/volumes/5c83e92d-351bd16e-9f9a-0025b5aa0000

After that my host is "not responding" in vCenter. It is not a network issue (this is based on the failed update?). Not sure why this happend.

I always update the hosts that way. Have done all the patches in the past like that. This time, i am getting this error. The error tells to check the log. Which log - why does it not mention the file to check right away? Checked esxupdate.log. I have attached the file.

Any ideas how to get this fixed?

Thanks!

Best regards,

Robert

Re: Vcenter installation Failure: "Failed to send http data"

Robert121281 — Mon, 17 Dec 2018 14:38:12 GMT

Thanks for your reply. I was deploying the vCSA on a NFS datastore mounted with NFS 4.1. The NFS share was provided by an Ubuntu server (nfs-kernel-server). There were problems creating the files on the NFS DS.

2018-12-13T10:55:18.226Z info hostd[2100244] [Originator@6876 sub=DiskLib] DISKLIB-VMFS : "/vmfs/volumes/1f1d7a8f-5ef53b0c-0000-000000000000/VMware vCenter Server Appliance (P)/VMware vCenter Server Appliance (P)-flat.vmdk" : failed to open (The file specified is not a virtual disk): Size of extent in descriptor file larger than real size. Type 3

2018-12-13T10:55:18.226Z info hostd[2100244] [Originator@6876 sub=DiskLib] DISKLIB-LINK : "/vmfs/volumes/1f1d7a8f-5ef53b0c-0000-000000000000/VMware vCenter Server Appliance (P)/VMware vCenter Server Appliance (P).vmdk" : failed to open (The file specified is not a virtual disk).

2018-12-13T10:55:18.227Z info hostd[2100244] [Originator@6876 sub=DiskLib] DISKLIB-CHAIN : "/vmfs/volumes/1f1d7a8f-5ef53b0c-0000-000000000000/VMware vCenter Server Appliance (P)/VMware vCenter Server Appliance (P).vmdk" : failed to open (The file specified is not a virtual disk).

2018-12-13T10:55:18.227Z info hostd[2100244] [Originator@6876 sub=DiskLib] DISKLIB-LIB : Failed to open '/vmfs/volumes/1f1d7a8f-5ef53b0c-0000-000000000000/VMware vCenter Server Appliance (P)/VMware vCenter Server Appliance (P).vmdk' with flags 0x8 The file specified is not a virtual disk (15).

Deployment on another datastore was fine. I found that people have some problems with NFS 4.1, reporting similar issues when booting VMs etc. Deployment on iSCSI or NFS 3 mounted datastore is fine.

Anybody managed to run NFS 4.1 with an Ubuntu (or other Linux) provided NFS share? Same issues I have when mounting NFS 4.1 from Debian. Share configuration is quite simple:

/nfs *(rw,no_root_squash,async,no_subtree_check)

Thanks,

Robert

Re: Vcenter installation Failure: "Failed to send http data"

Robert121281 — Wed, 12 Dec 2018 08:28:41 GMT

That's how the logs look for me. The issue is with the ovftool:

-->

2018-12-12T08:00:32.966+01:00 trivia OVFTool[01168] [Originator@6876 sub=Default] CURL: => Sending SSL data of size 5

2018-12-12T08:00:32.966+01:00 trivia OVFTool[01168] [Originator@6876 sub=Default] CURL: TLSv1.2 (OUT), TLS alert, Client hello (1):

-->

2018-12-12T08:00:32.966+01:00 trivia OVFTool[01168] [Originator@6876 sub=Default] CURL: => Sending SSL data of size 2

2018-12-12T08:00:32.966+01:00 verbose OVFTool[03932] [Originator@6876 sub=Default] Closing image source and targets

2018-12-12T08:00:32.966+01:00 verbose OVFTool[03932] [Originator@6876 sub=Default] Bad return code from POST request: 404

2018-12-12T08:00:32.966+01:00 error OVFTool[03932] [Originator@6876 sub=Default] Error closing image-target

2018-12-12T08:00:32.966+01:00 error OVFTool[03932] [Originator@6876 sub=Default] Error: class boost::exception_detail::clone_impl<struct boost::exception_detail::error_info_injector<class OvfToolException> >(Bad response code (404) from POST request)

--> [context]zKq7AUsEAQAAAH9cjQAUT1ZGVG9vbAAAA5Yadm1hY29yZS5kbGwAAOlyBQALlQUAzRYCAUOiAW92ZnRvb2wuZXhlAAHI7gsBsIgKAYhUBQEPkwUBC4gFAch5BQH6lwUBZJsFAJakFwAnmRgAu4gbAl2qA3VjcnRiYXNlLkRMTAADyjMBa2VybmVsMzIuZGxsAATSngNudGRsbC5kbGwABKWeAw==[/context]

2018-12-12T08:00:32.966+01:00 verbose OVFTool[03932] [Originator@6876 sub=Default] Connection error during upload

2018-12-12T08:00:32.966+01:00 verbose OVFTool[04156] [Originator@6876 sub=Default] Connection error, sleep then retry (10 remaining)

2018-12-12T08:00:37.978+01:00 verbose OVFTool[04156] [Originator@6876 sub=Default] Exception thrown: class boost::exception_detail::clone_impl<struct boost::exception_detail::error_info_injector<class OvfToolConnectionException> >(Failed to send http data)

--> [context]zKq7AUsEAQAAAH9cjQATT1ZGVG9vbAAAA5Yadm1hY29yZS5kbGwAAOlyBQALlQUAzRYCAeOeCW92ZnRvb2wuZXhlAAFTngkBqLsKAaiRBQELiAUByHkFAfqXBQFkmwUAlqQXACeZGAC7iBsCXaoDdWNydGJhc2UuRExMAAPKMwFrZXJuZWwzMi5kbGwABNKeA250ZGxsLmRsbAAEpZ4D[/context]

2018-12-12T08:00:37.978+01:00 verbose OVFTool[04156] [Originator@6876 sub=Default] Backtrace:

--> [backtrace begin] product: VMware Workstation, version: e.x.p, build: build-9264255, tag: OVFTool, cpu: x86, os: windows, buildType: release

--> backtrace[00] vmacore.dll[0x001A9603]

--> backtrace[01] vmacore.dll[0x000572E9]

--> backtrace[02] vmacore.dll[0x0005950B]

--> backtrace[03] vmacore.dll[0x000216CD]

--> backtrace[04] ovftool.exe[0x00099EE3]

--> backtrace[05] ovftool.exe[0x00099E53]

--> backtrace[06] ovftool.exe[0x000ABBA8]

--> backtrace[07] ovftool.exe[0x000591A8]

--> backtrace[08] ovftool.exe[0x0005880B]

--> backtrace[09] ovftool.exe[0x000579C8]

--> backtrace[10] ovftool.exe[0x000597FA]

--> backtrace[11] ovftool.exe[0x00059B64]

--> backtrace[12] vmacore.dll[0x0017A496]

--> backtrace[13] vmacore.dll[0x00189927]

--> backtrace[14] vmacore.dll[0x001B88BB]

--> backtrace[15] ucrtbase.DLL[0x0003AA5D]

--> backtrace[16] kernel32.dll[0x000133CA]

--> backtrace[17] ntdll.dll[0x00039ED2]

--> backtrace[18] ntdll.dll[0x00039EA5]

--> [backtrace end]

2018-12-12T08:00:37.978+01:00 verbose OVFTool[04156] [Originator@6876 sub=Default] [Vi4Target::Abort] started.

Anybody seen the same problem?

Thanks,

Robert

Re: Vcenter installation Failure: "Failed to send http data"

Robert121281 — Tue, 11 Dec 2018 23:13:29 GMT

This issue has nothing to do with the DNS. I have tried to deploy 6.7U1 from different hosts on different hosts. It is not working at all. There is no difference using the IP or the FQDN, no difference. You can enter the data, it fails. Try again - it goes to 20% and fails. Try again with the same data, fails again. It is totally random. I did try this on fresh installed hosts, fresh laptop, VM to perform the installation on. Nothing to do with any firewall either. DNS is fine. All entries are properly set and resolve fine.

Regards,

Robert

Re: vCenter 6.7U1 Deloyment - Installer does not load - white/empty window

Robert121281 — Tue, 11 Dec 2018 16:02:55 GMT

Issue does apply as well to other vCSA 6.7 versions.

- Yes, I rebooted the host and the computer where I am deploying from

- I deleted all temp data I found in the usual windows directories, does not help

- The imagine/iso is fine, MD5 etc. - no issue

Thanks,

Robert

vCenter 6.7U1 Deloyment - Installer does not load - white/empty window

Robert121281 — Tue, 11 Dec 2018 15:35:41 GMT

Hi guys,

I am trying to deploy vCSA 6.7U1 - VMware-VCSA-all-6.7.0-10244745. The installer starts, however I am presented with a white screen.

There is no content. It worked in the past, now it does not anymore. Does anybody know how to fix this please?

BTW: When the installer did start in the past, it did not work either:

- HTTP error, cannot send data (no, it has nothing to do with DNS, that is fine, as well not with using DNS name or FQDN - does not matter)

- Does not work on two machines

- Independent of the host the vCSA will be deployed on

Software quality is horrible.

Thanks,

Robert

Re: vCenter Server Appliance 6.7U1 Deployment fails with "Vpxd VA Post-install script failed: ..."

Robert121281 — Fri, 07 Dec 2018 15:07:50 GMT

Thanks for your answer. Input values do not matter because it works in 6.7 and not in 6.7U1. Values are _identical_. Hence, it is independent of the given values, IP, mask, domain etc.

Thanks,

Robert

Re: vCenter Server Appliance 6.7U1 Deployment fails with "Vpxd VA Post-install script failed: ..."

Robert121281 — Fri, 07 Dec 2018 10:45:35 GMT

Deploying VMware-VCSA-all-6.7.0-8217866.iso works fine. All with the same parameters/values as used in VMware-VCSA-all-6.7.0-10244745. OK fine, I can patch this now to U1. However, I think this is not the idea in the first place. Anybody facing the same issue when deploying VMware-VCSA-all-6.7.0-10244745.iso (vCSA 6.7U1).

Thanks,

Robert

vCenter Server Appliance 6.7U1 Deployment fails with "Vpxd VA Post-install script failed: ..."

Robert121281 — Fri, 07 Dec 2018 09:46:52 GMT

Hi Team,

I have deployed several ESXi hosts with VMware_ESXi_6.7.0_10302608_Custom_Cisco_6.7.1.1.iso + patched with ESXi670-201811001.zip. While deploying vCenter Appliance 6.7U1 (VMware-VCSA-all-6.7.0-10244745_6.7U1.ios) - Windows UI installer - I am getting the following error:

I tried it twice, same issue. Installer is stuck at 99% for hours.

The logs tell nothing of interest for the time mentioned.

Thanks for your help.

Regards,

Robert

Re: Unable to log into vCenter 6.7 VMware Appliance Management page

Robert121281 — Wed, 10 Oct 2018 07:05:34 GMT

I told several times - It is not a password issue. I did change the password to a different one and so on. It has nothing to do with the password. It is not working. This issue is not related to known bugs (certain chars in the password) and/or expired password.

Thanks,

Robert

Re: Unable to log into vCenter 6.7 VMware Appliance Management page

Robert121281 — Mon, 01 Oct 2018 17:56:37 GMT

Hi Benedikt,

Thanks. I did just now. Same situation

Regards,

Robert

Re: Unable to log into vCenter 6.7 VMware Appliance Management page

Robert121281 — Sun, 30 Sep 2018 19:25:38 GMT

Thanks. No, there is no colon. It is not a password/credentials issue. I can enter whatever credentials and I do get the same error. The https request has issues. It is a problem with the http-server/proxy responsible for this web interface.

I have checked the logs. The logs started the day I patched the appliance with "VMware-vCenter-Server-Appliance-6.7.0.14000-9451876-patch-FP". Hence, there is an obvious dependency to this patch.

You guys have this "abyss.log" in the root directory? It is weird, but guess this particular file has nothing to do with the issue. Only problem is, that it eats up the root partition space.

Best regards,

Robert

Re: Unable to log into vCenter 6.7 VMware Appliance Management page

Robert121281 — Sun, 30 Sep 2018 14:35:41 GMT

It is a lab, licensed. Not sure if this allows me to open an SR for this.

Regards,

Robert

Re: Unable to log into vCenter 6.7 VMware Appliance Management page

Robert121281 — Sun, 30 Sep 2018 13:49:50 GMT

Thanks. Have done this. 100 times. Same. There are some lack of resources for the proxy. That's some how related.

Regards,

Robert

Re: Unable to log into vCenter 6.7 VMware Appliance Management page

Robert121281 — Sun, 30 Sep 2018 13:42:18 GMT

Thanks. I have done this. Password is brand new, it is not expired. It is not a credentials issue. It is a lighttpd/proxy issue.

# chage -l root

Last password change : Sep 30, 2018

Password expires : Sep 30, 2019

Password inactive : never

Account expires : never

Minimum number of days between password change : 0

Maximum number of days between password change : 365

Number of days of warning before password expires : 7

I found another strange thing. In the root directory, there is a file:

# ls -l

total 1141

-rw------- 1 root root 1096973 Sep 30 15:38 abyss.log <- what is this file? Why is this in the root directory anyway?

lrwxrwxrwx 1 root root 7 Mar 7 2018 bin -> usr/bin

drwxr-xr-x 4 root root 1024 Mar 7 2018 boot

drwxr-xr-x 27 root root 4340 Sep 30 11:57 dev

drwxr-xr-x 85 root root 4096 Sep 30 12:02 etc

...

tail -f abyss.log

127.0.0.1:47301 - no_user - [30/Sep/2018:15:39:05 -0200] "POST" 200 2066

127.0.0.1:47301 - no_user - [30/Sep/2018:15:39:06 -0200] "POST" 200 2066

127.0.0.1:47301 - no_user - [30/Sep/2018:15:39:07 -0200] "POST" 200 2066

127.0.0.1:47301 - no_user - [30/Sep/2018:15:39:08 -0200] "POST" 200 2066

127.0.0.1:47301 - no_user - [30/Sep/2018:15:39:09 -0200] "POST" 200 2066

127.0.0.1:47301 - no_user - [30/Sep/2018:15:39:10 -0200] "POST" 200 2066

127.0.0.1:47301 - no_user - [30/Sep/2018:15:39:11 -0200] "POST" 200 2066

127.0.0.1:47301 - no_user - [30/Sep/2018:15:39:12 -0200] "POST" 200 2066

127.0.0.1:47301 - no_user - [30/Sep/2018:15:39:13 -0200] "POST" 200 423

127.0.0.1:47301 - no_user - [30/Sep/2018:15:39:13 -0200] "POST" 200 4915

127.0.0.1:47301 - no_user - [30/Sep/2018:15:39:13 -0200] "POST" 200 2066

127.0.0.1:47301 - no_user - [30/Sep/2018:15:39:14 -0200] "POST" 200 2066

127.0.0.1:47301 - no_user - [30/Sep/2018:15:39:15 -0200] "POST" 200 2066

lsof abyss.log

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

ld-linux. 1764 root 16w REG 8,3 1107846 16168 abyss.log

One log line every second. I tried to find what this file is used for but found no proper information.

Thanks,

Robert

Re: Unable to log into vCenter 6.7 VMware Appliance Management page

Robert121281 — Sun, 30 Sep 2018 13:34:01 GMT

Thanks for your answer. No, I updated from 6.5. I am running ESXi 6.7 and VCA 6.7 (both with latest patches). The login was working in the past. I never had issues with this, not in 6.5 and not in 6.7. Yesterday, I tried to login and I have seen this error. I have no reason what action could have triggered this new behavior.

It is for sure related to this "no proxy-handler" error message.

When I browse to the URL, I get this:

2018-09-30 15:31:44: (/build/mts/release/bora-7927448/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.1041) establishing connection failed: Connection refused

2018-09-30 15:31:44: (/build/mts/release/bora-7927448/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.1153) proxy-server disabled: 127.0.0.1 8201 10

2018-09-30 15:31:44: (/build/mts/release/bora-7927448/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.523) no proxy-handler found for: /rest/appliance/system/version

2018-09-30 15:31:49: (/build/mts/release/bora-7927448/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.1417) proxy - re-enabled: 127.0.0.1 8201

When I enter the root credentials and click login the following logs come up - basically the same as before:

2018-09-30 15:32:50: (/build/mts/release/bora-7927448/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.1041) establishing connection failed: Connection refused

2018-09-30 15:32:50: (/build/mts/release/bora-7927448/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.1153) proxy-server disabled: 127.0.0.1 8201 9

2018-09-30 15:32:50: (/build/mts/release/bora-7927448/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.523) no proxy-handler found for: /rest/com/vmware/cis/session

2018-09-30 15:32:55: (/build/mts/release/bora-7927448/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.1417) proxy - re-enabled: 127.0.0.1 8201

Regards,

Robert

Re: Unable to log into vCenter 6.7 VMware Appliance Management page

Robert121281 — Sun, 30 Sep 2018 12:34:36 GMT

I have done some further investigation:

tail -f /opt/vmware/var/log/lighttpd/error.log

When I access the URL https://x.x.x.x:5480, the following logs show up:

2018-09-30 14:31:46: (/build/mts/release/bora-7927448/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.1417) proxy - re-enabled: 127.0.0.1 8201

2018-09-30 14:31:48: (/build/mts/release/bora-7927448/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.1041) establishing connection failed: Connection refused

2018-09-30 14:31:48: (/build/mts/release/bora-7927448/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.1153) proxy-server disabled: 127.0.0.1 8201 13

2018-09-30 14:31:48: (/build/mts/release/bora-7927448/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.523) no proxy-handler found for: /rest/appliance/system/version

2018-09-30 14:31:53: (/build/mts/release/bora-7927448/studio/src/vami/apps/lighttpd/1.4.45/src/mod_proxy.c.1417) proxy - re-enabled: 127.0.0.1 8201

I have checked the error.log file, those errors do only show up recently because in the past, I never had issues to log into the webinterface. The "! unable to login" error comes regardless if I use the correct or wrong credentials.

Any idea how to fix this please?

Thanks,

Robert