Vesta Control Panel - Forum

Community Forum

Skip to content

Advanced search
  • Quick links
    • Main site
    • Github repo
    • Google Search
  • FAQ
  • Login
  • Register
  • Board index Main Section General Discussion
  • Search

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

General questions about VestaCP
Post Reply
  • Print view
Advanced search
3 posts • Page 1 of 1
adamjedgar
Posts: 43
Joined: Tue Apr 18, 2017 7:55 am

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

Post by adamjedgar » Wed Jun 05, 2019 9:11 pm

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
Top

linuxman
Posts: 47
Joined: Tue Jun 04, 2019 12:56 pm

Os: Debian 8x
Web: apache + nginx
Re: sed: cannot rename /usr/local/vesta/conf/sedGh77Ff: Operation not permitted
  • Quote

Post by linuxman » Thu Jun 06, 2019 11:37 am

adamjedgar wrote: ↑
Wed Jun 05, 2019 9:11 pm
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.
Top

adamjedgar
Posts: 43
Joined: Tue Apr 18, 2017 7:55 am

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

Post by adamjedgar » Sun Jun 16, 2019 10:48 pm

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?
Top


Post Reply
  • Print view

3 posts • Page 1 of 1

Return to “General Discussion”



  • Board index
  • All times are UTC
  • Delete all board cookies
  • The team
Powered by phpBB® Forum Software © phpBB Limited
*Original Author: Brad Veryard
*Updated to 3.2 by MannixMD
 

 

Login  •  Register

I forgot my password