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,
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
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
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.
>
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
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
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?
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
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,
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
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
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
12 matches
Mail list logo
