Just Screenly-Logo and no Web-GUI

Anthias
1

Hey guys,

I set up Anthias on a Raspberry Pi 4 Model B Rev 1.5 around 1,5 month ago.

It plays 15 pictures in a loop and I´m pretty happy with it.

Unfortunately it stopped working from the sudden and only displays the Screenly-Logo.
The Web-GUI pretents to load, but doesn´t appear.

SSH access is possible.

I already powercyled the Pi and tried several reboots without success.

May you please help me out how I can start troubleshooting? I’m at a bit of a loss right now. Unfortunately, the display is about 300km away.

I hope I can fix it remotely without driving over to replace the hardware.

Thank you in advance
Mats

systemd-analyze blame:

$ systemd-analyze blame
2min 431ms wg-quick@wg0.service
27.576s cloudflared.service
24.011s docker.service
8.318s NetworkManager-wait-online.service
6.499s e2scrub_reap.service
5.290s containerd.service
3.499s apt-daily.service
2.025s dev-mmcblk0p2.device
1.717s ModemManager.service
1.317s plymouth-start.service
1.289s systemd-binfmt.service
1.057s rpi-eeprom-update.service
1.017s networking.service
926ms ssh.service
892ms systemd-timesyncd.service
886ms NetworkManager.service
821ms systemd-journal-flush.service
673ms systemd-udev-trigger.service
601ms avahi-daemon.service
592ms bluetooth.service
575ms proc-sys-fs-binfmt_misc.mount
570ms polkit.service
551ms plymouth-read-write.service
534ms dbus.service
520ms keyboard-setup.service
512ms console-setup.service
501ms systemd-logind.service
491ms systemd-tmpfiles-setup.service
488ms systemd-fsck@dev-disk-by\x2dpartuuid-4a07fd05\x2d01.service
464ms wpa_supplicant.service
453ms run-rpc_pipefs.mount
398ms systemd-journald.service
383ms raspi-config.service
355ms sshswitch.service
293ms rc-local.service
267ms user@1000.service
226ms systemd-rfkill.service
190ms logrotate.service
187ms dev-mqueue.mount
182ms systemd-remount-fs.service
182ms sys-kernel-debug.mount
176ms sys-kernel-tracing.mount
175ms systemd-random-seed.service
168ms fake-hwclock.service
168ms systemd-sysctl.service
166ms systemd-sysusers.service
156ms kmod-static-nodes.service
152ms modprobe@configfs.service
143ms alsa-restore.service
142ms modprobe@drm.service

2

@matsmats, would you be able to provide the server and the viewer logs? Detailed steps on how to do them can be seen here. I would recommend you to run the following:

cd ~/screenly
docker compose logs -ft anthias-server # on one terminal session/tab/window
docker compose logs -ft anthias-viewer # on another terminal session/tab/window

If you have a spare hardware nearby and can’t wait, you can do the following:

  • Backup your Anthias data (limited to assets, asset metadata, and settings).
    • As a limitation, you won’t be able to backup your system settings like network settings (if there are any).
    • SSH to your device and do a software upgrade by running the following:
cd screenly/
./bin/run_upgrade.sh
  • Alternatively, you can also run the install script to update Anthias: bash <(curl -sL https://install-anthias.srly.io)

I hope this helps.

3

Hey mate,
thank you for your quick reply.
I used your commands and didn´t find anything conspicous in the logs.
But while digging deeper I noticed that my SSH-connection was very slow and patchy.
What should I say - in summary it was just a throttled mobile data connection that was to slow to show the web GUI and in coinsidence the assets we´re just expired.

Anyways. Thank you for your help and have a nice weekend :slight_smile:

1 Like