- This topic has 16 replies, 3 voices, and was last updated 17 years, 7 months ago by
.
-
Posts
-
@lunaticallday wrote:
So, with the nightlies svn1523 the lock_t issue is gone and I’m able to configure and compile without errors:
./configure --disable-mdns --enable-howl --enable-sqliteThe Webinterface behaves like Jens said.
If I click on Playlist I’m getting a reproducable “Segmentation Fault”.
The Soundbridge doesn’t see the server, so I assume there’s a mdns problem with avahi / howl (avahi-daemon is started).
For the mdns thing, I’d need to see a log file. Also, the *next* nightlies will have the newest mDNSResponder, so it would be interesting to see if that owrks with the built-in mdns.
As far as the other issue, what browser are you using? And from what kind of client?
Firefox 2 on linux and windows and IE6 on windows
the 1523-tarball behaves the same under edgy and solaris, except for the segmentation fault, which I don’t get with edgy as stated in this post:
http://forums.fireflymediaserver.org/viewtopic.php?t=5835I’m looking forward to the next nightly. It would be perfect if I could use the built-in mdns on solaris.
@lunaticallday wrote:
Firefox 2 on linux and windows and IE6 on windows
the 1523-tarball behaves the same under edgy and solaris, except for the segmentation fault, which I don’t get with edgy as stated in this post:
http://forums.fireflymediaserver.org/viewtopic.php?t=5835I’m looking forward to the next nightly. It would be perfect if I could use the built-in mdns on solaris.
It’s in the toaster now. Should pop out in a half hour or so.
— Ron
Hello,
I have continued to play with the Solaris version of Firefly-1528. The lock_t issue is gone and it complies fine. But as soon as I try to connect from iTunes it crashes. I should mention that I connect to the server using Rendezvous Proxy because Server and client PC are on different networks.
The server is logging something and then crashes. The pstack of the core file says something like strlen(). Please find the output from pstack core below:
{jheinitz@sun01-hh|/var/log/mt-daapd|62} pstack core
core 'core' of 6668: /usr/local/sbin/mt-daapd -c /usr/local/etc/mt-daapd.conf -d 9 -y -f -m
lwp# 1 / thread# 6
ff0b3218 strlen (0, fe8073cc, 0, ff13f789, 0, fefa82c0) + 80
ff10868c vsnprintf (fe807270, 7fffffff, fefa82b8, fe8073cc, 96150, 0) + 5c
0002f63c pi_log (9, fefa82b8, 0, 0, f423f, 7c290) + 24
fefa2f4c plugin_handler (8f6f8, 4000, 7c800, 7c800, fefa2d04, fefbae68) + 248
0002ef34 plugin_url_handle (8f6f8, 0, 0, 7c800, fe807460, fe806360) + 9c
0001bd64 ws_dispatcher (8f6f8, ff022708, 0, 7aa50, 7aa80, 58000) + 410
ff00b01c _thread_start (8f6f8, 0, 0, 0, 0, 0) + 40
lwp# 2 / thread# 2
ff11ed7c _signotifywait (ff01c000, 0, ff3e7aac, 1000, ff3d4124, ff3e8008) + 8
ff001c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
lwp# 3
ff11c920 _door_return (3, ff01d658, ff01d670, 3, ff01c000, 1) + 10
feffa358 _lwp_start (fefe5d98, 0, 6000, ffbeefd4, 0, 0) + 18
ff001c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
lwp# 4 / thread# 4
ff11c050 _so_accept (6, fea0bc18, ffffffff, fffffff8, 0, 90a1d) + 8
0001a58c ws_mainthread (87978, fefd3d38, 1, ff028d04, 0, 2) + 48
ff00b01c _thread_start (87978, 0, 0, 0, 0, 0) + 40
lwp# 5 / thread# 5
ff009200 private___lwp_cond_wait (ff01cd28, ff01c000, ff01cd10, fe909d30, ff01c000, 0) + 8
ff00b01c _thread_start (0, 0, 0, 0, 0, 0) + 40
thread# 1
feff7d88 cond_reltimedwait (0, 84c60, 0, ff01c000, 0, 0) + 1dc
ff009150 sleep (0, 84a88, 56cc0, 32, ff01c000, 2e50c) + 17c
0002e500 os_wait (2, 56cc0, 0, 7c800, ffbef4a0, 84c30) + 4
000194bc main (8, 56c00, ffbef6c8, 84c1c, 6, 1) + 584
00018ab4 _start (0, 0, 0, 0, 0, 0) + 5c
thread# 3
feffd9b8 _reap_wait (ff020980, 1e924, 0, ff01c000, 0, 0) + 38
feffd710 _reaper (ff01ce00, ff022708, ff020980, ff01cdd8, 1, fe400000) + 38
ff00b01c _thread_start (0, 0, 0, 0, 0, 0) + 40
{jheinitz@sun01-hh|/var/log/mt-daapd|63}
The output on the screen when running it with the following options shows:
/usr/local/sbin/mt-daapd -c /usr/local/etc/mt-daapd.conf -y -d 9 -f
Thread 0: Entering ws_dispatcher (Connection from 10.7.52.125)
Thread 0: got request
Request: GET daap://10.7.53.179:3689/server-info HTTP/1.1
Thread 0: Read: Accept: */*
Thread 0: Adding header *Accept=*/**
Added *Accept=*/**
Thread 0: Read: User-Agent: iTunes/7.0.2 (Windows; N)
Thread 0: Adding header *User-Agent=iTunes/7.0.2 (Windows; N)*
Added *User-Agent=iTunes/7.0.2 (Windows; N)*
Thread 0: Read: Client-DAAP-Version: 3.3
Thread 0: Adding header *Client-DAAP-Version=3.3*
Added *Client-DAAP-Version=3.3*
Thread 0: Read: Client-DAAP-Access-Index: 2
Thread 0: Adding header *Client-DAAP-Access-Index=2*
Added *Client-DAAP-Access-Index=2*
Thread 0: Read: Accept-Encoding: gzip
Thread 0: Adding header *Accept-Encoding=gzip*
Added *Accept-Encoding=gzip*
Thread 0: Read:
Thread 0: Headers parsed!
Checking to see if connection matches close
Nope!
Thread 0: Connection type HTTP/1.1
: Connection: persist
Thread 0: Original URI: daap://10.7.53.179:3689/server-info
Thread 0: Translated URI: /server-info
Thread 0: Preparing to find handler
Thread 0: URI Match!
Thread 0: Time is 1176370580 seconds after epoch
Thread 0: Setting time header
Added *Date=Thu, 12 Apr 2007 09:36:20 GMT*
Added *Connection=keep-alive*
Added *Server=mt-daapd/svn-1528*
Added *Content-Type=text/html*
Added *Content-Language=en_us*
Thread 0: Using non-default handler
in main_auth
Checking url /server-info
Checking url /server-info
Dispatching auth for /server-info to plugin
Checking url /server-info
Checking url /server-info
Dispatching /server-info to daap/svn-1528
in main_handler
Checking url /server-info
Checking url /server-info
Dispatching /server-info to plugin
Checking url /server-info
Checking url /server-info
Dispatching /server-info to daap/svn-1528
Getting uri...
Mallocing privinfo...
Added *Accept-Ranges=bytes*
Added *DAAP-Server=firefly/svn-1528*
Updating Content-Type from text/html to application/x-dmap-tagged
Added *Cache-Control=no-cache*
Added *Expires=-1*
Segmentation Fault (core dumped)
Hope that this information helps to identify the problem.
I’m running Solaris 8 on a Sun-Fire V210.
Best regards
Jens
@jheinitz wrote:
Hope that this information helps to identify the problem.
I’m running Solaris 8 on a Sun-Fire V210.
Best regards
Is it possible to get a gdb backtrace? That would show line number and be a lot easier.
— Ron
Hello Ron,
I installed gdb on the system. I launched:
gdb –exec=/usr/local/sbin/mt-daapd –core=core
In the (gdb) prompt I typed backtrace.
Here is what I got:
{jheinitz@sun01-hh|/var/log/mt-daapd|48} gdb --exec=/usr/local/sbin/mt-daapd --core=core
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.8".
Core was generated by `/usr/local/sbin/mt-daapd -c /usr/local/etc/mt-daapd.conf -f -y -d 9'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libresolv.so.2...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libresolv.so.2
Reading symbols from /usr/lib/libdl.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libdl.so.1
Reading symbols from /usr/lib/libpthread.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libpthread.so.1
Reading symbols from /usr/lib/libnsl.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libnsl.so.1
Reading symbols from /usr/lib/libsocket.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libsocket.so.1
Reading symbols from /usr/local/lib/libid3tag.so.0...done.
Loaded symbols for /usr/local/lib/libid3tag.so.0
Reading symbols from /usr/local/lib/libz.so...done.
Loaded symbols for /usr/local/lib/libz.so
Reading symbols from /usr/local/lib/libsqlite3.so.0...done.
Loaded symbols for /usr/local/lib/libsqlite3.so.0
Reading symbols from /usr/lib/libc.so.1...done.
Loaded symbols for /usr/lib/libc.so.1
Reading symbols from /usr/lib/libmp.so.2...done.
Loaded symbols for /usr/lib/libmp.so.2
Reading symbols from /usr/local/lib/libgcc_s.so.1...done.
Loaded symbols for /usr/local/lib/libgcc_s.so.1
Reading symbols from /usr/platform/SUNW,Sun-Fire-V210/lib/libc_psr.so.1...done.
Loaded symbols for /usr/platform/SUNW,Sun-Fire-V210/lib/libc_psr.so.1
Reading symbols from /usr/lib/libthread.so.1...done.
Loaded symbols for /usr/lib/libthread.so.1
Reading symbols from /usr/local/share/mt-daapd/plugins/out-daap.so...done.
Loaded symbols for /usr/local/share/mt-daapd/plugins/out-daap.so
Reading symbols from /usr/local/lib/libhowl.so.0...done.
Loaded symbols for /usr/local/lib/libhowl.so.0
Reading symbols from /usr/local/share/mt-daapd/plugins/rsp.so...done.
Loaded symbols for /usr/local/share/mt-daapd/plugins/rsp.so
Reading symbols from /usr/local/share/mt-daapd/plugins/ssc-script.so...done.
Loaded symbols for /usr/local/share/mt-daapd/plugins/ssc-script.so
#0 0xff0b3218 in strlen () from /usr/lib/libc.so.1
(gdb) backtrace
#0 0xff0b3218 in strlen () from /usr/lib/libc.so.1
#1 0xff106520 in _doprnt () from /usr/lib/libc.so.1
#2 0xff108694 in vsnprintf () from /usr/lib/libc.so.1
#3 0x0002f644 in ?? ()
(gdb)
I think that this is not what you want, right? Did I miss a flag for the gdb command?
Best regards
Jens
Hi Ron,
I got the information from the other Solaris Thread in the Nightly Feedback. So I ran the binary using gdb and here is what you want 8) :
...
...
Added *DAAP-Server=firefly/svn-1528*
Updating Content-Type from text/html to application/x-dmap-tagged
Added *Cache-Control=no-cache*
Added *Expires=-1*
Program received signal SIGSEGV, Segmentation fault.
0xff0b3218 in strlen () from /usr/lib/libc.so.1
(gdb) bt
#0 0xff0b3218 in strlen () from /usr/lib/libc.so.1
#1 0xff106520 in _doprnt () from /usr/lib/libc.so.1
#2 0xff108694 in vsnprintf () from /usr/lib/libc.so.1
#3 0x0002f644 in pi_log (level=-25136528, fmt=0x7fffffff ) at plugin.c:695
(gdb)
Please let me know if you need more information.
Kind regards
Jens
- The forum ‘Setup Issues’ is closed to new topics and replies.