Starting jackcontrol gives error

Raaphorst · Post by **Raaphorst** » Thu Jul 23, 2009 8:13 am

10:10:55.335 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

don't have clue why and what I should do about it

Post by **raboof** » Thu Jul 23, 2009 8:51 am

Raaphorst wrote:10:10:55.335 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

Could you open the 'Messages' window and paste the logging?

Raaphorst · Post by **Raaphorst** » Thu Jul 23, 2009 9:28 am

11:27:37.096 Patchbay deactivated.
11:27:37.327 Statistics reset.
11:27:37.537 ALSA connection graph change.
11:27:38.229 ALSA connection change.
11:27:40.619 Startup script...
11:27:40.619 artsshell -q terminate
sh: artsshell: not found
11:27:41.022 Startup script terminated with exit status=32512.
11:27:41.022 JACK is starting...
11:27:41.023 /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p1024 -n2
no message buffer overruns
jackd 0.116.1
Copyright 2001-2005 Paul Davis and others.
jackd 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
JACK compiled with System V SHM support.
cannot use real-time scheduling (FIFO at priority 10) [for thread -1212041536, from thread -1212041536] (1: Operation not permitted)
cannot create engine
11:27:41.071 JACK was started with PID=8219.
11:27:41.234 JACK was stopped successfully.
11:27:41.235 Post-shutdown script...
11:27:41.235 killall jackd
jackd: no process killed
11:27:41.644 Post-shutdown script terminated with exit status=256.
11:27:43.334 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

Post by **raboof** » Thu Jul 23, 2009 10:48 am

Raaphorst wrote:cannot use real-time scheduling (FIFO at priority 10) [for thread -1212041536, from thread -1212041536] (1: Operation not permitted)

You need to apply the configuration mentioned at http://wiki.linuxmusicians.com/doku.php ... imits.conf and add yourself to the audio group.

After changing that file, if i recall correctly you'll have to log out and back in to have them take effect.

Raaphorst · Post by **Raaphorst** » Sat Jul 25, 2009 8:32 am

do I need to perform the whole real-time kernell fix? like written at http://wiki.linuxmusicians.com/doku.php ... figuration ?

Post by **raboof** » Sat Jul 25, 2009 8:54 am

Raaphorst wrote:do I need to perform the whole real-time kernell fix? like written at http://wiki.linuxmusicians.com/doku.php ... figuration ?

Not to get things working - for this error the 'limits.conf' part should be enough.

If later you decide you decide you want to tune for improved performance you can revisit that page, but it's not strictly necessary.

Raaphorst · Post by **Raaphorst** » Sat Jul 25, 2009 11:49 am

thanks a lot!!

Raaphorst · Post by **Raaphorst** » Fri Jul 31, 2009 10:30 am

the file limits.conf is not writable. is there an easy way to change this?

and do I need to add these lines to that file? it seems that # means it's a comment-line, correct?

spm_gl · Post by **spm_gl** » Fri Jul 31, 2009 11:00 am

you need to be root to edit it. Use sudo. And yes, # is (usually) a comment.

Post by **raboof** » Fri Oct 02, 2009 6:34 am

As this is starting to become a major FAQ, I started http://trac.jackaudio.org/wiki/Troubleshooting

LinuxMusicians

Starting jackcontrol gives error

Starting jackcontrol gives error

Re: Starting jackcontrol gives error

Re: Starting jackcontrol gives error

Re: Starting jackcontrol gives error

Re: Starting jackcontrol gives error

Re: Starting jackcontrol gives error

Re: Starting jackcontrol gives error

Re: Starting jackcontrol gives error

Re: Starting jackcontrol gives error

Re: Starting jackcontrol gives error