Log 100% full due to libvirtd errors

[MtX]

Hello everyone, 
After the the recent update to 6.10.2 I've been having reoccurring issues with the log folder filling up. Im unaware if its due to the update or similar timing. Ive tracked it down the the libvirtd.log file filling it up. Im unsure whats causing all the errors so any insight would be appreciated.

mtx-unraid-diagnostics-20220605-2030.zip

[JorgeB]

Please reboot to clear the log and post new diags after array start.

[MtX]

10 hours ago, JorgeB said:

Please reboot to clear the log and post new diags after array start.

As requested, I have rebooted the server and have attached the new diag after the array has started. Thanks for the support!

mtx-unraid-diagnostics-20220606-1145.zip

[JorgeB]

Jun  6 11:44:38 MtX-Unraid emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/Vault2

Do you know what Vault2 is? It doesn't exist in any array/pool device.

[MtX]

19 minutes ago, JorgeB said:

Jun  6 11:44:38 MtX-Unraid emhttpd: error: share_luks_status, 6158: Operation not supported (95): getxattr: /mnt/user/Vault2

Do you know what Vault2 is? It doesn't exist in any array/pool device.

its a share made with unraids gui. I mounted some folders within the share. I was actually just looking at that error and found I shouldn't be mounting under /mnt/user/. Does this include within the share itself? ex (mount /mnt/user/Vault2/Somefolder/)?

Edited June 6, 2022 by MtX

[JorgeB]

19 minutes ago, MtX said:

I shouldn't be mounting under /mnt/user/. Does this include within the share itself?

Yes.

 

 

[MtX]

9 minutes ago, JorgeB said:

Yes.

 

 

 

Okay thanks! I have corrected this and no longer receiving that error and will further monitor it. Will that inadvertently cause the libvirtd.log to fill up as well? 

[MtX]

3 hours ago, JorgeB said:

Yes.

 

 

It appears libvirtd.log is still growing, its filling up with 
 

2022-06-06 17:51:50.377+0000: 20202: error : virPCIVPDResourceGetKeywordPrefix:70 : internal error: The keyword is not comprised only of uppercase ASCII letters or digits
2022-06-06 17:51:50.379+0000: 20202: error : virPCIVPDResourceGetKeywordPrefix:70 : internal error: The keyword is not comprised only of uppercase ASCII letters or digits
2022-06-06 17:51:50.379+0000: 20202: error : virPCIVPDParseVPDLargeResourceFields:529 : internal error: A field data length violates the resource length boundary.
2022-06-06 17:51:51.214+0000: 20202: error : virPCIVPDResourceGetKeywordPrefix:70 : internal error: The keyword is not comprised only of uppercase ASCII letters or digits
2022-06-06 17:51:51.216+0000: 20202: error : virPCIVPDResourceGetKeywordPrefix:70 : internal error: The keyword is not comprised only of uppercase ASCII letters or digits
2022-06-06 17:51:51.216+0000: 20202: error : virPCIVPDParseVPDLargeResourceFields:529 : internal error: A field data length violates the resource length boundary.
2022-06-06 17:51:51.218+0000: 20202: error : virPCIVPDResourceGetKeywordPrefix:70 : internal error: The keyword is not comprised only of uppercase ASCII letters or digits
2022-06-06 17:51:51.220+0000: 20202: error : virPCIVPDResourceGetKeywordPrefix:70 : internal error: The keyword is not comprised only of uppercase ASCII letters or digits
2022-06-06 17:51:51.220+0000: 20202: error : virPCIVPDParseVPDLargeResourceFields:529 : internal error: A field data length violates the resource length boundary.
2022-06-06 17:51:51.223+0000: 20202: error : virPCIVPDResourceGetKeywordPrefix:70 : internal error: The keyword is not comprised only of uppercase ASCII letters or digits

 

 

Note: No vms were running at the time either

Edited June 6, 2022 by MtX

[JorgeB]

Yes, I suspected the libvirt issues were unrelated, but have no idea what those are about, hopefully someone else will.

[MtX]

 

On 6/7/2022 at 12:59 AM, JorgeB said:

Yes, I suspected the libvirt issues were unrelated, but have no idea what those are about, hopefully someone else will.

Yeah I'm stumped as well, as far a libvirt/vms go, I haven't really adjusted anything in quite some time. Only recent changes would of been replacing my boot usb (drive went read only) and updating Unraid. I do appreciate the help you provided, thanks for that.