Skip to content
This repository has been archived by the owner on Sep 14, 2022. It is now read-only.

HTTP 503 response on startup causes crash #30

Open
ReagentX opened this issue Apr 24, 2022 · 1 comment
Open

HTTP 503 response on startup causes crash #30

ReagentX opened this issue Apr 24, 2022 · 1 comment

Comments

@ReagentX
Copy link

Specific error:

default	19:18:03.885087-0400	Nimble	Task <5BA756A7-9FF1-40DF-AE07-4F8628C432CB>.<0> received response, status 503 content K

In context:

default	19:18:03.850269-0400	Nimble	Connection 1: connected successfully
default	19:18:03.850310-0400	Nimble	Connection 1: TLS handshake complete
default	19:18:03.850532-0400	Nimble	Connection 1: ready C(N) E(N)
default	19:18:03.850747-0400	Nimble	Task <5BA756A7-9FF1-40DF-AE07-4F8628C432CB>.<0> now using Connection 1
default	19:18:03.850799-0400	Nimble	Connection 1: received viability advisory(Y)
default	19:18:03.852747-0400	Nimble	Task <5BA756A7-9FF1-40DF-AE07-4F8628C432CB>.<0> sent request, body N 0
default	19:18:03.885087-0400	Nimble	Task <5BA756A7-9FF1-40DF-AE07-4F8628C432CB>.<0> received response, status 503 content K
default	19:18:03.885137-0400	Nimble	Connection 1: read-side closed
default	19:18:03.885329-0400	Nimble	Task <5BA756A7-9FF1-40DF-AE07-4F8628C432CB>.<0> response ended
default	19:18:03.885418-0400	Nimble	Connection 1: cleaning up
default	19:18:03.885484-0400	Nimble	[C1 9E8772E0-530F-4D29-BA46-E308D2357544 Hostname#d52219e1:443 tcp, url hash: 5558627d, tls, definite, attribution: developer] cancel
default	19:18:03.886133-0400	Nimble	[C1 9E8772E0-530F-4D29-BA46-E308D2357544 Hostname#d52219e1:443 tcp, url hash: 5558627d, tls, definite, attribution: developer] cancelled
	[C1.1 99DC1CCE-6854-49FA-97DE-B624765A9602 10.192.122.11:49839<->IPv4#bd2f8a72:443]
	Connected Path: satisfied (Path is satisfied), viable, interface: utun3, ipv4, dns
	Privacy Stance: Not Eligible
	Duration: 0.168s, DNS @0.000s took 0.021s, TCP @0.023s took 0.036s, TLS 1.2 took 0.073s
	bytes in/out: 6209/910, packets in/out: 6/3, rtt: 0.033s, retransmitted bytes: 0, out-of-order bytes: 0
default	19:18:03.887058-0400	Nimble	nw_flow_disconnected [C1.1 IPv4#bd2f8a72:443 cancelled socket-flow ((null))] Output protocol disconnected
default	19:18:03.887327-0400	Nimble	nw_connection_report_state_with_handler_on_nw_queue [C1] reporting state cancelled
default	19:18:03.890288-0400	Nimble	Task <5BA756A7-9FF1-40DF-AE07-4F8628C432CB>.<0> done using Connection 1
default	19:18:03.890408-0400	Nimble	Task <5BA756A7-9FF1-40DF-AE07-4F8628C432CB>.<0> summary for task success {transaction_duration_ms=371, response_status=503, connection=1, protocol="http/1.1", domain_lookup_duration_ms=21, connect_duration_ms=109, secure_connection_duration_ms=72, private_relay=false, request_start_ms=333, request_duration_ms=0, response_start_ms=366, response_duration_ms=5, request_bytes=238, response_bytes=715, cache_hit=false}
default	19:18:03.890438-0400	Nimble	Connection 1: done
default	19:18:04.117904-0400	Nimble	[0x7fbd4f838c20] CVCGDisplayLink::finalize
default	19:18:04.117947-0400	Nimble	[0x7fbd4f838c20] CVDisplayLink::finalize
default	19:18:04.142637-0400	Nimble	Entering exit handler.
default	19:18:04.142678-0400	Nimble	Exiting exit handler.
@soops
Copy link
Collaborator

soops commented Apr 25, 2022

Hi,

Nimble is no longer maintained by us. We have sunsetted this project. If someone else would like to submit pull requests I will accept them.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants