Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTSRV-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Menu
LISTSERV Archives LISTSERV Archives
LSTSRV-L Home LSTSRV-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Monitoring Listserv
From:
Nathan Brindle <[log in to unmask]>
Reply To:
LISTSERV give-and-take forum <[log in to unmask]>
Date:
Tue, 28 Apr 2009 16:23:09 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (12 lines)
At 03:24 PM 4/28/2009 -0400, you wrote:
>We use IPMonitor and I only test listserv to see if it is responding on
>port 25.

Just a small point -- I would say that's not a sufficient test, because LISTSERV itself does not listen on port 25.  So testing on port 25 is a good thing, but not sufficient in and of itself, since port 25 being responsive is not a guarantee that LISTSERV itself is running.

If you're going to rely on port tests, then I would also test port 2306 (the TCPGUI port), since LISTSERV does listen directly to that port.  To test port 2306, you have to connect, send a non-authenticated LISTSERV command (like THANKS) to it, and read the response, as it doesn't respond with a 220 message when opened.

At one point I had a prototype Nagios script for LISTSERV that worked to an extent, but I never got it to work the way really I wanted it to.

Nathan

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV