Re: sa-vm1 migration to Ubuntu 18.04 / Puppet 6

2020-07-14 Thread Kevin A. McGrail 
Thanks., this appears to be the active.list error I was expecting.  I've
done an svn update and an svn revert on active.list.

If you can keep an eye out, we can see if that helps kick things in the
butt. I had a feeling modifying active.list was going to break things.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Tue, Jul 14, 2020 at 5:56 PM Giovanni Bechis  wrote:

> The script ~/svn/nitemc/corpora_runs is executed on Saturday (automc
> ~/svn/nitemc/corpora_runs >> ~/rsync/corpus/weekly-versions.txt) but I
> think that last Saturday it failed in some way, last line of
> weekly-versions.txt should contain the revision updated last Saturday
> ("2020-07-11  1879784") but "svn info" gives revision 1879467.
> "svn status --show-updates" tells that active.list is modified, I bet that
> running "svn update" by hand will fail and some errors should be fixed by
> hand.
> I think that, as you wrote, you should login, sudo to automc, svn up and
> then fix svn errors to be able to update the tree to latest revision.
>
>  Regards
>   Giovanni
>
> On 7/14/20 3:25 PM, Kevin A. McGrail wrote:
> > GB: I hadn't looked at masscheck as been sidetracked.  Henrik pointed
> out we fixed the lint warning issue on sa-update back with 3.4.3 so the
> people opening bugs are running old versions.  This isn't the lint issue,
> this is _check_whiitelist which is an internal function.  I fixed that on
> the 10th in revision 1879735 <
> https://svn.apache.org/viewvc?view=rev=1879735>
> >
> > From Memory, I think that SA will use the same version of the code for a
> week for masschecks but that could be an old system.
> >
> > Not sure if kicking the svn checkout.  Should I login, sudo to automc
> and go to /usr/local/spamassassin/svn/trunk and do svn up?  It's definitely
> running an older version from the 3rd, I checked on the server myself.
> >
> >
> > Hege: Thanks.  References to KAM's crashplan are out of date.  PCCC
> donates Crashplan services to the project / ASF formally since Spring
> 2018.  It's the project's crashplan and the credentials encrypted are
> stored in https://svn.apache.org/repos/asf/spamassassin/sysadmins/accounts
> so that two people had the credentials.
> >
> > Suggest you archive that 2017 Wiki Page and copy it to a new
> InfraNotes2020. Then you can rip and shred without any concerns.
> >
> > Regards,
> > KAM
> >
> > --
> > Kevin A. McGrail
> > Member, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >
> >
> > On Tue, Jul 14, 2020 at 8:23 AM Henrik K  h...@hege.li>> wrote:
> >
> > On Tue, Jul 14, 2020 at 02:20:29PM +0200, Giovanni Bechis wrote:
> > >
> > > automc seems still broken atm (commit to active.list fails), I am
> pretty sure you are aware of it and it will be fixed on new vm.
> > > I do not want to touch sa-vm1 now, new vm could go out-of-sync.
> > > https://markmail.org/message/ijg75xj3mguzvaxa
> >
> > Nothing can go out-of-sync.  At the time of switchover, all
> processes/crons
> > are stopped and final rsync is made to new vm.
> >
>
>

Re: sa-vm1 migration to Ubuntu 18.04 / Puppet 6

2020-07-14 Thread Giovanni Bechis 
The script ~/svn/nitemc/corpora_runs is executed on Saturday (automc 
~/svn/nitemc/corpora_runs >> ~/rsync/corpus/weekly-versions.txt) but I think 
that last Saturday it failed in some way, last line of weekly-versions.txt 
should contain the revision updated last Saturday ("2020-07-11  1879784") 
but "svn info" gives revision 1879467.
"svn status --show-updates" tells that active.list is modified, I bet that 
running "svn update" by hand will fail and some errors should be fixed by hand.
I think that, as you wrote, you should login, sudo to automc, svn up and then 
fix svn errors to be able to update the tree to latest revision.

 Regards
  Giovanni

On 7/14/20 3:25 PM, Kevin A. McGrail wrote:
> GB: I hadn't looked at masscheck as been sidetracked.  Henrik pointed out we 
> fixed the lint warning issue on sa-update back with 3.4.3 so the people 
> opening bugs are running old versions.  This isn't the lint issue, this is 
> _check_whiitelist which is an internal function.  I fixed that on the 10th in 
> revision 1879735 
> 
> From Memory, I think that SA will use the same version of the code for a week 
> for masschecks but that could be an old system.  
> 
> Not sure if kicking the svn checkout.  Should I login, sudo to automc and go 
> to /usr/local/spamassassin/svn/trunk and do svn up?  It's definitely running 
> an older version from the 3rd, I checked on the server myself.
> 
> 
> Hege: Thanks.  References to KAM's crashplan are out of date.  PCCC donates 
> Crashplan services to the project / ASF formally since Spring 2018.  It's the 
> project's crashplan and the credentials encrypted are stored in 
> https://svn.apache.org/repos/asf/spamassassin/sysadmins/accounts so that two 
> people had the credentials.
> 
> Suggest you archive that 2017 Wiki Page and copy it to a new InfraNotes2020. 
> Then you can rip and shred without any concerns.
> 
> Regards,
> KAM
> 
> --
> Kevin A. McGrail
> Member, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
> 
> 
> On Tue, Jul 14, 2020 at 8:23 AM Henrik K mailto:h...@hege.li>> 
> wrote:
> 
> On Tue, Jul 14, 2020 at 02:20:29PM +0200, Giovanni Bechis wrote:
> >
> > automc seems still broken atm (commit to active.list fails), I am 
> pretty sure you are aware of it and it will be fixed on new vm.
> > I do not want to touch sa-vm1 now, new vm could go out-of-sync.
> > https://markmail.org/message/ijg75xj3mguzvaxa
> 
> Nothing can go out-of-sync.  At the time of switchover, all 
> processes/crons
> are stopped and final rsync is made to new vm.
>

Re: sa-vm1 migration to Ubuntu 18.04 / Puppet 6

2020-07-14 Thread Kevin A. McGrail 
GB: I hadn't looked at masscheck as been sidetracked.  Henrik pointed out
we fixed the lint warning issue on sa-update back with 3.4.3 so the people
opening bugs are running old versions.  This isn't the lint issue, this is
_check_whiitelist which is an internal function.  I fixed that on the 10th
in revision 1879735 

>From Memory, I think that SA will use the same version of the code for a
week for masschecks but that could be an old system.

Not sure if kicking the svn checkout.  Should I login, sudo to automc and
go to /usr/local/spamassassin/svn/trunk and do svn up?  It's definitely
running an older version from the 3rd, I checked on the server myself.


Hege: Thanks.  References to KAM's crashplan are out of date.  PCCC donates
Crashplan services to the project / ASF formally since Spring 2018.  It's
the project's crashplan and the credentials encrypted are stored in
https://svn.apache.org/repos/asf/spamassassin/sysadmins/accounts so that
two people had the credentials.

Suggest you archive that 2017 Wiki Page and copy it to a new
InfraNotes2020. Then you can rip and shred without any concerns.

Regards,
KAM

--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Tue, Jul 14, 2020 at 8:23 AM Henrik K  wrote:

> On Tue, Jul 14, 2020 at 02:20:29PM +0200, Giovanni Bechis wrote:
> >
> > automc seems still broken atm (commit to active.list fails), I am pretty
> sure you are aware of it and it will be fixed on new vm.
> > I do not want to touch sa-vm1 now, new vm could go out-of-sync.
> > https://markmail.org/message/ijg75xj3mguzvaxa
>
> Nothing can go out-of-sync.  At the time of switchover, all processes/crons
> are stopped and final rsync is made to new vm.
>
>

Re: sa-vm1 migration to Ubuntu 18.04 / Puppet 6

2020-07-14 Thread Henrik K 
On Tue, Jul 14, 2020 at 02:20:29PM +0200, Giovanni Bechis wrote:
>
> automc seems still broken atm (commit to active.list fails), I am pretty sure 
> you are aware of it and it will be fixed on new vm.
> I do not want to touch sa-vm1 now, new vm could go out-of-sync. 
> https://markmail.org/message/ijg75xj3mguzvaxa

Nothing can go out-of-sync.  At the time of switchover, all processes/crons
are stopped and final rsync is made to new vm.

Re: sa-vm1 migration to Ubuntu 18.04 / Puppet 6

2020-07-14 Thread Giovanni Bechis 
Il 14 luglio 2020 13:20:11 CEST, Henrik K  ha scritto:
>
>Yes the new box is 100% identical in all aspects (pdns, rsync,
>masscheck,
>ruleqa, certbot, perl/python modules, paths etc).  Only some minor
>tweaks
>for Apache web server etc which make no difference documentation wise.
>
>Of course cron jobs are not yet running, they would mess around too
>much.
>
>I did not reach out to DNS people, I assume grant.kel...@sonic.com is
>still
>correct as per documentation, you probably know better..
>
>Cheers,
>Henrik
>
>
>On Tue, Jul 14, 2020 at 07:10:45AM -0400, Kevin A. McGrail wrote:
>> Nicely done.  Plus sysadmins list. Four key thought categories below;
>> 
>> Did you go through the documentation and the new box does everything
>the
>> old box did?  Like power DNS and the DNS GUI?  Rsync and the
>masscheck?
>> Ruleqa? The cron jobs? Sending root email to the same places?
>> 
>> Did you update the documentation?  We worked hard on it and don't
>want that
>> lost.
>> 
>> Have you reached to the DNS providers yet?  We can likely ask for two
>ips
>> to.allow xfer so no coordination is needed.
>> 
>> Do you already have the cron jobs running?
>> 
>> Beyond that we can switch any time you are around.  It will break
>masschecl
>> and everything and you might have to wait weeks to turn down the old
>box.
>> 
>> I would especially reach out to Dave Jones and see if he gives it a
>> greenlight.
>> 
>> Thanks for working on this.  KAM
>> 
>> On Tue, Jul 14, 2020, 06:57 Henrik K  wrote:
>> 
>> >
>> > Preparations are pretty much finished.
>> >
>> > Just need to agree on a date for the switchover.  What remains to
>be done
>> > then is changing/allowing the new master IP on DNS slaves, changing
>sa-vm1
>> > CNAMEs and final rsync.
>> >
>> > Could be for example next sunday or sometime next week.  Around
>17:00 UTC
>> > seems a quiet time on the box and everyone US/EU should be awake
>then..
>> >
>> >
>> > On Sat, Jun 20, 2020 at 05:18:32PM -0400, Kevin A. McGrail wrote:
>> > > Thanks Henrik for stepping up on it!
>> > > --
>> > > Kevin A. McGrail
>> > > Member, Apache Software Foundation
>> > > Chair Emeritus Apache SpamAssassin Project
>> > > [1]https://www.linkedin.com/in/kmcgrail - 703.798.0171
>> > >
>> > >
>> > > On Fri, Jun 19, 2020 at 3:50 PM Henrik K <[3]h...@hege.li> wrote:
>> > >
>> > >
>> > > Fyi, answered in the ticket..
>> > >
>> > > On Fri, Jun 19, 2020 at 10:08:26AM -0500, Drew Foulks wrote:
>> > > > Greetings SpamAssassin PMC!
>> > > >
>> > > > It's come to my attention that the VM that y'all are using
>needs an
>> > > upgrade!
>> > > > I'd like to take care of that for you and can start working
>on
>> > this as
>> > > soon as
>> > > > y'all say go. In the meantime, I've created a ticket (and
>linked
>> > your
>> > > trouble
>> > > > ticket) so that we can discuss and track this upgrade.
>> > > >
>> > > > [1][4]https://issues.apache.org/jira/browse/INFRA-20449
>> > > >
>> > > > cheers,
>> > > > --
>> > > > Drew Foulks, ASF Infra
>> > > >
>> > > >
>> > > >
>> > > > References:
>> > > >
>> > > > [1] [5]https://issues.apache.org/jira/browse/INFRA-20449
>> > >
>> > >
>> > > References:
>> > >
>> > > [1] https://www.linkedin.com/in/kmcgrail
>> > > [3] mailto:h...@hege.li
>> > > [4] https://issues.apache.org/jira/browse/INFRA-20449
>> > > [5] https://issues.apache.org/jira/browse/INFRA-20449
>> >

automc seems still broken atm (commit to active.list fails), I am pretty sure 
you are aware of it and it will be fixed on new vm.
I do not want to touch sa-vm1 now, new vm could go out-of-sync. 
https://markmail.org/message/ijg75xj3mguzvaxa

  Giovanni

Re: sa-vm1 migration to Ubuntu 18.04 / Puppet 6

2020-07-14 Thread Henrik K 


Then why does infranotes2017 say "KAM's Crashplan" everywhere?

There is backup dump of sa-vm1 already under
/usr/local/spamassassin/backups.


On Tue, Jul 14, 2020 at 08:13:40AM -0400, Kevin A. McGrail wrote:
> No it's an asf project crashplan account and infra does not do backups.  We
> almost lost the entire setup before and.my archives were all that saved
> it.  Crashplan is important.
> 
> Let me.see what is in the documentation about it.
> 
> Have you compared a process list on the two boxes and an nmap scan?
> 
> I recommend you make a copy of every scrap of data on the old.box over to
> the new.  When they decomm it you might need it.  We tried really hard to
> document it all but it was a big project.
> 
> On Tue, Jul 14, 2020, 08:08 Henrik K  wrote:
> 
> >
> > I have no clue about crashplan.  I assume that's your account, so please
> > install as you see fit.  It seems ASF infra also does backuppc/rsync
> > backups.
> >
> > Dunno but archives you are referring to, but I assume they would be under
> > /usr/local/spamassassin.
> >
> >
> > On Tue, Jul 14, 2020 at 08:00:15AM -0400, Kevin A. McGrail wrote:
> > > I do not remember, sorry.  It's been 3 years since I contacted them
> > last.  But
> > > at least for one of the DNS hosters, Send an email to [1]
> > supp...@pccc.com and I
> > > will make sure that a ticket for that mirror is updated.
> > >
> > > Did you get crashplan working on the new box?
> > >
> > > Also did you copy over all the data on the box?  I remember there are
> > archives
> > > there.  I can look through my notes about that.
> > >
> > >
> > >
> > > On Tue, Jul 14, 2020, 07:20 Henrik K <[2]h...@hege.li> wrote:
> > >
> > >
> > > Yes the new box is 100% identical in all aspects (pdns, rsync,
> > masscheck,
> > > ruleqa, certbot, perl/python modules, paths etc).  Only some minor
> > tweaks
> > > for Apache web server etc which make no difference documentation
> > wise.
> > >
> > > Of course cron jobs are not yet running, they would mess around too
> > much.
> > >
> > > I did not reach out to DNS people, I assume [3]
> > grant.kel...@sonic.com is
> > > still
> > > correct as per documentation, you probably know better..
> > >
> > > Cheers,
> > > Henrik
> > >
> > >
> > > On Tue, Jul 14, 2020 at 07:10:45AM -0400, Kevin A. McGrail wrote:
> > > > Nicely done.  Plus sysadmins list. Four key thought categories
> > below;
> > > >
> > > > Did you go through the documentation and the new box does
> > everything the
> > > > old box did?  Like power DNS and the DNS GUI?  Rsync and the
> > masscheck?
> > > > Ruleqa? The cron jobs? Sending root email to the same places?
> > > >
> > > > Did you update the documentation?  We worked hard on it and don't
> > want
> > > that
> > > > lost.
> > > >
> > > > Have you reached to the DNS providers yet?  We can likely ask for
> > two ips
> > > > to.allow xfer so no coordination is needed.
> > > >
> > > > Do you already have the cron jobs running?
> > > >
> > > > Beyond that we can switch any time you are around.  It will break
> > > masschecl
> > > > and everything and you might have to wait weeks to turn down the
> > old box.
> > > >
> > > > I would especially reach out to Dave Jones and see if he gives it a
> > > > greenlight.
> > > >
> > > > Thanks for working on this.  KAM
> > > >
> > > > On Tue, Jul 14, 2020, 06:57 Henrik K <[4]h...@hege.li> wrote:
> > > >
> > > > >
> > > > > Preparations are pretty much finished.
> > > > >
> > > > > Just need to agree on a date for the switchover.  What remains
> > to be
> > > done
> > > > > then is changing/allowing the new master IP on DNS slaves,
> > changing
> > > sa-vm1
> > > > > CNAMEs and final rsync.
> > > > >
> > > > > Could be for example next sunday or sometime next week.  Around
> > 17:00
> > > UTC
> > > > > seems a quiet time on the box and everyone US/EU should be awake
> > then..
> > > > >
> > > > >
> > > > > On Sat, Jun 20, 2020 at 05:18:32PM -0400, Kevin A. McGrail wrote:
> > > > > > Thanks Henrik for stepping up on it!
> > > > > > --
> > > > > > Kevin A. McGrail
> > > > > > Member, Apache Software Foundation
> > > > > > Chair Emeritus Apache SpamAssassin Project
> > > > > > [1][5]https://www.linkedin.com/in/kmcgrail - 703.798.0171
> > > > > >
> > > > > >
> > > > > > On Fri, Jun 19, 2020 at 3:50 PM Henrik K <[3][6]h...@hege.li>
> > wrote:
> > > > > >
> > > > > >
> > > > > > Fyi, answered in the ticket..
> > > > > >
> > > > > > On Fri, Jun 19, 2020 at 10:08:26AM -0500, Drew Foulks
> > wrote:
> > > > > > > Greetings SpamAssassin PMC!
> > > > > > >
> > > > > > > It's come to my attention that the VM that y'all are
> > using
> > > needs an
> > > > > > upgrade!
> > > > > > > I'd like to take care

Re: sa-vm1 migration to Ubuntu 18.04 / Puppet 6

2020-07-14 Thread Kevin A. McGrail 
No it's an asf project crashplan account and infra does not do backups.  We
almost lost the entire setup before and.my archives were all that saved
it.  Crashplan is important.

Let me.see what is in the documentation about it.

Have you compared a process list on the two boxes and an nmap scan?

I recommend you make a copy of every scrap of data on the old.box over to
the new.  When they decomm it you might need it.  We tried really hard to
document it all but it was a big project.

On Tue, Jul 14, 2020, 08:08 Henrik K  wrote:

>
> I have no clue about crashplan.  I assume that's your account, so please
> install as you see fit.  It seems ASF infra also does backuppc/rsync
> backups.
>
> Dunno but archives you are referring to, but I assume they would be under
> /usr/local/spamassassin.
>
>
> On Tue, Jul 14, 2020 at 08:00:15AM -0400, Kevin A. McGrail wrote:
> > I do not remember, sorry.  It's been 3 years since I contacted them
> last.  But
> > at least for one of the DNS hosters, Send an email to [1]
> supp...@pccc.com and I
> > will make sure that a ticket for that mirror is updated.
> >
> > Did you get crashplan working on the new box?
> >
> > Also did you copy over all the data on the box?  I remember there are
> archives
> > there.  I can look through my notes about that.
> >
> >
> >
> > On Tue, Jul 14, 2020, 07:20 Henrik K <[2]h...@hege.li> wrote:
> >
> >
> > Yes the new box is 100% identical in all aspects (pdns, rsync,
> masscheck,
> > ruleqa, certbot, perl/python modules, paths etc).  Only some minor
> tweaks
> > for Apache web server etc which make no difference documentation
> wise.
> >
> > Of course cron jobs are not yet running, they would mess around too
> much.
> >
> > I did not reach out to DNS people, I assume [3]
> grant.kel...@sonic.com is
> > still
> > correct as per documentation, you probably know better..
> >
> > Cheers,
> > Henrik
> >
> >
> > On Tue, Jul 14, 2020 at 07:10:45AM -0400, Kevin A. McGrail wrote:
> > > Nicely done.  Plus sysadmins list. Four key thought categories
> below;
> > >
> > > Did you go through the documentation and the new box does
> everything the
> > > old box did?  Like power DNS and the DNS GUI?  Rsync and the
> masscheck?
> > > Ruleqa? The cron jobs? Sending root email to the same places?
> > >
> > > Did you update the documentation?  We worked hard on it and don't
> want
> > that
> > > lost.
> > >
> > > Have you reached to the DNS providers yet?  We can likely ask for
> two ips
> > > to.allow xfer so no coordination is needed.
> > >
> > > Do you already have the cron jobs running?
> > >
> > > Beyond that we can switch any time you are around.  It will break
> > masschecl
> > > and everything and you might have to wait weeks to turn down the
> old box.
> > >
> > > I would especially reach out to Dave Jones and see if he gives it a
> > > greenlight.
> > >
> > > Thanks for working on this.  KAM
> > >
> > > On Tue, Jul 14, 2020, 06:57 Henrik K <[4]h...@hege.li> wrote:
> > >
> > > >
> > > > Preparations are pretty much finished.
> > > >
> > > > Just need to agree on a date for the switchover.  What remains
> to be
> > done
> > > > then is changing/allowing the new master IP on DNS slaves,
> changing
> > sa-vm1
> > > > CNAMEs and final rsync.
> > > >
> > > > Could be for example next sunday or sometime next week.  Around
> 17:00
> > UTC
> > > > seems a quiet time on the box and everyone US/EU should be awake
> then..
> > > >
> > > >
> > > > On Sat, Jun 20, 2020 at 05:18:32PM -0400, Kevin A. McGrail wrote:
> > > > > Thanks Henrik for stepping up on it!
> > > > > --
> > > > > Kevin A. McGrail
> > > > > Member, Apache Software Foundation
> > > > > Chair Emeritus Apache SpamAssassin Project
> > > > > [1][5]https://www.linkedin.com/in/kmcgrail - 703.798.0171
> > > > >
> > > > >
> > > > > On Fri, Jun 19, 2020 at 3:50 PM Henrik K <[3][6]h...@hege.li>
> wrote:
> > > > >
> > > > >
> > > > > Fyi, answered in the ticket..
> > > > >
> > > > > On Fri, Jun 19, 2020 at 10:08:26AM -0500, Drew Foulks
> wrote:
> > > > > > Greetings SpamAssassin PMC!
> > > > > >
> > > > > > It's come to my attention that the VM that y'all are
> using
> > needs an
> > > > > upgrade!
> > > > > > I'd like to take care of that for you and can start
> working on
> > > > this as
> > > > > soon as
> > > > > > y'all say go. In the meantime, I've created a ticket (and
> > linked
> > > > your
> > > > > trouble
> > > > > > ticket) so that we can discuss and track this upgrade.
> > > > > >
> > > > > > [1][4][7]
> https://issues.apache.org/jira/browse/INFRA-20449
> > > > > >
> > > > > > cheers,
> > > > > > --
> > >

Re: sa-vm1 migration to Ubuntu 18.04 / Puppet 6

2020-07-14 Thread Henrik K 


Of course /var/www is copied also.  And few home directories that had some
stuff under them.

On Tue, Jul 14, 2020 at 03:08:34PM +0300, Henrik K wrote:
> 
> I have no clue about crashplan.  I assume that's your account, so please
> install as you see fit.  It seems ASF infra also does backuppc/rsync
> backups.
> 
> Dunno but archives you are referring to, but I assume they would be under
> /usr/local/spamassassin.
> 
> 
> On Tue, Jul 14, 2020 at 08:00:15AM -0400, Kevin A. McGrail wrote:
> > I do not remember, sorry.  It's been 3 years since I contacted them last.  
> > But
> > at least for one of the DNS hosters, Send an email to [1]supp...@pccc.com 
> > and I
> > will make sure that a ticket for that mirror is updated.
> > 
> > Did you get crashplan working on the new box?
> > 
> > Also did you copy over all the data on the box?  I remember there are 
> > archives
> > there.  I can look through my notes about that.
> > 
> > 
> > 
> > On Tue, Jul 14, 2020, 07:20 Henrik K <[2]h...@hege.li> wrote:
> > 
> > 
> > Yes the new box is 100% identical in all aspects (pdns, rsync, 
> > masscheck,
> > ruleqa, certbot, perl/python modules, paths etc).  Only some minor 
> > tweaks
> > for Apache web server etc which make no difference documentation wise.
> > 
> > Of course cron jobs are not yet running, they would mess around too 
> > much.
> > 
> > I did not reach out to DNS people, I assume [3]grant.kel...@sonic.com is
> > still
> > correct as per documentation, you probably know better..
> > 
> > Cheers,
> > Henrik
> > 
> > 
> > On Tue, Jul 14, 2020 at 07:10:45AM -0400, Kevin A. McGrail wrote:
> > > Nicely done.  Plus sysadmins list. Four key thought categories below;
> > >
> > > Did you go through the documentation and the new box does everything 
> > the
> > > old box did?  Like power DNS and the DNS GUI?  Rsync and the 
> > masscheck?
> > > Ruleqa? The cron jobs? Sending root email to the same places?
> > >
> > > Did you update the documentation?  We worked hard on it and don't want
> > that
> > > lost.
> > >
> > > Have you reached to the DNS providers yet?  We can likely ask for two 
> > ips
> > > to.allow xfer so no coordination is needed.
> > >
> > > Do you already have the cron jobs running?
> > >
> > > Beyond that we can switch any time you are around.  It will break
> > masschecl
> > > and everything and you might have to wait weeks to turn down the old 
> > box.
> > >
> > > I would especially reach out to Dave Jones and see if he gives it a
> > > greenlight.
> > >
> > > Thanks for working on this.  KAM
> > >
> > > On Tue, Jul 14, 2020, 06:57 Henrik K <[4]h...@hege.li> wrote:
> > >
> > > >
> > > > Preparations are pretty much finished.
> > > >
> > > > Just need to agree on a date for the switchover.  What remains to be
> > done
> > > > then is changing/allowing the new master IP on DNS slaves, changing
> > sa-vm1
> > > > CNAMEs and final rsync.
> > > >
> > > > Could be for example next sunday or sometime next week.  Around 
> > 17:00
> > UTC
> > > > seems a quiet time on the box and everyone US/EU should be awake 
> > then..
> > > >
> > > >
> > > > On Sat, Jun 20, 2020 at 05:18:32PM -0400, Kevin A. McGrail wrote:
> > > > > Thanks Henrik for stepping up on it!
> > > > > --
> > > > > Kevin A. McGrail
> > > > > Member, Apache Software Foundation
> > > > > Chair Emeritus Apache SpamAssassin Project
> > > > > [1][5]https://www.linkedin.com/in/kmcgrail - 703.798.0171
> > > > >
> > > > >
> > > > > On Fri, Jun 19, 2020 at 3:50 PM Henrik K <[3][6]h...@hege.li> 
> > wrote:
> > > > >
> > > > >
> > > > >     Fyi, answered in the ticket..
> > > > >
> > > > >     On Fri, Jun 19, 2020 at 10:08:26AM -0500, Drew Foulks wrote:
> > > > >     > Greetings SpamAssassin PMC!
> > > > >     >
> > > > >     > It's come to my attention that the VM that y'all are using
> > needs an
> > > > >     upgrade!
> > > > >     > I'd like to take care of that for you and can start working 
> > on
> > > > this as
> > > > >     soon as
> > > > >     > y'all say go. In the meantime, I've created a ticket (and
> > linked
> > > > your
> > > > >     trouble
> > > > >     > ticket) so that we can discuss and track this upgrade.
> > > > >     >
> > > > >     > [1][4][7]https://issues.apache.org/jira/browse/INFRA-20449
> > > > >     >
> > > > >     > cheers,
> > > > >     > --
> > > > >     > Drew Foulks, ASF Infra
> > > > >     >
> > > > >     >
> > > > >     >
> > > > >     > References:
> > > > >     >
> > > > >     > [1] [5][8]https://issues.apache.org/jira/browse/INFRA-20449
> > > > >
> > > > >
> > > > > References:
> > > > >
> > > > > [1]

Re: sa-vm1 migration to Ubuntu 18.04 / Puppet 6

2020-07-14 Thread Henrik K 


I have no clue about crashplan.  I assume that's your account, so please
install as you see fit.  It seems ASF infra also does backuppc/rsync
backups.

Dunno but archives you are referring to, but I assume they would be under
/usr/local/spamassassin.


On Tue, Jul 14, 2020 at 08:00:15AM -0400, Kevin A. McGrail wrote:
> I do not remember, sorry.  It's been 3 years since I contacted them last.  But
> at least for one of the DNS hosters, Send an email to [1]supp...@pccc.com and 
> I
> will make sure that a ticket for that mirror is updated.
> 
> Did you get crashplan working on the new box?
> 
> Also did you copy over all the data on the box?  I remember there are archives
> there.  I can look through my notes about that.
> 
> 
> 
> On Tue, Jul 14, 2020, 07:20 Henrik K <[2]h...@hege.li> wrote:
> 
> 
> Yes the new box is 100% identical in all aspects (pdns, rsync, masscheck,
> ruleqa, certbot, perl/python modules, paths etc).  Only some minor tweaks
> for Apache web server etc which make no difference documentation wise.
> 
> Of course cron jobs are not yet running, they would mess around too much.
> 
> I did not reach out to DNS people, I assume [3]grant.kel...@sonic.com is
> still
> correct as per documentation, you probably know better..
> 
> Cheers,
> Henrik
> 
> 
> On Tue, Jul 14, 2020 at 07:10:45AM -0400, Kevin A. McGrail wrote:
> > Nicely done.  Plus sysadmins list. Four key thought categories below;
> >
> > Did you go through the documentation and the new box does everything the
> > old box did?  Like power DNS and the DNS GUI?  Rsync and the masscheck?
> > Ruleqa? The cron jobs? Sending root email to the same places?
> >
> > Did you update the documentation?  We worked hard on it and don't want
> that
> > lost.
> >
> > Have you reached to the DNS providers yet?  We can likely ask for two 
> ips
> > to.allow xfer so no coordination is needed.
> >
> > Do you already have the cron jobs running?
> >
> > Beyond that we can switch any time you are around.  It will break
> masschecl
> > and everything and you might have to wait weeks to turn down the old 
> box.
> >
> > I would especially reach out to Dave Jones and see if he gives it a
> > greenlight.
> >
> > Thanks for working on this.  KAM
> >
> > On Tue, Jul 14, 2020, 06:57 Henrik K <[4]h...@hege.li> wrote:
> >
> > >
> > > Preparations are pretty much finished.
> > >
> > > Just need to agree on a date for the switchover.  What remains to be
> done
> > > then is changing/allowing the new master IP on DNS slaves, changing
> sa-vm1
> > > CNAMEs and final rsync.
> > >
> > > Could be for example next sunday or sometime next week.  Around 17:00
> UTC
> > > seems a quiet time on the box and everyone US/EU should be awake 
> then..
> > >
> > >
> > > On Sat, Jun 20, 2020 at 05:18:32PM -0400, Kevin A. McGrail wrote:
> > > > Thanks Henrik for stepping up on it!
> > > > --
> > > > Kevin A. McGrail
> > > > Member, Apache Software Foundation
> > > > Chair Emeritus Apache SpamAssassin Project
> > > > [1][5]https://www.linkedin.com/in/kmcgrail - 703.798.0171
> > > >
> > > >
> > > > On Fri, Jun 19, 2020 at 3:50 PM Henrik K <[3][6]h...@hege.li> wrote:
> > > >
> > > >
> > > >     Fyi, answered in the ticket..
> > > >
> > > >     On Fri, Jun 19, 2020 at 10:08:26AM -0500, Drew Foulks wrote:
> > > >     > Greetings SpamAssassin PMC!
> > > >     >
> > > >     > It's come to my attention that the VM that y'all are using
> needs an
> > > >     upgrade!
> > > >     > I'd like to take care of that for you and can start working on
> > > this as
> > > >     soon as
> > > >     > y'all say go. In the meantime, I've created a ticket (and
> linked
> > > your
> > > >     trouble
> > > >     > ticket) so that we can discuss and track this upgrade.
> > > >     >
> > > >     > [1][4][7]https://issues.apache.org/jira/browse/INFRA-20449
> > > >     >
> > > >     > cheers,
> > > >     > --
> > > >     > Drew Foulks, ASF Infra
> > > >     >
> > > >     >
> > > >     >
> > > >     > References:
> > > >     >
> > > >     > [1] [5][8]https://issues.apache.org/jira/browse/INFRA-20449
> > > >
> > > >
> > > > References:
> > > >
> > > > [1] [9]https://www.linkedin.com/in/kmcgrail
> > > > [3] mailto:[10]h...@hege.li
> > > > [4] [11]https://issues.apache.org/jira/browse/INFRA-20449
> > > > [5] [12]https://issues.apache.org/jira/browse/INFRA-20449
> > >
> 
> 
> References:
> 
> [1] mailto:supp...@pccc.com
> [2] mailto:h...@hege.li
> [3] mailto:grant.kel...@sonic.com
> [4] mailto:h...@hege.li
> [5] https://www.linkedin.com/in/kmcgrail
> [6] mailto:h...@hege.li
> [7]

Re: sa-vm1 migration to Ubuntu 18.04 / Puppet 6

2020-07-14 Thread Kevin A. McGrail 
I do not remember, sorry.  It's been 3 years since I contacted them last.
But at least for one of the DNS hosters, Send an email to supp...@pccc.com
and I will make sure that a ticket for that mirror is updated.

Did you get crashplan working on the new box?

Also did you copy over all the data on the box?  I remember there are
archives there.  I can look through my notes about that.



On Tue, Jul 14, 2020, 07:20 Henrik K  wrote:

>
> Yes the new box is 100% identical in all aspects (pdns, rsync, masscheck,
> ruleqa, certbot, perl/python modules, paths etc).  Only some minor tweaks
> for Apache web server etc which make no difference documentation wise.
>
> Of course cron jobs are not yet running, they would mess around too much.
>
> I did not reach out to DNS people, I assume grant.kel...@sonic.com is
> still
> correct as per documentation, you probably know better..
>
> Cheers,
> Henrik
>
>
> On Tue, Jul 14, 2020 at 07:10:45AM -0400, Kevin A. McGrail wrote:
> > Nicely done.  Plus sysadmins list. Four key thought categories below;
> >
> > Did you go through the documentation and the new box does everything the
> > old box did?  Like power DNS and the DNS GUI?  Rsync and the masscheck?
> > Ruleqa? The cron jobs? Sending root email to the same places?
> >
> > Did you update the documentation?  We worked hard on it and don't want
> that
> > lost.
> >
> > Have you reached to the DNS providers yet?  We can likely ask for two ips
> > to.allow xfer so no coordination is needed.
> >
> > Do you already have the cron jobs running?
> >
> > Beyond that we can switch any time you are around.  It will break
> masschecl
> > and everything and you might have to wait weeks to turn down the old box.
> >
> > I would especially reach out to Dave Jones and see if he gives it a
> > greenlight.
> >
> > Thanks for working on this.  KAM
> >
> > On Tue, Jul 14, 2020, 06:57 Henrik K  wrote:
> >
> > >
> > > Preparations are pretty much finished.
> > >
> > > Just need to agree on a date for the switchover.  What remains to be
> done
> > > then is changing/allowing the new master IP on DNS slaves, changing
> sa-vm1
> > > CNAMEs and final rsync.
> > >
> > > Could be for example next sunday or sometime next week.  Around 17:00
> UTC
> > > seems a quiet time on the box and everyone US/EU should be awake then..
> > >
> > >
> > > On Sat, Jun 20, 2020 at 05:18:32PM -0400, Kevin A. McGrail wrote:
> > > > Thanks Henrik for stepping up on it!
> > > > --
> > > > Kevin A. McGrail
> > > > Member, Apache Software Foundation
> > > > Chair Emeritus Apache SpamAssassin Project
> > > > [1]https://www.linkedin.com/in/kmcgrail - 703.798.0171
> > > >
> > > >
> > > > On Fri, Jun 19, 2020 at 3:50 PM Henrik K <[3]h...@hege.li> wrote:
> > > >
> > > >
> > > > Fyi, answered in the ticket..
> > > >
> > > > On Fri, Jun 19, 2020 at 10:08:26AM -0500, Drew Foulks wrote:
> > > > > Greetings SpamAssassin PMC!
> > > > >
> > > > > It's come to my attention that the VM that y'all are using
> needs an
> > > > upgrade!
> > > > > I'd like to take care of that for you and can start working on
> > > this as
> > > > soon as
> > > > > y'all say go. In the meantime, I've created a ticket (and
> linked
> > > your
> > > > trouble
> > > > > ticket) so that we can discuss and track this upgrade.
> > > > >
> > > > > [1][4]https://issues.apache.org/jira/browse/INFRA-20449
> > > > >
> > > > > cheers,
> > > > > --
> > > > > Drew Foulks, ASF Infra
> > > > >
> > > > >
> > > > >
> > > > > References:
> > > > >
> > > > > [1] [5]https://issues.apache.org/jira/browse/INFRA-20449
> > > >
> > > >
> > > > References:
> > > >
> > > > [1] https://www.linkedin.com/in/kmcgrail
> > > > [3] mailto:h...@hege.li
> > > > [4] https://issues.apache.org/jira/browse/INFRA-20449
> > > > [5] https://issues.apache.org/jira/browse/INFRA-20449
> > >
>

Re: sa-vm1 migration to Ubuntu 18.04 / Puppet 6

2020-07-14 Thread Henrik K 


Yes the new box is 100% identical in all aspects (pdns, rsync, masscheck,
ruleqa, certbot, perl/python modules, paths etc).  Only some minor tweaks
for Apache web server etc which make no difference documentation wise.

Of course cron jobs are not yet running, they would mess around too much.

I did not reach out to DNS people, I assume grant.kel...@sonic.com is still
correct as per documentation, you probably know better..

Cheers,
Henrik


On Tue, Jul 14, 2020 at 07:10:45AM -0400, Kevin A. McGrail wrote:
> Nicely done.  Plus sysadmins list. Four key thought categories below;
> 
> Did you go through the documentation and the new box does everything the
> old box did?  Like power DNS and the DNS GUI?  Rsync and the masscheck?
> Ruleqa? The cron jobs? Sending root email to the same places?
> 
> Did you update the documentation?  We worked hard on it and don't want that
> lost.
> 
> Have you reached to the DNS providers yet?  We can likely ask for two ips
> to.allow xfer so no coordination is needed.
> 
> Do you already have the cron jobs running?
> 
> Beyond that we can switch any time you are around.  It will break masschecl
> and everything and you might have to wait weeks to turn down the old box.
> 
> I would especially reach out to Dave Jones and see if he gives it a
> greenlight.
> 
> Thanks for working on this.  KAM
> 
> On Tue, Jul 14, 2020, 06:57 Henrik K  wrote:
> 
> >
> > Preparations are pretty much finished.
> >
> > Just need to agree on a date for the switchover.  What remains to be done
> > then is changing/allowing the new master IP on DNS slaves, changing sa-vm1
> > CNAMEs and final rsync.
> >
> > Could be for example next sunday or sometime next week.  Around 17:00 UTC
> > seems a quiet time on the box and everyone US/EU should be awake then..
> >
> >
> > On Sat, Jun 20, 2020 at 05:18:32PM -0400, Kevin A. McGrail wrote:
> > > Thanks Henrik for stepping up on it!
> > > --
> > > Kevin A. McGrail
> > > Member, Apache Software Foundation
> > > Chair Emeritus Apache SpamAssassin Project
> > > [1]https://www.linkedin.com/in/kmcgrail - 703.798.0171
> > >
> > >
> > > On Fri, Jun 19, 2020 at 3:50 PM Henrik K <[3]h...@hege.li> wrote:
> > >
> > >
> > > Fyi, answered in the ticket..
> > >
> > > On Fri, Jun 19, 2020 at 10:08:26AM -0500, Drew Foulks wrote:
> > > > Greetings SpamAssassin PMC!
> > > >
> > > > It's come to my attention that the VM that y'all are using needs an
> > > upgrade!
> > > > I'd like to take care of that for you and can start working on
> > this as
> > > soon as
> > > > y'all say go. In the meantime, I've created a ticket (and linked
> > your
> > > trouble
> > > > ticket) so that we can discuss and track this upgrade.
> > > >
> > > > [1][4]https://issues.apache.org/jira/browse/INFRA-20449
> > > >
> > > > cheers,
> > > > --
> > > > Drew Foulks, ASF Infra
> > > >
> > > >
> > > >
> > > > References:
> > > >
> > > > [1] [5]https://issues.apache.org/jira/browse/INFRA-20449
> > >
> > >
> > > References:
> > >
> > > [1] https://www.linkedin.com/in/kmcgrail
> > > [3] mailto:h...@hege.li
> > > [4] https://issues.apache.org/jira/browse/INFRA-20449
> > > [5] https://issues.apache.org/jira/browse/INFRA-20449
> >

Re: sa-vm1 migration to Ubuntu 18.04 / Puppet 6

2020-07-14 Thread Kevin A. McGrail 
Nicely done.  Plus sysadmins list. Four key thought categories below;

Did you go through the documentation and the new box does everything the
old box did?  Like power DNS and the DNS GUI?  Rsync and the masscheck?
Ruleqa? The cron jobs? Sending root email to the same places?

Did you update the documentation?  We worked hard on it and don't want that
lost.

Have you reached to the DNS providers yet?  We can likely ask for two ips
to.allow xfer so no coordination is needed.

Do you already have the cron jobs running?

Beyond that we can switch any time you are around.  It will break masschecl
and everything and you might have to wait weeks to turn down the old box.

I would especially reach out to Dave Jones and see if he gives it a
greenlight.

Thanks for working on this.  KAM

On Tue, Jul 14, 2020, 06:57 Henrik K  wrote:

>
> Preparations are pretty much finished.
>
> Just need to agree on a date for the switchover.  What remains to be done
> then is changing/allowing the new master IP on DNS slaves, changing sa-vm1
> CNAMEs and final rsync.
>
> Could be for example next sunday or sometime next week.  Around 17:00 UTC
> seems a quiet time on the box and everyone US/EU should be awake then..
>
>
> On Sat, Jun 20, 2020 at 05:18:32PM -0400, Kevin A. McGrail wrote:
> > Thanks Henrik for stepping up on it!
> > --
> > Kevin A. McGrail
> > Member, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > [1]https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >
> >
> > On Fri, Jun 19, 2020 at 3:50 PM Henrik K <[3]h...@hege.li> wrote:
> >
> >
> > Fyi, answered in the ticket..
> >
> > On Fri, Jun 19, 2020 at 10:08:26AM -0500, Drew Foulks wrote:
> > > Greetings SpamAssassin PMC!
> > >
> > > It's come to my attention that the VM that y'all are using needs an
> > upgrade!
> > > I'd like to take care of that for you and can start working on
> this as
> > soon as
> > > y'all say go. In the meantime, I've created a ticket (and linked
> your
> > trouble
> > > ticket) so that we can discuss and track this upgrade.
> > >
> > > [1][4]https://issues.apache.org/jira/browse/INFRA-20449
> > >
> > > cheers,
> > > --
> > > Drew Foulks, ASF Infra
> > >
> > >
> > >
> > > References:
> > >
> > > [1] [5]https://issues.apache.org/jira/browse/INFRA-20449
> >
> >
> > References:
> >
> > [1] https://www.linkedin.com/in/kmcgrail
> > [3] mailto:h...@hege.li
> > [4] https://issues.apache.org/jira/browse/INFRA-20449
> > [5] https://issues.apache.org/jira/browse/INFRA-20449
>