I have an anoying problem.
In my qmail-send-logfile I see every some minuntes:
warning: unable to stat mess/0/0
warning: unable to stat mess/1/1
...
warning: unable to stat mess/22/22
No, I have not tampered the queue by hand - I had a hanging send process
a while ago and killed the server - perhaps that was an issue.
I also ran queue-repair, it does not report any problems and I also cant
find any orphaned files in todo/ or simlar that match these patterns.
Its very suspicious that its exectly "mess/x/x" - so first and second
name are the same....
I updated from "old" qmail to netqmail a while ago and reused the old
queue dir - might this be an issue ? Any ideas to fix the queue ??
Oliver
--
Diese Nachricht wurde digital unterschrieben
oliwel's public key: http://www.oliwel.de/oliwel.crt
Basiszertifikat: http://www.ldv.ei.tum.de/page72
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de
| I have an anoying problem.
| In my qmail-send-logfile I see every some minuntes:
|
| warning: unable to stat mess/0/0
| warning: unable to stat mess/1/1
| ...
| warning: unable to stat mess/22/22
|
| No, I have not tampered the queue by hand - I had a hanging send
| process a while ago and killed the server - perhaps that was an
| issue.
It shouldn't be.
| I updated from "old" qmail to netqmail a while ago and reused the
| old queue dir - might this be an issue ?
You haven't changed conf-split between the two installations, I
presume?
And what is the result of find /var/qmail/queue -name 0 -print ?
- Harald
> | I updated from "old" qmail to netqmail a while ago and reused the
> | old queue dir - might this be an issue ?
>
> You haven't changed conf-split between the two installations, I
> presume?
Not that I know, I reused the old configfiles and didnt set any
non-default options - if you tell me where I can find the setting used I
will have a look
> And what is the result of find /var/qmail/queue -name 0 -print ?
/var/qmail/queue/info/0
/var/qmail/queue/mess/0
/var/qmail/queue/remote/0
/var/qmail/queue/local/0
/var/qmail/queue/todo/0
/var/qmail/queue/intd/0
Same for everything else between 1 and 22
| Hi Harald,
|
| > | I updated from "old" qmail to netqmail a while ago and reused the
| > | old queue dir - might this be an issue ?
| >
| > You haven't changed conf-split between the two installations, I
| > presume?
|
| Not that I know, I reused the old configfiles and didnt set any
| non-default options - if you tell me where I can find the setting
| used I will have a look
In the source code. But see below.
| > And what is the result of find /var/qmail/queue -name 0 -print ?
|
| /var/qmail/queue/info/0
| /var/qmail/queue/mess/0
| /var/qmail/queue/remote/0
| /var/qmail/queue/local/0
| /var/qmail/queue/todo/0
| /var/qmail/queue/intd/0
|
| Same for everything else between 1 and 22
Methinks you had the big-todo patch applied to your old qmail
installation, but not the new one.
If you don't want the patch, just rmdir the extra directories 0,...,22
in todo/ and intd/. If you do want it, heed the warning that comes
with the patch.
- Harald
I hope the queue was empty. :D
| > seems as you were right ;)
| > rm'ing the both dirs did the trick.
| >
|
| I hope the queue was empty. :D
More to the point, one hopes the queue contained no unprocessed
messages when the qmail installation was upgraded.
I did specify rmdir, which would fail if there were any.
- Harald
:)
>
> I did specify rmdir, which would fail if there were any.
You know how hard instructions are to follow when someone does not
understand the reasoning behind them.