cenzar

This ended up fixing the issue I quadrupled the size of the arc and it is no longer having this issue. Hopefully once they release future updates allowing it to be dynamic there can be an easier solution.

I was looking at the logs is it possible unraid is spinning down disks and arc_evict then has no where to write to? Because the logs appear to stop outputting right after it lists drives it's spinning down then no longs until I ssh in. My current set up is 2 SSD cache pools, 1 is in a raid setup (i forget which number) but it is 3 drives all ZFS, then the second is raid 0 with ZFS (snapshotting it to HDD ZFS pools), and each drive in my system is ZFS formatted to be the hybrid ZFS system.

What exactly is arc_evict and what would cause it to run, and what would lead to it running at 100% for hours on end. These days my server isn't crashing but it's spending more time maxed out on running arc_evict then anything else. I'm currently away so currently i'm not in a position that make it easy to copy logs but when I return to the server I can, and is it ok to post the logs here or do I need to check anything to anonymise it.

That would make sense the diagnostics I got after rebooting so I'm realizing now they may not be relevant to solving this arc_evict issue

Yeah plex was streaming and recording live TV. I was unable to interact with the dashboard and didn't try turning it off but i'm fairly certain it was caused by the arc_evict process that stopped all containers and other processes. I attached the ouput of the top command from when I used ssh into the system.

I have had this issue a few times where everything on my server stops working and the top menu shows the command `arc_evict` at 100% on the CPU. At the same time of this happening everything else appears to shutdown or at least cease to respond including the dashboard, all my docker containers, VMs, SAMBA, etc. The only thing that appears to work is ssh but sometimes that freezes up too. In the past i've been able to shutdown via ssh access or in the past had to restart physically after hours of unresponsiveness from the server. For context all my drives do use ZFS cache pools together and individual hard drives are individual ZFS pools. I attached the diagnostics from my server after reboot. scarif-diagnostics-20240403-2127.zip

The solution, at least as of the last two weeks was just to upgrade to the updated version on unraid, I had held off due to high use on my server but once I updated things haven't been crashing. Still not really sure how this all started, but it is resolved now.

I appreciate the quick response, I did realize the syslog server was writing to a share so it's possible that went down when things froze up I updated it to store a copy on flash if it happens again i'll try to figure out what happened and I will try the safe mode, is there any other tools to check hardware for these potential issues?

This has happened two days in a row. I'm unsure the reason but things will freeze up. Yesterday this happened while I was working with a minecraft server in a docker container today it happened while working in a VM on some more demanding processes. I had something similar a few weeks back I think top showed something related to a process with `arc` in the name. I attached system diagnostics and the logs from my syslog. scarif-diagnostics-20240226-2306.zip syslog-192.168.1.64.log

Hello, I keep receiving notifications from that my log is filling up even though my server wasn't running for a very long time. I attached the diagnostics and could use some help figuring out if there is an issue and how to lower the log output. scarif-diagnostics-20240206-0851.zip

I'm trying to setup sharelatex and i'm hitting an issue with mongodb but I'm using the version specified by the overleaf setup mongo:4.4. Is there something i'm missing or something I should have setup in mongodb or sharelatex differently? mongodb was setup just by installing the template from community applications and I attached an image of my sharelatex docker config. I haven't found anything online that explains any steps besides just installing redis, mongodb, and sharelatex so i'm really confused why this is an issue given i matched the mongodb version as mentioned. *** Running /etc/my_init.d/00_make_sharelatex_data_dirs.sh... *** Running /etc/my_init.d/00_regen_sharelatex_secrets.sh... *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/00_restore_site_status... *** Running /etc/my_init.d/00_set_docker_host_ipaddress.sh... *** Running /etc/my_init.d/01_nginx_config_template.sh... *** Running /etc/my_init.d/10_delete_old_logs.sh... *** Running /etc/my_init.d/10_syslog-ng.init... *** Running /etc/my_init.d/98_check_db_access.sh... Mongo instance doesn't support transactions MongoServerError: Transaction numbers are only allowed on a replica set member or mongos at Connection.onMessage (/overleaf/services/web/node_modules/mongodb/lib/cmap/connection.js:231:30) at MessageStream.<anonymous> (/overleaf/services/web/node_modules/mongodb/lib/cmap/connection.js:61:60) at MessageStream.emit (node:events:517:28) at processIncomingData (/overleaf/services/web/node_modules/mongodb/lib/cmap/message_stream.js:125:16) at MessageStream._write (/overleaf/services/web/node_modules/mongodb/lib/cmap/message_stream.js:33:9) at writeOrBuffer (node:internal/streams/writable:392:12) at _write (node:internal/streams/writable:333:10) at Writable.write (node:internal/streams/writable:337:10) at Socket.ondata (node:internal/streams/readable:777:22) at Socket.emit (node:events:517:28) { ok: 0, code: 20, codeName: 'IllegalOperation', [Symbol(errorLabels)]: Set(0) {} } *** /etc/my_init.d/98_check_db_access.sh failed with status 1 *** Killing all processes... generating random secrets Nginx: generating config file from template Nginx: reloading config * Reloading nginx configuration nginx ...done. Jan 19 11:55:01 a55d3b55d698 syslog-ng[89]: syslog-ng starting up; version='3.25.1'

No, I wasn't able to find a fix, I switched to a different docker app

https://github.com/photoprism/photoprism/discussions/2698#discussioncomment-3674904

I'm having an issue where after a couple of days running on my unraid server the webui becomes inaccessible. My browser can no longer access it, the logs don't show any errors. The only thing that occurs on my server is a back up and auto update process, i'm wondering if it has issues with the docker shutting down and restarting after a backup. Any assistance would be greatly appreciated, currently I usually have to reinstall the docker container to get the ui working again.

Thanks I think the space is the issue. I was also setting it to large values just in case the -1 wasn't working as expected.