The solution was to unset the DISPLAY environment variable before starting Jenkins. This issue can be closed.
On Saturday, July 10, 2021 at 7:45:36 PM UTC+3 GI D wrote: > Thanks Mark, > > I see that on both servers /usr/bin/X is running, with the exact same > arguments. What I notice is that the console of this new server (which is a > VM) is black, so I rebooted it, and will try the build a 2nd time. This new > server is running CentOS-7, the older one is running Ubuntu 16.04. > > On Saturday, July 10, 2021 at 6:40:34 AM UTC+3 Mark Waite wrote: > >> On Fri, Jul 9, 2021 at 9:33 PM GI D wrote: >> >>> Thanks Mark, >>> >>> This Jenkins installation is a straight-up copy of the current >>> production one that does not have any such plugin, and where this very test >>> runs OK, as I'm told. >>> >>> >> Thanks for clarification. That likely means that the Jenkins >> installation is not quite a complete copy of the current production one. >> For example, the current production one probably has an X server running >> and accepting requests on localhost. The new one either is not running an >> X server or is not accepting requests to the X server from localhost. An X >> server running and accepting requests is not really something that Jenkins >> provides (at least not without the Xvnc or Xvfb plugins), but seems like it >> must exist on the production server (or those requests would not be >> satisfied). >> >> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/46873897-ac00-4ddf-bdd0-efa3e85cee77n%40googlegroups.com.
