OS Name/Version: Centos8 Stream
Product Name/Version: AMP 22.214.171.124 - Mainline
Problem Description: Game server crashes before fully starting, actually similar to this thread [Can’t start V-Rising instance] except I’m running CentOS and not on a VPS
C:\windows\system32\mpr.dll:mpr.dll (00007F4B32DF0000), size: 151552 (result: 0), SymType: '-deferred-', PDB: 'C:\windows\system32\mpr.dll', fileVersion: 5.0.2195.6611 ========== OUTPUTTING STACK TRACE ================== RtlLookupFunctionEntry returned NULL function. Aborting stack walk.
Steps to reproduce:
- Login to AMP and create
V-Risingserver as a container
V-Risinginstance and click on console tab.
updatebutton in console tab then click
startonce update is done.
Actions taken to resolve so far:
- Uninstalled manual docker installation and installed using
bash <(wget -qO- getamp.sh) installDockerand verified working
Docker version 20.10.17, build 100c701
- Had previously installed wine manually to get server working (before moving to docker instances), removed it just in case
- Verified docker isn’t the issue by creating a containerized
Satisfactorygame server and worked just fine (no errors in console and able to connect to it)
In an effort to save time, providing output of commands asked for in the similar thread listed at the beginning of post
[root@smoothsailing ~]# docker --version Docker version 20.10.17, build 100c701
[root@smoothsailing ~]# su -l amp [amp@smoothsailing ~]$ docker pull cubecoders/ampbase:wine wine: Pulling from cubecoders/ampbase Digest: sha256:e8c3180bbfba2762b91fec0effcd97fdf91aec459267bc31968894fc9353c117 Status: Image is up to date for cubecoders/ampbase:wine docker.io/cubecoders/ampbase:wine
[amp@smoothsailing ~]$ ampinstmgr restart vrising01 [Info] AMP Instance Manager v126.96.36.199 built 11/07/2022 20:17 [Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV [Info] Stopping Instance: 'VRising01' [Info] Stopping instance VRising01... AMP_VRising01 [Info] Instance VRising01 has stopped. [Info] Starting Instance: 'VRising01' [Info] 1421d915467a157693c0a516154d5ca90a19ac13f690b00d6225352d65f8674c
[amp@smoothsailing ~]$ ampinstmgr validate vrising01 [Info] AMP Instance Manager v188.8.131.52 built 11/07/2022 20:17 [Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV [Info] 0 missing files, 0 damaged files. [Info] All files passed OK!
UPDATE: While trying to answer
Can you make a new instance for me and check that two instances fail in the exact same way? The previously failing seems to work now once I started the second server but the second server is failing the same way the first server did. It’s as if the second one is being sacrificed in order for the first to work