Yeah, this is a time skew between servers. We ran into this issue somewhat recently (a month or two ago, I think?), and I put a fix in place that ought to have stopped the issue from coming up again (automatic job to refresh the time). Evidently, that didn't quite work. DST could have very well caused the issue, I'll look into it when I next get a chance.
Cheers, Torben On Thu, Mar 31, 2022 at 9:21 PM Jody Garnett <jody.garn...@gmail.com> wrote: > Torben, got a question for you. > > Does this error message represent a clock difference between servers? I > wonder if recent European timezone change has caused Jenkins to be slightly > ahead of itself.... > -- > Jody Garnett > > > On Mar 30, 2022 at 8:50:05 PM, Jody Garnett <jody.garn...@gmail.com> > wrote: > >> Blah it is worse than that, all the doc jobs are broken: >> >> geoserver-2.20.x-livedocs: >> >> Completed 87.3 MiB/96.4 MiB (0 Bytes/s) with 420 file(s) remaining >> upload failed: target/2.20.x/en/user/data/vector/properties.html to s3:// >> docs.geoserver.org/2.20.x/en/user/data/vector/properties.html An error >> occurred (RequestTimeTooSkewed) when calling the PutObject operation: The >> difference between the request time and the current time is too large. >> >> >> Geoserver-main-live-docs: >> >> upload failed: target/main/en/api/1.0.0/coverages.yaml to s3:// >> docs.geoserver.org/main/en/api/1.0.0/coverages.yaml An error occurred >> (RequestTimeTooSkewed) when calling the PutObject operation: The difference >> between the request time and the current time is too large. >> >> >> Looks like it started happening on the 28th.... >> >> Once again we do have a new location for docs available at OSGeo, and we >> can change Jenkins publish location: >> >> - #2640: task: docs.geoserver.org website request (new) >> <https://trac.osgeo.org/osgeo/ticket/2640> >> - #2461: task: Static web server for docs.geoserver.org (new) >> <https://trac.osgeo.org/osgeo/ticket/2461> >> >> >> It is just I am not volunteering to do so as I have wasted enough time on >> the domain name transfer. >> -- >> Jody Garnett >> >> >> On Mar 30, 2022 at 8:32:45 PM, Jody Garnett <jody.garn...@gmail.com> >> wrote: >> >>> Yes, we know - we cannot delete pages from S3 (we do not have >>> credentials for that). The best we can do is upload placeholder pages; but >>> we chose not to do so (as we were anticipating having control of >>> geoserver.org domain. >>> >>> Since that is not happening, I fully support adding placeholder pages to >>> the docs marking content that has graduated, or retired. >>> -- >>> Jody Garnett >>> >>> >>> On Mar 30, 2022 at 3:20:11 AM, Ian Turton <ijtur...@gmail.com> wrote: >>> >>>> If you goto >>>> https://docs.geoserver.org/latest/en/user/community/scripting/ you >>>> find a set of 2.19.x pages (rather than 2.21.x that is latest) that are not >>>> actually linked to anything (but they are still found in google) - is there >>>> any way to delete them? and I guess update the build process to make sure >>>> it builds into an empty directory. >>>> >>>> Ian >>>> >>>> -- >>>> Ian Turton >>>> _______________________________________________ >>>> Geoserver-devel mailing list >>>> Geoserver-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>>> >>>
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
