Re: masscheck sync server down?

2017-09-13 Thread Kevin A. McGrail

On 9/13/2017 5:28 AM, Tom Hendrikx wrote:

Hi,

This morning, masscheck gives me this error while syncing the initial
data (i.e. not the results):

Syncing nightly_mass_check
rsync: safe_read failed to read 1 bytes [Receiver]: Connection reset by
peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(276)
[Receiver=3.1.1]
ERROR: rsync failure 12, aborting...

Kind regards,

Tom


Thanks Tom, one of the issues we've been struggling with is the 
stability of that box.  It's a VM but the overall switch to Ubuntu and 
the lack of swap space has made some of our processes be auto-killed.  
And last time it hung the box.


https://issues.apache.org/jira/browse/INFRA-15078 is open and really 
appreciate you responding.  I was just looking for the reports from the 
machine.


Regards,
KM



Cron svn update /var/www/automc.spamassassin.org/updates > /dev/null

2017-09-13 Thread Cron Daemon
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for 
details)
svn: E155004: Working copy '/var/www/automc.spamassassin.org/updates' locked.
svn: E155004: '/var/www/automc.spamassassin.org/updates' is already locked.


checkSAupdateMirrors.sh on sa-vm1.apache.org - 0 mirrors DOWN, 5 mirrors STALE

2017-09-13 Thread root
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY

http://sa-update.dnswl.org/: UP (STALE)

http://www.sa-update.pccc.com/: UP (STALE)

http://sa-update.secnap.net/: UP (STALE)

http://sa-update.space-pro.be/: UP (STALE)

http://sa-update.ena.com/: UP (STALE)


Fwd: [jira] [Commented] (INFRA-15078) Cannot SSH to sa-vm1.apache.org

2017-09-13 Thread Kevin A. McGrail

FYI



 Forwarded Message 
Subject:[jira] [Commented] (INFRA-15078) Cannot SSH to sa-vm1.apache.org
Date:   Wed, 13 Sep 2017 13:10:00 + (UTC)
From:   Daniel Takamori (JIRA) 
To: kmcgr...@apache.org



[ 
https://issues.apache.org/jira/browse/INFRA-15078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164624#comment-16164624
 ]

Daniel Takamori commented on INFRA-15078:
-

I bumped the RAM to 12g and increased the cores from 4 -> 6.  Looks like 
something is OOMing so I'd take a look at your logs to make sure everything is 
running correctly.


Cannot SSH to sa-vm1.apache.org
---

Key: INFRA-15078
URL: https://issues.apache.org/jira/browse/INFRA-15078
Project: Infrastructure
 Issue Type: Project
 Components: VM
   Reporter: Kevin A. McGrail
   Assignee: Daniel Takamori

Repeat of INFRA-14785 likely and we have a hung box again.  Can you increase 
the RAM by 2-8GB depending on what you see?  Ty!




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)



Re: masscheck sync server down?

2017-09-13 Thread Kevin A. McGrail

Tom, the box ran out of ram.  We've increased the ram and bounced it.

Thanks again for letting us know!

Regards,
KAM


Cron svn update /var/www/automc.spamassassin.org/updates > /dev/null

2017-09-13 Thread Cron Daemon
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for 
details)
svn: E155004: Working copy '/var/www/automc.spamassassin.org/updates' locked.
svn: E155004: '/var/www/automc.spamassassin.org/updates' is already locked.


Cron svn update /var/www/automc.spamassassin.org/updates > /dev/null

2017-09-13 Thread Cron Daemon
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for 
details)
svn: E155004: Working copy '/var/www/automc.spamassassin.org/updates' locked.
svn: E155004: '/var/www/automc.spamassassin.org/updates' is already locked.


Cron svn update /var/www/automc.spamassassin.org/updates > /dev/null

2017-09-13 Thread Cron Daemon
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for 
details)
svn: E155004: Working copy '/var/www/automc.spamassassin.org/updates' locked.
svn: E155004: '/var/www/automc.spamassassin.org/updates' is already locked.


Cron svn update /var/www/automc.spamassassin.org/updates > /dev/null

2017-09-13 Thread Cron Daemon
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for 
details)
svn: E155004: Working copy '/var/www/automc.spamassassin.org/updates' locked.
svn: E155004: '/var/www/automc.spamassassin.org/updates' is already locked.


Cron svn update /var/www/automc.spamassassin.org/updates > /dev/null

2017-09-13 Thread Cron Daemon
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for 
details)
svn: E155004: Working copy '/var/www/automc.spamassassin.org/updates' locked.
svn: E155004: '/var/www/automc.spamassassin.org/updates' is already locked.


Cron svn update /var/www/automc.spamassassin.org/updates > /dev/null

2017-09-13 Thread Cron Daemon
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for 
details)
svn: E155004: Working copy '/var/www/automc.spamassassin.org/updates' locked.
svn: E155004: '/var/www/automc.spamassassin.org/updates' is already locked.


Cron svn update /var/www/automc.spamassassin.org/updates > /dev/null

2017-09-13 Thread Cron Daemon
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for 
details)
svn: E155004: Working copy '/var/www/automc.spamassassin.org/updates' locked.
svn: E155004: '/var/www/automc.spamassassin.org/updates' is already locked.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-13 Thread noreply

3.3.3.updates (TXT) -> \"1808086\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.