Cloudron Forum

this one (which I should have figured out earlier I think!) fixed collectd:
apt-get remove --auto-remove collectd-core
apt-get purge --auto-remove collectd-core
apt-get update
apt-get --yes install collectd

Then I also I had to run sudo /home/yellowtent/box/setup/start.sh

and we're up!

some stuff runs but the dashboard is broken and I can't for the life of met get Collectd to install properly...

troubleshooter starts cloudron and gets hung up on configuring collected:
2024-10-21T01:41:43 ==> start: Configuring collectd
A dependency job for collectd.service failed. See 'journalctl -xe' for details.

when installing various ways:

sudo apt install --fix-broken
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up collectd (5.12.0-17.1build2) ...
A dependency job for collectd.service failed. See 'journalctl -xe' for details.
invoke-rc.d: initscript collectd, action "restart" failed.
○ collectd.service - Statistics collection and monitoring daemon
     Loaded: loaded (/usr/lib/systemd/system/collectd.service; enabled; preset: enabled)
     Active: inactive (dead)
       Docs: man:collectd(1)
             man:collectd.conf(5)
             https://collectd.org

Oct 21 01:34:38 r00buntu-server systemd[1]: Dependency failed for collectd.service - Statistics collection and monitoring daemon.
Oct 21 01:34:38 r00buntu-server systemd[1]: collectd.service: Job collectd.service/start failed with result 'dependency'.
Oct 21 01:36:15 r00buntu-server systemd[1]: Dependency failed for collectd.service - Statistics collection and monitoring daemon.
Oct 21 01:36:15 r00buntu-server systemd[1]: collectd.service: Job collectd.service/start failed with result 'dependency'.
Oct 21 01:38:22 r00buntu-server systemd[1]: Dependency failed for collectd.service - Statistics collection and monitoring daemon.
Oct 21 01:38:22 r00buntu-server systemd[1]: collectd.service: Job collectd.service/start failed with result 'dependency'.
Oct 21 01:40:26 r00buntu-server systemd[1]: Dependency failed for collectd.service - Statistics collection and monitoring daemon.
Oct 21 01:40:26 r00buntu-server systemd[1]: collectd.service: Job collectd.service/start failed with result 'dependency'.
Oct 21 01:43:07 r00buntu-server systemd[1]: Dependency failed for collectd.service - Statistics collection and monitoring daemon.
Oct 21 01:43:07 r00buntu-server systemd[1]: collectd.service: Job collectd.service/start failed with result 'dependency'.
dpkg: error processing package collectd (--configure):
 installed collectd package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 collectd
E: Sub-process /usr/bin/dpkg returned an error code (1)

I've tried so many ways fo getting the package working including re-install all the dependencies:
https://askubuntu.com/questions/275719/reinstall-package-and-its-installed-dependencies

I'm having the same issue after upgrading to 24.04 and 8.0.3

r00buntu@r00buntu-server:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble
r00buntu@r00buntu-server:~$ mysql --version
mysql Ver 8.0.39-0ubuntu0.24.04.2 for Linux on x86_64 ((Ubuntu))

running the "ALTER TABLE" command above results in
"ERROR 1046 (3D000): No database selected"

Collectd seems to be failing to install properly and this happens when running the troubleshooter:
2024-10-21T01:41:43 ==> start: Configuring collectd
A dependency job for collectd.service failed. See 'journalctl -xe' for details.

it seems... (pending successful update) i've fixed this by manually installing systemd-resolved (indicated in error logs as missing) and then the update ran fine.

UPDATE: I haven't managed to get it working entirely yet - blank dashboard now... collectd issues...

Any indication it'd be important to keep/uninstall systemd-resolved after?

My upgrade log:

Oct 20 23:39:16 box:taskworker Starting task 5817. Logs are at /home/yellowtent/platformdata/logs/tasks/5817.log
Oct 20 23:39:16 box:tasks update 5817: {"percent":1,"message":"Checking disk space"}
Oct 20 23:39:16 box:shell file execArgs: df ["-B1","--output=source,fstype,size,used,avail,pcent,target","/"]
Oct 20 23:39:16 box:tasks update 5817: {"percent":5,"message":"Downloading and verifying release"}
Oct 20 23:39:16 box:shell downloadUrl execArgs: curl ["-s","--fail","https://releases.cloudron.io/versions.json","-o","/home/yellowtent/platformdata/update/versions.json"]
Oct 20 23:39:16 box:updater downloadUrl: downloading https://releases.cloudron.io/versions.json to /home/yellowtent/platformdata/update/versions.json
Oct 20 23:39:16 box:updater downloadUrl: done
Oct 20 23:39:16 box:shell downloadUrl execArgs: curl ["-s","--fail","https://releases.cloudron.io/versions.json.sig","-o","/home/yellowtent/platformdata/update/versions.json.sig"]
Oct 20 23:39:16 box:updater downloadUrl: downloading https://releases.cloudron.io/versions.json.sig to /home/yellowtent/platformdata/update/versions.json.sig
Oct 20 23:39:16 box:updater downloadUrl: done
Oct 20 23:39:16 box:shell gpgVerify execArgs: /usr/bin/gpg ["--status-fd","1","--no-default-keyring","--keyring","/home/yellowtent/box/src/releases.gpg","--verify","/home/yellowtent/platformdata/update/versions.json.sig","/home/yellowtent/platformdata/update/versions.json"]
Oct 20 23:39:16 box:updater gpgVerify: /usr/bin/gpg --status-fd 1 --no-default-keyring --keyring /home/yellowtent/box/src/releases.gpg --verify /home/yellowtent/platformdata/update/versions.json.sig /home/yellowtent/platformdata/update/versions.json
Oct 20 23:39:16 box:shell downloadUrl execArgs: curl ["-s","--fail","https://releases.cloudron.io/box-06e46e0f1e-06e46e0f1e-8.0.3.tar.gz","-o","/home/yellowtent/platformdata/update/box.tar.gz"]
Oct 20 23:39:16 box:updater downloadUrl: downloading https://releases.cloudron.io/box-06e46e0f1e-06e46e0f1e-8.0.3.tar.gz to /home/yellowtent/platformdata/update/box.tar.gz
Oct 20 23:39:19 box:updater downloadUrl: done
Oct 20 23:39:19 box:shell downloadUrl execArgs: curl ["-s","--fail","https://releases.cloudron.io/box-06e46e0f1e-06e46e0f1e-8.0.3.tar.gz.sig","-o","/home/yellowtent/platformdata/update/box.tar.gz.sig"]
Oct 20 23:39:19 box:updater downloadUrl: downloading https://releases.cloudron.io/box-06e46e0f1e-06e46e0f1e-8.0.3.tar.gz.sig to /home/yellowtent/platformdata/update/box.tar.gz.sig
Oct 20 23:39:19 box:updater downloadUrl: done
Oct 20 23:39:19 box:shell gpgVerify execArgs: /usr/bin/gpg ["--status-fd","1","--no-default-keyring","--keyring","/home/yellowtent/box/src/releases.gpg","--verify","/home/yellowtent/platformdata/update/box.tar.gz.sig","/home/yellowtent/platformdata/update/box.tar.gz"]
Oct 20 23:39:19 box:updater gpgVerify: /usr/bin/gpg --status-fd 1 --no-default-keyring --keyring /home/yellowtent/box/src/releases.gpg --verify /home/yellowtent/platformdata/update/box.tar.gz.sig /home/yellowtent/platformdata/update/box.tar.gz
Oct 20 23:39:19 box:shell extractTarball execArgs: tar ["-zxf","/home/yellowtent/platformdata/update/box.tar.gz","-C","/tmp/box-450620418"]
Oct 20 23:39:19 box:updater extractTarball: extracting /home/yellowtent/platformdata/update/box.tar.gz to /tmp/box-450620418
Oct 20 23:39:20 box:updater extractTarball: extracted
Oct 20 23:39:20 box:updater Updating box with https://releases.cloudron.io/box-06e46e0f1e-06e46e0f1e-8.0.3.tar.gz
Oct 20 23:39:20 box:tasks update 5817: {"percent":70,"message":"Installing update"}
Oct 20 23:39:20 box:shell update /usr/bin/sudo -S /home/yellowtent/box/src/scripts/update.sh /tmp/box-450620418 /home/yellowtent/platformdata/logs/tasks/5817.log
Oct 20 23:39:21 ==> installer: Updating from 7.7.2 to 8.0.3
Oct 20 23:39:21 ==> installer: Making sure apt is in a good state
Oct 20 23:39:21 ==> installer: Waiting for all dpkg tasks to finish...
[no timestamp] 
[no timestamp]  apt does not have a stable CLI interface. Use with caution in scripts.
[no timestamp] 
Jan 01 00:00:00 http://us.archive.ubuntu.com/ubuntu noble InRelease
Feb 01 00:00:00 https://linux.teamviewer.com/deb stable InRelease
Mar 01 00:00:00 http://us.archive.ubuntu.com/ubuntu noble-updates InRelease
Apr 01 00:00:00 http://security.ubuntu.com/ubuntu noble-security InRelease
May 01 00:00:00 http://us.archive.ubuntu.com/ubuntu noble-backports InRelease
Jun 01 00:00:00 https://dl.cloudsmith.io/public/balena/etcher/deb/ubuntu jammy InRelease [2,957 B]
[no timestamp]  2,957 B in 1s (4,211 B/s)
[no timestamp] 
[no timestamp] 
[no timestamp] 
Jan 01 00:00:00 packages can be upgraded. Run 'apt list --upgradable' to see them.
Oct 20 23:39:26 ==> installer: apt is ready
Oct 20 23:39:26 ==> installer: disabling unbound
[no timestamp]  state of unbound.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
[no timestamp]  /usr/lib/systemd/systemd-sysv-install disable unbound
Oct 20 23:39:29 ==> installer: enabling systemd-resolved
[no timestamp]  to enable unit: Unit file systemd-resolved.service does not exist.
Oct 20 23:39:31 box:shell update: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/update.sh /tmp/box-450620418 /home/yellowtent/platformdata/logs/tasks/5817.log errored BoxError: update exited with code 1 signal null
[no timestamp]  at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:110:19)
[no timestamp]  at ChildProcess.emit (node:events:513:28)
[no timestamp]  at ChildProcess._handle.onexit (node:internal/child_process:291:12) {
[no timestamp]  reason: 'Shell Error',
[no timestamp]  details: {},
[no timestamp]  code: 1,
[no timestamp]  signal: null
[no timestamp]  }
Oct 20 23:39:31 box:taskworker Task took 14.695 seconds
Oct 20 23:39:31 box:tasks setCompleted - 5817: {"result":null,"error":{"stack":"BoxError: update exited with code 1 signal null\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:110:19)\n at ChildProcess.emit (node:events:513:28)\n at ChildProcess._handle.onexit (node:internal/child_process:291:12)","name":"BoxError","reason":"Shell Error","details":{},"message":"update exited with code 1 signal null","code":1,"signal":null}}
Oct 20 23:39:31 box:tasks update 5817: {"percent":100,"result":null,"error":{"stack":"BoxError: update exited with code 1 signal null\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:110:19)\n at ChildProcess.emit (node:events:513:28)\n at ChildProcess._handle.onexit (node:internal/child_process:291:12)","name":"BoxError","reason":"Shell Error","details":{},"message":"update exited with code 1 signal null","code":1,"signal":null}}
[no timestamp]  update exited with code 1 signal null
[no timestamp]  at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:110:19)
[no timestamp]  at ChildProcess.emit (node:events:513:28)
[no timestamp]  at ChildProcess._handle.onexit (node:internal/child_process:291:12)

I accidentally upgraded to 24.04 before properly upgrading to 8.+ hopefully this can be resolved without too much trouble?

I can't seem to edit members of my organization for some reason. There are some errors in the job, I'll pass them in.

Is the current version in cloudron the latest?

Weirdly it just started working again.

I wasn't quite able to parse out the which were the errors that were happening.

Getting health check errors - any one else have this issue?

@girish yes, and someone like this has happened again.. still figuring out what...

I created a new snap_browsers file at /etc/apparmor.d/abstractions/snap_browers based on this:
https://gitlab.com/apparmor/apparmor/-/blob/31c9cf6845cb78cca59a753d7c5b27312d579be8/profiles/apparmor.d/abstractions/snap_browsers
and it seems to have resolved it.

Not sure why/how this happened though

It seems one of my disks may have gotten temporarily low and cuased an issue, but i'm having a little trouble sussing it out. A package was also broken, but getting that sorted. I checked the troubleshooting list and running ' sudo /home/yellowtent/box/setup/start.sh' yeilds this error ultimately:

2024-03-26T20:37:24 ==> start: Cloudron Start
media500:
2024-03-26T20:37:25 ==> start: Configuring docker
Synchronizing state of apparmor.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable apparmor
Job for apparmor.service failed because the control process exited with error code.
See "systemctl status apparmor.service" and "journalctl -xeu apparmor.service" for details.

server:~$ systemctl status apparmor.service
$ systemctl status apparmor.service
× apparmor.service - Load AppArmor profiles
Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2024-03-26 20:37:27 EDT; 16s ago
Docs: man:apparmor(7)
https://gitlab.com/apparmor/apparmor/wikis/home/
Process: 190543 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, status=1/FAILURE)
Main PID: 190543 (code=exited, status=1/FAILURE)
CPU: 386ms

Mar 26 20:37:27 r00buntu-server apparmor.systemd[190543]: Restarting AppArmor
Mar 26 20:37:27 r00buntu-server apparmor.systemd[190543]: Reloading AppArmor profiles
Mar 26 20:37:27 r00buntu-server apparmor.systemd[190558]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/usr.bin.evince at line 32: Could no>
Mar 26 20:37:27 r00buntu-server apparmor.systemd[190569]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Mar 26 20:37:27 r00buntu-server apparmor.systemd[190612]: AppArmor parser error for /etc/apparmor.d/usr.bin.evince in profile /etc/apparmor.d/usr.bin.evince at li>
Mar 26 20:37:27 r00buntu-server apparmor.systemd[190661]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Mar 26 20:37:27 r00buntu-server apparmor.systemd[190543]: Error: At least one profile failed to load
Mar 26 20:37:27 r00buntu-server systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 20:37:27 r00buntu-server systemd[1]: apparmor.service: Failed with result 'exit-code'.
Mar 26 20:37:27 r00buntu-server systemd[1]: Failed to start Load AppArmor profiles.

It seems it uses Grafana for visualizing:

Analyse and visualize DMARC results using open-source tools.

parsedmarc for parsing DMARC reports,
Elasticsearch to store aggregated data.
Grafana to visualize the aggregated reports.
See the full blog post with instructions at https://debricked.com/blog/2020/05/14/analyse-and-visualize-dmarc-results-using-open-source-tools/.

https://github.com/debricked/dmarc-visualizer

or any similar app...

@micmc oh, indeed! I didn't realize all the apps have sftp access, but I see that now! smacks forehead

Oh - hmm, I guess I did actually get it to work by cutting instead of copying, but I am still curious if there's a way to view progress and errors better by doing it on the CLI or some other tool.

Hi there, I need to get some files from my computer onto an app - a lot of files.

I was able to get many of them to transfer using the File Manager in Volumes, however, it seems to be failing without an error (just says it's pasting forever, with no file changes).

Is there a way to transfer files into an app or across apps other than the File Manager GUI that also does recursiveness?

I see the Cloudron CLI but there's no documentation of a recursive function for the push feature.

Thank you!

Did this get implemented or is it tracked somewhere as a feature request?

https://domainaware.github.io/parsedmarc/

https://debricked.com/blog/analyze-and-visualize-dmarc-report/

https://github.com/ckolderup/postmarks

sorry, I thought it was copying the line itself, not hte link to the file and then rushed off!

App\Http\Controllers\HoneyPotController::throwNotFound:66 The route api/v1/instance could not be found.

I'mnot even sure if this is related... there are many errors when uploading and few in the log, but this might occur once in the log per upload group.