Q&A
Import into 8.4, Segmentation Fault 11
Björn Schwab
10-5-17
I try to import a backup from 8.3 into 8.4 and it crashes with Segmentation Fault 11 after a few seconds. Customer is live on 8.3 170716, and we have tried to import backup to 8.4 170914
Agnieszka Klimkiewicz
10-5-17
Hi.

Have you tried to import same backup to 8.3 they are using? It looks like records in some register may be damaged. If so you would not be able to import this backup already to 8.3. You can check what register it is in hansa.log - suspected is register system was importing before Segmentation Fault message. If so as next step you may export this register and try to import just its data to empty system (only with date and numeric format you import before) and if you can do it analise what part of the register is problematic in order to fix it.

Regards


Reply
Björn Schwab
10-5-17
Created byAgnieszka Klimkiewicz15:29 5 Oct 2017
Hi. Have you tried to import same backup to 8.3 they are using? It looks like records in some register may be damaged. If so you would not be able to import this backup already to 8.3. You can check what register it is in hansa.log - suspected is regist
I can import same backup into 8.3 without any problems.

017-09-29 12:24:35 Importing text file: TB170904.TXT
2017-09-29 12:24:35 Database set to unsafe (import and maintenance) mode
2017-10-05 15:36:30 activate language ENG done
2017-10-05 15:36:30 *** running with new mail receiving and parsing ***
2017-10-05 15:36:30 *** Using Clock Replacement ***

2017-10-05 15:36:30 Last session was not properly terminated
2017-10-05 15:36:30 *** using a freelist to keep track of free space ***
2017-10-05 15:36:30 *** RELOAD UI FULLY ***
2017-10-05 15:36:30 *** RELOAD LANGUAGES ***
2017-10-05 15:36:30 activate language ENG
2017-10-05 15:36:30 functiontag HasModHotel modulename modHotel res 0
2017-10-05 15:36:30 activate language ENG done
2017-10-05 15:36:30 Database ID is: BFB4FDFD0854F804C54C1685D5E2C199

2017-10-05 15:36:30 Importing text file: TB171005.TXT
2017-10-05 15:36:30 Database set to unsafe (import and maintenance) mode


In terminal i have a segm fault 11 message.
Reply
Vadym
10-6-17
We also had a problem with import in 8.4.
With segm fault 11, with Killed 9 on Mac and with m4getnewpage(): Failed to allocate virtual memory, GetMemPages() failed on Windows server
Reply
Agnieszka Klimkiewicz
10-6-17
I am not able to repeat this on sample data. So there must be sth. special in this backup that makes problems. Please try to import with parameter

--verbosity=debug-detailed
and look in log what register is problematic for import - the one that system tries to import before the fault message.
Reply
Björn Schwab
10-6-17
Created byAgnieszka Klimkiewicz10:21 6 Oct 2017
I am not able to repeat this on sample data. So there must be sth. special in this backup that makes problems. Please try to import with parameter --verbosity=debug-detailed and look in log what register is problematic for import - the one that system t
2017-10-06 10:22:41 (-1) Database set to unsafe (import and maintenance) mode
2017-10-06 10:22:41 (-1) GetTyps cyblock2,gp->gOldStackSize: 336 ,execp->stackSz: 96
2017-10-06 10:22:41 (-1) failed to find typ enq during import, position 4
2017-10-06 10:22:45 (-1) Settings
2017-10-06 10:22:45 (-1) Settings
Reply
Björn Schwab
10-6-17
Created byBjörn Schwab10:23 6 Oct 2017
2017-10-06 10:22:41 (-1) Database set to unsafe (import and maintenance) mode 2017-10-06 10:22:41 (-1) GetTyps cyblock2,gp->gOldStackSize: 336 ,execp->stackSz: 96 2017-10-06 10:22:41 (-1) failed to find typ enq during import, position 4 2017-10-06 10:22:4
The backup is 6.8GB so I can´t open it and check if that statement is valid.
Reply
Vadym
10-6-17
In our case It's not a problem with Data in Registers. We can successful import DB by parts. We added log in import procedure and saw that a crash goes in different records. Sometimes it in Goods Receipts random records, but if we don't import NL Transactions records, that all Goods Receipts records imported normal.

But after that, if we make a reimport in a 8.4 version, we got this problem again.
Reply
Agnieszka Klimkiewicz
10-6-17
Enter in terminal following command

hexdump -n5 Backup.TXT

where Backup.TXT should be your backup file name or if in subfolder than with directory, and write what reply will you get.
Reply
Björn Schwab
10-6-17
Created byAgnieszka Klimkiewicz11:56 6 Oct 2017
Enter in terminal following command hexdump -n5 Backup.TXT where Backup.TXT should be your backup file name or if in subfolder than with directory, and write what reply will you get.
0000000 65 6e 71 09 0d
0000005
Reply
Agnieszka Klimkiewicz
10-6-17
Your file header is fine. We think it is a bug. Development department is looking into this.
Reply
Björn Schwab
10-7-17
Created byAgnieszka Klimkiewicz19:36 6 Oct 2017
Your file header is fine. We think it is a bug. Development department is looking into this.
:-)
Reply
Agnieszka Klimkiewicz
10-10-17
Hi.
So we think we fixed the bug.
Can you please check your customers backup import into 8.4 2017.10.03 version latest build and let us know. It is available on standardinstall.com after you log in as test version.

Reply
Björn Schwab
10-10-17
Created byAgnieszka Klimkiewicz09:48 10 Oct 2017
Hi. So we think we fixed the bug. Can you please check your customers backup import into 8.4 2017.10.03 version latest build and let us know. It is available on standardinstall.com after you log in as test version.
Thanks. Downloaded 84190407 and it imports the backup.
Reply
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Back to the list
Latest Posts
Re: Re: Periodic Customer Statement
Hello, Kindly please report the bug so that we can further investigate and resolve it. Thank you. Best regards, Benjamin...
11:31 3 May 2024
Re: Client Hansa.HDB
Hi, No changes should have been made that would increase client's HDB file. Please try to delete HANSA.HDB from client folder and reconnect to server and check if it will grow to 30MB again. ...
10:14 30 Apr 2024