Re: [Wrapper-user] Fwd: problems connecting to Xlib

[Leif M. <lei...@ta...>]

Klemens,
This sounds like a display problem.  Are you running the Wrapper as
"./myapp console" or "./myapp start", or is it being stared on system
startup?

Most X Windows applications work by looking for a DISPLAY environment
variable.  If that is not being found then the process will not be
able to display its GUI.

Try adding the following to your wrapper.conf so you get the current
environment dumped to the log file.  This should help debug the
problem.
http://wrapper.tanukisoftware.com/doc/english/prop-environment-dump.html
wrapper.environment.dump=TRUE

Please let me know how this works for you.

Cheers,
Leif

On Tue, Sep 6, 2011 at 5:54 PM, Klemens Loschy <kle...@gm...> wrote:
> Hi,
>
> we are using the service wrapper to start a bamboo remote agent (VM
> running a RHELS 5.6). if the agent is started using the the service
> wrapper, our selenium tests do not work because the browser (firefox)
> can not be opened:
> Xlib: connection to ":10.0" refused by server
> Xlib: Client is not authorized to connect to Server
> Error: cannot open display: :10
>
> When the remote agent is started without the service wrapper,
> everything works as expected. Always root is used to start the remote
> agent.
>
> Can anyone support me by solving this issue?
>
> thank you in advance, br klemensl