Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rTorrent not running after upgrading ruTorrent from 3.6-6 to 3.7-8 on DSM 5.2 #2369

Closed
damfino opened this issue Jun 8, 2016 · 4 comments
Closed

Comments

@damfino
Copy link

damfino commented Jun 8, 2016

For new Package Requests, see the guidelines

Setup

Package Name: ruTorrent
Package Version: 3.7-8

NAS Model: DS214play
NAS Architecture: INTEL Atom CE5335
DSM version: DSM 5.2-5644 Update 5

Expected behavior

Today I've upgraded the package from the 3.6-6 to 3.7-8.
Once the upgrade was done I've clicked on "Run" from the action menu on the package center window expecting to see the status change from "Stopped" to "Running".

Actual behavior

Instead nothing happens. The "loading" animation runs for a couple of seconds and the status doesn't change.
Checking /volume1/@appstore/rutorrent/var/rtorrent.pid it says that the process has PID 27777, but ps | grep rtorrent gives nothing. So the process is not running.

Steps to reproduce

1. Upgrade the package from the Package Center
2. Click on Run from the action menu
3.

Package log

Check Package Center or /usr/local/{package}/var/

Insert the package log here

Other logs

E.g. /var/log/messages or /var/log/synopkg.log
synopkg.log.zip
Insert log here

@damfino
Copy link
Author

damfino commented Jun 9, 2016

Is it possible to downgrade this package to the previous version?

@GoodOmens83
Copy link
Contributor

GoodOmens83 commented Jun 12, 2016

Few things:

  1. Can you access the rutorrent web interface?
  2. Have you tried simply rebooting the NAS (this might the simplest fix)?
  3. Have you tried removing the PID file and trying to restart it from the web interface?
  4. try running:
    var/packages/rutrorrent/scripts/start-stop-status stop
    /var/packages/rutrorrent/scripts/start-stop-status start
    and see if any errors are shown
  5. What are the contents of your .rtorrent.rc file? (/usr/local/rutorrent/var/.rtorrent.rc)

@damfino
Copy link
Author

damfino commented Jun 13, 2016

@GoodOmens83

Thanks for your interest in my issue.

  1. Can you access the rutorrent web interface?

Yep, and the "log" tab says:
[13.06.2016 13:20:51] WebUI started.
[13.06.2016 13:20:51] No connection to rTorrent. Check if it is really running. Check $scgi_port and $scgi_host settings in config.php and scgi_port in rTorrent configuration file.

  1. Have you tried simply rebooting the NAS (this might the simplest fix)?

Yes, I did it many times, no luck.

  1. Have you tried removing the PID file and trying to restart it from the web interface?

Just tried. Another pid files shows up but the daemon stops immediately.

  1. try running:
    var/packages/rutrorrent/scripts/start-stop-status stop
    /var/packages/rutrorrent/scripts/start-stop-status start
    and see if any errors are shown

Here's what I get:
DS214> /var/packages/rutorrent/scripts/start-stop-status stop
ruTorrent is not running
DS214> /var/packages/rutorrent/scripts/start-stop-status start
Starting ruTorrent ...
Apparently no errors, and /var/log/synopkg.log says:
2016/06/13 13:27:52 start rutorrent: begin to start version 3.7-8
2016/06/13 13:27:52 start rutorrent: start version 3.7-8 successfully, resul
t 0
But still, no rtorrent daemon running.

  1. What are the contents of your .rtorrent.rc file? (/usr/local/rutorrent/var/.rtorrent.rc)

scgi_port = localhost:8050
directory = /volume1/Torrent
session = /usr/local/rutorrent/var/.session
max_memory_usage = 183337984
log.open_file = "rtorrent.log", "/usr/local/rutorrent/var/rtorrent.log"
log.add_output = "warn", "rtorrent.log"
http_cacert = /usr/local/rutorrent/cert.pem
system.umask.set = 002
port_range = 42042-42045

BTW, the rtorrent.log does not exist anywhere.

@Safihre
Copy link
Contributor

Safihre commented Jun 24, 2018

Updates (like proper DSM6 support) will be handled in #2215 and maybe PR #3175.

@Safihre Safihre closed this as completed Jun 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants