check_snmp_int store data for 215 ROW limit?

[Jacker W]

(1)
check_snmp_int info with performance log:

[SERVICEPERFDATA]       1207799107      localhost       traffic_bce1
 0.086   0.102   OK : bce1:UP (7.3Kbps/0.2Kbps): 1 UP
'bce1_in_bps'=7304bps;100000;;0;1000000000
'bce1_in_bps'=208bps;100000;;0;1000000000

check result with store data file:
#wc -l tmp_Nagios_int.127.0.0.1.bce1
    213 tmp_Nagios_int.127.0.0.1.bce1

(2)
check_snmp_int info with performance log:

[SERVICEPERFDATA]       1207799407      localhost       traffic_bce1
 0.086   0.144   UNKOWN : bce1:UP !!Unable to write file
(7.3Kbps/0.1Kbps): 1 UP    'bce1_in_bps'=7296bps;100000;;0;1000000000
'bce1_in_bps'=112bps;100000;;0;1000000000


check result with store data file:
#wc -l tmp_Nagios_int.127.0.0.1.bce1
    214 tmp_Nagios_int.127.0.0.1.bce1

(3)
Now,Nagios Mainpage error info:
traffic_bce1  UNKNOWN 04-10-2008 11:52:05 0d 0h 2m 53s 3/4 UNKOWN :
bce1:UP !!Unable to write file (7.2Kbps/0.1Kbps): 1 UP

(4)
Now,check result all fail for check_snmp_int!

[SERVICEPERFDATA]       1207800487      localhost       traffic_bce1
 0.086   0.232   UNKOWN : bce1:UP !!Unable to write file  No usable
data on file (215 rows) : 1 UP


but snmpd process still normally and i am delete old
tmp_Nagios_int.xxx file,check_snmp_int retry touch new snmp store file
get back normally again.

why tmp_Nagios_int.xxx exceed 214 row get that error info?and i can
unset this limit?

anyone can help me solve that problem?thx for reply......

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Nagiosplug-help mailing list
Nagiosplug-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f at public.gmane.org
https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
::: Please include plugins version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null