Linux cook failure: Error: Failed to initialize libwebsockets

Development Platform & Builds
,
1

Hi. I’ve been getting a failure during builds for Linux (Shipping) on an Editor (5.5.1) running on Linux (Kubuntu 24.10, libwebsockets-dev 4.3.3):

AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure)

with the following in the cook log

LogWebSockets: Warning: Lws(Error): OOM allocating 1073741816 fds 
LogWebSockets: Warning: Lws(Error): ZERO RANDOM FD 
LogWebSockets: Error: Failed to initialize libwebsockets

This is the only error I could find in the cook log. Any idea what this would be caused by, considering that I have libwebsockets-dev installed?

2

Hi there @meoblast001

Welcome to the Unreal Engine Community Forum! I pulled a thread from another developer having a similar error. See if this helps! AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure)

3

Hi @meoblast001 ,

I am having the same issue with libwebsockets as well on the same Kubuntu setup!

Have you found out the issue?

It’s pretty annoying that the provided samples cannot be cooked fully…

4

I’ve been having the same issue with my Jenkins Docker Agent using UE 5.5.3.
I’ve done the following and it seems to have helped:

  1. In the Jenkins Docker image, add the following step:
RUN apt-get update && \
    apt-get install -y \
        libssl-dev \
        zlib1g-dev \
        ca-certificates && \
  apt-get clean
  1. In the Jenkins Docker image, add the following step (I think this is what ended up fixing it. Might want to try this before doing the other steps):
RUN echo "* soft nofile 1048576" >> /etc/security/limits.conf && \
    echo "* hard nofile 1048576" >> /etc/security/limits.conf
  1. Disable any plugins that depended on libwebsockets from the uproject file (I don’t think this actually helps as the module still tries to initialise with all dependencies disabled):
		{
			"Name": "EditorTelemetry",
			"Enabled": false
		},
		{
			"Name": "EditorPerformance",
			"Enabled": false
		},
		{
			"Name": "StudioTelemetry",
			"Enabled": false
		}
2 Likes
5

thanks dude!
this worked for me in cloudinit:

write_files:
  - path: /etc/security/limits.conf
    permissions: 0644
    owner: root
    content: |
      * soft nofile 32768
      * hard nofile 32768