Quoting previous mail from [EMAIL PROTECTED] :
Sent on Mon, Mar 08, 1999 at 08:33:07AM +1100 :
> At 06:24 PM 3/7/99 +0530, Sameer Vijay wrote:
> >Our server had been running qmail-1.02 for quite sometime. Recently, there
> >were few problems encountered. I have no idea whether sysad had any
> >hand in it or not.
> >
> >Problem 1. The remote mails were delievered instantly but the local
> >mails were not at all delivered. as a result we could not get any
> >mails. The logs showed upto 1400 local message nos. and the status
> >line read
> >
> >status: local 10/10 remote 0/20(or 5/20)
> >till the sysad forced qmail to deliever the local messages.
>
> Why not show is some log messages associated with the local delivery
> attempts. We cannot guess what those entries are.
The logs have been deleted. So I am sorry that I cant help much with
that. But the gist is...
o There were absolutely no local deliveries, only queueing up of mails
for local deliveries. The line that I have mentioned came in the
logs when a remote delivery was attempted (which was working fine)
o As there were no local deliveries, there were no lines saying
starting delivery xxx : mesg xxxx to local [EMAIL PROTECTED]
o the machine handles mail for about 2000 users. on a Sun machine with
SunOS 5.6.
Do the numbers (eg.920799649.721670) which come in the log after
'hostname qmail:' hold any significance? If yes, please tell how to
extract info from them and what do they mean?
> >There were once so many mails and the logs were really mounting up so
> >mush so that /var became full. the sysad then removed the log files
> >manually.
> >
> >Problem 2. After a reboot the problem really grew. qmail just couldnt
> >restart. the system logs was full of similar mesg.
> >
> >alert: unable to open(/read) todo/<some no.s> or
> >alert: unable to open(/read) mess/<some.nos> or
> >alert: unable to opendir todo, sleeping...
>
> Please don't sanitize log entries if you want a response. As has been said
> many times on this list - sanitized log messsages often hide the true nature
> of the problem.
In this case, the log file was completely full of such messages. the
no.s etc correspond to the queued mails ( I guess)
I can also add the log from another machine, which attempted to
deliver mail to the above machine (144.16.106.8)
Mar 7 15:10:48 calvin qmail: 920799648.346757 starting delivery 138: msg 241 to
remote [EMAIL PROTECTED]
Mar 7 15:10:48 calvin qmail: 920799648.346901 status: local 0/10 remote 2/20
Mar 7 15:10:49 calvin qmail: 920799649.721365 delivery 138: deferral:
144.16.106.8_failed_after_I_sent_the_message./Remote_host_said:_451_qq_trouble_creating_files_in_queue_(#4.3.0)/
Mar 7 15:10:49 calvin qmail: 920799649.721670 status: local 0/10 remote 0/20
Mar 7 15:17:29 calvin qmail: 920800049.730218 starting delivery 139: msg 241 to
remote [EMAIL PROTECTED]
Mar 7 15:17:29 calvin qmail: 920800049.730522 status: local 0/10 remote 1/20
Mar 7 15:17:29 calvin qmail: 920800049.931927 delivery 139: deferral:
144.16.106.8_failed_after_I_sent_the_message./Remote_host_said:_451_qq_trouble_creating_files_in_queue_(#4.3.0)/
Mar 7 15:17:29 calvin qmail: 920800049.932206 status: local 0/10 remote 0/20
Mar 7 15:37:29 calvin qmail: 920801249.950207 starting delivery 140: msg 241 to
remote [EMAIL PROTECTED]
Mar 7 15:37:29 calvin qmail: 920801249.950532 status: local 0/10 remote 1/20
Mar 7 15:37:30 calvin qmail: 920801250.154062 delivery 140: deferral:
144.16.106.8_failed_after_I_sent_the_message./Remote_host_said:_451_qq_trouble_creating_files_in_queue_(#4.3.0)/
Mar 7 15:37:30 calvin qmail: 920801250.154324 status: local 0/10 remote 0/20
As can be seen from these logs, the recipient machine has having
problem creating files in queue, which along with the fact that qmail
on that machine was unable to open dir(s) mess or todo, suggest that
something is amiss.
Hope that helps.
--
Sameer Vijay - [EMAIL PROTECTED] (Research Engineer)
Dept. of Chemical Engg, IIT Bombay, Mumbai 400076 INDIA.
Fax: +91-22-5796895 (dept), +91-22-5783480 (IITB)
