Startup Issue with Palworld - Palworld won't start

System Information

Field Value
Operating System Linux - Debian GNU/Linux 12 on x86_64
Product AMP ‘Phobos’ v2.6.0.6 (Mainline)
Virtualization None
Application Palworld
Module GenericModule
Running in Container No
Current State Failed

Problem Description

Issue

The error messages say there’s logs I can look at but I’ve checked the deployment logs on the main section, the console, and the event logs and I’m not seeing any relevant error messages. Also, I’m running inside the docker version of AMP (never had issues with this, no config changes here). Also, I can’t start either of my minecraft instances. It says Java isn’t found even though I’ve run su -l amp and java --version returns Temurin 21. Not sure if it’s related. Could be a permissions thing since I sometimes run chmod -R and I might’ve run it destructively, but I don’t know where to get more detailed logs.

Reproduction Steps

  • Update AMP
  • Update to Advanced License
  • Update all instance to advanced licenses with ampinstmgr reactivate (nothing was starting before) (I want to use ldap after this is fixed)
  • Start palword (Haven’t started this in a while)

Let’s start with one issue at a time. Right click the Palworld instance and View Logs to get the latest where you tried to start and share it here.

Ahhhhh these are the logs I wanted. Here:

[00:00:00] [Scheduler Info/52]    : Rollover from previous log file: AMP_Logs/AMPLOG 2024-12-01 23-30-22.log
[02:32:47] [System Activity/27]   : Authentication attempt for user shirom from 127.0.0.1
[02:32:48] [System Activity/26]   : Authentication success
[02:32:49] [Core:shirom Activity/30] : Starting the application.
[02:32:49] [Generic:shirom Info/30] : Merging config file ./palworld/2394010/Pal/Saved/Config/WindowsServer/PalWorldSettings.ini (Template) using Unicode (UTF-8) encoding.
[02:32:49] [Generic:shirom Info/30] : Merging config file ./palworld/2394010/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini (Template) using Unicode (UTF-8) encoding.
[02:32:49] [Generic:shirom Error/30] : PlatformException
[02:32:49] [Generic:shirom Error/30] : [0] (PlatformException) : An error occurred trying to start process '/home/amp/.ampdata/instances/cumpissfart01/palworld/2394010/Pal/Binaries/Linux/PalServer-Linux-Shipping' with working directory '/home/amp/.ampdata/instances/cumpissfart01/palworld/2394010'. Permission denied
[02:32:49] [Generic:shirom Error/30] :    at Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
   at Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
   at ModuleShared.AMPProcess.Start()
   at GenericModule.GenericApp.DoAppStartup(Boolean IsUpdating)
   at GenericModule.GenericApp.Start()

It is a permissions thing. I’m going to try to change the permissions on that directory and see how it goes.

You can open CMD as admin and run ampinstmgr fixPerms to hopefully resolve that. Do it while AMP is completely stopped (check Task Manager to make sure).

Preferable to run that in a root shell on Linux xD

It works on Windows too, from what Mike has said.

Right, but the OP is on Linux

Well, I’ll be damned. I don’t know what I saw that said Windows, unless it’s the directory in the log. Lol

ampinstmgr fixperms did not fix the problem. I tried running chown -R amp:amp /home/amp/.ampdata/ which also didn’t work. Both commands exited successfully.

Looking at the file that failed to run, it did not have execute permissions even after running ampinstmgr fixperms. Running chmod +x <failing file> worked. Looks like ampinstmgr fixperms doesn’t add execute bits or maybe it doesn’t know what the palworld executeable is. Maybe something for you guys to look into.

But looks like things are solved! Thanks!

Also, the logs tip helped me notice my Minecraft instances were set to java 21 and only java 17 was found. That’s fixed too.

One tip for your UI guys, there’s way too many places to check logs in this application which makes it confusing. The event log tab seems the most useless and the view logs seems the most useful but it’s hidden under a right click menu.

I suspect if you just updated the server inside the instance then steamcmd would have sorted the issue with the binary not being executable. Servers installed via steamcmd don’t need the executable bit set separately unless the devs have botched the steam upload

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.