Hi Karl,
Karl Berry wrote:
> Bob/Assaf - these monit reports were sent to "root@localhost" and
> therefore were held for moderation in mailman. I didn't want to add that
> address to any mailman field because it's invalid; mailman will let you
> add it but then (annoyingly/wrongly/uselessly)
Bob/Assaf - these monit reports were sent to "root@localhost" and
therefore were held for moderation in mailman. I didn't want to add that
address to any mailman field because it's invalid; mailman will let you
add it but then (annoyingly/wrongly/uselessly) complain on a subsequent
edit to that
(moving to savannah-hackers-public@ mailing list)
Hello,
On Fri, Feb 24, 2017 at 04:31:53PM -0500, SC Postmaster wrote:
I periodically check on our mirror status's, just to be sure that
everything is updating properly and there are no issues for any of the
projects that we mirror.
Thank you
Hello Bob,
Thanks for fixing the NFS last night! (glad we found the solution).
On Fri, Feb 24, 2017 at 02:36:13AM -0700, Bob Proulx wrote:
But that does not appear to be it. I wrote a small test program to
acquire locks over the nfs mount and that seems to be working
perfectly. Therefore I
> I am still leaning toward a problem with locks over nfs as to why the
> rsync isn't working. But not sure yet.
But that does not appear to be it. I wrote a small test program to
acquire locks over the nfs mount and that seems to be working
perfectly. Therefore I not know why rsync is not
> Where do groups come from?
> MySQL on internal0 ! which was just rebooted!
>
> Then, checking download:/var/log/daemon.log shows clearly:
> ===
> Feb 24 03:03:25 download mountd[4812]: libnss-mysql: Connection to server
> '208.118.235.75' failed: Lost connection to MySQL server at 'reading