On Monday, May 7, 2007 at 11:27:50 -0400, Daniel Ouellet wrote: >Maurice Janssen wrote: >>On Monday, May 7, 2007 at 03:11:41 -0400, Daniel Ouellet wrote: >>>Every time, I process the logs with webalizer, no problem what so ever. >>>Then a few customers wants the awstats version. So, I process that as >>>well, however it's also processing multiple logs, but when the awstats >>>PERL stuff kicks in, it does get the resources to the roof and badly so, >>>that so far it had the impact of freezing the server as a results of this. >>> >>>Now, why PERL would do this, I have no clue, but it does anyway in the >>>usage done by awstats. >>> >>>So far I reproduce this 5 times, so it's pretty consistent. >>> >>>What may cause this, I do not know more, but look like when PERL needs >>>to process huge amount of data, it end up affecting the server in ways >>>to make it crash/freeze. >> >>I don't think that Perl is the problem. Other programs would probably >>also be able to crash the machine, if the load is high enough. > >So far 5x it's always happen with PERL kicking in and starting the load.
Does it survive 'make build' or orther disk/cpu/mem intensive task? >>It could be a bug in the sparc64 port or bad RAM or some other hardware >>related problem. I've seen some strange behaviour [1] with sparc64 as >>well, but I'm not sure wether this is due to a bug. > >This is AMD64 Sorry, for some reason sparc64 was in my mind. Maurice
