Waltm

I'm hearing rumors that due to an exclusive deal between Wildcard/Snail Games and Nitrado, that the only way to run a dedicated Ark: Survival Ascended server is by renting through Nitrado. I hope this is only for rented servers and we will still be able to host our own.

Ok, thanks. If anyone has any more info, I have most of the containers installed and running by following the pinned post, but think I have issues with the ARK0 one. I had to move some files manually into the /serverdata/serverfiles location since it was just coming up with errors. When I navigate to the dynamic config IP in a browser, it downloads the file instead of displaying it in a browser like the official site. I did have to change the port to 8086 due to other docker conflicts and changed the map dockers to ?customdynamicconfigurl="http://(server IP):8086/dynamicconfig.ini" to match.

With the recent announcement that the official Ark servers will be shutting down and the save files available for download, I'm considering changing my single server setup to a cluster. Are the files and info at https://github.com/CydFSA/A3C still the best way to set this up? If so, is there a beginner friendly walkthrough an installing this as the instructions on github aren't that clear to me and I don't want to flood this thread with beginner questions.

After a server reboot the docker service started with no issues. Parity check is still running but I'm not sure what the previous errors are pointing to.

My Cache drive had filled up so I manually invoked the Mover from the main page. Sometime during the move the dockers became unavailable and even now that the move is complete, the docker service is showing errors and can not start. I have tried stopping and starting the docker service from the settings page but I'm afraid to actually stop the server itself. The server log is filling up with errors like this: Jun 11 14:42:19 Tower kernel: BTRFS info (device loop2): no csum found for inode 3871 start 0 Jun 11 14:42:19 Tower kernel: BTRFS warning (device loop2): csum failed root 8166 ino 3871 off 0 csum 0x2cfa2d2f expected csum 0x00000000 mirror 1 Jun 11 14:42:19 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 190029, gen 0 Jun 11 14:42:20 Tower kernel: BTRFS error (device loop2): parent transid verify failed on 32727040000 wanted 809781 found 807749 Jun 11 14:42:20 Tower kernel: BTRFS error (device loop2): parent transid verify failed on 32727040000 wanted 809781 found 807749 Jun 11 14:42:20 Tower kernel: BTRFS info (device loop2): no csum found for inode 1066 start 0 Jun 11 14:42:20 Tower kernel: BTRFS warning (device loop2): csum failed root 8081 ino 1066 off 0 csum 0x0f8afbf7 expected csum 0x00000000 mirror 1 Jun 11 14:42:20 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 190030, gen 0 Jun 11 14:42:29 Tower kernel: BTRFS error (device loop2): parent transid verify failed on 32726908928 wanted 809781 found 807749 Jun 11 14:42:29 Tower kernel: BTRFS error (device loop2): parent transid verify failed on 32726908928 wanted 809781 found 807749 tower-diagnostics-20220611-1437.zip

Good call, I didn't even realize I had anything plugged in but that fixed the USB errors. New drive is in and rebuilding. Docker service started with the reboot so I stopped them all for now. I'll try the balance command once the array is back to normal. Thanks for the help!

Hiya folks. I've been having some issues lately so when I checked the log I'm seeing this error repeating constantly. Any clue as to what to do about this? If it's a hardware failure can I turn it off somehow? For some background, log had filled up so rebooted the machine to clear it. Replaced a drive that was starting to have errors and was the smallest one on the array. When the array was rebuilding another drive reported a lot more errors and was disabled overnight. Replacement drive should be here tomorrow. Cache drive had filled up but has returned to 75%. Dockers will not start but I though that might be due to the damaged drive in the array. Error in log: May 15 14:40:28 Tower kernel: usb usb4-port5: Cannot enable. Maybe the USB cable is bad? May 15 14:40:32 Tower kernel: usb usb4-port5: Cannot enable. Maybe the USB cable is bad? May 15 14:40:36 Tower kernel: usb usb4-port5: Cannot enable. Maybe the USB cable is bad? May 15 14:40:40 Tower kernel: usb usb4-port5: Cannot enable. Maybe the USB cable is bad? This is what is showing up for usb devices: USB Devices Bus 001 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002:ID 8087:800a Intel Corp. Bus 002 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002:ID 8087:8002 Intel Corp. Bus 003 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002:ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 003 Device 003:ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub Bus 003 Device 004:ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 004 Device 001:ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 002:ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub Bus 005 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001:ID 1d6b:0003 Linux Foundation 3.0 root hub tower-diagnostics-20220515-1446.zip

It would appear I broke my ZM install. It has been down for a while waiting for a new data drive. I replaced the drive, set the mount name in the docker to match but when I tried to start ZM it just crashes. It appears to be an issue with the database connection. Is there a way to repair this? ZM startup log below. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/05_set_the_time.sh... *** Running /etc/my_init.d/06_set_php_time.sh... *** Running /etc/my_init.d/07_set_dri_permissions.sh... Granting permissions on /dev/dri/* devices... *** Running /etc/my_init.d/10_syslog-ng.init... Apr 10 15:25:18 d98319459b45 syslog-ng[20]: syslog-ng starting up; version='3.25.1' *** Running /etc/my_init.d/20_apt_update.sh... Performing updates... Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB] Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease Hit:3 http://ppa.launchpad.net/iconnor/zoneminder-1.36/ubuntu focal InRelease Get:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] Hit:5 http://ppa.launchpad.net/ondrej/apache2/ubuntu focal InRelease Get:6 http://archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB] Hit:7 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease Fetched 336 kB in 2s (177 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. *** Running /etc/my_init.d/30_gen_ssl_keys.sh... using existing keys in "/config/keys" *** Running /etc/my_init.d/40_firstrun.sh... Using existing conf folder File zm.conf already copied File zmeventnotification.ini already moved File secrets.ini already moved Event notification server already moved Pushover api already moved Using existing ssmtp folder Using existing mysql database folder Copy /config/control/ scripts to /usr/share/perl5/ZoneMinder/Control/ Copy /config/conf/ scripts to /etc/zm/conf.d/ Creating symbolink links usermod: no changes usermod: no changes usermod: no changes Using existing data directory for events Using existing data directory for images Using existing data directory for temp Using existing data directory for cache no crontab for root Starting services... * Starting Apache httpd web server apache2 * * Stopping MariaDB database server mysqld ...done. * Starting MariaDB database server mysqld ...fail! DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. Apr 10 15:26:05 d98319459b45 zmupdate[1153]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. Unable to connect to DB. ZM Cannot continue. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 150. Compilation failed in require at /usr/bin/zmupdate.pl line 74. BEGIN failed--compilation aborted at /usr/bin/zmupdate.pl line 74. Apr 10 15:26:05 d98319459b45 zmupdate[1153]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. Apr 10 15:26:05 d98319459b45 zmupdate[1155]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. Unable to connect to DB. ZM Cannot continue. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 150. Compilation failed in require at /usr/bin/zmupdate.pl line 74. BEGIN failed--compilation aborted at /usr/bin/zmupdate.pl line 74. Apr 10 15:26:05 d98319459b45 zmupdate[1155]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] Starting ZoneMinder: DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. Apr 10 15:26:16 d98319459b45 zmpkg[1166]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] DBI connect('database=zm;host=localhost','zmuser',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl5/ZoneMinder/Database.pm line 110. Unable to connect to DB. ZM Cannot continue. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder/Config.pm line 150. Compilation failed in require at /usr/share/perl5/ZoneMinder.pm line 33. BEGIN failed--compilation aborted at /usr/share/perl5/ZoneMinder.pm line 33. Compilation failed in require at /usr/bin/zmpkg.pl line 34. BEGIN failed--compilation aborted at /usr/bin/zmpkg.pl line 34. Apr 10 15:26:16 d98319459b45 zmpkg[1166]: ERR [Error reconnecting to db: errstr:Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) error val:] ZoneMinder failed to start *** /etc/my_init.d/40_firstrun.sh failed with status 255 *** Killing all processes... Apr 10 15:26:16 d98319459b45 syslog-ng[20]: syslog-ng shutting down; version='3.25.1'

Yes, your docker image and the server have been running great with the Alemia sponsored map/mod. I still have to manually transfer the mod files over from single player to the server every time they update since I haven't figured out the automanagemods yet. I think there was a post in this thread about having certain paths mapped in order to make it work but now I can't find it again.

Thanks, I'll ignore it. Sorry about not including the whole log, I've attached it here just so you have the whole thing. Log.txt

I just noticed a new line in the log when I restarted my Ark server after the latest steam update. [33;1mPlease use force_install_dir before logon! Is this anything to be concerned with or anything I need to actually do when starting the server? Thanks

Sorry, missed this part. I do run Pi-hole but disabled it to restart the server. I don't know if it makes a difference or not but I am running a mod map (Alemia).

After a few more tries I was able to get it to verify but it is still showing on the server list at the old version and the version.txt file in the ark-se folder also lists the old version. Log - Verify.txt

I've set validate to True but it still didn't seem to update the base game. Are there some files I can remove to force it to reload without removing the entire container?

Sorry if this has been asked and answered a dozen time already but how do I update the version of Ark being run? I thought that a docker restart would do it automatically but the log (pasted below) says it's the latest version but the server list in game and on steam shows I'm not on the current version after Official servers were just updated to a new minor version. ---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- ---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Update SteamCMD--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK ---Update Server--- ---Update Server--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK Success! App '376030' already up to date. ---Prepare Server--- Waiting for user info...OK Success! App '376030' already up to date. ---Prepare Server--- ---Server ready--- ---Start Server--- [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.

Thanks for the info. Sorry about the thread location, didn't realize it was related to the plugin and not just a device error.

Hi guys, I'm unable to mount a usb connected drive that was mounted in the past. The log shows the following when I click the "mount" button: Oct 11 10:53:10 Tower unassigned.devices: Adding disk '/dev/sdp1'... Oct 11 10:53:10 Tower unassigned.devices: Mounting partition '/dev/sdp1' at mountpoint '/mnt/disks/WD_easystore'... Oct 11 10:53:10 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdp1' '/mnt/disks/WD_easystore' Oct 11 10:53:10 Tower kernel: XFS (sdp1): Filesystem has duplicate UUID 1c07ea9b-98f8-4fd2-b808-d8ee8dae2c62 - can't mount Oct 11 10:53:10 Tower unassigned.devices: Mount of '/dev/sdp1' failed: 'mount: /mnt/disks/WD_easystore: wrong fs type, bad option, bad superblock on /dev/sdp1, missing codepage or helper program, or other error. ' Oct 11 10:53:10 Tower unassigned.devices: Partition 'WD_easystore' cannot be mounted. This is how it shows on the Main webpage. I have tried removing the drive from historical devices and reconnecting it with the same resultes. Could anyone point me in the right direction to further troubleshoot this issue? Thanks. tower-diagnostics-20211011-1059.zip

It's booting now. I may have missed a step in the UEFI setup, or at least I hope that's what happened. Creating a new one using the check box again failed to boot but for some reason in the setup it was showing one of the array drives as the first boot option now. It had 2 options listed for the usb drive and moving the UEFI one to 1st allowed it to boot. I'm almost afraid to try creating a new stick from my backup now that I've gotten this far but guess I need to. Thanks for your help!

If I remove the dash from a manually created drive it starts in the UEFI bios screen. Using the check box in the usb creator tool removes the hyphen automatically. Then I just get the flashing cursor.

I've tried both. If I try UEFI from the boot menu it just brings me to the bios setup

My boot usb drive was failing a few months ago. I was able to repair it in Windows. I took a backup and it was running fine. It failed again and I was not able to see it in windows so tried to create a new one using he unRaid usb creator tool. I have tried two different USB sticks, one was the same make/model as the original. I have tried creating from the backup using the tool, tried to copy the files and use the make bootable .bat file, and tried creating a new one from scratch without the backup config files. I have tried plugging into all usb slots on the motherboard. If I enter the boot menu (F8) the drive shows up and I can select it as well as setting it in the bios. Nothing I have tried will boot from either stick. I only see a flashing cursor on a monitor I've attached. The ip address does not show on my router and I can not connect through telnet. Any ideas what I should look at next?

Yeah, I try to reach the unRaid server in the phones web browser using it's ip address, and splashtop to access other machines on the network. They are the only things I really use it for and both stopped working. Oddly enough, after 3 days of trying everything I can think of, it just started working on it's own this morning. I'm happy that it's working but it really bugs me when problems 'resolve' themselves without me knowing what caused them or why they suddenly work again. I'll try switching it back to ddns when I get home tonight but don't think I'll have an issue with that now either. Thanks for chiming in with advice, I really appreciate the help. It still shows upnp forwarding not set, but can I ignore that if it seems to be working again, or is it something I should be concerned with?

So, I had this working fine and for some reason it recently stopped. I can't get it to show a connection or handshake. I've tried to reconfigure and even deleted the tunnel and started from scratch. I have upnp enabled on my router but the server is showing it's not set. I also have the port forwarded to the server. I've switched to my wan ip instead of ddns that was working. I've read through the troubleshooting tips at the start of this thread but am not sure where to look next. Any recommendations on what info I can provide to help get this resolved? Client is on an Android phone, wifi is off in order to use cell network.

Please ignore, my issue resolved itself when I updated other containers.

back up and running. Thanks for the help!