• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2138
  • Last Modified:

Clearing Inodes up - Sendmail not working.

I am having a problem with my sendmail application. For some time now my emails have not been sending from my Linux 7.3 Red hat Box. I traced down the problem and apparently it's happening because my I nodes are full and there is no available space. upon doing a df -i I get the following output:

Filesystem            Inodes   IUsed   IFree IUse% Mounted on
/dev/hda6              98392   21326   77066   22% /
/dev/hda1              12048      52   11996    1% /boot
/dev/hda5            1460160   30861 1429299    3% /home
none                   80337       1   80336    1% /dev/shm
/dev/hda2            3178496   77115 3101381    3% /usr
/dev/hda7              66264    3728   62536    6% /var


and "df -a" produces:

Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hda6               381139    133198    228263  37% /
none                         0         0         0   -  /proc
usbdevfs                     0         0         0   -  /proc/bus/usb
/dev/hda1                46636     18193     26035  42% /boot
none                         0         0         0   -  /dev/pts
/dev/hda5             11495900   1659772   9252168  16% /home
none                    321348         0    321348   0% /dev/shm
/dev/hda2             24991736   1170656  22551544   5% /usr
/dev/hda7               256667    256667         0 100% /var

As you can see hda7 is full and so this is causing the problem.

upong checking the maillogs i found the following error:

Nov  5 05:59:29 internal sendmail[17464]: kA35GC810968: to=kelly_wallace@cox.net, ctladdr=apache (48/48), delay=2+05:43:17, xdelay=00:04:00, mailer=esmtp, pri=10200317, relay=mx.west.cox.net. [68.6.19.3], dsn=4.0.0, stat=Deferred: Connection timed out with mx.west.cox.net.
Nov  5 06:00:00 internal sendmail[25583]: kA5B00R25583: from=root, size=265, class=0, nrcpts=1, relay=root@localhost
Nov  5 06:00:00 internal sendmail[25583]: kA5B00R25583: SYSERR(root): Error writing control file ./tfkA5B00R25583: No space left on device


As you can see on the very last night it says "No Space left on device"

Addiotionally when typing "sendmail"  on my box I get the following error: "Can't create a transcript file no space left on device".



So my question ultimately is, How do I free space up from this area?? What could I delete to make some space up I do not want to cause any problems by deleteing something that the system uses.

Best regards,
Caragol.
0
caragol
Asked:
caragol
  • 3
  • 3
1 Solution
 
ygouthamCommented:
you can look at /var/log and remove all old log files to a safer area or some other partition which has some free space.  check also /var/ftp/pub to see if anything can be moved out from there as well.
0
 
ygouthamCommented:
mails would not work if the system is not able to write to the log file.  you need space in /var/log area and therefore the error.
0
 
caragolAuthor Commented:
Yep I started deleting some stuff yesterday from the logs. Also can I delete these type of files  ./tfkA5B00R25583 created by the mail or will I screw something up??
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
caragolAuthor Commented:
Also can laslog be deleted? this file is huuuge.
I tried doing a cat on it but forget about it, it's too big for that.
0
 
ygouthamCommented:
if you are not sure about the logs, try moving it to some other computer where you can look at it in leisure.  the type of files tfkxxxxxxxxxxx should be residing somewhere in /var/spool/mail which indicates that it is a unsent message.  check with a

head tfkxxxxxxxxxxxxxxx | more

and see what the contents are before taking such actions.

it seems that the system is performing a loop function in one of the routine either in crontab or in one of cron.hourly / cron.daily /etc.

see through the log to understand such weird behaviour of system.  deleting files is an unintelligent option.  find out the cause of such activity and try eliminating them.  better safe than sorry ;-)
0
 
caragolAuthor Commented:
Thanks for your input on the matter ygoutham! : 0
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now