l2evy
-
Posts
17 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by l2evy
-
-
I keep getting out of memory errors with Conan Exiles server...more specific
LogMemory:Warning: Freeing 33554432 bytes from backup pool to handle out of memory. LogMemory:Warning: MemoryStats: AvailablePhysical 100261916672 AvailableVirtual 140726590709760 UsedPhysical 10897514496 PeakUsedPhysical 10897514496 UsedVirtual 10859667456 PeakUsedVirtual 10859667456 0108:err:sync:RtlpWaitForCriticalSection section 0000000004EAA8C0 (null) wait timed out in thread 0108, blocked by 0174, retrying (60 sec)it just keeps spamming the 0108:err after that....I watched it with HTOP, it stops at 10.4GB physical, 12.9GB virtual.....I have more than 90GB of free ram remaining? I suspect this is some limit in wine I need to adjust? Any help in the right direction would be much appreciated ❤️
-
Ahh I see. That would leave me stranded with some containers on community apps that have no real config files or WebUI to adjust the ports and they are only set on creation of the container. I suppose the only solution would be to custom setup my own container entirely from the start so I can configure the ports differently. I remember you could edit the raw container creation template (as xml I believe on creation) before at some point I think, however the option seems to be gone now.
On the network side of things, If I understand correctly when you set network to none and force it through to another container, it is then considered "raw" directly to the other container which is why no edits to the ports on creation of the container take effect as it then is irrelevant there. Also if the container you route has a WebUI you then configure the container it is connected to (In my case OpenVPN) and add the WebUI port so you can access it.
I have applied this new understanding to some containers and it seems to be working for containers that have the option of config edits or WebUI though. Progress
Edit:
When you do route the container network to another container, I assume the "Port Mappings (App to Host)" for that container is to be ignored?
They have no IP and just show port maps. For example " :8080/TCP <-> :8080 "
Edit 2:
QuoteI remember you could edit the raw container creation template (as xml I believe on creation) before at some point I think, however the option seems to be gone now.
Compose.Manager by dcflachs in the Community Apps is a plugin that is enabling docker compose management and will likely help make your own custom containers for situations like this a bit easier. This should help alleviate my issue but have yet to get down to it myself cause I am redoing my whole home network.
Also the Unraid 6.10 RC's have added functionality to set containers network to a wireguard VPN in Unraid (Settings > VPN Manager), so this might actually be a solution to allow port edits while retaining the ability to pass through a VPN.
-
Unraid Version : 6.10.0 RC4
I have some containers I am trying to setup and route them all through a OpenVPN container. (from community apps)
Some have a webUI using port 8080 on the container.
I set the containers network to None, and extra parameters set --net=container:OpenVPN , change the ports to something other than 8080 and install. The container installs fine, starts up but it ignores my port settings and uses default ports including 8080 for the webUI which causes conflicts. I suspect if you set the network to none, it ignores any port settings you specify cause without a network they are not necessary.
How does one go about setting the ports in a situation like this? I suspect others have ran into this issue as having each container use a separate instance of your paid VPN service will put you over the limit on simultaneous uses at some point if you add enough containers.
I have enabled advanced options in the docker settings so I have access to more things, tried editing the container port on creation with the extra options and it still invalidates any settings you do and reverts to using the default ports regardless.
-
Booted up default Arma 3 server container and get what I believe is the error here:
/opt/scripts/start-server.sh: line 54: 74 Segmentation fault ./arma3server ${GAME_PARAMS}I have done nothing to the GAME_PARAMS setting in the docker config this was just for a test boot before adding mods. The rest of the log looks fairly standard. Perhaps an update has broken something?
Edit: There is this at the front of the log might be of some help
Success! App '233780' already up to date. ---Prepare Server--- ---server.cfg found... ---Start Server--- 14:59:44 Could not enable linux core dumps. Error 1 - � 14:59:44 SteamAPI initialization failed. Steam features won't be accessible! -
Having strange issues on trying to add/edit a folder after an update to the plugin recently to latest version (2021.03.14).
Issue breakdown.
1) Adding a new folder after the update as normal created a folder called "undefined" and i can not edit it or do anything now, not even remove it. Trying to change the name, add icon, add in dockers, clicking submit does nothing. If you click submit without a name it alerts to add a name as normal but once you add in a name it still does not save.
2) Later inspection of existing folders before the update they all still exist and function but I can not do anything new to them.
3) Trying to create another new folder does not work either, brings you to settings and clicking submit does nothing.
Things I have tried:
-Disable > Enable docker from settings
-Rebooting the entire Unraid server
Possible Cause: I might have tried to pull a docker into the folder that already had a folder? I can't exactly tell as to what I did cause i can't edit and the folder acts as if its a phantom, and I can't find any logs anywhere pertaining to this plugin. I also used a 600x600 or so png file for the icon, maybe it did not like that but not really been a problem before.
Not sure it will help, but here is a screen of the folder.
Solution: Uninstall > Reinstall the plugin seems to have fixed my issue now, whatever it was. I did lose all my folders but it's fixable and at least working now.
-
1
-
-
Did anything change with Element ? Somehow my server has completely halted on sending messages. The server shows up like everything is fine and connected just can't send any messages.
Matrix server seems ok, however I am getting a weird error with Element:
2021/02/17 15:00:32 [error] 21#21: *48 open() "/usr/share/nginx/html/config.chat.mydomain.net.json" failed (2: No such file or directory), client: 172.18.0.2, server: localhost, request: "GET /config.chat.mydomain.net.json?cachebuster=1613592032263 HTTP/1.1", host: "chat.mydomain.net"I have not done any changes and this happened right after an update so I believe something has been broken by either the matrix update or element update recently. Before I go breaking things thought I would check for any tips or suggestions on recent changes maybe I missed.
-
just a heads up with Eco, there is now a native linux server, should be way better for a container.
Latest Patch Notes:
QuoteVersion 9.0.2 has been released and fixes the following issues:
-Linux Client is now available (Including server and - for the first time - singleplayer)
-IP binding for the webserver is now working correctly
-Maximum amount to buy in the purchase list now updates correctly
-The button to choose the type of road in road contracts can be clicked again
-The last clause of a contract can be moved and removed again
-
1
-
-
I may have found out what the issue is with new installs after June 2020, while combing through the github I found this under:synapse / docs / ACME.mdQuoteDeprecation of ACME v1
In March 2019, Let's Encrypt announced that they were deprecating version 1 of the ACME protocol, with the plan to disable the use of it for new accounts in November 2019, for new domains in June 2020, and for existing accounts and domains in June 2021.
Synapse doesn't currently support version 2 of the ACME protocol, which means that:
for existing installs, Synapse's built-in ACME support will continue to work until June 2021.
for new installs, this feature will not work at all.
Either way, it is recommended to move from Synapse's ACME support feature to an external automated tool such as certbot (or browse this list for an alternative ACME client).
so it seems now the built in ACME is non-functioning for new installs, breaking everything. So now you are to use certbot to place the files in the tls directory for tls authentication. Instructions will have to be reworked to reflect this or containers updated.If any of this is wrong please let me know so I can edit. ThanksEdit- 9/20/20 - I fixed my issue, you can't edit the homeserver.yaml and have it existing before you create the container, something bugs in generation.
-
I may have figured out what the issue is, I found this while combing through the github, under:synapse / docs / ACME.mdit says as follows:QuoteDeprecation of ACME v1
In March 2019, Let's Encrypt announced that they were deprecating version 1 of the ACME protocol, with the plan to disable the use of it for new accounts in November 2019, for new domains in June 2020, and for existing accounts and domains in June 2021.
Synapse doesn't currently support version 2 of the ACME protocol, which means that:
for existing installs, Synapse's built-in ACME support will continue to work until June 2021.
for new installs, this feature will not work at all.
Either way, it is recommended to move from Synapse's ACME support feature to an external automated tool such as certbot (or browse this list for an alternative ACME client).
I think this may be what the issue is for me, ACME is broken and killing the whole process. So I guess the only way forward is to sign it with certbot somehow...if I can figure it out I will write up some kind of tutorial. Maybe A75G can tweak the container to automatically do a certbot for ACME to function.Please ping me and let me let me know if anything is wrong here so I can edit.Edit- 9/20/20 - I fixed my issue, you can't edit the homeserver.yaml and have it existing before you create the container, something bugs in generation.
-
13 minutes ago, N¿¿B said:
Can't confirm, but I don't think anything should have changed after the update. My instance is still running fine. Did you have a working instance prior to the update?
Yea that's what I've heard from others as well. Existing installs prior to the update still work fine.
I don't doubt the few guide sets I've read as people have posted that they installed successfully just fine with them. Which is why I think something in the first file generation has changed that breaks everything now maybe. I did get a sample homeserver.yaml file to cross compare with and I noticed a lot more things was commented out on the generated file vs on the existing file someone shared with me they say is working.
I will try uncommenting everything that does not say optional and try that. I think maybe something was commented out on the new file vs the old file that is crucial somehow or a new feature.
-
Yea I have been having a similar issue for a few days in a fresh install. I am currently trying to track down exactly what changed to cause this.
Can anyone confirm after the July update that they have clean complete installed this following instructions and it works? Like boots up, no errors?
-
On 8/10/2020 at 1:29 PM, A75G said:
I'm still running my Matrix Server and it working really fine with postgres database and redis.
Permission issue it normal you need open with nano(cli) or use file managers that are available on CA.
I forgot how i set it up but ill upload my config and see what you did wrong (password and domain will be removed so dont just copy and paste).
If you are not using postgres or redis remove it and keep sqlite.
I followed the tutorial on Page 2, and a few other tutorials i found online. I seem to end up with it non-functioning when all the instructions said keep most all of it default initially and it should work. I believe something changed with the initial setup process in first generation of the files that does not effect existing setups perhaps (cause existing does no generation as it all exist).
Thanks for the file I will cross compare and tweak around work more on it see if I can figure out exactly whats going on.
Edit 8/11/20 - According to another post it seems others are getting a similar issue since a July update to Matrix, I guess I will have to go through everything step by step code wise to see what's changed and what exactly it going on. Normally I am good with following instructiins and I've done many things in unraid following a guide just fine. Matrix I've followed 3 different sets of instructions and they all seem to fail to get the server to function. Here is another reference to a similar problem in another topic on the forum if anyone happens across my post and is trying to track down the issue with me.
-
On 8/8/2020 at 4:18 PM, Stubbs said:
I'm trying to set up a Matrix server. I followed the tutorial, but still get this in the log:
-=> generate turn config -=> generate synapse config Generating config file /data/homeserver.tmp Generating log config file /data/matrix.log.config which will log to /homeserver.log Generating signing key file /data/matrix.signing.key A config file has been generated in '/data/homeserver.tmp' for server name 'matrix'. Please review this file and customise it to your needs. -=> configure some settings in homeserver.yaml -=> configure some settings in matrix.log.config -=> you have to review the generated configuration file homeserver.yaml -=> start turn -=> start matrix Cannot create pid file: /var/run/turnserver.pid: Permission denied socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported This server is configured to use 'matrix.org' as its trusted key server via the 'trusted_key_servers' config option. 'matrix.org' is a good choice for a key server since it is long-lived, stable and trusted. However, some admins may wish to use another server for this purpose. To suppress this warning and continue using 'matrix.org', admins should set 'suppress_key_server_warning' to 'true' in homeserver.yaml. -------------------------------------------------------------------------------- 2020-08-09 05:57:48,368 - twisted - 192 - INFO - None - Redirected stdout/stderr to logs 2020-08-09 05:57:48,369 - root - 257 - WARNING - None - ***** STARTING SERVER ***** 2020-08-09 05:57:48,369 - root - 258 - WARNING - None - Server /usr/local/lib/python3.7/dist-packages/synapse/app/homeserver.py version 1.18.0 2020-08-09 05:57:48,369 - root - 259 - INFO - None - Server hostname: matrix 2020-08-09 05:57:48,369 - root - 260 - INFO - None - Instance name: master 2020-08-09 05:57:48,369 - synapse.app.homeserver - 372 - INFO - None - Setting up server 2020-08-09 05:57:48,369 - synapse.server - 281 - INFO - None - Setting up. 2020-08-09 05:57:48,371 - twisted - 192 - ERROR - - Traceback (most recent call last): 2020-08-09 05:57:48,371 - twisted - 192 - ERROR - - File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main 2020-08-09 05:57:48,372 - twisted - 192 - ERROR - - "__main__", mod_spec) 2020-08-09 05:57:48,372 - twisted - 192 - ERROR - - File "/usr/lib/python3.7/runpy.py", line 85, in _run_code 2020-08-09 05:57:48,372 - twisted - 192 - ERROR - - exec(code, run_globals) 2020-08-09 05:57:48,372 - twisted - 192 - ERROR - - File "/usr/local/lib/python3.7/dist-packages/synapse/app/homeserver.py", line 687, in <module> 2020-08-09 05:57:48,373 - twisted - 192 - ERROR - - main() 2020-08-09 05:57:48,373 - twisted - 192 - ERROR - - File "/usr/local/lib/python3.7/dist-packages/synapse/app/homeserver.py", line 682, in main 2020-08-09 05:57:48,374 - twisted - 192 - ERROR - - hs = setup(sys.argv[1:]) 2020-08-09 05:57:48,374 - twisted - 192 - ERROR - - File "/usr/local/lib/python3.7/dist-packages/synapse/app/homeserver.py", line 375, in setup 2020-08-09 05:57:48,375 - twisted - 192 - ERROR - - hs.setup() 2020-08-09 05:57:48,375 - twisted - 192 - ERROR - - File "/usr/local/lib/python3.7/dist-packages/synapse/server.py", line 283, in setup 2020-08-09 05:57:48,376 - twisted - 192 - ERROR - - self.datastores = DataStores(self.DATASTORE_CLASS, self) 2020-08-09 05:57:48,376 - twisted - 192 - ERROR - - File "/usr/local/lib/python3.7/dist-packages/synapse/storage/data_stores/__init__.py", line 49, in __init__ 2020-08-09 05:57:48,376 - twisted - 192 - ERROR - - with make_conn(database_config, engine) as db_conn: 2020-08-09 05:57:48,377 - twisted - 192 - ERROR - - File "/usr/local/lib/python3.7/dist-packages/synapse/storage/database.py", line 110, in make_conn 2020-08-09 05:57:48,377 - twisted - 192 - ERROR - - db_conn = engine.module.connect(**db_params) 2020-08-09 05:57:48,377 - twisted - 192 - ERROR - - sqlite3.OperationalError: unable to open database file
I get the same exact thing been fighting it for days. Also had permission locked homeserver.yaml files as well as the random red errors...this is about as far as I have got with the errors gone, and still does not work. I have installed fresh to different appdata directories about 5 times.... I think something changed with the matrix codebase and the docker setup is borked now.
Here is a snip for about as far as I was able to get maybe be of some use, but mainly I think I was just changing things and ended up breaking something else.
0: IO-=> start turn -=> start matrix Cannot create pid file: /var/run/turnserver.pid: Permission denied 0: log file opened: /var/tmp/turn_8_2020-08-10.log 0: RFC 3489/5389/5766/5780/6062/6156 STUN/TURN Server Version Coturn-4.5.1.1 'dan Eider' 0: Max number of open files/sockets allowed for this process: 40960 0: Due to the open files/sockets limitation, max supported number of TURN Sessions possible is: 20000 (approximately) 0: ==== Show him the instruments, Practical Frost: ==== 0: TLS supported 0: DTLS supported 0: DTLS 1.2 supported 0: TURN/STUN ALPN supported 0: Third-party authorization (oAuth) supported 0: GCM (AEAD) supported 0: OpenSSL compile-time version: OpenSSL 1.1.1d 10 Sep 2019 (0x1010104f) 0: 0: SQLite supported, default database location is /var/lib/turn/turndb 0: Redis supported 0: PostgreSQL supported 0: MySQL supported 0: MongoDB is not supported 0: 0: Default Net Engine version: 3 (UDP thread per CPU core) ===================================================== 0: Domain name: 0: Default realm: turn.bridge.mydomain.dev 0: CONFIGURATION ALERT: You specified --lt-cred-mech and --use-auth-secret in the same time. Be aware that you could not mix the username/password and the shared secret based auth methohds. Shared secret overrides username/password based auth method. Check your configuration! 0: ERROR: CONFIG ERROR: Empty cli-password, and so telnet cli interface is disabled! Please set a non empty cli-password! 0: WARNING: cannot find certificate file: /data/bridge.mydomain.dev.tls.crt (1) 0: WARNING: cannot start TLS and DTLS listeners because certificate file is not set properly 0: WARNING: cannot find private key file: /data/bridge.mydomain.dev.tls.key (1) 0: WARNING: cannot start TLS and DTLS listeners because private key file is not set properly 0: WARNING: cannot find DH key file: /data/bridge.mydomain.dev.tls.dh (1) 0: NO EXPLICIT LISTENER ADDRESS(ES) ARE CONFIGURED 0: ===========Discovering listener addresses: ========= 0: Listener address to use: 127.0.0.1 0: Listener address to use: 172.18.0.3 0: ===================================================== 0: Total: 1 'real' addresses discovered 0: ===================================================== 0: NO EXPLICIT RELAY ADDRESS(ES) ARE CONFIGURED 0: ===========Discovering relay addresses: ============= 0: Relay address to use: 172.18.0.3 0: ===================================================== 0: Total: 1 relay addresses discovered 0: ===================================================== 0: Cannot create pid file: /var/run/turnserver.pid 0: pid file created: /var/tmp/turnserver.pid 0: IO method (main listener thread): epoll (with changelist) 0: Wait for relay ports initialization... 0: relay 172.18.0.3 initialization... 0: relay 172.18.0.3 initialization done 0: Relay ports initialization done 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=0 created 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=1 created 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=3 created 0: turn server id=2 created 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=4 created 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=6 created 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=5 created 0: turn server id=7 created 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=8 created 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=9 created 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=10 created 0: turn server id=11 created 0: IO method (general relay thread): epoll (with changelist) 0: IO method (general relay thread): epoll (with changelist) 0: turn server id=12 created 0: IO method (general relay thread): epoll (with changelist) socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported socket: Protocol not supported Traceback (most recent call last): File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib/python3.7/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/local/lib/python3.7/dist-packages/synapse/app/homeserver.py", line 687, in <module> main() File "/usr/local/lib/python3.7/dist-packages/synapse/app/homeserver.py", line 682, in main hs = setup(sys.argv[1:]) File "/usr/local/lib/python3.7/dist-packages/synapse/app/homeserver.py", line 351, in setup "Synapse Homeserver", config_options File "/usr/local/lib/python3.7/dist-packages/synapse/config/_base.py", line 619, in load_or_generate_config config_dict, config_dir_path=config_dir_path, data_dir_path=data_dir_path File "/usr/local/lib/python3.7/dist-packages/synapse/config/_base.py", line 641, in parse_config_dict data_dir_path=data_dir_path, File "/usr/local/lib/python3.7/dist-packages/synapse/config/_base.py", line 266, in invoke_all res[name] = getattr(config, func_name)(*args, **kwargs) File "/usr/local/lib/python3.7/dist-packages/synapse/config/repository.py", line 108, in read_config config.get("media_store_path", "media_store") File "/usr/local/lib/python3.7/dist-packages/synapse/config/_base.py", line 173, in ensure_directory os.makedirs(dir_path) File "/usr/lib/python3.7/os.py", line 211, in makedirs makedirs(head, exist_ok=exist_ok) File "/usr/lib/python3.7/os.py", line 221, in makedirs mkdir(name, mode) PermissionError: [Errno 13] Permission denied: '/DATADIR'
-
3 minutes ago, dlandon said:
Update UD. It should work now.
That it does, amazing and ultra fast update dlandon ❤️ my hero!
-
yog-sothoth-diagnostics-20200112-0652.zip Hmm, alright, from what I can tell it looks ok but I am new
Edit: OH I see, cool thanks for the update dlandon! ❤️
-
I am having a really strange issue...UD Settings > Destructive Mode refuses to save when I click apply it reverts to Disabled.
I have UD and UD+ installed, I am on 6.8.0 Version.
I have tried to reset everything by Uninstalling both UD+ and UD, and reinstalling, rebooting, fixing permissions...for some reason it refuses to work
Any ideas that could help me fix it? Thanks!
[Support] ich777 - Gameserver Dockers
in Docker Containers
Posted · Edited by l2evy
Sorry forgot to mention I am using a lot of mods >.< , I have since trimmed a lot out. I will try that command and see what happens, hopefully it will resolve the issue as the mods I have are not "too" big and should have more than enough ram to handle it.
Edit: That command seems to have worked! Thanks a bunch! I will report back if I get any kind of similar issue later on with ram. I assume you meant I have to issue the command on complete unraid reboot not game server reboot, in which case that happens not very often. I will have to look into that command further and potentially have it run on boot perhaps.