[asterisk-bugs] [JIRA] (ASTERISK-30380) Asterisk Crashes/Segfault frequently with sqlite

Wed Dec 28 18:29:06 CST 2022

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261075#comment-261075 ] 

Asterisk Team commented on ASTERISK-30380:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> Asterisk Crashes/Segfault frequently with sqlite
> ------------------------------------------------
>
>                 Key: ASTERISK-30380
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30380
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 20.0.0, 20.1.0
>         Environment: Gentoo Linux x86_64 - Asterisk ebuild in portage tree
>            Reporter: Reuben Farrelly
>            Severity: Major
>
> Asterisk is crashing frequently for me with the following printed in the system dmesg:
> [463264.572879] Code: 49 89 f0 8b b7 80 00 00 00 48 8d 97 88 00 00 00 31 c9 e9 f9 d3 ff ff 66 0f 1f 84 00 00 00 00 00 41 54 41 bc 0d 9c 02 00 55 53 <48> 8b 86 88 01 00 00 8b 10 85 d2 75 5b 48 89 fb 48 8b 7f 30 48 89
> [465079.782571] asterisk[5122]: segfault at 188 ip 00007f785395ed9a sp 00007f78514b5890 error 4 in libpjsip-simple.so.2[7f785395c000+a000] likely on CPU 1 (core 1, socket 0)
> [465079.782580] Code: 49 89 f0 8b b7 80 00 00 00 48 8d 97 88 00 00 00 31 c9 e9 f9 d3 ff ff 66 0f 1f 84 00 00 00 00 00 41 54 41 bc 0d 9c 02 00 55 53 <48> 8b 86 88 01 00 00 8b 10 85 d2 75 5b 48 89 fb 48 8b 7f 30 48 89
> [466895.025012] asterisk[5307]: segfault at 188 ip 00007fdd6445cd9a sp 00007fdd15f8a890 error 4 in libpjsip-simple.so.2[7fdd6445a000+a000] likely on CPU 3 (core 3, socket 0)
> [466895.025028] Code: 49 89 f0 8b b7 80 00 00 00 48 8d 97 88 00 00 00 31 c9 e9 f9 d3 ff ff 66 0f 1f 84 00 00 00 00 00 41 54 41 bc 0d 9c 02 00 55 53 <48> 8b 86 88 01 00 00 8b 10 85 d2 75 5b 48 89 fb 48 8b 7f 30 48 89
> This is with Asterisk-20.0.0 and 20.1.0-rc1.  Gentoo policy is that bundled libraries are not used so I am using the Gentoo portage pjsip (2.13).
> I have followed the instructions around generating a backtrace and will attach these soon.  However in short this is what is printed:
> Thread 71 (Thread 0x7f7865b6f6c0 (LWP 5096)):
> #0  0x00007f7865cc70ca in fdatasync () at /lib64/libc.so.6
> #1  0x00007f786643bc81 in unixSync () at /usr/lib64/libsqlite3.so.0
> #2  0x00007f7866489aab in syncJournal.part.0 () at /usr/lib64/libsqlite3.so.0
> #3  0x00007f7866495786 in sqlite3PagerCommitPhaseOne.part.0 () at /usr/lib64/libsqlite3.so.0
> #4  0x00007f7866496a3b in sqlite3BtreeCommitPhaseOne.part.0 () at /usr/lib64/libsqlite3.so.0
> #5  0x00007f7866498c28 in sqlite3VdbeHalt () at /usr/lib64/libsqlite3.so.0
> #6  0x00007f78664d09a4 in sqlite3VdbeExec () at /usr/lib64/libsqlite3.so.0
> #7  0x00007f78664d3ca6 in sqlite3_step () at /usr/lib64/libsqlite3.so.0
> #8  0x00007f78664d47ad in sqlite3_exec () at /usr/lib64/libsqlite3.so.0
> #9  0x000055f1869c29ec in db_execute_sql (sql=0x55f186b8563b "COMMIT", callback=0x0, arg=0x0) at db.c:315
>         errmsg = 0x0
>         res = 0
>         __FUNCTION__ = "db_execute_sql"
> #10 0x000055f1869c2a9b in ast_db_commit_transaction () at db.c:331
> #11 0x000055f1869c576c in db_sync_thread (data=0x0) at db.c:1148
>         __PRETTY_FUNCTION__ = "db_sync_thread"
> sqlite was updated on this system from 3.39 to 3.40 on November 25th which could be related.  Either way, Asterisk should not be crashing and restarting like this.
> These crashes happen every 30 minutes or so.
> I do not have sqlite configured anywhere in asterisk.

--
This message was sent by Atlassian JIRA
(v6.2#6252)