Hi Luke,
I have a few (~50) emails which perfSonar tried and failed to send,
but they ceased on 13 September. It looks as if it is trying to notify
the experts when there is a problem adding mesh tests. If you are still
seeing a "flood" this might suggest that your perfSonar box is not
working correctly (and Bristol is red on the Dashboard at
http://perfsonar.racf.bnl.gov:8080/exda/?page=25&cloudName=UK).
Cheers,
John
On 11/10/2013 13:44, L Kreczko wrote:
> Dear experts,
>
> Our perfSonar boxes seem to be trying to send many emails [1] to the
> admin addresses of other perfSonar boxes. Our IT services ask if this
> is an expected behaviour or a mis-configuration.
> Looking at some old documentation [2] it seems that perfSonar has
> indeed some sendmail modules.
>
> Is this absolutely required for the operation? It seems that if these
> emails are allowed this would lead to a virtual flood of emails for
> the site admins.
>
> Cheers,
> Luke
>
> [1] tail /var/log/maillog
> Oct 11 13:06:01 bfc postfix/smtp[17026]: AECFB2E09A6:
> to=<[log in to unmask]>, relay=none, delay=385029,
> delays=384909/0.13/120/0, dsn=4.4.1, status=deferred (connect to
> bristol.ac.uk.s200b2.psmtp.com[207.126.147.14]:25: Connection timed
> out)
> Oct 11 13:06:02 bfc postfix/smtp[17024]: 9F0292E09C6:
> to=<[log in to unmask]>, relay=none, delay=385029,
> delays=384909/0.12/120/0, dsn=4.4.1, status=deferred (connect to
> pic.es.s200b2.psmtp.com[207.126.147.14]:25: Connection timed out)
> Oct 11 13:06:02 bfc postfix/smtp[17024]: 9F0292E09C6:
> to=<[log in to unmask]>, relay=none, delay=385029, delays=384909/0.12/120/0,
> dsn=4.4.1, status=deferred (connect to
> pic.es.s200b2.psmtp.com[207.126.147.14]:25: Connection timed out)
>
> [2]
> http://www.terena.org/activities/training/perfsonar/berlin/docs/perfsonar-administration-guide-mainv2.1.pdf
>
|