New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not Running #49
Comments
hi @kakious thanks for reporting. What version of python and which operating system are currently using? |
I am running |
thanks @kakious please paste a copy of your Please also run plex-scrobble through strace and pass along the output. The following will stuff the output into /tmp/plex-scrobble.out. You can dump the output into http://pastebin.com or some other text sharing site.
If you have existing plex-scrobble cache files, try deleting those as well ( |
.toml Strace : http://termbin.com/ozu2 |
hey @kakious , in the run that was captured with PID defs19575 - parent plex-scrobble pid file handle 3
plex-scrobbler was attempting to stuff 170 bytes into file handle 3 (> /tmp/plex-scrobble.log) . Is there any data currently present in that log file ? If so , could you send it along file handle 4 Appears to be controlled by PID 19582 and looks like its reading your Plex log file. The select call waits for 30k microseconds then reads the file again looking for new log entries.. The polling behaviour seems to be working as expected..
If you didn't see anything in the log file that time around, I can create a patch that will allow you to log to STDOUT instead of a file for further debugging.... |
It seems there are some data in log. Here is what it has: I will actually try running it and testing it again. I just updated the system fully and there was a strange occurrence where I had multiple linux headers. UPDATE : Still not registering I am listening anything |
hi @kakious , if the script is still logging, please dump the most recent logs. Do you see the following logs being written to When you view your Plex server log data ( |
I have installed the terminal via PIP and it will not run. It is not producing any logs.
The text was updated successfully, but these errors were encountered: