Hello all
Currently I am working in a live production environment with 100+ Solaris servers . The environment has one DNS server and one SMTP server.
The problem that I am facing since the past 2 months is that the /var/spool/mqueue on my DNS server keeps getting full i.e. mails with name starting with qfr & dfr keeping on gathering up and I have to manually go and delete these mails.
Some sample outputs of these mail files are given below:
It seems that the issue is somewhat related to crons.
Does anyone know how I can get rid of such mails ? I have to empty the /var/spool/mqueue directory every 7-8 hours since the number of mails reaches 50,000 +
I keep having this msg on my SunOS console :
Jun 29 08:57:40 bersimis sendmail: NOQUEUE: low on space (have 0, SMTP-DAEMON needs 101 in /var/spool/mqueue)
I tried to make some space by deleting the files in it, but the msg came back ...
Any tips ?
Thanks (3 Replies)
Hi,
We have all the user account in a home direcory where their mail is stored and retrieved by email clients. We do however have /var/spool/mail with all the user accounts in it as well Our sendmail.cf is configured to use /var/spool/mqueue as the queue so .what is /var/spool/mail being used... (3 Replies)
Hi,
How can i get my mail on either /var/spool/mail or /var/mail?
I use mail and sendmail command to send mail. But everytime I send mail it comes to my outlook inbox and when I check with mail command I get the message "No mail for siba". (Note siba is my user Id.) (2 Replies)
Hello,
I have a bunch of cron jobs in the crontab. For some reason mail from the cron jobs started going to /var/spool/mqueue instead of being sent.
Does anyone know why mail from cron jobs would go to the queue instead of being sent? (9 Replies)
Hi, We have some 2-3 Solaris 9 servers with the following issue.
For every cron job which has email notifications, it is sending the emails, but it create files at /var/spool/clientmqueue/ which has similar contents.
"
V6
T1271362260
K1271362260
N1
P30359
MDeferred: Connection refused... (1 Reply)
Hi,
solaris : 9
can we delete the files from this location /var/spool/clientmqueue . I found around 40K files lying in this location.
Regards (1 Reply)
Hi
My box is running with AIX 6100-06 and Im the root user of this box
My /var gets filled up often to 100%
When I investigate I find that it is the below file which increases rapidly
/var/spool/mail/pdgadmin
I dont know why this file is growing up.
Can any one assist me on this.... (2 Replies)
Hi all,
I have some sort of problem with BIND DNS server my environment as follows.
bash-3.00# cat /etc/release
Solaris 10 6/06 s10s_u2wos_09a SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to... (3 Replies)
Hi guys .
I have a solaris machine serving as a DNS server for my environment. Everytime I go into /var/spool/mqueue , there are an aweful lot of emails with names likes:
qfqB6ChrpL006644.
When I cat the file , I get the following output:
H??Received: from machine.domain.com... (3 Replies)
Hi,
Am trying to configure DNS server and trying to keep the information in /etc/resolv.conf file as:
search server
nameserver 192.168.0.10
when i restart the network service with #service network restart, resolv.conf file is changing as:
nameserver 192.168.0.10
search server -... (5 Replies)
Discussion started by: raosr020
5 Replies
LEARN ABOUT PHP
cron
cron(1M) System Administration Commands cron(1M)NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init.
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5)NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)