Cron Mail Server

Hi good day.
Today I received 3 CRON emails from the server, with the following:
1.- sudo /usr/local/hestia/bin/v-backup-users
/etc/profile: fork: retry: Resource temporarily unavailable
/etc/profile: fork: retry: Resource temporarily unavailable
/etc/profile: fork: retry: Resource temporarily unavailable
/etc/profile: fork: retry: Resource temporarily unavailable
/etc/profile: fork: Resource temporarily unavailable

2.-sudo /usr/local/hestia/bin/v-update-letsencrypt-ssl
sudo: unable to fork: Resource temporarily unavailable

3.- sudo /usr/local/hestia/bin/v-update-sys-hestia-all

Cron Daemon [email protected]
07:50 (hace 1 hora)
para webmaster

/etc/profile: fork: retry: Resource temporarily unavailable
/usr/local/hestia/func/main.sh: fork: retry: Resource temporarily unavailable
/usr/local/hestia/func/main.sh: fork: retry: Resource temporarily unavailable
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://apt.hestiacp.com buster InRelease: Couldn’t spawn new processResource temporarily unavailable
W: Failed to fetch https://apt.hestiacp.com/dists/buster/InRelease Couldn’t spawn new processResource temporarily unavailable
W: Some index files failed to download. They have been ignored, or old ones used instead.
/usr/local/hestia/func/main.sh: fork: retry: Resource temporarily unavailable
/usr/local/hestia/func/main.sh: fork: retry: Resource temporarily unavailable
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://apt.hestiacp.com buster InRelease: Couldn’t spawn new processResource temporarily unavailable
W: Failed to fetch https://apt.hestiacp.com/dists/buster/InRelease Couldn’t spawn new processResource temporarily unavailable
W: Some index files failed to download. They have been ignored, or old ones used instead.
/usr/local/hestia/func/main.sh: fork: retry: Resource temporarily unavailable
/usr/local/hestia/func/main.sh: fork: retry: Resource temporarily unavailable
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://apt.hestiacp.com buster InRelease: Couldn’t spawn new processResource temporarily unavailable
W: Failed to fetch https://apt.hestiacp.com/dists/buster/InRelease Couldn’t spawn new processResource temporarily unavailable
W: Some index files failed to download. They have been ignored, or old ones used instead.

this sounds like a process limit. (ulimit)

check

ulimit -a
and
ulimit -u

ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 3832
max locked memory (kbytes, -l) 65536
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 3832
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

ulimit -u
3832

Is this a VPS by any chance?

Yes, and i just updated debian

maybe there is a hard limit set from your vps provider… that could be.

-Dennis

But a limit of what?

open files / open processes

This came today
1.- Cron admin@servpcspa sudo /usr/local/hestia/bin/v-backup-users
/bin/sh: 1: Cannot fork

2.- Cron admin@servpcspa sudo /usr/local/hestia/bin/v-update-letsencrypt-ssl
/bin/sh: 1: Cannot fork

What do I do, or what should I do?

Seems to be the limitations of your vps.

try in:

/etc/systemd/system.conf

at the end add:

DefaultLimitNOFILE=65000
DefaultLimitNPROC=65000
DefaultTasksMax=65000

and then run:

systemctl daemon-reload

and test

v-backup-users
1 Like

They were commented and
DefaultLimitNOFILE=1024:524288
It remained like this
Rebooted
systemctl daemon-reload
and i tried
v-backup-users
Apparently all good.

Thanks for the help, solved

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.