Comments (12)
adamcooke
commented on May 14, 2024
Is postal running? Can you run 'postal status' to see what's running?
from postal.
mu-arch
commented on May 14, 2024
When I ran that prior I got the error:
Error: The PID directory (/opt/postal/app/tmp/pids) is not empty. Cannot start unless things are clean.
So I presumed it was running.
from postal.
mu-arch
commented on May 14, 2024
Upon looking through my active processes I don't see Postal in there, I'm not sure if that's the name it goes by. Plenty of other database processes running though.
from postal.
adamcooke
commented on May 14, 2024
Sounds like it might have died at some point. The log/procodile.log should give you a clue as to why that happened.
from postal.
mu-arch
commented on May 14, 2024
Here are the contents of that log:
22:01:46 system | Procodile supervisor started with PID 2292
22:01:46 system | Application root is /opt/postal/app
22:01:46 system | Reloading configuration
22:01:46 web.1 | Started with PID 2298
22:01:46 fast.1 | Started with PID 2300
22:01:46 worker.1 | Started with PID 2302
22:01:46 cron.1 | Started with PID 2304
22:01:46 smtp.1 | Started with PID 2306
22:01:46 requeuer.1 | Started with PID 2309
22:01:46 control | Listening at /opt/postal/app/tmp/pids/procodile.sock
22:01:50 web.1 | => Puma starting in single mode...
22:01:50 web.1 | => * Version 3.8.2 (ruby 2.3.4-p301), codename: Sassy Salamander
22:01:50 web.1 | => * Min threads: 5, max threads: 5
22:01:50 web.1 | => * Environment: production
22:02:10 cron.1 | => E, [2017-04-26T22:02:10.402921 #2304] ERROR -- #<Bunny::Session:0x5e6d980 [email protected]:
5672, vhost=/postal, addresses=[127.0.0.1:5672]>: Authentication with RabbitMQ failed: 403 ACCESS_REFUSED - Login was ref
used using authentication mechanism PLAIN. For details see the broker logfile.
22:02:10 worker.1 | => E, [2017-04-26T22:02:10.421348 #2302] ERROR -- #<Bunny::Session:0x524cc00 [email protected]:
5672, vhost=/postal, addresses=[127.0.0.1:5672]>: Authentication with RabbitMQ failed: 403 ACCESS_REFUSED - Login was ref
used using authentication mechanism PLAIN. For details see the broker logfile.
22:02:10 worker.1 | => rake aborted!
22:02:10 worker.1 | => Bunny::AuthenticationFailureError: Authentication with RabbitMQ failed. Please check your c
onnection settings. Username: postal, vhost: /postal, password length: 27
22:02:10 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/bunny-2.5.1/lib/bunny/session.rb:1082:in `ope
n_connection'
22:02:10 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/bunny-2.5.1/lib/bunny/session.rb:304:in `star
t'
22:02:10 worker.1 | => /opt/postal/app/lib/postal/rabbit_mq.rb:15:in `create_connection'
22:02:10 worker.1 | => /opt/postal/app/lib/postal/rabbit_mq.rb:20:in `create_channel'
22:02:10 worker.1 | => /opt/postal/app/lib/postal/worker.rb:171:in `job_channel'
22:02:10 worker.1 | => /opt/postal/app/lib/postal/worker.rb:15:in `work'
22:02:10 worker.1 | => /opt/postal/app/lib/tasks/postal.rake:5:in `block (2 levels) in <top (required)>'
22:02:10 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/exe/rake:27:in `<top (required)>'
22:02:10 worker.1 | => Tasks: TOP => postal:worker
22:02:10 worker.1 | => (See full trace by running task with --trace)
22:02:13 web.1 | => * Listening on tcp://127.0.0.1:5000
22:02:13 web.1 | => Use Ctrl-C to stop
22:02:13 worker.1 | Process has stopped. Respawning...
22:02:13 worker.1 | Started with PID 2355
22:02:17 worker.1 | => E, [2017-04-26T22:02:17.941287 #2355] ERROR -- #<Bunny::Session:0x4d45978 [email protected]:
5672, vhost=/postal, addresses=[127.0.0.1:5672]>: Authentication with RabbitMQ failed: 403 ACCESS_REFUSED - Login was ref
used using authentication mechanism PLAIN. For details see the broker logfile.
22:02:17 worker.1 | => rake aborted!
22:02:17 worker.1 | => Bunny::AuthenticationFailureError: Authentication with RabbitMQ failed. Please check your c
onnection settings. Username: postal, vhost: /postal, password length: 27
22:02:17 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/bunny-2.5.1/lib/bunny/session.rb:1082:in `ope
n_connection'
t'
22:02:17 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/bunny-2.5.1/lib/bunny/session.rb:304:in `start'
22:02:17 worker.1 | => /opt/postal/app/lib/postal/rabbit_mq.rb:15:in `create_connection'
22:02:17 worker.1 | => /opt/postal/app/lib/postal/rabbit_mq.rb:20:in `create_channel'
22:02:17 worker.1 | => /opt/postal/app/lib/postal/worker.rb:171:in `job_channel'
22:02:17 worker.1 | => /opt/postal/app/lib/postal/worker.rb:15:in `work'
22:02:17 worker.1 | => /opt/postal/app/lib/tasks/postal.rake:5:in `block (2 levels) in <top (required)>'
22:02:17 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/exe/rake:27:in `<top (required)>'
22:02:17 worker.1 | => Tasks: TOP => postal:worker
22:02:17 worker.1 | => (See full trace by running task with --trace)
22:02:19 worker.1 | Process has stopped. Respawning...
22:02:19 worker.1 | Started with PID 2605
22:02:25 worker.1 | => E, [2017-04-26T22:02:25.200974 #2605] ERROR -- #<Bunny::Session:0x5ee60b0 [email protected]:5672, vhost=/postal, addresses=[127.0.0.1:5672]>: Authentication with RabbitMQ failed: 403 ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
22:02:25 worker.1 | => rake aborted!
22:02:25 worker.1 | => Bunny::AuthenticationFailureError: Authentication with RabbitMQ failed. Please check your connection settings. Username: postal, vhost: /postal, password length: 27
22:02:25 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/bunny-2.5.1/lib/bunny/session.rb:1082:in `open_connection'
22:02:25 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/bunny-2.5.1/lib/bunny/session.rb:304:in `start'
22:02:25 worker.1 | => /opt/postal/app/lib/postal/rabbit_mq.rb:15:in `create_connection'
22:02:25 worker.1 | => /opt/postal/app/lib/postal/rabbit_mq.rb:20:in `create_channel'
22:02:25 worker.1 | => /opt/postal/app/lib/postal/worker.rb:171:in `job_channel'
22:02:25 worker.1 | => /opt/postal/app/lib/postal/worker.rb:15:in `work'
22:02:25 worker.1 | => /opt/postal/app/lib/tasks/postal.rake:5:in `block (2 levels) in <top (required)>'
22:02:25 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/exe/rake:27:in `<top (required)>'
22:02:25 worker.1 | => Tasks: TOP => postal:worker
22:02:25 worker.1 | => (See full trace by running task with --trace)
22:02:25 worker.1 | Process has stopped. Respawning...
22:02:25 worker.1 | Started with PID 2832
22:02:29 worker.1 | => E, [2017-04-26T22:02:29.190409 #2832] ERROR -- #<Bunny::Session:0x63a5f60 [email protected]:5672, vhost=/postal, addresses=[127.0.0.1:5672]>: Authentication with RabbitMQ failed: 403 ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
22:02:29 worker.1 | => rake aborted!
22:02:29 worker.1 | => Bunny::AuthenticationFailureError: Authentication with RabbitMQ failed. Please check your connection settings. Username: postal, vhost: /postal, password length: 27
22:02:29 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/bunny-2.5.1/lib/bunny/session.rb:1082:in `open_connection'
22:02:29 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/bunny-2.5.1/lib/bunny/session.rb:304:in `start'
22:02:29 worker.1 | => /opt/postal/app/lib/postal/rabbit_mq.rb:15:in `create_connection'
22:02:29 worker.1 | => /opt/postal/app/lib/postal/rabbit_mq.rb:20:in `create_channel'
22:02:29 worker.1 | => /opt/postal/app/lib/postal/worker.rb:171:in `job_channel'
22:02:29 worker.1 | => /opt/postal/app/lib/postal/worker.rb:15:in `work'
22:02:29 worker.1 | => /opt/postal/app/lib/tasks/postal.rake:5:in `block (2 levels) in <top (required)>'
22:02:29 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/exe/rake:27:in `<top (required)>'
22:02:29 worker.1 | => Tasks: TOP => postal:worker
22:02:29 worker.1 | => (See full trace by running task with --trace)
22:02:31 worker.1 | Process has stopped. Respawning...
22:02:31 worker.1 | Started with PID 2842
22:02:34 worker.1 | => E, [2017-04-26T22:02:34.462391 #2842] ERROR -- #<Bunny::Session:0x5707150 [email protected]:5672, vhost=/postal, addresses=[127.0.0.1:5672]>: Authentication with RabbitMQ failed: 403 ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
22:02:34 worker.1 | => rake aborted!
22:02:34 worker.1 | => Bunny::AuthenticationFailureError: Authentication with RabbitMQ failed. Please check your connection settings. Username: postal, vhost: /postal, password length: 27
22:02:34 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/bunny-2.5.1/lib/bunny/session.rb:1082:in `open_connection'
22:02:34 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/bunny-2.5.1/lib/bunny/session.rb:304:in `start'
22:02:34 worker.1 | => /opt/postal/app/lib/postal/rabbit_mq.rb:15:in `create_connection'
22:02:34 worker.1 | => /opt/postal/app/lib/postal/rabbit_mq.rb:20:in `create_channel'
22:02:34 worker.1 | => /opt/postal/app/lib/postal/worker.rb:171:in `job_channel'
22:02:34 worker.1 | => /opt/postal/app/lib/postal/worker.rb:15:in `work'
22:02:34 worker.1 | => /opt/postal/app/lib/tasks/postal.rake:5:in `block (2 levels) in <top (required)>'
22:02:34 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/exe/rake:27:in `<top (required)>'
22:02:34 worker.1 | => Tasks: TOP => postal:worker
22:02:34 worker.1 | => (See full trace by running task with --trace)
22:02:37 worker.1 | Process has stopped. Respawning...
22:02:37 worker.1 | Started with PID 2849
22:02:41 worker.1 | => E, [2017-04-26T22:02:41.150982 #2849] ERROR -- #<Bunny::Session:0x6110868 [email protected]:5672, vhost=/postal, addresses=[127.0.0.1:5672]>: Authentication with RabbitMQ failed: 403 ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
22:02:41 worker.1 | => rake aborted!
22:02:41 worker.1 | => Bunny::AuthenticationFailureError: Authentication with RabbitMQ failed. Please check your connection settings. Username: postal, vhost: /postal, password length: 27
22:02:41 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/bunny-2.5.1/lib/bunny/session.rb:1082:in `open_connection'
22:02:41 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/bunny-2.5.1/lib/bunny/session.rb:304:in `start'
22:02:41 worker.1 | => /opt/postal/app/lib/postal/rabbit_mq.rb:15:in `create_connection'
22:02:41 worker.1 | => /opt/postal/app/lib/postal/rabbit_mq.rb:20:in `create_channel'
22:02:41 worker.1 | => /opt/postal/app/lib/postal/worker.rb:171:in `job_channel'
22:02:41 worker.1 | => /opt/postal/app/lib/postal/worker.rb:15:in `work'
22:02:41 worker.1 | => /opt/postal/app/lib/tasks/postal.rake:5:in `block (2 levels) in <top (required)>'
22:02:41 worker.1 | => /opt/postal/app/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/exe/rake:27:in `<top (required)>'
22:02:41 worker.1 | => Tasks: TOP => postal:worker
22:02:41 worker.1 | => (See full trace by running task with --trace)
22:02:43 worker.1 | Warning: this process has been respawned 5 times and keeps dying.
22:02:43 worker.1 | It will not be respawned automatically any longer and will no longer be managed.
22:02:43 worker.1 | Removed PID file
22:03:10 cron.1 | => E, [2017-04-26T22:03:10.502543 #2304] ERROR -- #<Bunny::Session:0x4b947a0 [email protected]:5672, vhost=/postal, addresses=[127.0.0.1:5672]>: Authentication with RabbitMQ failed: 403 ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
22:04:10 cron.1 | => E, [2017-04-26T22:04:10.575284 #2304] ERROR -- #<Bunny::Session:0x4b5f960 [email protected]:5672, vhost=/postal, addresses=[127.0.0.1:5672]>: Authentication with RabbitMQ failed: 403 ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
22:05:10 cron.1 | => E, [2017-04-26T22:05:10.636816 #2304] ERROR -- #<Bunny::Session:0x5f2e6a8 [email protected]:5672, vhost=/postal, addresses=[127.0.0.1:5672]>: Authentication with RabbitMQ failed: 403 ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
22:06:10 cron.1 | => E, [2017-04-26T22:06:10.698126 #2304] ERROR -- #<Bunny::Session:0x5f72218 [email protected]:5672, vhost=/postal, addresses=[127.0.0.1:5672]>: Authentication with RabbitMQ failed: 403 ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
22:07:10 cron.1 | => E, [2017-04-26T22:07:10.767730 #2304] ERROR -- #<Bunny::Session:0x5faf000 [email protected]:5672, vhost=/postal, addresses=[127.0.0.1:5672]>: Authentication with RabbitMQ failed: 403 ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
22:07:29 system | Supervisor received TERM signal
22:07:29 system | Stopping Procodile supervisor
from postal.
mu-arch
commented on May 14, 2024
Seems rabbitMQ has incorrect credentials?
from postal.
adamcooke
commented on May 14, 2024
Looks like your credentials for connecting to RabbitMQ in the config file are wrong.
from postal.
mu-arch
commented on May 14, 2024
sudo rabbitmqctl add_user postal XXX
At this step in the guide I replaced XXX with my own password, was that not correct?
from postal.
adamcooke
commented on May 14, 2024
That certainly is correct, yes. Did you add it to postal.yml too?
from postal.
mu-arch
commented on May 14, 2024
Yes I configured passwords for main_db, message_db, and rabbitmq in postal.yml. I suppose it is possible I made a typo but I don't think so.
from postal.
mu-arch
commented on May 14, 2024
I have just changed all the passwords to confirm I did not make a mistake. I am still getting the error :(
from postal.
mu-arch
commented on May 14, 2024
I solved the problem by deleting the contents of /opt/postal/app/tmp/pids and then running postal start again.
I can now access the control panel. I don't have any idea what happened there, perhaps it was caused by a reboot I did during the installation steps.
Thanks for the help.
from postal.
Related Issues (20)
- Problem sending emails
- Messages stay in pending state forever HOT 1
- Message Charset / Content-Transfer-Encoding Issue HOT 4
- X-Postal-Tag is not extracted from messages that are held HOT 3
- Webhook requests are not being pruned HOT 2
- Encoding display is incorrect in the web interface Postal HOT 4
- Sending mail issue
- FrozenError: can't modify frozen String: "" HOT 8
- Incorrect domain addition rp.postal.example.com HOT 1
- postal version command not working
- Return Path bounce processing HOT 6
- messages stuck in queue HOT 11
- Cannot send incoming emails to HTTP Endpoint HOT 6
- Missing attachment when email is not multipart and only contains an attachment HOT 7
- Emails not sent from Toshiba and Kyocera printers.
- Can't use multiple simultaneous SMTP connections. HOT 1
- Postal doesn't automatically restart when host reboots (Docker installation) HOT 1
- Update quickstart script to use docker compose v2 HOT 1
- API call from internal network doesn't work HOT 1
- Issue for non-admin users to change their email address HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from postal.