Well, sometimes swag's are good!! That worked!! a queue_repair.py command reported that /var/qmail/queue/lock/trigger was not found.
Based on that I ran a queue_repair.py -r Thanks for all the help!! I can now turn off my cron that restarted send every 5 minutes :) Fortunately none of my clients were impacted. Not sure which problem was the culprit, but there were several things it fixed as follows. checking files... queue/lock/trigger missing queue/lock/trigger ownership 0:0, should be qmails:qmail fixed, queue/lock/trigger ownership 7796:2108 queue/lock/trigger is mode 644, should be 622 changed queue/lock/trigger mode to 622 checking queue/mess files... checking split locations... queue/todo/4260285 ownership 7794:89, should be qmailq:qmail fixed, queue/todo/4260285 ownership 7794:2108 queue/todo/4260461 ownership 7794:89, should be qmailq:qmail fixed, queue/todo/4260461 ownership 7794:2108 queue/todo/4260538 ownership 7794:89, should be qmailq:qmail fixed, queue/todo/4260538 ownership 7794:2108 queue/todo/4260378 ownership 7794:89, should be qmailq:qmail fixed, queue/todo/4260378 ownership 7794:2108 queue/todo/4260637 ownership 7794:89, should be qmailq:qmail fixed, queue/todo/4260637 ownership 7794:2108 queue/mess/0/4260773 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/0/4260773 ownership 7794:2108 queue/mess/0/4260497 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/0/4260497 ownership 7794:2108 queue/mess/1/4261487 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/1/4261487 ownership 7794:2108 queue/mess/1/4261280 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/1/4261280 ownership 7794:2108 queue/mess/1/4261556 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/1/4261556 ownership 7794:2108 queue/mess/2/4261258 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/2/4261258 ownership 7794:2108 queue/mess/2/4260637 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/2/4260637 ownership 7794:2108 queue/mess/3/4261282 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/3/4261282 ownership 7794:2108 queue/mess/5/4261215 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/5/4261215 ownership 7794:2108 queue/mess/7/4261424 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/7/4261424 ownership 7794:2108 queue/mess/7/4260366 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/7/4260366 ownership 7794:2108 queue/mess/8/4261563 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/8/4261563 ownership 7794:2108 queue/mess/10/4260461 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/10/4260461 ownership 7794:2108 queue/mess/11/4260531 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/11/4260531 ownership 7794:2108 queue/mess/12/4261245 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/12/4261245 ownership 7794:2108 queue/mess/13/4261430 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/13/4261430 ownership 7794:2108 queue/mess/13/4261361 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/13/4261361 ownership 7794:2108 queue/mess/15/4261478 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/15/4261478 ownership 7794:2108 queue/mess/16/4261272 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/16/4261272 ownership 7794:2108 queue/mess/16/4261433 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/16/4261433 ownership 7794:2108 queue/mess/18/4260285 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/18/4260285 ownership 7794:2108 queue/mess/18/4261274 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/18/4261274 ownership 7794:2108 queue/mess/18/4260538 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/18/4260538 ownership 7794:2108 queue/mess/19/4260378 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/19/4260378 ownership 7794:2108 queue/mess/20/4260402 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/20/4260402 ownership 7794:2108 queue/mess/20/4261460 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/20/4261460 ownership 7794:2108 queue/mess/21/4260771 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/21/4260771 ownership 7794:2108 queue/mess/21/4261461 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/21/4261461 ownership 7794:2108 queue/mess/22/4261462 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/22/4261462 ownership 7794:2108 queue/mess/22/4261255 ownership 7794:89, should be qmailq:qmail fixed, queue/mess/22/4261255 ownership 7794:2108 queue/intd/4260285 is mode 644, should be 600 changed queue/intd/4260285 mode to 600 queue/intd/4260461 is mode 644, should be 600 changed queue/intd/4260461 mode to 600 queue/intd/4260538 is mode 644, should be 600 changed queue/intd/4260538 mode to 600 queue/intd/4260378 is mode 644, should be 600 changed queue/intd/4260378 mode to 600 queue/intd/4260637 is mode 644, should be 600 changed queue/intd/4260637 mode to 600 > There's a queue_repair.py script in QTP. I'd give that a shot (after > flushing the queue and stopping qmail). Just a swag at this point. > > Gary Bowling wrote: >> Yikes.. well, ok then. I rebooted, but still the same. Very perplexing >> as >> I have checked stuff until I don't know what else to check.. >> >> Gary >> >> >>> Sounds like qmail-send isn't able to read the queue after it's cycled >>> through once, like it's blocked or something. I'm not real familiar >>> with >>> how that mechanism works. >>> >>> I wonder if there isn't a zombie process hanging around that's gumming >>> up the works. Have you (dare I say) rebooted? >>> >>> Gary Bowling wrote: >>>> Just reflective of the last restart. From looking at the server >>>> everything seems to be operating as normal.. >>>> >>>> Also, just several FYIs.. >>>> >>>> - When I rebuilt qmail-toaster to remove the "/" in chkusr, I actually >>>> also upgraded. My server was running qmail-toaster-1.03 1.3.18 prior >>>> to >>>> the work and qmail-toaster-1.03 1.3.19 after. I also notice there are >>>> a >>>> few other minor updates to other packages since my old 1.3.18, such as >>>> my simscan is 1.4.0.-1.3.1 and I notice it's now 1.4.0-1.3.8 on the >>>> download. >>>> >>>> - The smtp2 service you see running is smtp on an alternate port so my >>>> road warriors work from any ISP, which was unchanged by the new >>>> update. >>>> >>>> - The crappy old tmda stuff was installed from Bill Shupp's toaster as >>>> that's what I used to run. I'm trying to get rid of it but have a few >>>> users who are holding on to it.. But again, that didn't change and I >>>> don't believe any of that install touches any of the toaster files, it >>>> just uses .qmail files in users directories to do it's thing. >>>> >>>> Gary >>>> >>>> Eric Shubert wrote: >>>>> Is the send daemon having a problem staying up? Or is that time >>>>> simply >>>>> reflective of the last time you restarted it? >>>>> >>>>> Gary Bowling wrote: >>>>>> Here it is: >>>>>> >>>>>> service qmail stat >>>>>> authlib: up (pid 1097) 6520 seconds >>>>>> clamd: up (pid 1061) 6520 seconds >>>>>> imap4: up (pid 5073) 5237 seconds >>>>>> imap4-ssl: up (pid 5071) 5237 seconds >>>>>> pop3: up (pid 5089) 5237 seconds >>>>>> pop3-ssl: up (pid 5066) 5237 seconds >>>>>> send: up (pid 19445) 100 seconds >>>>>> smtp: up (pid 10875) 3220 seconds >>>>>> smtp2: up (pid 5068) 5237 seconds >>>>>> spamd: up (pid 1054) 6520 seconds >>>>>> submission: up (pid 5095) 5237 seconds >>>>>> tmda-ofmipd: up (pid 1091) 6520 seconds >>>>>> tmda-ssl: up (pid 5113) 5237 seconds >>>>>> authlib/log: up (pid 1326) 1420511 seconds >>>>>> clamd/log: up (pid 6186) 16105 seconds >>>>>> imap4/log: up (pid 1309) 1420511 seconds >>>>>> imap4-ssl/log: up (pid 1307) 1420511 seconds >>>>>> pop3/log: up (pid 1320) 1420511 seconds >>>>>> pop3-ssl/log: up (pid 1328) 1420512 seconds >>>>>> send/log: up (pid 1314) 1420512 seconds >>>>>> smtp2/log: up (pid 1334) 1420512 seconds >>>>>> smtp/log: up (pid 1319) 1420512 seconds >>>>>> spamd/log: up (pid 13378) 29382 seconds >>>>>> submission/log: up (pid 1323) 1420512 seconds >>>>>> tmda-ofmipd/log: up (pid 1331) 1420512 seconds >>>>>> tmda-ssl/log: up (pid 1311) 1420512 seconds >>>>>> >>>>>> >>>>>> >>>>>> Eric Shubert wrote: >>>>>>> Yeah, I think that >>>>>>> # service qmail doqueue >>>>>>> would do the same thing. >>>>>>> >>>>>>> What do you see from: >>>>>>> # service qmail stat >>>>>>> >>>>>>> Gary Bowling wrote: >>>>>>>> Based on your last question, I have now also discovered that a >>>>>>>> stop/start of "send" will also deliver the email. >>>>>>>> >>>>>>>> svc -d /service/send >>>>>>>> svc -u /service/send >>>>>>>> >>>>>>>> and it clears the email. I can't find any errors in any log. >>>>>>>> >>>>>>>> Thanks, Gary >>>>>>>> >>>>>>>> Eric Shubert wrote: >>>>>>>>> Gary Bowling wrote: >>>>>>>>>> I had an issue with a blackberry user, so I went to the video to >>>>>>>>>> recompile the toaster to allow the "/" characters in the "from" >>>>>>>>>> address. >>>>>>>>>> >>>>>>>>>> All went well with the recompile and subsequent re-install. >>>>>>>>>> >>>>>>>>>> However, after the re-install I can no longer send or receive >>>>>>>>>> mail even to a local user. It seems all the mail queues up, so >>>>>>>>>> I'm not losing mail, and whatever is in the queue all releases >>>>>>>>>> if >>>>>>>>>> I restart qmail (qmailctl restart). >>>>>>>>>> >>>>>>>>>> In my toaster I had removed domain keys, by changing the link to >>>>>>>>>> qmail-queue to point to qmail-queue-orig, and I had installed >>>>>>>>>> spamdyke >>>>>>>>>> so I had to change the /service/smtp/run to link to >>>>>>>>>> /service/smtp/run.spamdyke, I remembered to change those back. >>>>>>>>>> But there >>>>>>>>>> is still something I'm missing. >>>>>>>>>> >>>>>>>>>> Unfortunately I didn't think about it changing all my settings >>>>>>>>>> until >>>>>>>>>> after the fact. I'm sure there is some other customization that >>>>>>>>>> I >>>>>>>>>> need >>>>>>>>>> to fix that I am missing. >>>>>>>>>> >>>>>>>>>> Any help would be appreciated as restarting qmail every 15 >>>>>>>>>> minutes or so >>>>>>>>>> to get mail to deliver is NOT working for me on a Friday :) >>>>>>>>>> >>>>>>>>>> Thanks, Gary >>>>>>>>>> >>>>>>>>> What is in the send log? >>>>>>>>> >>>>>>>> --------------------------------------------------------------------------------- >>> >>> -- >>> -Eric 'shubes' >>> >>> >>> --------------------------------------------------------------------------------- >>> Qmailtoaster is sponsored by Vickers Consulting Group >>> (www.vickersconsulting.com) >>> Vickers Consulting Group offers Qmailtoaster support and >>> installations. >>> If you need professional help with your setup, contact them >>> today! >>> --------------------------------------------------------------------------------- >>> Please visit qmailtoaster.com for the latest news, updates, and >>> packages. >>> >>> To unsubscribe, e-mail: >>> [email protected] >>> For additional commands, e-mail: >>> [email protected] >>> >>> >>> >> >> > > > -- > -Eric 'shubes' > > > --------------------------------------------------------------------------------- > Qmailtoaster is sponsored by Vickers Consulting Group > (www.vickersconsulting.com) > Vickers Consulting Group offers Qmailtoaster support and > installations. > If you need professional help with your setup, contact them today! > --------------------------------------------------------------------------------- > Please visit qmailtoaster.com for the latest news, updates, and > packages. > > To unsubscribe, e-mail: > [email protected] > For additional commands, e-mail: > [email protected] > > > -- --------------------------------------------------------------------------------- Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! --------------------------------------------------------------------------------- Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
