Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GameruserSettings.ini overwritten #260

Closed
Murdock2k opened this issue Nov 2, 2015 · 9 comments
Closed

GameruserSettings.ini overwritten #260

Murdock2k opened this issue Nov 2, 2015 · 9 comments

Comments

@Murdock2k
Copy link

Hey Guys,

everytime i start the Server, he overwrite my Servername/Slot and the passwords...
i changed these commands in the arkmanager.cfg and in the GameuserSettings.ini
but nothing happens, always Ark Server Tools name and 70 slots -.-
I use ubuntu 14.04 and a fresh install...

@klightspeed
Copy link
Collaborator

It is the ARK server itself that overwrites the GameUserSettings.ini file.

If you want to specify these settings (ServerPassword, ServerAdminPassword, SessionName, MaxPlayers) in your GameUserSettings.ini file, then you need to comment out (i.e. prepend the line with a # character) the ark_ServerPassword, ark_ServerAdminPassword, ark_SessionName and ark_MaxPlayers settings in the /etc/arkmanager/arkmanager.cfg file.

@Murdock2k
Copy link
Author

Hey,

i have specified it in the GemuserSettings "AND" in the arkmanager.cfg.
After that doesnt work i comment out the variables in the arkmanager.cfg and changed it
a few times in the GameuserSettings.ini but he always overwrite it...

the Steam user has rights on the gameusersettings.ini and the rootuser on the arkmanager cfg,
so that should be alright, but why ignores the server my commands and change it back to the
defaults?

@klightspeed
Copy link
Collaborator

Did you perform a user-install (i.e. curl -sL http://git.io/vtf5N | bash -s -- --me) or a system-wide install (i.e. curl -sL http://git.io/vtf5N | sudo bash -s steam)?

Does ~/.arkmanager.cfg exist? If both that file and /etc/arkmanager/arkmanager.cfg exist, and you don't want the settings in ~/.arkmanager.cfg to override those in /etc/arkmanager/arkmanager.cfg, then remove ~/.arkmanager.cfg. Note that a user-install (i.e. using the --me argument to the install) would have created that file.

@Murdock2k
Copy link
Author

hmm... now the server dont start and i got errors like:
"[ ERROR ] You have not rights to write in the log directory.
The server is starting...
/usr/local/bin/arkmanager: line 591: /var/log/arktools/arkserver.log: Permission denied
/usr/local/bin/arkmanager: line 592: /var/log/arktools/arkmanager.log: Permission denied"

i deletet the "~/.arkmanager.cfg" :-(

@klightspeed
Copy link
Collaborator

What are the permissions on /var/log/arktools?

Did you perform a system-wide install with another user, then perform a user-install with this user?

@Murdock2k
Copy link
Author

hmm... i think i did the install first with the "-s steam" command and than with the "-s -- --me" command -.-
shit... now? Reinstall the mod?

@klightspeed
Copy link
Collaborator

You should be able to change the owner of /var/log/arktools to the user you're running under (i.e. run as root: chown <username> /var/log/arktools), and update the steamcmd_user setting in /etc/arkmanager/arkmanager.cfg to be the username of that user.

You will also need to replace /home/steam in the following settings with the home directory of your ark user:

  • steamcmdroot
  • steamcmd_appinfocache
  • arkserverroot
  • arkbackupdir

@Lihis
Copy link
Contributor

Lihis commented Nov 3, 2015

Could someone confirm the permission issue too? As I fired up Debian 8.2 in virtualbox to test some mods for my server; I used curl -sL http://git.io/vtf5N | sudo bash -s steam to install arkmanager. On fresh arkmanager v1.4 install the /var/log/arktools is owned by root and by group root, which obviously causes the permission error.

Meanwhile on production server (Debian 8.2), where I upgraded the arkmanager to v1.4 there is no permission issues as log directory is owned by steam and by group root.

edit: Should I create issue for this?

@klightspeed
Copy link
Collaborator

@Lihis #265 should fix this fresh-install wrong-ownership issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants