downgrading from 16.0.26 to 16.0.23, then issuing a chown and refresh signatures, and then upgrading to 16.0.26 seems to have corrected the issue temporarily…
now the same error is back.
Downgraded to 16.0.23, chown, refresh signatures and the module is ok. Seems to be something wrong with 16.0.26
We have someone looking at this and have pulled that version from our mirrors over the weekend until we can figure out what has changed that its no longer happy.