#Trying to update the server from b42.15 to b42.16.3

1 messages · Page 1 of 1 (latest)

solar temple
fossil scarab
#

Typically the patches aren't compatible with each other. You have to start over.

#

The patch notes

#

@solar temple

solar temple
magic forge
# solar temple Well... people are somehow using a mod to convert it into a supported format

if you're sure that the java patch is active and functioning on your server, the fact that the issue is recurring would mean that that element is being actively re-added to the dictionary after the java patch removes it, likely because some 42.15 files did not get properly deleted during your server's upgrade (and you would be having the same error even with a fresh wipe)

does this file exist in the installation on your server? (unsure of absolute path, it will vary depending how you're hosting) -- media/scripts/generated/entities/misc/entity_logstack.txt
if you have that file on your server, try deleting it. it should not be there in 42.16

solar temple
magic forge
#

alternately, do a complete repair/reinstall of the server, then do the java patch again (it will have been overwriten in the repair/reinstall process)

#

some hosts just aren't reliable about deleting files that are removed in game updates

#

and those dangling files would be affecting you even with a fresh save

magic forge
solar temple
#

No, after I deleted those two files, it started complaining about ISCheatPanelUI.lua

magic forge
#

"file does not exist on client" sort of message?

magic forge
#

these are all just files that existed in 42.15, but don't exist in 42.16 (and your server host method didn't remove them). you can keep deleting them from the server one by one and eventually you'll be ok, or you can just do a full reinstall of the server

#

problem isn't your save, it's the game installation

#

how is your server hosted?

solar temple
solar temple
magic forge
#

I'm not totally familiar with pterodactyl's capabilities for reinstall/repair, unfortunately. do you know if the egg you're using is like a steamcmd docker under the hood?

solar temple
#

steamcmd i guess

magic forge
#

looking into that image to see what options you have to trigger it to repair itself

#

I'm getting a little lost in layers of pterodactyl...I think if you delete both media/ (where the problematic 42.15 files live) and steamapps/ inside the server installation data, turn "Steam Auto Update" on, and start up, it should be triggered into repairing itself (make sure your world data is not under either of those paths)

but alternately, maybe just make a new server instance (with the same value for "Server Name"), shut it down, and move your old server's data into it. (delete db/, Server/, and Saves/ in the new, and copy them over from the old)

#

if pterodactyl gives you the ability to open a terminal inside the container, maybe we could work with steamcmd directly--but it might be some trouble to know the right paths inside the container

#

odd that steamcmd has this dangling file issue on some installs but not others shrugDog

solar temple
magic forge
#

your old .15 world and everything?

#

I didn't realize so many files could mistakenly hang around after updating, added a note to the workshop page about what to do when the log_stack error seems to "come back"

#

glad you're fixed up 🫡

solar temple
#

thanks so much!