topic Alarm failed to start grpc connection with address urlcat.hawkeye.services-edge.paloaltonetworks.com:443 in General Topics

Alarm failed to start grpc connection with address urlcat.hawkeye.services-edge.paloaltonetworks.com:443

BigPalo — Fri, 23 Feb 2024 11:46:51 GMT

Hi,

We are receiving this alarm:

severity: high opaque: Failed to establish GRPC connection to UrlCat service: failed to start grpc connection with address urlcat.hawkeye.services-edge.paloaltonetworks.com:443, err context deadline exceeded

We tried to disable the app id cloud engine following the next procedure but the alert is still showing:

https://docs.paloaltonetworks.com/pan-os/10-1/pan-os-admin/app-id/cloud-based-app-id-service/enable-or-disable-the-app-id-cloud-engine

How can we stop generating this alarm?

Thanks

Re: Alarm failed to start grpc connection with address urlcat.hawkeye.services-edge.paloaltonetworks.com:443

NielsenStassyns — Wed, 28 Feb 2024 09:36:36 GMT

We have the same issue. I think it might be related to the IoT license. Our customer used to have this IoT trial license and now it is gone but I think the Palo Alto still tries to connect to urlcat.hawkeye.services-edge.paloaltonetworks.com

Is there some config that could be cleaned up?

KR,

Re: Alarm failed to start grpc connection with address urlcat.hawkeye.services-edge.paloaltonetworks.com:443

naveen3992 — Sat, 13 Apr 2024 05:15:15 GMT

We fixed by using the below commands and restart the service for the change to take into effect

set system setting ctd feature-forward mica disable

debug software restart process ctd-agent