Using gump.covalent.net to send nag-mails

[Stefan Bodewig <bo...@apache.org>]

Hi Sander,

the nightly Gump builds on gump.covalent.net are performed by a shell
script that I don't have write access to.  Could you please add the
following two lines

cd /home/rubys/gump
perl nag.pl work/naglist 

to the end of /home/rubys/bin/daily ?

This is supposed to make the machine send out mails on failing builds.
Those mails will probably need to get moderated in on the various dev
lists, but this is a different issue.

One problem I see is that I cannot seem to get gump.covalent.net to
send mails at all - and thus the above may not be enough.  I've tried
to send mails to myself (to bodewig@bost.de as well as
bodewig@apache.org) from the command line maybe an hour ago and still
haven't received anything yet.

I've also manually executed the perl script mentioned above, this
should have sent about twenty mails (if you want to review the logs).

Cheers

        Stefan

Re: http://cvs.apache.org/builds/gump/latest/

[Scott Sanders <sc...@dotnot.org>]

If no one beats me to it, I will try tonight.

Scott
On Thursday, October 9, 2003, at 12:07 PM, Adam R. B. Jack wrote:

> Does anybody have know-how/permissions to manually put a simple 
> index.html
> into the above that explain there is an outage, and point folks to 
> alternate
> servers via http://jakarta.apache.org/gump?

http://cvs.apache.org/builds/gump/latest/

["Adam R. B. Jack" <aj...@trysybase.com>]

Does anybody have know-how/permissions to manually put a simple index.html
into the above that explain there is an outage, and point folks to alternate
servers via http://jakarta.apache.org/gump?

regards,

Adam

Re: Using gump.covalent.net to send nag-mails

[Stefan Bodewig <bo...@apache.org>]

On Thu, 09 Oct 2003, Sander Temme <sa...@temme.net> wrote:

> Needs work. 

Many thanks for the work you've done so far!

Stefan

Re: Using gump.covalent.net to send nag-mails

[Sander Temme <sa...@temme.net>]

> So, we're not quite there yet, but we'll get this figured out.

Update: all the mails that sendmail just tried to send out bounced back,
including the 22 nag mails. ):

Needs work. 

S.

-- 
sander@temme.net              http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF

Re: Using gump.covalent.net to send nag-mails

[Sander Temme <sa...@temme.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> One problem I see is that I cannot seem to get gump.covalent.net to
> send mails at all - and thus the above may not be enough.  I've
> tried to send mails to myself (to bodewig@bost.de as well as
> bodewig@apache.org) from the command line maybe an hour ago and
> still haven't received anything yet.

OK... yeah, those were sitting in /var/spool/clientmqueue, deferred
for the reason that sendmail couldn't connect to the localhost.
Apparently, the sendmail on that box is set up to use its own deamon.
Bummer, cuz running a sendmail deamon on that machine is just not
going to work... 

I'm working on my Apachecon presentations today (and tomorrow, and
maybe the next day, and the day after that), but if I find time I'll
mess with the sendmail m4 configuration stuff to use our mailserver
as smarthost: that might work.
 
> I've also manually executed the perl script mentioned above, this
> should have sent about twenty mails (if you want to review the
> logs). 

The script says sendmail is in /usr/sbin, but on this box it's in
/usr/lib. Blame Sun. I have edited the  script and run it: the mails
were generated and ended up in that same clientmqueue directory I
mentioned above. I then briefly started the deamon and it sucked up
those deferred mails and sent them out: you should have yours by now
and the nag mails are also on their way.

So, we're not quite there yet, but we'll get this figured out.

S.

- -- 
sander@temme.net              http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.2 - not licensed for commercial use: www.pgp.com

iQA/AwUBP4WPwrK+vEAVKSSvEQINoACg4NHO10Ps3+MqNtAbVH9blUkUDGoAn0wM
dRiKGg0xbgxJUPA/nX5xG9F+
=/zIL
-----END PGP SIGNATURE-----