transmission-daemon exited on signal 11

[alexhore]

I’m replacing a very old 1TB Linkstation Pro. I wanted a small box with 4TB storage, relatively fast to run Windows CIFS sharing, Plex, Transmission. I am trying to get all this working and once I have I will scrub once per week and back up to a larger NAS built next month. I completely understand the risk associated with no redundancy here.

Spec
FreeNAS version FreeNAS 9.2.1.8-Release 64-bit (USB image)
Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
4039MB
2X2TB Stripped ZFS lz4

I have checked the rules and appreciate some of you are more eager to help someone meeting the minimum system requirements. I only have two slots on my motherboard for DDR2 and so the recommended 8GB was simply was out of my budget. I have been watching memory usage and this has thus far not been an issue especially since I am only trying to get Transmission running. I appreciate prefetch is being disabled and I can live without that for now.

Searched and most similar issues are old and fixed.

I have created the following datasets, Jails remains the propity of root and wheel the rest are all nobody nogroup with ticks all round.

Code:

NAS/Jails
NAS/Share/Media/Movies
NAS/Share/Media/Music
NAS/Share/Media/TVSeries
NAS/Transmission/Downloads
NAS/Transmission/Torrentfiles

My home network router is on 192.168.1.254, and I have given the NAS a fixed IP of 192.168.1.2 and edited the IP range in the router to keep the home network between 1 and 40 to avoid conflics.

Share has been Sharded with CIFS and works great.

Under the Jails config I have changed as follows:

Code:

Jail Root: /mnt/NAS/Jails
IPv4 Network Start Address: 192.168.1.41
IPv4 Network End Address: 192.168.1.50

I have installed the Transmission plugin and can now ping the Jail on 192.168.1.41.

From reading:
https://forums.freenas.org/index.ph...ssion-and-couchpotato-as-a-dlna-server.17165/
I have tried to address the limit of 88 characters creating some folders in the root of the jail using the jails command line as follows:

Code:

root@transmission_1:/ # mkdir -p Downloads                                   
root@transmission_1:/ # mkdir -p Torrentfiles                                
root@transmission_1:/ # mkdir -p Media                                       
root@transmission_1:/ # mkdir -p Media/Movies                                
root@transmission_1:/ # mkdir -p Media/TVSeries                               
root@transmission_1:/ # chmod -R 777 Downloads                               
root@transmission_1:/ # chmod -R 777 Torrentfiles                            
root@transmission_1:/ # chmod -R 777 Media                                   
root@transmission_1:/ # chmod -R 777 Media/Movies                            
root@transmission_1:/ # chmod -R 777 Media/TVSeries

I have then used the add storage option under the jail like so:

Code:

/mnt/NAS/Transmission/Downloads  ->  /Downloads
/mnt/NAS/Transmission/Torrentfiles  ->  /Torrentfiles
/mnt/NAS/Share/Media/Movies  ->  /Media/Movies
/mnt/NAS/Share/Media/TVShows  ->  /Media/TVShows

I have edited the config of transmission to change:

Code:

Watch Directory: /Torrentfiles
Configuration Directory: /
Download Directory: /Downloads

Note these changes don’t save, I have took a copy of the settings.json and the changes show in there just not the FreeNAS GUI Transmission Configuration pop up menu.

This way the config should save to root and the other two should be using storage outside of the jail.

Upon starting Transmission I get:

Code:

Oct 15 00:33:37 freenas kernel: pid 99604 (transmission-daemon), uid 921: exited on signal 11

I have been re-installing again and again to try and figure this out at one point Transmission was running when the config was not changes first but then as soon as I changed it I could not re-start it.

I have also tried not changing the Configuration Directory as I now relise this is not nessaseraly but that was previous to the attempt above.

Tonight ill try a re-install only changing the Watch Directory and Download Directory before running.

Then I will try a re-install running default then stopping and changing Watch Directory and Download Directory before re-running.

Cannot help but feel something is wrong here when it comes to saving the Configuration.

Settings.json contains:

Code:

"dht-enabled": true
"download-dir": "/Downloads"
"encryption": 1
"lpd-enabled": false
"peer-limit-global": 240
"peer-limit-per-torrent": 60
"peer-port": 51413
"port-forwarding-enabled": true
"ratio-limit": "2"
"rpc-authentication-required": false
"rpc-enabled": true
"rpc-password": "{da**Removedbyme**0d3255bfef95601890afd80709"
"rpc-port": 9091
"rpc-username": ""
"rpc-whitelist": ""
"rpc-whitelist-enabled": false
"utp-enabled": true
"watch-dir": "/Torrentfiles"
"watch-dir-enabled": true

Full output from console when I enable Transmission:

Code:

Oct 15 00:10:19 freenas warden: Building new Jail... Please wait...
Oct 15 00:10:19 freenas warden: zfs clone NAS/Jails/.warden-template-pluginjail@clean NAS/Jails/transmission_1
Oct 15 00:10:20 freenas warden: Success!
Oct 15 00:10:20 freenas warden: Jail created at /mnt/NAS/Jails/transmission_1
Oct 15 00:10:20 freenas kernel: bridge0: Ethernet address: 02:08:99:82:70:00
Oct 15 00:10:20 freenas kernel: bridge0: link state changed to UP
Oct 15 00:10:20 freenas kernel: re0: promiscuous mode enabled
Oct 15 00:10:20 freenas kernel: epair0a: Ethernet address: 02:c4:1b:00:0a:0a
Oct 15 00:10:20 freenas kernel: epair0b: Ethernet address: 02:c4:1b:00:0b:0b
Oct 15 00:10:20 freenas kernel: epair0a: link state changed to UP
Oct 15 00:10:20 freenas kernel: epair0b: link state changed to UP
Oct 15 00:10:20 freenas kernel: re0: link state changed to DOWN
Oct 15 00:10:20 freenas kernel: epair0a: promiscuous mode enabled
Oct 15 00:10:20 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Oct 15 00:10:24 freenas kernel: re0: link state changed to UP
Oct 15 00:10:28 freenas notifier: Performing sanity check on nginx configuration:
Oct 15 00:10:28 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Oct 15 00:10:28 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Oct 15 00:10:46 freenas dhclient: New IP Address (re0): 192.168.1.2
Oct 15 00:10:46 freenas kernel: arp: 192.168.1.2 moved from 02:c4:1b:00:0a:0a to 6c:f0:49:6f:6b:68 on epair0b
Oct 15 00:10:46 freenas dhclient: New Subnet Mask (re0): 255.255.255.0
Oct 15 00:10:46 freenas dhclient: New Broadcast Address (re0): 192.168.1.255
Oct 15 00:10:46 freenas dhclient: New Routers (re0): 192.168.1.254
Oct 15 00:33:37 freenas kernel: pid 99604 (transmission-daemon), uid 921: exited on signal 11
Oct 15 00:35:52 freenas manage.py: [common.pipesubr:58] Popen()ing: /sbin/zfs list -H -o name /mnt/NAS/Jails/.warden-template-pluginjail
Oct 15 00:35:52 freenas manage.py: [common.pipesubr:58] Popen()ing: /sbin/zfs get -H origin /mnt/NAS/Jails/transmission_1
Oct 15 00:47:32 freenas kernel: epair0a: link state changed to DOWN
Oct 15 00:47:32 freenas kernel: epair0b: link state changed to DOWN
Oct 15 00:47:32 freenas kernel: re0: link state changed to DOWN
Oct 15 00:47:32 freenas kernel: bridge0: link state changed to DOWN
Oct 15 00:47:32 freenas kernel: re0: promiscuous mode disabled
Oct 15 00:47:35 freenas kernel: ifa_del_loopback_route: deletion failed
Oct 15 00:47:35 freenas kernel: Freed UMA keg (udp_inpcb) was not empty (20 items).  Lost 2 pages of memory.
Oct 15 00:47:35 freenas kernel: Freed UMA keg (udpcb) was not empty (336 items).  Lost 2 pages of memory.
Oct 15 00:47:35 freenas kernel: Freed UMA keg (tcptw) was not empty (100 items).  Lost 2 pages of memory.
Oct 15 00:47:35 freenas kernel: Freed UMA keg (tcp_inpcb) was not empty (30 items).  Lost 3 pages of memory.
Oct 15 00:47:35 freenas kernel: Freed UMA keg (tcpcb) was not empty (12 items).  Lost 3 pages of memory.
Oct 15 00:47:35 freenas kernel: hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Oct 15 00:47:35 freenas kernel: hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
Oct 15 00:47:36 freenas kernel: re0: link state changed to UP
Oct 15 00:47:37 freenas dhclient: New IP Address (re0): 192.168.1.2
Oct 15 00:47:37 freenas dhclient: New Subnet Mask (re0): 255.255.255.0
Oct 15 00:47:37 freenas dhclient: New Broadcast Address (re0): 192.168.1.255
Oct 15 00:47:37 freenas dhclient: New Routers (re0): 192.168.1.254

Appreciate your thoughts, sorry for the size of the thread I imagine people will only ask me for the info later. I hope I have covered everything I need to I have spent three night trying to figure this out.

Edit, found this
https://forums.freenas.org/index.php?threads/transmission-ignoring-settings-json.10846/
I'm going to remove both and restart the jail then Transmission in the hope that it generate a new settings.json somwhere.

Edit still not working not even just running Transmission without adding storage. The switch on the plugin page turns to the on position but no GUI and nothing in console. Still no response to this post.

Ill try a fresh install of FreeNAS onto a fresh formatted hard drive next week to see if Transmission is simply broke with current release.

 

[alexhore]

So I followed the video from the freenas homepage View: http://www.youtube.com/watch?v=Vgh8VAR5iDU
on a fresh setup word for word and it seemed to start but sticking the address in for the GUI does not work and mounting storage results in an error. I fear Transmission does not work on the latest USB 64bit build. Would be great if someone else could try fresh and confirm I'm not going mad.