Hi, I think I'm experiencing a related problem with a running version of transmission-daemon 2.03-2 on Squeeze.
I have done a fresh purge and install of transmission-daemon and associated packages just to check its not a problem with local file permissions or anything. Description: When the transmission-daemon is closed (via a init.d stop), sometimes (and it is not all of the time, only some) the /etc/transmission-daemon/settings.json file is not fully replaced, and only a settings.json.tmp.XXXXX file is left. This means that when transmission is next started, it can not find a settings.json file, and so loads the system defaults (which are compiled into it?) As far as I can gather from this bug report and upstream descriptions, when stopped the daemon will first create a backup of the current settings.json file by moving it to a .tmp.XXXX file which is what I'm seeing. It is then supposed to write it's current configuration to settings.json, and remove the tmp file once that is completed. On Debian the daemon is by default set with CONFIG-DIR=/var/lib/transmission-daemon/info where it will look for the settings.json file. This is a symlink to /etc/transmission-daemon/settings.json. There are previous bugs in 1.X branches of transmission have resolved issues with following symlinks, so that transmission will not create the .tmp backup files in /var but instead follow the symlink and write to /etc/transmission-daemon. Transmision-daemon then saves its (defaulted) settings.json file and .tmp files directly into to /var/lib/transmission-daemon/info , I presume because the symlink is invalid it doesn't follow it to save the default settings in /etc/transmission-daemon, destroying the symlink in the process... I don't think it's a problem with Debian using symlinks to /etc/ either, because I've tried leaving the settings.json file in /var/lib/transmisison-daemon/info and modifying it to what I need, but it will still exhibit the same behaviour, remove settings.json and leave a .tmp file in its place, defaulting at next start up, I can't see anything in the logs (level 3, attatched) This is really frustrating as it means every so often if my connection drops, transmission-daemon resets to its defaults (restricting the web interface to the local-host, among other problems). I have a script setup to stop transmission-daemon on if-down and restart on if-up to save it banging its head agianst the wall and to stop it trying to use other interfaces, but even when not using this and manually stopping the daemon the problem still occurs. Is there any indication of a solution to the original problem ? - Howard
Sep 23 23:52:31 thoth transmission-daemon[14172]: Transmission 2.03 (11030) started (session.c:622) Sep 23 23:52:31 thoth transmission-daemon[14172]: RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:767) Sep 23 23:52:31 thoth transmission-daemon[14172]: RPC Server Adding address to whitelist: (rpc-server.c:767) Sep 23 23:52:31 thoth transmission-daemon[14172]: RPC Server Adding address to whitelist: 192.168.1.* (rpc-server.c:767) Sep 23 23:52:31 thoth transmission-daemon[14172]: RPC Server Serving RPC and Web requests on port 9091 (rpc-server.c:940) Sep 23 23:52:31 thoth transmission-daemon[14172]: RPC Server Whitelist enabled (rpc-server.c:944) Sep 23 23:52:31 thoth transmission-daemon[14172]: Port Forwarding Stopped (port-forwarding.c:178) Sep 23 23:52:31 thoth transmission-daemon[14172]: DHT Generating new id (tr-dht.c:378) Sep 23 23:52:31 thoth transmission-daemon[14172]: Using settings from "/var/lib/transmission-daemon/info" (daemon.c:443) Sep 23 23:52:31 thoth transmission-daemon[14172]: Saved "/etc/transmission-daemon/settings.json" (bencode.c:1651) Sep 23 23:52:31 thoth transmission-daemon[14172]: Loaded 1 torrents (session.c:1743) Sep 23 23:52:33 thoth kernel: [89063.488161] iptables denied: IN=ppp0 OUT= MAC= SRC=58.153.191.170 DST=93.182.190.43 LEN=56 TOS=0x00 PREC=0x00 TTL=117 ID=31607 DF PROTO=TCP SPT=52802 DPT=50001 WINDOW=8192 RES=0x00 SYN URGP=0 Sep 23 23:52:33 thoth transmission-daemon[14172]: CheckMyTorrentIP.jpg Tracker warning: "Your torrent client IP is #.#.#.#" (torrent.c:397) Sep 23 23:52:36 thoth transmission-daemon[14172]: Searching for web interface file "/home/debian-transmission/.local/share/transmission/web/index.html" (platform.c:524) Sep 23 23:52:36 thoth transmission-daemon[14172]: Searching for web interface file "/usr/share/transmission/web/index.html" (platform.c:524) Sep 23 23:52:45 thoth kernel: [89075.592282] iptables denied: IN=ppp0 OUT= MAC= SRC=#.#.#.# DST=#.#.#.# LEN=667 TOS=0x00 PREC=0x00 TTL=110 ID=62108 DF PROTO=TCP SPT=3351 DPT=50001 WINDOW=65535 RES=0x00 ACK PSH URGP=0 Sep 23 23:52:51 thoth pppd[14116]: Terminating on signal 15 Sep 23 23:52:51 thoth pptp[14143]: anon log[callmgr_main:pptp_callmgr.c:258]: Closing connection (shutdown) Sep 23 23:52:51 thoth pptp[14143]: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 'Call-Clear-Request' Sep 23 23:52:51 thoth pppd[14116]: Modem hangup Sep 23 23:52:51 thoth pppd[14116]: Connect time 0.6 minutes. Sep 23 23:52:51 thoth pptp[14143]: anon log[call_callback:pptp_callmgr.c:79]: Closing connection (call state) Sep 23 23:52:51 thoth pppd[14116]: Sent 26695 bytes, received 30483 bytes. Sep 23 23:52:51 thoth pppd[14116]: MPPE disabled Sep 23 23:52:51 thoth pppd[14116]: Connection terminated. Sep 23 23:52:51 thoth transmission-daemon[14172]: Closing session Sep 23 23:52:55 thoth named[2297]: received control channel command 'reconfig' Sep 23 23:52:55 thoth named[2297]: loading configuration from '/etc/bind/named.conf' Sep 23 23:52:55 thoth named[2297]: using default UDP/IPv4 port range: [1024, 65535] Sep 23 23:52:55 thoth named[2297]: using default UDP/IPv6 port range: [1024, 65535] Sep 23 23:52:55 thoth named[2297]: no longer listening on #.#.#.# ###
