Update Failure with Palworld - Palworld Server will not update to 1.0.3

Technical Support
, ,
1

System Information

Field Value
Operating System Linux - Debian GNU/Linux 13 on x86_64
Product AMP ‘Proteus’ v2.8.0.4 (Mainline)
Virtualization Docker
Application Palworld
Module GenericModule
Running in Container Yes
Current State Stopped

Problem Description

Issue

Redirecting stderr to '/home/amp/Steam/logs/stderr.txt'
Logging directory: '/home/amp/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logo
Steam Console Client (c) Valve Corporation - version 1785799152
-- type 'quit' to exit --
Loading Steam API...OK
force_install_dir "2394010"
Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
app_update 2394010 -beta public validate
 Update state (0x0) unknown, progress: 0.00 (0 / 0)
Error! App '2394010' state is 0x226 after update job.
quit
Unloading Steam API...OK
Redirecting stderr to '/home/amp/Steam/logs/stderr.txt'
Logging directory: '/home/amp/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logo
Steam Console Client (c) Valve Corporation - version 1785799152
-- type 'quit' to exit --
Loading Steam API...OK
force_install_dir "2394010"
Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
app_update 2394010 -beta public validate
 Update state (0x0) unknown, progress: 0.00 (0 / 0)
Error! App '2394010' state is 0x226 after update job.
quit
Unloading Steam API...OK

Reproduction Steps

  • Ran the AMP update, says it is latest version
  • Stopped Instance, made a backup, and tried to update inside instance
  • Viewed the console and noticed Error! App ‘2394010’ state is 0x226 after update job.
2

This is normally an out of space error.

3

Yes, I saw that but it didn’t look like the VM was out of space. But of course it was…

The following fixed my issue:

  1. Increased size of virtual disk from hypervisor
  2. Booted VM into GParted Live
  3. Extend vdisk to include more disk space
  4. Apply and shutdown
  5. Boot up VM
  6. List disks and storage: 
    • df -h
  7. List file system size: 
    • lsblk
  8. Since this should be lvm, run lvextend: 
    • lvextend -l +100%FREE <logical volume>

    • Mine specifically was:

      • lvextend -l +100%FREE /dev/mapper/ubuntu--vg-ubuntu--lv
  9. Resize the file system so it can use all of that space 
    • resize2fs <file system path>

    • Mine was

      • resize2fs /dev/mapper/ubuntu--vg-ubuntu--lv
  10. Re-run df -h and lsblk to verify total available has increased
  11. Restart VM and restart the updates to instances