We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
after building and running the image pushpin won’t respond to requests.
% curl http://localhost:7999 curl: (52) Empty reply from server
there appears to be no arm94 condure package https://fanout.jfrog.io/ui/native/debian
log tail of pushpin starting up:
[INFO] 2023-04-12 20:37:28.604 starting... [INFO] 2023-04-12 20:37:28.604 using config: /etc/pushpin/pushpin.conf [INFO] 2023-04-12 20:37:28.606 started [INFO] 2023-04-12 20:37:28.608 [proxy] starting... [INFO] 2023-04-12 20:37:28.608 [handler] starting... [DEBUG] 2023-04-12 20:37:28.608 [proxy] routes map: [DEBUG] 2023-04-12 20:37:28.608 [proxy] (default): staging-api.everbody.com;443 [INFO] 2023-04-12 20:37:28.608 [proxy] routes map loaded with 1 entries [INFO] 2023-04-12 20:37:28.608 [handler] zhttp in stream: ipc:///usr/local/var/run/pushpin/pushpin-m2zhttp-out-stream, ipc:///usr/local/var/run/pushpin/pushpin-m2zws-out-stream [INFO] 2023-04-12 20:37:28.608 [handler] zhttp out: ipc:///usr/local/var/run/pushpin/pushpin-m2zhttp-in, ipc:///usr/local/var/run/pushpin/pushpin-m2zws-in [INFO] 2023-04-12 20:37:28.608 [handler] inspect server: ipc:///usr/local/var/run/pushpin/pushpin-inspect [INFO] 2023-04-12 20:37:28.608 [handler] accept server: ipc:///usr/local/var/run/pushpin/pushpin-accept [INFO] 2023-04-12 20:37:28.609 [handler] control server: tcp://0.0.0.0:5563 [INFO] 2023-04-12 20:37:28.609 [handler] in pull: tcp://0.0.0.0:5560 [INFO] 2023-04-12 20:37:28.609 [handler] in sub: tcp://0.0.0.0:5562 [INFO] 2023-04-12 20:37:28.609 [handler] retry: ipc:///usr/local/var/run/pushpin/pushpin-retry [INFO] 2023-04-12 20:37:28.609 [handler] ws control in: ipc:///usr/local/var/run/pushpin/pushpin-ws-control-out [INFO] 2023-04-12 20:37:28.609 [handler] ws control out: ipc:///usr/local/var/run/pushpin/pushpin-ws-control-in [INFO] 2023-04-12 20:37:28.609 [handler] stats: ipc:///usr/local/var/run/pushpin/pushpin-stats [INFO] 2023-04-12 20:37:28.609 [handler] proxy stats: ipc:///usr/local/var/run/pushpin/pushpin-proxy-stats [INFO] 2023-04-12 20:37:28.609 [handler] proxy control client: ipc:///usr/local/var/run/pushpin/pushpin-proxy-command [INFO] 2023-04-12 20:37:28.609 [handler] http control server: 0.0.0.0:5561 [INFO] 2023-04-12 20:37:28.609 [handler] started [INFO] 2023-04-12 20:37:28.609 [proxy] started [INFO] 2023-04-12 20:37:28.611 [zurl] starting... [INFO] 2023-04-12 20:37:28.613 [zurl] started [DEBUG] 2023-04-12 20:37:28.613 [zurl] U0: attempting to use interface 0.0.0.0 [DEBUG] 2023-04-12 20:37:28.613 [zurl] U0: interface ready [DEBUG] 2023-04-12 20:37:28.613 [zurl] U1: attempting to use interface :: [DEBUG] 2023-04-12 20:37:28.613 [zurl] U1: interface ready
no [condure] [condure] starting... no condure at all
The text was updated successfully, but these errors were encountered:
No branches or pull requests
after building and running the image
pushpin won’t respond to requests.
there appears to be no arm94 condure package
https://fanout.jfrog.io/ui/native/debian
log tail of pushpin starting up:
no [condure] [condure] starting...
no condure at all
The text was updated successfully, but these errors were encountered: