# Problem updating system **URL:** \ **Category:** Access Issues\ **Created:** [3 January 2022 21:51 UTC](https://syncloud.discourse.group/t/problem-updating-system/147 "2022-01-03T21:51:39Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![docvalium](https://avatars.discourse-cdn.com/v4/letter/d/fbc32d/32.png) [@docvalium](https://syncloud.discourse.group/u/docvalium)\ **Post date:** [3 January 2022 21:51 UTC](https://syncloud.discourse.group/t/problem-updating-system/147/1 "2022-01-03T21:51:39Z")
Hi, i have recently run into problems updating the system. I have tried many times doing it via the web interface, where the circles just keep spinning for hours and when i reconnect I am back at the option to start the update. Today I have tried to do it via ssh but I do get an error message and still the update fails. > root@odroid-xu3and4:~# snap refresh platform > error: cannot perform the following tasks: > > - Run post-refresh hook of “platform” snap if present (run hook “post-refresh”: > > * * * > > 2022-01-03 21:36:04,252 - path\_checker - INFO - real link path: /opt/disk/external > 2022-01-03 21:36:04,252 - path\_checker - INFO - external disk path: /opt/disk/external > 2022-01-03 21:36:04,253 - path\_checker - INFO - link exists: True > cert/generator.go:80 certificate info {“category”: “certificate”, “valid days”: -31, “real”: true} > 2022/01/03 21:36:05 [INFO] acme: Registering account for [xxx@gmx.net](mailto:xxx@gmx.net) > cert/generator.go:66 unable to generate certificate: domain is not set {“category”: “certificate”} > cert/fake.go:50 generating fake certificate {“category”: “certificate”} > 2022/01/03 21:36:05 reloading platform.nginx-public > 2022/01/03 21:36:05 systemctl output: Job for snap.platform.nginx-public.service failed. See ‘systemctl status snap.platform.nginx-public.service’ and ‘journalctl -xn’ for details. > 2022/01/03 21:36:05 exit status 1 > Traceback (most recent call last): > File “/snap/platform/2112291188/meta/hooks/post-refresh”, line 5, in > PlatformInstaller().post\_refresh() > File “/snap/platform/current/python/usr/local/lib/python3.8/site-packages/syncloud\_platform-2112291188-py3.8.egg/syncloud\_platform/installer.py”, line 77, in post\_refresh > File “/snap/platform/current/python/usr/local/lib/python3.8/site-packages/syncloud\_platform-2112291188-py3.8.egg/syncloud\_platform/installer.py”, line 47, in init\_services > File “/snap/platform/current/python/usr/local/lib/python3.8/subprocess.py”, line 415, in check\_output > return run(\*popenargs, stdout=PIPE, timeout=timeout, check=True, > File “/snap/platform/current/python/usr/local/lib/python3.8/subprocess.py”, line 516, in run > raise CalledProcessError(retcode, process.args, > subprocess.CalledProcessError: Command ‘/snap/platform/current/bin/cli cert’ returned non-zero exit status 1. > -----) > root@odroid-xu3and4:~# systemctl status snap.platform.nginx-public.service -l > ● snap.platform.nginx-public.service - Service for snap application platform.nginx-public > Loaded: loaded (/etc/systemd/system/snap.platform.nginx-public.service; enabled) > Active: active (running) since Mon 2022-01-03 21:36:20 UTC; 3min 54s ago > Main PID: 3734 (nginx) > CGroup: /system.slice/snap.platform.nginx-public.service > ├─3734 nginx: master process /snap/platform/2110221095/nginx/sbin/nginx -c /var/snap/platform/current/nginx.conf -g error\_log /var/snap/platform/common/log/nginx\_public\_error.log warn > ├─3737 nginx: worker process > ├─3738 nginx: worker process > ├─3739 nginx: worker process > └─3740 nginx: worker process > > Jan 03 21:36:20 odroid-xu3and4 platform.nginx-public[3654]: nginx: [alert] could not open error log file: open() “/drone/src/nginx/build/nginx/logs/error.log” failed (2: No such file or directory) > Jan 03 21:36:20 odroid-xu3and4 platform.nginx-public[3654]: nginx: the configuration file /var/snap/platform/current/nginx.conf syntax is ok > Jan 03 21:36:20 odroid-xu3and4 platform.nginx-public[3654]: nginx: configuration file /var/snap/platform/current/nginx.conf test is successful > Jan 03 21:36:20 odroid-xu3and4 platform.nginx-public[3654]: nginx: [alert] could not open error log file: open() “/drone/src/nginx/build/nginx/logs/error.log” failed (2: No such file or directory) > Jan 03 21:36:20 odroid-xu3and4 nginx[3738]: odroid-xu3and4 nginx: ::1 - - [03/Jan/2022:21:36:20 +0000] “” 400 0 “-” “-” > Jan 03 21:36:20 odroid-xu3and4 systemd[1]: Started Service for snap application platform.nginx-public. > root@odroid-xu3and4:~# I don’t know if that means the problems are caused by a problem with certificates, because that is also a problem of mine: certificates would not renew although ports were open for extended periods. Any ideas are appreciated ```auto type or paste code here ``` ---
**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\ **Post date:** [3 January 2022 22:03 UTC](https://syncloud.discourse.group/t/problem-updating-system/147/2 "2022-01-03T22:03:55Z")
Are you using custom domain activation? ---
**Author:** ![docvalium](https://avatars.discourse-cdn.com/v4/letter/d/fbc32d/32.png) [@docvalium](https://syncloud.discourse.group/u/docvalium)\ **Post date:** [3 January 2022 22:21 UTC](https://syncloud.discourse.group/t/problem-updating-system/147/3 "2022-01-03T22:21:05Z")
No, it’s a xxx.syncloud.it domain. ---
**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\ **Post date:** [3 January 2022 22:29 UTC](https://syncloud.discourse.group/t/problem-updating-system/147/4 "2022-01-03T22:29:02Z")
Can you show this: ```auto ls -la /var/snap/platform/current/ ``` ---
**Author:** ![docvalium](https://avatars.discourse-cdn.com/v4/letter/d/fbc32d/32.png) [@docvalium](https://syncloud.discourse.group/u/docvalium)\ **Post date:** [3 January 2022 22:44 UTC](https://syncloud.discourse.group/t/problem-updating-system/147/5 "2022-01-03T22:44:11Z")
> root@odroid-xu3and4:~# ls -la /var/snap/platform/current/ > total 52 > drwxr-xr-x 7 root root 4096 Jan 3 21:36 . > drwxr-xr-x 6 root root 4096 Jan 3 21:36 … > srwxr-xr-x 1 root root 0 Jan 3 21:36 api.wsgi.sock > srwxr-xr-x 1 root root 0 Jan 3 21:36 backend.sock > drwxr-xr-x 10 root root 4096 Jan 3 22:38 certbot > drwxr-xr-x 12 root root 4096 Oct 4 21:01 nginx > -rw-r–r-- 1 root root 4032 Oct 30 19:44 nginx.conf > drwxr-xr-x 2 root root 4096 Jan 3 21:36 openldap > drwxr-xr-x 2 root root 4096 Jan 3 21:36 openldap-data > srwxrwxrwx 1 root root 0 Jan 3 21:36 openldap.socket > -rw-r–r-- 1 root root 3072 Dec 7 20:46 platform.db > srwxr-xr-x 1 root root 0 Jan 3 21:36 public.wsgi.sock > drwxr-xr-x 3 root root 4096 Oct 4 21:01 slapd.d > lrwxrwxrwx 1 root root 76 Dec 26 21:43 syncloud.crt → /var/snap/platform/current/certbot/live/_**.syncloud.it/fullchain.pem > lrwxrwxrwx 1 root root 74 Dec 26 21:43 syncloud.key → /var/snap/platform/current/certbot/live/**_.syncloud.it/privkey.pem > -rw-r–r-- 1 root root 5 Jan 3 21:36 uwsgi.api.pid > -rw-r–r-- 1 root root 5 Jan 3 21:36 uwsgi.public.pid ---
**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\ **Post date:** [3 January 2022 22:51 UTC](https://syncloud.discourse.group/t/problem-updating-system/147/6 "2022-01-03T22:51:47Z")
ok, it is a bug from with old activated devices, the fix is coming. I will let you know when it is pushed to the store. > ---
**Author:** ![docvalium](https://avatars.discourse-cdn.com/v4/letter/d/fbc32d/32.png) [@docvalium](https://syncloud.discourse.group/u/docvalium)\ **Post date:** [3 January 2022 22:53 UTC](https://syncloud.discourse.group/t/problem-updating-system/147/7 "2022-01-03T22:53:58Z")
Thanks a lot for all your work! ---
**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\ **Post date:** [4 January 2022 21:35 UTC](https://syncloud.discourse.group/t/problem-updating-system/147/8 "2022-01-04T21:35:16Z")
The fix is pushed to the store, can you try upgrading now? ---
**Author:** ![docvalium](https://avatars.discourse-cdn.com/v4/letter/d/fbc32d/32.png) [@docvalium](https://syncloud.discourse.group/u/docvalium)\ **Post date:** [5 January 2022 20:09 UTC](https://syncloud.discourse.group/t/problem-updating-system/147/9 "2022-01-05T20:09:46Z")
I see the upgrade, but it does not work. Circles are spinning for a short while, than it’s back to the start. Via ssh i get this error message (as seemingly do other people): > root@odroid-xu3and4:~# snap refresh platform > > error: cannot perform the following tasks: > > - Fetch and check assertions for snap “platform” (2147483647) (snap “platform” does not have expected ID or revision according to assertions (metadata is broken or tampered): 2147483647 / platform.2201041191 != 2147483647 / platform.2147483647) ---
**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\ **Post date:** [5 January 2022 20:31 UTC](https://syncloud.discourse.group/t/problem-updating-system/147/10 "2022-01-05T20:31:53Z")
yes, sorry our versioning has stopped working on arm (32bit) as 2201041191 is actually bigger than the maximum int32 number 2147483647, so we are moving to simple no date versioning like 1191. Fixing right now, will let you know. (year 22 problem of Syncloud 🙂 ) ---
**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\ **Post date:** [6 January 2022 06:45 UTC](https://syncloud.discourse.group/t/problem-updating-system/147/11 "2022-01-06T06:45:58Z")
This should be fixed now, can you try one more time? ---
**Author:** ![docvalium](https://avatars.discourse-cdn.com/v4/letter/d/fbc32d/32.png) [@docvalium](https://syncloud.discourse.group/u/docvalium)\ **Post date:** [6 January 2022 22:42 UTC](https://syncloud.discourse.group/t/problem-updating-system/147/12 "2022-01-06T22:42:15Z")
Yes! Thank you. Works fine now.