You are here: Home » Topic » 20060307 + sqlite3 on unslung 5.5 still no go

20060307 + sqlite3 on unslung 5.5 still no go

This topic contains 5 replies, has 1 voice, and was last updated by  goodnewscd 11 years, 6 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #196

    goodnewscd

    Platform: Linksys NSLU2
    OS: Unslung 5.5b
    DB version : sqlite3 v3.3.4 build from linux-nslu2.org
    mt-daapd build: 20060307

    This build does not start, or “abort” soon after it start. It works fine if recompile with –enable-sqlite.

    Hope it is not me only

    KK 🙁

    2006-03-07 15:20:43: Starting rendezvous daemon
    2006-03-07 15:20:43: get_ifi_info
    2006-03-07 15:20:43: intf 43220 name=lo AF=2, flags=00000002
    2006-03-07 15:20:43: intf 43220 name=ixp0 AF=2, flags=00000002
    2006-03-07 15:20:43: SetupInterfaceList
    2006-03-07 15:20:43: mDNS_RegisterInterface: InterfaceID 00053B50 192.168.1.2 not represented in list; marking active and retriggers
    2006-03-07 15:20:43: Adding 00053B60 ns.local. (Addr) to active record list
    2006-03-07 15:20:43: Adding 00053E0C 2.1.168.192.in-addr.arpa. (PTR) to active record list
    2006-03-07 15:20:43: Not creating HINFO record: platform support layer provided no information
    2006-03-07 15:20:43: SetupOneInterface: ixp0 192.168.1.2 Registered
    2006-03-07 15:20:43: select(6, 0.000976)
    2006-03-07 15:20:43: Starting signal handler
    2006-03-07 15:20:43: Signal handler started
    2006-03-07 15:20:43: mDNS_Execute
    2006-03-07 15:20:43: select(6, 0.220703)
    2006-03-07 15:20:43: Opening database
    2006-03-07 15:20:43: sqlite3 worker: starting
    2006-03-07 15:20:43: Executing: select value from config where term=’version’
    2006-03-07 15:20:43: Can’t get db version. New database?
    2006-03-07 15:20:43: Results: 0
    2006-03-07 15:20:43: Initializing database
    2006-03-07 15:20:43: Executing: select count(*) FROM songs
    2006-03-07 15:20:43: mDNS_Execute
    2006-03-07 15:20:43: SendQueries: Put Question ns.local. (Addr) probecount 2
    2006-03-07 15:20:43: SendQueries: Sending 1 Question 0 Answers 1 Update on 00053B50
    2006-03-07 15:20:43: select(6, 0.088867)
    2006-03-07 15:20:43: SocketDataReady got a packet from 192.168.1.2 to 224.0.0.251 on interface 192.168.1.2/ixp0/2
    2006-03-07 15:20:43: Received Query from 192.168.1.2 :5353 to 224.0.0.251 :5353 on 0x00053B50 with 1 Question, 0 Answers, s
    2006-03-07 15:20:43: select(6, 0.080078)
    2006-03-07 15:20:43: mDNS_Execute
    2006-03-07 15:20:43: select(6, 0.140625)
    2006-03-07 15:20:43: mDNS_Execute
    2006-03-07 15:20:43: SendQueries: Put Question ns.local. (Addr) probecount 1
    2006-03-07 15:20:43: SendQueries: Sending 1 Question 0 Answers 1 Update on 00053B50
    2006-03-07 15:20:43: select(6, 0.098632)
    2006-03-07 15:20:43: SocketDataReady got a packet from 192.168.1.2 to 224.0.0.251 on interface 192.168.1.2/ixp0/2
    2006-03-07 15:20:43: Received Query from 192.168.1.2 :5353 to 224.0.0.251 :5353 on 0x00053B50 with 1 Question, 0 Answers, s
    2006-03-07 15:20:43: select(6, 0.096679)
    2006-03-07 15:20:43: mDNS_Execute
    2006-03-07 15:20:43: select(6, 0.150390)
    2006-03-07 15:20:43: mDNS_Execute
    2006-03-07 15:20:43: SendQueries: Put Question ns.local. (Addr) probecount 0
    2006-03-07 15:20:43: SendQueries: Sending 1 Question 0 Answers 1 Update on 00053B50
    2006-03-07 15:20:43: select(6, 0.098632)
    2006-03-07 15:20:43: SocketDataReady got a packet from 192.168.1.2 to 224.0.0.251 on interface 192.168.1.2/ixp0/2
    2006-03-07 15:20:43: Received Query from 192.168.1.2 :5353 to 224.0.0.251 :5353 on 0x00053B50 with 1 Question, 0 Answers, s
    2006-03-07 15:20:43: select(6, 0.097656)
    2006-03-07 15:20:43: select(6, 0.000976)
    2006-03-07 15:20:43: mDNS_Execute
    2006-03-07 15:20:43: select(6, 0.140625)
    2006-03-07 15:20:44: mDNS_Execute
    2006-03-07 15:20:44: Probing for ns.local. (Addr) complete
    2006-03-07 15:20:44: HostNameCallback: ns.local. (Addr) Name registered (0)
    2006-03-07 15:20:44: Announcing ns.local. (Addr) 9
    2006-03-07 15:20:44: Announcing 2.1.168.192.in-addr.arpa. (PTR) 9
    2006-03-07 15:20:44: SendResponses: Sending 0 Deregistrations, 2 Announcements, 0 Answers, 0 Additionals on 00053B50
    2006-03-07 15:20:44: SendResponses: Next in 1024 ticks
    2006-03-07 15:20:44: select(6, 0.097656)
    2006-03-07 15:20:44: SocketDataReady got a packet from 192.168.1.2 to 224.0.0.251 on interface 192.168.1.2/ixp0/2
    2006-03-07 15:20:44: Received Response from 192.168.1.2 addressed to 224.0.0.251 on 00053B50 TTL 255 with 0 Questions, 2 s
    2006-03-07 15:20:44: select(6, 0.095703)
    2006-03-07 15:20:44: select(6, 0.000976)
    2006-03-07 15:20:44: mDNS_Execute
    2006-03-07 15:20:44: select(6, 0.890625)
    2006-03-07 15:20:45: mDNS_Execute
    2006-03-07 15:20:45: Announcing ns.local. (Addr) 8
    2006-03-07 15:20:45: Announcing 2.1.168.192.in-addr.arpa. (PTR) 8
    2006-03-07 15:20:45: SendResponses: Sending 0 Deregistrations, 2 Announcements, 0 Answers, 0 Additionals on 00053B50
    2006-03-07 15:20:45: SendResponses: Next in 2048 ticks
    2006-03-07 15:20:45: select(6, 0.097656)
    2006-03-07 15:20:45: SocketDataReady got a packet from 192.168.1.2 to 224.0.0.251 on interface 192.168.1.2/ixp0/2
    2006-03-07 15:20:45: Received Response from 192.168.1.2 addressed to 224.0.0.251 on 00053B50 TTL 255 with 0 Questions, 2 s
    2006-03-07 15:20:45: select(6, 0.096679)
    2006-03-07 15:20:45: Processing rendezvous message
    2006-03-07 15:20:45: Rendezvous socket closed (daap server crashed?) Aborting.
    2006-03-07 15:20:45: Aborting

    #4078

    rpedde
    Participant

    It may be a 3.3.4 issue. I have another 3.3.4 machine that just plain doesn’t work. 3.2.x works fine on multiple platforms, but 3.3.4 doesn’t on any platforms I have.

    The sqlite page show 3.3.4 is a beta (or maybe just out of beta) release, and that heavy work went on in thread-safety, but I can’t seem to make it work, even though this version absolutely follows their threading rules — all database access is handled from a single thread.

    So I dunno. Might just be 3.3.4 breakage.

    #4079

    goodnewscd

    Too bad, but I am happy. There is no problem on my NSLU2 and MP3 files.

    KK :rolleyes:

    #4080

    rpedde
    Participant

    My nslu2 is running sqlite 3.2.1, and it works like a champ. Someone was saying that AmaroK was having problems with sqlite 3.3.4 also, so there is another data point.

    #4081

    rpedde
    Participant

    Dunno… but it works fine with sqlite2.

    #4082

    goodnewscd

    Yes. It is fixed on 20060324 build. sqlite3 + NSLU2 is working now.

    Thanks rpedde and jlbz

    KK 🙂

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.