We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
sed: cannot rename /usr/local/vesta/conf/sedGh77Ff: Operation not permitted
-
- Posts: 43
- Joined: Tue Apr 18, 2017 7:55 am
sed: cannot rename /usr/local/vesta/conf/sedGh77Ff: Operation not permitted
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
(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
Re: sed: cannot rename /usr/local/vesta/conf/sedGh77Ff: Operation not permitted
Hello,adamjedgar wrote: ↑Wed Jun 05, 2019 9:11 pmHavent 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
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.
-
- Posts: 43
- Joined: Tue Apr 18, 2017 7:55 am
Re: sed: cannot rename /usr/local/vesta/conf/sedGh77Ff: Operation not permitted
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?
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?