Local mirror image url always keeps ubuntu image in queued state

prantiknag · 2 December 2024 20:10

Download from maas.io and created local mirror image and set the custom url but ubuntu 22.04 is remain in Queued for download state.

Anyone have any idea on this, how to resolve it?

r00ta · 2 December 2024 21:36

You’d better look at the MAAS logs to check what’s the underlying error

prantiknag · 3 December 2024 14:37

Didn’t get anything significant from the logs.
Created this local mirror and assigned it as custom url.
this mirror contains similar directory structures and files which is in maas.io url.
This 22.04 LTS always remains in Queued for Download state.
Also unable to upload custom image, it’s giving architecture not found!!

r00ta · 3 December 2024 14:39

this might be the problem

prantiknag · 3 December 2024 14:45

downloaded from maas.io website and placed the same directory in local mirror.

r00ta · 3 December 2024 14:46

Did you follow this doc?

prantiknag · 4 December 2024 05:33

I followed the document and created local mirror in the same way, however I am getting Region controller importing

Also Image is also in Queued for download state.
Tried to upload custom image but I am getting architecture not found error.

r00ta · 4 December 2024 07:28

Please upload the regiond logs somewhere so that I can double check if there is any exception

prantiknag · 4 December 2024 09:28

I am using without internet setup
and also havn’t found logs in /var/snap/maas/common/log/

r00ta · 4 December 2024 09:32

see here to understand how to extract the logs in 3.5 MAAS | About MAAS logging

prantiknag · 4 December 2024 10:54

Thanks, I got the logs and attaching the logs here—
Please check and help me to resolve this issue with local mirror and without internet—

Dec 04 04:26:36 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:26:36 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:26:52 RG-PT maas.pebble[138227]: 2024-12-04T09:26:52.750Z [pebble] GET /v1/services?names=http 66.547µs 200
Dec 04 04:26:52 RG-PT maas.pebble[138227]: 2024-12-04T09:26:52.750Z [pebble] GET /v1/services?names=dhcpd 73.581µs 200
Dec 04 04:26:52 RG-PT maas.pebble[138227]: 2024-12-04T09:26:52.750Z [pebble] GET /v1/services?names=agent 21.652µs 200
Dec 04 04:26:52 RG-PT maas.pebble[138227]: 2024-12-04T09:26:52.750Z [pebble] GET /v1/services?names=dhcpd6 41.099µs 200
Dec 04 04:26:59 RG-PT maas.pebble[138227]: 2024-12-04T09:26:59.646Z [pebble] GET /v1/services?names=bind9 64.794µs 200
Dec 04 04:26:59 RG-PT maas.pebble[138227]: 2024-12-04T09:26:59.646Z [pebble] GET /v1/services?names=syslog 42.893µs 200
Dec 04 04:26:59 RG-PT maas.pebble[138227]: 2024-12-04T09:26:59.646Z [pebble] GET /v1/services?names=temporal 41.94µs 200
Dec 04 04:26:59 RG-PT maas.pebble[138227]: 2024-12-04T09:26:59.646Z [pebble] GET /v1/services?names=ntp 72.158µs 200
Dec 04 04:26:59 RG-PT maas.pebble[138227]: 2024-12-04T09:26:59.646Z [pebble] GET /v1/services?names=http 28.165µs 200
Dec 04 04:26:59 RG-PT maas.pebble[138227]: 2024-12-04T09:26:59.647Z [pebble] GET /v1/services?names=temporal-worker 44.846µs 200
Dec 04 04:26:59 RG-PT maas.pebble[138227]: 2024-12-04T09:26:59.661Z [pebble] GET /v1/services?names=proxy 46.399µs 200
Dec 04 04:27:06 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:27:06 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:27:22 RG-PT maas.pebble[138227]: 2024-12-04T09:27:22.752Z [pebble] GET /v1/services?names=http 72.419µs 200
Dec 04 04:27:22 RG-PT maas.pebble[138227]: 2024-12-04T09:27:22.752Z [pebble] GET /v1/services?names=agent 44.655µs 200
Dec 04 04:27:22 RG-PT maas.pebble[138227]: 2024-12-04T09:27:22.752Z [pebble] GET /v1/services?names=dhcpd6 60.535µs 200
Dec 04 04:27:22 RG-PT maas.pebble[138227]: 2024-12-04T09:27:22.752Z [pebble] GET /v1/services?names=dhcpd 26.381µs 200
Dec 04 04:27:29 RG-PT maas.pebble[138227]: 2024-12-04T09:27:29.650Z [pebble] GET /v1/services?names=bind9 64.293µs 200
Dec 04 04:27:29 RG-PT maas.pebble[138227]: 2024-12-04T09:27:29.650Z [pebble] GET /v1/services?names=temporal-worker 20.54µs 200
Dec 04 04:27:29 RG-PT maas.pebble[138227]: 2024-12-04T09:27:29.650Z [pebble] GET /v1/services?names=ntp 18.857µs 200
Dec 04 04:27:29 RG-PT maas.pebble[138227]: 2024-12-04T09:27:29.650Z [pebble] GET /v1/services?names=syslog 31.35µs 200
Dec 04 04:27:29 RG-PT maas.pebble[138227]: 2024-12-04T09:27:29.650Z [pebble] GET /v1/services?names=temporal 65.385µs 200
Dec 04 04:27:29 RG-PT maas.pebble[138227]: 2024-12-04T09:27:29.650Z [pebble] GET /v1/services?names=http 68.792µs 200
Dec 04 04:27:29 RG-PT maas.pebble[138227]: 2024-12-04T09:27:29.663Z [pebble] GET /v1/services?names=proxy 65.886µs 200
Dec 04 04:27:36 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:27:36 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:27:52 RG-PT maas.pebble[138227]: 2024-12-04T09:27:52.751Z [pebble] GET /v1/services?names=http 68.962µs 200
Dec 04 04:27:52 RG-PT maas.pebble[138227]: 2024-12-04T09:27:52.751Z [pebble] GET /v1/services?names=dhcpd 55.667µs 200
Dec 04 04:27:52 RG-PT maas.pebble[138227]: 2024-12-04T09:27:52.751Z [pebble] GET /v1/services?names=dhcpd6 38.804µs 200
Dec 04 04:27:52 RG-PT maas.pebble[138227]: 2024-12-04T09:27:52.751Z [pebble] GET /v1/services?names=agent 35.949µs 200
Dec 04 04:27:59 RG-PT maas.pebble[138227]: 2024-12-04T09:27:59.646Z [pebble] GET /v1/services?names=bind9 62.229µs 200
Dec 04 04:27:59 RG-PT maas.pebble[138227]: 2024-12-04T09:27:59.646Z [pebble] GET /v1/services?names=ntp 59.052µs 200
Dec 04 04:27:59 RG-PT maas.pebble[138227]: 2024-12-04T09:27:59.647Z [pebble] GET /v1/services?names=temporal 32.361µs 200
Dec 04 04:27:59 RG-PT maas.pebble[138227]: 2024-12-04T09:27:59.647Z [pebble] GET /v1/services?names=http 35.007µs 200
Dec 04 04:27:59 RG-PT maas.pebble[138227]: 2024-12-04T09:27:59.647Z [pebble] GET /v1/services?names=syslog 24.267µs 200
Dec 04 04:27:59 RG-PT maas.pebble[138227]: 2024-12-04T09:27:59.647Z [pebble] GET /v1/services?names=temporal-worker 46.83µs 200
Dec 04 04:27:59 RG-PT maas.pebble[138227]: 2024-12-04T09:27:59.657Z [pebble] GET /v1/services?names=proxy 29.767µs 200
Dec 04 04:28:06 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:28:06 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:28:22 RG-PT maas.pebble[138227]: 2024-12-04T09:28:22.751Z [pebble] GET /v1/services?names=http 68.912µs 200
Dec 04 04:28:22 RG-PT maas.pebble[138227]: 2024-12-04T09:28:22.751Z [pebble] GET /v1/services?names=dhcpd 26.751µs 200
Dec 04 04:28:22 RG-PT maas.pebble[138227]: 2024-12-04T09:28:22.751Z [pebble] GET /v1/services?names=agent 61.657µs 200
Dec 04 04:28:22 RG-PT maas.pebble[138227]: 2024-12-04T09:28:22.751Z [pebble] GET /v1/services?names=dhcpd6 54.444µs 200
Dec 04 04:28:29 RG-PT maas.pebble[138227]: 2024-12-04T09:28:29.648Z [pebble] GET /v1/services?names=bind9 54.294µs 200
Dec 04 04:28:29 RG-PT maas.pebble[138227]: 2024-12-04T09:28:29.648Z [pebble] GET /v1/services?names=ntp 47.521µs 200
Dec 04 04:28:29 RG-PT maas.pebble[138227]: 2024-12-04T09:28:29.648Z [pebble] GET /v1/services?names=temporal-worker 23.595µs 200
Dec 04 04:28:29 RG-PT maas.pebble[138227]: 2024-12-04T09:28:29.648Z [pebble] GET /v1/services?names=syslog 65.045µs 200
Dec 04 04:28:29 RG-PT maas.pebble[138227]: 2024-12-04T09:28:29.648Z [pebble] GET /v1/services?names=http 17.703µs 200
Dec 04 04:28:29 RG-PT maas.pebble[138227]: 2024-12-04T09:28:29.648Z [pebble] GET /v1/services?names=temporal 22.142µs 200
Dec 04 04:28:29 RG-PT maas.pebble[138227]: 2024-12-04T09:28:29.654Z [pebble] GET /v1/services?names=proxy 48.052µs 200
Dec 04 04:28:36 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:28:36 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:28:52 RG-PT maas.pebble[138227]: 2024-12-04T09:28:52.753Z [pebble] GET /v1/services?names=agent 66.707µs 200
Dec 04 04:28:52 RG-PT maas.pebble[138227]: 2024-12-04T09:28:52.753Z [pebble] GET /v1/services?names=dhcpd6 46.289µs 200
Dec 04 04:28:52 RG-PT maas.pebble[138227]: 2024-12-04T09:28:52.753Z [pebble] GET /v1/services?names=http 132.223µs 200
Dec 04 04:28:52 RG-PT maas.pebble[138227]: 2024-12-04T09:28:52.753Z [pebble] GET /v1/services?names=dhcpd 21.672µs 200
Dec 04 04:28:59 RG-PT maas.pebble[138227]: 2024-12-04T09:28:59.647Z [pebble] GET /v1/services?names=bind9 57.83µs 200
Dec 04 04:28:59 RG-PT maas.pebble[138227]: 2024-12-04T09:28:59.647Z [pebble] GET /v1/services?names=ntp 59.354µs 200
Dec 04 04:28:59 RG-PT maas.pebble[138227]: 2024-12-04T09:28:59.647Z [pebble] GET /v1/services?names=syslog 40.838µs 200
Dec 04 04:28:59 RG-PT maas.pebble[138227]: 2024-12-04T09:28:59.647Z [pebble] GET /v1/services?names=temporal-worker 28.113µs 200
Dec 04 04:28:59 RG-PT maas.pebble[138227]: 2024-12-04T09:28:59.647Z [pebble] GET /v1/services?names=temporal 20.56µs 200
Dec 04 04:28:59 RG-PT maas.pebble[138227]: 2024-12-04T09:28:59.647Z [pebble] GET /v1/services?names=http 35.658µs 200
Dec 04 04:28:59 RG-PT maas.pebble[138227]: 2024-12-04T09:28:59.651Z [pebble] GET /v1/services?names=proxy 28.565µs 200
Dec 04 04:29:02 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:29:02 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:29:22 RG-PT maas.pebble[138227]: 2024-12-04T09:29:22.751Z [pebble] GET /v1/services?names=http 63.762µs 200
Dec 04 04:29:22 RG-PT maas.pebble[138227]: 2024-12-04T09:29:22.751Z [pebble] GET /v1/services?names=dhcpd6 54.344µs 200
Dec 04 04:29:22 RG-PT maas.pebble[138227]: 2024-12-04T09:29:22.751Z [pebble] GET /v1/services?names=dhcpd 29.236µs 200
Dec 04 04:29:22 RG-PT maas.pebble[138227]: 2024-12-04T09:29:22.751Z [pebble] GET /v1/services?names=agent 47.21µs 200
Dec 04 04:29:29 RG-PT maas.pebble[138227]: 2024-12-04T09:29:29.649Z [pebble] GET /v1/services?names=bind9 67.249µs 200
Dec 04 04:29:29 RG-PT maas.pebble[138227]: 2024-12-04T09:29:29.649Z [pebble] GET /v1/services?names=ntp 34.336µs 200
Dec 04 04:29:29 RG-PT maas.pebble[138227]: 2024-12-04T09:29:29.649Z [pebble] GET /v1/services?names=http 71.626µs 200
Dec 04 04:29:29 RG-PT maas.pebble[138227]: 2024-12-04T09:29:29.649Z [pebble] GET /v1/services?names=syslog 93.92µs 200
Dec 04 04:29:29 RG-PT maas.pebble[138227]: 2024-12-04T09:29:29.649Z [pebble] GET /v1/services?names=temporal 20.609µs 200
Dec 04 04:29:29 RG-PT maas.pebble[138227]: 2024-12-04T09:29:29.649Z [pebble] GET /v1/services?names=temporal-worker 27.372µs 200
Dec 04 04:29:29 RG-PT maas.pebble[138227]: 2024-12-04T09:29:29.658Z [pebble] GET /v1/services?names=proxy 48.443µs 200
Dec 04 04:29:36 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:29:36 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:29:36 RG-PT maas-regiond[138431]: regiond: [info] 127.0.0.1 GET /MAAS/rpc/ HTTP/1.1 → 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
Dec 04 04:29:52 RG-PT maas.pebble[138227]: 2024-12-04T09:29:52.753Z [pebble] GET /v1/services?names=agent 92.888µs 200
Dec 04 04:29:52 RG-PT maas.pebble[138227]: 2024-12-04T09:29:52.753Z [pebble] GET /v1/services?names=dhcpd6 24.727µs 200
Dec 04 04:29:52 RG-PT maas.pebble[138227]: 2024-12-04T09:29:52.753Z [pebble] GET /v1/services?names=dhcpd 27.923µs 200
Dec 04 04:29:52 RG-PT maas.pebble[138227]: 2024-12-04T09:29:52.754Z [pebble] GET /v1/services?names=http 904.901µs 200
Dec 04 04:29:59 RG-PT maas.pebble[138227]: 2024-12-04T09:29:59.646Z [pebble] GET /v1/services?names=bind9 56.849µs 200
Dec 04 04:29:59 RG-PT maas.pebble[138227]: 2024-12-04T09:29:59.646Z [pebble] GET /v1/services?names=ntp 39.987µs 200
Dec 04 04:29:59 RG-PT maas.pebble[138227]: 2024-12-04T09:29:59.646Z [pebble] GET /v1/services?names=syslog 38.785µs 200
Dec 04 04:29:59 RG-PT maas.pebble[138227]: 2024-12-04T09:29:59.646Z [pebble] GET /v1/services?names=temporal 19.467µs 200
Dec 04 04:29:59 RG-PT maas.pebble[138227]: 2024-12-04T09:29:59.646Z [pebble] GET /v1/services?names=http 19.147µs 200
Dec 04 04:29:59 RG-PT maas.pebble[138227]: 2024-12-04T09:29:59.646Z [pebble] GET /v1/services?names=temporal-worker 20.8µs 200
Dec 04 04:29:59 RG-PT maas.pebble[138227]: 2024-12-04T09:29:59.652Z [pebble] GET /v1/services?names=proxy 35.638µs 200
Dec 04 04:30:06 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:30:06 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:30:22 RG-PT maas.pebble[138227]: 2024-12-04T09:30:22.771Z [pebble] GET /v1/services?names=http 71.647µs 200
Dec 04 04:30:22 RG-PT maas.pebble[138227]: 2024-12-04T09:30:22.772Z [pebble] GET /v1/services?names=agent 29.797µs 200
Dec 04 04:30:22 RG-PT maas.pebble[138227]: 2024-12-04T09:30:22.772Z [pebble] GET /v1/services?names=dhcpd 33.945µs 200
Dec 04 04:30:22 RG-PT maas.pebble[138227]: 2024-12-04T09:30:22.772Z [pebble] GET /v1/services?names=dhcpd6 59.885µs 200
Dec 04 04:30:22 RG-PT maas-rackd[138284]: provisioningserver.rackdservices.dhcp_probe_service: [info] Probe for external DHCP servers started on interfaces: cni0, ens192, flannel.1.
Dec 04 04:30:29 RG-PT maas.pebble[138227]: 2024-12-04T09:30:29.647Z [pebble] GET /v1/services?names=bind9 56.027µs 200
Dec 04 04:30:29 RG-PT maas.pebble[138227]: 2024-12-04T09:30:29.647Z [pebble] GET /v1/services?names=syslog 64.153µs 200
Dec 04 04:30:29 RG-PT maas.pebble[138227]: 2024-12-04T09:30:29.647Z [pebble] GET /v1/services?names=ntp 43.093µs 200
Dec 04 04:30:29 RG-PT maas.pebble[138227]: 2024-12-04T09:30:29.647Z [pebble] GET /v1/services?names=temporal-worker 54.083µs 200
Dec 04 04:30:29 RG-PT maas.pebble[138227]: 2024-12-04T09:30:29.647Z [pebble] GET /v1/services?names=http 32.301µs 200
Dec 04 04:30:29 RG-PT maas.pebble[138227]: 2024-12-04T09:30:29.647Z [pebble] GET /v1/services?names=temporal 58.192µs 200
Dec 04 04:30:29 RG-PT maas.pebble[138227]: 2024-12-04T09:30:29.657Z [pebble] GET /v1/services?names=proxy 50.096µs 200
Dec 04 04:30:36 RG-PT maas-regiond[138431]: maasserver.regiondservices.active_discovery: [info] Active network discovery: Active scanning is not enabled on any subnet. Skipping periodic scan.
Dec 04 04:30:36 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:30:36 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:30:52 RG-PT maas.pebble[138227]: 2024-12-04T09:30:52.752Z [pebble] GET /v1/services?names=http 54.724µs 200
Dec 04 04:30:52 RG-PT maas.pebble[138227]: 2024-12-04T09:30:52.752Z [pebble] GET /v1/services?names=dhcpd 45.988µs 200
Dec 04 04:30:52 RG-PT maas.pebble[138227]: 2024-12-04T09:30:52.752Z [pebble] GET /v1/services?names=dhcpd6 135.389µs 200
Dec 04 04:30:52 RG-PT maas.pebble[138227]: 2024-12-04T09:30:52.752Z [pebble] GET /v1/services?names=agent 40.377µs 200
Dec 04 04:30:52 RG-PT maas-rackd[138284]: provisioningserver.rackdservices.dhcp_probe_service: [info] External DHCP probe complete.
Dec 04 04:30:59 RG-PT maas.pebble[138227]: 2024-12-04T09:30:59.647Z [pebble] GET /v1/services?names=bind9 59.093µs 200
Dec 04 04:30:59 RG-PT maas.pebble[138227]: 2024-12-04T09:30:59.647Z [pebble] GET /v1/services?names=syslog 42.041µs 200
Dec 04 04:30:59 RG-PT maas.pebble[138227]: 2024-12-04T09:30:59.647Z [pebble] GET /v1/services?names=temporal-worker 23.074µs 200
Dec 04 04:30:59 RG-PT maas.pebble[138227]: 2024-12-04T09:30:59.647Z [pebble] GET /v1/services?names=ntp 81.276µs 200
Dec 04 04:30:59 RG-PT maas.pebble[138227]: 2024-12-04T09:30:59.647Z [pebble] GET /v1/services?names=http 35.818µs 200
Dec 04 04:30:59 RG-PT maas.pebble[138227]: 2024-12-04T09:30:59.647Z [pebble] GET /v1/services?names=temporal 21.431µs 200
Dec 04 04:30:59 RG-PT maas.pebble[138227]: 2024-12-04T09:30:59.653Z [pebble] GET /v1/services?names=proxy 44.977µs 200
Dec 04 04:31:06 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:31:06 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:31:22 RG-PT maas.pebble[138227]: 2024-12-04T09:31:22.750Z [pebble] GET /v1/services?names=http 61.417µs 200
Dec 04 04:31:22 RG-PT maas.pebble[138227]: 2024-12-04T09:31:22.750Z [pebble] GET /v1/services?names=agent 36.529µs 200
Dec 04 04:31:22 RG-PT maas.pebble[138227]: 2024-12-04T09:31:22.750Z [pebble] GET /v1/services?names=dhcpd6 40.557µs 200
Dec 04 04:31:22 RG-PT maas.pebble[138227]: 2024-12-04T09:31:22.750Z [pebble] GET /v1/services?names=dhcpd 34.816µs 200
Dec 04 04:31:29 RG-PT maas.pebble[138227]: 2024-12-04T09:31:29.649Z [pebble] GET /v1/services?names=syslog 59.252µs 200
Dec 04 04:31:29 RG-PT maas.pebble[138227]: 2024-12-04T09:31:29.649Z [pebble] GET /v1/services?names=http 72.397µs 200
Dec 04 04:31:29 RG-PT maas.pebble[138227]: 2024-12-04T09:31:29.649Z [pebble] GET /v1/services?names=temporal 17.623µs 200
Dec 04 04:31:29 RG-PT maas.pebble[138227]: 2024-12-04T09:31:29.649Z [pebble] GET /v1/services?names=temporal-worker 19.908µs 200
Dec 04 04:31:29 RG-PT maas.pebble[138227]: 2024-12-04T09:31:29.649Z [pebble] GET /v1/services?names=ntp 50.646µs 200
Dec 04 04:31:29 RG-PT maas.pebble[138227]: 2024-12-04T09:31:29.649Z [pebble] GET /v1/services?names=bind9 33.503µs 200
Dec 04 04:31:29 RG-PT maas.pebble[138227]: 2024-12-04T09:31:29.652Z [pebble] GET /v1/services?names=proxy 28.213µs 200
Dec 04 04:31:36 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:31:36 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:31:52 RG-PT maas.pebble[138227]: 2024-12-04T09:31:52.752Z [pebble] GET /v1/services?names=http 71.046µs 200
Dec 04 04:31:52 RG-PT maas.pebble[138227]: 2024-12-04T09:31:52.752Z [pebble] GET /v1/services?names=dhcpd 68.501µs 200
Dec 04 04:31:52 RG-PT maas.pebble[138227]: 2024-12-04T09:31:52.752Z [pebble] GET /v1/services?names=agent 45.357µs 200
Dec 04 04:31:52 RG-PT maas.pebble[138227]: 2024-12-04T09:31:52.752Z [pebble] GET /v1/services?names=dhcpd6 35.257µs 200
Dec 04 04:31:59 RG-PT maas.pebble[138227]: 2024-12-04T09:31:59.645Z [pebble] GET /v1/services?names=bind9 79.131µs 200
Dec 04 04:31:59 RG-PT maas.pebble[138227]: 2024-12-04T09:31:59.645Z [pebble] GET /v1/services?names=temporal-worker 28.846µs 200
Dec 04 04:31:59 RG-PT maas.pebble[138227]: 2024-12-04T09:31:59.645Z [pebble] GET /v1/services?names=http 34.526µs 200
Dec 04 04:31:59 RG-PT maas.pebble[138227]: 2024-12-04T09:31:59.645Z [pebble] GET /v1/services?names=syslog 38.193µs 200
Dec 04 04:31:59 RG-PT maas.pebble[138227]: 2024-12-04T09:31:59.645Z [pebble] GET /v1/services?names=temporal 102.436µs 200
Dec 04 04:31:59 RG-PT maas.pebble[138227]: 2024-12-04T09:31:59.645Z [pebble] GET /v1/services?names=ntp 37.091µs 200
Dec 04 04:31:59 RG-PT maas.pebble[138227]: 2024-12-04T09:31:59.651Z [pebble] GET /v1/services?names=proxy 47.641µs 200
Dec 04 04:32:06 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:32:06 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:32:22 RG-PT maas.pebble[138227]: 2024-12-04T09:32:22.751Z [pebble] GET /v1/services?names=http 67.589µs 200
Dec 04 04:32:22 RG-PT maas.pebble[138227]: 2024-12-04T09:32:22.751Z [pebble] GET /v1/services?names=dhcpd6 68.651µs 200
Dec 04 04:32:22 RG-PT maas.pebble[138227]: 2024-12-04T09:32:22.751Z [pebble] GET /v1/services?names=dhcpd 21.852µs 200
Dec 04 04:32:22 RG-PT maas.pebble[138227]: 2024-12-04T09:32:22.751Z [pebble] GET /v1/services?names=agent 32.221µs 200
Dec 04 04:32:29 RG-PT maas.pebble[138227]: 2024-12-04T09:32:29.649Z [pebble] GET /v1/services?names=syslog 59.183µs 200
Dec 04 04:32:29 RG-PT maas.pebble[138227]: 2024-12-04T09:32:29.649Z [pebble] GET /v1/services?names=ntp 119.96µs 200
Dec 04 04:32:29 RG-PT maas.pebble[138227]: 2024-12-04T09:32:29.649Z [pebble] GET /v1/services?names=bind9 80.724µs 200
Dec 04 04:32:29 RG-PT maas.pebble[138227]: 2024-12-04T09:32:29.649Z [pebble] GET /v1/services?names=http 31.971µs 200
Dec 04 04:32:29 RG-PT maas.pebble[138227]: 2024-12-04T09:32:29.649Z [pebble] GET /v1/services?names=temporal-worker 42.14µs 200
Dec 04 04:32:29 RG-PT maas.pebble[138227]: 2024-12-04T09:32:29.649Z [pebble] GET /v1/services?names=temporal 22.543µs 200
Dec 04 04:32:29 RG-PT maas.pebble[138227]: 2024-12-04T09:32:29.661Z [pebble] GET /v1/services?names=proxy 65.395µs 200
Dec 04 04:32:36 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:32:36 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:32:52 RG-PT maas.pebble[138227]: 2024-12-04T09:32:52.753Z [pebble] GET /v1/services?names=http 62.089µs 200
Dec 04 04:32:52 RG-PT maas.pebble[138227]: 2024-12-04T09:32:52.753Z [pebble] GET /v1/services?names=dhcpd 49.995µs 200
Dec 04 04:32:52 RG-PT maas.pebble[138227]: 2024-12-04T09:32:52.753Z [pebble] GET /v1/services?names=dhcpd6 54.364µs 200
Dec 04 04:32:52 RG-PT maas.pebble[138227]: 2024-12-04T09:32:52.754Z [pebble] GET /v1/services?names=agent 29.156µs 200
Dec 04 04:32:59 RG-PT maas.pebble[138227]: 2024-12-04T09:32:59.647Z [pebble] GET /v1/services?names=bind9 65.876µs 200
Dec 04 04:32:59 RG-PT maas.pebble[138227]: 2024-12-04T09:32:59.647Z [pebble] GET /v1/services?names=syslog 35.558µs 200
Dec 04 04:32:59 RG-PT maas.pebble[138227]: 2024-12-04T09:32:59.647Z [pebble] GET /v1/services?names=ntp 103.668µs 200
Dec 04 04:32:59 RG-PT maas.pebble[138227]: 2024-12-04T09:32:59.647Z [pebble] GET /v1/services?names=http 57.159µs 200
Dec 04 04:32:59 RG-PT maas.pebble[138227]: 2024-12-04T09:32:59.647Z [pebble] GET /v1/services?names=temporal 20.83µs 200
Dec 04 04:32:59 RG-PT maas.pebble[138227]: 2024-12-04T09:32:59.647Z [pebble] GET /v1/services?names=temporal-worker 16.482µs 200
Dec 04 04:32:59 RG-PT maas.pebble[138227]: 2024-12-04T09:32:59.655Z [pebble] GET /v1/services?names=proxy 31.631µs 200
Dec 04 04:33:06 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:33:06 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:33:22 RG-PT maas.pebble[138227]: 2024-12-04T09:33:22.749Z [pebble] GET /v1/services?names=http 67.048µs 200
Dec 04 04:33:22 RG-PT maas.pebble[138227]: 2024-12-04T09:33:22.749Z [pebble] GET /v1/services?names=agent 30.959µs 200
Dec 04 04:33:22 RG-PT maas.pebble[138227]: 2024-12-04T09:33:22.749Z [pebble] GET /v1/services?names=dhcpd6 46.799µs 200
Dec 04 04:33:22 RG-PT maas.pebble[138227]: 2024-12-04T09:33:22.749Z [pebble] GET /v1/services?names=dhcpd 19.778µs 200
Dec 04 04:33:29 RG-PT maas.pebble[138227]: 2024-12-04T09:33:29.648Z [pebble] GET /v1/services?names=bind9 61.848µs 200
Dec 04 04:33:29 RG-PT maas.pebble[138227]: 2024-12-04T09:33:29.648Z [pebble] GET /v1/services?names=ntp 40.287µs 200
Dec 04 04:33:29 RG-PT maas.pebble[138227]: 2024-12-04T09:33:29.648Z [pebble] GET /v1/services?names=http 23.014µs 200
Dec 04 04:33:29 RG-PT maas.pebble[138227]: 2024-12-04T09:33:29.649Z [pebble] GET /v1/services?names=syslog 21.09µs 200
Dec 04 04:33:29 RG-PT maas.pebble[138227]: 2024-12-04T09:33:29.649Z [pebble] GET /v1/services?names=temporal 23.765µs 200
Dec 04 04:33:29 RG-PT maas.pebble[138227]: 2024-12-04T09:33:29.649Z [pebble] GET /v1/services?names=temporal-worker 33.854µs 200
Dec 04 04:33:29 RG-PT maas.pebble[138227]: 2024-12-04T09:33:29.655Z [pebble] GET /v1/services?names=proxy 30.849µs 200
Dec 04 04:33:36 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:33:36 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:33:52 RG-PT maas.pebble[138227]: 2024-12-04T09:33:52.751Z [pebble] GET /v1/services?names=http 67.829µs 200
Dec 04 04:33:52 RG-PT maas.pebble[138227]: 2024-12-04T09:33:52.751Z [pebble] GET /v1/services?names=dhcpd6 29.657µs 200
Dec 04 04:33:52 RG-PT maas.pebble[138227]: 2024-12-04T09:33:52.751Z [pebble] GET /v1/services?names=dhcpd 18.937µs 200
Dec 04 04:33:52 RG-PT maas.pebble[138227]: 2024-12-04T09:33:52.751Z [pebble] GET /v1/services?names=agent 67.589µs 200
Dec 04 04:33:59 RG-PT maas.pebble[138227]: 2024-12-04T09:33:59.647Z [pebble] GET /v1/services?names=bind9 63.591µs 200
Dec 04 04:33:59 RG-PT maas.pebble[138227]: 2024-12-04T09:33:59.647Z [pebble] GET /v1/services?names=ntp 77.508µs 200
Dec 04 04:33:59 RG-PT maas.pebble[138227]: 2024-12-04T09:33:59.647Z [pebble] GET /v1/services?names=temporal 32.302µs 200
Dec 04 04:33:59 RG-PT maas.pebble[138227]: 2024-12-04T09:33:59.647Z [pebble] GET /v1/services?names=syslog 54.674µs 200
Dec 04 04:33:59 RG-PT maas.pebble[138227]: 2024-12-04T09:33:59.647Z [pebble] GET /v1/services?names=http 41.168µs 200
Dec 04 04:33:59 RG-PT maas.pebble[138227]: 2024-12-04T09:33:59.647Z [pebble] GET /v1/services?names=temporal-worker 34.766µs 200
Dec 04 04:33:59 RG-PT maas.pebble[138227]: 2024-12-04T09:33:59.652Z [pebble] GET /v1/services?names=proxy 35.127µs 200
Dec 04 04:34:02 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:34:02 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:34:22 RG-PT maas.pebble[138227]: 2024-12-04T09:34:22.750Z [pebble] GET /v1/services?names=dhcpd 54.965µs 200
Dec 04 04:34:22 RG-PT maas.pebble[138227]: 2024-12-04T09:34:22.750Z [pebble] GET /v1/services?names=http 61.307µs 200
Dec 04 04:34:22 RG-PT maas.pebble[138227]: 2024-12-04T09:34:22.750Z [pebble] GET /v1/services?names=dhcpd6 20.128µs 200
Dec 04 04:34:22 RG-PT maas.pebble[138227]: 2024-12-04T09:34:22.750Z [pebble] GET /v1/services?names=agent 58.652µs 200
Dec 04 04:34:29 RG-PT maas.pebble[138227]: 2024-12-04T09:34:29.648Z [pebble] GET /v1/services?names=bind9 61.077µs 200
Dec 04 04:34:29 RG-PT maas.pebble[138227]: 2024-12-04T09:34:29.648Z [pebble] GET /v1/services?names=ntp 66.277µs 200
Dec 04 04:34:29 RG-PT maas.pebble[138227]: 2024-12-04T09:34:29.648Z [pebble] GET /v1/services?names=syslog 37.202µs 200
Dec 04 04:34:29 RG-PT maas.pebble[138227]: 2024-12-04T09:34:29.648Z [pebble] GET /v1/services?names=temporal 39.385µs 200
Dec 04 04:34:29 RG-PT maas.pebble[138227]: 2024-12-04T09:34:29.648Z [pebble] GET /v1/services?names=http 37.222µs 200
Dec 04 04:34:29 RG-PT maas.pebble[138227]: 2024-12-04T09:34:29.648Z [pebble] GET /v1/services?names=temporal-worker 23.735µs 200
Dec 04 04:34:29 RG-PT maas.pebble[138227]: 2024-12-04T09:34:29.652Z [pebble] GET /v1/services?names=proxy 27.242µs 200
Dec 04 04:34:36 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:34:36 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:34:52 RG-PT maas.pebble[138227]: 2024-12-04T09:34:52.749Z [pebble] GET /v1/services?names=http 67.378µs 200
Dec 04 04:34:52 RG-PT maas.pebble[138227]: 2024-12-04T09:34:52.749Z [pebble] GET /v1/services?names=agent 20.669µs 200
Dec 04 04:34:52 RG-PT maas.pebble[138227]: 2024-12-04T09:34:52.750Z [pebble] GET /v1/services?names=dhcpd 15.249µs 200
Dec 04 04:34:52 RG-PT maas.pebble[138227]: 2024-12-04T09:34:52.750Z [pebble] GET /v1/services?names=dhcpd6 59.925µs 200
Dec 04 04:34:59 RG-PT maas.pebble[138227]: 2024-12-04T09:34:59.649Z [pebble] GET /v1/services?names=bind9 70.274µs 200
Dec 04 04:34:59 RG-PT maas.pebble[138227]: 2024-12-04T09:34:59.649Z [pebble] GET /v1/services?names=syslog 60.746µs 200
Dec 04 04:34:59 RG-PT maas.pebble[138227]: 2024-12-04T09:34:59.649Z [pebble] GET /v1/services?names=ntp 53.131µs 200
Dec 04 04:34:59 RG-PT maas.pebble[138227]: 2024-12-04T09:34:59.649Z [pebble] GET /v1/services?names=temporal-worker 44.095µs 200
Dec 04 04:34:59 RG-PT maas.pebble[138227]: 2024-12-04T09:34:59.649Z [pebble] GET /v1/services?names=http 32.502µs 200
Dec 04 04:34:59 RG-PT maas.pebble[138227]: 2024-12-04T09:34:59.649Z [pebble] GET /v1/services?names=temporal 38.313µs 200
Dec 04 04:34:59 RG-PT maas.pebble[138227]: 2024-12-04T09:34:59.661Z [pebble] GET /v1/services?names=proxy 39.416µs 200
Dec 04 04:35:02 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=53554, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0))
Dec 04 04:35:02 RG-PT maas-regiond[138434]: RegionServer,45,::ffff:10.42.0.1: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=53554, flowInfo=0, scopeID=0))
Dec 04 04:35:02 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138434 lost burst connection to (‘10.42.0.1’, 5252).
Dec 04 04:35:02 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=53568, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0))
Dec 04 04:35:02 RG-PT maas-regiond[138434]: RegionServer,46,::ffff:10.42.0.1: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=53568, flowInfo=0, scopeID=0))
Dec 04 04:35:02 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138434 lost burst connection to (‘10.42.0.1’, 5252).
Dec 04 04:35:07 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:35:07 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:35:22 RG-PT maas-regiond[138434]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=51356, flowInfo=0, scopeID=0))
Dec 04 04:35:22 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=51356, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0))
Dec 04 04:35:22 RG-PT maas-regiond[138434]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=51370, flowInfo=0, scopeID=0))
Dec 04 04:35:22 RG-PT maas-regiond[138434]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=51386, flowInfo=0, scopeID=0))
Dec 04 04:35:22 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=51370, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0))
Dec 04 04:35:22 RG-PT maas-regiond[138434]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.1:51356’.
Dec 04 04:35:22 RG-PT maas-regiond[138434]: maasserver.rpc.regionservice: [info] Connection 1b057172-ad02-4f00-a3c9-a60f3325a7cc is trusted and ready to respond/serve commands.
Dec 04 04:35:22 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=51386, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0))
Dec 04 04:35:22 RG-PT maas.pebble[138227]: 2024-12-04T09:35:22.766Z [pebble] GET /v1/services?names=http 58.852µs 200
Dec 04 04:35:22 RG-PT maas.pebble[138227]: 2024-12-04T09:35:22.766Z [pebble] GET /v1/services?names=dhcpd 26.561µs 200
Dec 04 04:35:22 RG-PT maas.pebble[138227]: 2024-12-04T09:35:22.766Z [pebble] GET /v1/services?names=dhcpd6 37.452µs 200
Dec 04 04:35:22 RG-PT maas.pebble[138227]: 2024-12-04T09:35:22.766Z [pebble] GET /v1/services?names=agent 18.636µs 200
Dec 04 04:35:22 RG-PT maas-regiond[138434]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.1:51386’.
Dec 04 04:35:22 RG-PT maas-regiond[138434]: maasserver.rpc.regionservice: [info] Connection 22eb409c-7fb8-40f1-baaa-b62ebfa63c7e is trusted and ready to respond/serve commands.
Dec 04 04:35:22 RG-PT maas-regiond[138434]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.1:51370’.
Dec 04 04:35:22 RG-PT maas-regiond[138434]: maasserver.rpc.regionservice: [info] Connection 8282a3b9-e7c2-42ed-ae8a-bb9526b3a504 is trusted and ready to respond/serve commands.
Dec 04 04:35:22 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138434’ authenticated.
Dec 04 04:35:22 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138434’ authenticated.
Dec 04 04:35:22 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.
Dec 04 04:35:22 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138434 registered RPC connection to (‘q4tnrp’, ‘10.42.0.1’, 5252).
Dec 04 04:35:22 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138434’ authenticated.
Dec 04 04:35:23 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138434) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:35:23 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138434) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:35:23 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138434 registered RPC connection to (‘q4tnrp’, ‘10.42.0.1’, 5252).
Dec 04 04:35:23 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138434) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:35:23 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138434 registered RPC connection to (‘q4tnrp’, ‘10.42.0.1’, 5252).
Dec 04 04:35:29 RG-PT maas.pebble[138227]: 2024-12-04T09:35:29.651Z [pebble] GET /v1/services?names=bind9 59.945µs 200
Dec 04 04:35:29 RG-PT maas.pebble[138227]: 2024-12-04T09:35:29.651Z [pebble] GET /v1/services?names=ntp 59.584µs 200
Dec 04 04:35:29 RG-PT maas.pebble[138227]: 2024-12-04T09:35:29.651Z [pebble] GET /v1/services?names=temporal 32.823µs 200
Dec 04 04:35:29 RG-PT maas.pebble[138227]: 2024-12-04T09:35:29.651Z [pebble] GET /v1/services?names=http 58.111µs 200
Dec 04 04:35:29 RG-PT maas.pebble[138227]: 2024-12-04T09:35:29.651Z [pebble] GET /v1/services?names=temporal-worker 21.461µs 200
Dec 04 04:35:29 RG-PT maas.pebble[138227]: 2024-12-04T09:35:29.651Z [pebble] GET /v1/services?names=syslog 37.001µs 200
Dec 04 04:35:29 RG-PT maas.pebble[138227]: 2024-12-04T09:35:29.660Z [pebble] GET /v1/services?names=proxy 67.069µs 200
Dec 04 04:35:32 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=54010, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0))
Dec 04 04:35:32 RG-PT maas-regiond[138434]: RegionServer,47,::ffff:10.42.0.1: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=54010, flowInfo=0, scopeID=0))
Dec 04 04:35:32 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138434 lost burst connection to (‘10.42.0.1’, 5252).
Dec 04 04:35:32 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=54024, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0))
Dec 04 04:35:32 RG-PT maas-regiond[138434]: RegionServer,48,::ffff:10.42.0.1: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5252, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=54024, flowInfo=0, scopeID=0))
Dec 04 04:35:32 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138434 lost burst connection to (‘10.42.0.1’, 5252).
Dec 04 04:35:36 RG-PT maas-regiond[138431]: maasserver.regiondservices.active_discovery: [info] Active network discovery: Active scanning is not enabled on any subnet. Skipping periodic scan.
Dec 04 04:35:37 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: message repeated 2 times: [ [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.]
Dec 04 04:35:37 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:35:37 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:35:51 RG-PT maas-log[138571]: maas.neighbour: [info] ens192 (physical) on RG-PT: IP address 0.0.0.0 moved from 00:62:0b:1f:c3:e1 to 00:62:0b:1f:e5:01
Dec 04 04:35:52 RG-PT maas.pebble[138227]: 2024-12-04T09:35:52.752Z [pebble] GET /v1/services?names=dhcpd 53.883µs 200
Dec 04 04:35:52 RG-PT maas.pebble[138227]: 2024-12-04T09:35:52.752Z [pebble] GET /v1/services?names=dhcpd6 46.389µs 200
Dec 04 04:35:52 RG-PT maas.pebble[138227]: 2024-12-04T09:35:52.752Z [pebble] GET /v1/services?names=http 69.403µs 200
Dec 04 04:35:52 RG-PT maas.pebble[138227]: 2024-12-04T09:35:52.752Z [pebble] GET /v1/services?names=agent 105.402µs 200
Dec 04 04:35:59 RG-PT maas.pebble[138227]: 2024-12-04T09:35:59.648Z [pebble] GET /v1/services?names=temporal 64.112µs 200
Dec 04 04:35:59 RG-PT maas.pebble[138227]: 2024-12-04T09:35:59.648Z [pebble] GET /v1/services?names=syslog 72.679µs 200
Dec 04 04:35:59 RG-PT maas.pebble[138227]: 2024-12-04T09:35:59.648Z [pebble] GET /v1/services?names=bind9 38.233µs 200
Dec 04 04:35:59 RG-PT maas.pebble[138227]: 2024-12-04T09:35:59.648Z [pebble] GET /v1/services?names=temporal-worker 24.557µs 200
Dec 04 04:35:59 RG-PT maas.pebble[138227]: 2024-12-04T09:35:59.648Z [pebble] GET /v1/services?names=ntp 64.203µs 200
Dec 04 04:35:59 RG-PT maas.pebble[138227]: 2024-12-04T09:35:59.648Z [pebble] GET /v1/services?names=http 95.353µs 200
Dec 04 04:35:59 RG-PT maas.pebble[138227]: 2024-12-04T09:35:59.656Z [pebble] GET /v1/services?names=proxy 40.347µs 200
Dec 04 04:36:02 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=52988, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0))
Dec 04 04:36:02 RG-PT maas-regiond[138432]: RegionServer,44,::ffff:10.42.0.1: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=52988, flowInfo=0, scopeID=0))
Dec 04 04:36:02 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=52996, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0))
Dec 04 04:36:02 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138432 lost burst connection to (‘10.42.0.1’, 5251).
Dec 04 04:36:02 RG-PT maas-regiond[138432]: RegionServer,45,::ffff:10.42.0.1: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=52996, flowInfo=0, scopeID=0))
Dec 04 04:36:02 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138432 lost burst connection to (‘10.42.0.1’, 5251).
Dec 04 04:36:07 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:36:07 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:36:16 RG-PT maas-log[138571]: maas.neighbour: [info] ens192 (physical) on RG-PT: IP address 0.0.0.0 moved from 00:62:0b:1f:e5:01 to 00:62:0b:1f:c3:e1
Dec 04 04:36:22 RG-PT maas-regiond[138432]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=41834, flowInfo=0, scopeID=0))
Dec 04 04:36:22 RG-PT maas-regiond[138432]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=41842, flowInfo=0, scopeID=0))
Dec 04 04:36:22 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=41834, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0))
Dec 04 04:36:22 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=41842, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0))
Dec 04 04:36:22 RG-PT maas.pebble[138227]: 2024-12-04T09:36:22.753Z [pebble] GET /v1/services?names=http 54.805µs 200
Dec 04 04:36:22 RG-PT maas.pebble[138227]: 2024-12-04T09:36:22.753Z [pebble] GET /v1/services?names=dhcpd6 19.467µs 200
Dec 04 04:36:22 RG-PT maas.pebble[138227]: 2024-12-04T09:36:22.753Z [pebble] GET /v1/services?names=dhcpd 33.784µs 200
Dec 04 04:36:22 RG-PT maas.pebble[138227]: 2024-12-04T09:36:22.753Z [pebble] GET /v1/services?names=agent 68.541µs 200
Dec 04 04:36:22 RG-PT maas-regiond[138432]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.1:41842’.
Dec 04 04:36:22 RG-PT maas-regiond[138432]: maasserver.rpc.regionservice: [info] Connection 447da13f-6126-4efc-8556-7c95f90a6faf is trusted and ready to respond/serve commands.
Dec 04 04:36:22 RG-PT maas-regiond[138432]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.1:41834’.
Dec 04 04:36:22 RG-PT maas-regiond[138432]: maasserver.rpc.regionservice: [info] Connection 919985b5-cd09-4689-beca-d4a239178d7f is trusted and ready to respond/serve commands.
Dec 04 04:36:22 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138432’ authenticated.
Dec 04 04:36:22 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138432’ authenticated.
Dec 04 04:36:22 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.
Dec 04 04:36:22 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138432 registered RPC connection to (‘q4tnrp’, ‘10.42.0.1’, 5251).
Dec 04 04:36:23 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138432) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:36:23 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138432) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:36:23 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138432 registered RPC connection to (‘q4tnrp’, ‘10.42.0.1’, 5251).
Dec 04 04:36:29 RG-PT maas.pebble[138227]: 2024-12-04T09:36:29.648Z [pebble] GET /v1/services?names=ntp 57.74µs 200
Dec 04 04:36:29 RG-PT maas.pebble[138227]: 2024-12-04T09:36:29.648Z [pebble] GET /v1/services?names=bind9 69.422µs 200
Dec 04 04:36:29 RG-PT maas.pebble[138227]: 2024-12-04T09:36:29.648Z [pebble] GET /v1/services?names=temporal-worker 38.083µs 200
Dec 04 04:36:29 RG-PT maas.pebble[138227]: 2024-12-04T09:36:29.649Z [pebble] GET /v1/services?names=http 33.705µs 200
Dec 04 04:36:29 RG-PT maas.pebble[138227]: 2024-12-04T09:36:29.649Z [pebble] GET /v1/services?names=syslog 20.189µs 200
Dec 04 04:36:29 RG-PT maas.pebble[138227]: 2024-12-04T09:36:29.649Z [pebble] GET /v1/services?names=temporal 36.51µs 200
Dec 04 04:36:29 RG-PT maas.pebble[138227]: 2024-12-04T09:36:29.659Z [pebble] GET /v1/services?names=proxy 35.047µs 200
Dec 04 04:36:32 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=35236, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0))
Dec 04 04:36:32 RG-PT maas-regiond[138432]: RegionServer,46,::ffff:10.42.0.1: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=35236, flowInfo=0, scopeID=0))
Dec 04 04:36:32 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138432 lost burst connection to (‘10.42.0.1’, 5251).
Dec 04 04:36:32 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=35240, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0))
Dec 04 04:36:32 RG-PT maas-regiond[138432]: RegionServer,47,::ffff:10.42.0.1: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=35240, flowInfo=0, scopeID=0))
Dec 04 04:36:32 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138432 lost burst connection to (‘10.42.0.1’, 5251).
Dec 04 04:36:37 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.
Dec 04 04:36:37 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:36:37 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:36:52 RG-PT maas-regiond[138432]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=55332, flowInfo=0, scopeID=0))
Dec 04 04:36:52 RG-PT maas-regiond[138432]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=55340, flowInfo=0, scopeID=0))
Dec 04 04:36:52 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=55332, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0))
Dec 04 04:36:52 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=55340, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5251, flowInfo=0, scopeID=0))
Dec 04 04:36:52 RG-PT maas-regiond[138432]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.1:55332’.
Dec 04 04:36:52 RG-PT maas-regiond[138432]: maasserver.rpc.regionservice: [info] Connection 9141f0e7-24b4-4a81-9d00-3af818c1b784 is trusted and ready to respond/serve commands.
Dec 04 04:36:52 RG-PT maas-regiond[138432]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.1:55340’.
Dec 04 04:36:52 RG-PT maas-regiond[138432]: maasserver.rpc.regionservice: [info] Connection c6905a11-5e05-46e5-a8c1-6fd79eed6c6f is trusted and ready to respond/serve commands.
Dec 04 04:36:52 RG-PT maas.pebble[138227]: 2024-12-04T09:36:52.759Z [pebble] GET /v1/services?names=http 90.123µs 200
Dec 04 04:36:52 RG-PT maas.pebble[138227]: 2024-12-04T09:36:52.759Z [pebble] GET /v1/services?names=agent 27.282µs 200
Dec 04 04:36:52 RG-PT maas.pebble[138227]: 2024-12-04T09:36:52.759Z [pebble] GET /v1/services?names=dhcpd6 33.935µs 200
Dec 04 04:36:52 RG-PT maas.pebble[138227]: 2024-12-04T09:36:52.759Z [pebble] GET /v1/services?names=dhcpd 50.877µs 200
Dec 04 04:36:52 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138432’ authenticated.
Dec 04 04:36:52 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138432’ authenticated.
Dec 04 04:36:52 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.
Dec 04 04:36:52 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138432 registered RPC connection to (‘q4tnrp’, ‘10.42.0.1’, 5251).
Dec 04 04:36:52 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138432) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:36:53 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138432) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:36:53 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138432 registered RPC connection to (‘q4tnrp’, ‘10.42.0.1’, 5251).
Dec 04 04:36:59 RG-PT maas.pebble[138227]: 2024-12-04T09:36:59.647Z [pebble] GET /v1/services?names=bind9 66.948µs 200
Dec 04 04:36:59 RG-PT maas.pebble[138227]: 2024-12-04T09:36:59.647Z [pebble] GET /v1/services?names=http 17.132µs 200
Dec 04 04:36:59 RG-PT maas.pebble[138227]: 2024-12-04T09:36:59.647Z [pebble] GET /v1/services?names=ntp 35.147µs 200
Dec 04 04:36:59 RG-PT maas.pebble[138227]: 2024-12-04T09:36:59.647Z [pebble] GET /v1/services?names=syslog 37.081µs 200
Dec 04 04:36:59 RG-PT maas.pebble[138227]: 2024-12-04T09:36:59.647Z [pebble] GET /v1/services?names=temporal-worker 20.469µs 200
Dec 04 04:36:59 RG-PT maas.pebble[138227]: 2024-12-04T09:36:59.647Z [pebble] GET /v1/services?names=temporal 18.485µs 200
Dec 04 04:36:59 RG-PT maas.pebble[138227]: 2024-12-04T09:36:59.652Z [pebble] GET /v1/services?names=proxy 46.8µs 200
Dec 04 04:37:02 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=48044, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0))
Dec 04 04:37:02 RG-PT maas-regiond[138433]: RegionServer,46,::ffff:10.42.0.1: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=48044, flowInfo=0, scopeID=0))
Dec 04 04:37:02 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138433 lost burst connection to (‘10.42.0.1’, 5253).
Dec 04 04:37:02 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=48058, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0))
Dec 04 04:37:02 RG-PT maas-regiond[138433]: RegionServer,47,::ffff:10.42.0.1: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=48058, flowInfo=0, scopeID=0))
Dec 04 04:37:02 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138433 lost burst connection to (‘10.42.0.1’, 5253).
Dec 04 04:37:02 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=48064, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0))
Dec 04 04:37:02 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=48066, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0))
Dec 04 04:37:02 RG-PT maas-regiond[138433]: RegionServer,48,::ffff:10.42.0.1: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=48064, flowInfo=0, scopeID=0))
Dec 04 04:37:02 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138433 lost burst connection to (‘10.42.0.1’, 5253).
Dec 04 04:37:02 RG-PT maas-regiond[138433]: RegionServer,49,::ffff:10.42.0.1: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=48066, flowInfo=0, scopeID=0))
Dec 04 04:37:02 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138433 lost burst connection to (‘10.42.0.1’, 5253).
Dec 04 04:37:06 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.
Dec 04 04:37:06 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:37:06 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:37:22 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=51816, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0))
Dec 04 04:37:22 RG-PT maas-regiond[138433]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=51816, flowInfo=0, scopeID=0))
Dec 04 04:37:22 RG-PT maas-regiond[138433]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=51830, flowInfo=0, scopeID=0))
Dec 04 04:37:22 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=51830, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0))
Dec 04 04:37:22 RG-PT maas-regiond[138433]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.1:51816’.
Dec 04 04:37:22 RG-PT maas-regiond[138433]: maasserver.rpc.regionservice: [info] Connection 26b98a83-84db-4ac8-bc09-fb33ffab7a75 is trusted and ready to respond/serve commands.
Dec 04 04:37:22 RG-PT maas.pebble[138227]: 2024-12-04T09:37:22.781Z [pebble] GET /v1/services?names=dhcpd6 58.742µs 200
Dec 04 04:37:22 RG-PT maas.pebble[138227]: 2024-12-04T09:37:22.781Z [pebble] GET /v1/services?names=http 51.599µs 200
Dec 04 04:37:22 RG-PT maas.pebble[138227]: 2024-12-04T09:37:22.781Z [pebble] GET /v1/services?names=dhcpd 59.353µs 200
Dec 04 04:37:22 RG-PT maas.pebble[138227]: 2024-12-04T09:37:22.781Z [pebble] GET /v1/services?names=agent 20.99µs 200
Dec 04 04:37:22 RG-PT maas-regiond[138433]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.1:51830’.
Dec 04 04:37:22 RG-PT maas-regiond[138433]: maasserver.rpc.regionservice: [info] Connection 4265af4a-bd3b-4894-b3f0-882cf9c5eedf is trusted and ready to respond/serve commands.
Dec 04 04:37:22 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138433’ authenticated.
Dec 04 04:37:22 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138433’ authenticated.
Dec 04 04:37:22 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.
Dec 04 04:37:22 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138433 registered RPC connection to (‘q4tnrp’, ‘10.42.0.1’, 5253).
Dec 04 04:37:23 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138433) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:37:23 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138433) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:37:23 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138433 registered RPC connection to (‘q4tnrp’, ‘10.42.0.1’, 5253).
Dec 04 04:37:26 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.
Dec 04 04:37:26 RG-PT maas-log[138571]: maas.neighbour: [info] ens192 (physical) on RG-PT: IP address 0.0.0.0 moved from 00:62:0b:1f:c3:e1 to 00:62:0b:1f:e5:00
Dec 04 04:37:29 RG-PT maas.pebble[138227]: 2024-12-04T09:37:29.649Z [pebble] GET /v1/services?names=bind9 63.892µs 200
Dec 04 04:37:29 RG-PT maas.pebble[138227]: 2024-12-04T09:37:29.649Z [pebble] GET /v1/services?names=temporal 32.342µs 200
Dec 04 04:37:29 RG-PT maas.pebble[138227]: 2024-12-04T09:37:29.649Z [pebble] GET /v1/services?names=syslog 84.261µs 200
Dec 04 04:37:29 RG-PT maas.pebble[138227]: 2024-12-04T09:37:29.649Z [pebble] GET /v1/services?names=http 29.867µs 200
Dec 04 04:37:29 RG-PT maas.pebble[138227]: 2024-12-04T09:37:29.650Z [pebble] GET /v1/services?names=ntp 75.985µs 200
Dec 04 04:37:29 RG-PT maas.pebble[138227]: 2024-12-04T09:37:29.650Z [pebble] GET /v1/services?names=temporal-worker 19.257µs 200
Dec 04 04:37:29 RG-PT maas.pebble[138227]: 2024-12-04T09:37:29.656Z [pebble] GET /v1/services?names=proxy 45.387µs 200
Dec 04 04:37:32 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:37:32 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:37:35 RG-PT maas-log[138571]: maas.neighbour: [info] ens192 (physical) on RG-PT: IP address 0.0.0.0 moved from 00:62:0b:1f:e5:00 to 00:15:5d:5c:25:02
Dec 04 04:37:38 RG-PT maas-log[138571]: maas.neighbour: [info] ens192 (physical) on RG-PT: IP address 172.25.92.61 moved from 00:62:0b:1f:c3:e0 to 00:15:5d:5c:25:02
Dec 04 04:37:52 RG-PT maas-regiond[138433]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=32832, flowInfo=0, scopeID=0))
Dec 04 04:37:52 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=32832, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0))
Dec 04 04:37:52 RG-PT maas-regiond[138433]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=32846, flowInfo=0, scopeID=0))
Dec 04 04:37:52 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=32846, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.1’, port=5253, flowInfo=0, scopeID=0))
Dec 04 04:37:52 RG-PT maas.pebble[138227]: 2024-12-04T09:37:52.752Z [pebble] GET /v1/services?names=http 68.752µs 200
Dec 04 04:37:52 RG-PT maas.pebble[138227]: 2024-12-04T09:37:52.752Z [pebble] GET /v1/services?names=dhcpd 37.572µs 200
Dec 04 04:37:52 RG-PT maas.pebble[138227]: 2024-12-04T09:37:52.752Z [pebble] GET /v1/services?names=agent 18.776µs 200
Dec 04 04:37:52 RG-PT maas.pebble[138227]: 2024-12-04T09:37:52.752Z [pebble] GET /v1/services?names=dhcpd6 23.094µs 200
Dec 04 04:37:52 RG-PT maas-regiond[138433]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.1:32832’.
Dec 04 04:37:52 RG-PT maas-regiond[138433]: maasserver.rpc.regionservice: [info] Connection e605a975-89b2-49d8-946b-8e60a1ef9d18 is trusted and ready to respond/serve commands.
Dec 04 04:37:52 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138433’ authenticated.
Dec 04 04:37:52 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138433’ authenticated.
Dec 04 04:37:52 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.
Dec 04 04:37:52 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138433 registered RPC connection to (‘q4tnrp’, ‘10.42.0.1’, 5253).
Dec 04 04:37:52 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138433) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:37:52 RG-PT maas-regiond[138433]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.1:32846’.
Dec 04 04:37:52 RG-PT maas-regiond[138433]: maasserver.rpc.regionservice: [info] Connection 98e66a3b-9f89-4617-8ce6-56e9a39a54c5 is trusted and ready to respond/serve commands.
Dec 04 04:37:53 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138433) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:37:53 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138433 registered RPC connection to (‘q4tnrp’, ‘10.42.0.1’, 5253).
Dec 04 04:37:59 RG-PT maas.pebble[138227]: 2024-12-04T09:37:59.646Z [pebble] GET /v1/services?names=bind9 66.567µs 200
Dec 04 04:37:59 RG-PT maas.pebble[138227]: 2024-12-04T09:37:59.646Z [pebble] GET /v1/services?names=http 19.848µs 200
Dec 04 04:37:59 RG-PT maas.pebble[138227]: 2024-12-04T09:37:59.646Z [pebble] GET /v1/services?names=syslog 31.821µs 200
Dec 04 04:37:59 RG-PT maas.pebble[138227]: 2024-12-04T09:37:59.646Z [pebble] GET /v1/services?names=ntp 19.136µs 200
Dec 04 04:37:59 RG-PT maas.pebble[138227]: 2024-12-04T09:37:59.646Z [pebble] GET /v1/services?names=temporal-worker 14.588µs 200
Dec 04 04:37:59 RG-PT maas.pebble[138227]: 2024-12-04T09:37:59.646Z [pebble] GET /v1/services?names=temporal 29.897µs 200
Dec 04 04:37:59 RG-PT maas.pebble[138227]: 2024-12-04T09:37:59.653Z [pebble] GET /v1/services?names=proxy 46.579µs 200
Dec 04 04:38:02 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=57858, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0))
Dec 04 04:38:02 RG-PT maas-regiond[138431]: RegionServer,44,::ffff:10.42.0.0: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=57858, flowInfo=0, scopeID=0))
Dec 04 04:38:02 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138431 lost burst connection to (‘10.42.0.0’, 5250).
Dec 04 04:38:02 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=57860, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0))
Dec 04 04:38:02 RG-PT maas-regiond[138431]: RegionServer,45,::ffff:10.42.0.0: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=57860, flowInfo=0, scopeID=0))
Dec 04 04:38:02 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138431 lost burst connection to (‘10.42.0.0’, 5250).
Dec 04 04:38:07 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.
Dec 04 04:38:07 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:38:07 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:38:22 RG-PT maas-regiond[138431]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=35676, flowInfo=0, scopeID=0))
Dec 04 04:38:22 RG-PT maas-regiond[138431]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=35688, flowInfo=0, scopeID=0))
Dec 04 04:38:22 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=35676, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0))
Dec 04 04:38:22 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=35688, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0))
Dec 04 04:38:22 RG-PT maas.pebble[138227]: 2024-12-04T09:38:22.753Z [pebble] GET /v1/services?names=dhcpd6 37.021µs 200
Dec 04 04:38:22 RG-PT maas.pebble[138227]: 2024-12-04T09:38:22.753Z [pebble] GET /v1/services?names=agent 58.322µs 200
Dec 04 04:38:22 RG-PT maas.pebble[138227]: 2024-12-04T09:38:22.753Z [pebble] GET /v1/services?names=dhcpd 70.975µs 200
Dec 04 04:38:22 RG-PT maas.pebble[138227]: 2024-12-04T09:38:22.753Z [pebble] GET /v1/services?names=http 39.035µs 200
Dec 04 04:38:22 RG-PT maas-regiond[138431]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.0:35676’.
Dec 04 04:38:22 RG-PT maas-regiond[138431]: maasserver.rpc.regionservice: [info] Connection 3ca6996c-bb60-4b55-9746-917c4a113ccb is trusted and ready to respond/serve commands.
Dec 04 04:38:22 RG-PT maas-regiond[138431]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.0:35688’.
Dec 04 04:38:22 RG-PT maas-regiond[138431]: maasserver.rpc.regionservice: [info] Connection 9ac1c698-fc49-4f23-bd9e-79deb5a78274 is trusted and ready to respond/serve commands.
Dec 04 04:38:22 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138431’ authenticated.
Dec 04 04:38:22 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138431’ authenticated.
Dec 04 04:38:22 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.
Dec 04 04:38:22 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138431 registered RPC connection to (‘q4tnrp’, ‘10.42.0.0’, 5250).
Dec 04 04:38:22 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138431) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:38:23 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138431) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:38:23 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138431 registered RPC connection to (‘q4tnrp’, ‘10.42.0.0’, 5250).
Dec 04 04:38:29 RG-PT maas.pebble[138227]: 2024-12-04T09:38:29.648Z [pebble] GET /v1/services?names=bind9 74.202µs 200
Dec 04 04:38:29 RG-PT maas.pebble[138227]: 2024-12-04T09:38:29.648Z [pebble] GET /v1/services?names=ntp 88.279µs 200
Dec 04 04:38:29 RG-PT maas.pebble[138227]: 2024-12-04T09:38:29.648Z [pebble] GET /v1/services?names=temporal-worker 25.849µs 200
Dec 04 04:38:29 RG-PT maas.pebble[138227]: 2024-12-04T09:38:29.648Z [pebble] GET /v1/services?names=syslog 28.204µs 200
Dec 04 04:38:29 RG-PT maas.pebble[138227]: 2024-12-04T09:38:29.648Z [pebble] GET /v1/services?names=http 36.791µs 200
Dec 04 04:38:29 RG-PT maas.pebble[138227]: 2024-12-04T09:38:29.648Z [pebble] GET /v1/services?names=temporal 71.527µs 200
Dec 04 04:38:29 RG-PT maas.pebble[138227]: 2024-12-04T09:38:29.656Z [pebble] GET /v1/services?names=proxy 51.388µs 200
Dec 04 04:38:32 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=53402, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0))
Dec 04 04:38:32 RG-PT maas-regiond[138431]: RegionServer,46,::ffff:10.42.0.0: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=53402, flowInfo=0, scopeID=0))
Dec 04 04:38:32 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138431 lost burst connection to (‘10.42.0.0’, 5250).
Dec 04 04:38:32 RG-PT maas-rackd[138284]: ClusterClient,client: [info] ClusterClient connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=53412, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0))
Dec 04 04:38:32 RG-PT maas-regiond[138431]: RegionServer,47,::ffff:10.42.0.0: [info] RegionServer connection lost (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=53412, flowInfo=0, scopeID=0))
Dec 04 04:38:32 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138431 lost burst connection to (‘10.42.0.0’, 5250).
Dec 04 04:38:37 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.
Dec 04 04:38:37 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:38:37 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:38:42 RG-PT maas-log[138571]: maas.neighbour: [info] ens192 (physical) on RG-PT: IP address 172.25.92.62 moved from 02:ec:5c:25:00:00 to 00:15:5d:5c:25:02
Dec 04 04:38:52 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=38090, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0))
Dec 04 04:38:52 RG-PT maas-regiond[138431]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=38090, flowInfo=0, scopeID=0))
Dec 04 04:38:52 RG-PT maas-rackd[138284]: Uninitialized: [info] ClusterClient connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=38104, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0))
Dec 04 04:38:52 RG-PT maas.pebble[138227]: 2024-12-04T09:38:52.751Z [pebble] GET /v1/services?names=http 83.5µs 200
Dec 04 04:38:52 RG-PT maas.pebble[138227]: 2024-12-04T09:38:52.751Z [pebble] GET /v1/services?names=dhcpd 58.452µs 200
Dec 04 04:38:52 RG-PT maas.pebble[138227]: 2024-12-04T09:38:52.751Z [pebble] GET /v1/services?names=dhcpd6 62.439µs 200
Dec 04 04:38:52 RG-PT maas.pebble[138227]: 2024-12-04T09:38:52.751Z [pebble] GET /v1/services?names=agent 27.823µs 200
Dec 04 04:38:52 RG-PT maas-regiond[138431]: twisted.internet.protocol.Factory: [info] RegionServer connection established (HOST:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=5250, flowInfo=0, scopeID=0) PEER:IPv6Address(type=‘TCP’, host=‘::ffff:10.42.0.0’, port=38104, flowInfo=0, scopeID=0))
Dec 04 04:38:52 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138431’ authenticated.
Dec 04 04:38:52 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Event-loop ‘RG-PT:pid=138431’ authenticated.
Dec 04 04:38:53 RG-PT maas-regiond[138431]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.0:38104’.
Dec 04 04:38:53 RG-PT maas-regiond[138431]: maasserver.rpc.regionservice: [info] Connection 797339db-ee3d-4ab8-ad3e-fe8ff2da6958 is trusted and ready to respond/serve commands.
Dec 04 04:38:53 RG-PT maas-regiond[138431]: maasserver.rpc.regionservice: [info] Rack controller authenticated from ‘::ffff:10.42.0.0:38090’.
Dec 04 04:38:53 RG-PT maas-regiond[138431]: maasserver.rpc.regionservice: [info] Connection d8e7f184-d73b-4d52-bb00-e682f53d5cbb is trusted and ready to respond/serve commands.
Dec 04 04:38:53 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.
Dec 04 04:38:53 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138431) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:38:53 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138431 registered RPC connection to (‘q4tnrp’, ‘10.42.0.0’, 5250).
Dec 04 04:38:53 RG-PT maas-rackd[138284]: provisioningserver.rpc.clusterservice: [info] Rack controller ‘q4tnrp’ registered (via RG-PT:pid=138431) with MAAS version 3.5.2-16329-g.a0861379f.
Dec 04 04:38:53 RG-PT maas-regiond[138275]: maasserver.ipc: [info] Worker pid:138431 registered RPC connection to (‘q4tnrp’, ‘10.42.0.0’, 5250).
Dec 04 04:38:59 RG-PT maas.pebble[138227]: 2024-12-04T09:38:59.647Z [pebble] GET /v1/services?names=bind9 58.562µs 200
Dec 04 04:38:59 RG-PT maas.pebble[138227]: 2024-12-04T09:38:59.647Z [pebble] GET /v1/services?names=ntp 63.271µs 200
Dec 04 04:38:59 RG-PT maas.pebble[138227]: 2024-12-04T09:38:59.647Z [pebble] GET /v1/services?names=http 68.25µs 200
Dec 04 04:38:59 RG-PT maas.pebble[138227]: 2024-12-04T09:38:59.647Z [pebble] GET /v1/services?names=syslog 29.386µs 200
Dec 04 04:38:59 RG-PT maas.pebble[138227]: 2024-12-04T09:38:59.647Z [pebble] GET /v1/services?names=temporal 20.229µs 200
Dec 04 04:38:59 RG-PT maas.pebble[138227]: 2024-12-04T09:38:59.647Z [pebble] GET /v1/services?names=temporal-worker 36.529µs 200
Dec 04 04:38:59 RG-PT maas.pebble[138227]: 2024-12-04T09:38:59.656Z [pebble] GET /v1/services?names=proxy 27.692µs 200
Dec 04 04:39:02 RG-PT maas-log[138571]: maas.rpc.rackcontrollers: [info] Existing rack controller ‘RG-PT’ running version 3.5.2-16329-g.a0861379f has connected to region ‘RG-PT’.
Dec 04 04:39:02 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:39:02 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:39:22 RG-PT maas.pebble[138227]: 2024-12-04T09:39:22.751Z [pebble] GET /v1/services?names=http 72.259µs 200
Dec 04 04:39:22 RG-PT maas.pebble[138227]: 2024-12-04T09:39:22.752Z [pebble] GET /v1/services?names=dhcpd 59.353µs 200
Dec 04 04:39:22 RG-PT maas.pebble[138227]: 2024-12-04T09:39:22.752Z [pebble] GET /v1/services?names=agent 33.534µs 200
Dec 04 04:39:22 RG-PT maas.pebble[138227]: 2024-12-04T09:39:22.752Z [pebble] GET /v1/services?names=dhcpd6 35.609µs 200
Dec 04 04:39:29 RG-PT maas.pebble[138227]: 2024-12-04T09:39:29.649Z [pebble] GET /v1/services?names=bind9 54.414µs 200
Dec 04 04:39:29 RG-PT maas.pebble[138227]: 2024-12-04T09:39:29.649Z [pebble] GET /v1/services?names=http 19.507µs 200
Dec 04 04:39:29 RG-PT maas.pebble[138227]: 2024-12-04T09:39:29.649Z [pebble] GET /v1/services?names=ntp 31.41µs 200
Dec 04 04:39:29 RG-PT maas.pebble[138227]: 2024-12-04T09:39:29.650Z [pebble] GET /v1/services?names=syslog 65.365µs 200
Dec 04 04:39:29 RG-PT maas.pebble[138227]: 2024-12-04T09:39:29.650Z [pebble] GET /v1/services?names=temporal-worker 20.239µs 200
Dec 04 04:39:29 RG-PT maas.pebble[138227]: 2024-12-04T09:39:29.650Z [pebble] GET /v1/services?names=temporal 24.887µs 200
Dec 04 04:39:29 RG-PT maas.pebble[138227]: 2024-12-04T09:39:29.657Z [pebble] GET /v1/services?names=proxy 33.123µs 200
Dec 04 04:39:36 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:39:36 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”
Dec 04 04:39:43 RG-PT maas-log[138571]: maas.neighbour: [info] ens192 (physical) on RG-PT: IP address 172.25.92.63 moved from 02:ec:5c:25:00:00 to 00:15:5d:5c:25:02
Dec 04 04:39:52 RG-PT maas.pebble[138227]: 2024-12-04T09:39:52.750Z [pebble] GET /v1/services?names=http 171.467µs 200
Dec 04 04:39:52 RG-PT maas.pebble[138227]: 2024-12-04T09:39:52.750Z [pebble] GET /v1/services?names=agent 64.994µs 200
Dec 04 04:39:52 RG-PT maas.pebble[138227]: 2024-12-04T09:39:52.750Z [pebble] GET /v1/services?names=dhcpd6 60.255µs 200
Dec 04 04:39:52 RG-PT maas.pebble[138227]: 2024-12-04T09:39:52.750Z [pebble] GET /v1/services?names=dhcpd 72.418µs 200
Dec 04 04:39:59 RG-PT maas.pebble[138227]: 2024-12-04T09:39:59.646Z [pebble] GET /v1/services?names=bind9 55.887µs 200
Dec 04 04:39:59 RG-PT maas.pebble[138227]: 2024-12-04T09:39:59.646Z [pebble] GET /v1/services?names=syslog 37.161µs 200
Dec 04 04:39:59 RG-PT maas.pebble[138227]: 2024-12-04T09:39:59.646Z [pebble] GET /v1/services?names=ntp 45.437µs 200
Dec 04 04:39:59 RG-PT maas.pebble[138227]: 2024-12-04T09:39:59.646Z [pebble] GET /v1/services?names=temporal-worker 22.763µs 200
Dec 04 04:39:59 RG-PT maas.pebble[138227]: 2024-12-04T09:39:59.646Z [pebble] GET /v1/services?names=http 19.126µs 200
Dec 04 04:39:59 RG-PT maas.pebble[138227]: 2024-12-04T09:39:59.647Z [pebble] GET /v1/services?names=temporal 67.98µs 200
Dec 04 04:39:59 RG-PT maas.pebble[138227]: 2024-12-04T09:39:59.655Z [pebble] GET /v1/services?names=proxy 31.45µs 200
Dec 04 04:40:02 RG-PT maas-http[138571]: 172.25.92.166 - - [04/Dec/2024:09:40:02 +0000] “GET /MAAS/rpc/ HTTP/1.1” 200 372 “-” “provisioningserver.rpc.clusterservice.ClusterClientService”

prantiknag · 4 December 2024 11:00

Dec 04 05:58:59 RG-PT maas-temporal[138440]: {“level”:“error”,“ts”:“2024-12-04T10:58:59.253Z”,“msg”:“Operation failed with internal error.”,“error”:“UpdateTaskQueue failed. Failed to start transaction. Error: context canceled”,“operation”:“UpdateTaskQueue”,“logging-call-at”:“persistence_metric_clients.go:1281”,“stacktrace”:“go.temporal.io/server/common/log.(*zapLogger).Error\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/log/zap_logger.go:156\ngo.temporal.io/server/common/persistence.updateErrorMetric\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/persistence/persistence_metric_clients.go:1281\ngo.temporal.io/server/common/persistence.(*metricEmitter).recordRequestMetrics\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/persistence/persistence_metric_clients.go:1258\ngo.temporal.io/server/common/persistence.(*taskPersistenceClient).UpdateTaskQueue.func1\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/persistence/persistence_metric_clients.go:609\ngo.temporal.io/server/common/persistence.(*taskPersistenceClient).UpdateTaskQueue\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/persistence/persistence_metric_clients.go:611\ngo.temporal.io/server/common/persistence.(*taskRetryablePersistenceClient).UpdateTaskQueue.func1\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/persistence/persistence_retryable_clients.go:730\ngo.temporal.io/server/common/backoff.ThrottleRetryContext\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/backoff/retry.go:145\ngo.temporal.io/server/common/persistence.(*taskRetryablePersistenceClient).UpdateTaskQueue\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/persistence/persistence_retryable_clients.go:734\ngo.temporal.io/server/service/matching.(*taskQueueDB).UpdateState\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/service/matching/db.go:225\ngo.temporal.io/server/service/matching.(*taskReader).persistAckLevel\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/service/matching/task_reader.go:313\ngo.temporal.io/server/service/matching.(*taskReader).getTasksPump\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/service/matching/task_reader.go:211\ngo.temporal.io/server/internal/goro.(*Group).Go.func1\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/internal/goro/group.go:58”}
Dec 04 05:58:59 RG-PT maas-temporal[138440]: {“level”:“error”,“ts”:“2024-12-04T10:58:59.253Z”,“msg”:“Persistent store operation failure”,“service”:“matching”,“component”:“matching-engine”,“wf-task-queue-name”:“/_sys/region/3”,“wf-task-queue-type”:“Workflow”,“wf-namespace”:“default”,“store-operation”:“update-task-queue”,“error”:“UpdateTaskQueue failed. Failed to start transaction. Error: context canceled”,“logging-call-at”:“task_reader.go:214”,“stacktrace”:“go.temporal.io/server/common/log.(*zapLogger).Error\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/log/zap_logger.go:156\ngo.temporal.io/server/service/matching.(*taskReader).getTasksPump\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/service/matching/task_reader.go:214\ngo.temporal.io/server/internal/goro.(*Group).Go.func1\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/internal/goro/group.go:58”}
Dec 04 05:58:59 RG-PT maas.pebble[138227]: 2024-12-04T10:58:59.646Z [pebble] GET /v1/services?names=bind9 55.537µs 200
Dec 04 05:58:59 RG-PT maas.pebble[138227]: 2024-12-04T10:58:59.646Z [pebble] GET /v1/services?names=ntp 37.642µs 200
Dec 04 05:58:59 RG-PT maas.pebble[138227]: 2024-12-04T10:58:59.646Z [pebble] GET /v1/services?names=http 44.746µs 200
Dec 04 05:58:59 RG-PT maas.pebble[138227]: 2024-12-04T10:58:59.646Z [pebble] GET /v1/services?names=syslog 37.782µs 200
Dec 04 05:58:59 RG-PT maas.pebble[138227]: 2024-12-04T10:58:59.646Z [pebble] GET /v1/services?names=temporal 36.64µs 200
Dec 04 05:58:59 RG-PT maas.pebble[138227]: 2024-12-04T10:58:59.646Z [pebble] GET /v1/services?names=temporal-worker 45.667µs 200
Dec 04 05:58:59 RG-PT maas.pebble[138227]: 2024-12-04T10:58:59.652Z [pebble] GET /v1/services?names=proxy 95.513µs 200

r00ta · 4 December 2024 11:26

I suspect these are not the full logs so we are missing the actual failures.

Please stop/start the importing job in the UI and then extract the logs again. Then upload them here https://pastebin.ubuntu.com/

prantiknag · 4 December 2024 12:37

Unable to upload logs in tat url, giving gateway timeout

r00ta · 4 December 2024 12:41

you can use any other online tool such as gdrive or wetransfer

prantiknag · 4 December 2024 12:49

Please download it from this link
https://www.transfernow.net/dl/20241204JK85Lys9

prantiknag · 5 December 2024 04:08

While set the local-mirror url as boot source, I am getting the following error in without internet canonical-maas environment.

Dec 04 23:01:39 RG-PT maas-temporal[254632]: {“level”:“error”,“ts”:“2024-12-05T04:01:39.503Z”,“msg”:“Operation failed with an error.”,“error”:“context deadline exceeded”,“logging-call-at”:“visiblity_manager_metrics.go:264”,“stacktrace”:“go.temporal.io/server/common/log.(*zapLogger).Error\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/log/zap_logger.go:156\ngo.temporal.io/server/common/persistence/visibility.(*visibilityManagerMetrics).updateErrorMetric\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/persistence/visibility/visiblity_manager_metrics.go:264\ngo.temporal.io/server/common/persistence/visibility.(*visibilityManagerMetrics).RecordWorkflowExecutionStarted\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/persistence/visibility/visiblity_manager_metrics.go:98\ngo.temporal.io/server/service/history.(*visibilityQueueTaskExecutor).recordStartExecution\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/service/history/visibility_queue_task_executor.go:290\ngo.temporal.io/server/service/history.(*visibilityQueueTaskExecutor).processStartExecution\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/service/history/visibility_queue_task_executor.go:179\ngo.temporal.io/server/service/history.(*visibilityQueueTaskExecutor).Execute\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/service/history/visibility_queue_task_executor.go:116\ngo.temporal.io/server/service/history/queues.(*executableImpl).Execute\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/service/history/queues/executable.go:243\ngo.temporal.io/server/common/tasks.(*FIFOScheduler[…]).executeTask.func1\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/tasks/fifo_scheduler.go:223\ngo.temporal.io/server/common/backoff.ThrottleRetry.func1\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/backoff/retry.go:119\ngo.temporal.io/server/common/backoff.ThrottleRetryContext\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/backoff/retry.go:145\ngo.temporal.io/server/common/backoff.ThrottleRetry\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/backoff/retry.go:120\ngo.temporal.io/server/common/tasks.(*FIFOScheduler[…]).executeTask\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/tasks/fifo_scheduler.go:233\ngo.temporal.io/server/common/tasks.(*FIFOScheduler[…]).processTask\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/tasks/fifo_scheduler.go:211”}
Dec 04 23:01:39 RG-PT maas-temporal[254632]: {“level”:“error”,“ts”:“2024-12-05T04:01:39.503Z”,“msg”:“Fail to process task”,“shard-id”:1,“address”:“172.25.92.166:5273”,“component”:“visibility-queue-processor”,“wf-namespace-id”:“6b23c1fa-1d94-4a18-aa5e-f031a5a83586”,“wf-id”:“sync-boot-resources:streams”,“wf-run-id”:“f7f16b1a-4cf9-47f9-b2a4-de5dc0491543”,“queue-task-id”:3145939,“queue-task-visibility-timestamp”:“2024-12-05T03:29:41.299Z”,“queue-task-type”:“VisibilityStartExecution”,“queue-task”:{“NamespaceID”:“6b23c1fa-1d94-4a18-aa5e-f031a5a83586”,“WorkflowID”:“sync-boot-resources:streams”,“RunID”:“f7f16b1a-4cf9-47f9-b2a4-de5dc0491543”,“VisibilityTimestamp”:“2024-12-05T03:29:41.299243793Z”,“TaskID”:3145939,“Version”:0},“wf-history-event-id”:0,“error”:“context deadline exceeded”,“lifecycle”:“ProcessingFailed”,“logging-call-at”:“lazy_logger.go:68”,“stacktrace”:“go.temporal.io/server/common/log.(*zapLogger).Error\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/log/zap_logger.go:156\ngo.temporal.io/server/common/log.(*lazyLogger).Error\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/log/lazy_logger.go:68\ngo.temporal.io/server/service/history/queues.(*executableImpl).HandleErr\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/service/history/queues/executable.go:361\ngo.temporal.io/server/common/tasks.(*FIFOScheduler[…]).executeTask.func1\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/tasks/fifo_scheduler.go:224\ngo.temporal.io/server/common/backoff.ThrottleRetry.func1\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/backoff/retry.go:119\ngo.temporal.io/server/common/backoff.ThrottleRetryContext\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/backoff/retry.go:145\ngo.temporal.io/server/common/backoff.ThrottleRetry\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/backoff/retry.go:120\ngo.temporal.io/server/common/tasks.(*FIFOScheduler[…]).executeTask\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/tasks/fifo_scheduler.go:233\ngo.temporal.io/server/common/tasks.(*FIFOScheduler[…]).processTask\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/tasks/fifo_scheduler.go:211”}
Dec 04 23:01:39 RG-PT maas-temporal[254632]: {“level”:“error”,“ts”:“2024-12-05T04:01:39.503Z”,“msg”:“Critical error processing task, retrying.”,“shard-id”:1,“address”:“172.25.92.166:5273”,“component”:“visibility-queue-processor”,“wf-namespace-id”:“6b23c1fa-1d94-4a18-aa5e-f031a5a83586”,“wf-id”:“sync-boot-resources:streams”,“wf-run-id”:“f7f16b1a-4cf9-47f9-b2a4-de5dc0491543”,“queue-task-id”:3145939,“queue-task-visibility-timestamp”:“2024-12-05T03:29:41.299Z”,“queue-task-type”:“VisibilityStartExecution”,“queue-task”:{“NamespaceID”:“6b23c1fa-1d94-4a18-aa5e-f031a5a83586”,“WorkflowID”:“sync-boot-resources:streams”,“RunID”:“f7f16b1a-4cf9-47f9-b2a4-de5dc0491543”,“VisibilityTimestamp”:“2024-12-05T03:29:41.299243793Z”,“TaskID”:3145939,“Version”:0},“wf-history-event-id”:0,“attempt”:56,“error”:“context deadline exceeded”,“operation-result”:“OperationCritical”,“logging-call-at”:“lazy_logger.go:68”,“stacktrace”:“go.temporal.io/server/common/log.(*zapLogger).Error\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/log/zap_logger.go:156\ngo.temporal.io/server/common/log.(*lazyLogger).Error\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/log/lazy_logger.go:68\ngo.temporal.io/server/service/history/queues.(*executableImpl).HandleErr.func1\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/service/history/queues/executable.go:275\ngo.temporal.io/server/service/history/queues.(*executableImpl).HandleErr\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/service/history/queues/executable.go:362\ngo.temporal.io/server/common/tasks.(*FIFOScheduler[…]).executeTask.func1\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/tasks/fifo_scheduler.go:224\ngo.temporal.io/server/common/backoff.ThrottleRetry.func1\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/backoff/retry.go:119\ngo.temporal.io/server/common/backoff.ThrottleRetryContext\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/backoff/retry.go:145\ngo.temporal.io/server/common/backoff.ThrottleRetry\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/backoff/retry.go:120\ngo.temporal.io/server/common/tasks.(*FIFOScheduler[…]).executeTask\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/tasks/fifo_scheduler.go:233\ngo.temporal.io/server/common/tasks.(*FIFOScheduler[…]).processTask\n\t/build/temporal-8dYnj9/temporal-1.22.5/src/common/tasks/fifo_scheduler.go:211”}

r00ta · 5 December 2024 08:23

Are you using Ubuntu as host?

prantiknag · 5 December 2024 09:17

Yes ununtu 22.04 set as boot source and which is used for commissioning the machine. This should be synced but it’s showing queued for download and controller is in Region Importing state.

Also this canonical maas configured in without internet setup and created local mirror which is accessible wotking same as images.maas.io

When I set it as boot source url I am getting error from log which I pasted in previos reply and in UI I am getting “Failed to synchronise boot resources: Workflow timed out”

r00ta · 5 December 2024 09:27

I mean where did you install the snap MAAS? Did you install it on an Ubuntu server or RHEL or Oracle linux or something else?