Transmission settings.json resets after reboot (doesn't save/keep config on reboot)

[travisnj]

I have attempted to RTFM and search for "settings.json transmission reboot" and I have not found a thread on this issue so my appreciation to anyone that can assist me in this issue.

Good news is that if this HAS been discussed before, my apologies, but the good news is that the title on this is very clear and I have used clear tags on this thread for anyone in the future to easily find the answer.

I have AC56U, transmission 2.82 installed and does run.

I have configured settings.json and all is fine (with one more exception to that)

....Issue #1........

When I reboot, settings.json is removed on reboot. I can ssh to ~ and .config is not found UNTIL I start Transmission-daemon and it will create the .config/transmission-daemon/settings.json on the fly..

After starting the daemon, the .config is created and THEN I have to stop, edit, restart so I can access UI (whitelist rpc, download, incomplete, etc.)

What am I doing wrong and HOW can I make sure the configs KEEP through the next reboot

.... Issue #2.......

Issue following up with that would be how to allow transmission to use router port forwarding.

I other words, I start the daemon and configure it for say ... xxxx port number (yes I know it is a lower port number), I can even configure for xxxxx port number and the port is not able to be bound. In the log this is written (no matter what port I use 1025-65535):

Jan 5 05:48:05 transmission-daemon[1664]: Couldn't bind port 51400 on ::: Address already in use (Is another copy of Transmission already running?) (net.c:371)

....... End of Issues......

Your walk-through and assistance is deeply appreciated!

 

[sinshiva]

well, i imagine you can't use the /jffs/configs folder to replace it, but you could store the config in /jffs and use an appropriate startup script to replace it.

This should be helpful

[edit/] probably the post-mount script

sorry, i'm retarded; services-start script, skipped right by it

 

[travisnj]

Problem I have is no experience in scripting worth mentioning.

Anyone help with devising a script please?

Wish I could just create a config file in jffs and it replaced the file with the one I have created.

The biggest pain in this is the fact that on each boot, any torrent that was currently being seeded or downloading is lost....

Could some one chime in on this and the work around for:

1. Script to replace ~/.conf/transmission-daemon/settings.json on each boot

2. Keeping the "cache" or "status" of torrents without loosing them on reboot

OR

3. Preventing the removal of 1 and 2 on power/boot cycles...

:: I hate download2 manager... A worthless piece of ware (IMO)

 

[sinshiva]

the script is pretty simple;

you must enable JFFS on the router if you haven't already

#!/bin/sh
cp /jffs/settings.json ~/.conf/transmission-daemon/settings.json

save the script as /jffs/scripts/services-start

then use this command to make it work;

chmod a+rx /jffs/scripts/*

this script will transfer the settings.json from /jffs to ~/.conf/transmission-daemon/ and will be run after all the services have started. if you make any changes like restarting the transmission-daemon, you may lose the configuration and would have to either reapply the script manually or reboot the router.

This wont help with your second problem, unfortunately

[edit/] if you knew what file the torrents were saved in, you could do something like copy it to a flash drive on services-stop and back again on services-start. i haven't dealt with transmission in a while, so i wouldn't know. you want to write to jffs as little as possible, though, which is why i suggest the flash drive.

an aside, if services-start is too late to copy the transmission stuff, then post-mount if the files to be copied are on a flash drive or init-start for /jffs, might be best, sorry