UNRA1DUser

Do you also know the reason for that? I mean I really like to host a palworld server. And it seems to work for a lot of people. I can’t understand why one container is freezing a whole server.

I will give it a try after we fixed the freezes. can those freezes really come from just the palworld docker ? Is that possible ?

Can I also increase the NIC RX and TC Buffer? Do you have experience with that ?

I started the Unraid Server in normal mode and disabled VMs and Dockers and stopped the Array. I also started a stress test. It´s running since 17:35. So about 1 hour for now. Server is still running. CPU Temp 72 C and the cpu Mhz is @ 4899.996 Mhz stress --cpu 20 --vm 125 --vm-bytes 1024M I can just see a lot of Network drops. Is that Normal?

I also get this Error Message in Unraid 6.12.8 Note that closing this window will abort the execution of this script Intel(R) Xeon(R) W-1290P CPU @ 3.70GHz Intel(R) Xeon(R) W-1290P CPU @ 3.70GHz To Be Filled By O.E.M. CPU @ 2.6GHz ERROR:root:Failed to apply core: set -99.609375, read 0.0 temperature target: -0 (100C) core: 0.0 mV gpu: 0.0 mV cache: 0.0 mV uncore: 0.0 mV analogio: 0.0 mV powerlimit: 250.0W (short: 0.00244140625s - enabled) / 125.0W (long: 224.0s - enabled) turbo: enable Is there a fix for that?

I closed the memtest86 now. 4 Passes again without Errors.

Than it should be something like 2-4 Hours. I will stop the memtest86 now and start the Unraid Server in safe mode without Docker, VM and Plugins. I will also start a stress test to get some load on it. Let´s see whats gonna happening.

I can try that. Is there a problem if I stress test the Server in that mode? Otherwise there wouldn´t be any load to it. And how long should the Server run in that mode? As I know than the Server is running and running without problems. But there is also nothing installed that is using a lot of Resources of the Server itself. Last time I started the Unraid Server I stopped the Palworld Server and it runs for 4-5 hours before I restartet it by myself and tried another test (Went to sport in the mean time and forgot to start the Palworld Server again). I don´t know anymore if this was in safe mode or not. As I remember correctly the freezes started after I installed Palworld. But it´s not my first time that the Server is freezing -> After I bought this "Adapter" and connected it to the internal USB2.0 Port those freezes were gone. But I think I also played around and removed some Dockers. So could be possible that also another Docker was the reason for that. So should I abort my current running memtest86 and start the unraid server normally without the Palworld Docker and see if its running? Or should I first boot Unraid into safe mode without Docker, VMs and Plugins and wait for some hours ?

So you mean disable docker service and start a Benchmark on CPU and RAM? Would that stress the CPU and RAM correctly? I have 128GB RAM and 20 threads. 128 GB = 128000 MB / 1024 MB = 125 stress --cpu 20 --vm 125 --vm-bytes 1024M Or should I also stress the Storage and IO ? Is that the right Syntax? stress --cpu 20 --vm 125 --vm-bytes 1024M –hdd 20 –io 20 Besides that, my last memtest86 was running 21 hours and passed 5 times. Is that enough? Should I stop my current second memtest86 run? It´s actually running for 15 hours and has 3 passes.

Hi, I've been struggling with freezes again for a few weeks now. I have already tested the following: I bought a new PSU and connected it (FAILED) Removed powertop. Also every setting in the Go file. (FAILED) Removed Tips & Tweaks (FAILED) Removed my undervolting in the BIOS (FAILED) I ran Unraid in safe mode without any Plugins. Just the Dockers are running. VM is completly disabled (FAILED) I changed the USB-Stick from SanDisk Ultra Fit USB 3.2 Flash-Laufwerk 32 GB to Samsung BAR Plus USB-Stick Typ-A, 64 GB (FAILED) I also changed my MZHOU USB 3.1 zu 3.0 Adapter,Interner 19-Poliger Header Auf USB 3.1/Typ C 20-Poliger TYP-E - Frontplatten Adapter Unterstützungssysteme - WINXP/ 7/8 / 10 32 / 64BIT / MAC/Linux Adapter (FAILED) Also tried a different USB 2.0 Port with the Adapter (FAILED) Docker is set to IPVLAN (FAILED) I started a memtest86 and let it run for 21 hours. 5 passes without errors. 4x32GB ECC RAM - 128GB (Successfull) I have started a stress test for the CPU. It ran for just over an hour on all cores. CPU had 70 degrees. -> stress --cpu 20 (Successfull) I ran scrub on my Cache Pool. 2x SK hynix Gold P31 2TB PCIe NVMe Gen3 M.2 2280 in a ZFS-Encrypted - Mirror (Successfull) I ran SMART tests on both 12TB WD Red Plus WD120EFBX 256MB 3.5" (8.9cm) SATA 6Gb/s. (Successfull) I am out of Ideas. Currently I am running another memtest86 on all RAM. I think my server has been crashing ever since I started running the Palworld server. But I don't think it's because of this Docker or does anyone has the same behavior ? In that Topic you can see my BIOS settings (I removed the OC -> "Dynamic Vcore (DVID)" set to "auto" AND "PCH Core" set to "auto"): What else could I do? Thanks! tower-diagnostics-20240314-2102.ziptower-syslog-20240312-1118.ziptower-syslog-previous-20240312-1117.zip

Hallo zusammen, kann mir eventuell einer erklären wann und wie man PUID, PGID und UMASK für Docker Templates verwendet? Reicht das Flag "--user=99:100" in den ExtraParams oder lieber doch die Variablen dem Docker mitgeben? Gibt es da einen unterschied? Kann man die Variablen immer mit geben oder muss das Image diese auch zulassen? <Config Name="PUID" Target="PUID" Default="99" Mode="" Description="UID for permissions. Do not change unless you know what you're doing." Type="Variable" Display="advanced" Required="true" Mask="false"/> <Config Name="PGID" Target="PGID" Default="100" Mode="" Description="GID for permissions. Do not change unless you know what you're doing." Type="Variable" Display="advanced" Required="true" Mask="false"/> <Config Name="UMASK" Target="UMASK" Default="022" Mode="" Description="UMASK for newly created files. Do not change unless you know what you're doing." Type="Variable" Display="advanced" Required="false" Mask="false"/> Manchmal setzte ich das Flag "--user=99:100" und der Container funktioniert nicht. Nur ohne Flag funktioniert dieser. Manchmal muss ich auch nur die Variablen mitgeben. Manchmal beides. Ich verstehe das nicht so ganz. Danke!

I changed the PSU but the Server still get freezes. At the Weekend I will put some new paste on the CPU and test again.

Also in safe mode the Server restarts or freezes. I bought a new PSU and will check if it´s still restarting. If not it´s the PSU. If yes I will check the CPU cooling. I also did a Memtest and it passed 4-5 times. So the RAM is good.

Perfect, it´s working!

Hey, I started Unraid in safe mode and got this Error. Is that normal?

I have now started the UNRAID Server in Save mode and started all of my dockers to get some heat on the CPU and using as much power as possible from the PSU. Let´s see whats happening.

Is there maybe a CPU stress test for Unraid to test the CPU overheating? I also put my FAN Speed to 100% and the temps looked good so far. Maybe I should try another PSU.

The server was started shortly before 10 o'clock this morning. I logged in and entered the passphrase. Array started. Then I went to sport. About 2 hours later I open Unraid again and see that Unraid has restarted. I am at the login screen again and have to enter the passphrase to start the array. Enclosed are the logs. Does anyone have an idea? Why the Server restarted? Thanks! tower-syslog-20240312-1034.zip tower-syslog-previous-20240312-1033.zip

Support for Docker image Redis-Official Application: Redis - https://redis.io/ Docker Hub: https://hub.docker.com/_/redis GitHub: https://github.com/redis/redis Documentation: https://redis.io/docs/ Overview: Redis is an open-source, networked, in-memory, key-value data store with optional durability. It is written in ANSI C. The development of Redis is sponsored by Redis Labs today; before that, it was sponsored by Pivotal and VMware. According to the monthly ranking by DB-Engines.com, Redis is the most popular key-value store. The name Redis means REmote DIctionary Server. wikipedia.org/wiki/Redis This container is configured using the official redis.conf file! I have limited this Docker to 10 GB. If you want to use less or more RAM, you can change this under "Extra Parameters" -> "--memory=10G". You can also delete this value completely if you want the Docker to use as much RAM as necessary. After you started this Container the first time and the folder has been created. Stop the Server and upload the "redis.conf" file from "https://github.com/UNRA1DUser/unraid-docker-templates/blob/main/.conf/redis.conf" into your "/redis-official/conf" folder! Otherwithe this Container won´t start!

Sorry for my late response! Yes it´s under the 'advanced view'. I'm glad this has helped. If you remove the "mysqld --log-error=/var/log/mysql/error.log" out of the Post Arguments you wouldn´t get any kind of logs into the folder. Maybe try mysqld --log-error=/var/log/mysql/error.log --secure-file-priv=""

Thanks! In the OnlkyOffice Forum is no one helping. They are just telling me, that I should use a newer Docker Version and than it should work.

I created the following Docker with the Instructions from OnlyOffice. onlyoffice-mysql-server: mysql:8.0.29 onlyoffice-community-server: onlyoffice/communityserver:12.0.1.1748 onlyoffice-elasticsearch: onlyoffice/elasticsearch:7.16.3 onlyoffice-document-server: onlyoffice/documentserver:7.1.1.23 onlyoffice-mail-server: onlyoffice/mailserver:1.6.75 onlyoffice-control-panel: onlyoffice/controlpanel:3.1.1.467 Every Server except the onlyoffice-community-server is working as expected. If I start the community Server I get those Docker logs. sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' sed: -e expression #1, char 52: unknown option to `s' + find /var/www/onlyoffice/WebStudio -type f -name '*.json' -exec sed -i 's_\("core.machinekey":\|"machinekey":\).*,_\1 "core_secret",_' '{}' ';' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' + for i in "${!binDirs[@]}" + find /etc/onlyoffice/communityserver -type f -name '*.[cC]onfig' -exec sed -i '/core.\machinekey/s_\(value\s*=\s*"\)[^"]*"_\1core_secret"_' '{}' ';' sed: -e expression #1, char 52: unknown option to `s' + find /etc/onlyoffice/communityserver -type f -name '*.json' -exec sed -i 's_\("core.machinekey":\|"machinekey":\).*,_\1 "core_secret",_' '{}' ';' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' sed: -e expression #1, char 53: unknown option to `s' + continue + sed 's/{{APP_NIGNX_KEEPLIVE}}/32/g' -i /app/config/nginx/prepare-onlyoffice + bash -c 'echo "onlyoffice ALL=(ALL) NOPASSWD: /usr/sbin/service" | (EDITOR="tee -a" visudo)' onlyoffice ALL=(ALL) NOPASSWD: /usr/sbin/service + '[' false == true ']' + systemctl enable redis-server.service Synchronizing state of redis-server.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable redis-server + service redis-server start /etc/init.d/redis-server: 51: ulimit: error setting limit (Operation not permitted) Starting redis-server: redis-server. + redis-cli config set save '' OK + redis-cli config rewrite OK + redis-cli flushall OK + service redis-server stop Stopping redis-server: redis-server. + '[' SERVER == SERVICES ']' + systemctl enable monoserveApiSystem.service ++ seq 1 1 + for serverID in $(seq 1 ${APP_MONOSERVE_COUNT}) + index=1 + '[' 1 == 1 ']' + index= + systemctl enable monoserve.service + chown -R onlyoffice:onlyoffice /var/log/onlyoffice + chown -R onlyoffice:onlyoffice /var/www/onlyoffice/DocumentServerData ++ ls -alhd /var/www/onlyoffice/Data ++ awk '{ print $3 }' + '[' onlyoffice '!=' onlyoffice ']' + '[' '!' -d /var/www/onlyoffice/Data/Index/v7.16.3 ']' + mkdir -p /var/log/onlyoffice//Index + mkdir -p /var/www/onlyoffice/Data/Index/v7.16.3 ++ ls -alhd /var/www/onlyoffice/Data/Index/v7.16.3 ++ awk '{ print $3 }' + '[' elasticsearch '!=' elasticsearch ']' + chown -R elasticsearch:elasticsearch /var/log/onlyoffice//Index + dpkg -l + grep -q onlyoffice-xmppserver + sed '/web\.talk/s/value=\"\S*\"/value=\"true\"/g' -i /var/www/onlyoffice/WebStudio/web.appsettings.config + sed '/web\.chat/s/value=\"\S*\"/value=\"false\"/g' -i /var/www/onlyoffice/WebStudio/web.appsettings.config + systemctl stop onlyofficeRadicale System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeTelegram System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeSocketIO System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeThumb System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeFeed System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeIndex System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeJabber System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeMailAggregator System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeMailWatchdog System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeMailCleaner System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeMailImap System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeNotify System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeBackup System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeStorageMigrate System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeStorageEncryption System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeUrlShortener System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeThumbnailBuilder System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop onlyofficeAutoCleanUp System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop god System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl enable god + systemctl stop elasticsearch System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop redis-server System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop mysql System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop nginx System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl stop monoserveApiSystem.service System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl enable monoserveApiSystem.service ++ seq 1 1 + for serverID in $(seq 1 ${APP_MONOSERVE_COUNT}) + index=1 + '[' 1 == 1 ']' + index= + systemctl stop monoserve.service System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down + systemctl enable monoserve.service + '[' false == true ']' + systemctl enable onlyofficeRadicale.service + systemctl enable onlyofficeTelegram.service + systemctl enable onlyofficeSocketIO.service + systemctl enable onlyofficeThumb.service + systemctl enable onlyofficeFeed.service + systemctl enable onlyofficeIndex.service + systemctl enable onlyofficeJabber.service + systemctl enable onlyofficeMailAggregator.service + systemctl enable onlyofficeMailWatchdog.service + systemctl enable onlyofficeMailCleaner.service + systemctl enable onlyofficeMailImap.service + systemctl enable onlyofficeNotify.service + systemctl enable onlyofficeBackup.service + systemctl enable onlyofficeStorageMigrate.service + systemctl enable onlyofficeStorageEncryption.service + systemctl enable onlyofficeUrlShortener.service + systemctl enable onlyofficeThumbnailBuilder.service + systemctl enable onlyofficeAutoCleanUp.service Failed to enable unit, unit onlyofficeAutoCleanUp.service does not exist. + '[' SERVER == SERVER ']' + mv /app/config/nginx/prepare-onlyoffice /etc/nginx/sites-enabled/onlyoffice + service nginx stop * Stopping nginx nginx ...done. + systemctl enable nginx.service Synchronizing state of nginx.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable nginx ++ ps auxf ++ grep cron ++ grep -v grep ++ awk '{print $2}' + PID= + '[' ONLYOFFICE-Elasticsearch-Official ']' + service elasticsearch stop elasticsearch: unrecognized service + systemctl disable elasticsearch.service Failed to disable unit, unit elasticsearch.service does not exist. + rm -f /usr/lib/systemd/system/elasticsearch.service + rm -f /etc/init.d/elasticsearch + '[' -n '' ']' + rm -dfr '/tmp/onlyoffice*' + rm -dfr '/var/run/onlyoffice/*' + rm -dfr '/var/cache/nginx/onlyoffice/*' + '[' true == true ']' + exec /lib/systemd/systemd Systemd is not working in Unraid Dockers. So I think that Docker is using systemctl instead. That should be fine. I also red on the ONLYOFFICE Page that the latest Version of Docker is needed to install it. Unraid is some versions behind the latest one. Is there a way to Update the Docker Version? Could that be the Problem? Or do you have any other Idea about it? Thanks!

Hi all, I am just wondering if there is a way to Update / Upgrade the Docker Version to the latest one? As I can read on the OnlyOffice Page. I need the latest Docker Version for there Dockers. Iam currently using the Unraid Version 6.12.6 Greetings

I just installed my 2 SSDs. I am suprised that I can also use a ZFS-Encrypted - Mirror. What is the difference between ZFS-Encrypted - Mirror and BTRFs-Encrypted - Raid 1? Is the ZFS-Encrypted - Mirror faster? My Array is configured as xfs-Encrypted. Just a site question. I have an Encrypted Cache and Array. Is the Parity disk also encrypted?

I have 2 M.2 SSDs with 2TB storage each. How would you set up the cache pool? I mainly have docker containers. There are also a few VMs created, but they are almost always off. - A backup is made to the array every evening using the CA Backup Appdata plugin. - The mover runs daily. - A UPS is also available. I think the best option here is raid 1. But raid 0 is a bit faster, right?