Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 1074 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

too much memory for a single process

DerChris
[:S]   

Too much memory for a single process:
33740 kb for /usr/local/bin/fwlogwatch -S -D -d -f /var/log/kernel-20020813.gz -P n -b -m 5 -t -e -n -N -p
root      8284 78.2 17.0 33740 32708 ?       RN   00:14   1:51 /usr/local/bin/fwlogwatch -S -D -d -f /var/log/kernel-20020813.gz -P n -b -m 5 -t -e -n -N -p

Does anyone now, what that means?

Also the console constantly shows the message:
Read on closed filehandle (KLFIFO) at /usr/sbin/psd-watch.pl line 180
 
 [size="1"][ 13 August 2002, 19:27: Message edited by: f3@Rl3SS ][/size]


This thread was automatically locked due to age.
Parents
  • 0
    PS: restarting or stippoing the PSD didn't help anything.   [:(]
  • 0 in reply to DerChris
    I get the same thing in ASL 3.2x when trying to view Connection Tracking stats. Too much data for the CGI script to crunch and it dies.

    Here's what I was just about to post myself when I saw your post:

    Recently, during a peak day - I've attempted to view a connection tracking log so I can track down some users who have been connecting places they shouldn't be. 

    Problem is - using "connection tracking" in ASL 3.2x usually times out - with the e-mail error msg. arriving shortly after consisting of:

    [WAR 102] Too much memory for a single process - please check(2 times) F:/tmp/selfmonitoring.22223.tmp

    Seems like the only other way to view this is via the Network reporting, and it taint at all pretty. 

    Any thoughts on why this was designed to only display a limited amount of tracked connections?

    Thx,
    -Rick
Reply Children
No Data