Cannot utime: Operation not permitted

Discussion in 'General' started by almere, Aug 12, 2013.

  1. almere

    almere Member HowtoForge Supporter

    Hey there,

    If I try to restore the backup, I get an error:

    Code:
    tar: .: Cannot utime: Operation not permitted
    tar: .: Cannot change ownership to uid 0, gid 0: Operation not permitted
    tar: Exiting with failure status due to previous errors
    
    ls -l /var/backup/web157/
    Code:
    total 189M
    -rwxr-x--- 1 web157 client1 56K Aug 12 00:59 db_blabla_2013-08-12_00-59.sql.gz
    -rwxr-x--- 1 root   root    29M Aug  6 01:57 web157_2013-08-06_01-57.tar.gz
    -rwxr-x--- 1 root   root    29M Aug  7 01:57 web157_2013-08-07_01-57.tar.gz
    -rwxr-x--- 1 root   root    29M Aug  8 00:38 web157_2013-08-08_00-38.tar.gz
    -rwxr-x--- 1 root   root    29M Aug  9 00:38 web157_2013-08-09_00-38.tar.gz
    -rwxr-x--- 1 root   root    29M Aug 10 00:38 web157_2013-08-10_00-38.tar.gz
    -rwxr-x--- 1 root   root    29M Aug 11 00:39 web157_2013-08-11_00-39.tar.gz
    -rwxr-x--- 1 root   root    15M Aug 12 00:39 web157_2013-08-12_00-39.tar.gz
    
    If I try to restore the DB file, than it's going perfect...

    Any ideas ?


    Thank's
     
  2. almere

    almere Member HowtoForge Supporter

    He he :p

    My bad. It works, but why tar says:
    Code:
    tar: .: Cannot utime: Operation not permitted
    tar: .: Cannot change ownership to uid 0, gid 0: Operation not permitted
    tar: Exiting with failure status due to previous errors
    
    Code:
    tar: Exiting with failure status due to previous errors
    
    Thank's
     
  3. abdi

    abdi New Member

    I am having the same exact problem only that with mine nothing gets to be done!

    Code:
    server#: /usr/local/ispconfig/server/server.sh
    tar: .: Cannot utime: Operation not permitted
    tar: .: Cannot change ownership to uid 0, gid 0: Operation not permitted
    tar: .: Cannot change mode to rwxr-xr-x: Operation not permitted
    tar: Exiting with failure status due to previous errors
    finished.
    
    Anybody with an idea why this is happening?
     

Share This Page