Satisfactory 1.0 dedicated server

trilkk

trilkk

So, Satisfactory 1.0 came out and it's time to start building again.

However, there's an issue. I'm getting the following anomalies in log output when trying to run the dedicated server (which is using Linux compatibility):
Code: 
LogUnixPlatformFile: Warning: create dir('/path/to/satisfactory/Engine/Saved/Config/LinuxServer/Manifest.ini') failed: errno=21 (Is a directory)
LogUnixPlatformFile: Warning: create dir('/path/to/satisfactory/Engine/Saved/Config/LinuxServer') failed: errno=21 (Is a directory)
LogUnixPlatformFile: Warning: create dir('/path/to/satisfactory/Engine/Saved/Config') failed: errno=21 (Is a directory)
LogUnixPlatformFile: Warning: create dir('/path/to/satisfactory/Engine/Saved') failed: errno=21 (Is a directory)
LogUnixPlatformFile: Warning: create dir('/path/to/satisfactory/Engine/Saved') failed: errno=21 (Is a directory)
LogUnixPlatformFile: Warning: create dir('/path/to/satisfactory/Engine/Saved/Config/LinuxServer/Manifest.ini') failed: errno=21 (Is a directory)

The issue is not limited to the program folder, the same issue persists in the home folder too:
Code: 
[2024.09.20-13.12.43:469][  0]LogStreaming: Warning: Failed to read file '/home/user/.config/Epic/FactoryGame/Saved/SaveGames/ServerSettings.7777.sav' error.
[2024.09.20-13.12.43:469][  0]LogUnixPlatformFile: Warning: create dir('/home/user/.config/Epic/FactoryGame/Saved/SaveGames/ServerSettings.7777.sav') failed: errno=21 (Is a directory)
[2024.09.20-13.12.43:469][  0]LogUnixPlatformFile: Warning: create dir('/home/user/.config/Epic/FactoryGame/Saved/SaveGames') failed: errno=21 (Is a directory)
[2024.09.20-13.12.43:469][  0]LogUnixPlatformFile: Warning: create dir('/home/user/.config/Epic/FactoryGame/Saved') failed: errno=21 (Is a directory)
[2024.09.20-13.12.43:469][  0]LogUnixPlatformFile: Warning: create dir('/home/user/.config/Epic/FactoryGame') failed: errno=21 (Is a directory)
[2024.09.20-13.12.43:469][  0]LogUnixPlatformFile: Warning: create dir('/home/user/.config/Epic') failed: errno=21 (Is a directory)
[2024.09.20-13.12.43:469][  0]LogUnixPlatformFile: Warning: create dir('/home/user/.config/Epic') failed: errno=21 (Is a directory)
[2024.09.20-13.12.43:469][  0]LogUnixPlatformFile: Warning: create dir('/home/user/.config/Epic/FactoryGame/Saved/SaveGames/ServerSettings.7777.sav')

It seems the server process is having problems creating any file or directory. This includes saving the server settings or any game save file through the in-game server manager (after connecting to the server as admin). Funnily enough, playing the game actually works. Unless you shut down the server, it will continue working and serving clients perfectly fine. Of course, since one cannot save, it's impossible to kill the server for any reason (including crash bugs) and continue playing which naturally would make a 40-hour game run quite unsustainable.

Luckily I have old versions of the server saved up, including an old version that worked just fine and was able to save games. Going back in time, I was surprised to find it was printing similar errors to the log. This old version was used to play and complete a beta run of the game just fine at the end of last year. This means it's not some kind of new bug in the dedicated server - it's a bug in my setup and it has appeared sometime after upgrading to 14.1-RELEASE.

My Linux compatibility is enabled:
linux_enable="YES"
The Linux mounts are enabled:
linux_mounts_enable="YES"
The mounts also seem to have been made correctly:
Code: 
linprocfs on /compat/linux/proc (linprocfs, local)
linsysfs on /compat/linux/sys (linsysfs, local)
devfs on /compat/linux/dev (devfs)
fdescfs on /compat/linux/dev/fd (fdescfs)
tmpfs on /compat/linux/dev/shm (tmpfs, local)

Is there any setting regarding Linux compatibility that can block processes from writing files?

Has something regarding the compatibility changed recently?

This is probably the best place to ask.
 
create dir('/path/to/satisfactory/Engine/Saved/Config/LinuxServer/Manifest.ini') failed: errno=21 (Is a directory)

That doesn't make a lot of sense. It is obviously using mkdir(2) on something that should be a file.
 
I very much agree the ERRNO is extremely suspicious. But the dedicated server runs fine on Linux.

Well, I doubt it's fruitful to ask on Coffee Stain forums, but it cannot hurt either.
 
Sorry for not replying - we were content to just run the dedicated server on a friend's Linux box for now.

But to get back to the problem at hand - I did SHELL=/usr/bin/sh chroot /compat/linux/, and was able to create and remove files.
Similarly SHELL=/usr/bin/sh chroot -u myuser /compat/linux/ worked the same way, and creating files and directories was possible.

Before this I also switched to DEFAULT_VERSIONS+=linux=rl9 in /etc/make.conf and reinstalled all Linux packages just in case it would make a difference. It did not.

Trying to run the server from Linux chroot also fails. However, it somehow seems the system was interpreting me as root because it was trying to make stuff under /root/ even if I had used -u myuser for the chroot. This kinda makes sense since there are no users added for Linux and it obviously could not find any user data from anywhere.
In any case, the errors are identical across the board. The dedicated server program cannot create files or directories.
 
You must log in or register to reply here.
Back
Top