BETA6 kern.maxfiles messages

[freebsd]

Oh hold on, one more thing is mysql is running also, and it locked up on the 
same day of these messages now that I remember.  I'm guessing mysql is the 
culprit.  I hadn't rebuilt it from ports after upgrading from 5.2.1, and 
after it locked up I rebuilt it and haven't had it lock up since.

Chris

----- Original Message ----- 
From: "freebsd" <freebsd at paymentonline.net>
To: <freebsd-current at freebsd.org>
Sent: Tuesday, October 05, 2004 11:04 PM
Subject: BETA6 kern.maxfiles messages


>
> I'm suspicious someone was trying to probe or dos this server, but if 
> there is some other possible explanation, and since I have only seen this 
> on a 5.3 BETA box I thought I would post it here.  It looks to me like 
> someone was trying to do a small dos attack perhaps?
>
> Today I had these messages in dmesg.today:
>
> kern.maxfiles limit exceeded by uid 70, please see tuning(7).
> kern.maxfiles limit exceeded by uid 88, please see tuning(7).
> ......................
>
> The offending processes are:
> # ps 88
>  PID  TT  STAT      TIME COMMAND
>   88  ??  IL     0:00.00 [nfsiod 3]
> # ps 70
>  PID  TT  STAT      TIME COMMAND
>   70  ??  WL     0:08.60 [swi3: cambio]
>
> This is what kern.maxfiles looks like under normal operation.  This server 
> doesn't vary that much in traffic and these numbers shouldn't go up or 
> down too much.  I have apache/mod_perl and postgresql running and that is 
> about it.  Maybe a little bit of variation in maxfiles is normal, but I 
> can't think of what would open up almost 12,000 extra files.
>
> # sysctl kern.maxfiles
> kern.maxfiles: 12328
> # sysctl kern.openfiles
> kern.openfiles: 492
>
>
>
>
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>