Hi,
The main problem here is the access via NFS.
Used the local disks.
bye
UK
Search found 24 matches
- Thu Sep 29, 2011 2:41 am
- Forum: Help: Linux/Unix Specific
- Topic: Bad poller performance on VM
- Replies: 2
- Views: 616
- Mon Apr 18, 2011 2:40 am
- Forum: Help: Linux/Unix Specific
- Topic: ICMP Latency monitoring
- Replies: 2
- Views: 1658
Re: ICMP Latency monitoring
trying times without the "Downed Device Detection" selection
bye
bye
- Fri Aug 20, 2010 2:53 pm
- Forum: Help: Linux/Unix Specific
- Topic: reproducible for you (poller_interval)
- Replies: 8
- Views: 3939
Well you provided half the information i requested anyway. Make sure your rrdfiles are on separate physical disk from the database. TheWitness They are on different hard drives. mysql/OS Centos5.5 Raid1 2x149GB/15K ext3 cacti/rra Raid1 2x149GB/15k ext4 (defaults,noatime,nodiratime,data=writeback,co...
- Thu Aug 19, 2010 8:00 am
- Forum: Help: Linux/Unix Specific
- Topic: reproducible for you (poller_interval)
- Replies: 8
- Views: 3939
TheWitness wrote:How big is this system? How about a quick top screenshot and aCode: Select all
du -hs rra
Code: Select all
2.5G
- Thu Aug 19, 2010 3:51 am
- Forum: Help: Linux/Unix Specific
- Topic: reproducible for you (poller_interval)
- Replies: 8
- Views: 3939
Please show index from poller_item; to find out, which indexes are defined to your poller_item table R. Hi, here are the output. mysql> show index from poller_item; +-------------+------------+---------------+--------------+---------------+-----------+-------------+----------+--------+------+------...
- Tue Aug 17, 2010 10:01 am
- Forum: Help: Linux/Unix Specific
- Topic: reproducible for you (poller_interval)
- Replies: 8
- Views: 3939
Re: reproducible for you (poller_interval)
Hi, the source of the problem I could find. The high timeout value of the spine process are due to two mysql queries and query6 query7 caused. You can find both of these queries in the source code of spine (poller.c). query6="UPDATE poller_item SET rrd_next_step=rrd_next_step-300 WHERE host_id=...
- Fri Jul 30, 2010 4:33 am
- Forum: Help: Linux/Unix Specific
- Topic: spine appears slower from 0.8.7d to 0.8.7g
- Replies: 8
- Views: 2576
Re: spine appears slower from 0.8.7d to 0.8.7g
Hallo,
have the same observation, go back to spine-0.8.7e.
bye
have the same observation, go back to spine-0.8.7e.
bye
- Sat Feb 14, 2009 5:38 am
- Forum: Help: Linux/Unix Specific
- Topic: problem after upgrading to cacti 0.8.7c and spine 0.8.7c
- Replies: 11
- Views: 3510
- Thu May 15, 2008 10:58 am
- Forum: Help: Linux/Unix Specific
- Topic: reproducible for you (poller_interval)
- Replies: 8
- Views: 3939
reproducible for you (poller_interval)
Hallo, after alterations of the cacti-settings,increased itself powerfully the CPU-Load and poller-runtime. I found the settings value which produced this behavior. It is the „poller_intervall“ field. Here are my Testresults: System: cacti-0.8.7b with fc8 Method:spine Processes:2 Threads:4 Hosts:715...
- Tue Mar 04, 2008 6:35 am
- Forum: Help: Linux/Unix Specific
- Topic: Advanced ping issue
- Replies: 6
- Views: 2896
- Mon Dec 10, 2007 12:44 pm
- Forum: Help: Linux/Unix Specific
- Topic: Batch load of the complete configuration
- Replies: 9
- Views: 2131
- Mon Nov 26, 2007 3:05 am
- Forum: Help: Linux/Unix Specific
- Topic: Find Timed Out Error
- Replies: 1
- Views: 1106
- Wed Oct 31, 2007 7:07 am
- Forum: Help: Linux/Unix Specific
- Topic: Find Timed Out Error
- Replies: 1
- Views: 1106
Find Timed Out Error
Hallo, how can I find the "Timed Out" mistake? SPINE: Poller[0] ERROR: Spine Timed Out While Processing Hosts Internal SPINE: Poller[0] ERROR: Spine Timed Out While Processing Hosts Internal SPINE: Poller[0] Time: 294.0033 s, Threads: 4, Hosts: 348 SPINE: Poller[0] Time: 294.0018 s, Thread...
- Thu Mar 23, 2006 7:16 am
- Forum: Scripts and Templates
- Topic: EDIT: Advanced Ping Template Version 1.3 for Cacti 0.8.6g
- Replies: 527
- Views: 802331
hostname tcp:192.168.1.1
Hallo,
if that hostname like tcp:192.168.1.1 the script ss_fping.php not work correct.
That patch solve this problem.
bye uk
if that hostname like tcp:192.168.1.1 the script ss_fping.php not work correct.
That patch solve this problem.
bye uk
- Wed Feb 01, 2006 10:25 am
- Forum: Help: Linux/Unix Specific
- Topic: cactid error snmp_port
- Replies: 0
- Views: 524
cactid error snmp_port
Hallo,
hosts with snmp_port not equal UDP/161 worked not exact.
The snmp_session from cactid starts always with tarrget port 161.
my configuration cacti-0.8.6h/cacti-cactid-0.8.6g
bye uk
hosts with snmp_port not equal UDP/161 worked not exact.
The snmp_session from cactid starts always with tarrget port 161.
my configuration cacti-0.8.6h/cacti-cactid-0.8.6g
bye uk