|
From: Klemens L. <kle...@gm...> - 2011-09-06 13:41:22
|
Hi, set > env.txt show "DISPLAY=:10.0". Is there anything else I look after? 2011/9/6 Leif Mortenson <lei...@ta...>: > Klemens > If you can't upgrade, then try adding the following line to your shell > script just before the Wrapper is launched: > > set > env.txt > > This will store the current environment into a file. > > I am sure the problem is the DISPLAY variable though. > > Cheers, > Leif > > On Tue, Sep 6, 2011 at 9:47 PM, Klemens Loschy <kle...@gm...> wrote: >> Hi, >> >> unfortunately the update won't happen in near future. Things are bit >> complicated when you are trying to change a peace of software... Seems >> that 3.2.3 is installed. >> >> Sorry, br klemensl >> >> 2011/9/6 Leif Mortenson <lei...@ta...>: >>> Klemens, >>> Which version of the Wrapper are you using? The >>> wrapper.environment.dump property was added in version 3.5.0. If you >>> are using an older version, please upgrade to 3.5.11. That won't fix >>> your problem but it will let you investigate the issue. >>> >>> Cheers, >>> Leif >>> >>> On Tue, Sep 6, 2011 at 8:20 PM, Klemens Loschy <kle...@gm...> wrote: >>>> Hi, >>>> >>>> thank you very much for the quick and helpful reply. >>>> >>>> The app is started on system startup. i have stopped the wrapper with >>>> ./myapp stop and started the it again with ./myapp start -> same >>>> problem. when i start the bamboo remote agent via ./myapp console, >>>> everything works fine. prompting the env variable $DISPLAY in the >>>> shell shows me ":10.0", that should work. so only when the wrapper is >>>> started in daemonized mode, i have this display issues. unfortunately >>>> i am not able to dump the environment by adding the >>>> wrapper.environment.dump=TRUE attribute. >>>> >>>> thx, br klemensl >>>> >>>> 2011/9/6 Leif Mortenson <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 > > ------------------------------------------------------------------------------ > Special Offer -- Download ArcSight Logger for FREE! > Finally, a world-class log management solution at an even better > price-free! And you'll get a free "Love Thy Logs" t-shirt when you > download Logger. Secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsisghtdev2dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |