sed: cannot rename /usr/local/vesta/conf/sedGh77Ff: Operation not permitted

[adamjedgar]

Havent yet checked the logs, however, is the following a hackers attempt at getting into my system via external cron?

(Cron Daemon)
sed: cannot rename /usr/local/vesta/conf/sedGh77Ff: Operation not permitted

here is another one

sed: cannot rename /usr/local/vesta/conf/sedQ1mJHx: Operation not permitted

[linuxman]

Havent yet checked the logs, however, is the following a hackers attempt at getting into my system via external cron?

(Cron Daemon)
sed: cannot rename /usr/local/vesta/conf/sedGh77Ff: Operation not permitted

here is another one

sed: cannot rename /usr/local/vesta/conf/sedQ1mJHx: Operation not permitted

Hello,
I have the something same issue and when I reboot the server and connect to it with external console the disk need to check disk and fixed the empty inodes.
Please check the disk.

[adamjedgar]

If i setup Vesta to only allow 3 backups in package templates, the cron job v-backup-usr is still attempting to run on users that already have 3 backups.

This of course then incorrectly throws an error...sed: cannot rename /usr/local/vesta/conf/sedLOFmFM: Operation not permitted.

I wonder if Vesta is setting the directory to perhaps read only for the admin user?

Is there any particular reason why Vesta is configured this way?

how do we configure it so that the cron can overwrite existing automated backups once the max number allowed in Packages has been reached?