Sys out of space 1

[Juandaman81]

Hello All,

I need some guidance,

We have 180 netware 6.5 servers at one of our clients, it seems that in the last 2\3 weeks we've had 6-7 servers reporting their out of disk space. now with these stores i have used the nssmu utility and expanded the pool (only by 100mb, not sure if i was right to or not) the server's have been running for 3 years, is there some house keeping i need to do, anyone point me in the direction of a log file or something that can be cleared. or is expanding the sys pool the way forward? if so how far can i expand it without causing problems? bearing in mind i think i'd have to do it manually 180 times


any input would be appreciated!

If you try to fail, and succeed, which have you done?

 

[blister911]

One thought (and my terminology may be incorrect). Where are your print jobs spooling? I think typically people have been putting them on the SYS volume. It may be that you are getting some really big print jobs filling up the servers.

 

[Juandaman81]

All print queues point to vol1:

If you try to fail, and succeed, which have you done?

 

[marvhuffaker]

How big are the SYS volumes in the first place?

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[pagy]

Are they Dell servers with Dell openmanage agents running on them?? In particular the array manager?? If so check the MLIBDBG.TXT file in sys:\system\dell. I've had this file grow to over 2 gig in size and on each occassion there was nothing wrong with the arrays, just loads of informational messages being logged. Make sure there is nothing wrong with the arrays on these servers by using openmanage and then I had to unload arraymanager on the servers and rem it out of the autoexec.ncf

Paul

MCSE 2003

"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[lgarner]

Look for log files. NW6.5 has the portal running Apache, and access logs are on by default, as I recall. They will grow over time.

 

[Juandaman81]

My "technical junior" has had what is known as "a beast" at 3 different sites he has expanded the sys pool to the maximum amount of disk space left (33gb)... as this is the sys pool\volume what will happen next? will i encounter problems with sys being this size? I believe the pool can't be "shrunk" but because it's sys - a simple delete and re-create i dont think is an option.

If you try to fail, and succeed, which have you done?