threeguys@3guysgame:~$ ampinstmgr -t
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
threeguys@3guysgame:~$ journalctl -u ampinstmgr -n 100
Jul 18 07:22:29 3guysgame ampinstmgr[1170]: [Info/8] 4aea9d4143cb8f8a73276b7006fcbbfa55242cec8a83df52a2d55af8767f1025
Jul 18 07:22:29 3guysgame sudo[1937]: pam_unix(sudo:auth): conversation failed
Jul 18 07:22:29 3guysgame sudo[1937]: pam_unix(sudo:auth): auth could not identify password for [amp]
Jul 18 07:22:36 3guysgame ampinstmgr[1170]: [Info/6] 9ec1266207133584bddcbd5a255988b6fa32077dcf99a234fbcfcfbd52816593
Jul 18 07:22:41 3guysgame ampinstmgr[1170]: [Info/5] 64288e731bb632378510c0103ced34bb22830e3bd9c579b2fdda5265ba82aa2b
Jul 18 07:22:43 3guysgame systemd[1]: Finished AMP Instance Manager.
Jul 18 11:02:48 3guysgame ampinstmgr[19676]: [Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
Jul 18 11:02:48 3guysgame ampinstmgr[19676]: [Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Jul 18 11:02:46 3guysgame systemd[1]: Stopping AMP Instance Manager…
Jul 18 11:02:52 3guysgame ampinstmgr[19676]: [Info/1] Stopping Instance: ‘ADS01’
Jul 18 11:02:52 3guysgame ampinstmgr[19676]: [Info/1] Stopping instance ADS01…
Jul 18 11:02:52 3guysgame ampinstmgr[19676]: [Info/1] Requesting soft-stop…
Jul 18 11:02:53 3guysgame ampinstmgr[19676]: [Info/1] Waiting for instance to stop…
Jul 18 11:02:54 3guysgame ampinstmgr[19676]: [Info/6] Instance was shut down gracefully.
Jul 18 11:02:54 3guysgame ampinstmgr[19676]: [Info/6] Instance ADS01 has stopped.
Jul 18 11:02:54 3guysgame systemd[1]: ampinstmgr.service: Deactivated successfully.
Jul 18 11:02:54 3guysgame systemd[1]: Stopped AMP Instance Manager.
Jul 18 11:02:54 3guysgame systemd[1]: ampinstmgr.service: Consumed 40.819s CPU time.
– Boot 663879df001f44c9952ef1514484a1ea –
Jul 18 11:04:09 3guysgame systemd[1]: Starting AMP Instance Manager…
Jul 18 11:04:13 3guysgame ampinstmgr[1234]: [Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
Jul 18 11:04:15 3guysgame ampinstmgr[1234]: [Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Jul 18 11:04:23 3guysgame ampinstmgr[1234]: [Info/1] Waiting for AMP instance to start…
Jul 18 11:04:28 3guysgame ampinstmgr[1234]: [Error/5] Failed to start AMP. Exit code was 0
Jul 18 11:04:48 3guysgame ampinstmgr[1234]: [Info/8] fcb44bd8ff5329c263ebd0080315f26600cc040d2a814e003abb7d26e2747a54
Jul 18 11:04:55 3guysgame sudo[2769]: pam_unix(sudo:auth): conversation failed
Jul 18 11:04:55 3guysgame sudo[2769]: pam_unix(sudo:auth): auth could not identify password for [amp]
Jul 18 11:04:56 3guysgame ampinstmgr[1234]: [Info/4] 3aa0b2f1b0715aef2e0eb95034992701ff0fa9e528715a91f428a80bb04c2e37
Jul 18 11:05:00 3guysgame ampinstmgr[1234]: [Info/11] 0a1d080cefdc7861cf78b66eb8ccf177e9ce7df16a199f240c3cf1b4c0a23860
Jul 18 11:05:04 3guysgame systemd[1]: Finished AMP Instance Manager.
Jul 18 11:36:26 3guysgame systemd[1]: Stopping AMP Instance Manager…
Jul 18 11:36:26 3guysgame ampinstmgr[7425]: [Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
Jul 18 11:36:26 3guysgame ampinstmgr[7425]: [Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Jul 18 11:36:27 3guysgame ampinstmgr[7425]: [Info/1] Stopping Instance: ‘ADS01’
Jul 18 11:36:27 3guysgame ampinstmgr[7425]: [Info/1] Stopping instance ADS01…
Jul 18 11:36:27 3guysgame ampinstmgr[7425]: [Info/1] Requesting soft-stop…
Jul 18 11:36:27 3guysgame ampinstmgr[7425]: [Info/1] Waiting for instance to stop…
Jul 18 11:36:27 3guysgame ampinstmgr[7425]: [Info/5] Instance was shut down gracefully.
Jul 18 11:36:27 3guysgame ampinstmgr[7425]: [Info/5] Instance ADS01 has stopped.
Jul 18 11:36:27 3guysgame ampinstmgr[7425]: [Info/5] Stopping Instance: ‘ValheimI01’
Jul 18 11:36:27 3guysgame ampinstmgr[7425]: [Info/5] Stopping instance ValheimI01…
Jul 18 11:36:27 3guysgame ampinstmgr[7451]: AMP_ValheimI01
Jul 18 11:36:32 3guysgame ampinstmgr[7425]: [Info/5] Instance ValheimI01 has stopped.
Jul 18 11:36:32 3guysgame ampinstmgr[7425]: [Info/5] Stopping Instance: ‘Satisfactory101’
lines 1-44
It looks like there might be some permission issues with the amp user. Specifically, errors related to pam_unix(sudo:auth) suggest that the amp user might not have the right permissions or there’s an issue with the sudo configuration.
Let’s try a few things:
1. Check sudoers file for AMP user
Make sure the amp user has the required permissions in the sudoers file:
sudo visudo
Add the following line if it’s not already there (or adjust as needed):
amp ALL=(ALL) NOPASSWD:ALL
2. Fix AMP file permissions
Run the following command to fix any potential file permission issues:
sudo -u amp ampinstmgr fixperms
3. Restart AMP
Restart the AMP instance manager service again:
sudo systemctl restart ampinstmgr
4. List instances again
Finally, list the instances to see if they show up:
ampinstmgr -t
Try these steps and let’s see if it resolves the issue!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
threeguys@3guysgame:~$ sudo -u amp ampinstmgr fixperms
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Error/1] I require root/admin access to do that!
threeguys@3guysgame:~$
Alright, let’s run the ampinstmgr fixperms command with root privileges instead:
sudo ampinstmgr fixperms
This should fix the permissions without needing to switch users. After that, try listing the instances again with:
ampinstmgr -t
Give it a go and let me know how it works!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
[quote=“CubeCoders-Bot, post:24, topic:15026”]
ampinstmgr -t
[/quote]threeguys@3guysgame:~$ sudo ampinstmgr fixperms
[sudo] password for threeguys:
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] Updating permissions for amp…
threeguys@3guysgame:~$ ampinstmgr -t
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
threeguys@3guysgame:~$
Alright, permissions should be good now, but the instances are still not showing. Let’s try one more approach. We can manually check the instance configuration files to see if there are any issues or if they are misconfigured.
1. Check the Instances Directory
Let’s navigate to the directory where AMP instances are usually stored:
cd /home/amp/.ampdata/instances
2. List the Instances
List all the files and directories there to see if the instances are actually present:
ls -l
3. Check Individual Instance Info
If you see the instance directories, check the configuration files for one of them (e.g., ValheimI01):
cat ValheimI01/InstanceConfig.yaml
Check the configuration file for any obvious issues or inconsistencies.
4. Validate an Instance
If the instance directories are there, try validating one of them:
ampinstmgr validate ValheimI01
Let’s see if this gives us more insight into what might be wrong.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
threeguys@3guysgame:~$ cd /home/amp/.ampdata/instances
bash: cd: /home/amp/.ampdata/instances: Permission denied
threeguys@3guysgame:~$
It looks like you don’t have permission to access the AMP instances directory. Let’s try switching to the amp user and then navigate to the directory:
1. Switch to amp User
sudo su -l amp
2. Navigate to the Instances Directory
cd /home/amp/.ampdata/instances
3. List the Instances
ls -l
4. Check Individual Instance Info
cat ValheimI01/InstanceConfig.yaml
Let’s do these steps and see if we can get more information about the instances.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
threeguys@3guysgame:~$ sudo su -l amp
[sudo] password for threeguys:
CubeCoders AMP 
amp@3guysgame 
~ cd /home/amp/.ampdata/instances
CubeCoders AMP amp@3guysgame ~/.ampdata/instances ls -l
total 16
drwx------ 7 amp amp 4096 Jul 18 11:59 ADS01
drwx------ 10 amp amp 4096 Jul 18 12:00 Satisfactory101
drwx------ 10 amp amp 4096 Jul 18 12:45 Satisfactory201
drwx------ 10 amp amp 4096 Jul 18 11:45 ValheimI01
CubeCoders AMP amp@3guysgame ~/.ampdata/instances cat ValheimI01/InstanceConfig.yaml
cat: ValheimI01/InstanceConfig.yaml: No such file or directory
CubeCoders AMP amp@3guysgame ~/.ampdata/instances cd Satisfactory1-1
-bash: cd: Satisfactory1-1: No such file or directory
CubeCoders AMP amp@3guysgame ~/.ampdata/instances cd Satisfactory101
CubeCoders AMP amp@3guysgame ~/.ampdata/instances/Satisfactory101 ls
AMPConfig.conf Backups GenericApplication LocalFileBackupPlugin.kvp.old scheduleTimes.json
AMPConfig.conf.old configmanifest.json GenericModule.kvp metaconfig.json steamcmdplugin.kvp
AMP_Linux_x86_64 datastore.dat GenericModule.kvp.old Plugins steamcmdplugin.kvp.old
AMP_Logs EmailSenderPlugin.kvp geoip-data.mmdb.gz RCONPlugin.kvp WebRequestPlugin.kvp
AMPVersion EmailSenderPlugin.kvp.old InstalledDeps.json RCONPlugin.kvp.old WebRequestPlugin.kvp.old
AnalyticsPlugin.kvp FileManagerPlugin.kvp Licences satisfactory WebRoot
AnalyticsPlugin.kvp.old FileManagerPlugin.kvp.old LocalFileBackupPlugin.kvp scheduleEvents.json
CubeCoders AMP amp@3guysgame ~/.ampdata/instances/Satisfactory101
Alright, it appears that the InstanceConfig.yaml file is missing. This file is crucial for AMP to recognize and manage the instance. We might need to recreate or reconfigure the instance to regenerate this file.
Reconfigure the Instance
-
Exit the
ampuser shell:exit -
Reconfigure the instance using
ampinstmgr:sudo ampinstmgr reconfigureinstance Satisfactory101 -
Repeat for the other instances if needed:
sudo ampinstmgr reconfigureinstance Satisfactory201 sudo ampinstmgr reconfigureinstance ValheimI01 -
After reconfiguring, list the instances again:
ampinstmgr -t
Let’s go ahead with these steps and see if it helps regenerate the missing configuration files and recognize the instances.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
threeguys@3guysgame:~$ sudo ampinstmgr reconfigureinstance Satisfactory101
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Warning/1] The user you’re logged in as has no instances, but you have a separate ‘amp’ system user - did you mean to run ampinstmgr as that user instead?
[Warning/1] Run su -l amp to switch over. Then, run the same command again.
[Error/1] No such instance matching name: ‘Satisfactory101’
threeguys@3guysgame:~$
You’ll need to run these commands after switching to the amp user:
ampinstmgr reconfigureinstance Satisfactory101
ampinstmgr reconfigureinstance Satisfactory201
ampinstmgr reconfigureinstance ValheimI01
ampinstmgr -t
Let’s do it!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Instance Name │ Friendly Name │ Module │ IP │ Port │ Up
───────────────────┼──────────────────┼────────────┼─────────────────┼───────┼───
ADS01 │ ADS │ ADS │ 0.0.0.0 │ 8080 │
Satisfactory101 │ Satisfactory1 │ Generic │ 127.0.0.1 │ 8082 │
Satisfactory201 │ Satisfactory2 │ Generic │ 127.0.0.1 │ 8083 │
ValheimI01 │ Valheim1 │ Generic │ 127.0.0.1 │ 8081 │
CubeCoders AMP amp@3guysgame ~
Awesome, now the instances are listed! 
Let’s proceed with checking the instance configurations and ensuring they are properly set up.
1. View the configuration for each instance
You can do this via AMP’s web interface, but let’s start with Satisfactory101 as an example:
- Go to the AMP web interface in your browser.
- Log in and navigate to Instances.
- Select
Satisfactory101and go to its configuration page.
2. Ensure Ports and IPs are Correct
Make sure each instance has unique ports and correct IPs.
3. Start the Instances
Start each instance from the AMP web interface:
- Right-click on an instance and select “Start”.
4. Verify Connectivity
Try connecting to each server from your client.
If you still face issues, check the instance logs via the AMP interface:
- Right-click the instance.
- Select “View Logs”.
Let’s start with these steps. Let me know if you run into any issues along the way!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
threeguys@3guysgame:~$ ampinstmgr --RestartAllInstances
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
threeguys@3guysgame:~$
It looks like the command didn’t execute as expected because of a typo. The correct command should be:
ampinstmgr -a
Or, if you want to restart all instances with a delay between each restart:
ampinstmgr --restartallinstances
Give that a shot. You can also start individual instances using:
ampinstmgr -s [InstanceName]
So, for example, to start Satisfactory101:
ampinstmgr -s Satisfactory101
Try running these commands and let’s get those instances up and running!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Reason: AMP tried to login to auth server at http://localhost:8080/ but it could not be reached. This can be found under Configuration → New Instance Defaults → Auth Server URL. This URL should reflect the address of your primary AMP installation…
Connection refused - Connection refused
Got it, it seems like the ADS instance, which manages authentication, is not running or not reachable. Let’s make sure the ADS instance is up and running.
1. Start the ADS Instance
First, start the ADS instance since it’s crucial for managing other instances:
ampinstmgr -s ADS01
2. Verify ADS is Running
Make sure the ADS instance is actually running:
ampinstmgr -l
3. Restart Other Instances
Once the ADS instance is up, restart the other instances:
ampinstmgr --restartallinstances
4. Check the Auth Server URL
If you still face issues, verify the Auth Server URL:
- Go to the AMP web interface.
- Navigate to Configuration.
- Go to New Instance Defaults.
- Ensure the Auth Server URL points to your main AMP installation (e.g.,
http://localhost:8080/).
Let’s get the ADS instance up and running first. Give these steps a try and let me know how it goes!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
threeguys@3guysgame:~$ ampinstmgr -s ADS01
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Error/1] No such instance matching name: ‘ADS01’
threeguys@3guysgame:~$
Alright, it seems like the ADS instance might not be correctly set up or it’s named differently. Let’s list all instances to confirm their names again:
ampinstmgr -t
If ADS01 is not listed, we might need to recreate it. Here’s how you can do it:
1. Create a New ADS Instance
ampinstmgr -quick [AdminUsername] [AdminPassword]
Replace [AdminUsername] and [AdminPassword] with your desired admin credentials.
2. Start the New ADS Instance
Once created, start the new ADS instance:
ampinstmgr -s [ADSInstanceName]
3. Re-check the Instances
After starting the ADS instance, list the instances again to make sure everything is up:
ampinstmgr -t
Run these steps and let’s verify the setup.