The free forums are no longer in use. It remains available as read-only archive.
Log In
Home
12:00 am
1:
Backup Start Path and the backup start path are fine, buth the Temporary Folder has a double slash /www//administrator/backups is writeable, it would be nice to include it the same way as Backup Start Path so it can be manually corrected.
define("LM_CONFIG_INFO_ROOT_BPATH_TMP","Temporary Folder");
2:
define("LM_CONFIG_INFO_ROOT_PATH_TMP_SUB","this path needs to be created and be writeable in order for XCloner to work properly");
Which sub path or folder ?
3:Reason, Tarfile is corrupt, unexpected end.
Config: Joomla 1.5.7/VM .1.12/JoomFish 2.0
FTP path: /www (works) if i add a / it stops working.
Backup Start Path /www/ (works)
===Post=============================================
Problem Description:
Corrupted Tar
Actions Taken To Resolve:
Spending hours to figure it out
Diagnostic Information
Joomla! Version: Joomla! 1.5.7 Production/Stable [ Wovusani ] 9-September-2008 23:00 GMT
configuration.php: Writable (Mode: 644 ) | RG_EMULATION: N/A
Architecture/Platform: Linux 2.6.17.7ww1 ( i686) | Web Server: Apache/2.0.54 (Debian GNU/Linux) mod_ssl/2.0.54 OpenSSL/0.9.7e ( broomer.nl ) | PHP Version: 5.2.6-0.dotdeb.1
PHP Requirements: register_globals: Disabled | magic_quotes_gpc: Enabled | safe_mode: Disabled | MySQL Support: Yes | XML Support: Yes | zlib Support: Yes
mbstring Support (1.5): Yes | iconv Support (1.5): Yes | save.session_path: Writable | Max.Execution Time: 60 seconds | File Uploads: Enabled
MySQL Version: 4.1.15-Debian_0.dotdeb.4-log ( Localhost via UNIX socket )
Extended Information:
SEF: Enabled (with ReWrite) | FTP Layer: Disabled | htaccess: Implemented
PHP/suExec: User and Web Server accounts are the same. (PHP/suExec probably installed)
PHP Environment: API: cgi-fcgi | MySQLi: Yes | Max. Memory: 24M | Max. Upload Size: 8M | Max. Post Size: 8M | Max. Input Time: 90 | Zend Version: 2.2.0
Disabled Functions:
MySQL Client: 4.1.15 ( latin1 )
12:00 am
The temporary folder used is XCloner is a name mistake(we will correct that soon), in fact that is a required folder used mostly when restoring restore, anyway, the double slashes do not make any difference in the backup process, the path is the same as with one slash
So, if your backup Start path is let's say /home/user/www, then you also need to create and make writeable the /home/user/www/administrator/backups folder
As for issue 3., have you tried using a ftp client to download the backup and see if you have anymore issues? Also, is the processing reaching 100% when processing the files backup? And third, do you have enough disk space available to store a full site backup?
Ovidiu
All RSS1 Guest(s)
