segfault on ubuntu 14,04 that has been running fine..

Get help, report and discuss bugs.
stingray
Posts: 34
Joined: 25 Apr 2014, 08:38

segfault on ubuntu 14,04 that has been running fine..

Post by stingray » 17 Jul 2014, 11:10

so well nzbget have been working since i compiled 1044M i think it was called on startup.. that was like ~20 days or so ago..

sometime during today, it started messing about some segfault.. only thing i can think of is that it might be libpar2 related, but thats cause i know there was people having issues with libpar2, but those errors might be fixed, then this might be something new..

Code: Select all

Jul 17 12:24:16 *hostname* kernel: [693856.153689] nzbget[29741]: segfault at 0 ip 0000000000443394 sp 00007f42b72a9ee8 error 4 in nzbget[400000+98000]
anyway hugbug you might have some insight to were to look for the error..

hardware:
C2550D4I
8gb ecc ram
3x4tb raidz storage pool

software:
Ubuntu 14.04 LTS
ZFSonLinux 0.6.3-2
libpar2 with patches and cancel function
nzbget 1044 and 1055 both with same error.

nzbget starts with both initscript, and manually on nzbget -D, both exits after like a minute with segfault.. error 4.

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: segfault on ubuntu 14,04 that has been running fine..

Post by hugbug » 17 Jul 2014, 12:01

What are the last few lines in the log?

Please compile in debug mode (./configure --enable-debug), then activate option "DumpCore", then start nzbget. The log-file should have the stack trace printed. If it doesn't the core-file helps.

Send the core-file along with compiled nzbget binary at nzbget@gmail.com or upload the files to dropbox or similar if the files are too big. Or install "gdb" and start it as "gdb nzbget core.xxx" (from directory containing nzbget binary and core-file), then use command "bt" to print stack trace.

stingray
Posts: 34
Joined: 25 Apr 2014, 08:38

Re: segfault on ubuntu 14,04 that has been running fine..

Post by stingray » 17 Jul 2014, 14:42

hugbug wrote:What are the last few lines in the log?

Please compile in debug mode (./configure --enable-debug), then activate option "DumpCore", then start nzbget. The log-file should have the stack trace printed. If it doesn't the core-file helps.

Send the core-file along with compiled nzbget binary at nzbget@gmail.com or upload the files to dropbox or similar if the files are too big. Or install "gdb" and start it as "gdb nzbget core.xxx" (from directory containing nzbget binary and core-file), then use command "bt" to print stack trace.
will recompile with debug options and see what the stacktrace says.. will return when i get that info..

thanks

stingray
Posts: 34
Joined: 25 Apr 2014, 08:38

Re: segfault on ubuntu 14,04 that has been running fine..

Post by stingray » 17 Jul 2014, 15:27

had dump core when it crashed.. but that was before i enabled debug in configure..

anyway old core i guess aint much use..

Code: Select all

Core was generated by `/usr/local/bin/nzbget -D'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000435bec in ?? ()
(gdb) bt
#0  0x0000000000435bec in ?? ()
#1  0x00007f3b181a28c0 in ?? ()
#2  0x00000000004362b4 in ?? ()
#3  0x000000000000002f in ?? ()
#4  0x0000000000000000 in ?? ()
guess there is more info if it crashes now with debug on...

stingray
Posts: 34
Joined: 25 Apr 2014, 08:38

Re: segfault on ubuntu 14,04 that has been running fine..

Post by stingray » 17 Jul 2014, 20:19

well still not crashing.. so i guess i'll have to get back to this when ever it happens again.. :/

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: segfault on ubuntu 14,04 that has been running fine..

Post by hugbug » 17 Jul 2014, 20:20

What was in the log before crash?

stingray
Posts: 34
Joined: 25 Apr 2014, 08:38

Re: segfault on ubuntu 14,04 that has been running fine..

Post by stingray » 18 Jul 2014, 14:13

well that i kinda messed up with the option to remove logs on restart..

is there any way to limit logsize? switched that option on after i had a rather large logfile that felt out of proportion..

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: segfault on ubuntu 14,04 that has been running fine..

Post by hugbug » 18 Jul 2014, 14:37

stingray wrote:is there any way to limit logsize?
Soon to be there.

stingray
Posts: 34
Joined: 25 Apr 2014, 08:38

Re: segfault on ubuntu 14,04 that has been running fine..

Post by stingray » 19 Jul 2014, 11:25

finaly crashed...

Code: Select all

stingray@DS380:/development/nas/debug/nzbget$ gdb nzbget core 
GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from nzbget...done.
[New LWP 2508]
[New LWP 2020]
[New LWP 2017]
[New LWP 2021]
[New LWP 2022]
[New LWP 2013]
[New LWP 2018]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/local/bin/nzbget -D'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00000000004aee94 in NZBInfo::GetName() ()
(gdb) bt
#0  0x00000000004aee94 in NZBInfo::GetName() ()
#1  0x000000000050360c in HistoryInfo::GetName(char*, int) ()
#2  0x000000000053a7a2 in HistoryXmlCommand::Execute() ()
#3  0x0000000000533cae in XmlRpcProcessor::Dispatch() ()
#4  0x0000000000533966 in XmlRpcProcessor::Execute() ()
#5  0x0000000000532c19 in WebProcessor::Dispatch() ()
#6  0x00000000005329f8 in WebProcessor::Execute() ()
#7  0x0000000000531feb in RequestProcessor::Run() ()
#8  0x0000000000543640 in Thread::thread_handler(void*) ()
#9  0x00007fe9ae4d6182 in start_thread (arg=0x7fe9a98dd700) at pthread_create.c:312
#10 0x00007fe9ad14630d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
(gdb) 

Code: Select all

Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   nzbget 13.0 (nzbget.cpp:209:Run)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Initializing global thread data (Thread.cpp:145:Init)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating ServerPool (ServerPool.cpp:56:ServerPool)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating Scheduler (Scheduler.cpp:92:Scheduler)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating Thread (Thread.cpp:159:Thread)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating QueueEditor (QueueEditor.cpp:74:QueueEditor)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating QueueCoordinator (QueueCoordinator.cpp:82:QueueCoordinator)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Initializing global decoder (Decoder.cpp:112:Init)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating StatMeter (StatMeter.cpp:215:StatMeter)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating Scanner (Scanner.cpp:119:Scanner)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating Thread (Thread.cpp:159:Thread)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating Thread (Thread.cpp:159:Thread)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating ParChecker (ParChecker.cpp:157:ParChecker)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating Thread (Thread.cpp:159:Thread)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating ParRenamer (ParRenamer.cpp:81:ParRenamer)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating ParCoordinator (ParCoordinator.cpp:120:ParCoordinator)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating PrePostProcessor (PrePostProcessor.cpp:68:PrePostProcessor)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating HistoryCoordinator (HistoryCoordinator.cpp:66:HistoryCoordinator)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating Thread (Thread.cpp:159:Thread)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating UrlCoordinator (UrlCoordinator.cpp:105:UrlCoordinator)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating Thread (Thread.cpp:159:Thread)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Creating FeedCoordinator (FeedCoordinator.cpp:75:FeedCoordinator)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Reading options (nzbget.cpp:228:Run)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Adding server to ServerPool (ServerPool.cpp:89:AddServer)
Sat Jul 19 10:43:22 2014        140641642043264 DEBUG   Deleting old log-file (nzbget.cpp:241:Run)

thats what i got after it crashed..

great with logsize limit..

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: segfault on ubuntu 14,04 that has been running fine..

Post by hugbug » 21 Jul 2014, 10:44

Looks like the crash occurred during restart via web-intreface, is that correct?
Does it crash when you restart again (is it reproducible)?

Post Reply

Who is online

Users browsing this forum: No registered users and 44 guests