search

gilles-chanteperdrix / squeezelite

Automatically exported from code.google.com/p/squeezelite
Other
0 stars 0 forks source link

SqueezeLite crashes, after little more than 1 min. #26

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Starting up Squeezelite
2.
3.

What is the expected output? What do you see instead?
Default

What version of the product are you using? On what operating system?
1.1 on ArchLinux

Please provide any additional information below.
When I load up SqueezeLite, I can see it in the LMS and it works just fine 
playing everything I want. Then after little more than 1 min, I can't see the 
player anymore in LMS, so in order for it to come back , I have to start the 
service again. It will then crash after little more than 1 min again, and I can 
keep doing this, to hear music.

Original issue reported on code.google.com by dannyne...@gmail.com on 25 Apr 2013 at 11:13

GoogleCodeExporter commented 8 years ago 
Please provide more details - can't really diagnose from this.  Are you using 
mp3 if so there's a known bug in some versions of libmad on arm.

Other than that - please start from the command line with "-d all=debug" and 
post the debug messages and anything else you see when it crashes.

Original comment by trio...@btinternet.com on 25 Apr 2013 at 6:51

GoogleCodeExporter commented 8 years ago 
I basically only stream from Spotify 3rd party plugin, and hardly ever play the 
files I have on in my NAS media libary.

So I just tried running the command you told me, "-d all=debug" and it so 
happens that it didn't dissapear from the LMS at all, like it normally does. I 
ran it for nearly 15min, and it kept on playing. Then when I closed it down, 
and run it normally again without the debug it dissapeared after aprox 
1min30sec again. I'm so confused.

Here is the beginning of the log, even though I'm not sure if it helps?:

[root@alarm bin]# ./squeezelite -d all=debug
[16:05:48.770223] stream_init:264 init stream
[16:05:48.772073] stream_init:265 streambuf size: 2097152
[16:05:48.783116] output_init:1305 init output
[16:05:48.783798] output_init:1308 outputbuf size: 3528000
[16:05:48.784535] output_init:1340 requested buffer_time: 20000 period_count: 4 
format: any mmap: 1
[16:05:48.861889] output_init:1366 output: default maxrate: 384000
[16:05:48.885867] output_init:1376 memory locked
[16:05:48.887659] output_thread:583 open output device: default
[16:05:48.901917] alsa_open:269 opened device default using format: S32_LE 
sample rate: 44100 mmap: 1
[16:05:48.902711] alsa_open:317 buffer time: 85328 period count: 4 buffer size: 
3763 period size: 940
[16:05:48.903895] output_init:1399 set output sched fifo rt: 45
[16:05:48.908044] decode_init:101 init decode
[16:05:48.909041] load_faad:534 dlerror: libfaad.so.2: cannot open shared 
object file: No such file or directory
[16:05:48.910320] load_vorbis:216 dlerror: libvorbisidec.so.1: cannot open 
shared object file: No such file or directory
[16:05:48.911490] load_flac:175 dlerror: libFLAC.so.8: cannot open shared 
object file: No such file or directory
[16:05:48.912330] register_pcm:191 using pcm
[16:05:48.913306] load_mad:269 dlerror: libmad.so.0: cannot open shared object 
file: No such file or directory
[16:05:48.914311] load_mpg:176 dlerror: libmpg123.so.0: cannot open shared 
object file: No such file or directory
[16:05:48.915910] discover_server:631 sending discovery
[16:05:48.917208] discover_server:642 got response from: 192.168.0.11:3483
[16:05:48.917423] slimproto:683 connecting to 192.168.0.11:3483
[16:05:48.918061] slimproto:705 connected
[16:05:48.918739] sendHELO:109 mac: 00:25:31:05:9c:53
[16:05:48.919418] sendHELO:111 cap: 
Model=squeezelite,ModelName=SqueezeLite,AccuratePlayPoints=1,HasDigitalOut=1,Max
SampleRate=384000,aif,pcm
[16:05:48.931066] process:407 strm
[16:05:48.931825] process_strm:219 strm command s
[16:05:48.932263] process_strm:284 strm s autostart: 3 transition period: 10 
transition type: 0
[16:05:48.932477] sendSTAT:151 STAT: STMf
[16:05:48.932961] codec_open:150 codec open: 'p'
[16:05:48.933104] pcm_open:172 pcm size: 2 rate: 44100 chan: 2 bigendian: 0
[16:05:48.933582] stream_sock:352 connecting to 192.168.0.11:9005
[16:05:48.934480] stream_sock:381 header: GET 
spotify:track:1qDrWA6lyx8cLECdZE7TV7/stream.pcm?player=00%3A25%3A31%3A05%3A9c%3A
53&start=0&sync=1&id=26 SPOTSTREAM/1.0

[16:05:48.934755] sendSTAT:151 STAT: STMc
[16:05:48.934940] process_strm:307 set fade mode: 0
[16:05:48.935401] process:407 audg
[16:05:48.935833] process_audg:355 audg gainL: 22272 gainR: 22272 adjust: 1
[16:05:48.936010] process:411 unhandled setd
[16:05:48.936484] process:411 unhandled setd
[16:05:48.936886] process:407 aude
[16:05:48.937301] process_aude:338 enable spdif: 1 dac: 1
[16:05:48.937774] process:407 audg
[16:05:48.937910] process_audg:355 audg gainL: 22272 gainR: 22272 adjust: 1
[16:05:49.120912] stream_thread:150 headers: len: 25
SPOTSTREAM/1.0 200 OK

[16:05:49.121706] sendRESP:182 RESP
[16:05:49.126436] process:407 cont
[16:05:49.126613] process_cont:321 cont metaint: 0 loop: 0
[16:05:49.317131] pcm_decode:66 setting track_start
[16:05:49.333011] output_thread:773 track start sample rate: 44100 replay_gain: 
65536
[16:05:49.334006] sendSTAT:151 STAT: STMs
[16:05:49.334250] sendSTAT:151 STAT: STMt
[16:05:50.335780] sendSTAT:151 STAT: STMt
[16:05:51.058466] process:407 strm
[16:05:51.058659] process_strm:219 strm command t
[16:05:51.058759] sendSTAT:151 STAT: STMt

Original comment by dannyne...@gmail.com on 25 Apr 2013 at 9:06

GoogleCodeExporter commented 8 years ago 
I just installed these packages:

libmad
mpg123
faad2
flac

Original comment by dannyne...@gmail.com on 25 Apr 2013 at 9:21

GoogleCodeExporter commented 8 years ago 
There is nothing indicating a crash here - could you run for a while like this 
and see if you can reproduce - otherwise I would look at the startup script to 
see if it can capture more details on a failure (such as create a core dump)

Original comment by trio...@btinternet.com on 27 Apr 2013 at 8:45

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I tried running it last night for about 1h, without any errors. Somehow when 
I'm reporting debugs it's not going down. Maybe part of this problem, is in my 
installation and startup script as you said.

I'm running on a Pogoplug ARM5 with ArchLinux.

This is what I've done to install:

#Install SqueezeLite Player/Client
mkdir -p /usr/local/bin
cd /usr/local/bin

#originally from https://code.google.com/p/squeezelite/downloads/list
wget https://www.dropbox.com/s/ei7fl8i66dyifxc/squeezelite-armv5te-v1.1

#make executable
chmod a+x squeezelite

#download service file
cd /etc/systemd/system
wget https://www.dropbox.com/s/0i0bed1a819o706/squeezelite.service

#start squeezelite
systemctl start squeezelite.service

#autostart squeezelite on reboot
systemctl enable squeezelite.service

Original comment by dannyne...@gmail.com on 27 Apr 2013 at 1:25

GoogleCodeExporter commented 8 years ago 
Another weird thing is, if I open Putty and go to "/usr/local/bin", run the 
"./squeezelite" command, the Squeezelite will run without a problem, but it 
will just "hang" in the putty window, so I'm not able to do anything else, and 
if I terminate the putty window, it will terminate the Squeezelite too.

Original comment by dannyne...@gmail.com on 27 Apr 2013 at 1:29

GoogleCodeExporter commented 8 years ago 
Thats the intended operation - if you want it to run as a daemon and return 
control to the command line you need the -z param.

Original comment by trio...@btinternet.com on 27 Apr 2013 at 2:33

GoogleCodeExporter commented 8 years ago 
Yeah, I did. This is what my service file looks like: 
https://www.dropbox.com/s/0i0bed1a819o706/squeezelite.service

It's done there as -z. Try taking a look. Do I need any more commands?

Original comment by dannyne...@gmail.com on 27 Apr 2013 at 4:16

GoogleCodeExporter commented 8 years ago 
For some reason, I just tried starting SqueezeLite myself by doing the 
"./squeezelite -n PogoPlug_SqueezeLite -z", and now it's been running for 30min 
without a problem. Maybe my service file is wrong?

Original comment by dannyne...@gmail.com on 27 Apr 2013 at 4:35

GoogleCodeExporter commented 8 years ago 
Ok, I just want to update you again, and say that it works flawlessly now, and 
haven't been turning down at all lately. 

I'm curious what Rate and freq it's playing with. Is there a command I can 
punch in, to see this and more?

Original comment by dannyne...@gmail.com on 3 May 2013 at 6:21

GoogleCodeExporter commented 8 years ago 
The best information you will get is from the debug messages - other than that 
you should see information from the server as squeezelite is not designed to 
have a user interface.

Original comment by trio...@btinternet.com on 3 May 2013 at 7:10

GoogleCodeExporter commented 8 years ago 
Closing as no issue identified

Original comment by trio...@btinternet.com on 9 Jul 2013 at 6:46