Re: {bb} Bogus disk full messages?

[Sean MacGuire <sean@maclawran.ca>]

Elizabeth Schwartz wrote:
> I'm running BB 19c (old, I know, but it seems to work just fine) on servers
> and clients running mostly Solaris 9.
> I've got one machine that started sending bogus disk full messages a few
> days ago (see below)
>
> -the filesystem is not full
> -the filesystem is not out of inodes
> -the directory is owned by the BB user
> -BB is running as the correct user
> -nothing else that I know of has changed on this machine in many months
>
> I don't get the disk full message all the time; it is showing as OK roughly
> half the time, maybe a bit more
> http://enki.gsd.harvard.edu/cgi-bin/bb-hist.sh?HISTFILE=atlas%2Cgsd%2Charvard%2Cedu.disk&ENTRIES=50 
>
>
> I have restarted BB but not rebooted the machine (as it is a production
> Oracle server)
>
> There are a couple of errors in the system log from Tuesday but this 
> problem
> started earlier and the syslog errors have not repeated
>
> > > Oct  3 10:51:03 atlas genunix: [ID 470503 kern.warning] WARNING: 
> > > Sorry, no
>
> swap
> space to grow stack for pid 4846 (bb)
>
> > > Oct  3 10:51:03 atlas last message repeated 4 times
> > > Oct  3 17:11:21 atlas genunix: [ID 470503 kern.warning] WARNING: 
> > > Sorry, no
>
> swap
> space to grow stack for pid 19711 (bbrun)
>
> what else to look at?

Hmmmmm.

Looks like resource exhaustion on the machine (the swap space
error is the clue).  If that happens, it means that random processes
just might stop/not start... and it looks like it's touching the disk
test.

As far as the actual cause, maybe not being able to do stuff in /tmp...
--
Sean MacGuire                                 sean@maclawran.ca

icbm --> 45'31.06N-73'35.19W                    +1 514 996 4638
The best way to predict the future is to invent it. -  Alan Kay
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.