Forum Discussion
Ciyaresh
Mar 18, 2024Brass Contributor
Extension service logs - Failed to connect to pipe/local socket
Hello everyone,
We have recently on-boarded some test VMs to Azure Arc and now trying to install Azure Monitor Agent on them. However, the AMA extension is stuck in "creating" status in Azure. When we checked the logs on the VM from programdata\GuestCOnfig\ext_mgr_logs\gc_ext.log we see the
"failed to connect to pipe local socket"
errors followed by the
[2024-03-18 23:38:21.262] [PID 8528] [TID 5332] [Pull Client] [INFO] [607a4e22-78b0-43b2-9a6d-b0e584eedc03] invoke_agent_service_request return_code = 400
[2024-03-18 23:38:21.263] [PID 8528] [TID 5332] [Pull Client] [ERROR] [607a4e22-78b0-43b2-9a6d-b0e584eedc03] [C:\__w\1\s\src\dsc\gc_pullclient\dsc_pull_client.cpp:652] Failed to update extensions Error : Failed to get extension list from agent service. Status Code '400'. Error Message 'Failed to issue request : uri: https://uksouth-gas.guestconfiguration.azure.com/machines/xxxxxxx/extensions?api-version=2019-08-08// with error: SSL Error: WINHTTP_CALLBACK_STATUS_FLAG_SECURITY_CHANNEL_ERROR internal error.'.
[2024-03-18 23:38:21.263] [PID 8528] [TID 5332] [DISPATCHER] [ERROR] [607a4e22-78b0-43b2-9a6d-b0e584eedc03] [C:\__w\1\s\src\dsc\em_dispatcher\em_dispatcher.cpp:304] Failed to finish extension workflow. Error : Failed to get extension list from agent service. Status Code '400'. Error Message 'Failed to issue request : uri: https://uksouth-gas.guestconfiguration.azure.com/machines/7xxxxxxxxxxx/extensions?api-version=2019-08-08// with error: SSL Error: WINHTTP_CALLBACK_STATUS_FLAG_SECURITY_CHANNEL_ERROR internal error.'.
[2024-03-18 23:38:21.264] [PID 8528] [TID 5332] [TIMER] [ERROR] [607a4e22-78b0-43b2-9a6d-b0e584eedc03] [C:\__w\1\s\src\dsc\em_timer\em_timer.cpp:47] Failed when executing timer for System_Boot_Trigger
However, when we run the
azcmagent check --location UKSouth -p
all checks are passed?
1 Reply
- CiyareshBrass ContributorWe found out that local security policy for ciphers wasn't quite right. I don't know what IT did exactly but I believe we were using server 2012 group policies and this was a server 2022. Just in case anyone else has the same issue.