[asterisk-dev] A10 - db.c: Couldn't execute statment: SQL logic error or missing database

[Malcolm C. Davenport]

Howdy,

Could we coax you into open an issue on the issue tracker for this?

----- Original Message -----
> From what I could see reading all the upgrade/changes docs, it looks
> like going to Asterisk-10
> beta 1 would only break all my ConfBrdige stuff, so I figured I'd try
> it and see what happened. I
> didn't change anything from 1.8.5.0. Well, here's what happened.
> 
> Although astdb2sqlite3 was selected in make menuselect, I got this:
> 
> [2011-07-24 15:20:09.476] ERROR[12066] db.c: *** Database conversion
> failed!
> [2011-07-24 15:20:09.476] ERROR[12066] db.c: *** Asterisk now uses
> SQLite3 for its internal
> [2011-07-24 15:20:09.476] ERROR[12066] db.c: *** database. Conversion
> from the old astdb
> [2011-07-24 15:20:09.476] ERROR[12066] db.c: *** failed. Most likely
> the astdb2sqlite3 utility
> [2011-07-24 15:20:09.477] ERROR[12066] db.c: *** was not selected for
> build. To convert the
> [2011-07-24 15:20:09.477] ERROR[12066] db.c: *** old astdb, please
> delete '/var/lib/asterisk/astdb.sqlite3'
> [2011-07-24 15:20:09.477] ERROR[12066] db.c: *** and re-run 'make
> menuselect' and select astdb2sqlite3
> [2011-07-24 15:20:09.477] ERROR[12066] db.c: *** in the Utilities
> section, then 'make && make install'.
> [2011-07-24 15:20:14.477] WARNING[12066] db.c: Unable to open Asterisk
> database '/var/lib/asterisk/astdb.sqlite3': unable to open database
> file
> 
> So I manually ran astdb2sqlite3 against astdb. I make VERY little use
> of astdb, it contains my
> phone registrations, one device state and the last incoming caller
> number for one line. That's it. I
> can read the astdb.sqlite3 with sqlite3 just fine (and from the
> asterisk CLI).
> 
> But, I get a LOT of these messages:
> 
> [2011-07-24 15:36:01.955] WARNING[30154] db.c: Couldn't execute
> statment: SQL logic error or missing database
> [2011-07-24 15:36:01.956] VERBOSE[30154] chan_sip.c: > Saved useragent
> "Grandstream GXW-4008 V1.3A 1.0.5.5" for peer 2026
> [2011-07-24 15:36:01.968] NOTICE[30154] chan_sip.c: Peer '2026' is now
> Reachable. (11ms / 700ms)
> [2011-07-24 15:36:04.391] NOTICE[30154] chan_sip.c: Peer 'rapidvox' is
> now Reachable. (27ms / 700ms)
> [2011-07-24 15:36:05.496] WARNING[30154] db.c: Couldn't execute
> statment: SQL logic error or missing database
> [2011-07-24 15:36:05.496] VERBOSE[30154] chan_sip.c: > Saved useragent
> "Grandstream GXW4104 (HW 1.0, Ch:8) 1.3.4.10" for peer 2201
> [2011-07-24 15:36:05.499] NOTICE[30154] chan_sip.c: Peer '2201' is now
> Reachable. (2ms / 700ms)
> [2011-07-24 15:36:06.211] WARNING[30154] db.c: Couldn't execute
> statment: SQL logic error or missing database
> [2011-07-24 15:36:06.212] VERBOSE[30154] chan_sip.c: > Saved useragent
> "Grandstream GXV3000 1.2.3.7" for peer 2020
> [2011-07-24 15:36:06.214] NOTICE[30154] chan_sip.c: Peer '2020' is now
> Reachable. (2ms / 700ms)
> [2011-07-24 15:36:06.685] WARNING[30154] db.c: Couldn't execute
> statment: SQL logic error or missing database
> [2011-07-24 15:36:06.686] VERBOSE[30154] chan_sip.c: > Saved useragent
> "Grandstream GXW4104 (HW 1.0, Ch:11) 1.3.4.10" for peer 2204
> [2011-07-24 15:36:06.688] NOTICE[30154] chan_sip.c: Peer '2204' is now
> Reachable. (2ms / 700ms)
> [2011-07-24 15:36:07.624] WARNING[30154] db.c: Couldn't execute
> statment: SQL logic error or missing database
> [2011-07-24 15:36:07.625] VERBOSE[30154] chan_sip.c: > Saved useragent
> "Linksys/SPA962-6.1.5(a)" for peer 2022
> [2011-07-24 15:36:07.638] NOTICE[30154] chan_sip.c: Peer '2022' is now
> Reachable. (12ms / 700ms)
> [2011-07-24 15:36:09.477] WARNING[30154] db.c: Couldn't execute
> statment: SQL logic error or missing database
> [2011-07-24 15:36:09.478] VERBOSE[30154] chan_sip.c: > Saved useragent
> "Linksys/SPA3102-5.1.7(GW)" for peer 2205
> 
> I even did a chmod 777 on /var/lib/asterisk/astdb.sqlite3 to see if
> that was the problem. It wasn't.
> 
> I'm running Fedora 14. My sqlite rpm is version 3.6.23.1 Release
> 1.fc14.
> 
> I did go back and enable MeetMe and some other modules and that didn't
> make any difference
> (although I'm sure it would help if I tried to go into a MeetMe conf
> room).
> 
> I didn't open a Jira issue although I couldn't find anyone other issue
> with this error message. I
> figured I should ask around here first as there is a good chance I
> just missed something obvious.
> 
> Dennis
> 
> 
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev

-- 
--------------------------------------------------
Malcolm Davenport
Digium, Inc. | Senior Product Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Tel/Fax: +1 256 428 6252
malcolmd at digium.com