Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

Transmission doesn't start after reboot

Joined
Aug 23, 2016
Messages
3
Hi community, first post here.

I'm a new FreeNAS user, I'm using both osx and windows machines to connect. Still trying to get a grasp of the system and spent some time trying to set up transmission correctly. Last night I was able to fix my permission issues and was able to find which folder it downloads the stuff and how to share that folder (somehow without being so sure about what I'm doing, just followed many different advices on forums and youtube)

Since I'm the only user of FreeNAS and main reason is to gain experience on the system, it's not a critical component for me right now and I turn the system off before I go to bed. This morning I connected to my home computer from work using TeamViewer to connect my FreeNAS and freenas.local DNS didn't work. I put the IP address in and I was able to reach to the web GUI. But now I cannot start transmission, cannot get its web GUI. Also as I'm attaching the screenshot there's no + sign next to the plugins tab on the left bar. This happened (plus sign dissappearing) before when I deleted the transmission's jail without deleting the plug in properly but after that I used 8. option on the FreeNAS to restore the system to it's factory settings and set the transmission up from scratch and it had worked. Unfortunately until last night.

I thought restoring to factory settings is like a clean installation? If it's, maybe I'm doing something every time I set this system up that's causing this issue.

Any help would be appreciated, thanks in advance!

System information;

Build FreeNAS-9.10.1 (d989edd)
Platform Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
Memory 8162MB
 

Attachments

Last edited:

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
5,995
Error message? Does the jail exist? Can you use the cli to jls and jexec into the jail then try service transmission onestart? I bet you are changing the permissions of your pool root recursivly or modifying your jail root somehow.

Sent from my Nexus 5X using Tapatalk
 
Joined
Aug 23, 2016
Messages
3
Aug 26 09:21:51 freenas mDNSResponder: CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for PCP & NAT-PMP announcements
Aug 26 09:21:52 freenas manage.py: [freeadmin.navtree:631] An error occurred while unserializing from http://192.168.1.7/plugins/transmission/1/_s/treemenu: No JSON object could be decoded
Aug 26 09:21:53 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801406D60 freenas.local. (Addr) that's already in the list
Aug 26 09:21:53 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801407180 7.1.168.192.in-addr.arpa. (PTR) that's already in the list
Aug 26 09:21:53 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801409D60 freenas.local. (Addr) that's already in the list
Aug 26 09:21:53 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 000000080140A180 8.1.168.192.in-addr.arpa. (PTR) that's already in the list
Aug 26 10:53:37 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://192.168.1.7/plugins/transmission/1/_s/status: No JSON object could be decoded


I don't know if needed to hide anything from this error message for security reasons but here it is. Also I'm attaching the jail's screenshot.

This is the output of 'service transmission restart'


Shell
root@transmission_1:/ # service transmission restart
transmission not running? (check /var/run/transmission/daemon.pid).
usage: chown [-fhvx] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhvx] [-R [-H | -L | -P]] :group file ...
Starting transmission.
su: pam_start: system error
/usr/local/etc/rc.d/transmission: WARNING: failed to start transmission
root@transmission_1:/ #

When I go ahead and try to restart transmission under plug ins it fails and says some issue occurred.


Output of the ls -l /var/db/transmission

root@transmission_1:/ # ls -l /var/db/transmission
total 24
drwxrwxrwx 2 transmission transmission 2 Aug 25 09:30 blocklists
-rw------- 1 transmission transmission 562 Aug 26 00:00 dht.dat
drwxrwxrwx 2 transmission transmission 4 Aug 26 00:00 resume
-rw------- 1 transmission transmission 2184 Aug 26 00:00 settings.json
-rw------- 1 transmission transmission 147 Aug 25 23:56 stats.json
drwxrwxrwx 2 transmission transmission 4 Aug 25 10:48 torrents


Thanks for your time to read and response.
 

Attachments

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
5,995
Your network settings need to be filled out. Specifically you need to add a default gateway.

Sent from my Nexus 5X using Tapatalk
 
Joined
Aug 23, 2016
Messages
3
Thank you again for follow up.

This is my router settings. I don't know why but I can reach my router web page using either 192.168 1.1 or 0.2
Router Settings.png

This is my network settings. I tried removing google DNS but I was able to make things work with this settings last night.

Network.png

These are the errors when I reboot the system;

Aug 26 12:24:50 freenas mDNSResponder: mDNSResponder (Engineering Build) (Aug 3 2016 19:22:46) starting
Aug 26 12:24:50 freenas mDNSResponder: 8: Listening for incoming Unix Domain Socket client requests
Aug 26 12:24:50 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Aug 26 12:24:50 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Aug 26 12:24:50 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Aug 26 12:24:50 freenas netatalk[2778]: Netatalk AFP server starting
Aug 26 12:24:50 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000********D60 freenas.local. (Addr) that's already in the list
Aug 26 12:24:50 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000*********80 7.1.168.192.in-addr.arpa. (PTR) that's already in the list
Aug 26 12:24:50 freenas netatalk[2778]: Registered with Zeroconf
Aug 26 12:24:50 freenas cnid_metad[2799]: CNID Server listening on localhost:4700
Aug 26 12:24:51 freenas afpd[2798]: Netatalk AFP/TCP listening on 192.168.1.7:548
Aug 26 12:29:09 freenas manage.py: [freeadmin.navtree:631] An error occurred while unserializing from http://192.168.1.7/plugins/transmission/1/_s/treemenu: No JSON object could be decoded
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
5,995
Name server 1 should not be 192.168.1.7 it should be your Google addresses. Something in your network is messed up.

Sent from my Nexus 5X using Tapatalk
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
5,995
Forums are messed up today, I'm not seeing all your messages. You have modified the permissions of your jail dataset so all your jails are ruined. You need to rebuild them and never change their permissions or the permissions of your root dataset.

Sent from my Nexus 5X using Tapatalk
 

nojohnny101

FreeNAS Expert
Joined
Dec 3, 2015
Messages
1,455
Name server 1 should not be 192.168.1.7
start there. i just double checked mine and IPv4 Default Gateway (which is your router's IP address) should be the same as your Nameserver 1

I would make sure all your network settings are in order and then as @SweetAndLow said, start fresh with your jails. you need to be very careful modifying permissions from the CLI, especially if you don't know really what you're doing. i know this from experience (i'm still a relative noob).
 
Top