Please provide as much relevant log output as possible.
its not genertaing any log,whereas this is the old log
[worker.3:9014] [2017-07-11T22:16:30.448] INFO -- : [SUNIOHQOFT] [1::22995 23002] Message inspected successfully
[worker.3:9014] [2017-07-11T22:16:36.509] INFO -- : [SUNIOHQOFT] [1::22995 23002] Processing complete
[worker.3:9014] [2017-07-11T22:16:36.670] INFO -- : [SUNIOHQOFT] [1::88854 88861] Got queued message with exclusive lock
[worker.3:9014] [2017-07-11T22:16:36.839] INFO -- : [SUNIOHQOFT] [1::88854 88861] Parsing message content as it hasn't been parsed before
[worker.3:9014] [2017-07-11T22:16:36.978] INFO -- : [SUNIOHQOFT] [1::88854 88861] Inspecting message
[worker.3:9014] [2017-07-11T22:16:37.160] INFO -- : [SUNIOHQOFT] [1::88854 88861] Message inspected successfully
[worker.3:9014] [2017-07-11T22:16:38.554] INFO -- : Exit requested but job is running. Waiting for job to finish.
[worker.3:9014] [2017-07-11T22:16:39.818] INFO -- : [SUNIOHQOFT] [1::88854 88861] Processing complete
[worker.3:9014] [2017-07-11T22:16:40.106] INFO -- : [SUNIOHQOFT] Finished processing UnqueueMessageJob job in 10.270769806s
[worker.3:9014] [2017-07-11T22:16:40.107] INFO -- : Exiting because a job has ended.
Smtp server logs
https://www.screencast.com/t/BsssbR6px0
[smtp.1:10168] [2017-07-13T17:13:36.769] ERROR -- : [CVNBUR] /root/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:20:in dispatch'
[smtp.1:10168] [2017-07-13T17:13:36.769] ERROR -- : [CVNBUR] /root/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/l ib/thor/base.rb:444:instart'
[smtp.1:10168] [2017-07-13T17:13:36.769] ERROR -- : [CVNBUR] /root/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:10:in start'
[smtp.1:10168] [2017-07-13T17:13:36.769] ERROR -- : [CVNBUR] /root/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/exe/bundle:35:inblock i n with_friendly_errors'
[smtp.1:10168] [2017-07-13T17:13:36.769] ERROR -- : [CVNBUR] /root/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/exe/bundle:27:inload'
[smtp.1:10168] [2017-07-13T17:13:36.769] ERROR -- : [CVNBUR] /root/.rbenv/versions/2.4.0/bin/bundle:22:in
Nothing you've provided there can help us debug this.
=>"[email protected]", "subject"=>"Test Message at July 13, 2017 18:07", "plain_body"=>"This is a message to test the delivery of messages through Postal."}, "commit"=>"Send Message", "org_permalink"=>"migo01", "server_id"=>"mta-migo01-net"}
18:07:14 web.1 | => [web.1:31056] [2017-07-13T18:07:14.323] INFO -- : Completed 500 Internal Server Error in 210ms (ActiveRecord: 30.0ms)
18:07:14 web.1 | => [web.1:31056] [2017-07-13T18:07:14.324] FATAL -- :
18:07:14 web.1 | => [web.1:31056] [2017-07-13T18:07:14.324] FATAL -- : Bunny::NotAllowedError (Connection-level error: NOT_ALLOWED - access to vhost 'postal' refused for user 'postal'):
18:07:14 web.1 | => [web.1:31056] [2017-07-13T18:07:14.325] FATAL -- :
18:07:14 web.1 | => [web.1:31056] [2017-07-13T18:07:14.325] FATAL -- : lib/postal/rabbit_mq.rb:15:in `create_connection'
This definitely looks like it might explain the problem. Was this an automated installation, or did you configure things manually?
I have configured manually
Please suggest how to clear queue message.
https://www.screencast.com/t/2pTt5damB
I created a fresh testing environment for postal yesterday and for whatever reason the script didn't create the user, queue, or permissions in rabbitmq. I saw similar errors about not being able to connect.
Repeating the commands from the bash script and restarting postal resolved the issue.
rabbitmqctl add_vhost /postal
rabbitmqctl add_user postal p0stalpassw0rd
rabbitmqctl set_permissions -p /postal postal ".*" ".*" ".*"
Please suggest how to clear queue message.
https://www.screencast.com/t/2pTt5damB
I assume these are messages that are queued but were not able to be added to the RabbitMQ queue. Di you still wish to send them?
yes I would like to messages to be send
Most helpful comment
I created a fresh testing environment for postal yesterday and for whatever reason the script didn't create the user, queue, or permissions in rabbitmq. I saw similar errors about not being able to connect.
Repeating the commands from the bash script and restarting postal resolved the issue.