500 error mit Automation Plugin

Festinger · 26. April 2024 um 07:36

Hallo,

seit dem letzten Update erhalten wir mit dem Automatisierungs-Plugin einen “500 Internal Server Error”.

plugins/automation/lib/discourse_automation/scripts/auto_responder.rb:60:in `block (2 levels) in <main>'

plugins/automation/app/models/discourse_automation/automation.rb:141:in `trigger!'

plugins/automation/lib/discourse_automation/event_handlers.rb:64:in `block in handle_post_created_edited'

activerecord (7.0.8.1) lib/active_record/relation/batches.rb:71:in `each'

activerecord (7.0.8.1) lib/active_record/relation/batches.rb:71:in `block in find_each'

activerecord (7.0.8.1) lib/active_record/relation/batches.rb:138:in `block in find_in_batches'

activerecord (7.0.8.1) lib/active_record/relation/batches.rb:245:in `block in in_batches'

activerecord (7.0.8.1) lib/active_record/relation/batches.rb:229:in `loop'

activerecord (7.0.8.1) lib/active_record/relation/batches.rb:229:in `in_batches'

activerecord (7.0.8.1) lib/active_record/relation/batches.rb:137:in `find_in_batches'

activerecord (7.0.8.1) lib/active_record/relation/batches.rb:70:in `find_each'

plugins/automation/lib/discourse_automation/event_handlers.rb:14:in `handle_post_created_edited'

plugins/automation/plugin.rb:186:in `block (2 levels) in activate!'

lib/plugin/instance.rb:554:in `block in on'

lib/discourse_event.rb:12:in `block in trigger'

/usr/local/lib/ruby/3.2.0/set.rb:511:in `each_key'

/usr/local/lib/ruby/3.2.0/set.rb:511:in `each'

lib/discourse_event.rb:12:in `trigger'

lib/post_creator.rb:258:in `trigger_after_events'

lib/post_creator.rb:220:in `create'

lib/new_post_manager.rb:318:in `perform_create_post'

lib/new_post_manager.rb:252:in `perform'

app/controllers/posts_controller.rb:201:in `create'

actionpack (7.0.8.1) lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'

actionpack (7.0.8.1) lib/abstract_controller/base.rb:215:in `process_action'

actionpack (7.0.8.1) lib/action_controller/metal/rendering.rb:165:in `process_action'

actionpack (7.0.8.1) lib/abstract_controller/callbacks.rb:234:in `block in process_action'

activesupport (7.0.8.1) lib/active_support/callbacks.rb:118:in `block in run_callbacks'

app/controllers/application_controller.rb:423:in `block in with_resolved_locale'

i18n (1.14.4) lib/i18n.rb:322:in `with_locale'

app/controllers/application_controller.rb:423:in `with_resolved_locale'

activesupport (7.0.8.1) lib/active_support/callbacks.rb:127:in `block in run_callbacks'

activesupport (7.0.8.1) lib/active_support/callbacks.rb:138:in `run_callbacks'

actionpack (7.0.8.1) lib/abstract_controller/callbacks.rb:233:in `process_action'

actionpack (7.0.8.1) lib/action_controller/metal/rescue.rb:23:in `process_action'

actionpack (7.0.8.1) lib/action_controller/metal/instrumentation.rb:67:in `block in process_action'

activesupport (7.0.8.1) lib/active_support/notifications.rb:206:in `block in instrument'

activesupport (7.0.8.1) lib/active_support/notifications/instrumenter.rb:24:in `instrument'

activesupport (7.0.8.1) lib/active_support/notifications.rb:206:in `instrument'

actionpack (7.0.8.1) lib/action_controller/metal/instrumentation.rb:66:in `process_action'

actionpack (7.0.8.1) lib/action_controller/metal/params_wrapper.rb:259:in `process_action'

activerecord (7.0.8.1) lib/active_record/railties/controller_runtime.rb:27:in `process_action'

actionpack (7.0.8.1) lib/abstract_controller/base.rb:151:in `process'

actionview (7.0.8.1) lib/action_view/rendering.rb:39:in `process'

rack-mini-profiler (3.3.1) lib/mini_profiler/profiling_methods.rb:89:in `block in profile_method'

actionpack (7.0.8.1) lib/action_controller/metal.rb:188:in `dispatch'

actionpack (7.0.8.1) lib/action_controller/metal.rb:251:in `dispatch'

actionpack (7.0.8.1) lib/action_dispatch/routing/route_set.rb:49:in `dispatch'

actionpack (7.0.8.1) lib/action_dispatch/routing/route_set.rb:32:in `serve'

actionpack (7.0.8.1) lib/action_dispatch/journey/router.rb:50:in `block in serve'

actionpack (7.0.8.1) lib/action_dispatch/journey/router.rb:32:in `each'

actionpack (7.0.8.1) lib/action_dispatch/journey/router.rb:32:in `serve'

actionpack (7.0.8.1) lib/action_dispatch/routing/route_set.rb:852:in `call'

lib/middleware/omniauth_bypass_middleware.rb:64:in `call'

rack (2.2.9) lib/rack/tempfile_reaper.rb:15:in `call'

rack (2.2.9) lib/rack/conditional_get.rb:40:in `call'

rack (2.2.9) lib/rack/head.rb:12:in `call'

actionpack (7.0.8.1) lib/action_dispatch/http/permissions_policy.rb:38:in `call'

lib/content_security_policy/middleware.rb:12:in `call'

lib/middleware/anonymous_cache.rb:393:in `call'

lib/middleware/csp_script_nonce_injector.rb:12:in `call'

config/initializers/008-rack-cors.rb:14:in `call'

rack (2.2.9) lib/rack/session/abstract/id.rb:266:in `context'

rack (2.2.9) lib/rack/session/abstract/id.rb:260:in `call'

actionpack (7.0.8.1) lib/action_dispatch/middleware/cookies.rb:704:in `call'

actionpack (7.0.8.1) lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'

activesupport (7.0.8.1) lib/active_support/callbacks.rb:99:in `run_callbacks'

actionpack (7.0.8.1) lib/action_dispatch/middleware/callbacks.rb:26:in `call'

actionpack (7.0.8.1) lib/action_dispatch/middleware/debug_exceptions.rb:28:in `call'

actionpack (7.0.8.1) lib/action_dispatch/middleware/show_exceptions.rb:29:in `call'

logster (2.19.1) lib/logster/middleware/reporter.rb:40:in `call'

railties (7.0.8.1) lib/rails/rack/logger.rb:40:in `call_app'

railties (7.0.8.1) lib/rails/rack/logger.rb:27:in `call'

config/initializers/100-quiet_logger.rb:20:in `call'

config/initializers/100-silence_logger.rb:29:in `call'

actionpack (7.0.8.1) lib/action_dispatch/middleware/remote_ip.rb:93:in `call'

actionpack (7.0.8.1) lib/action_dispatch/middleware/request_id.rb:26:in `call'

lib/middleware/enforce_hostname.rb:24:in `call'

rack (2.2.9) lib/rack/method_override.rb:24:in `call'

actionpack (7.0.8.1) lib/action_dispatch/middleware/executor.rb:14:in `call'

rack (2.2.9) lib/rack/sendfile.rb:110:in `call'

actionpack (7.0.8.1) lib/action_dispatch/middleware/host_authorization.rb:131:in `call'

rack-mini-profiler (3.3.1) lib/mini_profiler.rb:191:in `call'

message_bus (4.3.8) lib/message_bus/rack/middleware.rb:60:in `call'

lib/middleware/request_tracker.rb:274:in `call'

railties (7.0.8.1) lib/rails/engine.rb:530:in `call'

railties (7.0.8.1) lib/rails/railtie.rb:226:in `public_send'

railties (7.0.8.1) lib/rails/railtie.rb:226:in `method_missing'

rack (2.2.9) lib/rack/urlmap.rb:74:in `block in call'

rack (2.2.9) lib/rack/urlmap.rb:58:in `each'

rack (2.2.9) lib/rack/urlmap.rb:58:in `call'

unicorn (6.1.0) lib/unicorn/http_server.rb:634:in `process_client'

unicorn (6.1.0) lib/unicorn/http_server.rb:739:in `worker_loop'

unicorn (6.1.0) lib/unicorn/http_server.rb:547:in `spawn_missing_workers'

unicorn (6.1.0) lib/unicorn/http_server.rb:143:in `start'

unicorn (6.1.0) bin/unicorn:128:in `<top (required)>'

vendor/bundle/ruby/3.2.0/bin/unicorn:25:in `load'

vendor/bundle/ruby/3.2.0/bin/unicorn:25:in `<main>'

Wir verwenden die neueste Version von Discourse und dem Automatisierungs-Plugin. Haben Sie eine Idee, wie dies behoben werden kann? Vielen Dank für Ihre Hilfe!

pfaffman · 26. April 2024 um 08:50

Ich weiß nicht, ob es damit zusammenhängt, aber

Sie könnten also versuchen, das Plugin aus Ihrer app.yml zu entfernen.

sam · 29. April 2024 um 00:05

Hmm, wir haben das Repository bereits geleert, daher hat dies nichts mit dem alten Plugin zu tun.

github.com/discourse/discourse-automation

plugin.rb

main

# frozen_string_literal: true

# name: discourse-automation
# about: Allows admins to automate actions through scripts and triggers. Customisation is made through an automatically generated UI.
# meta_topic_id: 195773
# version: 0.1
# authors: jjaffeux
# url: https://github.com/discourse/discourse-automation

after_initialize do
  class ProblemCheck::DiscourseAutomation < ProblemCheck
    self.priority = "low"

    def call
      problem
    end

    private

    def message

This file has been truncated. show original

Wir haben kürzlich ein wenig mit diesem Trigger gespielt, vielleicht hat @Osama einige Ideen.

Gibt es weitere Informationen in Ihren Protokollen @Festinger, was ist die Nachricht?

Können Sie eine neue Automatisierungsregel von Grund auf für dieselbe Aktion erstellen, funktioniert das als Problemumgehung?

Osama · 30. April 2024 um 15:43

Können Sie bitte die Fehlermeldung mitteilen? Sie sollte direkt vor dem Stacktrace angezeigt werden, den Sie geteilt haben.

Festinger · 1. Mai 2024 um 07:12

Vielen Dank für Ihr Feedback.

Bei der Überprüfung der Automatisierungsregeln habe ich festgestellt, dass sich der einer Regel zugewiesene Benutzername geändert hat und wir vergessen haben, den Benutzernamen zu aktualisieren.

Da wir nun den richtigen Benutzernamen zugewiesen haben, sind die Fehler behoben und die Automatisierungsregeln funktionieren wieder.

system · 31. Mai 2024 um 07:12

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

Thema		Antworten	Aufrufe
Discourse Automation Plugin failing with an 'internal server error' Bug automation	11	157	2. Mai 2025
Polls disabled caused 500 error Support	10	704	26. Juli 2018
The discourse stopped working with error 500 Internal Server Error Bug	2	3017	7. März 2017
Internal Server Error when creating new topic Bug	3	70	10. April 2025
Translation missing: en.dashboard.problem.discourse_automation Bug	6	111	20. August 2024

500 error mit Automation Plugin

Verwandte Themen