Synology: transmission.log is Empty #2792
Replies: 1 comment
-
Wanted to update in case this might help anyone else. Permissions and other settings that I thought might be at fault are all OK. I kept digging until I found the TRANSMISSION_MESSAGE_LEVEL option. The default is 2 (Error) and it seems that I haven't encountered any errors to be logged. I changed it to 5 (Debug) as a test and it started logging almost everything as expected. I've changed it to 4 (Info) for the short term and am seeing messages in the log. I will probably set it back to the default in the future. I'm guessing that the old log that ended in July was being generated because whatever guide I used to set things up had set the ENV variable to Info. The format of the log is different from the current version, so something must have changed to cause logging to stop. |
Beta Was this translation helpful? Give feedback.
-
I recently noticed an issue with my transmission-openvpn setup as I was doing some cleanup and reconfiguring of my docker setup. Even after completely removing my container and its data mount point on my Synology, the transmission.log remains empty with a file size of 0 bytes.
One possible clue, when I was moving the docker folder, I found there was a 502 mb transmission.log file that stopped updating back in July last year. I removed it and the new log never populated. Since then I've rebuilt the container and switched to using a compose file via a Portainer stack. I've also created a totally blank transmission folder and let everything be recreated by the container.
Everything else seems to be working fine, just no log.
Beta Was this translation helpful? Give feedback.
All reactions