Error Logs...

[hddtecky2k3]

Can anybody tell me how to delete the error messages thrown up on boot?

My machine fails to even reach the log-in screen, and I've been told its due to the drive having no more space to dump the error logs into. Is this correct?

If so, how, upon turning the machine on, can I delete some of the error logs to free up more space?

Thanks in advance

Dan

 

[KenCunningham]

Perhaps you need to boot -s cdrom from the Software disk 1 of 2 CD and mount the / filesystem (there's a faq on how to do this to change the root password, but it amounts to the same thing essentailly), so that you can clear down some of the files, perhaps in /var/adm. Look for large files like messages, wtmpx, sulog etc. These can either be pruned manually using vi or reset using something like cat /dev/null > filename

Hope this helps.

 

[KenCunningham]

Sorry, it's Faq60-1568 and it should be boot cdrom -s not as above. It's Monday, isn't it!

 

[hddtecky2k3]

Sounds good Steve, but I don't actually have the CD's to hand.

If I do 'boot -s', how do you manually mount the hard drive, to allow me to browse for large files?

After I've deleted some of the large files, do I just go back to booting Solaris as normal? Do you need to dis-mount the drive first? If so, what is the command for this?

Thanks Steve

Dan

 

[KenCunningham]

boot -s might work and should mount the necessary drive as part of the process if it does. Do you know whether /var was part of the / filesystem, or stand-alone? If it works, you should be able to delete files and then do a reboot to (hopefully) normal operation.

 

[hddtecky2k3]

Im not sure what /var even means Steve, sorry.

The machine basically tries to boot as if its on a network, so alot of error msgs are to do with no ethernet cable etc.

Once I can get into the machine, I will be re-configuring it as a stand alone machine rather than network based.

We're using it to asses fibre channel hard drives using an array, but each reboot produces masses of errors and clogs up the hard drive

Is /var a directory that hosts error logs then?

 

[KenCunningham]

Yes (to the /var question that is). If you try to boot -s it's my hope that the machine won't try to attach itself to the network and thus you'll be left in single user mode with the chance to delete files if this is what's required.

Incidentally, why do you think my name's Steve??

 

[hddtecky2k3]

You know what, I haven't got the foggiest why I thought you were Steve lol (monday morning) hahah, sorry.

I'll try a boot -s then, see what happens

 

[hddtecky2k3]

Ken,

I've managed to get into some of the system directories, and nullified some of the log sizes to maybe free up some space to help with new log creations.

I did the reboot and nothing changed still hangs at the same place each time.

This is really annoying now, as my project at work is waiting on the fix of this damn machine.

Bizarre thing is it worked fine Friday afternoon, shutdown over the weekend, and now Monday it's decided to balls up

 

[hddtecky2k3]

Upon booting, it appears to struggle at this line:

Uknown sendmail [267]: Unable to qualify my own domain name (Uknown) -- using short name

Does that mean anything?

 

[coffeysm]

No all that means is you need to add hostname.your.domainanme in your /etc/hosts file.

 

[coffeysm]

You should also check /var/adm/*tmp* those files log who is on the system and who logged in. They can grow tremendously. Also if you have BSM enabled check /var/audit those files can get huge. Check /var/crash also that is where crash files get stored also.

 

[KenCunningham]

As Coffeysm says, the sendmail 'problem' is really a red herring, and the advice re other /var files is good. Did you get any further with this?

 

[hddtecky2k3]

We did remove some rather larger files, well, we nullified the size instead of deleting them.

However, we didn't go into as many dir's as mentioned above, so could be worth a try.

Strange thing is, there was a good amount of free space on the disk when we ammended the files mentioned, so could it be something different?

Your help is greatley appreciated guys, just hope we can resolve the issue soon

Dan

 

[KenCunningham]

Can you look at /var/adm/messages to see whether it contains any clues as to what's happening (or not happening) on bootup?

 

[hddtecky2k3]

Im currently making an image of the drive before I look into it further, in case something screws up.

We're on a big learning curve you see, so we're a bit blind.

I'll look at what you suggested and get back to you

Cheers