[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Testing email settings


Thanks - this worked fine as a test but I noticed that after stopping
condor_collector, condor_status stoped reporting the state of all the

But it flushed out the errors in my email configuration QED.


-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Alan De Smet
Sent: Friday, 25 January 2008 10:17 a.m.
To: Condor-Users Mail List
Subject: Re: [Condor-users] Testing email settings

Robin Harrington <robin.harrington@xxxxxxxxxxxxxxxx> wrote:
> there a simple way to cause Condor to send an email to the
> to test the settings?

Toss a random file into your SPOOL, then run "condor_preen
-mail".  Something like this should do the job, assuming a
unix-like system:

su condor
cd `condor_config_val spool`
touch eraseme
condor_preen -mail

This, of course, isn't quite the same as the daemons sending
email.  To test that, all I can recommend is killing a Condor
daemon with SEGV (11) or a similar signal.  condor_master should
notice the death, send email complaining, and restart the dead
process.  The condor_collector or condor_negotiator would make
good sacrificial victims, since Condor recovers from them
restarting quicking.  After that, condor_schedd or condor_startd
would work fine.  condor_master won't work, since it has no
parent to notice and send email.

Alan De Smet                              Condor Project Research
adesmet@xxxxxxxxxxx                http://www.cs.wisc.edu/condor/
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at: