Heiko Richter wrote on Fri, Jul 13, 2012 at 12:55:26 +0200:
> And again there are several 'permission denied' errors. This time from
> the sync run at 10:55 UTC:
>
> rsync: readlink_stat("/geronimo/2.1.8/geronimo-2.1.8-source-release.tar.gz"
> (in apache-dist)) failed: Permission denied (13)
> rsync: readlink_stat("/geronimo/2.1.8/geronimo-tomcat6-minimal-2.1.8-bin.zip"
> (in apache-dist)) failed: Permission denied (13)
minotaur,29:~% ls -dl
/dist//geronimo/2.1.8/geronimo-tomcat6-javaee5-2.1.8-bin.tar.gz
ls: /dist//geronimo/2.1.8/geronimo-tomcat6-javaee5-2.1.8-bin.tar.gz: Permission
denied
I think these errors are unrelated and caused by the Geronimo PMC
accidentally removing the +x bit from the 2.1.8/ directory. (Reminder:
directories in dist/ should have 0775 permissions.)
Geronimo PMC: please fix.
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-tomcat6-javaee5-2.1.8-bin.tar.gz" (in
> apache-dist)) failed: Permission denied (13)
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-jetty6-javaee5-2.1.8-bin.tar.gz" (in
> apache-dist)) failed: Permission denied (13)
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-2.1.8-source-release.tar.gz.asc" (in
> apache-dist)) failed: Permission denied (13)
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-tomcat6-minimal-2.1.8-bin.tar.gz" (in
> apache-dist)) failed: Permission denied (13)
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-jetty6-minimal-2.1.8-bin.tar.gz" (in
> apache-dist)) failed: Permission denied (13)
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-tomcat6-javaee5-2.1.8-bin.zip.asc"
> (in apache-dist)) failed: Permission denied (13)
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-jetty6-minimal-2.1.8-bin.zip.asc" (in
> apache-dist)) failed: Permission denied (13)
> rsync: readlink_stat("/geronimo/2.1.8/geronimo-framework-2.1.8-bin.zip.asc"
> (in apache-dist)) failed: Permission denied (13)
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-framework-2.1.8-bin.tar.gz.asc" (in
> apache-dist)) failed: Permission denied (13)
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-tomcat6-javaee5-2.1.8-bin.tar.gz.asc"
> (in apache-dist)) failed: Permission denied (13)
> rsync: readlink_stat("/geronimo/2.1.8/geronimo-jetty6-javaee5-2.1.8-bin.zip"
> (in apache-dist)) failed: Permission denied (13)
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-tomcat6-minimal-2.1.8-bin.tar.gz.asc"
> (in apache-dist)) failed: Permission denied (13)
> rsync: readlink_stat("/geronimo/2.1.8/geronimo-jetty6-minimal-2.1.8-bin.zip"
> (in apache-dist)) failed: Permission denied (13)
> rsync: readlink_stat("/geronimo/2.1.8/geronimo-framework-2.1.8-bin.zip" (in
> apache-dist)) failed: Permission denied (13)
> rsync: readlink_stat("/geronimo/2.1.8/geronimo-2.1.8-source-release.zip.asc"
> (in apache-dist)) failed: Permission denied (13)
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-jetty6-javaee5-2.1.8-bin.zip.asc" (in
> apache-dist)) failed: Permission denied (13)
> rsync: readlink_stat("/geronimo/2.1.8/geronimo-2.1.8-source-release.zip" (in
> apache-dist)) failed: Permission denied (13)
> rsync: readlink_stat("/geronimo/2.1.8/RELEASE_NOTES.txt" (in apache-dist))
> failed: Permission denied (13)
> rsync: readlink_stat("/geronimo/2.1.8/geronimo-framework-2.1.8-bin.tar.gz"
> (in apache-dist)) failed: Permission denied (13)
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-jetty6-javaee5-2.1.8-bin.tar.gz.asc"
> (in apache-dist)) failed: Permission denied (13)
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-jetty6-minimal-2.1.8-bin.tar.gz.asc"
> (in apache-dist)) failed: Permission denied (13)
> rsync:
> readlink_stat("/geronimo/2.1.8/geronimo-tomcat6-minimal-2.1.8-bin.zip.asc"
> (in apache-dist)) failed: Permission denied (13)
> rsync: readlink_stat("/geronimo/2.1.8/geronimo-tomcat6-javaee5-2.1.8-bin.zip"
> (in apache-dist)) failed: Permission denied (13)
> rsync error: some files/attrs were not transferred (see previous errors)
> (code 23) at main.c(1526) [generator=3.0.7]
>
>
>
> Am 12.07.2012 21:46, schrieb Daniel Shahaf:
> > Heiko Richter wrote on Tue, Jul 10, 2012 at 22:15:26 +0200:
> >>> --- anyone has handy the date those error started?
> >> The first error mail my server produced, was at 10:40 UTC.
> >>
> >> I synchronize hourly so obviously the error startet between 09:40 UTC
> >> und 10:40 UTC....
> > I was looking for answer in the range of dates, not hours, since we have
> > had similar reports several times recently (but it seems to have started
> > sometime in the last 1-6 months)
> >
>
>
>
