Hi I have a new issue with 0.7.9

I have an interface on a local port 80, where a default apache webserver is
running. The 'Check Content URL' is "http://[ip#]/"; and 'Check Content RegExp'
is "Welcome", which is on the default page.

I guess the 'Established Connections' graph shows succesful content hits, set
like above. Though I keep getting zero in the graphs.

So after looking trough 'tcp_port_content.php' I checked the debug data.
first there is a line
"REGEXP: /Welcome/i"    which i was lookign for after i had seen the code.
Then the line
"DATA: "with indeed the data on "http://[ip#]/";

. so far so good.
then the 'var_dump($parts); //DEBUG':

array(1) {
  [0]=>
  string(7) "Welcome"
}

and in the php code there after $valid is set to true, which is also displayed
in teh next debug line:

 :  H   2 :  I  12 :  P  30 : tcp_content_analisis(tcp_..ent): valid|Welcome to
the Advanced Extranet Server, -> alarm(39): Nothing was done (time P:5.3 |
2.64)

but..
it still shows "alarm(39): Nothing was done", just like the other TCP port
polling, which don't have 'Check Content' checked in the webinterface.

I tried finding where it is going wrong, but did not find it yet.
Is my expectation about this 'Check Content' showing in the 'Established
Connections' graph correct? Or how does it else work?

This Check URL option is quite critical to what we want to use JFFNMS for, so I
have to get it working.

Thanks again, Alex

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
jffnms-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jffnms-users

Reply via email to