failure notice

[timryberg]

I have about 60 of these in my from MY SEERVER in my mailbox:



Hi. This is the qmail-send program at centos.transwarphosting.net.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<webmaster@transwarphositing.net>:
Sorry, I couldn't find any host named transwarphositing.net. (#5.1.2)

--- Below this line is a copy of the message.

Return-Path: <webmaster@transwarphosting.net>
Received: (qmail 19357 invoked by uid 0); 20 Jan 2005 23:31:00 -0000
Received: from phpmailer
by localhost.localdomain with local (phpmailer);
Thu, 20 Jan 2005 18:31:00 -0500
Date: Thu, 20 Jan 2005 18:31:00 -0500
To: webmaster@transwarphositing.net
From: NodeWorx Server Manager <webmaster@transwarphosting.net>
Subject: centos.transwarphosting.net:/boot partition 81% alert
Message-ID: <d074de5741f5485790ac36490288be54@localhost.localdo main>
X-Priority: 3
X-Mailer: phpmailer [version 1.65]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="iso-8859-1"

Hi,

This in an automatic informational message to notify you that the /boot
partition on centos.transwarphosting.net has hit the storage partition
threshold set for your server. The /boot partition is 81% full at the time
of this e-mail's creation.

Thanks,

Your NodeWorx Server Manager


I continue to get them every five minutes. There is nothing wrong with Transwarphosting.net, as edivenced by the fact that these are being delivered to webmaster at transwarphosting.net

The only thing I've done is try to install the frontPage server extentions yesterday and that's not in the boot partition (as far as I know) Any ideas?

Here are the contents of /boot



[root@centos boot]# dir
config-2.4.21-15.0.4.EL System.map-2.4.21-20.EL.c0
config-2.4.21-15.0.4.ELsmp System.map-2.4.21-20.EL.c0smp
config-2.4.21-20.0.1.EL System.map-2.4.21-27.0.1.EL
config-2.4.21-20.0.1.ELsmp System.map-2.4.21-27.0.1.ELsmp
config-2.4.21-20.EL.c0 System.map-2.4.21-27.0.2.EL
config-2.4.21-20.EL.c0smp System.map-2.4.21-27.0.2.ELsmp
config-2.4.21-27.0.1.EL System.map-2.4.21-27.EL
config-2.4.21-27.0.1.ELsmp System.map-2.4.21-27.ELsmp
config-2.4.21-27.0.2.EL System.map-2.4.21-9.0.1.EL.c0
config-2.4.21-27.0.2.ELsmp System.map-2.4.21-9.0.1.EL.c0smp
config-2.4.21-27.EL vmlinux-2.4.21-15.0.4.EL
config-2.4.21-27.ELsmp vmlinux-2.4.21-15.0.4.ELsmp
config-2.4.21-9.0.1.EL.c0 vmlinux-2.4.21-20.0.1.EL
config-2.4.21-9.0.1.EL.c0smp vmlinux-2.4.21-20.0.1.ELsmp
grub vmlinux-2.4.21-20.EL.c0
initrd-2.4.21-15.0.4.EL.img vmlinux-2.4.21-20.EL.c0smp
initrd-2.4.21-15.0.4.ELsmp.img vmlinux-2.4.21-27.0.1.EL
initrd-2.4.21-20.0.1.EL.img vmlinux-2.4.21-27.0.1.ELsmp
initrd-2.4.21-20.0.1.ELsmp.img vmlinux-2.4.21-27.0.2.EL
initrd-2.4.21-20.EL.c0.img vmlinux-2.4.21-27.0.2.ELsmp
initrd-2.4.21-20.EL.c0smp.img vmlinux-2.4.21-27.EL
initrd-2.4.21-27.0.1.EL.img vmlinux-2.4.21-27.ELsmp
initrd-2.4.21-27.0.1.ELsmp.img vmlinux-2.4.21-9.0.1.EL.c0
initrd-2.4.21-27.0.2.EL.img vmlinux-2.4.21-9.0.1.EL.c0smp
initrd-2.4.21-27.0.2.ELsmp.img vmlinuz-2.4.21-15.0.4.EL
initrd-2.4.21-27.EL.img vmlinuz-2.4.21-15.0.4.ELsmp
initrd-2.4.21-27.ELsmp.img vmlinuz-2.4.21-20.0.1.EL
initrd-2.4.21-9.0.1.EL.c0.img vmlinuz-2.4.21-20.0.1.ELsmp
initrd-2.4.21-9.0.1.EL.c0smp.img vmlinuz-2.4.21-20.EL.c0
kernel.h vmlinuz-2.4.21-20.EL.c0smp
lost+found vmlinuz-2.4.21-27.0.1.EL
message vmlinuz-2.4.21-27.0.1.ELsmp
message.ja vmlinuz-2.4.21-27.0.2.EL
System.map vmlinuz-2.4.21-27.0.2.ELsmp
System.map-2.4.21-15.0.4.EL vmlinuz-2.4.21-27.EL
System.map-2.4.21-15.0.4.ELsmp vmlinuz-2.4.21-27.ELsmp
System.map-2.4.21-20.0.1.EL vmlinuz-2.4.21-9.0.1.EL.c0
System.map-2.4.21-20.0.1.ELsmp vmlinuz-2.4.21-9.0.1.EL.c0smp
[root@centos boot]#

[IWorx-Paul]

Well, the reason the message is bouncing is because the domain is misspelled:

transwarphositing.net

That's probably just mistyped in the Server Setup section of NodeWorx.

As for the boot partition being 80% full, perhaps a new kernel was installed just recently?

[timryberg]

after taking a look around I found that I got the following updates last night"

1 kernel 2.4.21-27.0.2.EL os applied
2 kernel-smp 2.4.21-27.0.2.EL os applied
3 krb5-devel 1.2.7-38 os applied
4 krb5-libs 1.2.7-38 os applied
5 krb5-workstation 1.2.7-38 os applied

which apparently started this. I just rebooted the server to take advantage of the kernal upgrade listed here. I guess the solution to part of my problem is th delete some of the /boot directory. The question is what is safe to delete. I know grub boot loader detects all available kernals. If the old ones are just deleted whill that cause problems?

[timryberg]

Well, the reason the message is bouncing is because the domain is misspelled:

transwarphositing.net

That's probably just mistyped in the Server Setup section of NodeWorx.




Yes, I just fixed it now; dang I didn't see it.



As for the boot partition being 80% full, perhaps a new kernel was installed just recently?

Yes, last night, causing this problem. Is it safe to delete older versions of files located in the /boot directory?

Tim