Skip to content

Live Logs connecting to wrong port on workers #426

@rrusso1982

Description

@rrusso1982

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions