Ad blocker detected: Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker on our website.
I woke up this morning to find my Cacti server practically unresponsive. Upon further investigation, I saw 100+ instances of php.exe running which was consuming ~80% CPU.
When logging onto the server, I could see several of the following messages on the dos cmd.php windows:
ERROR: illegal attempt to update using time 1105711803 when last update time is 1105712103 (minimum one second step)
OK
OK
Content-type: text/html
X-Powered-By: PHP/4.3.10
01/14/2005 06:24:58 AM - POLLER: Poller[0] Maximum runtime of 296 seconds exceeded. Exiting.
Anyways, after restarting IIS, it appears the server and poller is back to normal. Is this the type of problems people have been having with PHP 4.3.10 ?
Last edited by BSOD2600 on Mon Jan 17, 2005 3:17 am, edited 1 time in total.
Crap, well it's not a php 4.3.10 issue. I went back to 4.3.9 and the same thing happened again! Now what can I do to find out why the heck the processes are not closing?
I too, am having this problem. Not so bad, it doesn't seem to happen each cycle, but gradually my process table is filling with php.exe and cactid.exes.
I am running w2k3, iis6, php 5.0.2 (was running 5.0.3, but per our guru's advice, dropped back to 5.0.2. Seems better, but not fixed.), mysql 4.0.20, rrdtool 1.0.48.
did not have this problem with php 4.3.8.
my poller_output table is empty.
I have some errors mentioning re-caching, but that's about it.
There appears to be 4 rows in poller_output (viewed with phpmyadmin):
local_data_id, rrd_name, time, output
I'm going to switch from cmd.php to cactid.exe and see how that does for a while. Odd thing I've already noticed is that it does not create the log, even though I've got it set to in cactid.conf.
Is the log path, basing itself off where the poller lives. Meaning, since cmd.php lives in: C:\Auntie\cacti\, the log path: ././log/cacti.log works fine. But when I'm using cactid, that log path is not valid. If this is the case, is there a global name, like <path_rra> which I can use so the log file is always defaulted to the same location, regardless of which poller is being used?
edit:
Well I tried to use the path: <path_cacti>/log/cacti.log for the log. but it didn't work. Got the following errors when I went to use the system utils -> View Cacti Log File:
Warning: touch(): Unable to create file <path_cacti>/log/cacti.log because Invalid argument in c:\auntie\cacti\utilities.php on line 107
Warning: file(/log/cacti.log): failed to open stream: Invalid argument in c:\auntie\cacti\utilities.php on line 108
Warning: array_reverse(): The argument should be an array in c:\auntie\cacti\utilities.php on line 111
Warning: Invalid argument supplied for foreach() in c:\auntie\cacti\utilities.php on line 116
And what is the interval which you are polling on?
[size=117][i][b]Tony Roman[/b][/i][/size]
[size=84][i]Experience is what causes a person to make new mistakes instead of old ones.[/i][/size]
[size=84][i]There are only 3 way to complete a project: Good, Fast or Cheap, pick two.[/i][/size]
[size=84][i]With age comes wisdom, what you choose to do with it determines whether or not you are wise.[/i][/size]
The following is when there are no errors or extra php processes running:
SYSTEM STATS: Time: 47.9460 s, Method: cmd.php, Processes: 2, Threads: N/A, Hosts: 11, Hosts/Process: 6
Polling every 5 minutes. This problem with extra processes just started 3 days ago, and I don't recall making any system changes, EXCEPT installing PHP 4.3.10. After a day, I went back to 4.3.9. If I type php -v at the commandline, it does say I've got 4.3.9 too.
I think this might be a Win2K3 problem. I got to looking at the number of connections that were made when the server would choke. Turns out there is a shitload! Disable and re-enabling the NIC fixes the connection problem. I also can see that the when this problem is happening, the cmd.php window will get through some clients and then just hang.
All the connections at the time the problem is occuring: