Ertcexecuteerror error connection problems no response received - Исправление ошибок и поиск оптимальных решений проблем

Содержание

Eexecuteerror ошибка при соединении с 9099
Несколько вариантов поиска ошибок и решений:
Ubuntu 18.04 VPN Connection fails #32421
Comments
Document Details
0.14.0.dev4 windows — no no response received in 2 seconds. #936
Comments

Eexecuteerror ошибка при соединении с 9099

Бывает, однажды, ни с того и с чего программа 1С нам выдает: Ошибка соединения с сервером 1С:Предприятие Не запущен ни один рабочий процесс. Соединение с базой невозможно.

Несколько вариантов поиска ошибок и решений:

1. Глюк сервака — всякое бывает

Остановите в диспетчере задач процессы: ragent rphost rmngr и Запустите службу «Агент сервера 1С:Предприятие»

2. При внезапном отключения питания или аналогичных ситуациях — повредился файл srvribrg.lst

Нужно удалить все из папки srvinfo

Для Windows зайдите в каталог c:program files1c1cv82 srvinfo, если Linux — то файлы лежат в домашнем каталоге пользователя от имени которого запускается сервис: usr1cv8/home/.1cv8/1C/1cv8 .

Запустите службу «Агент сервера 1С:Предприятие».

Через Администрирование серверов 1С Предприятия по новой создать кластер 1С и добавить информационные базы

3. Переименовали сервер на котором служба агента 1С

После переименования сервера Windows Server 2008 с установленным 1С:Предприятие 8.2, перестала работать служба «Агент сервера 1С:Предприятие 8.2». Она запускается, работает несколько секунд и останавливается. Если подключаться к серверу 1С:Предприятие 8.2 через консоль серверов, то возникает ошибка:

Ошибка соединения с сервером 1С:Предприятие 8.2 server_addr=tcp://SERVER:1540 descr=Ошибка сетевого доступа к серверу (Windows Sockets — 10061(0x0000274D). Подключение не установлено, т.к. конечный компьютер отверг запрос на соединение.) line=590 file=.SrcDataExchangeTcpClientItmpl.cpp

При подключении к базе на этом сервере имеем следующую ошибку:

Не запущен ни один рабочий процесс. Соединение с базой невозможно.

Данная проблема связана с тем, что настройки кластера серверов 1С:Предприятие хранятся в файлах в каталоге srvinfo (путь к нему указывает параметр -d в свойствах службы «Агент сервера 1С:Предприятие»). Поэтому после изменения имени компьютера надо выполнить дополнительно следующие действия:

Для Windows зайдите в каталог c:program files1c1cv82srvinfo, если Linux — то файлы лежат в домашнем каталоге пользователя от имени которого запускается сервис: usr1cv8/home/.1cv8/1C/1cv8 .

Отредактируйте в любом текстовом редакторе два файла: srvinfosrvribrg.lst и srvinfo
eg_15411CV8Reg.lst. Замените в этих файлах старое имя сервера на новое.

Запустите службу «Агент сервера 1С:Предприятие».

После выполнения указанных действий — Все будет

В момент запуска «1С: Предприятия» выводится окно с текстом «Ошибка связи: Невозможно соединиться с сервером ХХХХ – Ошибка # 10061-Connection refused»:

Необходимо убедиться, что правильно указан путь к серверу СЛК (правильно указано имя компьютера с установленным сервером СЛК или его IP-адрес).

Если расположение сервера указано корректно, то необходимо убедиться, что:

1. Есть возможность установить связь с сервером по протоколу TCP/IP (например, через системную команду ping);

2. Работа сервера СЛК (программа «C:Program Files (x64)1CLicence 2.0BinLicenceServer.exe») на компьютере, выполняющем роль сервера, не блокируется программным обеспечением компьютера: Брандмауэром Windows или антивирусом.

В случае, если работа сервера СЛК блокируется, необходимо добавить сервер СЛК или используемый для соединения с сервером СЛК порт в список исключений защищающего программного обеспечения.

Обычно данная ошибка выходит после обновления. Для того, чтобы исправить данную ошибку нужно установить СЛК.

Рис.1. Ошибка соединения СЛК

Установочный файл хранится в папке с релизом, для этого заходим на портал 1С (https://portal.1c.ru/) под своим аккаунтом. Выбираем пункт обновление программ.

Рис.2. Скачивание обновлений

Далее переходим по ссылке «Скачать обновления программ»

Рис.3. Скачивание дистрибутива

После в открывшемся списке выбираем нашу программу.

Далее в открывшемся окне нужно скачивать и устанавливать сверху вниз каждый релиз.

Рис.5. Список релизов

Пока в папке куда установится релиз не появится папка «Protection».

Рис.6. Папка с установленным релизом

В этой папке как раз и хранится установочный файл СЛК. Запускаем его и устанавливаем после чего ошибка СЛК пропадет.

Источник

Ubuntu 18.04 VPN Connection fails #32421

I’ve been attempting to setup a connection using the Linux guides here and I get the following on

I’ve tried it out with both the strongswan GUI and CLI guides.

I’ve attempted to disable additional plugins as recommended here: https://serverfault.com/questions/840920/how-connect-a-linux-box-to-an-azure-point-to-site-gateway but this doesn’t seem to have any effect.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0d5150fc-9936-07cf-dce7-44d0ec114cd0
Version Independent ID: 8b627174-56cd-a81e-a687-34ba66d33550
Content: Create and install P2S VPN client configuration files for Azure certificate authentication: Azure
Content Source: articles/vpn-gateway/point-to-site-vpn-client-configuration-azure-cert.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

The text was updated successfully, but these errors were encountered:

To try and rule out anything odd I’ve recreated a new set of certs following this process and retried but still no joy.

@lawrencegripper , The error description for 13806 is «ERROR_IPSEC_IKE_NO_CERT | IKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a valid certificate in the appropriate Certificate Store.»

Select tunnel type as SSTP in the P2S settings
Reinstalled the VPN client

Let me know if this works for you

This is running on a Ubuntu 18.04 install, should I re-install the strongswan packages? I don’t believe Ubuntu has support for SSTP in the main set of repositories, I am attempting to connect with IKE2 .

My /etc/ipsec.conf file is as follows, certs are placed in the right location (I hope checked this a fair few times but still might have an issue here).

Is that error returned by the server as the certificate presented isn’t valid?

After re-checking certs I do see the two certificates (CA for the VPN server and client certificate) mentioned in the logs.

@lawrencegripper , Can you post your issue in MSDN or StackOverflow ?

This forum is used to enhance the documentation and your query seems to be more specific to your environment.

It’s an interesting line to draw.

At what point is this an problem an issue with the docs? Currently it looks like the setup guide gives incorrect certificate configuration instructions or a least a bit muddled and that’s why I see the issue but I’m not able to 100% validate. If I can reproduce this with a brand new Ubuntu 18.04 machine does this then become a docs issue?

Specifically regarding the docs it’s not clear how the following relates to the setup.

If the certs have been generated using one of the other guides then it looks like these will always fail as the CommonName is set as follows New-SelfSignedCertificate -Type Custom -DnsName P2SChildCert . I think this would mean these certs would never work as the %client line in the linux setup looks like it has to match the CommonName set on the self signed certificate. Can the author of the LinuxCLI guide confirm this?

This flow is fairly common as a Windows based Admin might setup a VPN then issue certificates to a Linux user to connect.

@cherylmc, can you add your comment here?

Sure — which article could use a note saying that if you are installing on a Linux client, you must create the certificate using the Linux steps? (Just making sure I understand what is being asked)

Hi- can you confirm that certificates for Linux clients must be generated using a Linux computer? If so, I will update the documentation to reflect that. @msrini-MSFT

Nope I don’t think that certs need to be generated with a Linux computer but I do think the CommonName used when generating has to be updated on the %client line of the config when using the CLI path to match the CommonName of the certificate.

I haven’t been able to test this further as I went back to using the GUI based setup and managed to get this working.

I seem to have the same issue:

Nope I didn’t have any luck getting the non-gui instructions working, sorry 🙁

@anzaman , Can you take a look at this issue?

I have found the problem. I noticed the following error:

This happened because I was missing a package. I figured it out after checking this post. In order to have EAP_IDENTITY support, I had to run

sudo apt install -y libcharon-extra-plugins

After that, everything worked.

Finally I did it, thanks @lawrencegripper without this comment:
«Nope I don’t think that certs need to be generated with a Linux computer but I do think the CommonName used when generating has to be updated on the %client line of the config when using the CLI path to match the CommonName of the certificate. I haven’t been able to test this further as I went back to using the GUI based setup and managed to get this working.»
I’ll explain what I did:
1- I had this problem:
no TLS peer certificate found for ‘client’, skipping client authentication
2- After reinstall, build strongswan always I had the same error.
3- I noticed that the value of leftid=%client is the value of the CN of P12 certificate to check this I need to
openssl pkcs12 -in MY_PERSONAL_P12.p12 -nodes -passin pass:»SOME_DARK_PASSWORD» | openssl x509 -noout -subject
with that value I changed %cliente to %MY_DARK_CN
it’s important this P12 is the same certificate that i configured in ipsec.secrets
: P12 MY_PERSONAL_P12.p12 ‘SOME_DARK_PASSWORD’
and azure console Point-to-site configuration in your Virtual network gateway
4- after this I restarted the service «ipsec restart» and tried to connect «ipsec up azure» and all fine

I have found the problem. I noticed the following error:

This happened because I was missing a package. I figured it out after checking this post. In order to have EAP_IDENTITY support, I had to run

sudo apt install -y libcharon-extra-plugins

After that, everything worked.

I was need to install some other libs. My final list is:

@krpovmu so much thanks about that command, i got to realize that no name (in my case a generic ‘client’) was given in the process due to a bad variable name in the script!

Источник

0.14.0.dev4 windows — no no response received in 2 seconds. #936

Getting a fatal error on 0.14.0.dev4 on windows:

The text was updated successfully, but these errors were encountered:

the same also here with this version ethminer 0.14.0rc4, until now it becomes a misery with mining ethminer 0.14.0rc4, miner stops and goes no further, please watchdog please just like Phoenixminer or Claymore there are enough examples but ethminer developers are sleeping .

Same. Win10, GTX 1070. Won’t post logs as it was default verbosity and look basically the same, so probably not helpful. I turn on a lot of security stuff like DEP and Manditory ASLR and such, if that matters.

Please redo your tests with ethminer 0.14.0rc6

but ethminer developers are sleeping .

Please keep always in mind that we’re giving our spare time for free. No one gets paid for this nor you pay a single dime for using ethminer.

@digitalpara THANK YOU FOR ALL THE WORK AND YOUR FREE TIME.

@Topic: 0.14.0rc6 also not working for me. Same error on PIMP 2.5

0.14.rc7
0.15.dev6

Confirm 0.15.dev6 resolves my issue

Windows then reports that ethminer.exe stopped working. I would be happy if the miner continued to run rather than die, just so that I don’t have to write a process supervisor

Its not fixed for me on Linux with 0.15.dev6

Please try latest. We’ve pushed some little changes few minutes ago.
And report back.

kk, give it a try.

Same Error after about 10 Minutes.

Is there a log I could provide to help you find the responsible code? If it’s relevant, im using SSL right now. Should I test without?

Well . actually this is not really a bug.
You’re suffering from a huge delay in ethermine.org’s responses to your submissions. Do not know about your connection and wether it’s stable or not (do you have dynamic ip ?).

Aside from this the behavior of ethminer is correct even if I agree with you 1 minute to reconnect is not acceptable.
Those «not-connected» warnings come from a process which is locking.

Will report back.

I use a Cable-Connection with 400mbit down/20 mbit up. Normally my submissions take

20ms. It is dynamic IP but the IP changes every 6 — 8 Weeks.

OK, thank you. I try to provide fast feedback if you have a new release.

@faithless1108
can you describe your environment ?
CPU and flavour (x86/x64) ?
OS and flavour

sure. All it takes to solve this.

CPU: CPU Intel Celeron G3900 2x 2.80GHz (64Bit)
MoBo: ASRock BTC Pro H110
RAM: 4GB (Cheapest I could find, dont know the Vendor)

OS: PIMP 2.5 (https://getpimp.org/, I think its a modified Ubuntu 16.04.4 LTS)

Connected via LAN-Cable to Router. Internetconnection is a verry stable Calbe-Broadband-Connection with 400Mbit down- / 20 Mbit upstream.

You need something else?

Thanks for your greate support Mate!!

I found the Invoce. Its Crucial RAM

OS:
NAME=»Ubuntu»
VERSION=»16.04.4 LTS (Xenial Xerus)»
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=»Ubuntu 16.04.4 LTS»
VERSION_ID=»16.04″
HOME_URL=»http://www.ubuntu.com/»
SUPPORT_URL=»http://help.ubuntu.com/»
BUG_REPORT_URL=»http://bugs.launchpad.net/ubuntu/»
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Do you have other rigs ? If so .. it happens only on one of them or it’s random ?

From the log I see, apparently, your machine takes 20 seconds to run a very simple disconnection of the socket (code follows) which, coupled with your exhuberant network configuration, leads me to think you might have a network card error.

This code takes 20 seconds to run on your machine

It’s the only Rig I have.

But with Claymore-Miner there is absolutely no problem. SSH and all the Stuff works and is stable (Miner-Test for Hours). I really dont think it’s the Card.

shutdown : this should ensure that any pending operations on the socket are properly cancelled and any buffers are flushed prior to the call to socket.close.

but . you’re shutting down because you previously had a 2 seconds response timeout on the socket thus, somehow, your network card (or it’s driver) was already non responding.

I’ve seen similar problems with same MOBO as yours at high overclocking values (network card becomes unresponsive and takes time to «restore»).

Would ask you to :

ensure MOBO BIOS is up to date
try a batch test with NO overclocking
check with dmesg if there are relevant messages about network card.

But with Claymore-Miner there is absolutely no problem. SSH and all the Stuff works and is stable (Miner-Test for Hours). I really dont think it’s the Card.

We do not know how Claymore implements socket management as it’s code is closed.
Maybe they don’t care about a clean shutdown (and drop the socket abruptly) or don’t care about the 2 seconds timeout on response.

OK here is DMESG Output. I will turn down OC and retest.

[51125.588443] stratum[3210]: segfault at 0 ip 0000000000530005 sp 00007f5324ccf780 error 4 in ethminer[400000+8f6000]
[51323.829224] stratum[8965]: segfault at 28 ip 0000000000533c25 sp 00007f950afb8600 error 4 in ethminer[400000+8f6000]
[52728.318270] stratum[14976]: segfault at 28 ip 0000000000548c25 sp 00007f31f1e5b5a0 error 4 in ethminer[400000+912000]
[53576.010483] stratum[23236]: segfault at 0 ip 0000000000545005 sp 00007fcafdf36720 error 4 in ethminer[400000+912000]
[55937.909989] stratum[3066]: segfault at 0 ip 0000000000545005 sp 00007f060fc60720 error 4 in ethminer[400000+912000]
[56065.028380] stratum[25578]: segfault at 0 ip 0000000000545005 sp 00007fa63744b720 error 4 in ethminer[400000+912000]
[58443.937327] stratum[28350]: segfault at 0 ip 0000000000545005 sp 00007f0c0b7fc720 error 4 in ethminer[400000+912000]
[58927.095611] stratum[24083]: segfault at 0 ip 0000000000545005 sp 00007fe60a899720 error 4 in ethminer[400000+912000]
[59003.544400] stratum[31441]: segfault at 0 ip 0000000000545005 sp 00007f722fffd720 error 4 in ethminer[400000+912000]
[59281.624316] stratum[6378]: segfault at 0 ip 0000000000545005 sp 00007f4fd900f720 error 4 in ethminer[400000+912000]
[59405.937630] stratum[9416]: segfault at 0 ip 0000000000545005 sp 00007fd32cc11720 error 4 in ethminer[400000+912000]
[59733.962419] stratum[14835]: segfault at 0 ip 0000000000545005 sp 00007fb1c587b720 error 4 in ethminer[400000+912000]
[59935.803082] stratum[19768]: segfault at 0 ip 0000000000545005 sp 00007fb57ccda720 error 4 in ethminer[400000+912000]
[62757.081930] stratum[31374]: segfault at 0 ip 0000000000545005 sp 00007fb96a83a720 error 4 in ethminer[400000+912000]
[63901.208425] stratum[16150]: segfault at 0 ip 0000000000530005 sp 00007fc62e7fa780 error 4 in ethminer[400000+8f6000]
[63962.155699] stratum[19783]: segfault at 0 ip 0000000000530005 sp 00007f5dd0de5780 error 4 in ethminer[400000+8f6000]
[64774.659709] stratum[3905]: segfault at 0 ip 0000000000545005 sp 00007f9c937fc720 error 4 in ethminer[400000+912000]
[99601.601113] stratum[30824]: segfault at 0 ip 0000000000545005 sp 00007f4ff17f8720 error 4 in ethminer[400000+912000]
[117424.506637] NVRM: GPU at PCI:0000:01:00: GPU-81cd05f7-c980-2da1-548d-3fd0bd11b467
[117424.506639] NVRM: GPU Board Serial Number:
[117424.506641] NVRM: Xid (PCI:0000:01:00): 31, Ch 00000013, engmask 00000101, intr 10000000
[201856.641368] NVRM: GPU at PCI:0000:0f:00: GPU-f20881bf-564b-e590-2d5a-550fd51f88ff
[201856.641371] NVRM: GPU Board Serial Number:
[201856.641373] NVRM: Xid (PCI:0000:0f:00): 31, Ch 00000013, engmask 00000101, intr 10000000
[216913.765332] NVRM: GPU at PCI:0000:0e:00: GPU-82beea07-282d-b430-1627-1a56cbb1b797
[216913.765334] NVRM: GPU Board Serial Number:
[216913.765336] NVRM: Xid (PCI:0000:0e:00): 31, Ch 00000013, engmask 00000101, intr 10000000
[235491.030270] NVRM: Xid (PCI:0000:0e:00): 31, Ch 00000013, engmask 00000101, intr 10000000
[245616.267109] perf: interrupt took too long (3967 > 3946), lowering kernel.perf_event_max_sample_rate to 50250
[268258.303253] stratum[8787]: segfault at 221d150 ip 000000000221d150 sp 00007f6c18f61b38 error 15
[269535.986400] stratum[27157]: segfault at 2ee5f60 ip 0000000002ee5f60 sp 00007f938cc47b38 error 15
[271120.134178] stratum[31027]: segfault at 2cb8ed0 ip 0000000002cb8ed0 sp 00007fe776374b78 error 15
[274452.629114] stratum[25487]: segfault at 240ced0 ip 000000000240ced0 sp 00007f88aedccb78 error 15
[277440.151200] stratum[28755]: segfault at 203ded0 ip 000000000203ded0 sp 00007fc1024f1b78 error 15
[278934.978085] stratum[32430]: segfault at 17d9ed0 ip 00000000017d9ed0 sp 00007efcb4e56b78 error 15
[279355.290977] stratum[11134]: segfault at 1b56ed0 ip 0000000001b56ed0 sp 00007f072a4bab78 error 15
[279911.053137] stratum[14558]: segfault at 17b8ed0 ip 00000000017b8ed0 sp 00007f81210e3b78 error 15

Segfault error 4 means thread name «stratum» could not read and the only thing it reads is socket data over the network card (look ip — instruction pointer is always the same 0000000000545005 — we have only one instruction where we invoke read). This causes your 2 seconds reponse time-out

Segfault error 15 means stratum could not write to socket.

Think it’s machine related . not code related.

Think it’s machine related . not code related.

Источник

Несколько вариантов поиска ошибок и решений:

1. Глюк сервака — всякое бывает

Остановите в диспетчере задач процессы: ragent rphost rmngr и Запустите службу «Агент сервера 1С:Предприятие»

2. При внезапном отключения питания или аналогичных ситуациях — повредился файл srvribrg.lst

Нужно удалить все из папки srvinfo

Запустите службу «Агент сервера 1С:Предприятие».

Через Администрирование серверов 1С Предприятия по новой создать кластер 1С и добавить информационные базы

3. Переименовали сервер на котором служба агента 1С

При подключении к базе на этом сервере имеем следующую ошибку:

Не запущен ни один рабочий процесс. Соединение с базой невозможно.

Запустите службу «Агент сервера 1С:Предприятие».

После выполнения указанных действий — Все будет

Если расположение сервера указано корректно, то необходимо убедиться, что:

1. Есть возможность установить связь с сервером по протоколу TCP/IP (например, через системную команду ping);

Обычно данная ошибка выходит после обновления. Для того, чтобы исправить данную ошибку нужно установить СЛК.

Рис.1. Ошибка соединения СЛК

Рис.2. Скачивание обновлений

Далее переходим по ссылке «Скачать обновления программ»

Рис.3. Скачивание дистрибутива

После в открывшемся списке выбираем нашу программу.

Далее в открывшемся окне нужно скачивать и устанавливать сверху вниз каждый релиз.

Рис.5. Список релизов

Пока в папке куда установится релиз не появится папка «Protection».

Рис.6. Папка с установленным релизом

Источник

Eexecuteerror ошибка при соединении с 9099

Несколько вариантов поиска ошибок и решений:

1. Глюк сервака — всякое бывает

Остановите в диспетчере задач процессы: ragent rphost rmngr и Запустите службу «Агент сервера 1С:Предприятие»

2. При внезапном отключения питания или аналогичных ситуациях — повредился файл srvribrg.lst

Нужно удалить все из папки srvinfo

Запустите службу «Агент сервера 1С:Предприятие».

Через Администрирование серверов 1С Предприятия по новой создать кластер 1С и добавить информационные базы

3. Переименовали сервер на котором служба агента 1С

При подключении к базе на этом сервере имеем следующую ошибку:

Не запущен ни один рабочий процесс. Соединение с базой невозможно.

Запустите службу «Агент сервера 1С:Предприятие».

После выполнения указанных действий — Все будет

Если расположение сервера указано корректно, то необходимо убедиться, что:

1. Есть возможность установить связь с сервером по протоколу TCP/IP (например, через системную команду ping);

Обычно данная ошибка выходит после обновления. Для того, чтобы исправить данную ошибку нужно установить СЛК.

Рис.1. Ошибка соединения СЛК

Рис.2. Скачивание обновлений

Далее переходим по ссылке «Скачать обновления программ»

Рис.3. Скачивание дистрибутива

После в открывшемся списке выбираем нашу программу.

Далее в открывшемся окне нужно скачивать и устанавливать сверху вниз каждый релиз.

Рис.5. Список релизов

Пока в папке куда установится релиз не появится папка «Protection».

Рис.6. Папка с установленным релизом

Источник

Overcoming HTTPS Socket Errors in JMeter

When executing performance and/or load testing against an SSL-enabled application using Apache JMeter, SSL socket errors can be a frequently encountered nuisance which can severely hinder your testing efforts. This article highlights how to overcome these connection-related errors by configuring and tuning JMeter accordingly.

Examples of error messages that indicate SSL socket issues in Jmeter include the following:

Non HTTP response code: java.net.SocketException Non HTTP response message: Connection reset
Non HTTP response code: java.net.SocketTimeoutException Non HTTP response message: connect timed out
Non HTTP response code: java.net.SocketTimeoutException Non HTTP response message: Read timed out

Recommendation #1: Use latest version of JMeter

It is highly recommended to use the most recent version, to leverage new improvements and components.

Avoid using versions that are older than 3 versions before the last one.

Recommendation #2: Enable DEBUG mode in JMeter

Add the following like to jmeter.properties to enable the JMeter Logger Panel:

To increase the log level to DEBUG via the JMeter menu:

Options -> Log Level -> DEBUG

To enable debug mode for context and wire logging via log4j2.xml:

Recommendation #3: Set Connection timeout

The default connection timeout in JMeter is 20 seconds out-of-the-box. To help diagnose and resolve socket connection issues, it is often helpful to increase this value. To do so, specify a higher connection timeout the HTTP Request object in your JMeter test plan. For example, set to 60000 (milliseconds) to increase the overall timeout to 60 seconds.

Add a ‘HTTP Request Default’ configuration element from the ‘Configuration Elements’ option (i.e., Right-click test plan and add this ‘HTTP Request Default’).

In this ‘HTTP Request Default’, there is an option – Connect in ‘Timeouts (milliseconds)’ Specify your connection timeout value in this field and it will be applied to all child samplers. If this ‘HTTP Request Default’ is added at Test Plan level, then it will be applied to all samplers and all thread groups.

In order to specify individual Connection Timeout, then specify in same field of each sampler. Individual sampler Connection timeout will override the ‘HTTP Request Default’ connection timeout value.

Recommendation #4: Delay Thread Creation

JMeter has an option to delay thread creation until the thread starts sampling (i.e., after any thread group delay and the ramp-up time for the thread itself). This allows for a very large total number of threads, provided that not too many are active concurrently.

Recommendation #5: Disable Parallel Downloads

JMeter uses more resources to simulate the browser parallel fetching of embedded resources like css, gif, js and static content. If there are many users, too many threads may get created and start affecting the response times adversely due to bandwidth contention at the JMeter side. If many users are to be simulated, it’s recommended to disable parallel downloads as JMeter does not simulate browser’s cache and browsers don’t re-download embedded resources on subsequent requests.

Recommendation #6: Configure trusted and client SSL certs

If you have internally-signed or self-signed certificates on your application server tier, JMeter will need to be configured to recognize those certificates as valid. To remedy this, modify system.properties and configure the truststore with the relevant signer certs.

# Truststore properties (trusted certificates)
javax.net.ssl.trustStore=C:/trust.jks
javax.net.ssl.trustStorePassword=sample

If your application requires SSL client certificate authentication or authorization, you will need to create a keystore and set the following properties in the system.properties file pointing to that keystore:

# Keystore properties (client certificates)
javax.net.ssl.keyStore=C:/key.jks
javax.net.ssl.keyStorePassword=sample

Recommendation #7: Tweak JMeter SSL configuration

Set the properties below in the jmeter.properties to adjust the way that JMeter handles SSL sessions, protocols and ciphers:

To enable SSL session sharing:

To set Default HTTPS protocol level:

To enable multiple HTTPS protocols:

To enable multiple ciphers:

To retain SSL context for the duration of test:

To set retry count on http 4

Recommendation #8: Enable stale connection check

To avoid issues with HTTP connection pooling, it may be necessary to enable a stale connection check in JMeter. This step should be used when receiving “Socket Closed” exceptions during JMeter test runs. To enable the stale connection check, set the following property in user.properties:

Recommendation #9: Enable HTTP Keep-Alive on web servers

Keep-Alive is very important feature of HTTP protocol. It allows the client to make several HTTP requests over single TCP connection. This provides a great performance gain, since otherwise establishing many TCP connections will produce a lot of unnecessary networking overhead.

Recommendation #10: Check the load balancer configuration

If your load test is hitting an application which is fronted by a load balancer, ensure that the load balancer is configured with an adequate max connections limit to handle the anticipated load. Likewise, validate that the load balancing algorithm is not skewing excessive traffic to one or more application server instances, and that load is adequately dispersed amongst application server backends.

6 Comments

Getting the error Response code: No response Response message: Read timeout, no response received.

I am using Jmeter for the load testing of an application which includes web socket connection.

When trying to read the data in a frame using Single Read Sampler,got an error Response code: No response Response message: Read timeout, no response received.

Please find attached the screenshot.

Can anybody help me in solving this issue?

I am still facing the same Connection issue even after implementing the 3rd step.. increased the timeout to 30,40,90 seconds but no luck..still same issue..

Note: Able to access it in Postman successfully but only facing this connectivity timedout issue in jmeter

Thread Name: Thread Group 1-1
Sample Start: 2021-02-08 11:47:58 IST
Load time: 21481
Connect Time: 21481
Latency: 0
Size in bytes: 2233
Sent bytes:0
Headers size in bytes: 0
Body size in bytes: 2233
Sample Count: 1
Error Count: 1
Data type (“text”|”bin”|””): text
Response code: Non HTTP response code: java.net.ConnectException
Response message: Non HTTP response message: Connection timed out: connect

HTTPSampleResult fields:
ContentType:
DataEncoding: null

you are facing a Connection issue in only 1 thread?

Источник

Support Questions

Subscribe to RSS Feed
Mark Question as New
Mark Question as Read
Float this Question for Current User
Bookmark
Subscribe
Mute
Printer Friendly Page

Created on ‎01-25-2019 08:31 AM — edited ‎09-16-2022 07:05 AM

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

I’m able to create a System DSN using the «ODBC Data Source Administrator» with a successfull test.

My Authentication mecanism is «User Name and Passowrd»

SSL Options: «Enable SSL» checked

SSL Options: I’m providing the path to a certificate

BUT, trying to connect using pyodbc with the same parameters (server, port, username and password) gives always the same error below whatever the auth_mechanism provided:

Error: (‘HY000′, u'[HY000] [Cloudera][DriverSupport] (1170) Unexpected response received from server. Please ensure the server host and port specified for the connection are correct. (1170) (SQLDriverConnect); [HY000] [Cloudera][DriverSupport] (1170) Unexpected response received from server. Please ensure the server host and port specified for the connection are correct. (1170)’)

ODBC Version: 03.80
Driver Version: 2.6.0.1000
Bitness: 64-bit
Locale: fr_CA

Источник

UNAVAILABLE: HTTP/2 error code: NO_ERROR Received Goaway #8310

Comments

c-s-t-z commented Jul 8, 2021 •

What version of gRPC-Java are you using?

What is your environment?

Linux xxxxx016 3.10.0-1062.18.1.el7.x86_64 #1 SMP Tue Mar 17 23:49:17 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
java version «1.8.0_91»
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)

What did you expect to see?

What did you see instead?

Steps to reproduce the bug

The java grpc client connects to the go grpc service (service grpc version 1.27.1). The above exception occurs. The service uses container deployment and nginx for load balancing. There is a high probability of this abnormal situation.
Of course, we are also working hard to find a solution, but there is no progress. Hope to get your guidance and help.
I will be very grateful.

The text was updated successfully, but these errors were encountered:

c-s-t-z commented Jul 9, 2021 •

The client language Java uses version 1.30.0, and the server language c++ uses version 1.27.1. The server uses docker container deployment. If there is anything else I need to provide, please feel free to contact me, thank you very much.

ericgribkoff commented Jul 12, 2021

Are you able to connect from the client to the server directly without nginx in the middle? Or are you successful when using a gRPC Go client and only the gRPC Java client has an issue? My guess here is that the connection is being interrupted by nginx or some other middle component as generally gRPC servers themselves will not terminate a connection with NO_ERROR but rather this is what you’d expect from a proxy in the middle.

c-s-t-z commented Jul 12, 2021

你能在中间没有nginx的情况下直接从客户端连接到服务器吗？或者您在使用 gRPC Go 客户端时是否成功并且只有 gRPC Java 客户端有问题？我的猜测是，连接被 nginx 或其他一些中间组件中断，因为通常 gRPC 服务器本身不会终止与之的连接， NO_ERROR 但这正是您对中间代理的期望。

Thank you for your reply, can I think that this NO_ERROR exception has no effect on a connection; can this exception call grpc’s onError method;
Which link may be the problem or how do I need to deal with this exception?

ericgribkoff commented Jul 12, 2021

Do you always see the NO_ERROR exception? That is, the client can never connect to the server? Or can your client connect to the server and exchange messages but then periodically sees the exception message and the connection gets broken?

The error indicates that something the gRPC client is connected to has terminated the connection with a GOAWAY frame saying NO_ERROR. This could come from the gRPC server (if you turn on verbose logging in the server, you may be able to see if this is happening) but I think it is more likely coming from an intermediate layer. If your clients can connect but then see this error after some time, it could be that there is a timeout configured in nginx or elsewhere causing it to terminate the stream (just a guess)

c-s-t-z commented Jul 13, 2021

Do you always see the NO_ERROR exception? That is, the client can never connect to the server? Or can your client connect to the server and exchange messages but then periodically sees the exception message and the connection gets broken?

Thank you for your reply again. When the amount of data is large, this problem will be reported every time a connection is established; and it is more frequent, because I don’t know very much about this, and it is not clear whether it is when creating StreamObserver or in requestObserver.onNext (request) When the onError method was triggered, the NO_ERROR exception was reported; so I want to get more guidance and help from you.

ericgribkoff commented Jul 13, 2021

The NO_ERROR part of the exception message corresponds to the GOAWAY received on the HTTP/2 stream (the spec for this is at https://httpwg.org/specs/rfc7540.html#ErrorCodes). There is in fact an «error» on the stream from the gRPC client’s perspective, because the stream has been broken — the GOAWAY with NO_ERROR just indicates that the server or intermediate proxy sending that is terminating the connection is intentionally breaking the stream or rejecting creation of a new stream. To debug further, we would need to identify where this GOAWAY is being generated and why.

c-s-t-z commented Jul 13, 2021

The NO_ERROR part of the exception message corresponds to the GOAWAY received on the HTTP/2 stream (the spec for this is at https://httpwg.org/specs/rfc7540.html#ErrorCodes). There is in fact an «error» on the stream from the gRPC client’s perspective, because the stream has been broken — the GOAWAY with NO_ERROR just indicates that the server or intermediate proxy sending that is terminating the connection is intentionally breaking the stream or rejecting creation of a new stream. To debug further, we would need to identify where this GOAWAY is being generated and why.

Thank you very much for your prompt response, I understand that you need this information here:
grpc client version 1.30.2, error location at io.grpc.Status.asRuntimeException(Status.java:533);

ericgribkoff commented Jul 13, 2021

Sorry, the information that is needed for you to debug the problem is identifying where in the network the GOAWAY is being generated. This is being received over the network by the client, so the exception message from the client is expected and doesn’t give any further information about where or why the connection was closed. You would need to determine if the gRPC server were sending the GOAWAY, or if it is being created by an intermediate like nginx.

c-s-t-z commented Jul 14, 2021

Sorry, the information that is needed for you to debug the problem is identifying where in the network the GOAWAY is being generated. This is being received over the network by the client, so the exception message from the client is expected and doesn’t give any further information about where or why the connection was closed. You would need to determine if the gRPC server were sending the GOAWAY, or if it is being created by an intermediate like nginx.

Thank you for your reply. I would like to ask, can I set the number of streams in each connect on the client side? When this value is reached, a new connection will be used. We guess that ng intercepted but let’s modify the configuration of this parameter, see Is there any relief?

ejona86 commented Jul 16, 2021 •

If I had to guess, I’d expect nginx is closing connections very frequently, potentially with you trying to do more concurrent RPCs than its MAX_CONCURRENT_STREAMS. There is a client-side race that can be hit here and you’re already on grpc-java 1.30 which reduced the window. 1.34 had improvements to GOAWAY error reporting that now tell us a bit more of what was going on. I suggest upgrading to 1.36.2 or later, which had bug fixes related to GOAWAY error messages. Upgrading should tell us more precisely what is going on.

huangchong94 commented Jul 20, 2021

From my experience nginx will close connection due to the limit of http2_max_requests and http2_max_concurrent_streams in nginx.conf.

Before nginx closes connection, it seems nginx will send only one GOAWAY to client which is not graceful according to grpc/grpc#24237 and this behaviour will cause UNAVAILABLE: HTTP/2 error code: NO_ERROR Received Goaway in client side.

If we use only one thread to send RPC in a loop with enableRetry turn on, despite nginx will close connection due to http2_max_requests , everything works fine, no error occurs.

But when we use multiple threads( parallelStream ) to send concurrent rpcs to nginx, enableRetry will only mitigate this issue can’t fix it

ejona86 commented Jul 20, 2021

Before nginx closes connection, it seems nginx will send only one GOAWAY to client which is not graceful according to grpc/grpc#24237

Then the only options are to fix/improve nginx or require retries on the client-side.

huangchong94 commented Jul 21, 2021 •

Before nginx closes connection, it seems nginx will send only one GOAWAY to client which is not graceful according to grpc/grpc#24237

Then the only options are to fix/improve nginx or require retries on the client-side.

We did client-side retry by enableRetry when building channel, in my understanding enableRetry will turn on transparent retry and it works fine in case 1, single thread sends RPCs to Nginx in a loop.

But in case 2, use parallelStream to send concurrent RPCs to Nginx, transparent retry will only reduce error frequency, we can still see UNAVAILABLE: HTTP/2 error code: NO_ERROR Received Goaway occurs.

It’s not uncommon that people use nginx as reverse proxy for their grpc services and C-core based gRPC such as python doesn’t do a double goaway when they close connection (grpc/grpc#24237)

If client sends concurrent RPCs to Nginx or C-core based gRPC with MAX_CONNECTION_AGE set, they will probably encounter the same problem

So it would be great if gRPC built-in transparent retry can fully handle this situation

ejona86 commented Jul 21, 2021

Case 1 doesn’t need enableRetry at all. There is no race in case 1.

In case 2, it is hard to say what is happening. I still recommend upgrading grpc-java to improve the error message.

If client sends concurrent RPCs to Nginx or C-core based gRPC with MAX_CONNECTION_AGE set, they will probably encounter the same problem

So it would be great if gRPC built-in transparent retry can fully handle this situation

It is much, much simpler to fix the servers than fix the clients. The servers should be fixed independent of transparent retry, as you’ll see increased latency when transparent retry is used. It is so very, very easy for a server to do the right thing here and it benefits all client implementations.

Our main interest in transparent retry is to resolve a client-side race, not for this GOAWAY race.

huangchong94 commented Jul 22, 2021 •

Case 1 doesn’t need enableRetry at all. There is no race in case 1.

In case 2, it is hard to say what is happening. I still recommend upgrading grpc-java to improve the error message.

If client sends concurrent RPCs to Nginx or C-core based gRPC with MAX_CONNECTION_AGE set, they will probably encounter the same problem
So it would be great if gRPC built-in transparent retry can fully handle this situation

Our main interest in transparent retry is to resolve a client-side race, not for this GOAWAY race.

Upgrade grpc-java to 1.37.0, the error message is:

io.grpc.StatusRuntimeException: UNAVAILABLE: Abrupt GOAWAY closed sent stream. HTTP/2 error code: NO_ERROR

With a service config like this

in case 2, using multiple threads(parallelStream) to send concurrent RPCs to nginx, no error occurs

I didn’t expect the service config above would take effect, because Retryable Status Codes section in gRPC Retry Design said

When gRPC receives a non-OK response status from a server, this status is checked against the set of retryable status codes in retryableStatusCodes to determine if a retry attempt should be made.

Nginx didn’t return unavailable status code, it simply sent GOAWAY frame to client and closed connection, so I assumed the retryPolicy in service config would not work in this circumstance.

Surprisingly, it worked, maybe I misunderstood the grpc retry mechanism

Источник

BigShmax

05.03.13 — 14:37

1с сервер на одной машине. ключи и сервер лицензий на другой. На той машине где стоят ключи установлен сервер все красиво ключи видно все расчудесно. на сервере 1с есть файл LicenceAddIn.config с содержимым:

[5E45]

Host=192.168.0.231

Port=9099

ReadTimeout=30

KeepAlivePeriod=60

KeyNo=0

но при запуске настройки системы защиты лезет ошибка :

Невозможно соединиться с сервером localhost:9099 — Socket Error # 10061

Connection refused.

какого 1с ищет сервер лицензий на локалхосте сервера 1с ? как его заставить опрашивать именно Host=192.168.0.231 ?

H A D G E H O G s

1 — 05.03.13 — 14:40

C:ProgramData1CLicence 2.0LicenceAddIn.config

BigShmax

2 — 05.03.13 — 15:19

черт, а я был уверен что в програм филес1с…..

ща попробую

BigShmax

3 — 05.03.13 — 15:30

(1) спасибо, нашелся сервер. Может подскажете, что за файл не находится на этой картинке?

http://s1.ipicture.ru/uploads/20130305/2lhrX3qa.jpg

H A D G E H O G s

4 — 05.03.13 — 15:32

5E45.datafile не найден. Что непонятного то?

ДенисЧ

5 — 05.03.13 — 15:33

(4) Вот он и спрашивает, кто спёр файл? Ты не брал, случайно?

H A D G E H O G s

6 — 05.03.13 — 15:34

(5) найн!

BigShmax

7 — 05.03.13 — 15:34

да нет его в поставке

H A D G E H O G s

8 — 05.03.13 — 15:35

Nahm ich nicht das verdammte Ding, der Teufel mich nehmen!

ДенисЧ

9 — 05.03.13 — 15:35

(6) Ну вот… И я не брал… А кто тогда? Может, его автор потихоньку домой утащил? А с нас теперь требует…

H A D G E H O G s

10 — 05.03.13 — 15:35

(7) Должен быть. Без него не пройдет сертификацию в 1С решение.

BigShmax

11 — 05.03.13 — 15:36

вот такой есть

5E45.uprof.datafile

H A D G E H O G s

12 — 05.03.13 — 15:44

(11) Попробуй его переименовать и захреначить в папку, в которой лежит сервер СЛК

BigShmax

13 — 05.03.13 — 15:46

еще не понимаю что значит вот в этой картинке

http://s1.ipicture.ru/uploads/20130305/VSEU4V1z.jpg

лицензий 6 — понятно

подключений 3 — это как я понимаю компы с которых есть обращения к севреру

использовано лицензий — 0

так подключились они или нет. и почему лицензии не тронуты

(12) пробовал. хотяяяя. у меня этих папок — я уже не знаю откуда сервер то грузится :0-( как я понимаю эта папка на машине где ключи торчат

H A D G E H O G s

14 — 05.03.13 — 15:48

(13) mstsc на IT2, диспетчер задач, ищем LicenceServer.exe смотрим его командную строку запуска, идем в эту папку

BigShmax

15 — 05.03.13 — 16:10

(14) точно так, я дурилко службу не рестартил. пропала надпись

терь бы понять что за соединения при не занятых лицензиях

H A D G E H O G s

16 — 05.03.13 — 16:16

(15) Возможно покривому написана система защиты в решении.

Забить.

BigShmax

17 — 05.03.13 — 16:40

(16) я рад в принципе забить но нужно мониторить занятые и свободные лицензии.

ВНИМАНИЕ! Если вы потеряли окно ввода сообщения, нажмите Ctrl-F5 или Ctrl-R или кнопку «Обновить» в браузере.

Тема не обновлялась длительное время, и была помечена как архивная. Добавление сообщений невозможно.
Но вы можете создать новую ветку и вам обязательно ответят!
Каждый час на Волшебном форуме бывает более 2000 человек.

Источник

09-10-2018, 14:38

#61 (permalink)

khorshed2

Freak Poster

Join Date: Jan 2013

Location: Bhaluka, Mymensingh, Dhaka

Posts: 223

Member: 1868469

Status: Offline

Thanks Meter: 78

Quote:

Originally Posted by owais a

check again now problem solved

thanks a lot umt team
i like most umt
i also selling umt dongle in my country

The Following User Says Thank You to khorshed2 For This Useful Post:

09-30-2018, 14:55

#62 (permalink)

JPS784695

Freak Poster

Join Date: Oct 2016

Posts: 116

Member: 2632043

Status: Offline

Thanks Meter: 244

Post UMT Team

Pls add OPPO A3S,Realme 2 & Pro

The Following 2 Users Say Thank You to JPS784695 For This Useful Post:

10-01-2018, 12:23

#63 (permalink)

laduka

No Life Poster

Join Date: Oct 2005

Location: georgia tbilisi

Posts: 2,095

Member: 194939

Status: Offline

Sonork: 100.168.25.6

Thanks Meter: 623

cannt update umt

when start, update masaage comes and can update

10-01-2018, 12:28

#64 (permalink)

ub mobiles

Freak Poster

Join Date: Aug 2005

Location: Greece

Age: 36

Posts: 391

Member: 173946

Status: Offline

Sonork: 100.1585498

Thanks Meter: 42

Getting Error Connecting to server… [cardupdate]Too many connection, try latter[01]

Getting Error during update card
Connecting to server…
[cardupdate]Too many connection, try latter[01].
any solution Please

10-01-2018, 12:41

#65 (permalink)

black_spider00

Freak Poster

Join Date: Jul 2010

Location: manila

Posts: 140

Member: 1356301

Status: Offline

Sonork: 1013140207746

Thanks Meter: 22

same problem.. pls need help

10-01-2018, 13:27

#66 (permalink)

mouhannadoo

Major Poster

Join Date: Nov 2013

Posts: 44

Member: 2072130

Status: Offline

Thanks Meter: 5

saaaaaaaame problem

saaaaaaaame problem why i cant update card???

10-01-2018, 14:42

#67 (permalink)

ub mobiles

Freak Poster

Join Date: Aug 2005

Location: Greece

Age: 36

Posts: 391

Member: 173946

Status: Offline

Sonork: 100.1585498

Thanks Meter: 42

Still no answer from Server,

10-01-2018, 14:45

#68 (permalink)

Farrukh.Raja

Freak Poster

Join Date: Jan 2013

Location: Rawalpindi & Brussels

Posts: 163

Member: 1874467

Status: Offline

Sonork: 100.1614500

Thanks Meter: 27

same problem here demon in UMT what heppend whats wrong gone???

10-01-2018, 14:45

#69 (permalink)

laduka

No Life Poster

Join Date: Oct 2005

Location: georgia tbilisi

Posts: 2,095

Member: 194939

Status: Offline

Sonork: 100.168.25.6

Thanks Meter: 623

Quote:

Originally Posted by laduka

when start, update masaage comes and can update

now error connect to server.no response

10-01-2018, 14:48

#70 (permalink)

radus81

Junior Member

Join Date: Sep 2009

Location: istanbul

Posts: 28

Member: 1128520

Status: Offline

Thanks Meter: 0

same problem.. server error..

10-01-2018, 15:33

#71 (permalink)

telmagdy

Freak Poster

Join Date: Jan 2011

Location: HK

Posts: 300

Member: 1494964

Status: Offline

Sonork: 100.100.573

Thanks Meter: 169

Card connected, reading info.
Serial: UMTxxxxxxxxx
Connecting to server, chhecking for update, wait.

10-01-2018, 15:37

#72 (permalink)

GAURAV-MOBILE

Freak Poster

Join Date: Aug 2012

Location: Pratapgarh,U.P.,India

Posts: 166

Member: 1798882

Status: Offline

Thanks Meter: 155

umt team please fix update error problem

umt team please fix update error problem

and

please reply

10-01-2018, 15:46

#73 (permalink)

LoveLess

No Life Poster

Join Date: May 2005

Age: 39

Posts: 9,742

Member: 146708

Status: Offline

Sonork: 100.108221

Thanks Meter: 1,611

hey..

any problem on latest updater..? qc fire..? not updating the box fw…

Error: Connection problems , no response received..

10-01-2018, 15:59

#74 (permalink)

moqued

Insane Poster

Join Date: Aug 2009

Location: Spain

Age: 32

Posts: 82

Member: 1089253

Status: Offline

Sonork: 100.1659642

Thanks Meter: 7

Can you help me? I cant update my dongle
«Error: Conection Problems, no response received»
thanks

10-01-2018, 16:17

#75 (permalink)

mmtheo

No Life Poster

Join Date: Jul 2016

Location: Africa

Posts: 838

Member: 2601900

Status: Offline

Thanks Meter: 519

same here no connection

Источник

Were you able to set it up? @cherylmc @lawrencegripper @msrini-MSFT

I seem to have the same issue:

$ sudo ipsec up azure
initiating IKE_SA azure[1] to X.X.X.X
generating IKE_SA_INIT request 0 [ SA KE No N(NATD_S_IP) N(NATD_D_IP) N(FRAG_SUP) N(HASH_ALG) N(REDIR_SUP) ]
sending packet: from 10.100.102.4[500] to X.X.X.X[500] (726 bytes)
received packet: from X.X.X.X[500] to 10.100.102.4[500] (38 bytes)
parsed IKE_SA_INIT response 0 [ N(INVAL_KE) ]
peer didn't accept DH group ECP_256, it requested MODP_2048
initiating IKE_SA azure[1] to X.X.X.X
generating IKE_SA_INIT request 0 [ SA KE No N(NATD_S_IP) N(NATD_D_IP) N(FRAG_SUP) N(HASH_ALG) N(REDIR_SUP) ]
sending packet: from 10.100.102.4[500] to X.X.X.X[500] (918 bytes)
received packet: from X.X.X.X[500] to 10.100.102.4[500] (517 bytes)
parsed IKE_SA_INIT response 0 [ SA KE No N(FRAG_SUP) N(NATD_S_IP) N(NATD_D_IP) V V CERTREQ ]
received MS NT5 ISAKMPOAKLEY v9 vendor ID
received MS-Negotiation Discovery Capable vendor ID
local host is behind NAT, sending keep alives
received cert request for "CN=VPN CA"
sending cert request for "CN=VPN CA"
sending cert request for "C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Global Root CA"
establishing CHILD_SA azure{1}
generating IKE_AUTH request 1 [ IDi N(INIT_CONTACT) CERTREQ CPRQ(ADDR DNS) SA TSi TSr N(MOBIKE_SUP) N(ADD_4_ADDR) N(ADD_4_ADDR) N(EAP_ONLY) N(MSG_ID_SYN_SUP) ]
sending packet: from 10.100.102.4[4500] to X.X.X.X[4500] (339 bytes)
received packet: from X.X.X.X[4500] to 10.100.102.4[4500] (1276 bytes)
parsed IKE_AUTH response 1 [ EF(1/3) ]
received fragment #1 of 3, waiting for complete IKE message
received packet: from X.X.X.X[4500] to 10.100.102.4[4500] (1276 bytes)
parsed IKE_AUTH response 1 [ EF(2/3) ]
received fragment #2 of 3, waiting for complete IKE message
received packet: from X.X.X.X[4500] to 10.100.102.4[4500] (1132 bytes)
parsed IKE_AUTH response 1 [ EF(3/3) ]
received fragment #3 of 3, reassembling fragmented IKE message
parsed IKE_AUTH response 1 [ IDr CERT CERT AUTH EAP/REQ/ID ]
received end entity cert "C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=EDITED.vpn.azure.com"
received issuer cert "C=US, O=DigiCert Inc, CN=DigiCert SHA2 Secure Server CA"
  using certificate "C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=EDITED.vpn.azure.com"
  using untrusted intermediate certificate "C=US, O=DigiCert Inc, CN=DigiCert SHA2 Secure Server CA"
checking certificate status of "C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=EDITED.vpn.azure.com"
  requesting ocsp status from 'http://ocsp.digicert.com' ...
unable to fetch from http://ocsp.digicert.com, no capable fetcher found
ocsp request to http://ocsp.digicert.com failed
ocsp check failed, fallback to crl
  fetching crl from 'http://crl3.digicert.com/ssca-sha2-g6.crl' ...
unable to fetch from http://crl3.digicert.com/ssca-sha2-g6.crl, no capable fetcher found
crl fetching failed
  fetching crl from 'http://crl4.digicert.com/ssca-sha2-g6.crl' ...
unable to fetch from http://crl4.digicert.com/ssca-sha2-g6.crl, no capable fetcher found
crl fetching failed
certificate status is not available
  using trusted ca certificate "C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Global Root CA"
checking certificate status of "C=US, O=DigiCert Inc, CN=DigiCert SHA2 Secure Server CA"
  requesting ocsp status from 'http://ocsp.digicert.com' ...
unable to fetch from http://ocsp.digicert.com, no capable fetcher found
ocsp request to http://ocsp.digicert.com failed
ocsp check failed, fallback to crl
  fetching crl from 'http://crl3.digicert.com/DigiCertGlobalRootCA.crl' ...
unable to fetch from http://crl3.digicert.com/DigiCertGlobalRootCA.crl, no capable fetcher found
crl fetching failed
  fetching crl from 'http://crl4.digicert.com/DigiCertGlobalRootCA.crl' ...
unable to fetch from http://crl4.digicert.com/DigiCertGlobalRootCA.crl, no capable fetcher found
crl fetching failed
certificate status is not available
certificate policy 2.16.840.1.114412.1.1 for 'C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=EDITED.vpn.azure.com' not allowed by trustchain, ignored
certificate policy 2.23.140.1.2.2 for 'C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=EDITED.vpn.azure.com' not allowed by trustchain, ignored
  reached self-signed root ca with a path length of 1
authentication of 'C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=EDITED.vpn.azure.com' with RSA signature successful
server requested EAP_IDENTITY (id 0x00), sending 'xavier001'
EAP_IDENTITY not supported, sending EAP_NAK
generating IKE_AUTH request 2 [ EAP/RES/NAK ]
sending packet: from 10.100.102.4[4500] to X.X.X.X[4500] (67 bytes)
received packet: from X.X.X.X[4500] to 10.100.102.4[4500] (72 bytes)
parsed IKE_AUTH response 2 [ N(MS_STATUS(1244)) ]
received MS_NOTIFY_STATUS notify error
establishing connection 'azure' failed

$ cat /etc/ipsec.conf

conn azure
	keyexchange=ikev2
	type=tunnel
	leftfirewall=yes
	left=%any
	leftauth=eap-tls
	leftid=%xavier001 # use the DNS alternative name prefixed with the %
	right=azuregateway-EDITED.vpn.azure.com
	rightid=%azuregateway-EDITED.vpn.azure.com
	rightsubnet=0.0.0.0/0
	leftsourceip=%config
	auto=add

$ sudo cat /etc/ipsec.secrets
: P12 xavier001.p12 'pass' # key filename inside /etc/ipsec.d/private directory

$ ls -la /etc/ipsec.d/private/
-rw-------  1 root   root   3157 Jul 26 03:11 xavier001.p12

$ ls -la /etc/ipsec.d/cacerts/
-rw-rw-r--  1 root root  947 Jul 26 02:51 VpnServerRoot.cer

$ sudo apt list --installed | grep strongswan

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libstrongswan/bionic-updates,now 5.6.2-1ubuntu2.4 arm64 [installed,automatic]
libstrongswan-standard-plugins/bionic-updates,now 5.6.2-1ubuntu2.4 arm64 [installed]
strongswan/bionic-updates,now 5.6.2-1ubuntu2.4 all [installed,automatic]
strongswan-charon/bionic-updates,now 5.6.2-1ubuntu2.4 arm64 [installed,automatic]
strongswan-libcharon/bionic-updates,now 5.6.2-1ubuntu2.4 arm64 [installed,automatic]
strongswan-pki/bionic-updates,now 5.6.2-1ubuntu2.4 arm64 [installed]
strongswan-starter/bionic-updates,now 5.6.2-1ubuntu2.4 arm64 [installed,automatic]
strongswan-swanctl/bionic-updates,now 5.6.2-1ubuntu2.4 arm64 [installed]

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.2 LTS
Release:	18.04
Codename:	bionic

$ uname -a
Linux nvidia-desktop 4.9.140-tegra #1 SMP PREEMPT Tue Jul 16 17:09:53 PDT 2019 aarch64 aarch64 aarch64 GNU/Linux

Any idea?

Источник