502 Command not implemented

support
1

Hi,

On a regular basis we create a newsletter for all users by a new subject in a category set up a standard setting as watching first post. Today only about 50 messages were sent.
About 130 users, randomly, no cetain trust level and both new and old ones is listed as emails skipped with reason:

|user_watching_first_post|, 502 Command not implemented|

I´ve checked some of those and they have the correct setting and everything in their profile.
What´s causing this error and how to solve it?

Will the system try to resend those skipped or is it any way to trigger this without making a new post?

It seems we had the same issue before 14/8 regarding:

|user_posted|, 502 Command not implemented|

I never noticed this one. Also randomly among our users.

What´s causing this?

1 Like
2

Where are you getting this 502 from? Is there any more details next to it?

Are there any relevant entries in /logs?

2 Likes
3

bild
bild1517×456 36.8 KB

Nothing in /logs

bild
bild1583×730 52.5 KB

4

aha there´s another one…

at the same time:

Job exception:connection reset by peer
/usr/local/lib/ruby/2.6.0/openssl/buffering.rb:383:in `syswrite_nonblock'
/usr/local/lib/ruby/2.6.0/openssl/buffering.rb:383:in `write_nonblock'
/usr/local/lib/ruby/2.6.0/net/protocol.rb:277:in `block in write0'
/usr/local/lib/ruby/2.6.0/net/protocol.rb:275:in `each'
/usr/local/lib/ruby/2.6.0/net/protocol.rb:275:in `each_with_index'
/usr/local/lib/ruby/2.6.0/net/protocol.rb:275:in `write0'
/usr/local/lib/ruby/2.6.0/net/protocol.rb:256:in `block in writeline'
/usr/local/lib/ruby/2.6.0/net/protocol.rb:265:in `writing'
/usr/local/lib/ruby/2.6.0/net/protocol.rb:255:in `writeline'
/usr/local/lib/ruby/2.6.0/net/smtp.rb:934:in `block in getok'
/usr/local/lib/ruby/2.6.0/net/smtp.rb:960:in `critical'
/usr/local/lib/ruby/2.6.0/net/smtp.rb:933:in `getok'
/usr/local/lib/ruby/2.6.0/net/smtp.rb:919:in `quit'
/usr/local/lib/ruby/2.6.0/net/smtp.rb:612:in `do_finish'
/usr/local/lib/ruby/2.6.0/net/smtp.rb:521:in `ensure in start'
/usr/local/lib/ruby/2.6.0/net/smtp.rb:521:in `start'
mail-2.7.1/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session'
mail-2.7.1/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!'
mail-2.7.1/lib/mail/message.rb:2159:in `do_delivery'
mail-2.7.1/lib/mail/message.rb:260:in `block in deliver'
actionmailer-6.0.3.2/lib/action_mailer/base.rb:589:in `block in deliver_mail'
activesupport-6.0.3.2/lib/active_support/notifications.rb:180:in `block in instrument'
activesupport-6.0.3.2/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
activesupport-6.0.3.2/lib/active_support/notifications.rb:180:in `instrument'
actionmailer-6.0.3.2/lib/action_mailer/base.rb:587:in `deliver_mail'
mail-2.7.1/lib/mail/message.rb:260:in `deliver'
actionmailer-6.0.3.2/lib/action_mailer/message_delivery.rb:115:in `block in deliver_now'
actionmailer-6.0.3.2/lib/action_mailer/rescuable.rb:17:in `handle_exceptions'
actionmailer-6.0.3.2/lib/action_mailer/message_delivery.rb:114:in `deliver_now'
/var/www/discourse/lib/email/sender.rb:215:in `send'
/var/www/discourse/app/jobs/regular/user_email.rb:61:in `execute'
/var/www/discourse/app/jobs/base.rb:232:in `block (2 levels) in perform'
rails_multisite-2.3.0/lib/rails_multisite/connection_management.rb:68:in `with_connection'
/var/www/discourse/app/jobs/base.rb:221:in `block in perform'
/var/www/discourse/app/jobs/base.rb:217:in `each'
/var/www/discourse/app/jobs/base.rb:217:in `perform'
sidekiq-6.0.7/lib/sidekiq/processor.rb:196:in `execute_job'
sidekiq-6.0.7/lib/sidekiq/processor.rb:164:in `block (2 levels) in process'
sidekiq-6.0.7/lib/sidekiq/middleware/chain.rb:138:in `block in invoke'
/var/www/discourse/lib/sidekiq/pausable.rb:138:in `call'
sidekiq-6.0.7/lib/sidekiq/middleware/chain.rb:140:in `block in invoke'
sidekiq-6.0.7/lib/sidekiq/middleware/chain.rb:143:in `invoke'
sidekiq-6.0.7/lib/sidekiq/processor.rb:163:in `block in process'
sidekiq-6.0.7/lib/sidekiq/processor.rb:136:in `block (6 levels) in dispatch'
sidekiq-6.0.7/lib/sidekiq/job_retry.rb:111:in `local'
sidekiq-6.0.7/lib/sidekiq/processor.rb:135:in `block (5 levels) in dispatch'
sidekiq-6.0.7/lib/sidekiq.rb:37:in `block in <module:Sidekiq>'
sidekiq-6.0.7/lib/sidekiq/processor.rb:131:in `block (4 levels) in dispatch'
sidekiq-6.0.7/lib/sidekiq/processor.rb:257:in `stats'
sidekiq-6.0.7/lib/sidekiq/processor.rb:126:in `block (3 levels) in dispatch'
sidekiq-6.0.7/lib/sidekiq/job_logger.rb:13:in `call'
sidekiq-6.0.7/lib/sidekiq/processor.rb:125:in `block (2 levels) in dispatch'
sidekiq-6.0.7/lib/sidekiq/job_retry.rb:78:in `global'
sidekiq-6.0.7/lib/sidekiq/processor.rb:124:in `block in dispatch'
sidekiq-6.0.7/lib/sidekiq/logger.rb:10:in `with'
sidekiq-6.0.7/lib/sidekiq/job_logger.rb:33:in `prepare'
sidekiq-6.0.7/lib/sidekiq/processor.rb:123:in `dispatch'
sidekiq-6.0.7/lib/sidekiq/processor.rb:162:in `process'
sidekiq-6.0.7/lib/sidekiq/processor.rb:78:in `process_one'
sidekiq-6.0.7/lib/sidekiq/processor.rb:68:in `run'
sidekiq-6.0.7/lib/sidekiq/util.rb:15:in `watchdog'
sidekiq-6.0.7/lib/sidekiq/util.rb:24:in `block in safe_thread'
1 Like
5

That’s a problem with your email setup / SMTP provider.

Try talking to your email provider for extra help debugging what’s going on!

Additionally, that is not an effective redaction; can you produce a new version showing a few records using black boxes instead of the spraypaint function and edit the post to use that image instead?
=> Thanks, we’ve removed the old version of the post.

4 Likes
6

Will do so, have to get in contact with our manager first, he´s on vaccation.

Thx!

1 Like
7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.