On 3/26/22 10:28, Shashikanth Komandoor wrote:
Hi Team,
We have restarted the services as well but no change.
Odd.
We tried manually moving the pck file from pipeline queue to
out queue but the file disappeared from out queue but is not getting delivered.
This is expected because if the message hasn't been processed through the pipeline, it has no recipients in the metadata, so the outgoing runner delivered it to no one. Also, it skipped archiving and digesting.
We moved the pck file from pipeline queue to out queue with the
extension .bak still no use.
Same as above.
Not sure what to try next. Please help.
Mi first guess is the pipeline runner isn't running, but you restarted the services, presumably Mailman core, and that might fix it, but there are various ways the pipeline runner could have died that would cause the master to not restart it.
You need to stop Mailman core and then start it rather than just restarting. That may help.
Also look in mailman.log. Assuming the pipeline runner died at some point, there should be a log entry and possible an exception with traceback indicating why.
You can see which runners are running with something like
ps -fwwA|grep runner=|sed s/.*runner=//
This should produce a list something like
archive:0:1
bounces:0:1
command:0:1
in:0:1
lmtp:0:1
nntp:0:1
out:0:1
pipeline:0:1
rest:0:1
retry:0:1
task:0:1
virgin:0:1
digest:0:1
rest:0:1
rest:0:1
except depending on version, task
may not be there.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan