WordPress Designpraxis Forum

WordPress Designpraxis Forum » BackUpWordPress Issues

1. GLehnhoff
   Member

   With the new version I always get following error when I try to do a backup:

   Backups Verwalten
   Your backup is being processed.
   Internal Server Error
   The server encountered an internal error or misconfiguration and was unable to complete your request.

   Please contact the server administrator, service@webmailer.de and inform them of the time the error occurred, and anything you might have done that may have caused the error.

   More information about this error may be available in the server error log.
   -------
   I use WordPress 2.2.3 DE, PHP4, mySQL 5

   Posted 4 years ago #

2. rol
   Key Master

   Gerhard, this error unfortunately is a server-side issue. With WordPress, most of these error 500 messages derive from a faulty .htaccess. Try to remove your .htaccess files(s) and switch to standard permalinks for a test.

   Posted 4 years ago #

3. GLehnhoff
   Member

   Well rol,

   let's start with this issue before we come to the issue with the not working Restore. I manage several sites with the version 0.3.1 on WP 2.2.3.

   My Permalinks are standard. There is non .htaccess-file in place (there was one but I head problems with it which disapearded after deleting the .htaccess-file).

   I have three full backups in my backup-directory which are not shown in "Manage Backups" (Backups verwalten). In there, only the SQL-Backups are shown. These full backups seem to be ok. So, I assume that the copy worked alright and that the crash comes somewhere later.

   I can't download the SQL-backups within BackUpWordPress because they lead to a file like "farzCaqzS" without extension. I have 10 files like this in my backup-directory. There are all 4MB large and seem to be the SQL-Backups listet in "Manage Backups". When I copy these files manually to my Linux-Desktop (Ubuntu 7.04), my system seems to see the file as an archive but can't open it, even not with the extension "tar.gz".

   And now the really funny thing: On this site, let's call it "BGM", I have ftp-access only and I am not able to rename files. I am only able to delete and copy files.

   Does it ring? (You know, what I mean - I don't know whether this can be translated word by word from German to English :-)

   I will check soon with another site, let's call it "SW", where I have full ssh-access and no problems with renaming files.

   Cheers - Gerhard

   Posted 4 years ago #

4. GLehnhoff
   Member

   Here I am again. I continue with my issues above.

   Now, I work on the above mentioned second site, called "SW". Here I still have the older version 0.1.2 installed on WP 2.2.3. Here, I don't have any problems with renaming files. Permalinks are standard, there is a .htaccess-file in place with regards to the mod-rewrite-module (can anybody explain what it does?) and some manually added lines by myself for Error-Document-Handling (403, 404, and 500 - lead all to the start-page). All Backups seems to be ok, all can be downloaded from the "Manage Backups" (Backups verwalten) screen.

   On weekend I will upgrade this version to the latest one and will than see what happens.

   I will come to the topic "Restore", which is part of another thread, later. As both systems mentioned above, "SW" and "BGM", are Live-Systems, I will set-up a third system called "Test" and will do the Restore-Testing over there.

   Cheers - gl

   Posted 4 years ago #

5. GLehnhoff
   Member

   I was wrong. I managed to open one of the archives called for example "farzCaqzS". It seems to be a full backup. All 4MB files mentioned two comments above are full backups, not sql-backups.

   Posted 4 years ago #

6. GLehnhoff
   Member

   Well, on "BGM" (see above), Backup SQL works fine. Full-Backup seems to crash (Interneal Error) when the temporary Zip-File (2 are created) should be renamed. Could this be?

   Posted 4 years ago #

7. rol
   Key Master

   Gerhard, Files named "farzCaqzS" and similar are the temporary files created while archiving. This is the procedure of a backup task:

   - creating a backup directory named with a timestamp
   - building SQL-Dump
   - copying the files to backup into the backup directory
   - archiving the backup directory

   So i suppose you are right. Everything works fine until the point your finished archive file "farzCaqzS" should be renamed.
   This seems strange, since the permissions seem to be right for reading and writing.
   Have you ever tried to run an offline copy of your blog and try BackUpWordPress there?
   Here is a tuorial for it: http://wordpress.designpraxis.at/2007/09/21/how-to-setup-a-cross-platform-environment-for-wordpress-plugin-development/

   Posted 4 years ago #

RSS feed for this topic

Reply

You must log in to post.