remote execution fail

rbees · 01-18-2016, 12:19 PM

Ladies & Gents

Thanks for all the great help offered on this site.

I have a script that plays an online radio station. It contains one line

Code:

mpg123 http://216.118.106.247:7000

When run locally it work fine, but sometimes when run remotely it fails with

Code:

:~$ radio
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
JackTemporaryException : now quits...
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock

[jack.c:252] error: Failed to open jack client: 0x11
[jack.c:58] warning: FIXME: One needs to wait or write some silence here to prevent the last bits of audio to vanish out of the ringbuffer.
/home/rbees/bin/radio: line 1: 28872 Segmentation fault      mpg123 http://216.118.106.247:7000

I had thought it may be the result of executing it from a ssh/screen terminal but it also fails from just an ssh terminal. It works fine when executed locally.

Any idea what may be causing this?

Note that sometimes remote execution works just fine, so I suspect that it has something to do with running debian testing and packages not being updated to work together like in stable. So there may be nothing I can do about it. But I am curious.

I can see that a socket is not being created or accessed but I have no idea how to fix it. Or it if is something I should fix.

Thanks

jpollard · 01-18-2016, 07:36 PM

Most likely it doesn't have access to an audio output.

There is nothing in ssh that would forward/emulate an audio device.

Run locally you have whatever local audio access is granted via a desktop login.

rbees · 01-19-2016, 04:55 AM

Thanks jpollard,

I don't suppose you have any pointers on where to look? When I get a chance I will look into user permissions. It is the same user locally as well as remotely.

jpollard · 01-19-2016, 05:15 AM

It will depend on what other services are available for forwarding audio. It usually isn't all that secure. Sometimes it requires using ssh to forward network ports, but I have no information on which ones, or what services.

pan64 · 01-19-2016, 05:35 AM

for example if you have a pulseaudio server you need to set PULSE_SERVER on the client (where mpg123 executed) and it will send the sound to that host. But it is only for pulseaudio.
In your case alsa tries to find an audio output and you need to configure it either to use pulse audio server or ???

rbees · 01-25-2016, 05:22 PM

it's working again remotely after the latest round of updates