Narrative Bot not responding due to Mailing List Mode

joebuhlig · June 1, 2017, 2:15pm

I’m pretty certain this isn’t a bug but it’s driving me nuts. If I do the following I get no responses from the bot:

I can verify that responding to the bot works for new users. There’s no issue there. But for some reason my admin account never triggers a reply from the bot. And I haven’t been able to locate an error anywhere in the console or in /logs.

I should also note that I have two other instances that I’ve tested this on and it works flawlessly. I’m simply at a loss for where to look next. Ideas?

SidV · June 1, 2017, 2:34pm

Guildbot?
I assume you changed the name of the bot.
Try re-name to discobot and try again

joebuhlig · June 1, 2017, 2:50pm

Well, that was certainly something I missed trying. But no dice. I changed it back, tried to trigger display help, and still no response.

codinghorror · June 1, 2017, 6:18pm

Not sure @tgxworld would need to weigh in. Could be the rename but that is supported.

cpradio · June 1, 2017, 6:22pm

Depending the version of Discourse/Narative Bot you are on, there was at one point a requirement of a rebuild for the rename to take effect. I know that requirement is no longer necessary, but maybe it was a timing thing and doing a rebuild would clear it up now?

tobiaseigen · June 1, 2017, 6:23pm

stupid question - did you disable public replies?

joebuhlig · June 1, 2017, 7:11pm

I was operating on that assumption originally. I didn’t realize until later that it wasn’t required if I was on latest first. So I made the change and then ran a rebuild. It didn’t make any difference.

Good thing to check on for sure. I wish that had been it, but it’s not. Good call, though.

codinghorror · June 1, 2017, 7:34pm

If you did a bot rename on an old version you may have run into a bug; I suggest restarting the docker container to make sure all values are reloaded.

joebuhlig · June 1, 2017, 8:17pm

Just tried a stop app and start app. No change there. Could there be a rate limiter involved here?

tophee · June 1, 2017, 8:41pm

I vaguely remember having had similar issues after renaming the bot and after some time (perhaps after I rebuilt?) it suddenly worked again. That was more than a month ago, though.

tgxworld · June 2, 2017, 3:36am

There are a couple of things you can check.

What is the locale of the site/your user locale?
Do someone rename the trigger in site settings text customizations?

joebuhlig · June 2, 2017, 11:13am

Locales are both English.

I’ve not touched any text customizations. I’m the only admin on the site.

I did do a bit more digging and found a potential error that’s related. It didn’t seem relevant at the time and it still doesn’t add up to me why failing once would cause it to continue to fail. Either way, here’s the trace:

Job exception: RateLimiter::LimitExceeded

/var/www/discourse/lib/rate_limiter.rb:61:in `performed!'
/var/www/discourse/lib/rate_limiter/on_create_record.rb:42:in `block in rate_limit'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:446:in `instance_exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:446:in `block in make_lambda'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:228:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:506:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:506:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:506:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in `_run_create_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/callbacks.rb:306:in `_create_record'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/timestamp.rb:57:in `_create_record'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/persistence.rb:504:in `create_or_update'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/callbacks.rb:302:in `block in create_or_update'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/callbacks.rb:778:in `_run_save_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/callbacks.rb:302:in `create_or_update'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/persistence.rb:120:in `save'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/validations.rb:37:in `save'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/attribute_methods/dirty.rb:21:in `save'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:286:in `block (2 levels) in save'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:211:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:220:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:348:in `with_transaction_returning_status'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:286:in `block in save'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:301:in `rollback_active_record_state!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:285:in `save'
/var/www/discourse/lib/post_creator.rb:430:in `save_post'
/var/www/discourse/lib/post_creator.rb:143:in `block in create'
/var/www/discourse/lib/distributed_mutex.rb:21:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:5:in `synchronize'
/var/www/discourse/lib/post_creator.rb:293:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:220:in `transaction'
/var/www/discourse/lib/post_creator.rb:287:in `transaction'
/var/www/discourse/lib/post_creator.rb:140:in `create'
/var/www/discourse/lib/post_creator.rb:182:in `create!'
/var/www/discourse/lib/post_creator.rb:209:in `create!'
/var/www/discourse/plugins/discourse-narrative-bot/lib/discourse_narrative_bot/advanced_user_narrative.rb:119:in `init_tutorial_edit'
/var/www/discourse/plugins/discourse-narrative-bot/lib/discourse_narrative_bot/base.rb:189:in `init_state'
/var/www/discourse/plugins/discourse-narrative-bot/lib/discourse_narrative_bot/base.rb:49:in `block in input'
/var/www/discourse/plugins/discourse-narrative-bot/lib/discourse_narrative_bot/advanced_user_narrative.rb:375:in `block in synchronize'
/var/www/discourse/lib/distributed_mutex.rb:21:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:5:in `synchronize'
/var/www/discourse/plugins/discourse-narrative-bot/lib/discourse_narrative_bot/advanced_user_narrative.rb:375:in `synchronize'
/var/www/discourse/plugins/discourse-narrative-bot/lib/discourse_narrative_bot/base.rb:15:in `input'
/var/www/discourse/plugins/discourse-narrative-bot/jobs/narrative_init.rb:8:in `block in execute'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/i18n-0.8.1/lib/i18n.rb:257:in `with_locale'
/var/www/discourse/plugins/discourse-narrative-bot/jobs/narrative_init.rb:7:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'

joebuhlig · June 2, 2017, 4:13pm

Thinking about this a bit further, would it make sense to manually trigger the NarrativeInit job? That seems to be where the beginning of that trace develops.

tgxworld · June 5, 2017, 1:31am

@joebuhlig That trace was super helpful . Can you try again? I’ve deployed the following fix

https://github.com/discourse/discourse/commit/418cb09713be53b7437c8b33a963365cef98dd36

joebuhlig · June 5, 2017, 11:31am

Just gave it a try. No dice. I’m on 30f275. Is there a log file somewhere I can run through to see what’s going on when the trigger phrase is used? That’s the only thing I can think of right now since there are no errors. I’ve tried numerous ways of reproducing this and can’t get it done.

tgxworld · June 5, 2017, 11:42am

Hmm can you try to trigger a job manually? Is the site we’re talking about feverbee?

joebuhlig · June 5, 2017, 12:02pm

Ok. Here’s what I did.

enter app and ran Jobs.enqueue(:narrative_init, user_id: 1, klass:DiscourseNarrativeBot::NewUserNarrative.to_s)
I received the welcome message from the bot but bookmarking the message does nothing.
I checked all my settings for the bot to make sure I didn’t miss something. Here’s what I have:

Admin_-_Productivity_Guild.jpg1286×836 136 KB
I managed to find the log files on the server but nothing stands out as odd to me.
No errors in console or /logs.

And the site in question is productivityguild.com

tgxworld · June 5, 2017, 12:12pm

Are you still the only user that is unable to interact with the bot? If not can you ensure that Sidekiq is running?

joebuhlig · June 5, 2017, 12:18pm

It’s still just me. I can create a new user and it works fine. Sidekiq is running. That’s how I was able to manually trigger the job.

tgxworld · June 5, 2017, 12:20pm

Ah ha do you have mailing list mode enabled?

Topic		Replies	Views
Discobot not responding to bookmark? support	5	922	June 1, 2018
New users aren't starting the discobot tutorial feature discobot	80	15485	December 13, 2023
Discourse web interface becomes unresponsive a few minutes after starting installation	35	6300	January 9, 2018
Bug when discobot assigns the name in the certificate bug discobot	23	3029	June 12, 2017
Discourse Narrative Bot Beta Feedback announcements new-feature	58	27918	June 7, 2017

Narrative Bot not responding due to Mailing List Mode

Related Topics