Tool

Submitted by stegillard on 25 February 2008 - 6:56pm.

One thing I don't like is the auto setting of the log interval to a hard-coded 30 seconds if the server isn't "Healthy". Couldn't this be configurable?

Its also a little unpleasant to have the admin password stored in a clear text file.

Other than that, very useful!

Submitted by rpiercey on 26 February 2008 - 10:58am.

Great information.

It would be nice to have a startup script top run as a daemon.

I have tried using "edirmon -D &" but it stops updating after a few intervals.

Also a single loop option would be helpful then edirmon could be integrated with Hobbit Server.

Submitted by Dieseloreo on 1 April 2008 - 3:49pm.

try adding a file edirmon in /etc/xinet.d with all the needed args to run as a server from xinet.d

then restart xinet.d

or start the binary

edirmon -D /dev/null 2>&1 &

hit contrl -z
use command bg to send to background

then use disown -h to disown the process.

logout and the program will stay running.

Submitted by mkoeppl on 30 April 2008 - 1:19am.

Hello,

it would be fine to use CASA to store the username/password if running as daemon.

But really a nice tool.

Submitted by aterea on 9 June 2008 - 4:17pm.

any possiblity of allowing the log facility to be configurable?

Submitted by aterea on 9 June 2008 - 6:17pm.

is it possible to make hte logging facility configurable?
Instead of using LOG_USER we would like LOG_LOCAL0 or something like that so we can configure syslog to send these messages to a separate file from the main log file.

Submitted by tjbayly on 12 June 2008 - 12:53pm.

It would certainly be possible to make it configurable in a new version but since it's specified in only one place in code, it's also easy to change directly for yourself. Edit /opt/novell/edirmon/lib/environment.pl. The line in question is openlog("edirmon","ndelay,pid","LOG_USER"). Change LOG_USER to whatever valid facility you'd like.

Also, you didn't mention what flavor of Linux you are using, but if your distro uses syslog-ng it's pretty trivial to get edirmon messages into a separate file even if using the LOG_USER facility along with other processes. Something along the lines of:

filter f_edirmon { program('^edirmon); };
destination edirmon { file("/var/log/edirmon"); };
log { source(src); filter(f_edirmon); destination(edirmon); };

That would put them into a new /var/log/edirmon file. Eliminating it from the /var/log/messages file would be a question of modifying the filter f_messages to include:

and not filter(f_edirmon)

Submitted by Bambid on 19 June 2008 - 11:04am.

Even with oldie but goodie eDir 8.7.3 works this perfectly, good job.

David

Submitted by samthendsgod on 2 July 2008 - 12:59pm.

How difficult would it be to have an email sent when suspect or unhealthy state is reached? Maybe specify an smtp server, and an address to send an alert to? (I'm not a programmer - this may be trivial to do, or may cause a huge amount of rewrite....) I've got about 200 servers and 900 replicas to monitor, so checking all of the proactively would be unfeasible. But to get an email when a monitored server got itself into a bad state would be most-excellent.

Great product by the way!

Sam

Submitted by tjbayly on 7 July 2008 - 10:23pm.

It wouldn't be terribly difficult to add a sendmail module and have edirmon send e-mail directly, but it would violate one of the design principles. edirmon is written to be very minimal - it only uses stock perl so that the sysadmin doesn't have to install and compile a bunch of extras to use it.

In your case I'd look at accomplishing e-mail through the syslog: setting up a pipe to mail, implementing swatch, Novell Sentinel, etc.

Glad to hear that you find the tool useful.

Submitted by davidkrotil on 14 December 2008 - 3:48pm.

Hi,
are they any development news ? If not, I found after running this tool for a long time major design problem. You use ndsrepair to catch problems of edir, but you don't care about ndsrepair.log which is after long run very huge. I needed to delete this log while it has 15 GB.
You should change name of the log and put some rollover mechanism, that this log doesn't fill entire partition.

Regards