-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
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
Live Logs connecting to wrong port on workers #426
Comments
Yes! I have this same exact issue! Would love to see this resolved! :) |
I'm afraid it's not possible in this configuration. Downgrading websockets from https to http is blocked by design. |
It will 😊, and also HTTPS/SSL will be fully supported 100%. |
I have worked to put together this PR that implements live log proxying through the master. Please take a look and let me know what you think. Also much thanks to @mikeTWC1984 for the inspiration and base code that I worked from for this. |
I'd highly appreciate to have this merged! |
Summary
When attempting to view live logs on worker nodes The system attempts to connect to https://:3012. However 3012 is the http port on the worker and not the https port. This causes live logs to not be streamed to the job as it runs. Logs become available after the job has completed.
Steps to reproduce the problem
Run any job in the system and attempt to view the live logs. Instead of logs you will get messages of the type: Log Watcher: Server Connect Error: Error: websocket error (https://10.75.6.150:3012)
Your Setup
Single master with many workers. The master is behind a load balancer. The LB has an SSL certificate installed to present https to the end user. Master and Workers are configured with http only.
Operating system and version?
Amazon Linux 2
Node.js version?
v14.17.1
Cronicle software version?
0.8.62
Are you using a multi-server setup, or just a single server? Multi
Are you using the filesystem as back-end storage, or S3/Couchbase? S3
Can you reproduce the crash consistently? Yes
Log Excerpts
Log Watcher: Connecting to server: https://10.75.6.150:3012...
Log Watcher: Server Connect Error: Error: websocket error (https://10.75.6.150:3012)
Log Watcher: Server Connect Error: Error: websocket error (https://10.75.6.150:3012)
The text was updated successfully, but these errors were encountered: