-
- Influencer
- Posts: 17
- Liked: 1 time
- Joined: Sep 21, 2022 2:38 pm
- Contact:
Problem after install update veeam 11a and vcenter 7.0.3k
Tiket: 02853768
We have very strange situation.
At the end of March, we put the last patch on 11 and in parallel updated vcenter 7 (before that it was 6.5). Everything worked correctly for two days, and then we started to catch errors. An error occurred on random jobs. Backup jobs were created a long time ago, before that everything worked fine.
Error:
EOF was observed that violates the SSL/TLS protocol. The client probably provided invalid authentication information.Detail: 'Detail: 'SSL/TLS handshake failed', endpoint: 'https://vcenter.xxx.local:443/sdk'
The paradox is that about 10 backup jobs are performed per day. At least one task falls into this error. But the automatic retry 1 is always success!!!. Different jobs. The connection is made through the center.
Very similar to some kind of bug or incompatibility.
There are no firewalls or a/v. The problem started after the updates
We have very strange situation.
At the end of March, we put the last patch on 11 and in parallel updated vcenter 7 (before that it was 6.5). Everything worked correctly for two days, and then we started to catch errors. An error occurred on random jobs. Backup jobs were created a long time ago, before that everything worked fine.
Error:
EOF was observed that violates the SSL/TLS protocol. The client probably provided invalid authentication information.Detail: 'Detail: 'SSL/TLS handshake failed', endpoint: 'https://vcenter.xxx.local:443/sdk'
The paradox is that about 10 backup jobs are performed per day. At least one task falls into this error. But the automatic retry 1 is always success!!!. Different jobs. The connection is made through the center.
Very similar to some kind of bug or incompatibility.
There are no firewalls or a/v. The problem started after the updates
-
- Service Provider
- Posts: 449
- Liked: 112 times
- Joined: Apr 03, 2019 6:53 am
- Full Name: Karsten Meja
- Contact:
Re: Problem after install update veeam 11a and vcenter 7.0.3k
did the certificate change? did you try to get through the vcenter wizard again? does it finish without errors?
maybe it is a DNS issue?
maybe it is a DNS issue?
-
- Influencer
- Posts: 17
- Liked: 1 time
- Joined: Sep 21, 2022 2:38 pm
- Contact:
Re: Problem after install update veeam 11a and vcenter 7.0.3k
Yes, certificate changed.
did you try to get through the vcenter wizard again?
yes, everything is ok.
No, I gont have a problem with DNS (from .txt files logs I see record - resolve and Ip address.
I went through a lot of veeam KB...Evething look good.
I found this post:
veeam-backup-replication-f2/ssl-tls-err ... 34686.html
In this post also task finished success in retry 1.
So maybe problem with this. In 7.0.3 only lest tsl 1.2
did you try to get through the vcenter wizard again?
yes, everything is ok.
No, I gont have a problem with DNS (from .txt files logs I see record - resolve and Ip address.
I went through a lot of veeam KB...Evething look good.
I found this post:
veeam-backup-replication-f2/ssl-tls-err ... 34686.html
In this post also task finished success in retry 1.
So maybe problem with this. In 7.0.3 only lest tsl 1.2
-
- Service Provider
- Posts: 449
- Liked: 112 times
- Joined: Apr 03, 2019 6:53 am
- Full Name: Karsten Meja
- Contact:
Re: Problem after install update veeam 11a and vcenter 7.0.3k
what is the Veeam support engineer saying?
-
- Influencer
- Posts: 17
- Liked: 1 time
- Joined: Sep 21, 2022 2:38 pm
- Contact:
Re: Problem after install update veeam 11a and vcenter 7.0.3k
Long correspondence, almost a week already. It is not yet clear what the problem is.
We tested the execution of backup jobs directly on esxi without vcenter. Everything works ok. The problem is only when backups are made via vcenter...
We tested the execution of backup jobs directly on esxi without vcenter. Everything works ok. The problem is only when backups are made via vcenter...
-
- Influencer
- Posts: 12
- Liked: 3 times
- Joined: May 25, 2022 2:27 pm
- Contact:
Re: Problem after install update veeam 11a and vcenter 7.0.3k
-
- Influencer
- Posts: 17
- Liked: 1 time
- Joined: Sep 21, 2022 2:38 pm
- Contact:
Re: Problem after install update veeam 11a and vcenter 7.0.3k
Thanks but not my case.
-
- Influencer
- Posts: 17
- Liked: 1 time
- Joined: Sep 21, 2022 2:38 pm
- Contact:
Re: Problem after install update veeam 11a and vcenter 7.0.3k
I reinstalled veeam 12 on new fresh windows 2022. The same problem...
-
- Novice
- Posts: 5
- Liked: 1 time
- Joined: Aug 14, 2018 1:37 pm
- Full Name: Alpha_One
- Contact:
Re: Problem after install update veeam 11a and vcenter 7.0.3k
I'm facing the same problem here (case 02627044), and I was told by the support to upgrade to the latest v12 patch P20230412.
So even with a clean install on a fresh windows 2022 patched with no specifics SSL/TLS settings, it's not working ?
So even with a clean install on a fresh windows 2022 patched with no specifics SSL/TLS settings, it's not working ?
-
- Influencer
- Posts: 17
- Liked: 1 time
- Joined: Sep 21, 2022 2:38 pm
- Contact:
Re: Problem after install update veeam 11a and vcenter 7.0.3k
It is work only with fresh install vcenter.
So it is look like problem with vcenter not in veeam...
So we try to find problem in vcenter...
So it is look like problem with vcenter not in veeam...
So we try to find problem in vcenter...
-
- Novice
- Posts: 5
- Liked: 1 time
- Joined: Aug 14, 2018 1:37 pm
- Full Name: Alpha_One
- Contact:
Re: Problem after install update veeam 11a and vcenter 7.0.3k
With the help of VMware we found the issue for my case: too many simultaneous https sessions. I can see it on vcenter log /storage/log/vmware/envoy/envoy.log : remote https connections exceed max allowed: 2048 (we have many third-party apps querying vcenter)
The solution is to modify the value in etc/vmware-rhttpproxy/config.xml to change it to 3072. IMPORTANT: always take a cold snapshot of vCenter before doing any changes in the file.
This is field in question: , <maxRemoteHttpsConnections>3072</maxRemoteHttpsConnections>
I strongly suggest you reach out to VMware support and work with them: They knew about this issue and the answer was very quick and spot on. You can reference my case 23429278305
The solution is to modify the value in etc/vmware-rhttpproxy/config.xml to change it to 3072. IMPORTANT: always take a cold snapshot of vCenter before doing any changes in the file.
This is field in question: , <maxRemoteHttpsConnections>3072</maxRemoteHttpsConnections>
I strongly suggest you reach out to VMware support and work with them: They knew about this issue and the answer was very quick and spot on. You can reference my case 23429278305
Who is online
Users browsing this forum: No registered users and 175 guests