Read docs/FAQ... there's quite a write up on URL security.

And, please, one problem per message, with a meaningful subject - e.g. "rrd
and URL security problem" - makes it easier in the future for others to find
that we've ANSWERED THE SAME QUESTION previously.

-----Burton


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> Of Fischman, Reuben
> Sent: Thursday, December 18, 2003 2:31 PM
> To: '[EMAIL PROTECTED]'
> Subject: [Ntop-dev] RRD Plugin problems..
>
>
> Thanks Luca for fixing that netflow issue.  Have had ntop running most of
> the day, and now I see the following in the syslog:
>
>
> Dec 18 15:22:28 linuxnm ntop[3442]:   **ERROR** URL security:
> '/plugins/rrdPlugin?action=graph&key=interfaces/NetFlow-device/hos
> ts//&name=
> bytesRcvd&title=bytesRcvd&start=now-12h&end=now' rejected
> (code=2)(client=131.19.176.157)
> Dec 18 15:22:28 linuxnm ntop[3442]:   **ERROR** Rejected request from
> address 131.19.176.157 (it previously sent ntop a bad request)
> Dec 18 15:25:08 linuxnm ntop[3442]:   **ERROR** Rejected request from
> address 131.19.176.157 (it previously sent ntop a bad request)
> Dec 18 15:26:39 linuxnm ntop[3442]:   **WARNING** RRD:
> rrd_update(/usr/local/share/ntop/rrd/interfaces/NetFlow-device/hos
> ts//bytesR
> cvd.rrd) error: illegal attempt to update using time 1071779175 when last
> update time is 1071779175 (minimum one second step)
> Dec 18 15:26:39 linuxnm ntop[3442]:   **WARNING** RRD:
> rrd_update(/usr/local/share/ntop/rrd/interfaces/NetFlow-device/hos
> ts//bytesS
> entLoc.rrd) error: illegal attempt to update using time
> 1071779175 when last
> update time is 1071779175 (minimum one second step)
> Dec 18 15:26:39 linuxnm ntop[3442]:   **WARNING** RRD:
> rrd_update(/usr/local/share/ntop/rrd/interfaces/NetFlow-device/hos
> ts//bytesR
> cvdLoc.rrd) error: illegal attempt to update using time
> 1071779175 when last
> update time is 1071779175 (minimum one second step)
> Dec 18 15:27:12 linuxnm ntop[3442]:   **ERROR** Rejected request from
> address 131.19.176.157 (it previously sent ntop a bad request)
>
> And those messages repeat continuously.  I've also noticed that
> it seems to
> have the IP Address backwards in the log.. It should be 157.176.19.131..
>
> THe ntop server continues to run, and other hosts can connect to
> it.  So my
> question now is twofold:
>
> How do I get it to accept connections from my host again?
> How do I correct the rrd_update errors?
>
> Ideally I'd like to correct the first problem without restarting ntop.
>
> THanks again
>
> Reuben
> _______________________________________________
> Ntop-dev mailing list
> [EMAIL PROTECTED]
> http://listgateway.unipi.it/mailman/listinfo/ntop-dev
>

_______________________________________________
Ntop-dev mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev

Reply via email to