search

ena30 / snake-os

Automatically exported from code.google.com/p/snake-os
0 stars 0 forks source link

Transmission ui not reachable, no login prompt #136

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. try to connect with webui (either from within snakeos or transmission remote 
client)
2. try to restart transmission via snakeos ui, reports as not running 
3. if pull power to nas transmission needs to be started still not able to 
reach ui

What is the expected output? What do you see instead?
expected password prompt when clicking transmission webui link within snakeos, 
if using transmission remote gui it either says connection timed out

What version of the product are you using? On what operating system?
newest snakeos with whichever transmission version 2.11 i think

Please provide any additional information below.

in addition the cpu is at 100% while transmission is running if stopped it 
reports around 5%.

maybe related but i did a disk check and it came back with errors so i 
connected it to my ubuntu and ran fdsk and it came back clean, but still 
problems with transmission.

i have to say the nas has been running perfect with an up time exceeding days 
as oppossed to the orginal fw of reboots continously

Original issue reported on code.google.com by paveysc...@googlemail.com on 27 Feb 2011 at 4:00

GoogleCodeExporter commented 8 years ago 
Maybe its just the transmission checking the torrent files.

Original comment by gfernan...@gmail.com on 27 Feb 2011 at 11:20

GoogleCodeExporter commented 8 years ago 
Ok I don't think this is a bug as such I have it working, did a config reset 
and it worked straight away as soon as I changed the download folder it stops 
working, I have no torrents added or anything like that, what causes this maybe 
a corrupt disk?

Thanks
Scott

Original comment by paveysc...@googlemail.com on 28 Feb 2011 at 12:45

GoogleCodeExporter commented 8 years ago 
I had a problem related to disk corruption too. It is even worse if the disk is 
NTFS-formatted.

Original comment by gfernan...@gmail.com on 1 Mar 2011 at 12:56

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I have the same problem, just when I have syslog stopped. Please check if you 
have syslog started. Thats works for me

Original comment by julianlo...@atletaviajero.info on 16 Feb 2012 at 10:37