My log file keeps filling up with the following line... (When I run the following command tail -f /var/log/syslog)

 

request-key: : No matching action

 

As I keep the command open in the terminal, the two entries are added every minute. I have tried turning off all docker containers and VMs, but every minute without fail an entry is entered.

 

I was updating somethings in the settings section of unRaid while monitoring the log. These errors ceased for 5 minutes, until the nginx config was reloaded. Not sure what was significant with the reloading, Any thougts?

 

Here is the log entry that started the errors up again. 

Jan 22 19:18:32   sshd[4795]: Server listening on 0.0.0.0 port 22.
Jan 22 19:18:32   sshd[4795]: Server listening on :: port 22.
Jan 22 19:18:33   emhttpd: shcmd (5614): /etc/rc.d/rc.nginx reload
Jan 22 19:18:33  root: Checking configuration for correct syntax and
Jan 22 19:18:33  root: then trying to open files referenced in configuration...
Jan 22 19:18:33  root: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
Jan 22 19:18:33  root: nginx: configuration file /etc/nginx/nginx.conf test is successful
Jan 22 19:18:33  root: Reloading Nginx configuration...
Jan 22 19:18:52   request-key: : No matching action
Jan 22 19:18:52   request-key: : No matching action

 

 

 

unraiddiagnostics.zip

Edited January 23, 20233 yr by NotAZombie
Updated post with new details

@NotAZombie Did you end up figuring this out? This started happening to mine.

Anyone seeing this, it is a NFS issue. Verify permissions. If permissions are not set, then it is a NFS bug. Seems to not hurt anything, but fills logs ( which can eventually cause issues ).

@slimshizn

I did get it resolved, but I am not quite sure of my solution.

 

I started testing and verifying all my connections with the my NAS server (separate for storage) were correct. I did reconnected to it under the Unassigned Devices and I believe that was the issue, but again it was a random bunch of things I did that seemed to stop the logs from filling up so I didn't post a solution.

According to your answer it seems that could have been the NFS permissions, which coincided of my reconnecting with the unassigned devices. Thanks for posting the solution.