Anyone come across this error after upgrading from 1.11 to latest 1.12. it happen on gateway and customer auth creation and updates.
Apr 11 19:19:52 yetiswitch yeti-web[170604]: [98d8c0e0-ddd7-41d5-a001-5fe1ef41a04c] Started PATCH “/customers_auths/20119” for 192.168.113.122 at 2023-04-11 19:19:52 +0200
Apr 11 19:19:52 yetiswitch yeti-web[170604]: [98d8c0e0-ddd7-41d5-a001-5fe1ef41a04c] Processing by CustomersAuthsController#update as HTML
Apr 11 19:19:52 yetiswitch yeti-web[170604]: [98d8c0e0-ddd7-41d5-a001-5fe1ef41a04c] Parameters: {“utf8”=>“✓”, “authenticity_token”=>“cOzWKuqToVTidpENj_IMEADAFcRXGR65VG-VFWFqTrAV8V03Kn8N64ZyOdrQDdZt1Y9-zQGPRVFswg6H9DA5Hg”, “customers_auth”=>{“name”=>“PTTTest”, “enabled”=>“0”, “reject_calls”=>“0”, “customer_id”=>“12”, “account_id”=>“29”, “check_account_balance”=>“0”, “gateway_id”=>“32”, “require_incoming_auth”=>“0”, “rateplan_id”=>“14”, “routing_plan_id”=>“6”, “dst_numberlist_id”=>“”, “src_numberlist_id”=>“”, “dump_level_id”=>“0”, “enable_audio_recording”=>“0”, “capacity”=>“”, “cps_limit”=>“”, “allow_receive_rate_limit”=>“0”, “send_billing_information”=>“0”, “transport_protocol_id”=>“”, “ip”=>“191.81.195.88, 192.168.112.36, 192.168.116.36, 192.168.116.44, 192.168.112.44, 192.168.112.39, 192.168.116.34”, “pop_id”=>“6”, “src_prefix”=>“2711088, 2711095, 2711028”, “src_number_min_length”=>“8”, “src_number_max_length”=>“100”, “dst_prefix”=>“272232000000”, “dst_number_min_length”=>“8”, “dst_number_max_length”=>“100”, “uri_domain”=>“”, “from_domain”=>“”, “to_domain”=>“”, “x_yeti_auth”=>“”, “diversion_policy_id”=>“1”, “diversion_rewrite_rule”=>“”, “diversion_rewrite_result”=>“”, “src_numberlist_use_diversion”=>“0”, “src_name_field_id”=>“1”, “src_name_rewrite_rule”=>“”, “src_name_rewrite_result”=>“”, “src_number_field_id”=>“1”, “src_rewrite_rule”=>“”, “src_rewrite_result”=>“”, “dst_number_field_id”=>“1”, “dst_rewrite_rule”=>“”, “dst_rewrite_result”=>“”, “lua_script_id”=>“”, “cnam_database_id”=>“”, “radius_auth_profile_id”=>“”, “src_number_radius_rewrite_rule”=>“”, “src_number_radius_rewrite_result”=>“”, “dst_number_radius_rewrite_rule”=>“”, “dst_number_radius_rewrite_result”=>“”, “radius_accounting_profile_id”=>“”, “tag_action_id”=>“3”, “tag_action_value”=>[“20”]}, “commit”=>“Update Customers auth”, “id”=>“20119”}
Apr 11 19:19:52 yetiswitch yeti-web[170604]: [98d8c0e0-ddd7-41d5-a001-5fe1ef41a04c] Completed 500 Internal Server Error in 75ms (Allocations: 16009)
Apr 11 19:19:52 yetiswitch yeti-web[170604]: [98d8c0e0-ddd7-41d5-a001-5fe1ef41a04c] [98d8c0e0-ddd7-41d5-a001-5fe1ef41a04c] ActiveRecord::StatementInvalid (PG::InternalError: ERROR: No such queue#012CONTEXT: PL/pgSQL function pgq.insert_event(text,text,text,text,text,text,text) line 24 at RETURN#012PL/pgSQL function pgq.insert_event(text,text,text) line 18 at RETURN#012):#012[98d8c0e0-ddd7-41d5-a001-5fe1ef41a04c] #012[98d8c0e0-ddd7-41d5-a001-5fe1ef41a04c] app/models/concerns/pg_event.rb:19:in pgq_insert_event'#012[98d8c0e0-ddd7-41d5-a001-5fe1ef41a04c] app/models/concerns/pg_event.rb:40:in pg_event!‘#012[98d8c0e0-ddd7-41d5-a001-5fe1ef41a04c] app/models/concerns/pg_event.rb:36:in pg_record_update'#012[98d8c0e0-ddd7-41d5-a001-5fe1ef41a04c] app/admin/routing/customers_auths.rb:97:in update’#012[98d8c0e0-ddd7-41d5-a001-5fe1ef41a04c] config/initializers/instrumentation_notification.rb:32:in block in process_action'#012[98d8c0e0-ddd7-41d5-a001-5fe1ef41a04c] config/initializers/instrumentation_notification.rb:31:in process_action’