That usually happens when the system itself runs out of memory. You can check to see how close that is to happening by typing "free" at the command prompt. If you have a RAM quota, that may also be why it happened as you might have exceeded your allotment.
Yep, looks like the system you're on is low on memory - the free memory is only 45240 which is bad, though there should have been enough swap to fall back on to prevent problems.
Yep, looks like the system you're on is low on memory - the free memory is only 45240 which is bad, though there should have been enough swap to fall back on to prevent problems.
Actually it's probably not low ram at all. Note the "cached" number. That's the amount of ram used for caching files. Modern systems often do this in order to minimize disk hits, because accessing disk is a slow operation. Caching lets you boost performance by avoiding unnecessary disk i/o. When more ram is needed, cached stuff gets released.
Having said that, 7g of cached data is a lot of cached data. I'm guessing someone is using the hell out of that system, squeezing as much ram for whatever it is they're doing, which suggests to me they'd likely have an interest in capping your ram, if possible.
Like I said, talk to the admin…he'll know more about your specific situation that we will.
No, this means that it's a linux system with no (or not enough) adjustments in sysctl.conf. Linux caching system by default doesn't swap/free even a lone byte unless it's required by another process. Having a HUGE amount taken by caches is completely normal. The compiler crashes because (according to output of ulimit -a) the account is limited to 32 MB of virtual memory for everything to share.
this mean someone has a process running at like 99%?
The amount of CPU used isn't really what I'm talking about, although indeed that may also be happening.
Basically I'm explaining the probable reason you have a memory limit.
It doesn't really matter what the cpu utilization is. Your problem is a memory limit.
I am making the guess that your admin wants to limit your ram because he does something that uses a lot of ram for disk caching. But this is only a guess. You need to talk to you admin to know if you can get more memory. Or you need to use less memory.
ianshirm@evileye:~/rommud/src$ make
gcc -O -g3 -Wall -DIMC -DIMCROM -c -o obj/act_comm.o act_comm.c
cc1: out of memory allocating 4064 bytes after a total of 4583424 bytes
make: *** [obj/act_comm.o] Error 1
any idea why?
-Xrak