Database update

Resolved shivda
(@shivda)

8 years, 3 months ago

After updating to 3.16.4 clearing the cache and clicking update database, my update is stuck at 67%. Debug is enabled.

Viewing 9 replies - 1 through 9 (of 9 total)

Thomas Patrick Levy
(@thomasplevy)

8 years, 3 months ago

@shivda,

Sorry this happened… It may be a timeout issue which I’ve fixed in version 3.16.5.

If you can rollback to a backup and then try again on 3.16.5 it may fix the issue.

Are you seeing any information in your debug.log that may point to an error of any kind that could help me determine what’s causing it to get stuck?

Thread Starter shivda
(@shivda)

8 years, 3 months ago

I am still having the issues, I did a rollback to 3.16.1 then I ran the update but the LifterLMS database update still stuck at 67%

Thread Starter shivda
(@shivda)

8 years, 3 months ago

I am getting a 500 error when I try to update the database.

Thomas Patrick Levy
(@thomasplevy)

8 years, 3 months ago

@shivda,

I am not sure what’s happening here. I am very sorry. You’ll have to enable WP_DEBUG and WP_DEBUG_LOG in your wp-config.php file (https://codex.ww.wp.xz.cn/WP_DEBUG) and then provide me with a copy of the error message found in your debug.log file.

There’s definitely something broken here but I’m really not sure what the issue is without your help to find the error message.

I’m very sorry about this but I promise I can write the mistake if you can provide me with an error message from your logs.

Thaks,
rwpett
(@rwpett)

8 years, 3 months ago
I set the debug and debug_log to true, tried to update the database and got the following error
Error 500 – Internal server error
An internal server error has occured!
Please try again later.
Found debug log information this time It says in the last few lines:
02-07-2018 @ 22:48:03 – Running llms_update_3160_update_quiz_settings callback
02-07-2018 @ 22:48:03 – Finished llms_update_3160_update_quiz_settings callback
02-07-2018 @ 22:48:03 – Running llms_update_3160_attempt_migration callback
02-07-2018 @ 22:48:03 – Finished llms_update_3160_attempt_migration callback
02-07-2018 @ 22:48:03 – Running llms_update_3160_lesson_to_quiz_relationships_migration callback
02-07-2018 @ 22:48:03 – Finished llms_update_3160_lesson_to_quiz_relationships_migration callback
02-07-2018 @ 22:48:03 – Running llms_update_3160_ensure_no_dupe_question_rels callback
02-07-2018 @ 22:48:03 – Finished llms_update_3160_ensure_no_dupe_question_rels callback
02-07-2018 @ 22:48:03 – Running llms_update_3160_ensure_no_lesson_dupe_rels callback
02-07-2018 @ 22:48:03 – Finished llms_update_3160_ensure_no_lesson_dupe_rels callback
02-07-2018 @ 22:48:03 – Running llms_update_3160_update_question_data callback
02-07-2018 @ 22:48:04 – Finished llms_update_3160_update_question_data callback
02-07-2018 @ 22:48:04 – Running llms_update_3160_update_attempt_question_data callback

The database update is stuck at 0%
tried removing and reinstalling the lifterlms plugin and no change.
Is there anything else I can do to help resolve this?

INFO on setup
Wordpress
——————————————-

Home Url: https://rabbithill.olt4you.ca
Site Url: https://rabbithill.olt4you.ca
Version: 4.9.4
Debug Mode: Yes
Locale: en_US
Multisite: No
Page For Posts: Not Set
Page On Front: Login Page (#127)
Permalink Structure: /%postname%
Show On Front: page
Wp Cron: Yes

Settings
——————————————-

Version: 3.16.6
Db Version: 3.15.1
Course Catalog: Membership Catalog (#8)
Course Catalog Per Page: -1
Course Catalog Sorting: menu_order,ASC
Membership Catalog: Membership Catalog (#8)
Membership Catalog Per Page: 9
Membership Catalog Sorting: menu_order
Site Membership: Not Set
Student Dashboard: View my course enrollments (#10)
Courses Endpoint: my-courses
Edit Endpoint: edit-account
Lost Password Endpoint: lost-password
Vouchers Endpoint: redeem-voucher
Autogenerate Username: no
Password Strength Meter: yes
Minimum Password Strength: strong
Terms Required: no
Terms Page: Not Set
Checkout Names: required
Checkout Address: optional
Checkout Phone: hidden
Checkout Email Confirmation: yes
Open Registration: yes
Registration Names: required
Registration Address: optional
Registration Phone: hidden
Registration Voucher: required
Registration Email Confirmation: yes
Account Names: required
Account Address: optional
Account Phone: optional
Account Email Confirmation: yes
Checkout Page: Purchase (#9)
Confirmation Endpoint: confirm-payment
Force Ssl Checkout: no
Country: CA
Currency: CAD
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Decimals: 2
Trim Zero Decimals: no
Recurring Payments: no
Email From Address: [email protected]
Email From Name: Rabbit Hill Training
Email Footer Text:
Email Header Image:
Cert Bg Width: 800
Cert Bg Height: 616
Cert Legacy Compat: yes

Gateways
——————————————-

Manual: Disabled
Manual Logging:
Manual Order: 1

Server
——————————————-

Mysql Version: 5.5.58
Php Curl: Yes
Php Default Timezone: UTC
Php Fsockopen: Yes
Php Max Input Vars: 1000
Php Max Upload Size: 64 MB
Php Memory Limit: 268435456
Php Post Max Size: 67108864
Php Soap: Yes
Php Suhosin: No
Php Time Limt: 30
Php Version: 7.0.27
Software: Apache
Wp Memory Limit: 40M

Theme
——————————————-

Name: Twenty Seventeen
Version: 1.4
Themeuri: https://ww.wp.xz.cn/themes/twentyseventeen/
Authoruri: https://ww.wp.xz.cn/
Template:
Child Theme: No
Llms Support: No

Plugins
——————————————-

1&1 WP Assistant: 4.0.0
Activity Log: 2.4.0
Import users from CSV with meta: 1.10.9.1
LifterLMS: 3.16.6
PDF Embedder: 3.1.8

Integrations
——————————————-

BbPress: No
BuddyPress: No

Template Overrides
——————————————-
- This reply was modified 8 years, 3 months ago by rwpett.
- This reply was modified 8 years, 3 months ago by rwpett. Reason: additional information from debug log
Thomas Patrick Levy
(@thomasplevy)

8 years, 3 months ago

@rwpett,

This is the LifterLMS log but not the server’s debug.log that will show the error message causing the 500.

You can find your debug.log file in the wp-content directory on your server which you can find via a filemanager or FTP (not through the WordPress admin panel).

Can you grab that file please and paste the contents!

Thanks,

rwpett
(@rwpett)

8 years, 3 months ago

Sorry, here you go:
[09-Feb-2018 23:53:32 UTC] PHP Warning: Invalid argument supplied for foreach() in /homepages/3/d88752171/htdocs/clickandbuilds/RabbitHillTraining/wp-content/plugins/1and1-wordpress-assistant/inc/dashboard-widget.php on line 168
[09-Feb-2018 23:53:32 UTC] PHP Warning: array_merge(): Argument #2 is not an array in /homepages/3/d88752171/htdocs/clickandbuilds/RabbitHillTraining/wp-content/plugins/1and1-wordpress-assistant/inc/dashboard-widget.php on line 181
Thomas Patrick Levy
(@thomasplevy)

8 years, 3 months ago
@rwpett,

These are not coming from LifterLMS and also Warnings will not cause a 500 error so I’m not sure we’ve found the source of the error…

Also: Do you have WP_CRON enabled? I saw another report of the upgrader getting stuck and it turned it was that WP_CRON. Our background upgrader relies on WP_CRON to process upgrades that take a while (a minute or more) so it’s possible that your upgrade got 67% though and then halted because the remaining updates were never triggered.

You could enable WP Crontrol (https://ww.wp.xz.cn/plugins/wp-crontrol/) to try to manually move the process forward

Look for the cron task “wp_llms_bg_updater_cron” and click the “Run” button on it if it’s scheduled and it says “now” next to the next run.

That should push it home!
- This reply was modified 8 years, 3 months ago by Thomas Patrick Levy. Reason: clarity
rwpett
(@rwpett)

8 years, 3 months ago

That has resolved the issue. Thank you

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Database update’ is closed to new replies.