Live log feature not working

mpatel-cpi commented 5 years ago

Summary

Live log feature doesn't work, logs show up after the job has finished. I checked that the firewall rules are fine. Is there any way to debug this further?

Steps to reproduce the problem

Your Setup

Cronicle master: Accessible from my laptop Cronicle slave: Accessible from cronicle master (but not from my laptop)

Excerpts from config:

        "server_comm_use_hostnames": 1,
        "web_socket_use_hostnames": 1,

        "WebServer": {
                "http_port": 3012,

                "https": 1,
                "https_port": 3013,
                "https_cert_file": "conf/ssl.crt",
                "https_key_file": "conf/ssl.key",
                "https_force": 0,
                "https_timeout": 30,

Operating system and version?

Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial

Node.js version?

v8.11.2

Cronicle software version?

0.8.28

Are you using a multi-server setup, or just a single server?

1 cronicle master + 1 cronicle slave

Are you using the filesystem as back-end storage, or S3/Couchbase?

File system

Can you reproduce the crash consistently?

Yes

Log Excerpts

Log Watcher: Connecting to server: https://cronicle-slave.us.prod.chargepoint.local:3013... Log Watcher: Server Connect Error: Error: websocket error (https://cronicle-slave.us.prod.chargepoint.local:3013) Log Watcher: Server Connect Error: Error: websocket error (https://cronicle-slave.us.prod.chargepoint.local:3013)

jhuckaby commented 5 years ago

The live log feature requires a direct connection from the client web browser to the machine running the job. You can control whether it tries to connect via IP or hostname, using the web_socket_use_hostnames configuration property, but either way the web browser needs to establish a WebSocket connection directly to the machine running the job, for a live log display.

There is currently no way to proxy that through the master server, but I am planning on introducing such a feature in an upcoming version of Cronicle. Stay tuned!

lettore commented 2 years ago

There's a way to fix this?

john8329 commented 1 year ago

I believe this fails when using HTTPS and a self signed certificate, is that correct? It definitely seems the case but there's no specific error in the browser's console.

tomerh2001 commented 3 months ago

+1

jhuckaby / Cronicle