[NFS-Ganesha-Support] inconsistent nfs-ganesha error at startup (v2.8, CentOS 7)

I'm using nfs-ganesha 2.8 on CentOS 7. Inconsistently, I will get errors like this in ganesha.log at nfs-ganesha startup: 08/04/2020 22:25:26 : epoch 5e8e8796 : ganesha : ganesha.nfsd-1647[main] init_export_root :EXPORT :CRIT :Lookup failed on path, ExportId=20040 Path=/pool/export/a FSAL_ERROR=(Invalid object type,10063) This is using PROXY FSAL for a valid, functioning nfs export from another host X. I have other PROXY exports with different export IDs and different paths for this same host X that succeed during the same startup for which the error above is generated. I will see different exports IDs and paths in these errors for different startups, so it's not consistently always failing on one particular export ID. From one startup to another: - I may see this error about this same export, - I may see this error about some other export, - I may see no errors. Thoughts? Thanks, Todd