Marcus Furlong
Marcus Furlong
Are they actually unprocessed though? Or just showing as unprocessed in the web interface? If you disable caching completely, does that fix the issue? NB you'll probably need to restart...
> > Are they actually unprocessed though? Or just showing as unprocessed in the web interface? > > How can I check this? `patchman -p` > > > If you...
The web UI is caching the DB results, so when you see unprocessed reports in the UI you are getting an (out-of-date) cached result. The reports are actually processed in...
`patchman -p` would be a better indicator of unprocessed reports.
Check the apache logs, but I think `require ip` is the ip range of the clients. The apache logs should let you know if this is the case.
Question answered. Feel free to reopen if this is still an issue.
We don't (yet!) support authenticated apt repos. A workaround may be to set the clients to report local updates?
v4 is not released yet. It is currently only available in the backports section of the repo for testing purposes with an associated PR here: https://github.com/furlongm/patchman/pull/675/files Feel free to test...
I released 3.0.19 into the repos. There is only one commit that affects users: https://github.com/furlongm/patchman/commit/fdeea13da8d147f72f3f005ce84f199ae62ac676) I removed the 4.0.0 release candidate for now.
Can you check if this is still required with the latest release?