Good morning,

 

I have a problem with unraid, that it on and off crashes without writing errors in the log. Since I now finally got a KVM I am able to see what is happening across my server. 

 

So what is happening:

- Unraid GUI is not responding on requests

- NGINX ProxyManager is still working in the background as it looks like, as I still can access e.g. my KVM with its subdomain. 

- Some of my docker containers I still can reach via its IP adress and WebGUI and some not

- NGINX Proxy Manager is e.g. working via GUI, where Grafana and Bitwarden (and others) is not working anymore (getting a timeout when trying to reach it via IP and 502 Bad gateway, when trying to reach via subdomain)

- Also I cant connect via SSH anymore

 

 

This was the output, when I logged in this morning via my KVM:

 

 

When I tried to reload NGINX e.g.:

 

 

Any idea what I can do or how to give you more input?

 

Thanks in advance

 ...

Review:

make chagnes to nginx...

 

User script plugin at boot:

#!/bin/bash
# Unraid User Script to modify nginx.conf and restart Nginx

# Define file paths
NGINX_CONF="/etc/nginx/nginx.conf"
BACKUP_CONF="/etc/nginx/nginx.conf.bak"

# Backup the existing nginx.conf
if [ -f "$NGINX_CONF" ]; then
    cp "$NGINX_CONF" "$BACKUP_CONF"
    echo "Backup created at $BACKUP_CONF"
else
    echo "Error: $NGINX_CONF not found! Exiting."
    exit 1
fi

# Add the new configuration settings
sed -i '/^http {/a \    nchan_max_reserved_memory 64M;\n    nchan_message_timeout 30s;\n    nchan_message_buffer_length 100;' "$NGINX_CONF"

if [ $? -eq 0 ]; then
    echo "Nginx configuration updated successfully."
else
    echo "Error: Failed to update Nginx configuration."
    exit 1
fi

# Restart Nginx
/etc/rc.d/rc.nginx stop && /etc/rc.d/rc.nginx start

if [ $? -eq 0 ]; then
    echo "Nginx restarted successfully."
else
    echo "Error: Failed to restart Nginx. Check configuration."
    exit 1
fi

exit 0

Test and let us know whats up. Not sure whats causing these nginx issues I have not yet seen one in my testing...

Good morning,

 

when I do compare both NGINX Configs I see a difference. In the Backup/old config (.bak) file those three lines are missing:

 

 

nchan_max_reserved_memory 64M;
nchan_message_timeout 30s;
nchan_message_buffer_length 100;

 

Its working with the new .conf. I never touched the old config (as far as I remember, espcially not under UNRAID 7)

As those crashes are happening on a random base (did not happened for a while) I will report back once its not working anymore.

Good morning,

 

problem still occours, Server was not reachable anymore via Web, just via KVM.

 

This is what I got as an error message in the monitor:

 

When I tried to login it just logged in, then logged out directly:

 

As always: after a reboot its fine and I assume its fine for quiete some time now again.

Edited March 5, 20251 yr by Fabske

12 hours ago, Fabske said:

Good morning,

 

problem still occours, Server was not reachable anymore via Web, just via KVM.

 

This is what I got as an error message in the monitor:

 

When I tried to login it just logged in, then logged out directly:

 

As always: after a reboot its fine and I assume its fine for quiete some time now again.

 

upgrade to v7.0.1 and install the CA unraid patch.

v7.0.1 has a implementation that fixes nchan.

https://docs.unraid.net/unraid-os/release-notes/7.0.1/

 

Quote

Fix a possible cause of nchan memory leak

 

8 hours ago, bmartino1 said:

 

upgrade to v7.0.1 and install the CA unraid patch.

v7.0.1 has a implementation that fixes nchan.

https://docs.unraid.net/unraid-os/release-notes/7.0.1/

 

 

 

I upgraded before the crash to 7.0.1, but did nto restarted.

Now after I restarted and 7.0.1 was isntalled I had the crash once again this morning with the same error. 

Any chance to maybe create the monitor config from scratch? Otherwise I can post it here.

are you referring to a nginx configuration?

I don't know what you mean when you say monitor config.

you would have to share the user script monitor for me to read though and check what its doing. as it appears that the monitor script is causing the nginx issues...

Edited March 6, 20251 yr by bmartino1

On 3/6/2025 at 6:23 PM, bmartino1 said:

are you referring to a nginx configuration?

I don't know what you mean when you say monitor config.

you would have to share the user script monitor for me to read though and check what its doing. as it appears that the monitor script is causing the nginx issues...

 

 

Attached the requested Monitor file, which I was reffering to

monitor

How are you launching this web page?

This monitor script appears to be calling other emhttp php web pages and may not be using emhttp/nginx correctly... ??

this website php may need additional edits to close what's its is doing if ran mutule times. As that could cause the memory issues your experiencing...

as it appears your pulling unraisd web ui emhttp php pages that may not have or need additional code for you to use the monitor website?

 

require_once "$docroot/webGui/include/Helpers.php";
require_once "$docroot/webGui/include/Preselect.php";

 

https://github.com/unraid/webgui/blob/master/emhttp/plugins/dynamix/include/Helpers.php

https://github.com/unraid/webgui/blob/master/emhttp/plugins/dynamix/include/Preselect.php

 

are you looking to monitor unraid dashboard for changes?

what is the purpose of the monitor web page causing you the nchan issues?

as there are dockers and other that exist in monitoring unraid:

including limetiech unraid guide for 2 docker  monitoring:
https://unraid.net/blog/prometheus?srsltid=AfmBOoquq94ePPcvwb4Ux_JicpQsoeU5hZdL8G75KkOIgCwP1A4R4amv

 

Analysis of the monitor Script

The monitor script is a PHP-based monitoring tool for Unraid, primarily responsible for checking disk health, temperature, SMART status, usage, and parity operations, and sending notifications via notify.

 

The exit status 1 error suggests that something is causing the script to terminate unexpectedly. Here are potential causes:

 

-Missing or Corrupt Files:

The script exits early if /var/local/emhttp/var.ini is missing

if (!file_exists("/var/local/emhttp/var.ini")) exit;

 

If other required files like /var/local/emhttp/devs.ini or /var/local/emhttp/disks.ini are missing or corrupted, it may cause execution errors

 

-Execution of External Commands (exec()):

The script frequently calls exec() for notification commands

exec("$notify -l '/Main' -e ...");

 

if notify is missing or has incorrect permissions, these commands could fail.

 

-Errors in Required Files (Helpers.php and Preselect.php):

If these files contain syntax errors or undefined functions, they may prevent the script from running.

 

-Issues with parse_ini_file():

The script uses @parse_ini_file() to read configuration files

$var = (array)@parse_ini_file("/var/local/emhttp/var.ini");

 

If these files contain invalid formatting, they may cause execution failures.

 

-File Permission Issues

If the script cannot write to /var/local/emhttp/monitor.ini or /boot/config/plugins/dynamix/monitor.ini, it may cause failures

 

...I don't want to touch unriads emhttp. its a complicated mess and I would rewrite it on Debian if i got involved enouth...

however... Here are some Suggested Fixes:

 

-Debugging the Exit Condition

Modify the script to log failures before exiting:

if (!file_exists("/var/local/emhttp/var.ini")) {
    error_log("ERROR: var.ini file missing", 3, "/var/log/monitor_error.log");
    exit(1);
}

This will create a log file (/var/log/monitor_error.log) to check if the file exists.

 

-Verify Required Files

Run the following command in the Unraid terminal to confirm the files exist:

ls -l /var/local/emhttp/

If files are missing, check if they are created by another process or regenerate them.

 

-Check notify Command Execution

Modify exec() calls to capture errors:

 

$output = [];
$return_var = 0;
exec("$notify -l '/Main' -e 'Test Notification' 2>&1", $output, $return_var);
if ($return_var !== 0) {
    error_log("ERROR: Notify command failed - " . implode("\n", $output), 3, "/var/log/monitor_error.log");
}

If notify is missing or misconfigured, reinstall or fix permissions

chmod +x /usr/local/emhttp/webGui/scripts/notify

...

 

 

-Validate Configuration Files

run:

php -r 'var_dump(parse_ini_file("/var/local/emhttp/var.ini"));'

If it returns false, the file has syntax issue

 

-Adjust Error Handling for parse_ini_file()

Modify the script to prevent execution if parsing fails:

$var = @parse_ini_file("/var/local/emhttp/var.ini");
if (!$var) {
    error_log("ERROR: Failed to parse var.ini", 3, "/var/log/monitor_error.log");
    exit(1);
}

 

-Check Nginx Logs:

cat /var/log/nginx/error.log | grep monitor

new monitor file with recomend fixes explained above... (Untested...)

#!/usr/bin/php -q
<?PHP
/* Copyright 2005-2023, Lime Technology
 * Copyright 2012-2023, Bergware International.
 *
 * This program is free software; you can redistribute it and/or
 * modify it under the terms of the GNU General Public License version 2,
 * as published by the Free Software Foundation.
 */
?>
<?
$docroot ??= ($_SERVER['DOCUMENT_ROOT'] ?: '/usr/local/emhttp');
require_once "$docroot/webGui/include/Helpers.php";
require_once "$docroot/webGui/include/Preselect.php";

// Multi-language handling
if (!function_exists('_')) {
  function _($text) {return $text;}
}
// Exit when settings are not yet initialized
if (!file_exists("/var/local/emhttp/var.ini")) {
    error_log("ERROR: var.ini file missing", 3, "/var/log/monitor_error.log");
    exit(1);
}

$var = @parse_ini_file("/var/local/emhttp/var.ini");
if (!$var) {
    error_log("ERROR: Failed to parse var.ini", 3, "/var/log/monitor_error.log");
    exit(1);
}

$devs  = (array)@parse_ini_file("/var/local/emhttp/devs.ini",true);
$disks = (array)@parse_ini_file("/var/local/emhttp/disks.ini",true);

require_once "$docroot/webGui/include/CustomMerge.php";

extract(parse_plugin_cfg("dynamix",true));

$notify = "$docroot/webGui/scripts/notify";
$ram    = "/var/local/emhttp/monitor.ini";
$rom    = "/boot/config/plugins/dynamix/monitor.ini";
$saved  = @parse_ini_file($ram,true);
$high1  = _var($display,'critical',0);
$high2  = _var($display,'warning',0);
$server = strtoupper(_var($var,'NAME','tower'));
$pools  = pools_filter($disks);
$errors = [];
$top    = 120;

// Check if notify script exists and is executable
if (!file_exists($notify) || !is_executable($notify)) {
    error_log("ERROR: notify script missing or not executable", 3, "/var/log/monitor_error.log");
}

function execute_notify($command) {
    global $notify;
    $output = [];
    $return_var = 0;
    exec("$notify $command 2>&1", $output, $return_var);
    if ($return_var !== 0) {
        error_log("ERROR: Notify command failed - " . implode("\n", $output), 3, "/var/log/monitor_error.log");
    }
}

// Save new status
if ($saved) {
    $text = '';
    foreach ($saved as $item => $block) {
        if ($block) $text .= "[$item]\n";
        foreach ($block as $key => $value) $text .= no_tilde($key)."=\"$value\"\n";
    }
    if ($text) {
        if ($text != @file_get_contents($ram)) file_put_contents($ram, $text);
        if (!file_exists($rom) || exec("diff -q $ram $rom")) file_put_contents($rom, $text);
    } else {
        delete_file($ram,$rom);
    }
}
exit(0);
?>

But I would recommend using the docker grafana and  Prometheus in implementing a monitor and notify system... Unraid also already has notified setting area and pre captured reports...

http://[unriadIP]/Settings/Notifications
WebUI > Settings > Notification Settings


 

otherwise, I'm over thinking this, and  you made edits to emhttps config scripts and may need to recreate your unriad falsh drive...

the github has the original monitor php...

 

https://github.com/unraid/webgui/blob/master/emhttp/plugins/dynamix/scripts/monitor

14 hours ago, bmartino1 said:

otherwise, I'm over thinking this, and  you made edits to emhttps config scripts and may need to recreate your unriad falsh drive...

the github has the original monitor php...

 

https://github.com/unraid/webgui/blob/master/emhttp/plugins/dynamix/scripts/monitor

Thanks for the lots of proposals, I will try them out or directly recreate my whole unraid flash drive, its maybe easier, to reinstall everything as I understand? 

 

I did not do any changes to the montior php/file, so thats really odd. 

Okay, I did a full reinstall to Unraid and did even change my USB Stick, but still having problems, as soon as the appdata backup starts, my unraid seems to be crashing somehow, thats the log from the console:

 

 

So it seems, that a plugin (combination?) is causing it.

 

I have the exact same issue (but not using monitor plugin), I somehow also have the feeling it is related to appdata backup.
Just updated to 7.1.1 as my server with 7.0.1 got unbresponsive today again (GUI, SSH, Bitwarden, Nextcloud, ... not working/available; other local docker frontends still available).

Hopefully 7.1.1 fixes it.

Edited May 9, 20251 yr by Stiefmeister

@Stiefmeister Still on 7.0.1. But one trick did it somehow for me: Changing the USB Port of my Storage device. Since I plugged in my Unraid FLashdrive into another USB Port I have a stable system since 10 Days.

If you guys see this again, can you post the output of

ls -ail /usr/local/emhttp/plugins/dynamix/scripts

Hi, since updating to > 7.1 it did no occur again for me. So far uptime of 12 days

I just faced this issue on 7.1.4.

@squid

43 minutes ago, Joloxx9 said:

I just faced this issue on 7.1.4.

@squid

If you guys see this again, can you post the output of

ls -ail /usr/local/emhttp/plugins/dynamix/scripts

14 hours ago, bmartino1 said:

If you guys see this again, can you post the output of

ls -ail /usr/local/emhttp/plugins/dynamix/scripts

root@Arrakis:~# ls -ail /usr/local/emhttp/plugins/dynamix/scripts
total 174
 5500 drwxr-xr-x 1 root root    80 Nov  4 01:51 ./
   37 drwxr-xr-x 1 root root   300 Nov  4 01:51 ../
 5205 -rwxr-xr-x 1 root root   434 Nov 15  2023 agent*
 5206 -rwxr-xr-x 1 root root   229 Nov 15  2023 bootmode*
 5207 -rwxr-xr-x 1 root root   420 Nov 15  2023 btrfs_balance*
 5208 -rwxr-xr-x 1 root root  1397 Jun  6  2024 btrfs_check*
 5209 -rwxr-xr-x 1 root root   819 Nov 15  2023 btrfs_scrub*
 5210 -rwxr-xr-x 1 root root   775 Nov 15  2023 console*
 5211 -rwxr-xr-x 1 root root 37808 May  1  2025 diagnostics*
 5212 -rwxr-xr-x 1 root root   774 Nov 15  2023 disk_size*
 5213 -rwxr-xr-x 1 root root   489 Nov 15  2023 emcmd*
 5214 -rwxr-xr-x 1 root root   728 Feb 16  2025 error_interfaces*
 5215 -rwxr-xr-x 1 root root 13602 Apr  4  2025 feedback*
 5216 -rwxr-xr-x 1 root root  1693 Nov 15  2023 flash_backup*
 5217 -rwxr-xr-x 1 root root   577 Nov 15  2023 ftpusers*
 5218 -rwxr-xr-x 1 root root  2399 Nov 15  2023 install_key*
 5219 -rwxr-xr-x 1 root root 15620 Jun 29  2024 monitor*
 5220 -rwxr-xr-x 1 root root  6538 Feb 26  2025 netconfig*
 5221 -rwxr-xr-x 1 root root  2703 Sep 21  2024 newperms*
 5222 -rwxr-xr-x 1 root root   849 Jan  9  2025 nfsSettings*
 5223 -rwxr-xr-x 1 root root  9915 Feb 16  2025 notify*
 5224 -rwxr-xr-x 1 root root  1282 Apr 22  2025 open_ssl*
 5225 -rwxr-xr-x 1 root root  3390 Dec 17  2024 outgoingproxy*
 5226 -rwxr-xr-x 1 root root  1154 Nov 15  2023 parity_control*
53832 -rwxr-xr-x 1 root root  8099 Nov  4 01:51 parity_history*
53830 -rwxr-xr-x 1 root root  3150 Feb  5  2024 parity_history.orig*
 5228 -rwxr-xr-x 1 root root   141 Dec 29  2023 powermode*
 5229 -rwxr-xr-x 1 root root   676 Oct 11  2024 reiserfs_check*
 5230 -rwxr-xr-x 1 root root   336 Jun  2 17:22 reload_services*
 5231 -rwxr-xr-x 1 root root   649 Feb  5  2024 replace_key_job*
 5232 -rwxr-xr-x 1 root root   677 Mar 26  2025 restore_favorites*
 5233 -rwxr-xr-x 1 root root  3583 Feb 16  2024 rsyslog_config*
 5234 -rwxr-xr-x 1 root root  1437 Nov 15  2023 run_cmd*
 5235 -rwxr-xr-x 1 root root  2967 Feb  5  2024 select_case*
 5236 -rwxr-xr-x 1 root root  4182 Jul 16  2024 set_proxy*
 5237 -rwxr-xr-x 1 root root   826 Nov 15  2023 share_size*
 5238 -rwxr-xr-x 1 root root   269 Jul 27  2024 show_interfaces*
 5239 -rwxr-xr-x 1 root root  4272 Feb 27  2025 ssd_trim*
 5240 -rwxr-xr-x 1 root root  8080 Mar 23  2024 statuscheck*
 5241 -rwxr-xr-x 1 root root 10104 Feb 25  2025 system_information*
 5242 -rwxr-xr-x 1 root root  1771 Apr 22  2025 update_access*
 5243 -rwxr-xr-x 1 root root   541 Jun  2 17:22 update_services*
 5244 -rwxr-xr-x 1 root root  1602 Nov 15  2023 upnp_poller*
 5245 -rwxr-xr-x 1 root root   104 Nov 15  2023 upnp_poller_start*
 5246 -rwxr-xr-x 1 root root  1334 Nov 15  2023 upnp_port*
 5247 -rwxr-xr-x 1 root root  2304 Feb  5  2024 wg_config*
 5248 -rwxr-xr-x 1 root root  1649 Mar 31  2025 wireless*
 5249 -rwxr-xr-x 1 root root  2640 Jul  1  2024 xfs_check*
 5250 -rwxr-xr-x 1 root root   518 Nov 15  2023 zfs_scrub*

I also can subscribe, facing the same issue. Whats the point of this output? Here's mine as well:

# ls -ail /usr/local/emhttp/plugins/dynamix/script
s
total 176
100 drwxr-xr-x 1 root root 80 Nov 3 20:40 ./
99 drwxr-xr-x 1 root root 180 Nov 3 20:40 ../
6940 -rwxr-xr-x 1 root root 434 Nov 16 2023 agent*
6941 -rwxr-xr-x 1 root root 229 Nov 16 2023 bootmode*
6942 -rwxr-xr-x 1 root root 420 Nov 16 2023 btrfs_balance*
6943 -rwxr-xr-x 1 root root 330 Aug 15 21:24 btrfs_check*
6944 -rwxr-xr-x 1 root root 819 Nov 16 2023 btrfs_scrub*
6945 -rw-r--r-- 1 root root 1739 Aug 18 20:23 check.source
6946 -rwxr-xr-x 1 root root 775 Nov 16 2023 console*
6947 -rwxr-xr-x 1 root root 39251 Oct 15 06:42 diagnostics*
6948 -rwxr-xr-x 1 root root 774 Nov 16 2023 disk_size*
6949 -rwxr-xr-x 1 root root 489 Nov 16 2023 emcmd*
6950 -rwxr-xr-x 1 root root 728 Feb 16 2025 error_interfaces
*
6951 -rwxr-xr-x 1 root root 236 Aug 15 21:24 exfat_check*
6952 -rwxr-xr-x 1 root root 226 Aug 15 21:24 ext_check*
6953 -rwxr-xr-x 1 root root 13602 Apr 4 2025 feedback*
6954 -rwxr-xr-x 1 root root 1693 Nov 16 2023 flash_backup*
6955 -rwxr-xr-x 1 root root 577 Nov 16 2023 ftpusers*
6956 -rwxr-xr-x 1 root root 2114 Aug 14 07:44 install_key*
6957 -rwxr-xr-x 1 root root 15620 Jun 29 2024 monitor*
6958 -rwxr-xr-x 1 root root 6538 Feb 26 2025 netconfig*
6959 -rwxr-xr-x 1 root root 2514 Aug 14 07:44 newperms*
6960 -rwxr-xr-x 1 root root 849 Jan 9 2025 nfsSettings*
6961 -rwxr-xr-x 1 root root 9915 Feb 16 2025 notify*
6962 -rwxr-xr-x 1 root root 229 Aug 15 21:24 ntfs_check*
6963 -rwxr-xr-x 1 root root 1282 Apr 22 2025 open_ssl*
6964 -rwxr-xr-x 1 root root 3390 Dec 17 2024 outgoingproxy*
6965 -rwxr-xr-x 1 root root 1154 Nov 16 2023 parity_control*
4159 -rwxr-xr-x 1 root root 8099 Nov 3 20:40 parity_history*
6966 -rwxr-xr-x 1 root root 3150 Feb 5 2024 parity_history.o
rig*
6967 -rwxr-xr-x 1 root root 141 Dec 29 2023 powermode*
6968 -rwxr-xr-x 1 root root 255 Aug 15 21:24 reiserfs_check*
6969 -rwxr-xr-x 1 root root 336 May 10 10:32 reload_services*
6970 -rwxr-xr-x 1 root root 649 Feb 5 2024 replace_key_job*
6971 -rwxr-xr-x 1 root root 677 Mar 26 2025 restore_favorite
s*
6972 -rwxr-xr-x 1 root root 3583 Feb 16 2024 rsyslog_config*
6973 -rwxr-xr-x 1 root root 1437 Nov 16 2023 run_cmd*
6974 -rwxr-xr-x 1 root root 4582 Jun 23 19:24 select_case*
6975 -rwxr-xr-x 1 root root 4182 Jul 16 2024 set_proxy*
6976 -rwxr-xr-x 1 root root 826 Nov 16 2023 share_size*
6977 -rwxr-xr-x 1 root root 269 Jul 27 2024 show_interfaces*
6978 -rwxr-xr-x 1 root root 4035 Aug 14 07:44 ssd_trim*
6979 -rwxr-xr-x 1 root root 8080 Mar 23 2024 statuscheck*
6980 -rwxr-xr-x 1 root root 9897 Oct 15 06:42 system_informati
on*
6981 -rwxr-xr-x 1 root root 1771 Apr 22 2025 update_access*
6982 -rwxr-xr-x 1 root root 541 May 30 20:22 update_services*
6983 -rwxr-xr-x 1 root root 1602 Nov 16 2023 upnp_poller*
6984 -rwxr-xr-x 1 root root 104 Nov 16 2023 upnp_poller_star
t*
6985 -rwxr-xr-x 1 root root 1350 May 31 17:54 upnp_port*
6986 -rwxr-xr-x 1 root root 2304 Feb 5 2024 wg_config*
6987 -rwxr-xr-x 1 root root 1649 Mar 31 2025 wireless*
6988 -rwxr-xr-x 1 root root 252 Aug 15 21:24 xfs_check*
6989 -rwxr-xr-x 1 root root 518 Jul 30 19:52 zfs_scrub*

Edited November 4, 2025Nov 4 by UnraidTobias

@Squid

to hit this a runaway script may be running. we are trying to track the scirpt to kill the process and patch so it done't happen again.

not sure if its a 3rd party plugin or other unatentd bug or interaction.

I personaly haven't hit this error and can't reproduce it.

Otehrs claim it leaving it on the dashbaord on a browser over night that fills up and const refresh the script.

that comand as you see list the scripts active and curenlty running for squid and other devs to take a look and inspect.

I'm seeing alot of WG, Reversproxy and other runing whcih coould cause the connections over them to hist the memory cap and connt load of the emhttp page...

I'm not saying its the vpn... but @UnraidTobias yor line shows.
6986 -rwxr-xr-x 1 root root 2304 Feb 5 2024 wg_config*
6964 -rwxr-xr-x 1 root root 3390 Dec 17 2024 outgoingproxy*

is showing mutiple vpn scripts running...

where @Joloxx9

your lines don't...

and we can compare on a healthy sytem what scirpt doen't belong and whats still running that might cause this error...

root@The-Borg:~# ls -ail /usr/local/emhttp/plugins/dynamix/scripts

total 176

118 drwxr-xr-x 1 root root 80 Oct 29 18:48 ./

117 drwxr-xr-x 1 root root 140 Oct 29 18:48 ../

6940 -rwxr-xr-x 1 root root 434 Nov 15 2023 agent*

6941 -rwxr-xr-x 1 root root 229 Nov 15 2023 bootmode*

6942 -rwxr-xr-x 1 root root 420 Nov 15 2023 btrfs_balance*

6943 -rwxr-xr-x 1 root root 330 Aug 15 14:24 btrfs_check*

6944 -rwxr-xr-x 1 root root 819 Nov 15 2023 btrfs_scrub*

6945 -rw-r--r-- 1 root root 1739 Aug 18 13:23 check.source

6946 -rwxr-xr-x 1 root root 775 Nov 15 2023 console*

6947 -rwxr-xr-x 1 root root 39251 Oct 14 23:42 diagnostics*

6948 -rwxr-xr-x 1 root root 774 Nov 15 2023 disk_size*

6949 -rwxr-xr-x 1 root root 489 Nov 15 2023 emcmd*

6950 -rwxr-xr-x 1 root root 728 Feb 16 2025 error_interfaces*

6951 -rwxr-xr-x 1 root root 236 Aug 15 14:24 exfat_check*

6952 -rwxr-xr-x 1 root root 226 Aug 15 14:24 ext_check*

6953 -rwxr-xr-x 1 root root 13602 Apr 4 2025 feedback*

6954 -rwxr-xr-x 1 root root 1693 Nov 15 2023 flash_backup*

6955 -rwxr-xr-x 1 root root 577 Nov 15 2023 ftpusers*

6956 -rwxr-xr-x 1 root root 2114 Aug 14 00:44 install_key*

6957 -rwxr-xr-x 1 root root 15620 Jun 28 2024 monitor*

6958 -rwxr-xr-x 1 root root 6538 Feb 25 2025 netconfig*

6959 -rwxr-xr-x 1 root root 2514 Aug 14 00:44 newperms*

6960 -rwxr-xr-x 1 root root 849 Jan 8 2025 nfsSettings*

6961 -rwxr-xr-x 1 root root 9915 Feb 16 2025 notify*

6962 -rwxr-xr-x 1 root root 229 Aug 15 14:24 ntfs_check*

6963 -rwxr-xr-x 1 root root 1282 Apr 21 2025 open_ssl*

6964 -rwxr-xr-x 1 root root 3390 Dec 16 2024 outgoingproxy*

6965 -rwxr-xr-x 1 root root 1154 Nov 15 2023 parity_control*

17077 -rwxr-xr-x 1 root root 8099 Oct 29 18:48 parity_history*

6966 -rwxr-xr-x 1 root root 3150 Feb 5 2024 parity_history.orig*

6967 -rwxr-xr-x 1 root root 141 Dec 29 2023 powermode*

6968 -rwxr-xr-x 1 root root 255 Aug 15 14:24 reiserfs_check*

6969 -rwxr-xr-x 1 root root 336 May 10 03:32 reload_services*

6970 -rwxr-xr-x 1 root root 649 Feb 5 2024 replace_key_job*

6971 -rwxr-xr-x 1 root root 677 Mar 26 2025 restore_favorites*

6972 -rwxr-xr-x 1 root root 3583 Feb 16 2024 rsyslog_config*

6973 -rwxr-xr-x 1 root root 1437 Nov 15 2023 run_cmd*

6974 -rwxr-xr-x 1 root root 4582 Jun 23 12:24 select_case*

6975 -rwxr-xr-x 1 root root 4182 Jul 16 2024 set_proxy*

6976 -rwxr-xr-x 1 root root 826 Nov 15 2023 share_size*

6977 -rwxr-xr-x 1 root root 269 Jul 27 2024 show_interfaces*

6978 -rwxr-xr-x 1 root root 4035 Aug 14 00:44 ssd_trim*

6979 -rwxr-xr-x 1 root root 8080 Mar 22 2024 statuscheck*

6980 -rwxr-xr-x 1 root root 9897 Oct 14 23:42 system_information*

6981 -rwxr-xr-x 1 root root 1771 Apr 21 2025 update_access*

6982 -rwxr-xr-x 1 root root 541 May 30 13:22 update_services*

6983 -rwxr-xr-x 1 root root 1602 Nov 15 2023 upnp_poller*

6984 -rwxr-xr-x 1 root root 104 Nov 15 2023 upnp_poller_start*

6985 -rwxr-xr-x 1 root root 1350 May 31 10:54 upnp_port*

6986 -rwxr-xr-x 1 root root 2304 Feb 5 2024 wg_config*

6987 -rwxr-xr-x 1 root root 1649 Mar 31 2025 wireless*

6988 -rwxr-xr-x 1 root root 252 Aug 15 14:24 xfs_check*

6989 -rwxr-xr-x 1 root root 518 Jul 30 12:52 zfs_scrub*

root@The-Borg:~#

real hardware non affected system...

VM hardware no afected system..
root@BMM-Tower:~# ls -ail /usr/local/emhttp/plugins/dynamix/scripts

total 167

118 drwxr-xr-x 2 root root 967 Oct 14 23:42 ./

117 drwxr-xr-x 1 root root 160 Nov 4 11:01 ../

6940 -rwxr-xr-x 1 root root 434 Nov 15 2023 agent*

6941 -rwxr-xr-x 1 root root 229 Nov 15 2023 bootmode*

6942 -rwxr-xr-x 1 root root 420 Nov 15 2023 btrfs_balance*

6943 -rwxr-xr-x 1 root root 330 Aug 15 14:24 btrfs_check*

6944 -rwxr-xr-x 1 root root 819 Nov 15 2023 btrfs_scrub*

6945 -rw-r--r-- 1 root root 1739 Aug 18 13:23 check.source

6946 -rwxr-xr-x 1 root root 775 Nov 15 2023 console*

6947 -rwxr-xr-x 1 root root 39251 Oct 14 23:42 diagnostics*

6948 -rwxr-xr-x 1 root root 774 Nov 15 2023 disk_size*

6949 -rwxr-xr-x 1 root root 489 Nov 15 2023 emcmd*

6950 -rwxr-xr-x 1 root root 728 Feb 16 2025 error_interfaces*

6951 -rwxr-xr-x 1 root root 236 Aug 15 14:24 exfat_check*

6952 -rwxr-xr-x 1 root root 226 Aug 15 14:24 ext_check*

6953 -rwxr-xr-x 1 root root 13602 Apr 4 2025 feedback*

6954 -rwxr-xr-x 1 root root 1693 Nov 15 2023 flash_backup*

6955 -rwxr-xr-x 1 root root 577 Nov 15 2023 ftpusers*

6956 -rwxr-xr-x 1 root root 2114 Aug 14 00:44 install_key*

6957 -rwxr-xr-x 1 root root 15620 Jun 28 2024 monitor*

6958 -rwxr-xr-x 1 root root 6538 Feb 25 2025 netconfig*

6959 -rwxr-xr-x 1 root root 2514 Aug 14 00:44 newperms*

6960 -rwxr-xr-x 1 root root 849 Jan 8 2025 nfsSettings*

6961 -rwxr-xr-x 1 root root 9915 Feb 16 2025 notify*

6962 -rwxr-xr-x 1 root root 229 Aug 15 14:24 ntfs_check*

6963 -rwxr-xr-x 1 root root 1282 Apr 21 2025 open_ssl*

6964 -rwxr-xr-x 1 root root 3390 Dec 16 2024 outgoingproxy*

6965 -rwxr-xr-x 1 root root 1154 Nov 15 2023 parity_control*

6966 -rwxr-xr-x 1 root root 3150 Feb 5 2024 parity_history*

6967 -rwxr-xr-x 1 root root 141 Dec 29 2023 powermode*

6968 -rwxr-xr-x 1 root root 255 Aug 15 14:24 reiserfs_check*

6969 -rwxr-xr-x 1 root root 336 May 10 03:32 reload_services*

6970 -rwxr-xr-x 1 root root 649 Feb 5 2024 replace_key_job*

6971 -rwxr-xr-x 1 root root 677 Mar 26 2025 restore_favorites*

6972 -rwxr-xr-x 1 root root 3583 Feb 16 2024 rsyslog_config*

6973 -rwxr-xr-x 1 root root 1437 Nov 15 2023 run_cmd*

6974 -rwxr-xr-x 1 root root 4582 Jun 23 12:24 select_case*

6975 -rwxr-xr-x 1 root root 4182 Jul 16 2024 set_proxy*

6976 -rwxr-xr-x 1 root root 826 Nov 15 2023 share_size*

6977 -rwxr-xr-x 1 root root 269 Jul 27 2024 show_interfaces*

6978 -rwxr-xr-x 1 root root 4035 Aug 14 00:44 ssd_trim*

6979 -rwxr-xr-x 1 root root 8080 Mar 22 2024 statuscheck*

6980 -rwxr-xr-x 1 root root 9897 Oct 14 23:42 system_information*

6981 -rwxr-xr-x 1 root root 1771 Apr 21 2025 update_access*

6982 -rwxr-xr-x 1 root root 541 May 30 13:22 update_services*

6983 -rwxr-xr-x 1 root root 1602 Nov 15 2023 upnp_poller*

6984 -rwxr-xr-x 1 root root 104 Nov 15 2023 upnp_poller_start*

6985 -rwxr-xr-x 1 root root 1350 May 31 10:54 upnp_port*

6986 -rwxr-xr-x 1 root root 2304 Feb 5 2024 wg_config*

6987 -rwxr-xr-x 1 root root 1649 Mar 31 2025 wireless*

6988 -rwxr-xr-x 1 root root 252 Aug 15 14:24 xfs_check*

6989 -rwxr-xr-x 1 root root 518 Jul 30 12:52 zfs_scrub*

root@BMM-Tower:~#



Its more to verify that its not a plugin causing this...

FYI monitor is the script that is prepackaged with emhttp and is what auto reloads the stats on the dashboard...
The question is what ran or didn't run correctly to cause it to break exit code 1 and fail...

Please post a diag and make a bug report.

Edited November 4, 2025Nov 4 by bmartino1
data

Thx. I Just checked those two scrips on my Side:

usr/local/emhttp/plugins/dynamix/scripts/outgoingproxy

/usr/local/emhttp/plugins/dynamix/scripts/wg_config

I've none of those services configured or in use (checked in settings, there are NOT Setup/configured/active) at all. And...I am usig tailscale anyway instead. - So i think those have nothing to-do with it.

Edited November 4, 2025Nov 4 by UnraidTobias

I can confirm that system was running in my case for 30 days+ and I left 5 windows of unraid open on my machine and left it for like 16 hours, at 23:30 all was good but system crashed right before midnight.

I could still access containers through IP:port

Nginx reverse proxy was not working

CF tunnel was down(even that all containters were running)

I could not SSH to the server - connection refused
I could not log in directly on the machine as you can see on above screenshot, putting anything as login was doing nothing.

After restart from the button(thank god for KVM!) all is back an running, minus 30hours for parity check -.-

Edited November 4, 2025Nov 4 by Joloxx9

12 hours ago, bmartino1 said:

@Squid

to hit this a runaway script may be running. we are trying to track the scirpt to kill the process and patch so it done't happen again.

not sure if its a 3rd party plugin or other unatentd bug or interaction.

I personaly haven't hit this error and can't reproduce it.

Otehrs claim it leaving it on the dashbaord on a browser over night that fills up and const refresh the script.

that comand as you see list the scripts active and curenlty running for squid and other devs to take a look and inspect.

I'm seeing alot of WG, Reversproxy and other runing whcih coould cause the connections over them to hist the memory cap and connt load of the emhttp page...

I'm not saying its the vpn... but @UnraidTobias yor line shows.
6986 -rwxr-xr-x 1 root root 2304 Feb 5 2024 wg_config*
6964 -rwxr-xr-x 1 root root 3390 Dec 17 2024 outgoingproxy*

is showing mutiple vpn scripts running...

where @Joloxx9

your lines don't...

and we can compare on a healthy sytem what scirpt doen't belong and whats still running that might cause this error...

@Squid The problem is back

I expierence again the same problem since I upgraded to 7.2.0. My Server/Machine was stable since Mid may. Back then I thought it was a USB port causing the problems and switching was helping.

When I upgraded to the latest stable Unraid Version, which I did it via my mobile phone. There were no other PCs running with the webinterface, so this means the option with

Otehrs claim it leaving it on the dashbaord on a browser over night that fills up and const refresh the script.

Is probably out of scope.

Output of:

ls -ail /usr/local/emhttp/plugins/dynamix/scripts

98 drwxr-xr-x 2 root root 967 Oct 15 06:42 ./
97 drwxr-xr-x 14 root root 2732 Oct 22 22:03 ../
6940 -rwxr-xr-x 1 root root 434 Nov 16 2023 agent*
6941 -rwxr-xr-x 1 root root 229 Nov 16 2023 bootmode*
6942 -rwxr-xr-x 1 root root 420 Nov 16 2023 btrfs_balance*
6943 -rwxr-xr-x 1 root root 330 Aug 15 21:24 btrfs_check*
6944 -rwxr-xr-x 1 root root 819 Nov 16 2023 btrfs_scrub*
6945 -rw-r--r-- 1 root root 1739 Aug 18 20:23 check.source
6946 -rwxr-xr-x 1 root root 775 Nov 16 2023 console*
6947 -rwxr-xr-x 1 root root 39251 Oct 15 06:42 diagnostics*
6948 -rwxr-xr-x 1 root root 774 Nov 16 2023 disk_size*
6949 -rwxr-xr-x 1 root root 489 Nov 16 2023 emcmd*
6950 -rwxr-xr-x 1 root root 728 Feb 16 2025 error_interfaces*
6951 -rwxr-xr-x 1 root root 236 Aug 15 21:24 exfat_check*
6952 -rwxr-xr-x 1 root root 226 Aug 15 21:24 ext_check*
6953 -rwxr-xr-x 1 root root 13602 Apr 4 2025 feedback*
6954 -rwxr-xr-x 1 root root 1693 Nov 16 2023 flash_backup*
6955 -rwxr-xr-x 1 root root 577 Nov 16 2023 ftpusers*
6956 -rwxr-xr-x 1 root root 2114 Aug 14 07:44 install_key*
6957 -rwxr-xr-x 1 root root 15620 Jun 29 2024 monitor*
6958 -rwxr-xr-x 1 root root 6538 Feb 26 2025 netconfig*
6959 -rwxr-xr-x 1 root root 2514 Aug 14 07:44 newperms*
6960 -rwxr-xr-x 1 root root 849 Jan 9 2025 nfsSettings*
6961 -rwxr-xr-x 1 root root 9915 Feb 16 2025 notify*
6962 -rwxr-xr-x 1 root root 229 Aug 15 21:24 ntfs_check*
6963 -rwxr-xr-x 1 root root 1282 Apr 22 2025 open_ssl*
6964 -rwxr-xr-x 1 root root 3390 Dec 17 2024 outgoingproxy*
6965 -rwxr-xr-x 1 root root 1154 Nov 16 2023 parity_control*
6966 -rwxr-xr-x 1 root root 3150 Feb 5 2024 parity_history*
6967 -rwxr-xr-x 1 root root 141 Dec 29 2023 powermode*
6968 -rwxr-xr-x 1 root root 255 Aug 15 21:24 reiserfs_check*
6969 -rwxr-xr-x 1 root root 336 May 10 10:32 reload_services*
6970 -rwxr-xr-x 1 root root 649 Feb 5 2024 replace_key_job*
6971 -rwxr-xr-x 1 root root 677 Mar 26 2025 restore_favorites*
6972 -rwxr-xr-x 1 root root 3583 Feb 16 2024 rsyslog_config*
6973 -rwxr-xr-x 1 root root 1437 Nov 16 2023 run_cmd*
6974 -rwxr-xr-x 1 root root 4582 Jun 23 19:24 select_case*
6975 -rwxr-xr-x 1 root root 4182 Jul 16 2024 set_proxy*
6976 -rwxr-xr-x 1 root root 826 Nov 16 2023 share_size*
6977 -rwxr-xr-x 1 root root 269 Jul 27 2024 show_interfaces*
6978 -rwxr-xr-x 1 root root 4035 Aug 14 07:44 ssd_trim*
6979 -rwxr-xr-x 1 root root 8080 Mar 23 2024 statuscheck*
6980 -rwxr-xr-x 1 root root 9897 Oct 15 06:42 system_information*
6981 -rwxr-xr-x 1 root root 1771 Apr 22 2025 update_access*
6982 -rwxr-xr-x 1 root root 541 May 30 20:22 update_services*
6983 -rwxr-xr-x 1 root root 1602 Nov 16 2023 upnp_poller*
6984 -rwxr-xr-x 1 root root 104 Nov 16 2023 upnp_poller_start*
6985 -rwxr-xr-x 1 root root 1350 May 31 17:54 upnp_port*
6986 -rwxr-xr-x 1 root root 2304 Feb 5 2024 wg_config*
6987 -rwxr-xr-x 1 root root 1649 Mar 31 2025 wireless*
6988 -rwxr-xr-x 1 root root 252 Aug 15 21:24 xfs_check*
6989 -rwxr-xr-x 1 root root 518 Jul 30 19:52 zfs_scrub*

Edited November 5, 2025Nov 5 by Fabske