Transmission exiting on signal 11/10

Status
Not open for further replies.
Naesstrom

Naesstrom

Contributor
Joined
Jul 10, 2012
Messages
108
So, I used the new built in updater in 9.3 the other day and ran into some problems with my transmission plugin (2.84_1). I've deleted the plugin and reinstalled it but now it keeps shutting down with the message:
Code:
pid 36027 (transmission-daemon), uid 921: exited on signal 10

Sometimes it's signal 11 instead of 10 but other then that I can't find anything different, sometimes it's followed by
Code:
Limiting icmp unreach response from 733 to 200 packets/sec

where the first numbers will change but nothing after that

Now when I think about it, the first thing I changed was the kern.ipc.maxsockbuf since I got some errors relative to that at first.

If anyone have some ideas what I should change I would be happy to hear them!

dmesg
Code:
pid 11164 (transmission-daemon), uid 921: exited on signal 11
Limiting icmp unreach response from 464 to 200 packets/sec
epair3a: link state changed to DOWN
epair3b: link state changed to DOWN
pid 36027 (transmission-daemon), uid 921: exited on signal 10
Limiting icmp unreach response from 735 to 200 packets/sec
ifa_del_loopback_route: deletion failed
Freed UMA keg (udp_inpcb) was not empty (20 items).  Lost 2 pages of memory.
Freed UMA keg (udpcb) was not empty (336 items).  Lost 2 pages of memory.
Freed UMA keg (tcpreass) was not empty (168 items).  Lost 2 pages of memory.
Freed UMA keg (tcptw) was not empty (100 items).  Lost 2 pages of memory.
Freed UMA keg (tcp_inpcb) was not empty (20 items).  Lost 2 pages of memory.
Freed UMA keg (tcpcb) was not empty (16 items).  Lost 4 pages of memory.
hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
pid 56971 (transmission-daemon), uid 921: exited on signal 11
Limiting icmp unreach response from 553 to 200 packets/sec
pid 63702 (transmission-daemon), uid 921: exited on signal 11
Limiting icmp unreach response from 429 to 200 packets/sec
pid 96388 (transmission-daemon), uid 921: exited on signal 11
Limiting icmp unreach response from 715 to 200 packets/sec
pid 13630 (transmission-daemon), uid 921: exited on signal 11
Limiting icmp unreach response from 733 to 200 packets/sec
pid 29630 (transmission-daemon), uid 921: exited on signal 10
Limiting icmp unreach response from 645 to 200 packets/sec
pid 2469 (transmission-daemon), uid 921: exited on signal 10
Limiting icmp unreach response from 323 to 200 packets/sec
pid 27965 (transmission-daemon), uid 921: exited on signal 10
[root@Katrinelund] ~#


Sysinfo:
BuildFreeNAS-9.3-STABLE-201412200530
PlatformAMD Athlon(tm) II X2 215 Processor
Memory7909MB
System TimeThu Dec 25 15:56:22 CET 2014
Uptime3:56PM up 19:13, 1 user
Load Average0.29, 0.95, 0.66
 

Attachments

  • debug-Katrinelund-20141225155308.tgz
    697 KB · Views: 292
M

M@rk

Dabbler
Joined
Sep 24, 2013
Messages
10
I'm having exactly the same issues since the update to transmission last week.
 
D

dlavigne

Guest
From your /var/log/messages, these are troubling:

Dec 25 00:36:13 Katrinelund kernel: Limiting icmp unreach response from 645 to 200 packets/sec
Dec 25 00:44:58 Katrinelund smartd[2308]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors

It looks like the system is directly connected to the Internet (not protected by a firewall/router) so it is exposed to network probes. The real problem seems to be ada1 though, looks like that drive has issues.
 
C

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Yep.. two independent problems (both should be fixed asap).
 
Naesstrom

Naesstrom

Contributor
Joined
Jul 10, 2012
Messages
108
dlavigne said:
From your /var/log/messages, these are troubling:

Dec 25 00:36:13 Katrinelund kernel: Limiting icmp unreach response from 645 to 200 packets/sec
Dec 25 00:44:58 Katrinelund smartd[2308]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors

It looks like the system is directly connected to the Internet (not protected by a firewall/router) so it is exposed to network probes. The real problem seems to be ada1 though, looks like that drive has issues.
Click to expand...

Yeah I know about the pending sectors and I've had that for a while without any problem, just waiting for my replacement HD to arrive before I swap it out!

The icmp is more strange tough, the server is behind my Linksys (Cisco) router, the firewall on it is turned on and no DMZ configured! So is any of these 2 the reason for my Transmission to shut down suddenly?
 
Naesstrom

Naesstrom

Contributor
Joined
Jul 10, 2012
Messages
108
Hmm, so I googled it and ran tcpdump -ni nfe0 "icmp[0]=3 and icmp[1]=3" that outputted the log below, I have no clue what it means but I did understand that transmissions port "51413" was unreachable... not that strange since I forgot to update the port forward in my router when I reinstalled it, did that know and will see if it helps in any way! But what about all the ports?

Code:
[root@Katrinelund] ~# tcpdump -ni nfe0 "icmp[0]=3 and icmp[1]=3"
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on nfe0, link-type EN10MB (Ethernet), capture size 65535 bytes
20:56:43.336302 IP 46.107.231.198 > 192.168.1.12: ICMP 46.107.231.198 udp port 1083 unreachable, length 133
20:56:59.403774 IP 85.24.161.144 > 192.168.1.12: ICMP 85.24.161.144 udp port 51413 unreachable, length 66
20:56:59.731022 IP 182.140.170.59 > 192.168.1.12: ICMP 182.140.170.59 udp port 2638 unreachable, length 66
20:56:59.949197 IP 182.131.11.17 > 192.168.1.12: ICMP 182.131.11.17 udp port 2418 unreachable, length 66
20:57:02.486266 IP 85.24.161.144 > 192.168.1.12: ICMP 85.24.161.144 udp port 51413 unreachable, length 66
20:57:02.776001 IP 46.107.231.198 > 192.168.1.12: ICMP 46.107.231.198 udp port 1083 unreachable, length 133
20:57:02.812853 IP 182.140.170.59 > 192.168.1.12: ICMP 182.140.170.59 udp port 2638 unreachable, length 66
20:57:18.906704 IP 46.107.231.198 > 192.168.1.12: ICMP 46.107.231.198 udp port 1083 unreachable, length 133
20:57:19.474545 IP 188.86.17.72 > 192.168.1.12: ICMP 188.86.17.72 udp port 46395 unreachable, length 133
20:57:34.746786 IP 176.109.225.17 > 192.168.1.12: ICMP 176.109.225.17 udp port 26324 unreachable, length 36
20:57:50.158124 IP 176.109.225.17 > 192.168.1.12: ICMP 176.109.225.17 udp port 26324 unreachable, length 36
20:58:02.972939 IP 192.168.1.18 > 192.168.1.2: ICMP 192.168.1.18 udp port 23865 unreachable, length 36
20:58:02.977010 IP 192.168.1.18 > 192.168.1.2: ICMP 192.168.1.18 udp port 23865 unreachable, length 36
20:58:02.979621 IP 192.168.1.18 > 192.168.1.2: ICMP 192.168.1.18 udp port 23865 unreachable, length 36
20:58:02.980586 IP 192.168.1.18 > 192.168.1.2: ICMP 192.168.1.18 udp port 23865 unreachable, length 36
20:58:03.447009 IP 192.168.1.1 > 192.168.1.18: ICMP 192.168.1.1 udp port 5351 unreachable, length 48
20:58:03.453415 IP 192.168.1.1 > 192.168.1.18: ICMP 192.168.1.1 udp port 5351 unreachable, length 48
20:58:07.160605 IP 176.109.225.17 > 192.168.1.12: ICMP 176.109.225.17 udp port 26324 unreachable, length 36
20:58:07.225289 IP 85.24.161.144 > 192.168.1.12: ICMP 85.24.161.144 udp port 51413 unreachable, length 66
20:58:07.552688 IP 182.140.170.59 > 192.168.1.12: ICMP 182.140.170.59 udp port 2638 unreachable, length 66
20:58:07.668895 IP 188.86.17.72 > 192.168.1.12: ICMP 188.86.17.72 udp port 46395 unreachable, length 133
20:58:07.670127 IP 182.131.11.19 > 192.168.1.12: ICMP 182.131.11.19 udp port 2016 unreachable, length 66
20:58:07.769534 IP 182.131.11.17 > 192.168.1.12: ICMP 182.131.11.17 udp port 2418 unreachable, length 66
20:58:10.255395 IP 85.24.161.144 > 192.168.1.12: ICMP 85.24.161.144 udp port 51413 unreachable, length 66
20:58:10.582284 IP 182.140.170.59 > 192.168.1.12: ICMP 182.140.170.59 udp port 2638 unreachable, length 66
20:58:10.700498 IP 182.131.11.19 > 192.168.1.12: ICMP 182.131.11.19 udp port 2016 unreachable, length 66
20:58:10.799295 IP 182.131.11.17 > 192.168.1.12: ICMP 182.131.11.17 udp port 2418 unreachable, length 66
20:58:50.165506 IP 78.92.227.82 > 192.168.1.12: ICMP 78.92.227.82 udp port 15251 unreachable, length 36
20:59:03.210282 IP 162.219.176.234 > 192.168.1.12: ICMP 162.219.176.234 udp port 40959 unreachable, length 66
20:59:06.225135 IP 162.219.176.234 > 192.168.1.12: ICMP 162.219.176.234 udp port 40959 unreachable, length 66
20:59:06.333142 IP 78.92.227.82 > 192.168.1.12: ICMP 78.92.227.82 udp port 15251 unreachable, length 36
20:59:06.549199 IP 46.63.148.170 > 192.168.1.12: ICMP 46.63.148.170 udp port 41293 unreachable, length 133
20:59:07.238022 IP 62.76.24.226 > 192.168.1.12: ICMP 62.76.24.226 udp port 35940 unreachable, length 133
20:59:22.405314 IP 78.92.227.82 > 192.168.1.12: ICMP 78.92.227.82 udp port 15251 unreachable, length 36
20:59:38.044275 IP 182.140.170.59 > 192.168.1.12: ICMP 182.140.170.59 udp port 2638 unreachable, length 66
20:59:41.041413 IP 182.140.170.59 > 192.168.1.12: ICMP 182.140.170.59 udp port 2638 unreachable, length 66
20:59:52.317853 IP 95.85.38.66 > 192.168.1.12: ICMP 95.85.38.66 tcp port 6669 unreachable, length 68
20:59:52.792680 IP 95.85.38.66 > 192.168.1.12: ICMP 95.85.38.66 tcp port 6669 unreachable, length 68
21:00:00.752291 IP 85.24.161.144 > 192.168.1.12: ICMP 85.24.161.144 udp port 51413 unreachable, length 66
21:00:01.079230 IP 182.140.170.59 > 192.168.1.12: ICMP 182.140.170.59 udp port 2638 unreachable, length 66
21:00:03.759906 IP 85.24.161.144 > 192.168.1.12: ICMP 85.24.161.144 udp port 51413 unreachable, length 66
21:00:04.304008 IP 182.131.11.17 > 192.168.1.12: ICMP 182.131.11.17 udp port 2418 unreachable, length 66
21:00:59.781738 IP 182.140.170.59 > 192.168.1.12: ICMP 182.140.170.59 udp port 2638 unreachable, length 66
21:00:59.953097 IP 85.24.161.144 > 192.168.1.12: ICMP 85.24.161.144 udp port 51413 unreachable, length 66
21:00:59.996399 IP 182.140.158.203 > 192.168.1.12: ICMP 182.140.158.203 udp port 2023 unreachable, length 66
21:01:02.810999 IP 182.140.170.59 > 192.168.1.12: ICMP 182.140.170.59 udp port 2638 unreachable, length 66
21:01:02.958061 IP 85.24.161.144 > 192.168.1.12: ICMP 85.24.161.144 udp port 51413 unreachable, length 66
21:01:04.714596 IP 183.23.115.134 > 192.168.1.12: ICMP 183.23.115.134 udp port 23506 unreachable, length 92
21:01:21.246926 IP 183.23.115.134 > 192.168.1.12: ICMP 183.23.115.134 udp port 23506 unreachable, length 92
21:02:08.925405 IP 192.168.1.2 > 192.168.1.12: ICMP 192.168.1.2 udp port 48196 unreachable, length 130
21:02:20.164869 IP 95.121.240.51 > 192.168.1.12: ICMP 95.121.240.51 udp port 1084 unreachable, length 133
21:02:34.872885 IP 193.53.83.19 > 192.168.1.12: ICMP 193.53.83.19 udp port 49001 unreachable, length 36
21:03:01.571373 IP 182.140.170.59 > 192.168.1.12: ICMP 182.140.170.59 udp port 2638 unreachable, length 66
21:03:01.786200 IP 182.140.158.203 > 192.168.1.12: ICMP 182.140.158.203 udp port 2023 unreachable, length 66
21:03:01.788900 IP 182.131.11.17 > 192.168.1.12: ICMP 182.131.11.17 udp port 2418 unreachable, length 66
21:03:03.245963 IP 84.211.76.50 > 192.168.1.12: ICMP 84.211.76.50 udp port 61092 unreachable, length 66
21:03:03.883930 IP 184.75.212.234 > 192.168.1.12: ICMP 184.75.212.234 udp port 40959 unreachable, length 66
21:03:04.586289 IP 182.140.170.59 > 192.168.1.12: ICMP 182.140.170.59 udp port 2638 unreachable, length 66
21:03:04.801700 IP 182.140.158.203 > 192.168.1.12: ICMP 182.140.158.203 udp port 2023 unreachable, length 66
21:03:06.295274 IP 84.211.76.50 > 192.168.1.12: ICMP 84.211.76.50 udp port 61092 unreachable, length 66
21:03:06.929756 IP 184.75.212.234 > 192.168.1.12: ICMP 184.75.212.234 udp port 40959 unreachable, length 66
21:03:07.685863 IP 182.131.11.19 > 192.168.1.12: ICMP 182.131.11.19 udp port 2016 unreachable, length 66
21:03:10.683129 IP 182.131.11.19 > 192.168.1.12: ICMP 182.131.11.19 udp port 2016 unreachable, length 66
21:03:58.482533 IP 192.168.1.2 > 192.168.1.12: ICMP 192.168.1.2 udp port 48196 unreachable, length 130
21:04:40.478201 IP 85.24.161.144 > 192.168.1.12: ICMP 85.24.161.144 udp port 51413 unreachable, length 66
21:04:43.497242 IP 85.24.161.144 > 192.168.1.12: ICMP 85.24.161.144 udp port 51413 unreachable, length 66
21:04:44.037977 IP 182.140.158.203 > 192.168.1.12: ICMP 182.140.158.203 udp port 2023 unreachable, length 66
21:05:07.349816 IP 182.140.170.59 > 192.168.1.12: ICMP 182.140.170.59 udp port 2638 unreachable, length 66
^C
68 packets captured
3933783 packets received by filter
0 packets dropped by kernel
[root@Katrinelund] ~#
 
Naesstrom

Naesstrom

Contributor
Joined
Jul 10, 2012
Messages
108
So a short update. I've replaced the drive so the pending sector is fixed, also increased the UDP buffer so now I'm not getting the message about limiting icmp etc. but still... Transmission randomly exits by itself.
Made a new install at work on my server there and it does the same there to.
 
nanopete

nanopete

Dabbler
Joined
Nov 20, 2014
Messages
47
Hello, do you have any updates on the random exits? I have the same problem since updating to 9.3, tried disabling my remaining plugins and it still happens.
And how do you find the exit message? "pid 36027 (transmission-daemon), uid 921: exited on signal 10"
 
M

M@rk

Dabbler
Joined
Sep 24, 2013
Messages
10
nanopete said:
Hello, do you have any updates on the random exits? I have the same problem since updating to 9.3, tried disabling my remaining plugins and it still happens.
And how do you find the exit message? "pid 36027 (transmission-daemon), uid 921: exited on signal 10"
Click to expand...

exactly the same issue im having.
 
Radu

Radu

Dabbler
Joined
Mar 7, 2014
Messages
45
I can confirm that the issue is real and i have it too. the plugin version 2.83 was fine, since the upgrade to 2.84(2.84_1) the issue appeared. I have tried to reinstall the plugin, to install transmission (the same version from ports) in a separate jail and the problem is almost the same, the exit signal message is 15 not 10 or 11 like in the original plugin jail.
 
Supa

Supa

Patron
Joined
Jan 10, 2014
Messages
204
same issue:

xIqNjub.png
 
nanopete

nanopete

Dabbler
Joined
Nov 20, 2014
Messages
47
I always receive the signal 10 error and it is followed by a another one on RST response.

Jan 23 11:48:02 freenas kernel: pid 54861 (transmission-daemon), uid 921: exited on signal 10
Jan 23 11:48:03 freenas kernel: Limiting closed port RST response from 249 to 200 packets/sec
 
Joshua Parker Ruehlig

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
if you guys can figure out the cause and solution to this crash i can recompile the transmission PBI and repost it.

but we gotta track down the cause. maybe let's try confirming if it's just in the plugin, or of installing transmission-daemon from pkg in a jail has the same issue.
 
Radu

Radu

Dabbler
Joined
Mar 7, 2014
Messages
45
the pbi crashes with signal 10 and 11 for me , and the install form pkg, in a separate jail, crashes with signal 15 randomly ... i can not figure why ... yet ...

Jan 22 15:46:00 transmission syslogd: exiting on signal 15
 
Naesstrom

Naesstrom

Contributor
Joined
Jul 10, 2012
Messages
108
Thank god, I'm not going crazy then! it's happening to someone else to!
I've also tried to remove the jail and re-install it, even installed it on another server but the same result there.
 
R

Rikkard

Dabbler
Joined
Dec 2, 2014
Messages
26
Same here. Rolled back a snapshot of jail/transmission. It worked, everything is back to normal but freenas gui says I have transmission 2.84 installed, but I don't anymore.
 
Joshua Parker Ruehlig

Joshua Parker Ruehlig

Hall of Famer
Joined
Dec 5, 2011
Messages
5,949
SmallGuy

SmallGuy

Guru
Joined
Jun 7, 2013
Messages
560
Same here with pbi 2.84_1:
Code:
[root@FreeNAS] ~# grep transmission /var/log/messages
/var/log/messages:Jan 23 17:40:06 FreeNAS kernel: pid 44673 (transmission-daemon), uid 816: exited on signal 11
/var/log/messages:Jan 25 23:03:26 FreeNAS kernel: pid 68773 (transmission-daemon), uid 816: exited on signal 10

[Edit]Roll back to 2.82 fix it for me.
 
Last edited:
t3hG04T

t3hG04T

Cadet
Joined
Jan 26, 2015
Messages
7
Having the same problem over here.

Just an idea: are you guys forcing encryption? I am, wondering if it might be related in any way.
 
nanopete

nanopete

Dabbler
Joined
Nov 20, 2014
Messages
47
SmallGuy said:
Same here with pbi 2.84_1:
Code:
[root@FreeNAS] ~# grep transmission /var/log/messages
/var/log/messages:Jan 23 17:40:06 FreeNAS kernel: pid 44673 (transmission-daemon), uid 816: exited on signal 11
/var/log/messages:Jan 25 23:03:26 FreeNAS kernel: pid 68773 (transmission-daemon), uid 816: exited on signal 10

[Edit]Roll back to 2.82 fix it for me.
Click to expand...
Ehm just for the newbie, can you point me in the direction of the easiest way to roll back to an earlier version? Make a new template Jail and find a package with 2.82 and install that in there?
Thank you :)
 
Status
Not open for further replies.

Similar threads

Ustak
  • Locked
Qbittorrent exiting on signal 10/11
Replies
2
Views
1K
Ustak
Ustak
marcevan
  • Locked
Plex mdlna offline
2
Replies
21
Views
4K
panz
panz
Supa
  • Locked
Transmission shuts itself off like every few hours.
Replies
2
Views
919
dlavigne
D
R
  • Locked
FreeNAS 10 - Plex and Transmission situation
Replies
8
Views
6K
cmh
cmh
alexhore
  • Locked
transmission-daemon exited on signal 11
Replies
1
Views
2K
alexhore
alexhore
Top