13 minutes ago, Steviewunda said:

I'm getting this warning even after making the recommended change in Docker Settings

 

Sorry - just did a reboot and no longer getting this warning

I got this macvlan error too and not sure if it's a simple matter of changing that option in the Docker settings area.

 

Did you have to recreate the vlan after making this setting change so it uses ipvlan instead of macvlan?

Edited April 20, 20233 yr by nraygun

I tried changing to ipvlan and it broke DuckDNS. Putting it back restored operation. Not sure why. It's not on a custom network, just Host.

Guess I'll leave it alone unless someone else has some guidance.

Seems that the plugin should flag macvlan as a warning versus an error.

Edited April 21, 20233 yr by nraygun

Anyone else getting "not available" for this plugin when looking at update status on the plugin page?

Edited April 21, 20233 yr by rkotara

27 minutes ago, rkotara said:

Anyone else getting "not available" for this plugin when looking at update status on the plugin page?

+1

Yeah.  inadvertent change to the .plg that messed it up.

 

If it was summer and I had a pool, you have permission to beat me with a wet noodle

Is there a way to disable checking for new docker versions?  My dockers all auto-update on a set schedule, but this means I'll often have 20+ notifications (for docker updates) all of which have already automatically been updated since.  It's not useful and spams the notification list badly. 

13 hours ago, Wintersdark said:

Is there a way to disable checking for new docker versions?  My dockers all auto-update on a set schedule, but this means I'll often have 20+ notifications (for docker updates) all of which have already automatically been updated since.  It's not useful and spams the notification list badly. 

Me too.

 

Wasn't happening until recently. Not sure where those emails are coming from but FCP seems the only logical source.

Yeah I know, this here is mentioned very often already but still unresolved and nagging:

May 14 04:40:02 F root: Fix Common Problems Version 2023.04.26
May 14 04:40:04 F root: Fix Common Problems: Warning: unRaids built in FTP server is currently disabled, but users are defined ** Ignored

 

The message is simply wrong, There are no ftp users in unraid, there is a docker with crushftp installed (and with its own database for users). Also, nobody knows how to "resolve" this common problem.

Yeah, you can ignore it, but the message should never pop up.

 

This is not "Fix Common Problems" this is more "Create Common Problems".

 

My file log is filling up to 110%. I have added my diagnostic file for review.  

syslog.1.txt

4 minutes ago, Rick Pawlowski said:

My file log is filling up to 110%. I have added my diagnostic file for review.  

Tame your client  192.168.88.110.

 

He is banging something on your server many thousands of times per seconds. The log does not say which program is been banged, but I would look for something that offers net services like nextcloud or so.

 

There is something running wild on that client.

On 5/13/2023 at 10:55 PM, MAM59 said:

Yeah I know, this here is mentioned very often already but still unresolved and nagging:

May 14 04:40:02 F root: Fix Common Problems Version 2023.04.26
May 14 04:40:04 F root: Fix Common Problems: Warning: unRaids built in FTP server is currently disabled, but users are defined ** Ignored

 

The message is simply wrong, There are no ftp users in unraid, there is a docker with crushftp installed (and with its own database for users). Also, nobody knows how to "resolve" this common problem.

Yeah, you can ignore it, but the message should never pop up.

 

You can see the FCP code here:

  https://github.com/Squidly271/fix.common.problems/blob/ce84e87f79caaf750bc84a16f7ecdb93561f4cec/source/fix.common.problems/usr/local/emhttp/plugins/fix.common.problems/include/tests.php#L714

 

If this file exists on your flash drive it will trigger that message:

  /boot/config/vsftpd.user_list

 

It looks like when you go to Settings -> FTP Server and remove the users, it empties the file but does not delete it.

 

The FCP test could be updated to ignore a file with no data.

 

In the meantime you can get rid of the message by deleting the empty config/vsftpd.user_list file from your flash drive.

7 hours ago, ljm42 said:

The FCP test could be updated to ignore a file with no data.

 

In the meantime you can get rid of the message by deleting the empty config/vsftpd.user_list file from your flash drive.

tnx! this worked. Maybe you should  add this explanation/solution to the warning message? So affected people instantly would know why it happens and how to fix it?

I never had any vsftp users, as far as I can remember, but in the beginnings I have turned on the builtin ftp just to see that it does not fulfill my needs. So I guess, the file was autocreated, but how could I know?

 

My /var/log is getting full. It is not egregious, but the constant notifications are getting old. I am unable to figure out what is causing this. Any help is appreciated.cassandra-diagnostics-20230530-1001cassandra-diagnostics-20230530-1001cassandra-diagnostics-20230530-1001cassandra-diagnostics-20230530-1001

cassandra-diagnostics-20230530-1001.zip

20 hours ago, RMichaelRae said:

/var/log is getting full

Doesn't seem to be a problem with FCP plugin

  

On 5/8/2016 at 4:01 PM, Squid said:

Any support for problems this plugin finds, should be posted in the General v6 section of these forums

 

I am having a problem with FCP hanging on scanning.  I initially was running this because a script that I back of PFSense with is not assigning permissions they way it should, not sure what to do about that.  But, FPC should not hang.

tower-diagnostics-20230606-1052.zip

When running a manual scan, the popup shows the progress (the current scan).  What does it say?

This is all I get... would a manual scan be something different than clicking rescan in the GUI?

On 3/4/2023 at 8:11 AM, Squid said:

"addons" issue fixed on today's release

I had a feeling an update was just needed to correct the error. But I am still receiving the error. Can you or someone else help me ID the folder the errant folder.

 

root@******:~# ls -l /mnt/
total 32
drwxrwxrwt 2 nobody users  40 May 25 23:21 addons/
drwxr-xr-x 3 root   root   60 May 25 23:21 cache/
drwxrwxrwx 1 nobody users  28 Jun 10 04:40 cache_downloads/
drwxrwxrwx 1 nobody users  48 Jun 10 04:40 cache_main/
drwxrwxrwx 7 nobody users 101 Jun 10 04:40 disk1/
drwxrwxrwx 5 nobody users  66 Jun 10 04:40 disk10/
drwxrwxrwx 4 nobody users  48 Jun 10 04:40 disk11/
drwxrwxrwx 5 nobody users  66 Jun 10 04:40 disk12/
drwxrwxrwx 5 nobody users  66 Jun 10 04:40 disk13/
drwxrwxrwx 5 nobody users  66 Jun 10 04:40 disk14/
drwxrwxrwx 5 nobody users  50 Jun 10 04:40 disk15/
drwxrwxrwx 5 nobody users  66 Jun 10 04:40 disk16/
drwxrwxrwx 5 nobody users  66 Jun 10 04:40 disk17/
drwxrwxrwx 5 nobody users  66 Jun 10 04:40 disk18/
drwxrwxrwx 5 nobody users  66 Jun 10 04:40 disk19/
drwxrwxrwx 6 nobody users  85 Jun 10 04:40 disk2/
drwxrwxrwx 6 nobody users  84 Jun 10 04:40 disk20/
drwxrwxrwx 6 nobody users  87 Jun 10 04:40 disk21/
drwxrwxrwx 5 nobody users  66 Jun 10 04:40 disk22/
drwxrwxrwx 4 nobody users  48 Jun 10 04:40 disk23/
drwxrwxrwx 5 nobody users  69 Jun 10 04:40 disk24/
drwxrwxrwx 7 nobody users 101 Jun 10 04:40 disk3/
drwxrwxrwx 6 nobody users  85 Jun 10 04:40 disk4/
drwxrwxrwx 6 nobody users  82 Jun 10 04:40 disk5/
drwxrwxrwx 5 nobody users  66 Jun 10 04:40 disk6/
drwxrwxrwx 5 nobody users  66 Jun 10 04:40 disk7/
drwxrwxrwx 5 nobody users  66 Jun 10 04:40 disk8/
drwxrwxrwx 6 nobody users  87 Jun 10 04:40 disk9/
drwxrwxrwt 2 nobody users  40 May 25 23:21 disks/
drwxrwxrwt 2 nobody users  40 May 25 23:21 remotes/
drwxrwxrwt 2 nobody users  40 May 25 23:21 rootshare/
drwxrwxrwx 1 nobody users 101 Jun 10 04:40 user/
drwxrwxrwx 1 nobody users 101 Jun 10 04:40 user0/
 

Edited June 10, 20233 yr by jginzkey

On 6/6/2023 at 4:09 PM, mattw said:

This is all I get... would a manual scan be something different than clicking rescan in the GUI?

In Settings > NetworkSettings change IPv4 DNS server assignment from Automatic to Static

Set IPv4 DNS server to 8.8.8.8 and 8.8.4.4

Now try and see if it works.

 

*EDIT* You will have to disable Docker and VM's in the settings before you can make these adjustments.

Edited June 14, 20233 yr by Grimbone
Clarity

Hi,

every day i get this "root: Fix Common Problems: Warning: Write Cache is disabled on disk8"

Disk8 is actual disk 8 in the array?

I tested every disk with that command that the plugin links to, and it says that cache is ON.

But every day im getting a report that cache is off

Hi,

since some month I got the warning:

 

I've ignored this because everything works fine, but before updating to 6.12 I would like to solve this issue...

All shares works like a charm, the system is running smoothly without any other problems.

 

But I can not find any problem in my shares configuration.

 

It would be great if someone has an idea!

nasgw-diagnostics-20230616-0726.zip

Edited June 16, 20233 yr by KHP_BOH

2 hours ago, KHP_BOH said:

I've ignored this because everything works fine, but before updating to 6.12 I would like to solve this issue...

All shares works like a charm, the system is running smoothly without any other problems.

 

But I can not find any problem in my shares configuration.

Have you checked that you do not have a top level folder called 'disks' on either a cache pool or on any array drive?  The FCP messages imply it might be on the cache.

Great, thanks a lot for this!

Some time ago I've made a copy of the USB-Disk to the cache...

 

Deleted -> Error has gone.

Current version not compatible with Unraid latest version 6.12.0? When click on it just hanging on scanning screen without moving.