after upgrade to rc2 transmission is unaccessible
GoogleCodeExporter opened this issue · comments
What steps will reproduce the problem?
1. rc1 with transmission 2.41 installed
2. update to rc2
3. update all packages including transmission (to 2.42)
What is the expected output? What do you see instead?
web page is inaccessible, including the iframe in the transmission settings page
What Alt-F version are you using? Have you flashed it?
RC2, no
What is the box hardware revision level? A1, B1 or C1? (look at the label
at the box bottom)
What is your disk configuration? Standard, RAID (what level)...
What operating system are you using on your computer? Using what browser?
ubuntu 11.10, opera & chrome
Please provide any additional information below.
Have tried the following and tested after each attempt:
1. resaved transmission configuration
2. restarted transmission (warning: "Service was successfully signaled to stop
but is slow to finish.
")
3. rebooted nas
4. uninstalled and reinstalled transmission
5. rebooted nas again
Note: there were files in the torrents folder during the upgrade
Original issue reported on code.google.com by Cas...@gmail.com on 24 Feb 2012 at 3:32
In addition:
I checked the Transmission log and saw:
[17:35:55.264] RPC Server Adding address to whitelist: 127.0.0.1
(rpc-server.c:803)
[17:35:55.264] RPC Server Adding address to whitelist: 192.168.2.*
(rpc-server.c:803)
[17:35:55.265] RPC Server Serving RPC and Web requests on port
127.0.0.1:9091/transmission/ (rpc-server.c:997)
[17:35:55.265] RPC Server Whitelist enabled (rpc-server.c:1001)
Should the server not also serve web requests on 192.168.2.* ?
Original comment by Cas...@gmail.com on 24 Feb 2012 at 3:40
> Adding address to whitelist: 192.168.2.*
What is the box ip? The log shows that all hosts in the 192.168.2 network are
allowed to connect.
Can you please direct your browser to the box ip on port 9091, using the url
http://<box ip>:9091
Only next week I will be able to reproduce the problem myself.
Original comment by whoami.j...@gmail.com on 24 Feb 2012 at 6:40
Nas ip: 192.168.2.2
It has magically solved itself: the webpage is accessible again. Maybe the
webserver did not boot as it was checking existing torrent files?
Original comment by Cas...@gmail.com on 26 Feb 2012 at 11:34
Perhaps, and that also explains the "Service was successfully signaled to stop
but is slow to finish" warning message.
This is a transmission miss-feature, although I never saw it happens in a
desktop environment; instead I see a "checking torrent" message -- perhaps a
release regression?
Original comment by whoami.j...@gmail.com on 28 Feb 2012 at 4:54
Original comment by whoami.j...@gmail.com on 12 Mar 2012 at 2:40
- Changed state: WontFix