Error in Log-Reader

---

I get some Errors from the log reader:

error [pimatic]: A uncaught exception occured: Error: ENOENT: no such file or directory, stat '/tmp/oscam.log’
at Error (native)
at Object.fs.statSync (fs.js:844:18)
at Tail.watchEvent (/home/pi/pimatic-app/node_modules/pimatic-log-reader/node_modules/tail/tail.js:98:18)
at FSWatcher.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-log-reader/node_modules/tail/tail.js:84:22)
at emitTwo (events.js:87:13)
at FSWatcher.emit (events.js:172:7)
at FSEvent.FSWatcher._handle.onchange (fs.js:1221:12)
This is most probably a bug in pimatic or in a module, please report it!

The file is there. Sometimes pimatic crasches. The following message comes at the same time.

warn [pimatic]: Keeping pimatic alive, but could be in an undefined state, please restart pimatic as soon as possible!

@daice said in Error in Log-Reader:

ENOENT: no such file or directory, stat '/tmp/oscam.log’

Please make sure the file /tmp/oscam.log always exist and is readable. Note, that /tmp is usually cleared on system reboot.

Which version of the plugin are you using? How oten do you see the error message? Does it just happen once on startup?

I’m using version 0.9.0. The file is at this place and oscam starts much faster than pimatic so on startup the file is generated before pimatic is up and running. It happens on normal running, not on system startup. I would say it happens 2-3 times a week.

@daice said in Error in Log-Reader:

I would say it happens 2-3 times a week.

Do you use logrotate, and if yes, how often is the file being rotated (-> have a look at the timestamps of the previously rotated files)?

The size of the log file is restriceted to 2048kB, so i think it use logrotate or somthing similar. I don’t know how often the file is being rotated. Because it depends on the entrys the server is generating and what is going on on the server. Does the log-reader plugin has problems with rotating logfiles?

Regards daice

@daice said in Error in Log-Reader:

I don’t know how often the file is being rotated.

-> have a look at the timestamps of the previously rotated files

Does the log-reader plugin has problems with rotating logfiles?

This depends on the logration method and needs to be investigated.