search

andig / moode

Moode audio distribution
3 stars 3 forks source link

player_wrk log #10

Closed andig closed 9 years ago

andig commented 9 years ago

I've finally broken my install: changed (digiamp+) mixer to hardware and now:

any idea where to check? log file?

Can I trigger a frist-time install from the command line? player_wrk seems to support a first time install?

moodeaudio commented 9 years ago

Ouch!

Is this with virgin 2.1 ?

On Aug 17, 2015, at 12:51 PM, andig notifications@github.com wrote:

I've finally broken my install: changed (digiamp+) mixer to hardware and now:

now audio (also after reboot) mpd-config hangs when called twice after first call player_wrk starts hogging all cpu any idea where to check? log file?

— Reply to this email directly or view it on GitHub https://github.com/andig/moode/issues/10.

andig commented 9 years ago

Hehe, mine is far from virgin. I'll try resetting repo to first commit and check if it works. To see the delta a log file would be good as otherwise its a black box, but there is none, right?

andig commented 9 years ago

And do you know if digiamp plus should work with hw mixer?

moodeaudio commented 9 years ago

IQaudIO DigiAMP+ works perfect w hardware volume and logarithmic curve. I have one connected to HSU STF-2 sub and KEF Q60 mains.

On Aug 17, 2015, at 2:34 PM, andig notifications@github.com wrote:

And do you know if digiamp plus should work with hw mixer?

— Reply to this email directly or view it on GitHub https://github.com/andig/moode/issues/10#issuecomment-131919535.

moodeaudio commented 9 years ago

Ive had PHP hang when I accidentally fat-fingerer php.ini and half a commented setting became uncommented. It took me two days to work that one out...

On Aug 17, 2015, at 2:31 PM, andig notifications@github.com wrote:

Hehe, mine is far from virgin. I'll try resetting repo to first commit and check if it works. To see the delta a log file would be good as otherwise its a black box, but there is none, right?

— Reply to this email directly or view it on GitHub https://github.com/andig/moode/issues/10#issuecomment-131918912.

andig commented 9 years ago

Mhm. Seems something (definitely not me) has changed permissions for /run to something else than 777 which breaks session writing and may have got the worker stuck.

andig commented 9 years ago

I'll add some logging. Still gets stuck but I can see that its in the worker, just not sure why yet...

andig commented 9 years ago

Turned out to be a PHP change with version 5.4 and following: http://stackoverflow.com/questions/32139840/why-cant-daemon-attach-to-php-session/32164649#32164649

moodeaudio commented 9 years ago

Nice work tracking that one down :-) Is there a patch?

On Aug 23, 2015, at 7:55 AM, andig notifications@github.com wrote:

Turned out to be a PHP change with version 5.4 and following: http://stackoverflow.com/questions/32139840/why-cant-daemon-attach-to-php-session/32164649#32164649 http://stackoverflow.com/questions/32139840/why-cant-daemon-attach-to-php-session/32164649#32164649 — Reply to this email directly or view it on GitHub https://github.com/andig/moode/issues/10#issuecomment-133821476.

andig commented 9 years ago

See this https://github.com/andig/moode/commit/4f4f949f5903c0dbcb42f0559ea2af79d1e7392b for part of a bigger update- all session read and write access is wrapped in a non-root-user section that allows access to the actual session file (though not much else...)