TVE issues again

Looks like I'm having another Chromium issue ...

Server is Ubuntu 22.04 on bare metal
Channels DVR is 2022.07.19.2302

2022/07/20 20:15:41.645516 [ERR] Failed to start stream for ch6199: TVE: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/07/20 20:15:41.665340 [HLS] Couldn't generate stream playlist for ch6199-dANY-ip172.16.0.1: TVE: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/07/20 20:15:41.665364 [HLS] Stopping transcoder session ch6199-dANY-ip172.16.0.1
2022/07/20 20:15:42.783260 [ERR] Failed to clean up /usr/channelsdvr/Streaming/ch6199-dANY-ip172.16.0.1-4267009442: unlinkat /usr/channelsdvr/Streaming/ch6199-dANY-ip172.16.0.1-4267009442/cache: directory not empty
2022/07/20 20:15:43.717084 [ERR] Failed to start stream for ch6199: TVE: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/07/20 20:15:43.754850 [HLS] Couldn't generate stream playlist for ch6199-dANY-ip172.16.0.1: TVE: chrome failed to start:
/system.slice/channels-dvr.service is not a snap cgroup
2022/07/20 20:15:43.754877 [HLS] Stopping transcoder session ch6199-dANY-ip172.16.0.1
2022/07/20 20:15:44.882516 [ERR] Failed to clean up /usr/channelsdvr/Streaming/ch6199-dANY-ip172.16.0.1-821629520: unlinkat /usr/channelsdvr/Streaming/ch6199-dANY-ip172.16.0.1-821629520/cache: directory not empty
2022/07/20 20:17:33.321506 [TRS] DNS: OK: Resolved host via system DNS

Running through the Channels Diagnostics page indicates a corrupt Chromium install; I "Click here to install Chromium" and unfortunately still have an issue. If I click it several times, it'll upgrade and test OK, but then I can stream TVE exactly once. On second attempt, it goes back to the same failed state.

Submitted diags as b1bfc133-c8a1-4162-95f9-b32f18451e8f

Please let me know if I'm doing something wrong or that I shouldn't be doing!

Does Ubuntu offer other avenues to install Chrome/Chromium at the system level beyond snaps? Ubuntu's Chrome snaps have a long history of being broken in myriad ways.

(Ubuntu's transition to firstly cloud-init, and now snaps, are the reasons why I will use an Ubuntu-based distro ever again.)

1 Like

Yes, but it's not particularly nice. Unsupported/untrusted PPA and all that.

I'm not wedded to ubuntu by any means; honestly if I could just run on Solaris I would... (yes, I'm old. No neckbeard though, I promise.)

I don't like what Fedora is up to. Now Ubuntu is making a mess with snaps and such. Really struggling to find a Linux server distro that'll make life easy and has broad package availability.

I switched from Ubuntu to Arch; from Arch to Fedora. However, I agree with some of the out-there measures FESCo is considering, especially with RHEL trickle-down.

Intel's Clear seems viable, but I'm currently leaning more towards SUSE.

(Of course, I completely understand your Solaris tilt; I remember using Solaris back at university in the late 90s. But presently I prefer OpenBSD if possible for server applications.

… Maybe they might consider OpenBSD binaries for Channels, considering it has quite decent Golang support. If there's enough community support for OBSD, I might even consider donating a cloud server solely for building.)

I had a similar issue a week ago. I reboot the server and it started working again. In my case it was during the channel scan when doing a new setup.

Same versions as you.