Joplin Installing - Cleaning up old install

[JOduMonT]

So I upgraded and reboot Cloudron
I installed a new nextcloud without issue
remove a ghost
and now I try to install joplin (which is my first time on this server, and it's the first time I use this subdomain also)
and I have this message which it has to clean before installing

• Joplin Server 1.4.0
• Cloudron v7.1.4 (Ubuntu 20.04.3 LTS)

Apr 11 19:59:55 box:shell startTask (stdout): Service box-task-1763 finished with exit code 0
Apr 11 19:59:55 box:tasks startTask: 1763 completed with code 0 and signal 0
Apr 11 19:59:55 box:apps scheduleTask: task 1763 of a4382bae-efd0-487e-abb9-423feba0e726 completed
Apr 11 19:59:55 box:locker Released : apptask
Apr 11 19:59:55 box:scheduler resumeJobs: a4382bae-efd0-487e-abb9-423feba0e726
Apr 11 19:59:55 box:tasks startTask: 1763 done. error: null
Apr 11 20:00:00 box:janitor Cleaning up expired tokens
Apr 11 20:00:00 box:janitor Cleaned up 0 expired tokens
Apr 11 20:00:00 box:apphealthmonitor app health: 7 alive / 0 dead.
Apr 11 20:00:10 box:apphealthmonitor app health: 7 alive / 0 dead.
Apr 11 20:00:20 box:apphealthmonitor app health: 7 alive / 0 dead.
Apr 11 20:00:30 box:apphealthmonitor app health: 7 alive / 0 dead.
Apr 11 20:00:40 box:apphealthmonitor app health: 7 alive / 0 dead.
Apr 11 20:00:50 box:apphealthmonitor app health: 7 alive / 0 dead.
Apr 11 20:01:00 box:apphealthmonitor app health: 7 alive / 0 dead.
Apr 11 20:01:10 box:apphealthmonitor app health: 7 alive / 0 dead.
Apr 11 20:01:20 box:apphealthmonitor app health: 7 alive / 0 dead.
Apr 11 20:01:30 box:apphealthmonitor app health: 7 alive / 0 dead.
Apr 11 20:01:40 box:apphealthmonitor app health: 7 alive / 0 dead.
Apr 11 20:01:50 box:apphealthmonitor app health: 7 alive / 0 dead.
Apr 11 20:01:56 box:sysinfo/generic getServerIPv4: getting server IP
Apr 11 20:01:56 box:apps downloading manifest from https://api.cloudron.io/api/v1/apps/org.joplinapp.cloudron/versions/1.4.0
Apr 11 20:01:57 box:apps Will install app with id : 12e002df-8e26-4d2b-826f-0ed925d7faf2
Apr 11 20:01:58 box:locker Acquired : apptask
Apr 11 20:01:58 box:scheduler suspendJobs: 12e002df-8e26-4d2b-826f-0ed925d7faf2
Apr 11 20:01:58 box:tasks startTask - starting task 1764 with options {"timeout":72000000,"nice":15,"memoryLimit":400,"logFile":"/home/yellowtent/platformdata/logs/12e002df-8e26-4d2b-826f-0ed925d7faf2/apptask.log"}. logs at /home/yellowtent/platformdata/logs/12e002df-8e26-4d2b-826f-0ed925d7faf2/apptask.log
Apr 11 20:01:58 box:shell startTask spawn: /usr/bin/sudo -S -E /home/yellowtent/box/src/scripts/starttask.sh 1764 /home/yellowtent/platformdata/logs/12e002df-8e26-4d2b-826f-0ed925d7faf2/apptask.log 15 400
Apr 11 20:01:58 box:shell startTask (stdout): Running as unit: box-task-1764.service

I look and my drive are fine I still have 50GiB free space

what could cause this issue ?

[nebulon]

@JOduMonT I can't actually spot any error in those logs. Which line are you referring to and what exactly is not working?

[JOduMonT]

@nebulon said in Joplin Installing - Cleaning up old install:

@JOduMonT I can't actually spot any error in those logs. Which line are you referring to and what exactly is not working?

it odd message for me was "cleaning up old install install"
since I never installed Joplin before, but I let the installer overnight brewing and this morning everything is fine.

It must being cleaning other install, other then joplin.

[JOduMonT]

@nebulon now again I just changed the email for an nextcloud instance, and it takes age claiming it have to clean an old install

[nebulon]

Ah ok, so this is to be expected. Although I guess we could look into this to either make the progress message more on point or better check what parts could be skipped.

This is to get a fresh start in case an installation failed and the install task is retried. This has nothing to do with a previous other app instance.

For the second issue with Nextcloud, this may be something else though. Also here note that this particular "Cleaning up old install" step is performed in many app tasks. Since this will cleanup docker container and addon resources for a fresh start, maybe docker is currently a bit slow on your instance?

[JOduMonT]

@nebulon said in Joplin Installing - Cleaning up old install:

maybe docker is currently a bit slow on your instance?

good question ?
how I may know ?
I thought so docker was only a daemon

[nebulon]

@JOduMonT it is only a daemon, but sometimes containers are recreated, images are managed and so forth which may use up a lot of server resources temporarily, especially if disk I/O is slow.

To give some reference here, we are talking about the code section from https://git.cloudron.io/cloudron/box/-/blob/master/src/apptask.js#L318 to https://git.cloudron.io/cloudron/box/-/blob/master/src/apptask.js#L340 so something is slow on your system in that area. Not sure how much tinkering you want to do for debugging, but you could stray in some console.log()s there to narrow down the issue. I can also help here, if you enable remote SSH support and send us a mail with your dashboard domain to support@cloudron.io