TW-858 |
Agent fails if it can't connect to X display |
|
0
|
|
I ssh into a remote machine and start an agent.
At this point everything runs OK because ssh is set up to do X forwarding, so any process that needs an X server can use my local machine.
I then put the agent process into the background and log out of my remote session. The agent can no longer connect to my X server on my local machine.
Now I get an error whenever I try to run an Inspections build. I attach the log.
Looks the same as TW-773
Environment: RH Linux on headless machine
Issue wasresolved
At this point everything runs OK because ssh is set up to do X forwarding, so any process that needs an X server can use my local machine.
I then put the agent process into the background and log out of my remote session. The agent can no longer connect to my X server on my local machine.
Now I get an error whenever I try to run an Inspections build. I attach the log.
Looks the same as TW-773
Environment: RH Linux on headless machine
Issue wasresolved
Sorry for inconvenience.
Thank you.
to fix this?
Other possibility, you can run Xvfb, which is a virtual frame buffer. We run it with:
/usr/X11R6/bin/Xvfb :0 -screen 0 1600x1024x16
and have a display to point to at :0.
I'll try and find Xvfb and give it a go.
Inspections should be able to run completely headlessly - if it needs path variables and they haven't been defined in the build configuration it should just crash giving the name of the variable to define. In my case it's doubly annoying because the output directory is specified as part of the build.