Poll does not close after that expiration time ends. Bug or my fault?

It looks to me that any tasks that are background jobs are not executing.

If you load https://yourserver.com/sidekiq it will show you the status of background jobs, and might explain what's going on in there.

You'll need to be logged in as an admin user.

Oh cool! I did not know this feature. This is great!

I made a screnshot and I placed it here. (unfortunately, it is in german, but I clicked on the tab "Tries".



It seems that for some jobs there is a SMTP failure. Could that be?

I just tried my SMTP through the login via email verification: So it seems to work - I received an email from the server with the verification code. Furthermore I receive also emails, when e.g. another person is answering on one of my comments. That is also a hint, that SMTP ist working, isn't it?

By the way, some days ago everything seemed to work fine. The polls where claused automatically and I got a reminder mail before the poll closed. I cannot explain why it worked suddenly. Now, it does not work anymore... I think that I changed nothing :/ And I cannot explain myself why..

ok! so it seems like it is retrying the expire lapsed polls job because an email is not able to send correctly. The job itself should probably be rewritten so that it does not do this, but you can still fix this by either deleting the jobs, and/or, working out why the email's are failing.

Okay. I deleted the jobs through the sidekiq applicaton.

Should I delte also the lines that are listed in the queue tab?

There is one thing that I did not unserstand yet concerning the crontab lines.

Is an empty log file good or bad?

I deleted the entries in the qaiting queue now. Let's see what will happen.

I looked now also in the details of the Failure Messege. This is what is logged inside - but I cannot figure it out.

I see that there is a "block in deliver mail" sentences inside the log.

I checked the SMTP Server, that is from the same provider, where the DNS is running.

Error
Error Class Net: SMTPFatalError
Error Message: 550-Requested action not taken: mailbox unavailable
Error Report

/usr/local/lib/ruby/2.6.0/net/smtp.rb:969:in `check_response' /usr/local/lib/ruby/2.6.0/net/smtp.rb:937:in`getok'  
/usr/local/lib/ruby/2.6.0/net/smtp.rb:865:in `rcptto' /usr/local/lib/ruby/2.6.0/net/smtp.rb:846:in`block in rcptto\_list'  
/usr/local/lib/ruby/2.6.0/net/smtp.rb:844:in `each' /usr/local/lib/ruby/2.6.0/net/smtp.rb:844:in`rcptto\_list'  
/usr/local/lib/ruby/2.6.0/net/smtp.rb:659:in `send_message' /usr/local/bundle/gems/mail-2.7.1/lib/mail/network/delivery_methods/smtp_connection.rb:54:in`deliver!'  
/usr/local/bundle/gems/mail-2.7.1/lib/mail/network/delivery\_methods/smtp.rb:101:in `block in deliver!' /usr/local/lib/ruby/2.6.0/net/smtp.rb:519:in`start'  
/usr/local/bundle/gems/mail-2.7.1/lib/mail/network/delivery\_methods/smtp.rb:109:in `start_smtp_session' /usr/local/bundle/gems/mail-2.7.1/lib/mail/network/delivery_methods/smtp.rb💯in`deliver!'  
/usr/local/bundle/gems/mail-2.7.1/lib/mail/message.rb:2159:in `do_delivery' /usr/local/bundle/gems/mail-2.7.1/lib/mail/message.rb:260:in`block in deliver'  
/usr/local/bundle/gems/actionmailer-5.2.4.2/lib/action\_mailer/base.rb:560:in `block in deliver_mail' /usr/local/bundle/gems/activesupport-5.2.4.2/lib/active_support/notifications.rb:168:in`block in instrument'  
/usr/local/bundle/gems/activesupport-5.2.4.2/lib/active\_support/notifications/instrumenter.rb:23:in `instrument' /usr/local/bundle/gems/activesupport-5.2.4.2/lib/active_support/notifications.rb:168:in`instrument'  
/usr/local/bundle/gems/actionmailer-5.2.4.2/lib/action\_mailer/base.rb:558:in `deliver_mail' /usr/local/bundle/gems/mail-2.7.1/lib/mail/message.rb:260:in`deliver'  
/usr/local/bundle/gems/actionmailer-5.2.4.2/lib/action\_mailer/message\_delivery.rb:114:in `block in deliver_now' /usr/local/bundle/gems/actionmailer-5.2.4.2/lib/action_mailer/rescuable.rb:17:in`handle\_exceptions'  
/usr/local/bundle/gems/actionmailer-5.2.4.2/lib/action\_mailer/message\_delivery.rb:113:in `deliver_now' /loomio/app/models/concerns/events/notify/author.rb:8:in`email\_author!'  
/loomio/app/models/events/poll\_expired.rb:16:in `email_author!' /loomio/app/models/concerns/events/notify/author.rb:4:in`trigger!'  
/loomio/app/models/concerns/events/notify/third\_party.rb:3:in `trigger!' /loomio/app/models/concerns/events/notify/in_app.rb:5:in`trigger!'  
/loomio/app/models/event.rb:45:in `tap' /loomio/app/models/event.rb:45:in`publish!'  
/loomio/app/models/events/poll\_expired.rb:7:in `publish!' /loomio/app/services/poll_service.rb:78:in`block in expire\_lapsed\_polls'  
/usr/local/bundle/gems/activerecord-5.2.4.2/lib/active\_record/relation/delegation.rb:71:in `each' /usr/local/bundle/gems/activerecord-5.2.4.2/lib/active_record/relation/delegation.rb:71:in`each'  
/loomio/app/services/poll\_service.rb:75:in `expire_lapsed_polls' /usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/extensions/class_methods.rb:19:in`perform'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:196:in `execute_job' /usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:164:in`block (2 levels) in process'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/middleware/chain.rb:138:in `block in invoke' /usr/local/bundle/gems/newrelic_rpm-6.10.0.364/lib/new_relic/agent/instrumentation/sidekiq.rb:32:in`block in call'  
/usr/local/bundle/gems/newrelic\_rpm-6.10.0.364/lib/new\_relic/agent/instrumentation/controller\_instrumentation.rb:376:in `perform_action_with_newrelic_trace' /usr/local/bundle/gems/newrelic_rpm-6.10.0.364/lib/new_relic/agent/instrumentation/sidekiq.rb:28:in`call'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/middleware/chain.rb:140:in `block in invoke' /usr/local/bundle/gems/sentry-raven-2.13.0/lib/raven/integrations/sidekiq.rb:9:in`call'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/middleware/chain.rb:140:in `block in invoke' /usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/middleware/chain.rb:143:in`invoke'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:163:in `block in process' /usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:136:in`block (6 levels) in dispatch'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/job\_retry.rb:111:in `local' /usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:135:in`block (5 levels) in dispatch'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/rails.rb:43:in `block in call' /usr/local/bundle/gems/activesupport-5.2.4.2/lib/active_support/execution_wrapper.rb:87:in`wrap'  
/usr/local/bundle/gems/activesupport-5.2.4.2/lib/active\_support/reloader.rb:73:in `block in wrap' /usr/local/bundle/gems/activesupport-5.2.4.2/lib/active_support/execution_wrapper.rb:87:in`wrap'  
/usr/local/bundle/gems/activesupport-5.2.4.2/lib/active\_support/reloader.rb:72:in `wrap' /usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/rails.rb:42:in`call'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:131:in `block (4 levels) in dispatch' /usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:257:in`stats'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:126:in `block (3 levels) in dispatch' /usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/job_logger.rb:13:in`call'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:125:in `block (2 levels) in dispatch' /usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/job_retry.rb:78:in`global'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:124:in `block in dispatch' /usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/logger.rb:10:in`with'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/job\_logger.rb:33:in `prepare' /usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:123:in`dispatch'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:162:in `process' /usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:78:in`process\_one'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/processor.rb:68:in `run' /usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/util.rb:15:in`watchdog'  
/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/util.rb:24:in \`block in safe\_thread'

What happens when the email is to a completely different address, for instance, a gmail address? Does it deliver?

I did not understand your question. How can I check to which mail address the mail is delivered.

I am receiving mails to my Gmail address, with which I created my Admin account.

I created a new group on the loomio server, then a new discussion with a poll wirth experation date.

The service worked, I got an email that the poll was closed. I checked in the loomio discussion and the state of the poll changed to ended.

So here it worked. But I did not get a what happend on loomio mail.

In sidekiq, there are still occurring error messages of the same kind.

The catch up email is only sent if there is content which you have not read, is it possible that you have just read all the content, that's why you don't get any mail?

The error you're seeing must be to another user with a bad email address. And it could be "Loomio Bot", which I should remove. That failure won't stop other emails from being delivered.

Oh yes. You were right. I did no Catch Up Mail because I was very active in the discussions and had nothing unread. I tested it and I can confirm that I am receiving this mails.

Maybe, like you assume, the Loomio Bot is the cause of the error messages in the Sidekiq. How can I check this to get this information for you?

Thanks four help, @Rob Guthrie