[slurm-users] Building SLURM with X11 support

[Thekla Loizou]

Hi all,

I managed to solve the issue...xauth was missing from the compute nodes!

I increased the debug level in the slurmd logging and finally figured it 
out.

Thanks again for your help,

Thekla

On 28/5/21 2:15 μ.μ., Marcus Boden wrote:
> Hi Thekla,
>
> these are all the installed packages with x11 in the name:
> libX11
> libX11-common
> libX11-devel
> xorg-x11-apps
> xorg-x11-drv-intel
> xorg-x11-fonts-Type1
> xorg-x11-font-utils
> xorg-x11-proto-devel
> xorg-x11-server-common
> xorg-x11-server-utils
> xorg-x11-server-Xorg
> xorg-x11-utils
> xorg-x11-xauth
> xorg-x11-xbitmaps
> xorg-x11-xinit
> xorg-x11-xkb-utils
>
> Hope that help!
> Marcus
>
>
> On 28.05.21 13:01, Thekla Loizou wrote:
>> Dear Marcus,
>>
>> Thanks a lot once again for the reply.
>>
>> Would it be easy for you to tell me which X development libraries you 
>> have on your system?
>>
>> I cannot find something in the configure script..
>>
>> Thanks,
>>
>> Thekla
>>
>> On 28/5/21 12:56 μ.μ., Marcus Boden wrote:
>>> I have the same in our config.log and the x11 forwarding works fine. 
>>> No other lines around it (about some failing checks or something), 
>>> just this:
>>>
>>> [...]
>>> configure:22134: WARNING: unable to locate rrdtool installation
>>> configure:22176: support for ucx disabled
>>> configure:22296: checking whether Slurm internal X11 support is enabled
>>> configure:22311: result:
>>> configure:22350: checking for check >= 0.9.8
>>> [...]
>>>
>>> Best,
>>> Marcus
>>>
>>>
>>> On 28.05.21 09:26, Bjørn-Helge Mevik wrote:
>>>> Thekla Loizou <t.loizou at cyi.ac.cy> writes:
>>>>
>>>>> Also, when compiling SLURM in the config.log I get:
>>>>>
>>>>> configure:22291: checking whether Slurm internal X11 support is 
>>>>> enabled
>>>>> configure:22306: result:
>>>>>
>>>>> The result is empty. I read that X11 is build by default so I don't
>>>>> expect a special flag to be given during compilation time right?
>>>>
>>>> My guess is that some X development library is missing. Perhaps 
>>>> look in
>>>> the configure script for how this test was done (typically it will try
>>>> to compile something with those devel libraries, and fail). Then see
>>>> which package contains that library, install it and try again.
>>>>
>>>
>