Waltm

Hiya folks. I'm starting to see incompatibilities with the older version I'm running, so was thinking about upgrading. Is upgrading recommended and if so, what is the most stable version with the least install issues?

Starting fresh worked. It even seems like there are fewer ports with the new install than there were on the old one. Thank you for your help!

Hi folks, I had a Satisfactory server running over a year ago when it was early access. I recently tried to start it up again now that the game is released, and while it appears to have updated properly, I am having an issue connecting to the server with the client. After adding a server with the my LAN IP and default port, the client shows a server with low ping, it shows the "Server Name Pending" and "not authenticated" as well as "Failed to Connect to the Server API". Unfortunately I don't remember if there were other steps I took to get it running originally. Can anyone shed some light on this?

Thank you, this worked. If there is an advantage to using port forwarding with this container I will edit the list of endpoints to only those that support it.

Thank you for your quick reply. I'm sorry to follow up with what are probably basic questions, but where is the setting for STRICT_PORT_FORWARD? I didn't see it in the edit screen. Also, it is always trying to connect to 'us-newyorkcity.privacy.network' even though that is not what I have in the settings. None of the US servers have port forwarding and it was set to one in Europe, but I have tried to enter several others on the settings page. Is there some place else I should be changing this? I'm assuming there was a change either on SAB or the VPN side of things since this is a new issue.

I'm also having the same problem of no UI after working for several years. I'm not sure exactly when this started but just noticed it today. supervisord.log Command execution.txt

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.