Empty Log File

[alexfornuto]

I'm running as a user-level systemd service. I've manually configured a log path and touched that file, but the log remains empty. The file lives in the home directory of the user running the service.

• ruby -v ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux-gnu]

• transmission-rss -v 1.0.0

• The content for your configuration file:

feeds:
  - url: REDACTED
    regexp: (REDACTED)
    download_path:REDACTED

server:
  host: localhost
  port: 9091
  tls: false
  rpc_path: /transmission/rpc

login:
  username: REDACTED
  password: REDACTED

log:
  target: /home/alex/rss.log
  level: debug

• Relevant lines from log output. There is no log file in the default location (/var/log/transmissiond-rss.log according to the README). journalctl -xe shows standard logging, nothing related to the log file.

[alexfornuto]

P.S. What is the point of the seen file? It just looks like a block of junk to me.

[alexfornuto]

P.P.S. The service keeps stopping, and without the log file I'm not sure why. All I have is from journalctl:

transmission-rss.service: Main process exited, code=killed, status=15/TERM

[Petemir]

P.S. What is the point of the seen file? It just looks like a block of junk to me.

I believe that the seenfile shows what torrents have already been seen by the program.

Other than that, I am having the same problem, I cannot see the log file configured in the config.yml... maybe the way to solve it is to just redirect the output of the process to one file :man_shrugging: .

[Petemir]

@alexfornuto as a workaround: You can do it like this , although surely it should work as specified by the README...

[nning]

@Petemir is right about the seenfile; it contains hashes of all URLs already added successfully to Transmission or ignored through filtering.

This seems to be a bug with transmission-rss and I will look further into this when I have some spare time.

[alexfornuto]

Any updates on this? I finally got back around to it, and the linked workaround does have me logging to a file, so now hopefully the next time it crashes I can submit a proper issue for it. Still, it would be nice to have logs working as defined in the config file.