search

syncloud / platform

Run popular services on your device with one click
https://syncloud.org
GNU General Public License v3.0
393 stars 40 forks source link

WebGui error #596

Closed sttrebo closed 3 years ago

sttrebo commented 3 years ago

getting a webgui error 'connection aborted;' sent the error logs under personal email. Capture

ran this: journalctl -u snap.platform.backend

got this: journalctl -u snap.platform.backend -- Logs begin at Wed 2021-07-07 07:15:04 UTC, end at Wed 2021-07-07 11:54:00 UTC -- No entries -- lines 1-2/2 (END)

ran this: systemctl status snap.platform.backend

got this: systemctl status snap.platform.backend ● snap.platform.backend.service - Service for snap application platform.backend Loaded: loaded (/etc/systemd/system/snap.platform.backend.service; enabled; v Active: active (running) since Thu 2019-02-14 10:12:03 UTC; 2 years 4 months Main PID: 478 (backend) Memory: 8.2M CGroup: /system.slice/snap.platform.backend.service └─478 /snap/platform/210321656/bin/backend /var/snap/platform/common/

Warning: Journal has been rotated since unit was started. Log output is incomple lines 1-9/9 (END)

cyberb commented 3 years ago

can you try:

systemctl restart snap.platform.backend

And try UI again?

sttrebo commented 3 years ago

ran it a couple of times, no response on the putty session to that command and the WebGui still has the same error.

cyberb commented 3 years ago

sorry, it was actually snapd from the logs, can you run this:

systemctl status snapd
sttrebo commented 3 years ago

systemctl status snapd ● snapd.service - Snappy daemon Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: en Active: failed (Result: exit-code) since Wed 2021-07-07 01:19:56 UTC; 19h ago Process: 1001 ExecStart=/usr/lib/snapd/snapd (code=exited, status=2) Main PID: 1001 (code=exited, status=2)

Warning: Journal has been rotated since unit was started. Log output is incomple lines 1-7/7 (END)

cyberb commented 3 years ago 
systemctl restart snapd
sttrebo commented 3 years ago

systemctl restart snapd root@syncloud:~# systemctl status snapd ● snapd.service - Snappy daemon Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2021-07-08 15:12:05 UTC; 42s ago Process: 23275 ExecStart=/usr/lib/snapd/snapd (code=exited, status=2) Main PID: 23275 (code=exited, status=2)

Jul 08 15:12:05 syncloud systemd[1]: snapd.service: Service RestartSec=100ms expired, scheduling restart. Jul 08 15:12:05 syncloud systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5. Jul 08 15:12:05 syncloud systemd[1]: Stopped Snappy daemon. Jul 08 15:12:05 syncloud systemd[1]: snapd.service: Start request repeated too quickly. Jul 08 15:12:05 syncloud systemd[1]: snapd.service: Failed with result 'exit-code'. Jul 08 15:12:05 syncloud systemd[1]: Failed to start Snappy daemon.

i'm thinking maybe it's time to reflash/start over and just restore my data. but since everything else is working fine, might just wait until the Pi4-64 is available then go with that... unless you have any other ideas?

cyberb commented 3 years ago 
journalctl -e -u snapd
sttrebo commented 3 years ago

hi- thanks, but i ended up starting from scratch to get things cleaned up. did a fresh install. when i added in the nextcloud apps that i need (tasks, news, calendar, and several others), nextcloud displayed a banner at the top saying then apps would cause nextcloud to be unstable therefore they could not be installed. weird, never seen that before. sorry i didn't capture those messages. but i think i'll wait for the Pi4-64 version because it sounds like 64bit support is going to become more and more required. plus it'll give me an easy reason to buy a bigger SSD..

cyberb commented 3 years ago

Ok, let's close this then.