zrhoffman edited a comment on pull request #6532: URL: https://github.com/apache/trafficcontrol/pull/6532#issuecomment-1027131794
> I had done that, and it would start but it was not servicing any HTTP or DNS requests I threw at it. That is normal if it cannot fetch the CrConfig yet, it only serves HTTP and DNS responses *after* that point. Once the comments I have made on #6532 are addressed, TR prints only this message repeatedly: ```java trafficcontrol-trafficrouter-1 | 17:43:00.361 [pool-3-thread-1] ERROR org.apache.traffic_control.traffic_router.core.secure.CertificatesClient - No traffic ops hostname yet! ``` which makes sense, since TM does not serve a CrConfig. ``` trafficrouter:/# curl -v trafficmonitor/publish/CrConfig; * Trying 172.25.0.4:80... * Connected to trafficmonitor (172.25.0.4) port 80 (#0) > GET /publish/CrConfig HTTP/1.1 > Host: trafficmonitor > User-Agent: curl/7.80.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 503 Service Unavailable < Date: Tue, 01 Feb 2022 17:59:21 GMT < Content-Length: 19 < Content-Type: text/plain; charset=utf-8 < * Connection #0 to host trafficmonitor left intact Service Unavailable ``` Corresponding message from Traffic Monitor logs: ```go trafficcontrol-trafficmonitor-1 | ERROR: datareq.go:161: 2022-02-01T18:00:21.366963347Z: Request Error: /publish/CrConfig: service still starting, some caches unpolled: map[] ``` So, the key to getting TR to serve HTTP and DNS responses is to get Traffic Monitor to serve the CrConfig. The TR piece works fine with the suggested changes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
