Forums

Resolved
0 votes
A couple weeks ago my transmission just quit working. Went to restart it and it wont start. I cant find any logs for it anywhere to get help at whats wrong with it. Anyone?
Maybe an update issued to something that hosed it up?
Anyone else have trans stop working and not restarting?
Wednesday, August 28 2019, 02:41 PM
Share this post:
Responses (5)
  • Accepted Answer

    Rich
    Rich
    Offline
    Sunday, May 10 2020, 01:41 AM - #Permalink
    Resolved
    0 votes
    Found this post, helped me with the same issue. Transmission was working, then quit, I didn't have backup of the config so I uninstalled and reinstalled, set the password again and now Transmission is working again. It even remembered what I had downloaded and was seeding.

    Not sure why the config disappeared.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, August 31 2019, 12:06 PM - #Permalink
    Resolved
    0 votes
    What the holy hell!?!?
    Your right my config file is completely blank. Now how the hell did that happen.
    Not a problem. I have backups
    Thanks for pointing this out.
    I wish there was an actual log for transmission in clearos
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 30 2019, 11:12 PM - #Permalink
    Resolved
    0 votes
    Your log says you might be missing a config file?
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 30 2019, 09:22 PM - #Permalink
    Resolved
    0 votes
    login as: root
    root@192.168.1.2's password:
    Last login: Fri Aug 30 10:44:46 2019 from jdkillian.the-killians.com
    [root@server ~]# systemctl status transmission-daemon -l
    ● transmission-daemon.service - Transmission BitTorrent Daemon
    Loaded: loaded (/usr/lib/systemd/system/transmission-daemon.service; enabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Fri 2019-08-30 10:48:24 CDT; 7s ago
    Process: 13628 ExecStart=/usr/bin/transmission-daemon -f --log-error (code=exited, status=1/FAILURE)
    Main PID: 13628 (code=exited, status=1/FAILURE)

    Aug 30 10:48:24 server.the-killians.com transmission-daemon[13628]: [2019-08-30 10:48:24.064] transmission-daemon Error loading config file -- exiting. (daemon.c:693)
    Aug 30 10:48:24 server.the-killians.com systemd[1]: transmission-daemon.service: main process exited, code=exited, status=1/FAILURE
    Aug 30 10:48:24 server.the-killians.com systemd[1]: Failed to start Transmission BitTorrent Daemon.
    Aug 30 10:48:24 server.the-killians.com systemd[1]: Unit transmission-daemon.service entered failed state.
    Aug 30 10:48:24 server.the-killians.com systemd[1]: transmission-daemon.service failed.
    [root@server ~]#


    [root@server ~]# journalctl -xe
    Aug 30 10:48:54 server.the-killians.com postfix/smtpd[4534]: disconnect from unknown[141.98.9.42]
    Aug 30 10:48:54 server.the-killians.com postfix/smtpd[12330]: connect from unknown[185.234.219.193]
    Aug 30 10:48:54 server.the-killians.com sudo[14025]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:48:54 server.the-killians.com sudo[14025]: pam_unix(sudo:session): session closed for user root
    Aug 30 10:48:54 server.the-killians.com sudo[14030]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:48:54 server.the-killians.com sudo[14030]: pam_unix(sudo:session): session closed for user root
    Aug 30 10:48:55 server.the-killians.com saslauthd[2994]: pam_unix(smtp:auth): check pass; user unknown
    Aug 30 10:48:55 server.the-killians.com saslauthd[2994]: pam_unix(smtp:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
    Aug 30 10:48:55 server.the-killians.com saslauthd[2991]: DEBUG: auth_pam: pam_authenticate failed: User not known to the underlying authentication module
    Aug 30 10:48:55 server.the-killians.com saslauthd[2991]: do_auth : auth failure: [user=arnelle] [service=smtp] [realm=the-killians.com] [mech=pam] [reason=PAM au
    Aug 30 10:48:55 server.the-killians.com postfix/smtpd[10697]: warning: unknown[141.98.9.67]: SASL LOGIN authentication failed: authentication failure
    Aug 30 10:48:55 server.the-killians.com sudo[14038]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:48:55 server.the-killians.com sudo[14038]: pam_unix(sudo:session): session closed for user root
    Aug 30 10:48:56 server.the-killians.com sudo[14043]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:48:56 server.the-killians.com sudo[14043]: pam_unix(sudo:session): session closed for user root
    Aug 30 10:48:56 server.the-killians.com postfix/smtpd[10697]: disconnect from unknown[141.98.9.67]
    Aug 30 10:48:56 server.the-killians.com saslauthd[2994]: DEBUG: auth_pam: pam_authenticate failed: User not known to the underlying authentication module
    Aug 30 10:48:56 server.the-killians.com saslauthd[2994]: do_auth : auth failure: [user=barbara] [service=smtp] [realm=the-killians.com] [mech=pam] [reason=PAM au
    Aug 30 10:48:56 server.the-killians.com postfix/smtpd[12330]: warning: unknown[185.234.219.193]: SASL LOGIN authentication failed: authentication failure
    Aug 30 10:48:56 server.the-killians.com postfix/smtpd[12330]: lost connection after AUTH from unknown[185.234.219.193]
    Aug 30 10:48:56 server.the-killians.com postfix/smtpd[12330]: disconnect from unknown[185.234.219.193]
    Aug 30 10:48:57 server.the-killians.com sudo[14051]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:48:57 server.the-killians.com sudo[14051]: pam_unix(sudo:session): session closed for user root
    Aug 30 10:48:57 server.the-killians.com sudo[14056]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:48:57 server.the-killians.com sudo[14056]: pam_unix(sudo:session): session closed for user root
    Aug 30 10:48:57 server.the-killians.com postfix/smtpd[10500]: warning: hostname suffil.rostage.com does not resolve to address 141.98.9.5
    Aug 30 10:48:57 server.the-killians.com postfix/smtpd[10500]: connect from unknown[141.98.9.5]
    Aug 30 10:48:58 server.the-killians.com sudo[14064]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:48:58 server.the-killians.com sudo[14064]: pam_unix(sudo:session): session closed for user root
    Aug 30 10:48:58 server.the-killians.com sudo[14069]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:48:58 server.the-killians.com sudo[14069]: pam_unix(sudo:session): session closed for user root
    Aug 30 10:48:59 server.the-killians.com sudo[14079]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:48:59 server.the-killians.com sudo[14079]: pam_unix(sudo:session): session closed for user root
    Aug 30 10:48:59 server.the-killians.com sudo[14086]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:48:59 server.the-killians.com sudo[14086]: pam_unix(sudo:session): session closed for user root
    Aug 30 10:49:00 server.the-killians.com sudo[14094]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:49:00 server.the-killians.com sudo[14094]: pam_unix(sudo:session): session closed for user root
    Aug 30 10:49:00 server.the-killians.com sudo[14099]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:49:00 server.the-killians.com sudo[14099]: pam_unix(sudo:session): session closed for user root
    Aug 30 10:49:01 server.the-killians.com sudo[14107]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:49:01 server.the-killians.com sudo[14107]: pam_unix(sudo:session): session closed for user root
    Aug 30 10:49:01 server.the-killians.com sudo[14112]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Aug 30 10:49:01 server.the-killians.com sudo[14112]: pam_unix(sudo:session): session closed for user root
    lines 1030-1072/1072 (END)
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, August 28 2019, 04:15 PM - #Permalink
    Resolved
    0 votes
    Mine still works. Straight after the failure, have you tried "systemctl status transmission-daemon -l" and "journalctl -xe" for more information. There has been no transmission update since April although there is one in epel-unverified waiting to come through.
    The reply is currently minimized Show
Your Reply