Search found 66 matches

by maki.ato
Sun Nov 18, 2012 9:45 pm
Forum: General
Topic: i need to make a script, need help
Replies: 1
Views: 1015

Re: i need to make a script, need help

you need to setup a couple of cron jobs, one to start transmission, the other to shut it down.
read the man pages about cron, crontab, etc.
by maki.ato
Thu Nov 01, 2012 10:52 pm
Forum: Support
Topic: Transmission help on Buffalo linkstation
Replies: 1
Views: 2952

Re: Transmission help on Buffalo linkstation

The receipt assumes some basic linux skills. You should read about adduser. Try "adduser --help" from the command line, and also here: http://linux.die.net/man/8/adduser In addition, you'll probably run into all sorts of permission problems. Lean about it here: http://linux.die.net/Intro-Linux/sect_...
by maki.ato
Mon Oct 29, 2012 10:16 am
Forum: Web Interface
Topic: Yet Another 403: Forbidden!
Replies: 4
Views: 13392

Re: Yet Another 403: Forbidden!

Make sure you're editing the correct settings file. Check how transmission-daemon is started. There's a command-line switch that may be used to override this.
Make sure transmission-daemon is down BEFORE editing settings.json.
by maki.ato
Thu Oct 25, 2012 2:43 pm
Forum: Support
Topic: Start Transmission with different user (init script)
Replies: 3
Views: 14085

Re: Start Transmission with different user (init script)

What does the log say?
Does the $USER user have the proper permissions for read/write the settings file?
Did you try to:

Code: Select all

sudo -u down transmission-daemon
Does that work?
by maki.ato
Thu Oct 25, 2012 11:44 am
Forum: Support
Topic: rpc-bind-address changes on its own?!
Replies: 28
Views: 18198

Re: rpc-bind-address changes on its own?!

rb07 wrote:Some of the facts don't seem right: if settings.json changed, why you never see the daemon starting with a changed IP? It only changed just after you noticed the loss of RPC... unlikely.
This should be easy to reproduce: Turn off daemon, edit rpc-bind-address in settings.json, start daemon.
by maki.ato
Wed Oct 24, 2012 9:01 am
Forum: Support
Topic: rpc-bind-address changes on its own?!
Replies: 28
Views: 18198

Re: rpc-bind-address changes on its own?!

rb07 wrote:
maki.ato wrote:There are other accounts of this, or something similar happening?
Can you point me to the thread(s)/Trac Ticket(s)?
No, there are no other reports about this, just about weird thing happening.
Any of them may be related?
by maki.ato
Tue Oct 23, 2012 8:12 pm
Forum: Support
Topic: rpc-bind-address changes on its own?!
Replies: 28
Views: 18198

Re: rpc-bind-address changes on its own?!

There are other accounts of this, or something similar happening?
Can you point me to the thread(s)/Trac Ticket(s)?
by maki.ato
Tue Oct 23, 2012 5:18 pm
Forum: Support
Topic: rpc-bind-address changes on its own?!
Replies: 28
Views: 18198

Re: rpc-bind-address changes on its own?!

We may be looking at two unrelated problems: daemon stops working (very common on NASes, see Wiki ), something changes settings.json (not unheard off, but the reports on this forum never went anywhere). I never entertained the the idea that transmission stopped working. When I think about it, I bel...
by maki.ato
Tue Oct 23, 2012 3:59 pm
Forum: Support
Topic: Uses over 300MB of RAM
Replies: 3
Views: 1661

Re: Uses over 300MB of RAM

I'm experiencing similar excessive memory usage by transmission-daemon on my NAS (and I wrote a watchdog cron job to restart it when it gets out of hand). When started, transmission uses about 60% of available memory, and that number grows to over 100% in a matter of a few days. I seed about ~500 to...
by maki.ato
Tue Oct 23, 2012 11:28 am
Forum: Support
Topic: rpc-bind-address changes on its own?!
Replies: 28
Views: 18198

Re: rpc-bind-address changes on its own?!

rb07 wrote:I don't think the Mac has anything to do here... he's using a daemon in a NAS, the log is from that NAS (running Linux).
Yup, pretty much so. daemon running on NAS (linux), no syslogd, logging to file using the -e option.
by maki.ato
Mon Oct 22, 2012 11:13 pm
Forum: Support
Topic: rpc-bind-address changes on its own?!
Replies: 28
Views: 18198

Re: rpc-bind-address changes on its own?!

OK, now this gets even stranger. I tried that new grep on the current log (message-level 3) and it produced the (expected) following output: sh-3.2# cd /mnt/HD_a2/.transmission-daemon/ sh-3.2# grep -i rpc transmission-daemon.log [22:12:26.264] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-s...
by maki.ato
Mon Oct 22, 2012 8:12 pm
Forum: Support
Topic: rpc-bind-address changes on its own?!
Replies: 28
Views: 18198

Re: rpc-bind-address changes on its own?!

message-level is 2 Try setting to 3. Stop the daemon first. Search for "bound". 2012-10-22 12:14:04 -0600 net.c:558 [Debug] TurboT: Bound socket 11 to port xxxxx on 0.0.0.0 Sure, I can do that....I just did. Currently, after I fixed that setting again everything is in order. So I/we can wait till t...
by maki.ato
Mon Oct 22, 2012 9:25 am
Forum: Support
Topic: rpc-bind-address changes on its own?!
Replies: 28
Views: 18198

Re: rpc-bind-address changes on its own?!

regarding the log: I imagine that it's some build-time option/config Kylek uses to reduce log verbosity. Kylek's plugin has nothing to do with Transmission's log... or maybe I don't know what the plugin (funplug?) is, I was assuming it is Kylek's automatic (a RSS feed scanner to load torrents autom...
by maki.ato
Sun Oct 21, 2012 10:21 pm
Forum: Support
Topic: rpc-bind-address changes on its own?!
Replies: 28
Views: 18198

Re: rpc-bind-address changes on its own?!

transmission-remote-gui, not transmission-remote-guy. Sorry for the typo. Both listed on the add-on page (http://www.transmissionbt.com/resources/), for both I use the latest version. oh, and the daemon is started with just two command line flags: -g -e regarding the log: I imagine that it's some bu...
by maki.ato
Sun Oct 21, 2012 7:56 pm
Forum: Support
Topic: rpc-bind-address changes on its own?!
Replies: 28
Views: 18198

Re: Something strange just happend

Thank you so much for helping me make sense of it. ... Looking at the log would be interesting, I would expect an error logged about not being able to bind to that address; I should've added that I grepped through Transmission Daemon's log and found nothing relevant. I "grep -i" for error, fail, rpc...