moc FATAL_ERROR: Server exited!

Submitted by qinohe on Sun, 2014-05-18 17:15

Forums:

MOC on non-standard platforms

Hi all,

Thanks for your player, I'm enjoying it very much. However, I'm having a problem on the Raspberry Pi.
I'm running Archlinux Arm, Linux 3.12.19-3-ARCH armv6l
mocp -V

This is : Music On Console
Version : 2.5.0-beta2
Revision : 2604
Built : Feb 6 2014 14:24:27
Compiled with : OSS ALSA JACK Network streams resample
Running on : Linux 3.12.19-3-ARCH armv6l
Author : Damian Pietras
Homepage : http://moc.daper.net/
E-Mail : mocmaint@daper.net
Copyright : (C) 2003-2014 Damian Pietras and others
License : GNU General Public License, version 2 or later
Already pasted output on ArchlinuxArm, without answer, which I did not expect perse.
Running the server...
Trying JACK...
FATAL_ERROR: Server exited!
Removed the cache, reinstalled, without success.

A strace shows a SIGCHLD,
<... futex resumed> ) = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
1556 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=1557, si_status=0, si_utime=1, si_stime=5} ---
1556 futex(0xb6b5546c, FUTEX_WAIT_PRIVATE, 1, NULL
1555 <... read resumed> "/dev/shm\n", 4096) = 9
1555 close(9) = 0
1555 wait4(1557, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 1557
1555 munmap(0xb6f0e000, 4096) = 0
1555 open("/proc/cpuinfo", O_RDONLY) = 9
1555 fstat64(9, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
1555 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb6f0e000
1555 read(9, "processor\t: 0\nmodel name\t: ARMv6-compatible proces"..., 1024) = 278
1555 read(9, "", 1024) = 0
1555 close(3) = 0
1555 exit_group(1) = ?
1556 +++ exited with 1 +++
1554 <... read resumed> "", 4) = 0
1554 write(2, "\nFATAL_ERROR: Server exited!\n\n", 30) = 30
1554 close(3
1555 +++ exited with 1 +++
1554 <... close resumed> ) = 0
1554 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=1555, si_status=1, si_utime=0, si_stime=4} ---
1554 exit_group(2) = ?
1554 +++ exited with 2 +++

Thanks for any help, qinohe

Log in to post comments

jcf

Sun, 2014-05-18 23:43

Difficult... Very Difficult

It's very difficult to determine what is happening here. It may or may not be related to the SIGCHLD or some problem connecting to JACK. Unfortunately, your MOC was not built with logging enabled, so that avenue of evidence gathering is denied to us.

However, we have recently committed r2635 which might provide a solution (but it's a long shot).

You may want the check that your JACK server is behaving as intended because I'm not in a position to test or debug the MOC JACK sound driver at this time.

You might also want to check any external commands run using the On... options in your MOC configuration file.

If you are able, then rebuilding MOC (preferably at the current SVN HEAD) configured with --enable-debug, running with the -D option and sending mocmaint the compressed mocp_server_log file would enable further investigation.

Log in to post comments

qinohe

Tue, 2014-05-20 10:40

Thank you very much for your

Thank you very much for your answer.

Have tried to start jack as follows, which gives me an error.

I also tried to build the svn, it failed with the following build file and next the error
PKGBUILD;

ERROR;

Thanks again for any help, or pointers on what to do next

Log in to post comments

jcf

Tue, 2014-05-20 10:48

Missing "cpu MHz"

The line starting with the word "FATAL" when launching JACK is probably the clue you need. I think you need to ask the Raspberry Pi community about that. It's now clear why there is one more process in your original posting's strace output than expected (it's the JACK server), and I'll have a look and see if MOC is reporting on the failure to launch JACK appropriately.

The line preceeding the final "ERROR" during the MOC build suggests you may need to be doing that as root.

There are several additional problems apparant in your build which the Raspberry Pi MOC package maintainer can take up with me if he wishes to e-mail mocmaint.

Log in to post comments

jcf

Tue, 2014-05-20 22:59

On Foreign Threads

I'm also tracking the thread you mentioned above. The libraries mentioned in the messages are not required otherwise JACK would not have started at all. They will no doubt be optional and are dynamically loaded at run time.

It might be useful for you to post the output of cat /proc/cpuinfo. There should be a line there "cpu MHz" for which JACK is looking. If there is no file /proc/cpuinfo then you need to look at whether procfs is enabled in your kernel and the /proc filesystem is mounted (check using the mount command without any arguments).

Log in to post comments

qinohe

Wed, 2014-05-21 09:41

Yes, about the libraries

Yes, about the libraries being optional, I thought so.

Cpuinfo does show output, but no Mhz.

Mount shows the following output

I'm very glad with the help I get, as MOC was playing 24/7 on the RPI (literately), I definitely miss that.

Log in to post comments

jcf

Wed, 2014-05-21 10:04

So Ditch The JACK

That then is the source of your problem: JACK needs it, /proc/cpuinfo doesn't have it, game over!

It's something you'll need to take up with the Raspberry Pi package maintainers, but I'm a little surprised they've let such an obvious problem through.

But do you actually have a need for JACK? MOC should run fine with just ALSA. Try running MOC with the -O "SoundDriver=ALSA" option. If that works you can set that option up permanently in your ~/.moc/config file.

Log in to post comments

qinohe

Wed, 2014-05-21 11:16

Right now I love you

MOC is playing again, that's solved. ;)

You mean the Archlinux ARM packagers I guess, or specifically the Raspberry Pi package maintainers?
Would be nice to see JACK is patched.

Do I need JACK? No, I don't need JACK, ALSA is installed, I immediately changed the config, working OOTB.
What I don't understand, why it has been playing for the last 5 months' with the same config.

Thank you very much jcf, helping me troubleshoot this .

Regards,
qinohe

Log in to post comments

jcf

Wed, 2014-05-21 19:38

The Meaning of Life

You mean the Archlinux ARM packagers I guess...

Yep.

What I don't understand, why it has been playing for the last 5 months with the same config.

The answer to that is simple: something changed. Your purpose in this life is to figure out what.

Log in to post comments

qinohe

Thu, 2014-05-22 12:39

New purpose

Ah right, I already left a comment at ARCHlinux ARM about that.

Yeah, I have found 'My meaning of life', I'm now gonna look for the Holy Grail

The reason, not being able to configure without root rights, was simply a security problem.
mount showed;

So I changed to my /data partition, which doesn't have these options set.

Now the configure part runs smoothly, only make fails.

My PKGBUILD looks like this right now;

The error;

Maybe you have some pointers?
I have a log file at http://pastebin.com/vRkKAd9z
Thanks,
qinohe

Log in to post comments

jcf

Thu, 2014-05-22 20:00

Give Yourself Permission

Well, this is another permissions problem which has probably arisen after having had repeated build attempts as different users. It should be easily solved by setting the directory ownership and permissions correctly and consistantly. (See the -R option of chown(1) and chmod(1).)

But if you need to, start over with a fresh source tree and build as a single user having appropriate permissions.

Log in to post comments

qinohe

Thu, 2014-05-22 20:48

Success

All works well, the change to another build partition, and a few minor adjustments to the PKGBUILD.
I tried the PKGBUILD from the other maintainer, and that also works on that partition.

I'll keep svn version running as it does all it should, and more.

This little problem learned me a lot. Thanks for your patience jcf
Regards, qinohe

Log in to post comments

jcf

Thu, 2014-05-22 22:35

Glad I Could Help

This little problem learned me a lot.

Yes, between the two threads I could almost see you learning as we went along. Very rewarding.

Log in to post comments

jcf

Tue, 2014-06-10 22:15

Also See...

Also see this thread and this thread for further information.

(Thanks to user "trpost" for spotting these.)

Log in to post comments

qinohe

Wed, 2014-06-11 11:45

Jack package patch

Thank you for this information, and trpost for finding this.
I have updated ArchLinuxArm
The idea is, patching Arm package with code provided on Jack audio forum by Fernando Lopez-Lez, until a fix is submitted, although, I don't know if this is appropriate?, but we would be able to use Jack.

Log in to post comments

qinohe

Thu, 2014-06-12 18:27

JACK running on RPI

After learning how to patch, I did it, JACK is running on the PI, need to solve some issues, though.
When all is done, I will make a package with the patch available, for ArchLinuxArm (armv6h)

Log in to post comments

qinohe

Wed, 2014-05-21 09:43

Thanks for looking into

Thanks for looking into JACK.

I reported to Mr.Elendig, the maintainer of the AUR (Arch user repository)package about this, now I can only hope he'll contact you.
The package can be found here https://aur.archlinux.org/packages/moc-svn/

I tried to create a package myself, without success at the moment, I'll try some more, first time, so could take a while.

Log in to post comments

qinohe

Tue, 2014-05-20 10:40

edit; should have used the

edit; should have used the reply button.

Log in to post comments