gui having issue after applying update of yeti-web 1.12.67-1
yes, this is known problem
after updating billing is not working anymore, please fix it as soon as possible
can I downgrade to a working version of yeti-web? all these errors are related to this latest upgrade
I’ve live traffic and 342380 pending events, i tried to restart yeti-cdr-billing@cdr_billing but it doesn’t restart for an error with yeti-web
Apr 11 12:36:03 Debian-bullseye-latest-amd64-base systemd[1]: Started YETI CDR billing: cdr_billing.
Apr 11 12:36:03 Debian-bullseye-latest-amd64-base ruby[126987]: Calling `DidYouMean::SPELL_CHECKERS.merge!(error_name => spell_checker)' has been deprecated. Please call `DidYouMean.correct_error(error_name, spell_checker)' instead.
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: rake aborted!
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: ArgumentError: wrong number of arguments (given 2, expected 1)
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/pgq_config.rb:17:in `config'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/pgq_config.rb:11:in `initialize'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/pgq_env.rb:33:in `new'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/pgq_env.rb:33:in `initialize'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/Rakefile:8:in `new'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/Rakefile:8:in `block (2 levels) in <top (required)>'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:63:in `load'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:63:in `kernel_load'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/bundler-2.1.4/lib/bundler/cli/exec.rb:28:in `run'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/bundler-2.1.4/lib/bundler/cli.rb:476:in `exec'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor.rb:399:in `dispatch'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/bundler-2.1.4/lib/bundler/cli.rb:30:in `dispatch'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/bundler-2.1.4/lib/bundler/vendor/thor/lib/thor/base.rb:476:in `start'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/bundler-2.1.4/lib/bundler/cli.rb:24:in `start'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/bundler-2.1.4/exe/bundle:46:in `block in <top (required)>'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/bundler-2.1.4/lib/bundler/friendly_errors.rb:123:in `with_friendly_errors'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundle/ruby/3.2.0/gems/bundler-2.1.4/exe/bundle:34:in `<top (required)>'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundler/bin/bundle:25:in `load'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: /opt/yeti-web/pgq-processors/vendor/bundler/bin/bundle:25:in `<main>'
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: Tasks: TOP => pgq:worker
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base ruby[126987]: (See full trace by running task with --trace)
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base systemd[1]: yeti-cdr-billing@cdr_billing.service: Main process exited, code=exited, status=1/FAILURE
Apr 11 12:36:04 Debian-bullseye-latest-amd64-base systemd[1]: yeti-cdr-billing@cdr_billing.service: Failed with result 'exit-code'.
/opt/yeti-web/pgq-processors/pgq_config.rb:17:
replace
@config ||= YAML.safe_load(File.read(config_file), [Symbol])[section]
with
@config ||= YAML.safe_load(File.read(config_file), permitted_classes: [Symbol])[section]
GREAT! it started billing again and decreasing pending events! thank you very much for your help!