Solaris

Do you need sendmail on this machine since its mail delivered to root and postmaster from local host and isnt obviously working. If this isnt an MTA mailserver/relay then stop the deamon. I know its installed and started by default..

The main issue seems to me there is a process (or more) constantly trying to send mails to a local mail server (likely sendmail) but the latter is not running. The fix would be then to start the mailserver daemon, not to stop it.

Hi ,

thanks for your update.
[CODE]

Code:

1)
root $pwd
/var/crash/DBSERVER
root $ls -ltr
total 2
-rw-r--r--   1 root     root           2 Jun 30  2007 bounds
root $cat bounds
2

2)
root $du -sh * |sort -rn |head
 936K   core
 623M   root
 208K   tmp
 189K   TT_DB
  78M   etc
  75M   kernel
  62K   lost+found
  58K   devices
  57M   jdk
  52G   oratest

latest update from /var/log 
root $pwd
/var/log
DBSERVER@root $ls -ltr
total 2624816
-rwxrwxrwx   1 root     sys            0 Oct 17  2005 authlog
-rwxrwxrwx   1 root     other        254 Oct 17  2005 sysidconfig.log
-rw-r--r--   1 oradb   dba        23212 Feb 17 09:44 syslog_last_100_lines
-rwxrwxrwx   1 root     sys      1343205902 Feb 20 11:15 syslog

need your suggestion
Regards

First of all try to use

Code:

du -sk *

not "h" h is human readable so the ordering is not good as you can see 52 G Bytes is on the bottom. What is in oratest directory, check it, try to compress all of the old logs with tar and then gunzip, not the latest one.
Check debug level, be sure its in error in production env. And then check errors, exceptions in logs especially in the logs under oratest.

check sendmail process with

Code:

ps -ef | grep -i sendmail

then the process details with

Code:

pargs PID

Hi Jlliagre,

Code:

The main issue seems to me there is a processe (or more) constantly trying to send mails to a local mail server (likely sendmail) but the latter is not running. The fix would be then to start the mailserver daemon, not to stop it.

can we stop the process which is trying to sendmails to localserver if yes , how can we find and stop that particular process so that other process will not get affected.

Regards

Hi,

Code:

root $du -sk * |sort -rn |head
4496236787      proc
54248518       oratest
53829376        oraprod
49589198        oldddb
48127146        oravis
40591308        oradev
25036669        ora_stag
 2333210 var
 2239583 usr
 1378185 opt

proc size seems to be very big,

size is growing for syslog
root $ls -ltr
total 3904464
-rwxrwxrwx 1 root sys 0 Oct 17 2005 authlog
-rwxrwxrwx 1 root other 254 Oct 17 2005 sysidconfig.log
-rw-r--r-- 1 oraprod dba 23212 Feb 17 09:44 syslog_last_100_lines
-rwxrwxrwx 1 root sys 1998068399 Feb 22 14:31 syslog


please advice me .

Regards

ok i will just talk about general debugging. Check what causes Proc size to be very large, any log there which is in debug or finest level? If its so then second step check what causes too much logs, then third step search for any exception or error.
You should be debugging carefully and having good control of which processes runs in the system.
check running processes with

Code:

ps -ef

or cpu, mem usage with "prstat". grep errors, warnings or exceptions. If you dont know what log to check then type something general, just an example:

Code:

find . -type f -name "*log" -print | xargs grep -i error

maybe sendmail will not give any error after you start it?and queued processes will be completed

---------- Post updated at 09:47 PM ---------- Previous update was at 08:13 PM ----------

I've found something could be very usefull regarding to your sendmail:

You can test connecting to sendmail locally by issuing the command

Code:

telnet localhost 25

Note that we are not actually telnetting but attempting to establish a connection on port 25, which is the port mail transfer agents listen on for incoming connections.

If you get something like the following then you were successfully able to connect. To disconnect from sendmail type "quit" and hit enter.

Code:

Connected to localhost.
Escape character is '^]'.
220 laptop.electrictoolbox.com ESMTP Sendmail 8.12.8/8.12.8; Sun, 30 Nov 2003 13:19:45 +1300

If you could not connect then you'll see something like the following instead. If you get this then you probably don't have sendmail running, or the appropriate entry in your inetd or xinetd settings, depending on how your machine is configured. Fixing this sort of problem is not within the scope of this article.

Code:

Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused

Whether attempting to connect to a local or remote server you will get the same sort of result, either the connection will be refused or you will be greeted by the mail server. To allow access to incoming remote connections, you need to modify the sendmail configuration.

There are two ways to modify sendmail's configuration file. The sendmail.cf file contains all the instructions sendmail needs to run as you intend it to. It is generated automatically from the sendmail.mc file, which is a much easier to read and understand configuration file. Whereever possible you should always modify the snedmail.mc file rather than the sendmail.cf file. However, the are circumstances when someone has changed the sendmail.cf file manually and therefore you need to edit that again to prevent overwriting their changes.

sendmail.cf
To modify sendmail to accept remote connections in the sendmail.cf file, comment out (or delete) the following line:

Code:

O DaemonPortOptions=Port=smtp,Addr=127.0.0.1, Name=MTA

The commented out version of this line would then look like so:

Code:

#O DaemonPortOptions=Port=smtp,Addr=127.0.0.1, Name=MTA

Restart sendmail after doing this and you should now be able to connect to sendmail from a remote machine. If you commented out the line rather than deleted it you are then able to easily revert back to your previous configuration.

sendmail.mc
The preferred option is to edit the sendmail.mc file instead. It's always a good idea to make a backup copy of the sendmail.cf file though in case something goes wrong and there had been changes made to that file that are not in the sendmail.mc file.

As with the sendmail.cf file you need to comment out (or delete) the same option. In the sendmail.mc file this looks like so:

DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')

After commenting out the line it will now look like so:

dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')

You now need to compile this file into a new sendmail.cf file by issuing the following command:

m4 sendmail.mc > sendmail.cf

and then restarting sendmail. Remember it's important to make a backup copy of the sendmail.cf file first so you can revert back to it if sendmail stops working like it did before.