toatlantis

I just checked the mentioned issues (1. backing up backups and 2. folder-change) before. Both issues are no reason for the problems. I posted only sizes of the compressed files. So I have never mentioned any differences between compressed and uncompressed files. … This might not be the problem, too.

And I already splitted up the backups. My database is 22 MB large. The rest is the content. …

I just started the backup.

Memory seems not to be the problem (see the following timeline). Maybe some timeouts? Maybe false memory-calculations?

Here is some kind of a timeline, what follows:

(1) Backup starts without any problems.
(2) Really fast, I get the following line within the console-ouput of the backup-plugin: “Komprimiere Dateien als Tar. Bitte habe einen Moment Geduld.” … in English something link: “Compressing files as tar. Please be patient.” …
(3) Parallel to the Compression, I get a folder under …/wp-content/uploads/backwpup-*****-temp (the stars indicate the unique identifier). In that folder, I do have a tar-file, which is 223 MB large (and rising).
(4) I first get the following linke within the console-output of the backup-plugin: “[05-Jan-2014 19:00:37] WARNUNG: Auftrag durch Inaktivit?t von mehr als 5 Minuten neu gestartet” … in English something like: “Warning: Job restart due to inactivity for more than 5 Minutes.”
(5) The size of the tar-file within the temp-Folder is still rising, now exceeding the above mentioned 256 MB. 429 MB large (and rising)
(6) I now get the following message within the console-output of the backup-plugin: “2. Versuche, Backup zu erstellen …” … in English: “Trying to make a backup for the 2nd time”.
(7) The size of the tar-file within the temp-Folder is still rising, now exceeding 531 MB large (and rising)
(8) I now get the following message within the console-output of the backup-plugin: “3. Versuche, Backup zu erstellen …” … in English: “Trying to make a backup for the 3rd time”.
(9) The size of the tar-file within the temp-Folder is still rising, now exceeding 634 MB large (and rising). It is now rising very incremental. Everytime I go on “reload” the size increases a bit. This has not been during the other stages mentioned above.
(10) I now get the following message within the console-output of the backup-plugin: “4. Versuche, Backup zu erstellen …” … in English: “Trying to make a backup for the 4th time”.
(11) … I get the following message: “Backup wurde erstellt.” … “backup created”.
(12) … now, the plugin tries to upload the file (666.2 MB on my FTP, 635,37 MB stated in the console log) to the dropbox, previously connected.
(13) within the console of the plugin, I get the statement: “11386 Dateien mit 631,86 MB in Archiven.” … 631,86 MB … third statement to the size of my archive. And none of them fits to the other.
(14) within the console of the plugin, I get the statement, that the upload just started.

Authentifiziert mit Dropbox von Benutzer T*** K*** (***@***.**)
Hochladen zur Dropbox hat begonnen …

(15) I get the job reset due to inactivity. Upload starts a 2nd time.

WARNUNG: Auftrag durch Inaktivit?t von mehr als 5 Minuten neu gestartet
2. Versuche, das Backup zur Dropbox zu senden …
Authentifiziert mit Dropbox von Benutzer T*** K*** (***@***.**)
Hochladen zur Dropbox hat begonnen …

(16) Whatever the following statement means, I get it in the console of the plugin:
(400) False offset will corrected
(17) After a very long time, I just get the following statement in the console of the plugin:

WARNUNG: Auftrag durch Inaktivit?t von mehr als 5 Minuten neu gestartet
3. Versuche, das Backup zur Dropbox zu senden …
Authentifiziert mit Dropbox von Benutzer T*** K*** (***@***.**)
Hochladen zur Dropbox hat begonnen …

(18) After a very long time, I get nearly the same statement in the console, but not, I get the unknown “400”-error again:

WARNUNG: Auftrag durch Inaktivit?t von mehr als 5 Minuten neu gestartet
4. Versuche, das Backup zur Dropbox zu senden …
Authentifiziert mit Dropbox von Benutzer T*** K*** (***@***.**)
Hochladen zur Dropbox hat begonnen …
<strong>(400) False offset will corrected</strong>

(19) After a very long time again (doing this for 1 hour now!), I get something news at the console. 5th try, but without the offset-correction-error-message:

WARNUNG: Auftrag durch Inaktivit?t von mehr als 5 Minuten neu gestartet
5. Versuche, das Backup zur Dropbox zu senden …
Authentifiziert mit Dropbox von Benutzer T*** K*** (***@***.**)
Hochladen zur Dropbox hat begonnen …

(20) After a very long time again, I get the following statement:

Backup übertragen zu https://api-content.dropbox.com/1/files/dropbox/***/***.tar
WARNUNG: Job mit Warnungen beendet in 3417 Sekunden. Bitte beheben Sie die Warnungen für eine korrekte Ausführung.

I do have 100 GB at my Dropbox-Account. so memory may not be the problem at all. Now my Dropbox syncs with my local laptop. So the tar-file may find its way. But nevertheless, I got the timout-warning 8 times. And I got a strange error-message in addition to that.

I do have a limit of 256 MB, as shown below. This is an extract from the “informations”-panel on the plugin-page.

PHP Memory Limit	256M
WordPress-Memory-Limit	256M
Maximales WordPress-Memory-Limit	256M

Where exactly do I find the “tmp”-folder? Is it a folder made by the backup-plugin (with the unique numbers in it?)

No. I’m hosted at df.eu (Domain Factory).

No help?

Hey Plugin-Developers,

on search for any solution for my problems, I just checked the maximal execution time. But this time is set to 300 seconds at my server. So, this can’t be the reason for my problems (details below).

Can you give me some advice, what to do?

WordPress-Version	3.8
BackWPup-Version	3.1.1 Pro-Version kaufen
PHP-Version	5.2.17
MySQL-Version	5.5.28-log
cURL-Version	7.24.0
cURL-SSL-Version	OpenSSL/1.0.0i
WP-Cron URL:	https://www.dertimm.de/***
Verbindung zum Server selbst:	Response Test O.K.
Temp Verzeichnis:	/kunden/***/wp-content/uploads/backwpup-***-temp/
Protokoll-Ordner:	/kunden/***/wp-content/uploads/backwpup-***-logs/
Server	Apache/2.2.22
Betriebssystem	Linux
PHP SAPI	cgi
Aktueller PHP user	***
Safe Mode	Aus
Max. Ausführungszeit	300 Sekunden
Alternative WP Cron	Aus
WP Cron abgeschaltet	Aus
CHMOD Verzeichnis	489
Server Zeit	17:26
Webseite Zeit	19:26
Webseite Zeitzone	Etc/GMT-2
Webseite Zeitversetzung	2 Stunden
Webseiten Sprache	de-DE
MySQL Client Encoding	utf8
Webseiten Charset	UTF-8
PHP Memory Limit	256M
WordPress-Memory-Limit	256M
Maximales WordPress-Memory-Limit	256M
Speicher in Benutzung	45,00 MB
Geladene PHP Erweiterungen	PDO, Reflection, SPL, SQLite, SimpleXML, Zend Optimizer, bcmath, bz2, calendar, cgi, ctype, curl, date, dba, dbase, dom, exif, filter, ftp, gd, gettext, hash, iconv, imap, json, libxml, mbstring, mcrypt, mhash, mysql, mysqli, openssl, pcre, pdo_mysql, pdo_sqlite, pgsql, posix, session, soap, standard, tokenizer, wddx, xml, xmlreader, xmlwriter, xsl, zlib

Hi!

I have the same problem. It seems as if the thumbnails can not be generated. But even at the frontend, no image is being displayed.

JF.merle … As you seem to have the problem by replacing a manage-images.php, where did you get the manage-images.php file? I just have the most recent one inside the “admin” folder and don’t know, at which place I should drag it.

Maybe, you can give us a more detailed description. (And hopefully a bug fix will come soon.)

Regards.