Solved log.io on Fedora 26 Cannot Fine logging
-
This is not the harvester, so in theory it should not be looking to any logs at all yet.
-
@scottalanmiller said in log.io on Fedora 26 Cannot Fine logging:
This is not the harvester, so in theory it should not be looking to any logs at all yet.
Oh ok.
-
Same thing works fine immediately on Ubuntu 17.04
-
@scottalanmiller said in log.io on Fedora 26 Cannot Fine logging:
Same thing works fine immediately on Ubuntu 17.04
Isn't syslog enabled on ubuntu by default?
Does it work on ubuntu after stopping syslog? -
I like the idea of this program. Going to install and try it out.
-
@black3dynamite said in log.io on Fedora 26 Cannot Fine logging:
@scottalanmiller said in log.io on Fedora 26 Cannot Fine logging:
Same thing works fine immediately on Ubuntu 17.04
Isn't syslog enabled on ubuntu by default?
Does it work on ubuntu after stopping syslog?Runs the same with it started or stopped. It's looking for a bit of logging code that it can't load.
-
Got it, this one is weird. The /root/.log.io/web_server.conf file is empty and it cannot be. Add this into it and voila:
exports.config = { host: '0.0.0.0', port: 28778, /* // Enable HTTP Basic Authentication auth: { user: "admin", pass: "1234" }, */ /* // Enable HTTPS/SSL ssl: { key: '/path/to/privatekey.pem', cert: '/path/to/certificate.pem' }, */ /* // Restrict access to websocket (socket.io) // Uses socket.io 'origins' syntax restrictSocket: '*:*', */ /* // Restrict access to http server (express) restrictHTTP: [ "192.168.29.39", "10.0.*" ] */ }
-
Nice catch. Is that .conf file empty on a Ubuntu system as well ?
-
@jmoore said in log.io on Fedora 26 Cannot Fine logging:
Nice catch. Is that .conf file empty on a Ubuntu system as well ?
No, Ubuntu populates it with the sample data. Fedora does not. But it is the same npm command on both, so it is something wrong with their own install scripts.
-
Oh ok, that sure is weird.
-