[BUG] After updating, Bitfocus doesn't start

[steven3003202]

Is this a bug in companion itself or a module?

• I believe this to be a bug in companion

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I updated to the latest 3.5.1 and see this massage, i didn't do anything

Steps To Reproduce

No response

Expected Behavior

No response

Environment (please complete the following information)

- OS: Windows
- Browser:
- Companion Version: 3.5.1

Additional context

No response

[alalba75]

me too

from terminal:
Feb 06 18:39:52 raspberrypi systemd[1]: companion.service: Scheduled restart job, restart counter is at 5.
Feb 06 18:39:52 raspberrypi systemd[1]: Stopped companion.service - Bitfocus Companion.
Feb 06 18:39:52 raspberrypi systemd[1]: companion.service: Consumed 1.073s CPU time.
Feb 06 18:39:52 raspberrypi systemd[1]: companion.service: Start request repeated too quickly.
Feb 06 18:39:52 raspberrypi systemd[1]: companion.service: Failed with result 'exit-code'.
Feb 06 18:39:52 raspberrypi systemd[1]: Failed to start companion.service - Bitfocus Companion.

[Julusian]

Can you provide some more logs?
Those logs say that companion restarted too many times in a short period, but nothing about why it restarted

[Julusian]

I updated to the latest 3.5.1 and see this massage, i didn't do anything

That can happen if you ran a 3.5 beta at any point before going back to 3.4
Because your 3.5 config will then be preserved, so what you see when opening companion might not be what you expect.

This dialog is normal, and wont stop companion launching.
Logs from %APPDATA%/companion/logs please

[cvorn]

Same here - won't start after updating.

companion-2025-02-07.0.log

[Michael-Rempel]

+1 I want to rely on Companion for my broadcasting, but failures like this make it prohibitive. It needs to be far more reliable for users to count on it.