Hi,

 

I received the error message "/var/log is getting full (currently 51 % used)" overnight from the Fix Common Problems plugin. I had a quick look through the syslog and didn't notice any glaring issues but I'm not really sure if that's the correct log to be checking or not? My server has an uptime of 87 days but I've had longer runs before that without getting this error. My array is 99% full though and not sure if that would cause the issue?

 

I've attached my diagnostics file, if anyone could have a look at it and give me some advice on what to do I would greatly appreciate it.

 

Thank-you.

 

mediaserver-diagnostics-20200606-1123.zip

These are what is spamming your log:

 

Mar 30 15:59:14 Mediaserver rpc.mountd[8249]: authenticated mount request from 192.168.0.128:519 for /mnt/user/Media (/mnt/user/Media)
Mar 30 15:59:14 Mediaserver rpcbind[18335]: connect from 192.168.0.128 to null()
Mar 30 15:59:14 Mediaserver rpcbind[18336]: connect from 192.168.0.128 to getport/addr(nfs)
Mar 30 16:02:13 Mediaserver rpcbind[23302]: connect from 192.168.0.128 to null()
Mar 30 16:02:13 Mediaserver rpcbind[23303]: connect from 192.168.0.128 to getport/addr(mountd)
Mar 30 16:02:13 Mediaserver rpc.mountd[8249]: authenticated mount request from 192.168.0.128:525 for /mnt/user/Pictures (/mnt/user/Pictures)
Mar 30 16:02:13 Mediaserver rpcbind[23313]: connect from 192.168.0.128 to null()
Mar 30 16:02:13 Mediaserver rpcbind[23314]: connect from 192.168.0.128 to getport/addr(nfs)
Mar 30 16:05:18 Mediaserver rpcbind[28349]: connect from 192.168.0.128 to null()
Mar 30 16:05:18 Mediaserver rpcbind[28350]: connect from 192.168.0.128 to getport/addr(mountd)
Mar 30 16:05:18 Mediaserver rpcbind[28351]: connect from 192.168.0.128 to null()
Mar 30 16:05:18 Mediaserver rpcbind[28352]: connect from 192.168.0.128 to getport/addr(mountd)
Mar 30 16:05:18 Mediaserver rpc.mountd[8249]: authenticated mount request from 192.168.0.128:536 for /mnt/user/Pictures (/mnt/user/Pictures)
Mar 30 16:05:18 Mediaserver rpcbind[28353]: connect from 192.168.0.128 to null()
Mar 30 16:05:18 Mediaserver rpcbind[28354]: connect from 192.168.0.128 to getport/addr(nfs)
Mar 30 16:08:15 Mediaserver rpcbind[629]: connect from 192.168.0.128 to null()
Mar 30 16:08:15 Mediaserver rpcbind[630]: connect from 192.168.0.128 to getport/addr(mountd)
Mar 30 16:08:15 Mediaserver rpc.mountd[8249]: authenticated mount request from 192.168.0.128:541 for /mnt/user/Media (/mnt/user/Media)
Mar 30 16:08:15 Mediaserver rpcbind[631]: connect from 192.168.0.128 to null()
Mar 30 16:08:15 Mediaserver rpcbind[632]: connect from 192.168.0.128 to getport/addr(nfs)
Mar 30 16:08:19 Mediaserver rpcbind[638]: connect from 192.168.0.64 to null()
Mar 30 16:08:19 Mediaserver rpcbind[639]: connect from 192.168.0.64 to getport/addr(mountd)
Mar 30 16:08:19 Mediaserver rpc.mountd[8249]: authenticated mount request from 192.168.0.64:786 for /mnt/user/Media (/mnt/user/Media)
Mar 30 16:08:19 Mediaserver rpcbind[640]: connect from 192.168.0.64 to null()
Mar 30 16:08:19 Mediaserver rpcbind[641]: connect from 192.168.0.64 to getport/addr(nfs)
Mar 30 16:18:55 Mediaserver rpcbind[18202]: connect from 192.168.0.128 to null()
Mar 30 16:18:55 Mediaserver rpcbind[18203]: connect from 192.168.0.128 to getport/addr(mountd)
Mar 30 16:18:55 Mediaserver rpc.mountd[8249]: authenticated mount request from 192.168.0.128:550 for /mnt/user/Media (/mnt/user/Media)

 

Thank you for the quick reply.

 

A few follow-up questions if I may?

 

Are those messages that are spamming the log an indication of a problem? I'm guessing no since the message looks pretty harmless but I could be wrong. Is there anything I can/should do to stop the messages? I'm guessing that the logs will eventually fill up? Will a reboot clear it or is there something else I should do?

 

Thanks again for any help.

15 hours ago, derekvm said:

Are those messages that are spamming the log an indication of a problem?

They are the result of something connecting with the NFS protocol.

 

15 hours ago, derekvm said:

Is there anything I can/should do to stop the messages?

Never used NFS but it's not usually that chatty.

 

15 hours ago, derekvm said:

I'm guessing that the logs will eventually fill up? Will a reboot clear it or is there something else I should do?

A reboot will clear it but you might want to try and decrease all that chatting.

Thanks for your help, I appreciate it.

 

I found another thread here with about half a dozen people having the same issue stretching back to January 2019 so I've posted there asking if they found a resolution. I'm really not sure how to go about resolving it but I'll keep googling!