WARNING: File name is too long to be saved correctly in TarGz archive!
-
Great plugin, and I’ve manually gone through and fixed the error I was getting, but is there anyway the plugin could notify me and not fail the backup when it encounters long file names?
Starting from line 13 of the log file I received via email:
[10-Oct-2017 08:32:53] Compressing files as TarGz. Please be patient, this may take a moment. [10-Oct-2017 08:34:27] WARNING: File name "wp-content/uploads/sites/...9700.png" is too long to be saved correctly in TarGz archive! [10-Oct-2017 08:34:27] WARNING: File name "wp-content/uploads/sites/...x150.png" is too long to be saved correctly in TarGz archive! [10-Oct-2017 08:34:27] WARNING: File name "wp-content/uploads/sites/...x270.png" is too long to be saved correctly in TarGz archive! [10-Oct-2017 08:34:27] WARNING: File name "wp-content/uploads/sites/...x300.png" is too long to be saved correctly in TarGz archive! [10-Oct-2017 08:34:27] WARNING: File name "wp-content/uploads/sites/...x180.png" is too long to be saved correctly in TarGz archive! [10-Oct-2017 08:34:27] WARNING: File name "wp-content/uploads/sites/...8593.png" is too long to be saved correctly in TarGz archive! [10-Oct-2017 08:34:27] WARNING: File name "wp-content/uploads/sites/...0x150.png" is too long to be saved correctly in TarGz archive! [10-Oct-2017 08:34:27] WARNING: File name "wp-content/uploads/sites/...32x32.png" is too long to be saved correctly in TarGz archive! [10-Oct-2017 08:34:27] WARNING: File name "wp-content/uploads/sites/...0x150.png" is too long to be saved correctly in TarGz archive! [10-Oct-2017 08:34:27] WARNING: File name "wp-content/uploads/sites/...9700.png" is too long to be saved correctly in TarGz archive! [10-Oct-2017 08:34:27] WARNING: File name "wp-content/uploads/sites/...2x192.png" is too long to be saved correctly in TarGz archive! [10-Oct-2017 08:34:30] Backup archive created. [10-Oct-2017 08:34:30] Archive size is 1.03 GB. [10-Oct-2017 08:34:30] 20542 Files with 1.20 GB in Archive. [10-Oct-2017 08:34:31] 1. Try to send backup file to an FTP server … [10-Oct-2017 08:34:31] Connected to FTP server: [10-Oct-2017 08:34:31] FTP client command: USER [10-Oct-2017 08:34:31] FTP server response: User logged in. [10-Oct-2017 08:34:31] FTP client command: SYST [10-Oct-2017 08:34:31] FTP server reply: UNIX [10-Oct-2017 08:34:31] FTP current folder is: [10-Oct-2017 08:34:31] FTP client command: PASV [10-Oct-2017 08:34:31] FTP server reply: Entering passive mode [10-Oct-2017 08:34:31] Starting upload to FTP … [10-Oct-2017 08:34:49] WARNING: ftp_nb_continue(): Accepted data connection [10-Oct-2017 08:34:49] ERROR: Cannot transfer backup to FTP server! [10-Oct-2017 08:34:51] 2. Try to send backup file to an FTP server … [10-Oct-2017 08:34:51] Connected to FTP server: [10-Oct-2017 08:34:51] FTP client command: USER [10-Oct-2017 08:34:51] FTP server response: User logged in. [10-Oct-2017 08:34:51] FTP client command: SYST [10-Oct-2017 08:34:51] FTP server reply: UNIX [10-Oct-2017 08:34:51] FTP client command: PASV [10-Oct-2017 08:34:51] FTP server reply: Entering passive mode [10-Oct-2017 08:34:51] Starting upload to FTP … [10-Oct-2017 08:34:51] WARNING: ftp_nb_continue(): Accepted data connection [10-Oct-2017 08:34:51] ERROR: Cannot transfer backup to FTP server! [10-Oct-2017 08:34:51] 3. Try to send backup file to an FTP server … [10-Oct-2017 08:34:51] Connected to FTP server: [10-Oct-2017 08:34:51] FTP client command: USER [10-Oct-2017 08:34:51] FTP server response: User logged in. [10-Oct-2017 08:34:51] FTP client command: SYST [10-Oct-2017 08:34:51] FTP server reply: UNIX [10-Oct-2017 08:34:51] FTP client command: PASV [10-Oct-2017 08:34:51] FTP server reply: Entering passive mode [10-Oct-2017 08:34:51] Starting upload to FTP … [10-Oct-2017 08:34:51] WARNING: ftp_nb_continue(): Accepted data connection [10-Oct-2017 08:34:51] ERROR: Cannot transfer backup to FTP server! [10-Oct-2017 08:34:51] ERROR: Step aborted: too many attempts! [10-Oct-2017 08:34:51] ERROR: Job has ended with errors in 118 seconds. You must resolve the errors for correct execution.
It seems that it thinks it successfully created the backup archive, but after I fixed only the file name length problem, it had no trouble uploading this job to the FTP.
Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
- The topic ‘WARNING: File name is too long to be saved correctly in TarGz archive!’ is closed to new replies.