Transmission stops working after a while

[Tenek]

Hi Community!

I'm having issues with Transmissions (plugin jail).
It was working fine before, I'm not sure what has changed.
After Jail start-up it works for a minute or two and I can't access it after that. All connections are refused. What could cause this? Are there any logs I could check out?
I can post my settings.json here if necessary.

Thanks!

FreeNAS-9.2.1.2-RELEASE-x64.

 

[dlavigne]

Anything related in /var/log/messages of FreeNAS or the jail?

 

[Tenek]

I didn't see anything in Jails /var/log/messages.
On FreeNas I have the following:

Apr 15 16:26:07 freenas notifier: Performing sanity check on nginx configuration :
Apr 15 16:26:07 freenas notifier: nginx: the configuration file /usr/local/etc/n ginx/nginx.conf syntax is ok
Apr 15 16:26:07 freenas notifier: nginx: configuration file /usr/local/etc/nginx /nginx.conf test is successful
Apr 15 16:26:09 freenas kernel: bridge0: Ethernet address: 02:87:d3:8c:f6:00
Apr 15 16:26:09 freenas kernel: bridge0: link state changed to UP
Apr 15 16:26:09 freenas kernel: bge0: promiscuous mode enabled
Apr 15 16:26:09 freenas kernel: epair0a: Ethernet address: 02:46:08:00:0a:0a
Apr 15 16:26:09 freenas kernel: epair0b: Ethernet address: 02:46:08:00:0b:0b
Apr 15 16:26:09 freenas kernel: epair0a: link state changed to UP
Apr 15 16:26:09 freenas kernel: epair0b: link state changed to UP
Apr 15 16:26:09 freenas kernel: epair0a: promiscuous mode enabled
Apr 15 16:26:10 freenas kernel: arp: c0:3f:0e:3e:67:a4 is using my IP address 19 2.168.1.3 on epair0b!
Apr 15 16:26:16 freenas kernel: arp: c0:3f:0e:3e:67:a4 is using my IP address 19 2.168.1.3 on epair0b!
Apr 15 16:26:21 freenas kernel: ifa_del_loopback_route: deletion failed
Apr 15 16:26:21 freenas kernel: Freed UMA keg (udp_inpcb) was not empty (40 item s). Lost 4 pages of memory.
Apr 15 16:26:21 freenas kernel: Freed UMA keg (udpcb) was not empty (336 items). Lost 2 pages of memory.

19 2.168.1.3 is IP address assigned to Jail.

Next thing I noticed, that transmissions-daemon keeps working and downloading content. It is something about UI connectivity only.

 

[dlavigne]

Apr 15 16:26:10 freenas kernel: arp: c0:3f:0e:3e:67:a4 is using my IP address 192.168.1.3 on epair0b!

That's the problem. Typing arp -da from the FreeNAS shell will clear the ARP table. You then need to figure out what is causing the addressing conflict in your network.

 

[Tenek]

Thanks! You nailed it. My router (stupid comcast xfinity modem) was the issue. I have had to reset it factory settings. I might need some real router in the future...