[Almost all of the various programs accept a
There are two tools which are specifically intended for finding problems:
Are things running?
The first thing to check is whether run-remstats2 is being started by cron.
Once it's running, you can check what data it found in the last run. Look in data/LAST/<collectorname>. The lines are all the data which that collector found on the last run.
First of all, make sure that the perl specified in the shebang line exists
and is the right perl to use. If you're getting a message like "
And make sure that the specified perl (in the example
If you're having difficulty getting data from remstats servers, you should check them out without the collectors. For the unix-status-server, you can make sure that you have access, by running the following on the server host:
% telnet localhost 1957 UNAME GO
If you don't get connected, you'll have to look at your inetd configuration, and the output it logs. You might have to run inetd with debugging flags to get it to log enough to be usefull.
If you get connected and then shortly afterwards disconnected, this is the
signature of the tcp_wrappers refusing a connection: check out
unix-status-server : collector-host localhost log-server : collector-host localhost
Note that inetd will refer to
Almost all of the programs will take a
If you're trying to figure out what's happening, it's helpful to run
run-remstats2 interactively with
Follow that by running a collector interactively with the
It's also good to know what the output of a collector looks like. You can
get a general description under collectors, or you can just run a collector
interactively and see what it comes up with. Remember that collectors won't
even try to get information that they don't need yet, so if you want to see
everything that the collector would get in a normal run, you might want to
There are some useful files to look at:
Send your report to the mailing-list <firstname.lastname@example.org>.
Always include the remstats version. You can find it in the
Run check-config interactively and include the output.
Describe what you ran to produce the error, including command-line args.
Include any error messages you received from cron, or found in any of the above files, even if you don't understand them.
Complain, in detail, about documentation or error messages which you don't understand. They're intended to be comprehensible.
All remstats error messages should be prefixed by
[Top] [Remstats] [SourceWorks] [RRDtool] [SourceForge]
Last updated Fri May 30 13:51:13 PDT 2003 by <email@example.com>.