Web UI not reachable

I’ve sent a log package now.

I did not receive it, did you check include support?

Did it again with the check.

But what would that improve? The Pi’s internal memory is fixed to 1 GB, and now that I removed the old snap package versions I am at 66 % usage, which should be OK?

root@syncloud:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       6.9G  4.3G  2.3G  66% /
devtmpfs        325M     0  325M   0% /dev
tmpfs           455M  2.3M  453M   1% /dev/shm
tmpfs           455M   12M  443M   3% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           455M     0  455M   0% /sys/fs/cgroup
/dev/loop2      142M  142M     0 100% /snap/gogs/249
/dev/loop0      173M  173M     0 100% /snap/users/299
/dev/loop1      490M  490M     0 100% /snap/nextcloud/812
/dev/loop3      267M  267M     0 100% /snap/pihole/556
/dev/loop4      131M  131M     0 100% /snap/platform/2189
/dev/loop5      449M  449M     0 100% /snap/grocy/79
/dev/loop6      248M  248M     0 100% /snap/syncthing/134
/dev/sda1       288G   15G  259G   6% /opt/disk/external

Anyways, some more info: The openldap service seems to have the timeout issue:

root@syncloud:~# snap start platform.api
Started.
root@syncloud:~# snap start platform.authelia
Started.
root@syncloud:~# snap start platform.backend
Started.
root@syncloud:~# snap start platform.nginx-public
Started.
root@syncloud:~# snap start platform.openldap
error: cannot perform the following tasks:
- Run service command "start" for services ["openldap"] of snap "platform" (systemctl command [start snap.platform.openldap.service] failed with exit status 1: Job for snap.platform.openldap.service failed because a timeout was exceeded.
See "systemctl status snap.platform.openldap.service" and "journalctl -xe" for details.
)
root@syncloud:~# snap start platform
Started.
[Everything working now]

And I found this conspicuous log message, maybe it tells you something:

Dec 07 10:43:37 syncloud ntpd[4439]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
Dec 07 10:43:37 syncloud ntpd[4439]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2022-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
Dec 07 10:43:37 syncloud ntpd[4439]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 711 days ago

I now added the following line to my crontab, which appears to work. :person_shrugging:

@reboot snap start platform.api; snap start platform.authelia; snap start platform.backend; snap start platform.nginx-public; snap start platform.openldap; snap start platform

ok, platform has default 30 seconds start timeout, but for other apps I switched to much higher number. your device is obviously overloaded and app updates make it even worse as no one is really optimizing their apps to work on 1g ram RPi :slight_smile:

So I pushed an update, I will let you know when it is in the store, let’s try to remove the manual reboot hack and test the normal behaviour when it is ready.

The fix is out, could you update the system (v2192) from Settings - Updates, remove the xrom hack and test either by rebooting the device or by running this command:

snap restart platform

Better, but not fully fixed. On startup the web UI is still not reachable, I have to run snap start platform, which takes ~90 seconds, then everything works. snap restart platform does nothing, I have to do start.

Can you remove the cron restart the device wait for 10 mins if it does not come up run:

snap start platform

and send me the output please, also send the logs from settings - support after it starts

Sorry for the delay!

root@syncloud:~# date
Tue 17 Dec 2024 01:14:44 PM UTC
root@syncloud:~# sudo reboot now
[...]
root@syncloud:~# date; systemctl status snap.platform.*
Tue 17 Dec 2024 01:31:19 PM UTC
root@syncloud:~# snap start platform
Started.
root@syncloud:~# date
Tue 17 Dec 2024 01:32:52 PM UTC

So the services were not running on startup and manually starting the services took about 90 s.
I’ve sent a log package after running the above commands.

sorry no logs, did you include support checkbox?

Strange, the e-mail that I received was also sent to support@syncloud.it; I’ve forwarded it again to that address.

Did you receive the logs via support@syncloud.it?

Sorry I did actually.
Still cannot see anything stopping platfrom from starting automatically, another test is to run also this command:

journalctl --no-pager  -u snap.platform.*

Again without cron and after the reboot.

root@syncloud:~# date; shutdown -r now
Mon 30 Dec 2024 10:52:23 AM UTC
root@syncloud:~# Connection to [...] closed by remote host.
[...]
root@syncloud:~# date; journalctl --no-pager -u snap.platform.*
Mon 30 Dec 2024 10:56:32 AM UTC
Failed to add filter for units: No data available
[...]
root@syncloud:~# date; journalctl --no-pager -u snap.platform.*
Mon 30 Dec 2024 11:02:09 AM UTC
Failed to add filter for units: No data available
root@syncloud:~# snap start platform
Started.
root@syncloud:~# date; journalctl --no-pager -u snap.platform.*
Mon 30 Dec 2024 11:03:46 AM UTC
-- Logs begin at Thu 2019-02-14 10:11:59 UTC, end at Mon 2024-12-30 11:03:46 UTC. --
Dec 30 11:02:31 syncloud systemd[1]: Started Service for snap application platform.api.
Dec 30 11:02:32 syncloud systemd[1]: Started Service for snap application platform.authelia.
Dec 30 11:02:32 syncloud systemd[1]: Started Service for snap application platform.backend.
Dec 30 11:02:32 syncloud systemd[1]: Starting Service for snap application platform.nginx-public...
Dec 30 11:03:01 syncloud platform.nginx-public[1394]: nginx: the configuration file /var/snap/platform/current/nginx.conf syntax is ok
Dec 30 11:03:01 syncloud platform.nginx-public[1394]: nginx: configuration file /var/snap/platform/current/nginx.conf test is successful
Dec 30 11:03:02 syncloud systemd[1]: Started Service for snap application platform.nginx-public.
Dec 30 11:03:02 syncloud systemd[1]: Starting Service for snap application platform.openldap...
Dec 30 11:03:02 syncloud platform.openldap[1481]: +++ dirname /snap/platform/2196/openldap/sbin/slapd.sh
Dec 30 11:03:02 syncloud platform.openldap[1481]: ++ cd /snap/platform/2196/openldap/sbin
Dec 30 11:03:02 syncloud platform.openldap[1481]: ++ cd ..
Dec 30 11:03:02 syncloud platform.openldap[1481]: ++ pwd
Dec 30 11:03:02 syncloud platform.openldap[1481]: + DIR=/snap/platform/2196/openldap
Dec 30 11:03:02 syncloud platform.openldap[1481]: ++ echo /snap/platform/2196/openldap/lib/aarch64-linux-gnu
Dec 30 11:03:02 syncloud platform.openldap[1481]: + LIBS=/snap/platform/2196/openldap/lib/aarch64-linux-gnu
Dec 30 11:03:02 syncloud platform.openldap[1481]: ++ echo /snap/platform/2196/openldap/usr/lib/aarch64-linux-gnu
Dec 30 11:03:02 syncloud platform.openldap[1481]: + LIBS=/snap/platform/2196/openldap/lib/aarch64-linux-gnu:/snap/platform/2196/openldap/usr/lib/aarch64-linux-gnu
Dec 30 11:03:02 syncloud platform.openldap[1481]: ++ echo /snap/platform/2196/openldap/usr/lib
Dec 30 11:03:02 syncloud platform.openldap[1481]: + LIBS=/snap/platform/2196/openldap/lib/aarch64-linux-gnu:/snap/platform/2196/openldap/usr/lib/aarch64-linux-gnu:/snap/platform/2196/openldap/usr/lib
Dec 30 11:03:02 syncloud platform.openldap[1481]: + /snap/platform/2196/openldap/lib/aarch64-linux-gnu/ld-2.28.so --library-path /snap/platform/2196/openldap/lib/aarch64-linux-gnu:/snap/platform/2196/openldap/usr/lib/aarch64-linux-gnu:/snap/platform/2196/openldap/usr/lib /snap/platform/2196/openldap/usr/sbin/slapd -h 'ldap://127.0.0.1:389 ldapi://%2Fvar%2Fsnap%2Fplatform%2F2196%2Fopenldap.socket' -F /var/snap/platform/current/slapd.d
Dec 30 11:03:39 syncloud slapd[1507]: @(#) $OpenLDAP: slapd 2.4.57+dfsg-1~bpo10+1 (Jan 30 2021 06:59:51) $
                                              Debian OpenLDAP Maintainers <pkg-openldap-devel@lists.alioth.debian.org>
Dec 30 11:03:42 syncloud slapd[1518]: slapd starting
Dec 30 11:03:42 syncloud systemd[1]: Started Service for snap application platform.openldap.
Dec 30 11:03:46 syncloud platform.api[1362]: Started api

Why aren’t there any logs from the past? :face_with_raised_eyebrow: Ugh …

Yeah not sure, but did it start automatically this time?

No, manually doing snap start platform was necessary.

Can you try another sd card?