8 hours ago, WizADSL said:

Also, it SEEMS that the ignore mechanism uses the exact wording of the notification which for something like Docker updates would be a real game of Whack-a-Mole as the message would vary depending on the name of the container.

The way it works now it can react on any message that appears somewhere. You can then ignore THIS message.

But what you propose is that the plugin already knows ALL possible messages (which is impossible because of Updates or new Components installed). 

That does not work unless you want the poor programmer to work 24/7/365 and issue 20 Updates of the plugin per day.

 

I'm hoping someone can help with this — I want to keep all my usual notifications, but I manage Docker updates outside of Unraid. The issue is, every time a new container (especially with a new name) gets added, I get spammed with emails saying an update is available.

My Fix Common Problems ignore list is getting massive because I have to manually ignore each one. It's becoming unmanageable.

Is there a way to:

Ignore all Docker update warnings globally?

Or maybe ignore containers based on a wildcard pattern in the name?

I’d love a clean solution that lets me still receive useful warnings, just not for Docker updates I handle manually. Any ideas?

On 4/16/2025 at 2:42 AM, MAM59 said:

Since when is the "Done" Button the same as "Rescan" ?

(And how can I now gracefully leave FcP )

It's not.  DONE is the same as everywhere else in the WebGUI.  It goes to the previous page you were at (ie, in the URL, you'll see something like /Settings/FixProblems.  Hitting Done takes you to Settings

5 hours ago, Squid said:

Hitting Done takes you to Settings

Thats what I am used to.

But that day it looped to "scanning..." over and over.

Anyway, I have just retried now (in between there was a reboot or something), now "done" is back to "done".

So, whatever it was, its gone now...

I will report, if it shows up again someday.

I am getting the following warning....

/var/log is getting full (currently 54 % used) Either your server has an extremely long uptime, or your syslog could be potentially being spammed with error messages. A reboot of your server will at least temporarily solve this problem, but ideally you should seek assistance in the forums and post your   More Information

 

 

Thanks in advance for help fixing this issue..

 

 

tower-unraid-diagnostics-20250501-1942.zip

25 minutes ago, farberm said:

potentially being spammed with error messages

In many of the Syslogs files I see very many Entry's about a sshd-session that's starting/closed many times and periodic.

 

A example:

"

Apr  8 11:29:08 Tower-Unraid sshd-session[2834620]: Close session: user root from 192.168.2.60 port 55128 id 0
Apr  8 11:29:08 Tower-Unraid sshd-session[2834620]: Starting session: command for root from 192.168.2.60 port 55128 id 0
Apr  8 11:29:08 Tower-Unraid sshd-session[2834620]: Close session: user root from 192.168.2.60 port 55128 id 0
Apr  8 11:29:08 Tower-Unraid sshd-session[2834620]: Starting session: command for root from 192.168.2.60 port 55128 id 0
Apr  8 11:29:08 Tower-Unraid sshd-session[2834620]: Close session: user root from 192.168.2.60 port 55128 id 0

"

 

Maybe is this the Issue.

 

You should see this on your Syslog too.

Edited May 2, 20251 yr by Revan335

20 hours ago, dopeytree said:

Came to inquire about this same warning received this morning. Still on 7.0.1 Thanks.

For File Activity: 

 

Some one is very wrong with the Plugins or the Repositorys of @dlandon. @Squid

 

I don't see/can find the GitHub Repositorys of this. Have GitHub are strong Bug and deleted Repositorys?

 

Description: Investigate at Settings / User Utilities / Fix Common Problems
Importance: warning

* The plugin enhanced.log.plg is not known to Community Applications and is possibly incompatible with your server
* The plugin file.activity.plg is not known to Community Applications and is possibly incompatible with your server
* The plugin libvirt.hotplug.usb.plg is not known to Community Applications and is possibly incompatible with your server

4 hours ago, Revan335 said:

Some one is very wrong with the Plugins or the Repositorys of @dlandon. @Squid

 

I don't see/can find the GitHub Repositorys of this. Have GitHub are strong Bug and deleted Repositorys?

 

Description: Investigate at Settings / User Utilities / Fix Common Problems
Importance: warning

* The plugin enhanced.log.plg is not known to Community Applications and is possibly incompatible with your server
* The plugin file.activity.plg is not known to Community Applications and is possibly incompatible with your server
* The plugin libvirt.hotplug.usb.plg is not known to Community Applications and is possibly incompatible with your server

yes now this morning I have this also.

 

The plugin enhanced.log.plg is not known to Community Applications and is possibly incompatible with your server

3 hours ago, wirenut said:

yes now this morning I have this also.

 

The plugin enhanced.log.plg is not known to Community Applications and is possibly incompatible with your server

I do not know why the author chose to delete the repositories, but that is unfortunately out of my hands, and at this time I have far too much on my plate to be able to fork and republish the plugins.

 

The notification from Fix Common Problems is correct, as the plugins are currently unknown to CA, but I do not see any reason for these in particular to be uninstalled as there are no compatibility or security issues with them as far as I know.  But keeping them or uninstalling them is however entirely up to you guys.

 

Maybe in the future the author will reactivate these plugins, but that decision is entirely out of my hands.

21 minutes ago, Squid said:

I do not know why the author chose to delete the repositories, but that is unfortunately out of my hands, and at this time I have far too much on my plate to be able to fork and republish the plugins.

 

The notification from Fix Common Problems is correct, as the plugins are currently unknown to CA, but I do not see any reason for these in particular to be uninstalled as there are no compatibility or security issues with them as far as I know.  But keeping them or uninstalling them is however entirely up to you guys.

 

Maybe in the future the author will reactivate these plugins, but that decision is entirely out of my hands.

Thanks Squid.

 

Good to know fix common problems and CA are working correctly.

 

I'll keep an eye on the specific plugin threads that are effecting me to see if some information arises there.

@Squid for the people using docker compose or managing dockers without unraid directly could you add a setting to ignore updates errors?

 

For some reason if you use docker compose Unraid is not able to read the images versions and we get this warnings all the time

 

@Squid 

I got this warning:
 

Quote

“Share databases set to use pool ssdraid, but files / folders exist on the ssdraid__ pool”.

 

[in the message is ssdraid__ (two underscores)]

 

It applies to four shares. And everything happened after that:
I had a ZFS pool named Ssdraid, on it those four previously mentioned shares. I needed to swap the disk. I created a new ZFS pool named Ssdraid_ (one underscore) on the new disk and copied all the data from the Ssdraid pool. Then, from the Unraid UI, I renamed the Ssdraid pool to Ssdraid__ (two underscores), and renamed the Ssdraid_ pool (one underscore) to Ssdraid.

 

And now, all in all, I don't know where the error is, because in the share settings everything looks fine to me:

 

 

It may be important, but these four shares are ZFS datasets.

 

Edited May 11, 20251 yr by jaclas

ZFS is an Depuplicated Filesystem and his Datasets are an Filesystem in the Filesystem. So my wisdom.

 

Maybe ZFS or another are have underground processes to this files and deleted or give this free in the future. When you don't see this in the file manager, Krusader, Shell, MC, ...

@Squid knows what he specifically checks to show this message, so I'm hoping for some guidance. I haven't found anything myself by looking for links in the file system and processes.

 

ps. Because, all in all, I'm guessing that maybe it's a false alarm, and it's actually worth investigating to possibly correct it.

 

-- after few hours

 

Additional key information in my opinion:
I disabled the ssdraid__ pool and the server is running completely normally (all applications data is on ssdraid pool) and the Fix Common Problems plugin shows no problems now.

 

Edited May 11, 20251 yr by jaclas

I have two SSDs, a small one serving as cache in front of the bigger one. I get this warning. What should I do to resolve it?

See screenshots for setup details:

Edited May 11, 20251 yr by neuronflow

20 hours ago, neuronflow said:

I have two SSDs, a small one serving as cache in front of the bigger one. I get this warning. What should I do to resolve it?

See screenshots for setup details:

 

Perhaps the problem is the same directory structure (or datasets in the case of ZFS) i.e. the same names on different drives? This is the common part of both our cases. @Squid, here's a note for you 🙂

Edited May 12, 20251 yr by jaclas

The update assistant still shows 7.0.1 as the current stable release. Please update it to use the latest version of Unraid (7.1.2)

On 5/11/2025 at 2:41 AM, jaclas said:

I got this warning:

I'll look into it.

 

Thanks

On 5/12/2025 at 11:01 PM, Squid said:

I'll look into it.

 

Thanks

Any solution to this?

https://forums.unraid.net/topic/47266-plugin-ca-fix-common-problems/page/97/#findComment-1552392

I'm on unRAID 7.1.2
Fix Common Problems: 2025.05.29

I don't have an Array
I have two ZFS Pools:
One nvme for the Cache and a raidz1 with spinning discs.

When I run the Fix Common Problems it says:

Scheduled Parity Checks are not enabled.
It is highly recommended to schedule parity checks for your system (most users choose monthly).

This is so that you know if Unraid has the ability to rebuild a failed drive if it needs to.

Set the schedule here:

In the <scheduler> I can't see the option to set a parity check.

Is that a false positives in the Fix Common Problems plugin - or is there something I need to setup?

2 hours ago, cphMichael said:

Is that a false positives in the Fix Common Problems plugin - or is there something I need to setup?

Ignore it. I'll fix the conditions for triggering it.

Thanks for reporting :)

On 5/12/2025 at 5:39 PM, jaclas said:

Perhaps the problem is the same directory structure (or datasets in the case of ZFS) i.e. the same names on different drives? This is the common part of both our cases. @Squid, here's a note for you 🙂

Can you elaborate, please? My unraid runs on btrfs.