Page 1 of 1

Segmentation fault after update

PostPosted: Wed Sep 09, 2015 5:30 pm
by Dcdata
Hi Guys

After running the update tng-update-1_1_1_12_2014 on a tng system we get a segmentation fault.

I ran the following command:
Code: Select all
strace -f ./tng 2> full.log


The full.log file is attached to this post.

Please can you help us determine the reason why we are getting a segmentation fault.

Re: Segmentation fault after update

PostPosted: Fri Sep 11, 2015 3:56 pm
by Leon van Heerden
Hi,
Did you do an export for LANG=C before you ran the TNG like this?

So can you try this:
Code: Select all
export LANG=C
strace -f -s 255 ./tng 2> trace.log


Leon

Re: Segmentation fault after update

PostPosted: Mon Sep 14, 2015 8:42 am
by Dcdata
Hi Leon

Thank-you for your reply.

We ran the code as you asked and have attached the trace.log file.

Please le us know if we can assist you any further.

Re: Segmentation fault after update

PostPosted: Tue Sep 22, 2015 8:55 am
by Leon van Heerden
I have looked at this log and can't see what is causing the crash.
I am investigating further and will give more feedback/suggestions shortly.
Leon

Re: Segmentation fault after update

PostPosted: Mon Sep 28, 2015 12:26 pm
by Leon van Heerden
This issue was the dial code that was used to build the Exchange.Dat file, was not a known number. This normally causes a blank database to be build in windows, but it seems to cause the Linux version to crash with this segmentation fault.
I looked up a number int he same area as this client and entered the first 6 digits from the Telkom number as the LocalNumber. There after the exchange build normally and TNG started.

Code: Select all
[PLUGIN]
localnumber=0114440000
localcode=011


The error was actually displayed in the tng.log when it started.