Recent Topics

1 Jun 04, 2013 18:20    

Hi guys,

i just tried to update my blog, during backup the whole thing crashed and I cannot do anything anymore. Before I do something wrong I wanted to ask what is the best thing to do at this point.

Below please find the screen output. On the server, there is more than 500 GB empty space left.

-------

Checking .htaccess denial for directory: /kunden/369922_85462/_upgrade/

Downloading package to «/kunden/369922_85462/_upgrade/b2evolution-5.0.3-beta-5-2013-04-28-2013-06-04.zip»...

Unpacking package to «/kunden/369922_85462/_upgrade/b2evolution-5.0.3-beta-5-2013-04-28-2013-06-04»...

Switching to maintenance mode...
Verifying that all destination files can be overwritten...
Verifying «/kunden/369922_85462/cache»...
Verifying «/kunden/369922_85462/plugins»...
Verifying «/kunden/369922_85462/skins_email»...
Verifying «/kunden/369922_85462/install»...
Verifying «/kunden/369922_85462/xmlsrv»...
Verifying «/kunden/369922_85462/rsc»...
Verifying «/kunden/369922_85462/locales»...
Verifying «/kunden/369922_85462/inc»...
Verifying «/kunden/369922_85462/skins»...
Verifying «/kunden/369922_85462/htsrv»...
Verifying «/kunden/369922_85462/conf»...
Verifying «/kunden/369922_85462/cron»...
Verifying «/kunden/369922_85462/media»...
Verifying «/kunden/369922_85462/skins_adm»...

Starting backup to: «/kunden/369922_85462/_backup/2013-06-04-18-04-17/» ...

Checking .htaccess denial for directory: /kunden/369922_85462/_backup/
Creating folders/files backup...
Archiving files to «/kunden/369922_85462/_backup/2013-06-04-18-04-17/files.zip»...
Backing up «/kunden/369922_85462/7812_1028635695_MVM_0.tmp» ...
Backing up «/kunden/369922_85462/index.php» ...
Backing up «/kunden/369922_85462/10004_788716640_MVM_3.tmp» ...
Backing up «/kunden/369922_85462/7812_1028635695_MVM_8.tmp» ...
Backing up «/kunden/369922_85462/sitemap_a.php» ...
Backing up «/kunden/369922_85462/multiblogs.php» ...
Backing up «/kunden/369922_85462/index_multi.php» ...
Backing up «/kunden/369922_85462/cache/» ...
Backing up «/kunden/369922_85462/6380_82930802_MVM_6.tmp» ...
Backing up «/kunden/369922_85462/10004_788716640_MVM_5.tmp» ...
Backing up «/kunden/369922_85462/plugins/» ...
Backing up «/kunden/369922_85462/7812_1028635695_MVM_4.tmp» ...
Backing up «/kunden/369922_85462/6380_82930802_MVM_0.tmp» ...
Backing up «/kunden/369922_85462/default.php» ...
Backing up «/kunden/369922_85462/6380_82930802_MVM_1.tmp» ...
Backing up «/kunden/369922_85462/xmlsrv/» ...
Backing up «/kunden/369922_85462/crossdomain.xml» ...
Backing up «/kunden/369922_85462/7812_1028635695_MVM_2.tmp» ...
Backing up «/kunden/369922_85462/6552_89204928_MVM_0.tmp» ...
Backing up «/kunden/369922_85462/favicon.ico.bak» ...
Backing up «/kunden/369922_85462/blog6.php» ...
Backing up «/kunden/369922_85462/rsc/» ...
Backing up «/kunden/369922_85462/6380_82930802_MVM_2.tmp» ...
Backing up «/kunden/369922_85462/10004_788716640_MVM_6.tmp» ...
Backing up «/kunden/369922_85462/10004_788716640_MVM_7.tmp» ...
Backing up «/kunden/369922_85462/locales/» ...
Backing up «/kunden/369922_85462/sitemap_blogs.php» ...
Backing up «/kunden/369922_85462/blog1.php» ...
Backing up «/kunden/369922_85462/__eigene_daten/» ...
Backing up «/kunden/369922_85462/6380_82930802_MVM_4.tmp» ...
Backing up «/kunden/369922_85462/10004_788716640_MVM_4.tmp» ...
Backing up «/kunden/369922_85462/inc/» ...
Backing up «/kunden/369922_85462/admin.php» ...
Backing up «/kunden/369922_85462/blog2.php» ...
Backing up «/kunden/369922_85462/skins/» ...
Backing up «/kunden/369922_85462/chCounter/» ...
Backing up «/kunden/369922_85462/.htaccess» ...
Backing up «/kunden/369922_85462/charts.txt» ...
Backing up «/kunden/369922_85462/7812_1028635695_MVM_3.tmp» ...
Backing up «/kunden/369922_85462/a_noskin.php» ...
Backing up «/kunden/369922_85462/blog4.php» ...
Backing up «/kunden/369922_85462/6380_82930802_MVM_7.tmp» ...
Backing up «/kunden/369922_85462/blog5.php» ...
Backing up «/kunden/369922_85462/a_stub.php» ...
Backing up «/kunden/369922_85462/sample.htaccess» ...
Backing up «/kunden/369922_85462/summary.php» ...
Backing up «/kunden/369922_85462/7812_1028635695_MVM_5.tmp» ...
Backing up «/kunden/369922_85462/10004_788716640_MVM_2.tmp» ...
Backing up «/kunden/369922_85462/contact.php» ...
Backing up «/kunden/369922_85462/statistik/» ...
Backing up «/kunden/369922_85462/blog7.php» ...
Backing up «/kunden/369922_85462/htsrv/» ...
Backing up «/kunden/369922_85462/7812_1028635695_MVM_1.tmp» ...
Backing up «/kunden/369922_85462/conf/» ...
Backing up «/kunden/369922_85462/10004_788716640_MVM_0.tmp» ...
Backing up «/kunden/369922_85462/cron/» ...
Backing up «/kunden/369922_85462/media/» ...
Backing up «/kunden/369922_85462/license.txt» ...
Backing up «/kunden/369922_85462/skins_adm/» ...
Backing up «/kunden/369922_85462/7812_1028635695_MVM_6.tmp» ...
Backing up «/kunden/369922_85462/6380_82930802_MVM_3.tmp» ...
Backing up «/kunden/369922_85462/10004_788716640_MVM_1.tmp» ...
Backing up «/kunden/369922_85462/blog3.php» ...
Backing up «/kunden/369922_85462/6380_82930802_MVM_5.tmp» ...
Creating database backup...
Dumping tables to «/kunden/369922_85462/_backup/2013-06-04-18-04-17/db.sql»...
Backing up table «chc_access» ...
Backing up table «chc_config» ...
Backing up table «chc_counted_users» ...
Backing up table «chc_data» ...
Backing up table «chc_downloads_and_hyperlinks» ...
Backing up table «chc_downloads_and_hyperlinks_logs» ...
Backing up table «chc_ignored_users» ...
Backing up table «chc_locale_information» ...
Backing up table «chc_log_data» ...
Backing up table «chc_online_users» ...
Backing up table «chc_pages» ...
Backing up table «chc_referrers» ...
Backing up table «chc_screen_resolutions» ...
Backing up table «chc_search_engines» ...
Backing up table «chc_user_agents» ...
Backing up table «evo_antispam» ...
Backing up table «evo_basedomains» ...
Backing up table «evo_bloggroups» ...
Backing up table «evo_blogs» ...
Backing up table «evo_blogusers» ...
Backing up table «evo_categories» ...
Backing up table «evo_coll_settings» ...
Backing up table «evo_comments» ...
Backing up table «evo_country» ...
Backing up table «evo_cron__log» ...
Backing up table «evo_cron__task» ...
Backing up table «evo_currency» ...
Backing up table «evo_files» ...
Backing up table «evo_filetypes» ...
Backing up table «evo_global__cache» ...
Backing up table «evo_groups» ...
Backing up table «evo_groups__groupsettings» ...
Backing up table «evo_hitlog» ...

Fatal error: Allowed memory size of 104857600 bytes exhausted (tried to allocate 61 bytes) in /kunden/369922_85462/inc/_core/model/db/_db.class.php on line 1095

--------

Help please! Thanks in advance!

2 Jun 04, 2013 18:24

Currently, I cannot access the webpage:

----

503 Service Unavailable

System upgrade is in progress. Please reload this page in a few minutes.

Site administrators: please view the source of this page for details.

----

How can I change this to display the page as it was before?

3 Jun 04, 2013 18:41

Got it out of maintenance mode. Still, update didn't work automatically. Any tips?

4 Jun 05, 2013 03:06

It seems your server did not have enough memory to back everything up before starting upgrade.

What version did you upgrade FROM?

5 Jun 05, 2013 15:49

Hi Francois,

the current version is 4.1.6.

Concerning the harddrive, there is more that 500gig of free space available. By memory do you mean RAM?

Thanks!

6 Jun 05, 2013 15:53

Looks like it hit the

PHP memory_limit 100M

How can I change that and why does the script require 100MB of memory?

7 Jun 05, 2013 19:36

You can change it in the php.ini configuration file.

It doesn't seem right that we need 100M of memory indeed, unless you have debugging turned on, which will keep tons of SQL requests in memory. Can you confirm you don't have debugging turned on?

Thank you.

8 Jun 06, 2013 14:28

Debugging should be of, the content of _advanced.php is still the default:

---

/**
* Display debugging informations?
*
* 0 = no
* 1 = yes
* 2 = yes and potentially die() to display debug info (needed before redirects, e-g message_send.php)
* 'pwd' = require password
*
* @global integer
*/
$debug = 'pwd';

/**
* When $debug is 'pwd' and you set a /password/ below,
* you can turn on debugging at any time by adding ?debug=YOUR_PASSWORD to your url.
* You can turn off by adding just ?debug
*
* @var string
*/
$debug_pwd = '';

---

...and I did not add ?debug=YOUR_PASSWORD or anything to the url. I that what you meant?

In case the automatic update will keep on not working, would it be safe to simply download and overwrite all files?

Thanks!

10 Jun 06, 2013 18:01

Tried to manually update. Got the following error:

MySQL error!
Unknown column 'sess_lastseen' in 'evo_sessions'(Errno=1054)
Your query:
ALTER TABLE evo_sessions CHANGE COLUMN sess_lastseen sess_lastseen_ts TIMESTAMP NOT NULL DEFAULT '2000-01-01 00:00:00' COMMENT 'User last logged activation time. Value may be off by up to 60 seconds'

Any idea?

11 Jun 06, 2013 19:02

We'll check on that.

Regarding your memory exhaustion error, could you confirm it also happens when you use the backup feature (instead of the upgrade feature, which includes backup).

Thank you.

-Francois.

12 Jun 06, 2013 20:47

Confirmed, same error. My guess would be the db is too big if zipping is completely done in RAM.

Thanks!

13 Jun 10, 2013 13:31

Hi Francois,

any news on the failure during update?

Could you perhaps tell me how long you think for looking into the issue? I just ask because our site is down for a while now and if it would take longer, I would try to reverse the whole procedure with the backups I have.

Thanks a lot!

14 Jun 10, 2013 16:07

You *have* to revert to a backup no matter what.

The probability upgrade can recover from a failed upgrade is very very very low.

Also can you confirm that your 4.1.6 to 5.0.3 upgrade was made from a clean 4.1.6 install and not one that had been partially upgraded before.

We did make the test and a stock 4.1.6 install does upgrade to 5.0.3 without Problems. It does seem you had a partially upgraded db priori to your manual upgrade attempt.

Please restore a backup that you know has not suffered a partial upgrade and try from there.

Otherwise, it's going to be a tedious task to recover from a partially upgraded db. It will require some PHP and MySQL skills.

15 Jun 10, 2013 16:35

Hi Francois,

I did not partially update the b2evo db, the only thing I did are some hacks to the skin (in the custom skin folder though) and some manual language extensions. Also I installed a few plugins. Additionally I installed chCounter that also has some data in the db.

I have three blogs within the b2evo installation with multiple posts per blog - I think this would be the main difference to a fresh install which would be empty.

I'll try to revert to backup and update again.

16 Jun 16, 2013 20:51

I just tried to revert the whole process

1) files - no problem
2) database - problem here

I did a backup of the whole database in phpmyadmin by choosing 'export' in the start page, thus exported the whole database, not the single tables.
For reverting the update process I dropped all tables in the database on the server, then tried an import of the backup file. The problem is that I do not have permission on my server to create a database, I can only use the database that's already there, called "db...[some number]". After the tool uploaded the backup file, it threw an error telling me that the database I was trying to import was already there.

Can you tell me what I have to do in order to just import the old tables into the given database from the backup file which contains the database on the first layer, followed by the tables? Is there some nice SQL command I can use? I am a real newb when it comes to SQL, would be very happy if you could give a hint.

Thanks alot!

17 Jun 20, 2013 01:39

You can open the .SQL file with a text editor and comment out the "CREATE DATABASE" statement.

Then you can import into an existing database.


Form is loading...