Error: database schema has changed on 1171 RH8.0 sqlite3

[TC]

This occures after I delete /var/cache/mt-daapd/*

root@redhat mt-daapd-svn-1171]# ./src/mt-daapd -f -d1 -c/etc/mt-daapd.conf
setting dest to 1
Starting with debuglevel 1
Starting rendezvous daemon
Starting signal handler
Initializing database
Starting web server from /usr/local/share/mt-daapd/admin-root on port 3689
Registering rendezvous names
Error getting song count: Misc SQL Error: database schema has changed
Aborting
[root@redhat mt-daapd-svn-1171]# Rendezvous socket closed (daap server crashed?) Aborting.
Aborting

also tried
[root@redhat mt-daapd-svn-1171]# /usr/local/bin/mtd-update -c/etc/mt-daapd.conf
Loading config file: /etc/mt-daapd.conf
Opening database (type: sqlite3, parms: /var/cache/mt-daapd)
Database is already up-to-date
Success!

[rpedde]

That’s a red herring. It can’t get that far if there really is a db problem.

Check the obvious — that the db directory is writable by the runas user.

Beyond that, what does a -d9 look like? Any help there? If not, email me the -d9 (ron at pedde.com)

[TC]

[root@redhat bin]# cat /etc/mt-* | grep runas
# must be writable by the “runas” user.
# runas (required)
runas = nobody

drwxrwxrwx 2 nobody nobody 4096 Jun 4 22:00 mt-daapd
-rw-r–r– 1 nobody nobody 3616768 Jun 5 06:12 songs3.db

[root@redhat mt-daapd-svn-1171]# ./src/mt-daapd -f -d9 -c/etc/mt-daapd.conf
setting dest to 1
Expanding precomments to 256
Expanding precomments to 512
Found 1 tokens in /mnt/public/music
Token 1: /mnt/public/music
Expanding precomments to 1024
Expanding precomments to 2048
Expanding precomments to 4096
Checking existence of /usr/local/share/mt-daapd/admin-root
Checking existence of /usr/local/share/mt-daapd/admin-root
Checking existence of /var/cache/mt-daapd
Checking existence of /var/cache/mt-daapd
Checking existence of /usr/local/share/mt-daapd/plugins
Checking existence of /usr/local/share/mt-daapd/plugins
Loading new config file.
Starting with debuglevel 9
Starting rendezvous daemon
get_ifi_info
intf name=lo AF=2, flags=00000002
intf name=eth0 AF=2, flags=00000002
SetupInterfaceList
mDNS_RegisterInterface: InterfaceID 0808DDD0 192.168.1.6 not represented in list; marking active and retriggering queries
Adding 0808DDE0 redhat.local. (Addr) to active record list
Adding 0808E08C 6.1.168.192.in-addr.arpa. (PTR) to active record list
Not creating HINFO record: platform support layer provided no information
SetupOneInterface: eth0 192.168.1.6 Registered
select(5, 0.000976)
Starting signal handler
Signal handler started
Opening database
Executing: select value from config where term=’version’
Results: 0
mDNS_Execute
select(5, 0.242187)
Initializing database
Executing: select count(*) FROM songs
Executing: select value from config where term=’rescan’
Executing: vacuum
mDNS_Execute
SendQueries: Put Question redhat.local. (Addr) probecount 2
SendQueries: Sending 1 Question 0 Answers 1 Update on 0808DDD0
select(5, 0.100585)
SocketDataReady got a packet from 192.168.1.6 to 224.0.0.251 on interface 192.168.1.6/eth0/2
Received Query from 192.168.1.6 :5353 to 224.0.0.251 :5353 on 0x0808DDD0 with 1 Question, 0 Answers, 1 Authority, 0 Additionals
select(5, 0.100585)
mDNS_Execute
select(5, 0.140625)
mDNS_Execute
SendQueries: Put Question redhat.local. (Addr) probecount 1
SendQueries: Sending 1 Question 0 Answers 1 Update on 0808DDD0
select(5, 0.099609)
SocketDataReady got a packet from 192.168.1.6 to 224.0.0.251 on interface 192.168.1.6/eth0/2
Received Query from 192.168.1.6 :5353 to 224.0.0.251 :5353 on 0x0808DDD0 with 1 Question, 0 Answers, 1 Authority, 0 Additionals
select(5, 0.098632)
mDNS_Execute
select(5, 0.149414)
mDNS_Execute
SendQueries: Put Question redhat.local. (Addr) probecount 0
SendQueries: Sending 1 Question 0 Answers 1 Update on 0808DDD0
select(5, 0.099609)
SocketDataReady got a packet from 192.168.1.6 to 224.0.0.251 on interface 192.168.1.6/eth0/2
Received Query from 192.168.1.6 :5353 to 224.0.0.251 :5353 on 0x0808DDD0 with 1 Question, 0 Answers, 1 Authority, 0 Additionals
select(5, 0.098632)
mDNS_Execute
select(5, 0.149414)
mDNS_Execute
Probing for redhat.local. (Addr) complete
HostNameCallback: redhat.local. (Addr) Name registered (0)
Announcing redhat.local. (Addr) 9
Announcing 6.1.168.192.in-addr.arpa. (PTR) 9
SendResponses: Sending 0 Deregistrations, 2 Announcements, 0 Answers, 0 Additionals on 0808DDD0
SendResponses: Next in 1024 ticks
select(5, 0.079101)
SocketDataReady got a packet from 192.168.1.6 to 224.0.0.251 on interface 192.168.1.6/eth0/2
Received Response from 192.168.1.6 addressed to 224.0.0.251 on 0808DDD0 TTL 255 with 0 Questions, 2 Answers, 0 Authorities, 0 Additionals
select(5, 0.071289)
mDNS_Execute
select(5, 0.885742)
mDNS_Execute
Announcing redhat.local. (Addr) 8
Announcing 6.1.168.192.in-addr.arpa. (PTR) 8
SendResponses: Sending 0 Deregistrations, 2 Announcements, 0 Answers, 0 Additionals on 0808DDD0
SendResponses: Next in 2048 ticks
select(5, 0.100585)
SocketDataReady got a packet from 192.168.1.6 to 224.0.0.251 on interface 192.168.1.6/eth0/2
Received Response from 192.168.1.6 addressed to 224.0.0.251 on 0808DDD0 TTL 255 with 0 Questions, 2 Answers, 0 Authorities, 0 Additionals
select(5, 0.100585)
mDNS_Execute
select(5, 1.894531)
Rows: 1
Starting web server from /usr/local/share/mt-daapd/admin-root on port 3689
Listening on port 3689
Starting server thread
Registering rendezvous names
Processing rendezvous message
Registering mt-daapd._daap._tcp (3689)
Adding 08090C38 mt-daapd._daap._tcp.local. (SRV) to active record list
Adding 08090EE4 mt-daapd._daap._tcp.local. (TXT) to active record list
Adding 080906E0 _services._dns-sd._udp.local. (PTR) to active record list
Adding 0809098C _daap._tcp.local. (PTR) to active record list
Registered service 0, name ‘mt-daapd’, type ‘_daap._tcp’, domain ‘local.’, port 3689
select(5, 0.250000)
Processing rendezvous message
Registering mt-daapd._http._tcp (3689)
Adding 08091810 mt-daapd._http._tcp.local. (SRV) to active record list
Adding 08091ABC mt-daapd._http._tcp.local. (TXT) to active record list
Adding 080912B8 _services._dns-sd._udp.local. (PTR) to active record list
Adding 08091564 _http._tcp.local. (PTR) to active record list
Registered service 1, name ‘mt-daapd’, type ‘_http._tcp’, domain ‘local.’, port 3689
select(5, 0.248046)
Current lock level: 0
Executing: select count(*) FROM songs
Error getting song count: Misc SQL Error: database schema has changed
Aborting
Processing rendezvous message
Rendezvous socket closed (daap server crashed?) Aborting.
Aborting
[root@redhat mt-daapd-svn-1171]#

well that looks bizzare
Initializing database
Executing: select count(*) FROM songs
Executing: select value from config where term=’rescan’
then later it craps doing
Current lock level: 0
Executing: select count(*) FROM songs

…

[rpedde]

I don’t see it.

What sqlite3, and where did you get the packages? I’d like to duplicate this.

I wouldn’t be surprised to hear of problems with something before 3.3.0, as there were large changes in threading. Ideally, you should be running 3.3.6 (isn’t that the latest?) as there were a number of bugs in 3.3.x and 3.3.6 seems pretty stable.

That said, it isn’t as stable as sqlite2. So if you already *are* running 3.3.6, if you move to sqlite 2.8.x (they can both be installed at the same time), I think the problem will go away.

Isn’t a big help, I understand, but I think it will be a working workaround.

— Ron

[TC]

3.0.2
ok older but it ran fine until this update

also one other data point if i wipe the db & let it create a new db
it will load that 1 time but crap on any restart

ok compiled 3.3.6 and it installed the fix all problems flag 🙂

thx Ron you the man
heads up for anyone else running early version of sqlite3

[rpedde]

@TC wrote:

3.0.2
ok older but it ran fine until this update

also one other data point if i wipe the db & let it create a new db
it will load that 1 time but crap on any restart

ok compiled 3.3.6 and it installed the fix all problems flag 🙂

thx Ron you the man
heads up for anyone else running early version of sqlite3

Yeah, go figure. There was a time that it was working fine too, until a particular 3.3.x came out, and then it broke also. Maybe fixing the 3.3.x thing broke the 3.0.2 thing.

Gack. Least it works now.

— Ron

[Author]

Posts