Yeti-switch installed this April stopped working after update

Yeti installation and upgrade
1

After running apt-update and apt-upgrade, Yeti works for incoming and outgoing calls (I don’t know about saving data to CDR), but it’s impossible to log in – every login attempt ends with the message:

“We’re sorry, but something went wrong.
If you are the application owner check the logs for more information.”

Please help me, I performed this on production and access to yet-web is really urgent.

root@localhost:~# service yeti-web status
● yeti-web.service - YETI system web interface
     Loaded: loaded (/lib/systemd/system/yeti-web.service; enabled; preset: enabled)
     Active: active (running) since Thu 2025-09-04 03:09:55 CEST; 8min ago
       Docs: https://yeti-switch.org/docs/
   Main PID: 701 (bundle)
      Tasks: 37 (limit: 9478)
     Memory: 624.8M
        CPU: 27.508s
     CGroup: /system.slice/yeti-web.service
             ├─ 701 "puma 6.5.0 (unix:///run/yeti/yeti-unicorn.sock) [/]"
             ├─1590 "puma: cluster worker 0: 701 [/]"
             └─1597 "puma: cluster worker 1: 701 [/]"
Sep 04 03:14:24 localhost.localdomain ruby[1590]: /opt/yeti-web/vendor/bundle/ruby/3.3.0/gems/puma-6.5.0/lib/puma/server.>
Sep 04 03:14:24 localhost.localdomain ruby[1590]: /opt/yeti-web/vendor/bundle/ruby/3.3.0/gems/puma-6.5.0/lib/puma/server.>
Sep 04 03:14:24 localhost.localdomain ruby[1590]: /opt/yeti-web/vendor/bundle/ruby/3.3.0/gems/puma-6.5.0/lib/puma/thread_>
Sep 04 03:14:24 localhost.localdomain ruby[1590]: 2025-09-04 03:14:24.410432 I [1590:worker-2] Rails -- sentry -- [Transp>
Sep 04 03:14:25 localhost.localdomain ruby[1590]: 2025-09-04 03:14:25.418774 E [1590:worker-2 logging_helper.rb:9] Rails >
Sep 04 03:14:25 localhost.localdomain ruby[1590]: 2025-09-04 03:14:25.418993 I [1590:worker-2] Rails -- sentry -- Unrepor>
Sep 04 03:14:25 localhost.localdomain ruby[1590]: LINE 10:  WHERE a.attrelid = '"class4"."gateway_throttling_profiles"'...
Sep 04 03:14:25 localhost.localdomain ruby[1590]:                              ^
Sep 04 03:14:25 localhost.localdomain ruby[1590]: 2025-09-04 03:14:25.419128 E [1590:worker-2 logging_helper.rb:9] Rails >
Sep 04 03:16:18 localhost.localdomain ruby[701]: [701] 2025-09-04 03:16:18 +0200: PumaWorkerKiller: Consuming 749.96875 m>
lines 1-23/23 (END)...skipping...
● yeti-web.service - YETI system web interface
     Loaded: loaded (/lib/systemd/system/yeti-web.service; enabled; preset: enabled)
     Active: active (running) since Thu 2025-09-04 03:09:55 CEST; 8min ago
       Docs: https://yeti-switch.org/docs/
   Main PID: 701 (bundle)
      Tasks: 37 (limit: 9478)
     Memory: 624.8M
        CPU: 27.508s
     CGroup: /system.slice/yeti-web.service
             ├─ 701 "puma 6.5.0 (unix:///run/yeti/yeti-unicorn.sock) [/]"
             ├─1590 "puma: cluster worker 0: 701 [/]"
             └─1597 "puma: cluster worker 1: 701 [/]"
Sep 04 03:14:24 localhost.localdomain ruby[1590]: /opt/yeti-web/vendor/bundle/ruby/3.3.0/gems/puma-6.5.0/lib/puma/server.rb:468:in `process_client'
Sep 04 03:14:24 localhost.localdomain ruby[1590]: /opt/yeti-web/vendor/bundle/ruby/3.3.0/gems/puma-6.5.0/lib/puma/server.rb:249:in `block in run'
Sep 04 03:14:24 localhost.localdomain ruby[1590]: /opt/yeti-web/vendor/bundle/ruby/3.3.0/gems/puma-6.5.0/lib/puma/thread_pool.rb:166:in `block in spawn_thread'
Sep 04 03:14:24 localhost.localdomain ruby[1590]: 2025-09-04 03:14:24.410432 I [1590:worker-2] Rails -- sentry -- [Transport] Sending envelope with items [event, client_report] 26d4250b00734c43b17bec09cb439daa to Sentry
Sep 04 03:14:25 localhost.localdomain ruby[1590]: 2025-09-04 03:14:25.418774 E [1590:worker-2 logging_helper.rb:9] Rails -- sentry -- Event sending failed: Failed to open TCP connection to errors.yeti-switch.org:443 (execution expired)
Sep 04 03:14:25 localhost.localdomain ruby[1590]: 2025-09-04 03:14:25.418993 I [1590:worker-2] Rails -- sentry -- Unreported Event: PG::UndefinedTable: ERROR:  relation "class4.gateway_throttling_profiles" does not exist (PG::UndefinedT>
Sep 04 03:14:25 localhost.localdomain ruby[1590]: LINE 10:  WHERE a.attrelid = '"class4"."gateway_throttling_profiles"'...
Sep 04 03:14:25 localhost.localdomain ruby[1590]:                              ^
Sep 04 03:14:25 localhost.localdomain ruby[1590]: 2025-09-04 03:14:25.419128 E [1590:worker-2 logging_helper.rb:9] Rails -- sentry -- exception happened in background worker: Failed to open TCP connection to errors.yeti-switch.org:443 (>
Sep 04 03:16:18 localhost.localdomain ruby[701]: [701] 2025-09-04 03:16:18 +0200: PumaWorkerKiller: Consuming 749.96875 mb with master and 2 workers.
2

After executing:

root@localhost:~# cd /opt/yeti-web && RAILS_ENV=production ./bin/bundle.sh exec rake db:migrate

Everything started working. Is there anything else I need to do? I don’t want anything to break later.

One more question: how to replace the favicon.ico with my own in yeti-web? Currently, there isn’t any favicon, and I would like to add an icon.

3

Usually you also should upgrade SEMS and configure it according to documentation.

4

There was no installation candidate for SEMS, sems was configured correctly, and connections worked both ways. The problem was accessing the panel. As mentioned above, the only command that fixed it was:

“root@localhost:~# cd /opt/yeti-web && RAILS_ENV=production ./bin/bundle.sh exec rake db:migrate”

That fixed the problem. Although I don’t think additional migrations should be necessary for the same version of Yeti (which were previously performed during installation – I’ve been using Yeti for quite a few years – and such a requirement has never been present before).

5

You upgraded your yeti so it is not same version.