Broken XML client API extensions

[serxxx]

Howdy,

The page http://wiki.mt-daapd.org/wiki/XML_Client_API describes the XML API, and at the bottom lists a number of extensions specific to the Firefly (née mt-daapd) server. Some of these, at least, appear to be broken in r1450 and r1465. Are these extensions not supported in the Firefly incarnation of mt-daapd? In any case, I doubt that the correct behavior is a crash.

I’m running on Gentoo Linux against SQLite3. The query I’m trying is:

   /databases/1/containers/add?output=readable&org.mt-daapd.playlist-type=0&dmap.itemname=test

The result from curl is:

   curl: (52) Empty reply from server

and in the server logs:

   Jan  4 22:04:31 [mt-daapd] Rendezvous socket closed (daap server crashed?) Aborting._

The strace of one mt-daapd process (I’m guessing the Rendevous one) is:

Process 28651 attached - interrupt to quit

select(6, [4 5], NULL, NULL, {0, 896000}) = 0 (Timeout)

gettimeofday({1167963367, 364156}, NULL) = 0

sendto(5, "20416thaselmaus5local1200"..., 933, 0, {sa_family=AF_INET, sin_port=htons(5353), sin_addr=inet_addr("224.0.0.251")}, 16) = 933

gettimeofday({1167963367, 368816}, NULL) = 0

select(6, [4 5], NULL, NULL, {0, 95703}) = 1 (in [5], left {0, 95703})

recvmsg(5, {msg_name(16)={sa_family=AF_INET, sin_port=htons(5353), sin_addr=inet_addr("192.168.1.2")}, msg_iov(1)=[{"20416thaselmaus5local1200"..., 8952}], msg_controllen=24, {cmsg_len=24, cmsg_level=SOL_IP, cmsg_type=, ...}, msg_flags=0}, 0) = 933

gettimeofday({1167963367, 374187}, NULL) = 0

gettimeofday({1167963367, 375899}, NULL) = 0

gettimeofday({1167963367, 377293}, NULL) = 0

select(6, [4 5], NULL, NULL, {0, 86914}) = 0 (Timeout)

gettimeofday({1167963367, 468070}, NULL) = 0

gettimeofday({1167963367, 469753}, NULL) = 0

select(6, [4 5], NULL, NULL, {127, 893554}) = 1 (in [4], left {89, 584000})

read(4, "", 684)                        = 0

write(2, "Rendezvous socket closed (daap s"..., 58) = 58

write(2, "Abortingn", 9)               = 9

time([1167963405])                      = 1167963405

stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0

stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0

stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3519, ...}) = 0

send(3, "<25>Jan  4 21:16:45 mt-daapd[286"..., 95, MSG_NOSIGNAL) = 95

exit_group(1)                           = ?

Process 28651 detached

and the trace of the second mt-daapd process is:

Process 5925 attached - interrupt to quit

setup()                                 = 0

rt_sigprocmask(SIG_BLOCK, [CHLD], [HUP INT TERM CHLD], 8) = 0

nanosleep({2, 0}, {2, 0})               = 0

rt_sigprocmask(SIG_BLOCK, [CHLD], [HUP INT TERM CHLD], 8) = 0

nanosleep({2, 0}, {2, 0})               = 0

rt_sigprocmask(SIG_BLOCK, [CHLD], [HUP INT TERM CHLD], 8) = 0

nanosleep({2, 0}, 0xbfad9074)           = ? ERESTART_RESTARTBLOCK (To be restarted)

+++ killed by SIGSEGV +++

I don’t know if these traces are at all useful; they certainly don’t tell me much.

Thanks for any help!

[rpedde]

@serxxx wrote:

The page http://wiki.mt-daapd.org/wiki/XML_Client_API describes the XML API, and at the bottom lists a number of extensions specific to the Firefly (née mt-daapd) server. Some of these, at least, appear to be broken in r1450 and r1465. Are these extensions not supported in the Firefly incarnation of mt-daapd? In any case, I doubt that the correct behavior is a crash.

Bug from the migration of daap to a module, I think. I’ll take a closer look at it.

– Ron

[serxxx]

@rpedde wrote:

Bug from the migration of daap to a module, I think. I’ll take a closer look at it.

Were you able to reproduce the crash?

[rpedde]

@serxxx wrote:

@rpedde wrote:

Bug from the migration of daap to a module, I think. I’ll take a closer look at it.

Were you able to reproduce the crash?

Yup. Fixed in r1478. Look for it in next nightlies.

— Ron

[serxxx]

@rpedde wrote:

Yup. Fixed in r1478. Look for it in next nightlies.

Excellent. Thank you.

[Author]

Posts