Precisely.
I don't know if it's really worth it at this point. We know what the
problem is, and have a permanent fix for it. In addition, I'll be adding
an execution of queue_repair.py to qtp-newmodel, just to make sure
things are kept clean.
Kent Busbee wrote:
something like
queue_repair.
something like
queue_repair.py $@ | tee -a /var/log/queue_repair
See response above; Eric Shubert wrote:
> No, it simply sends output to the terminal.
>
> I suppose that a customized version for QTP which would tee off a log
> file automatically would be nice. That would be pretty simple to do wi
Thanks Kent, that's helpful.
I hope to be looking at these in more detail later today. Jake and I
suspect that these permissions are not a problem, but I hope to fix them
one way or another (so there's no message if they're not).
The trigger pipe/file was definitely a problem though, which is
After reading these I checked mine and did have errors. I could not
scroll back very far but did have permissions problems:
checking split locations...
queue/mess/1/11175402 ownership 7794:0, should be qmailq:qmail
fixed, queue/mess/1/11175402 ownership 7794:2108
queue/mess/1/11175195 owner
Jake Vickers wrote:
Lucian Cristian wrote:
I don't have it anymore, but socket file "trigger" from queue/lock was
missing and permissions on some files
Same here on one I fixed for someone this morning. "No such file or
directory: queue/lock/trigger"
I'll look at the last changes in the spe
Lucian Cristian wrote:
I don't have it anymore, but socket file "trigger" from queue/lock was
missing and permissions on some files
Same here on one I fixed for someone this morning. "No such file or
directory: queue/lock/trigger"
I'll look at the last changes in the spec file a little more
No, it simply sends output to the terminal.
I suppose that a customized version for QTP which would tee off a log
file automatically would be nice. That would be pretty simple to do with
a script wrapper. Would anyone like to take a shot at writing a
qtp-queue-repair script that would do this?
Is the queue_repair logged? If so I can forward it to you. Tell me
what file you want.
Eric Shubert wrote:
> Thanks Lucian.
>
> We still don't know for sure how the queues became borked. Nothing in
> that area has changed that we know of.
>
> At any rate, if anyone experiences delayed deliveries
I don't have it anymore, but socket file "trigger" from queue/lock was
missing and permissions on some files
Lucian
Eric Shubert wrote:
Thanks Lucian.
We still don't know for sure how the queues became borked. Nothing in
that area has changed that we know of.
At any rate, if anyone experie
Thanks Lucian.
We still don't know for sure how the queues became borked. Nothing in
that area has changed that we know of.
At any rate, if anyone experiences delayed deliveries after an update,
the thing to do would be to stop qmail and run the queue_repair.py tool.
It would be helpful if
it was a clean shutdown in my case, I don't know what happened, anyway
now it's ok
Regards
Lucian
Eric Shubert wrote:
We're guessing here, but it's possible that qmail didn't terminate
successfully (or cleanly) when the update was actually done.
qtp-newmodel presently simply waits 5 seconds t
We're guessing here, but it's possible that qmail didn't terminate
successfully (or cleanly) when the update was actually done.
qtp-newmodel presently simply waits 5 seconds then displays the result
of qmailctl stat.
Does anyone happen to remember seeing anything other than 'not running',
lik
Maxwell Smart wrote:
Any ideas what caused this yet?
Some suspicions and we're investigating further.
-
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting
Same issue I had.
Lucian Cristian wrote:
> It seems that the problems is solved, there was some file missing and
> some permission problems on queue dir
>
> Regards
> Lucian
>
> Lucian Cristian wrote:
>> Hi
>>
>> thanks for info, I tried it some seconds ago, after I sent the mail
>> to mailing lis
It seems that the problems is solved, there was some file missing and
some permission problems on queue dir
Regards
Lucian
Lucian Cristian wrote:
Hi
thanks for info, I tried it some seconds ago, after I sent the mail to
mailing list occurred to me to test queue repair, and it seems to work
Hi
thanks for info, I tried it some seconds ago, after I sent the mail to
mailing list occurred to me to test queue repair, and it seems to work
it was a qtp-newmodel upgrade and the x64 was a clean install.
the x86 versions seems to lag, I'll test a bit more
Regards
Lucian
Jake Vickers wrot
Any ideas what caused this yet?
Jake Vickers wrote:
> Lucian Cristian wrote:
>> Hi everyone I have problems with the queue on to different systems,
>> the queue will not be processed as soon as possible, there is some
>> lag, if a do a qmailqtl restart the mails will be processed if not I
>> have
Lucian Cristian wrote:
Hi everyone I have problems with the queue on to different systems,
the queue will not be processed as soon as possible, there is some
lag, if a do a qmailqtl restart the mails will be processed if not I
have to wait a random time
I've read about "qmail silly syndrome"
Hi everyone I have problems with the queue on to different systems, the
queue will not be processed as soon as possible, there is some lag, if a
do a qmailqtl restart the mails will be processed if not I have to wait
a random time
I've read about "qmail silly syndrome" is this the problem ?
p
19 matches
Mail list logo
