<div dir="ltr">Oh,<div><br></div><div>that was a misunderstanding. You should not change the client script that way, but test at shell level what the df -P output is like (especially if the USB output is all in one line).</div><div>As Michael pointed out, the server routines needs the standard Posix output format.</div><div>But if you run the standard client script manually, you will see the same output as at server side under "client info available". In the df section there should be the USB disk usage in one line like the other partitions.</div><div>If it is not there, but visible by df -P at the client, then it is stripped by the $EXCLUDE in the client script.</div><div><br></div><div>Norbert </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am Di., 29. Nov. 2022 um 20:41 Uhr schrieb Kris Springer <<a href="mailto:kspringer@innovateteam.com" target="_blank">kspringer@innovateteam.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
Running df -P | grep USB manually results in the following results,
with quite a bit of space between the output sections.<br>
/dev/sda 960303848 268800 911180536 1%
/media/user/USB-1TB<br>
<br>
Putting df -P | grep USB into the script results in the Server page
showing the 'Expected strings (Capacity and Mounted) not found'
error<br>
<br>
<pre cols="72">Kris Springer
</pre>
<div>On 11/29/22 10:07, nor krie wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi Kris,
<div><br>
</div>
<div>in analysis.cfg you can only set thresholds for disks which
are reported by the client and thus are already visible in the
disk and inode column of your Xymon server.</div>
<div>If there is no USB drive and no graph, then you don't need
to mess up with server side config.</div>
<div>By default the Xymon client will only provide info about
local disks (which makes sense, as the remote mounted disks
should be monitored at the source and not at dozens of
connected servers), and also only for fixed mounted disks to
avoid alerts if a removable media gets disconnected.</div>
<div>If you want to change this you have to modify the linux
client script (but as pointed out, ensure the output as Posix
standard to not confuse the server side evaluation!).</div>
<div>So it is no problem to remove the "l" from "df -Pl", but
not the "P". You can also remove the "-x $EXCLUDES" w/o
problems.</div>
<div>Does a "df -P | grep USB" show your USB drive?</div>
<div>If yes, modify the client script and test by
"./xymonclient-linux.sh | grep USB". This also should show
your USB drive.</div>
<div>If not, the disk is not properly mounted.</div>
<div><br>
</div>
<div>Norbert</div>
<div><br>
</div>
<div> </div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Am Di., 29. Nov. 2022 um
17:11 Uhr schrieb Kris Springer <<a href="mailto:kspringer@innovateteam.com" target="_blank">kspringer@innovateteam.com</a>>:<br>
</div>
<blockquote class="gmail_quote">Continued thanks for the
responses. I did try commenting everything out <br>
of the analysis.cfg except for the default DISK * line, but
still no <br>
joy. I don't think analysis.cfg is causing the USB to be
ignored. The <br>
xymonclient-linux script has been set back to it's original
state.<br>
<br>
Kris Springer<br>
<br>
<br>
On 11/29/22 08:28, Adam Thorn wrote:<br>
> On 29/11/2022 01:21, Kris Springer wrote:<br>
><br>
>> Thanks for pointing me in the direction of the client
script. I <br>
>> messed around with it a lot<br>
><br>
> I'd advise against editing the xymonclient script unless
you're very <br>
> careful, because...<br>
><br>
>> So then in the script with all the df stuff commented
out, I had it run<br>
>> df /dev/sda<br>
><br>
> ...putting this in the client script will break
server-side processing <br>
> because...<br>
><br>
>> The results of the script show the USB, but nothing
shows up on the <br>
>> Server Disk page except this error.<br>
>> Expected strings (Capacity and Mounted) not found in
df output<br>
><br>
> ..one of the df arguments specified in the original
client script is <br>
> "-P" which specifies "use the POSIX output format".
Compare the header <br>
> row generated by df with and without -P:<br>
><br>
> $ df | head -n1<br>
> Filesystem 1K-blocks Used Available Use% Mounted
on<br>
><br>
> $ df -P | head -n1<br>
> Filesystem 1024-blocks Used Available Capacity
Mounted on<br>
><br>
> xymond is expecting the latter format, so by manually
hacking the <br>
> client script and changing the arguments, the message
sent to the <br>
> server is no longer in the format it expects - which is
what's leading <br>
> to that "Expected strings ... not found" message, I
think.<br>
><br>
> I'd suggest putting the original client script back in
place and <br>
> debugging from there. Perhaps a good place to start would
be with a <br>
> very simple analysis.cfg with just two lines:<br>
><br>
> DEFAULT<br>
> DISK * 90 95<br>
><br>
> and nothing else. If your disk then shows up in the
'disk' report, the <br>
> problem is somewhere in your live analysis.cfg. I'm not
immediately <br>
> sure when analysis.cfg is reread - I can't see any
mention in the <br>
> documentation, but I may not be looking in the right
place.<br>
><br>
> Adam<br>
> _______________________________________________<br>
> Xymon mailing list<br>
> <a href="mailto:Xymon@xymon.com" target="_blank">Xymon@xymon.com</a><br>
> <a href="http://lists.xymon.com/mailman/listinfo/xymon" rel="noreferrer" target="_blank">http://lists.xymon.com/mailman/listinfo/xymon</a><br>
<br>
_______________________________________________<br>
Xymon mailing list<br>
<a href="mailto:Xymon@xymon.com" target="_blank">Xymon@xymon.com</a><br>
<a href="http://lists.xymon.com/mailman/listinfo/xymon" rel="noreferrer" target="_blank">http://lists.xymon.com/mailman/listinfo/xymon</a><br>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote></div>