[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: scheduler: unlink(280943-8844)[sch-sch-done]: No such file or directory



On Tue, Aug 29, 2000 at 04:05:51PM +0400, Eugene Crosser wrote:
> Matti,
> 
> I am having a problem right now that *might* be related to the one that
> I complained several times.  I have a great many files in the queue
> directory (and not so many in queue/?/).  I do not have SCHEDULERDIRHASH
> defined in /etc/zmailer.conf.
> 
> In the scheduler log file, I see a great lot of these messages:
>   scheduler: stat(../queue/O/281048-8845): No such file or directory

	there is just one place where that can happen, and if all else
	works just fine, it is telling that there is TA file which is
	located into /O/ subdir, but no matching file in the queue.

> and some these:
>   scheduler: unlink(280943-8844)[sch-sch-done]: No such file or directory

	Removal from the  $POSTOFFICE/transport/ directory is not
	successfull then.  Race somewhere ?  File(s) got moved, but
	that unlink() still gets original input directory reference.

> When I look into the directories, I see that there are no files in
> the subdirectories (say, queue/O/281048-8845) but the files with same
> names are in the queue directory itself (say, queue/281048-8845).
> 
> Scheduling seems to have effectively stopped now.

	Moving all files up from queue and transport subdirs should
	restore sanity -- but which system now had made movings into
	wrong places in the first place ?

> new mailq does not work (mailq: cannot find address of localhost), old
> mailq (that used to work) show insane things: it does not display any
> threads, and summary information is like this:

	hmm..  half-a-dozen things in mailq, and getaddrinfo() are
	causing that connectivity problem.  CVS cured now.
	However the scheduler report is quite consistent with a complete
	failure to schedule :-/

> Kids: 0  Idle:  0  Msgs: -3103  Thrds:   0  Rcpnts:    0  Uptime: 20m6s
> Msgs in 3103 out 0 stored 4294964193 Rcpnts in 3406 out 0 stored 3406 (0)

	The message count has been decrementing in place where it should not..
	And the stored count in unsigned int (32 bits) of some negative value.

> Eugene

-- 
/Matti Aarnio	<mea@nic.funet.fi>