Closed greggitter closed 1 year ago
sure. those messages are at debug level [info]
so there's nothing really broken that needs to be "fixed" but you can adjust your logging settings to a different level with environment variable LOGLEVEL
. The available levels are from most-to-least verbose: trace, debug, info, warn, error and fatal
Ah...OK makes sense. I tried adding the environment variable to the service line in the systemd config but it errors out (I'm using native, not docker). Tried these and none work...fails to start.
ExecStart=/opt/infinitude/infinitude daemon -m production -e LOGLEVEL error -l "http://:3000" &>/dev/null &
and....
ExecStart=/opt/infinitude/infinitude daemon -m production -e LOGLEVEL=error -l "http://:3000" &>/dev/null &
and....
ExecStart=/opt/infinitude/infinitude daemon -m production -l "http://:3000" &>/dev/null & -e LOGLEVEL error
In the meantime I commented out all the log lines in the source...which works fine. :) Thanks!
commenting out the log lines is guaranteed to work! :)
if you're already going to the effort of modifying source, it would be easier to change the loglevel here to 'error'
As far as I know Mojolicious doesn't support the concept of setting env vars with -e
, but if this is a systemd service file I think you may be able to just set the env in the exec line like so...
ExecStart=LOGLEVEL=error /opt/infinitude/infinitude daemon -m production -l "http://:3000"
or worst case, make a bash wrapper script to do the same.
Thanks. Just went and tried that per above (the "ExecStart=LOGLEVEL=error..." option), but unfortunately doesn't work...fails to start. No worries....I'll tweak it in the source.
Cheers! :)
Infinitude has been working well, integrated with HA and today I happened to check the syslog and noticed these messages repeating every 1 minute.
What are these messages and can it be fixed to resolve the messages or suppressed? How? Much appreciated!
Thanks!