Alright. If we see it again I will ask infra and check status.a.o. Regards, KAM
On June 20, 2017 7:45:35 AM EDT, Dave Jones <[email protected]> wrote: >On 06/20/2017 06:36 AM, Dave Jones wrote: >> On 06/19/2017 08:41 PM, Kevin A. McGrail wrote: >>> I thought this was an interesting one... >>> >>> >>> >>> -------- Forwarded Message -------- >>> Subject: Cron <root@sa-vm1> svn update >>> /var/www/automc.spamassassin.org/updates > /dev/null >>> Date: Tue, 20 Jun 2017 01:30:02 +0000 (UTC) >>> From: Cron Daemon <[email protected]> >>> Reply-To: [email protected] >>> To: [email protected] >>> >>> >>> >>> svn: E170013: Unable to connect to a repository at URL >>> 'http://svn.apache.org/repos/asf/spamassassin/site/updates' >>> svn: E175013: Access to '/repos/asf/spamassassin/site/updates' >forbidden >>> >>> >> I have a cron'd svn update on sa-vm1 that pulls regularly to keep >this >> folder updated from SVN. This was a single "blip" in the svn update. > >> If we see more of these repeating in a short interval, then we would >> need to start investigating. I don't think we need to worry about a >> single issue like this one. >> >> Dave >> >Well, after catching up on newer mail, this wasn't a single event but >it >seemed to happen a few more times. It stopped so we should be still be > >OK. This may have been a sign that there were general SVN issues or it > >could have been isolated to the spamassassin_role SVN ID that the >automc >user is setup to use. > >Dave
