backup failed can't zip file
I got this error "Creating Archive ....open3: exec of /usr/bin/gzip -6 failed at /usr/local/cpanel
/Cpanel/IO/Tarball.pm line 85"
How to fix it?
Thank you
-
Hello :) Please check to see if the gzip RPM is installed on your system: rpm -qa|grep gzip
If it's not installed, please install it via:yum install gzip
If it is already installed, please check it's permissions/ownership:stat /usr/bin/gzip stat /bin/gzip
Thank you.0 -
this is result [QUOTE]root@www2 [~]# rpm -qa|grep gzip gzip-1.3.5-13.el5.centos root@www2 [~]# stat /usr/bin/gzip File: `/usr/bin/gzip' -> `../../bin/gzip' Size: 14 Blocks: 0 IO Block: 4096 symbolic link Device: 803h/2051d Inode: 56626351 Links: 1 Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2014-01-13 03:45:23.000000000 +0700 Modify: 2011-09-15 03:40:41.000000000 +0700 Change: 2011-09-15 03:40:41.000000000 +0700 root@www2 [~]# stat /bin/gzip File: `/bin/gzip' Size: 63316 Blocks: 126 IO Block: 4096 regular file Device: 801h/2049d Inode: 693331 Links: 3 Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2014-01-13 04:02:44.000000000 +0700 Modify: 2011-07-22 15:30:31.000000000 +0700 Change: 2013-12-08 19:11:04.000000000 +0700 root@www2 [~]#
is it correct?0 -
Yes, that looks normal. Feel free to open a support ticket using the link in my signature so we can take a closer look. Ensure you include specific instructions on how we can reproduce the error as opposed to simply pasting the error message. You can paste the ticket number here so we can update this thread with the outcome. Thank you. 0 -
Hi, I was submitted to licensepal and waiting for an answer Thank you 0 -
until now no answer from licensepal - - 0 -
[quote="bugton, post: 1562292">until now no answer from licensepal - -
You can open the support ticket with us if you have root access to your server using the instructions from my last response. Thank you.0 -
He was replied the ticket my fault it's symlinks of /usr/bin I can fix this problem Thank you all 0 -
I am happy to see the issue is now resolved. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
8 comments