Server IP & Live Log issue about cronicle HOT 5 CLOSED

Wow, that's an odd one.

When Cronicle starts up, it scans the local network interfaces, and picks the first interface with an IPv4 address, that is also marked as not internal:

https://github.com/jhuckaby/pixl-config/blob/master/config.js#L268-L277

Somehow this code is picking your server's 127.0.0.1 local loopback adapter, which very much SHOULD be marked as internal. What a weird situation. I've never seen this one before.

If your server has a fixed (static) IP address, you can probably get around this by placing the IP in your /opt/cronicle/conf/config.json config file as a top-level JSON property called ip. Example:

"ip": "1.2.3.4"

from cronicle.

Weird, based on that logic, it should be grabbing the correct IP. All looks correct if I run os.networkInterfaces() in a node repl.

Local loopback is set to internal: true on both entries.

I made the config change and did a restart.

First job I ran, it seemed to have worked, but it was such a quick job I only saw it in "live" for a second before the refresh.

I did a second longer job, and it seems to have hung up after the first few lines (only Cronicle generated output though):

Once it finished, refresh and full log was present.

I'll see if it works any different next time I'm at the office.

from cronicle.

Same thing when at the office.

Connects, but never shows any output.

from cronicle.

I have been running some Python script with Cronicle and I had the same issue as you - the live log showed me only these 4 lines. I solved it by adding export PYTHONUNBUFFERED=1. I don't know if it's your case, but it can be related to some log buffering in a script that you are running.

from cronicle.

@krasnyd That was it!

I'm using Python as well, so that was a very quick test.

For anyone who might stumble on this, some alternative options for Python specifically are:

• Run the script with the -u flag: python -u script.py
• Pass flush=True to print()

Thanks guys! 🍻

from cronicle.