Cron in nextcloud Scale Cobia Beta.1

[Isma]

Hello, I understand that there were modifications and I don't know how to change docker to kuber but I would like to see how to configure the cron for nextcloud for this new version of scale beta.1

In scale 22 use this reference

TrueNAS Scale Nextcloud cron not working

Hello! Read a few posts about this problem but no solution found yet... I am running: TrueNAS-SCALE-22.02.2.1 Nextcloud app 24.0.3_1.6.6 Cannot get the cron job to work. The settings in the app is as follows: CronJob configuration Setup cronjob for nextcloud Enable cronjobs for nextcloud...

www.truenas.com

But now... the command "docker ps | grep nextcloud" does not work for me, when updating I would like to know what the new one would be and how to configure the new cron for nextcloud

Scale 22
docker exec --user root `docker ps | grep "nextcloud_nextcloud" | awk '{ print $1; }'` php cron.php

Scale 23
?¿???

 

[sfatula]

I am not running Cobia. However, another way to execute a command in a container without docker command which was removed, at least in 22 Scale is:

k3s kubectl exec -n ix-nextcloud --stdin --tty "$(/usr/local/bin/k3s kubectl -n ix-nextcloud get pods --field-selector status.phase=Running -o name | cut -f2 -d'/')" -- su -s /bin/bash www-data -c 'php occ maintenance:mode --on'

You can replace the php maintenance command with cron most likely, give it a try. I'm curious so let me know. kubectl doesn't support directly a run as user option.

 

[Isma]

I am not running Cobia. However, another way to execute a command in a container without docker command which was removed, at least in 22 Scale is:

k3s kubectl exec -n ix-nextcloud --stdin --tty "$(/usr/local/bin/k3s kubectl -n ix-nextcloud get pods --field-selector status.phase=Running -o name | cut -f2 -d'/')" -- su -s /bin/bash www-data -c 'php occ maintenance:mode --on'

You can replace the php maintenance command with cron most likely, give it a try. I'm curious so let me know. kubectl doesn't support directly a run as user option.

k3s kubectl exec -n ix-nextcloud --stdin --tty "$(/usr/local/bin/k3s kubectl -n ix-nextcloud get pods --field-selector status.phase=Running -o name | cut -f2 -d'/')" -- su -s /bin/bash www-data -c 'php cron.php'


k3s kubectl exec -n ix-nextcloud --stdin --tty "$(/usr/local/bin/k3s kubectl -n ix-nextcloud get pods --field-selector status.phase=Running -o name | cut -f2 -d'/')" -- su -s /bin/bash root -c 'php cron.php'

Error: [EFAULT] CronTask "k3s kubectl exec -n ix-nextcloud --stdin --tty "$(/usr/local/bin/k3s kubectl -n ix-nextcloud get pods --field-selector status.phase=Running -o name | cut -f2 -d'/')" -- su -s /bin/bash root -c 'php cron.php' > /dev/null" exited with 1 (non-zero) exit status.

 

[sfatula]

Likely a way to make it work but as I don't have a Cobia, can't play with each piece of the command. Forgetting using it in cron, did you try via command line from truenas (not container) shell?

 

[Isma]

Probablemente sea una forma de hacerlo funcionar, pero como no tengo un Cobia, no puedo jugar con cada pieza del comando. Olvidando usarlo en cron, ¿intentó a través de la línea de comando desde el shell truenas (no contenedor)?

the documentation according to nextcloud gives me these steps

Background jobs — Nextcloud latest Administration Manual latest documentation

Cron in Kubernetes: "can't set groups: Operation not permitted"

▶ Support intro Nextcloud version (eg, 20.0.5): 24.0.6 Operating system and version (eg, Ubuntu 20.04): Docker Image (Debian Bullseye) Apache or nginx version (eg, Apache 2.4.25): Apache (see Docker image) PHP version (eg, 7.4): 8.2 (see Docker image) Environment infos: K3s v1.24.8+k3s1 as...

help.nextcloud.com

try even adding said commands inside the pod itself

 

[sfatula]

True, but that's not with kubernetes/Truenas. Sorry I can't play with it myself to make it work in Cobia.

I don't believe cron runs in the container at all, without supervisord. I use a modified version of the docker container, based on this dockerfile setup:

docker/.examples/dockerfiles/cron/apache at master · nextcloud/docker

⛴ Docker image of Nextcloud. Contribute to nextcloud/docker development by creating an account on GitHub.

github.com

And then use load docker image button to load my custom image.

The readme was here:

docker/.examples/README.md at master · nextcloud/docker

⛴ Docker image of Nextcloud. Contribute to nextcloud/docker development by creating an account on GitHub.

github.com

Which explains.

 

[Isma]

True, but that's not with kubernetes/Truenas. Sorry I can't play with it myself to make it work in Cobia.

I don't believe cron runs in the container at all, without supervisord. I use a modified version of the docker container, based on this dockerfile setup:

docker/.examples/dockerfiles/cron/apache at master · nextcloud/docker

⛴ Docker image of Nextcloud. Contribute to nextcloud/docker development by creating an account on GitHub.

github.com

And then use load docker image button to load my custom image.

The readme was here:

docker/.examples/README.md at master · nextcloud/docker

⛴ Docker image of Nextcloud. Contribute to nextcloud/docker development by creating an account on GitHub.

github.com

Which explains.

Get by modifying the command of this post a half response

Need help directing Cron Job to an app

Hi all, fairly new Truenas SCALE user, looking for some Cron help! I have an app, Photoprism, that I would like to run a Cron job on each night. I've found some examples online which do what I'd like: "docker exec -ti photoprism photoprism index —cleanup" However this command doesn't work...

www.truenas.com

and I started using commands

k3s kubectl get namespaces -o name | grep nextcloud

and I adapted it guiding me from the failures but I did not finish fine-tuning it by changing my user to root

k3s kubectl get -o name -n nextcloud_nextcloud pods | sed -r "s/pod\///g" | xargs -I{} k3s kubectl exec -n nextcloud_nextcloud --stdin --tty {} -- su -s /bin/bash root -c 'php cron.php'

he swallows it but it must not be right

 

[Isma]

Maybe it worked, I'll be watching

With this

k3s kubectl get -o name -n ix-nextcloud pods | sed -r "s/pod\///g" | xargs -I{} k3s kubectl exec -n ix-nextcloud --stdin --tty {} -- su -s /bin/bash root -c 'php cron.php'

although maybe with errors

 

[sfatula]

My container runs as www-data, the default one. But maybe yours is running as root. It does appear it worked. I will apparently be fine tuning my kubectl commands for Cobia! What I sent you works fine under Truenas before Cobia.

 

[Isma]

My container runs as www-data, the default one. But maybe yours is running as root. It does appear it worked. I will apparently be fine tuning my kubectl commands for Cobia! What I sent you works fine under Truenas before Cobia.

Yes, I rely on the installation as shown in the cron user root

It's funny, it must be the wrong command, but it does what it should xD

k3s kubectl get -o name -n ix-nextcloud pods | xargs -I{} k3s kubectl exec -n ix-nextcloud --stdin --tty {} -- su -s /bin/bash root -c 'php cron.php'

 

[sfatula]

Try shortening it to:

k3s kubectl get -o name -n ix-nextcloud pods | xargs -I{} k3s kubectl exec -n ix-nextcloud --stdin --tty {} -- php cron.php

You shouldn't need the su portion as you should already be root in the container if I understand you correctly. May or may not get rid of exit code.

My command was checking for pod status running. The reason was here and there, I'd find failed pods so there would be multiple ones. This would make the command fail. So, I ignored them with my version of the command. If you never have failed pods, won't matter.

Glad you got it working though.

 

[Isma]

Try shortening it to:

k3s kubectl get -o name -n ix-nextcloud pods | xargs -I{} k3s kubectl exec -n ix-nextcloud --stdin --tty {} -- php cron.php

You shouldn't need the su portion as you should already be root in the container if I understand you correctly. May or may not get rid of exit code.

My command was checking for pod status running. The reason was here and there, I'd find failed pods so there would be multiple ones. This would make the command fail. So, I ignored them with my version of the command. If you never have failed pods, won't matter.

Glad you got it working though.

It works the same, but with the same error

 

[sretalla]

It might be worth saying that all 3 of the options for Background Jobs in Nextcloud are intended to be run from within the container, not outside it.

Can't you use Webcron instead? or investigate why the cron job isn't running properly from inside the container?

 

[sretalla]

Consider the last part in the command you're trying:

php cron.php

I imagine the system will need context to know where both of those components are, so specifying the paths, not just the filenames would probably help.

 

[Isma]

Consider the last part in the command you're trying:

php cron.php

I imagine the system will need context to know where both of those components are, so specifying the paths, not just the filenames would probably help.

Apparently I did not find the correct key, inside the nextcloud jail there is a section called cron because it automatically calls it every 5 minutes but it asks you for the command, try putting it in that section, both with the path and the full path, like the path it finds from the shell like simply invoking it and the same result but with the error showing the path that it uses at that moment

routes used

php /html/cron.php
php cron.php
php /nextclouddatos/html/cron.php
cron.php

 

[Isma]

It might be worth saying that all 3 of the options for Background Jobs in Nextcloud are intended to be run from within the container, not outside it.

Can't you use Webcron instead? or investigate why the cron job isn't running properly from inside the container?

I have been using it too, from a website that calls cron every 5 minutes but it seems that nextcloud does not work well and the internal administration panel shows that it is not running, even if I do it manually I eat the website

Web

Online cron service - EasyCron

EasyCron provides the most stable online cron service. Here you can schedule cron jobs that run periodically, with execution logs, email notifications, webhooks, execution time predictions and a bunch of other features.

www.easycron.com

 

[sretalla]

Based on the error, I see that cron.php is expecting some more information from the command to call it...

But it's not clear from what you showed above that you're trying the command in the existing container now...

Are you running the command like this?

k3s kubectl get -o name -n ix-nextcloud pods | xargs -I{} k3s kubectl exec -n ix-nextcloud --stdin --tty {} -- php /pnextclouddatos/html/cron.php

From the shell of TrueNAS?

 

[sfatula]

Cron is not running in docker. Docker starts a single process. That process is nextcloud (web). Without changes to the dockerfile, there is no cron. If you do a ps, no cron. That's why. I modify the dockerfile from hub.docker to run supervisord as mentioned earlier in the thread to instead run supervisord, which in turn runs nextcloud (apache) and crond. Then it works fine. The suggested changes are on github.

If sretalia is interested in more whys, read here:

Background jobs: Cron does not run · Issue #1695 · nextcloud/docker

Tag: latest (2022/02/04) When trying to setup Cron as the background job, it seems it cannot work without a lot of work on top of the image Missing: Packages: Cron (and dependencies) Service: Somet...

github.com

They actually expect you to run a separate docker container for cron. Honestly though, the "app" for Scale as given by IX Systems should include the modified version of the nextcloud docker than includes cron. IX doesn't provide a cron "app". It's really not that difficult to change the dockerfile and include supervisord.

 

[Isma]

both

k3s kubectl get -o name -n ix-nextcloud pods | xargs -I{} k3s kubectl exec -n ix-nextcloud --stdin --tty {} -- php cron.php

but it only works from the truenas gui with this command, even if there is an error, it executes it

k3s kubectl get -o name -n ix-nextcloud pods | xargs -I{} k3s kubectl exec -n ix-nextcloud --stdin --tty {} -- php cron.php

 

[Isma]

Based on the error, I see that cron.php is expecting some more information from the command to call it...

But it's not clear from what you showed above that you're trying the command in the existing container now...

Are you running the command like this?

k3s kubectl get -o name -n ix-nextcloud pods | xargs -I{} k3s kubectl exec -n ix-nextcloud --stdin --tty {} -- php /pnextclouddatos/html/cron.php

From the shell of TrueNAS?