The full stack trace is: 16/07/2021 17:58:24 :: [console] Error writing to collectd.localhost.df-sdc1.df_complex-used: Unable to read header (/var/lib/graphite/whisper/collectd/localhost/df-sdc1/df_complex-used.wsp) 16/07/2021 17:58:24 :: [console] Unhandled Error Traceback (most recent call last): File "/usr/lib/python3/dist-packages/twisted/python/threadpool.py", line 266, in <lambda> inContext.theWork = lambda: context.call(ctx, func, *args, **kw) File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 122, in callWithContext return self.currentContext().callWithContext(ctx, func, *args, **kw) File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 85, in callWithContext return func(*args,**kw) File "/usr/lib/python3/dist-packages/carbon/writer.py", line 189, in writeForever writeCachedDataPoints() --- <exception caught here> --- File "/usr/lib/python3/dist-packages/carbon/writer.py", line 165, in writeCachedDataPoints state.database.write(metric, datapoints) File "/usr/lib/python3/dist-packages/carbon/database.py", line 124, in write whisper.update_many(path, datapoints) File "/usr/lib/python3/dist-packages/whisper.py", line 740, in update_many return file_update_many(fh, points, now) File "/usr/lib/python3/dist-packages/whisper.py", line 747, in file_update_many header = __readHeader(fh) File "/usr/lib/python3/dist-packages/whisper.py", line 294, in __readHeader raise CorruptWhisperFile("Unable to read header", fh.name) whisper.CorruptWhisperFile: Unable to read header (/var/lib/graphite/whisper/collectd/localhost/df-sdc1/df_complex-free.wsp) The last line gives a hint that the graphite file is corrupt. So, I removed all the whisper files in /home/yellowtent/platformdata/graphite/whisper/collectd/localhost/df-sdc1 and graphs seems to work after that. @atridad Maybe a good idea to check the health of the hard disk ? Also, since we hit the systemd issue on the same server.

For future reference, systemd was acting all strange. We got all sorts of errors. # systemctl restart box Failed to restart box.service: Connection timed out See system logs and 'systemctl status box.service' for details. # systemctl status box Failed to get properties: Connection timed out # systemctl status box Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Restarting the server seems to fix it.

@privsec That worked, thanks!

@scooke we have traced this down to a nodejs bug apparently with the domain in question. The upstream issue is at https://github.com/nodejs/node/issues/39397

@nebulon Sorry for a doublet

Thanks for reporting, I've fixed this now for the next release.

@girish thanks, I'm away for a few days but will try once I'm back...

@nj yes with the folder in place there adding the -r to solve this makes sense, however the initial issue is that this folder should not be there in the first place. As the name already suggests, I guess this was just some intermediate manual action to stash certs. Essentially if you don't actively use files in that folder then just delete it to solve this for future releases.

@girish

@girish yeah, I've already bumped the memory up, thanks.

@girish ok i was on the initial setup and i had to click 'show advanced settings' and then set the subdomain to the zone. a simple hint after the error with something like your message would be super helpful on that page. i'm super busy right now but could try a merge request if that would be welcome. i appreciate the quick help, thank you.

@mazarian that's correct, the permission is the thing I fixed in 6.3.5. Glad it's working now and thanks for reporting back!

@kdev Indeed as @scooke mentioned it seems that docker is already installed on the server. Can you uninstall it and try again? In general, Cloudron must be installed on a fresh Ubuntu 20.04 without docker etc.

@luckow yes, good catch! fixed now. will be in 6.3.5

@nebulon Oh yeah, I had not thought to try the right-click, good catch. Right-clicking on a webpage never feels intuitive to me, except when I want the browser's context menu

hey @nebulon, no, only 2-3 ports tcp/udp (wireguard/snmp/ssh) and it happened inbetween again, without any reboots/upgrades/etc. I got notfied by network mgmgt system, that my cloudron server is down - luckily it was just the firewall…

@girish That did it! You are awesome! Thank you for all your help from a -1 rep person :). Thank you and the cloudron team for all you do in helping us newbies. (had to wait 3 minutes)

@girish HAH nevermind. Its me being a Linux noob... turns out I mounted the drive itself not the partition. The files are there.