can you please take a Look at #18003 if this Discussion help?

or tell us more details about your issue ....

I'm not sure how any code can bring down a Db unless it was somehow malicious but even then crashing a database...I never heard about that. I would like to guess this was first line tech support with that handy nugget of info. It may have been the crash that ruined your install?
Do you have a backup? What host are you using?

I am using InMotionHosting.com for the host provider and use a VPS. I will finish installing the update on the remainder of the websites on the server, but I can tell you I definitely had some issues. The server was flawless up until I started applying the update. Certainly coincidence is possible. I’ll let you know how the remainder of updates goes.

From: landed [mailto:notifications@github.com]
Sent: Wednesday, September 20, 2017 11:44 AM
To: joomla/joomla-cms joomla-cms@noreply.github.com
Cc: Steve Dunn sdunn@marketingape.com; Author author@noreply.github.com
Subject: Re: [joomla/joomla-cms] Updating to Joomla 3.8 crashes InnoDB (#18018)

I'm not sure how any code can bring down a Db unless it was somehow malicious but even then crashing a database...I never heard about that. I would like to guess this was first line tech support with that handy nugget of info. It may have been the crash that ruined your install?
Do you have a backup? What host are you using?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub#18018 (comment), or mute the threadhttps://github.com/notifications/unsubscribe-auth/AbRyOb659FJnR1HpuSYvk_m4hfDMsKscks5skUCygaJpZM4PeH0T.

Weirdly I had a similar issue today not sure if it is related... updated to 3.8 locally and MySQL went down, had to reboot to get it backup.

What mysql version etc
What version of Joomla were you updating from
Was there anything in the mysql logs

Personally I didn't bother looking, just assumed it was a process lockup for some reason or other. But thought it worth mentioning on here incase it has any relevance.

Here is some info on my configuration

• Server: Localhost via UNIX socket

• Server type: MySQL

• Server version: 5.6.37 - MySQL Community Server (GPL)

• Protocol version: 10

• User: root@localhost

• Server charset: UTF-8 Unicode (utf8)
  Web server

• cpsrvd 11.66.0.23

• Database client version: libmysql - 5.1.73

• PHP extension: mysqli[Documentation]https://marketingape.net:2087/cpsess0938720071/3rdparty/phpMyAdmin/url.php?url=https%3A%2F%2Fsecure.php.net%2Fmanual%2Fen%2Fbook.mysqli.php curl[Documentation]https://marketingape.net:2087/cpsess0938720071/3rdparty/phpMyAdmin/url.php?url=https%3A%2F%2Fsecure.php.net%2Fmanual%2Fen%2Fbook.curl.php mbstring[Documentation]https://marketingape.net:2087/cpsess0938720071/3rdparty/phpMyAdmin/url.php?url=https%3A%2F%2Fsecure.php.net%2Fmanual%2Fen%2Fbook.mbstring.php

• PHP version: 5.6.30
  phpMyAdmin

• Version information: 4.7.3

From: Brian Teeman [mailto:notifications@github.com]
Sent: Wednesday, September 20, 2017 1:28 PM
To: joomla/joomla-cms joomla-cms@noreply.github.com
Cc: Steve Dunn sdunn@marketingape.com; Author author@noreply.github.com
Subject: Re: [joomla/joomla-cms] Updating to Joomla 3.8 crashes InnoDB (#18018)

What mysql version etc
What version of Joomla were you updating from
Was there anything in the mysql logs

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub#18018 (comment), or mute the threadhttps://github.com/notifications/unsubscribe-auth/AbRyOUfLeHPNZZ-OsM2e-CJWZDyY8KDKks5skVkngaJpZM4PeH0T.

So first attempt to upgrade to 3.8 following crash, it has a problem while doing the ackeeba backup prior to installing 3.8. Here is the message ackeeba produced:
AJAX Loading Error
HTTP Status: 500 (Internal Server Error)
Internal status: error
XHR ReadyState: 4
Raw server response:
(HTML containing script tags)
Then, InnoDB and MySql crashes.

From: Brian Teeman [mailto:notifications@github.com]
Sent: Wednesday, September 20, 2017 1:28 PM
To: joomla/joomla-cms joomla-cms@noreply.github.com
Cc: Steve Dunn sdunn@marketingape.com; Author author@noreply.github.com
Subject: Re: [joomla/joomla-cms] Updating to Joomla 3.8 crashes InnoDB (#18018)

What mysql version etc
What version of Joomla were you updating from
Was there anything in the mysql logs

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub#18018 (comment), or mute the threadhttps://github.com/notifications/unsubscribe-auth/AbRyOUfLeHPNZZ-OsM2e-CJWZDyY8KDKks5skVkngaJpZM4PeH0T.

MySql logs indicate the table jycbs_weblinks gets corrupted. Is this table accessed as part of the update? I was able to do an Ackeeba backup successfully on its own (not part of the Joomla update process). Leads me to believe the update is corrupting the table. Here is the MySQL log:

2017-09-20 15:37:04 21532 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 9599
2017-09-20 15:37:04 7f5032e5f720 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./wmtlaw_jmla37/jycbs_weblinks.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

From: Brian Teeman [mailto:notifications@github.com]
Sent: Wednesday, September 20, 2017 1:28 PM
To: joomla/joomla-cms joomla-cms@noreply.github.com
Cc: Steve Dunn sdunn@marketingape.com; Author author@noreply.github.com
Subject: Re: [joomla/joomla-cms] Updating to Joomla 3.8 crashes InnoDB (#18018)

What mysql version etc
What version of Joomla were you updating from
Was there anything in the mysql logs

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub#18018 (comment), or mute the threadhttps://github.com/notifications/unsubscribe-auth/AbRyOUfLeHPNZZ-OsM2e-CJWZDyY8KDKks5skVkngaJpZM4PeH0T.

So from that information we can see that your issue is server related and
not to do with the upgrade as akeeba fails before the upgrade starts

On 20 Sep 2017 8:31 pm, "MarketingApe" notifications@github.com wrote:

So first attempt to upgrade to 3.8 following crash, it has a problem while
doing the ackeeba backup prior to installing 3.8. Here is the message
ackeeba produced:
AJAX Loading Error
HTTP Status: 500 (Internal Server
Error)
Internal status: error
XHR ReadyState: 4
Raw server
response:
(HTML containing script tags)
Then, InnoDB and MySql crashes.

From: Brian Teeman [mailto:notifications@github.com]
Sent: Wednesday, September 20, 2017 1:28 PM
To: joomla/joomla-cms joomla-cms@noreply.github.com
Cc: Steve Dunn sdunn@marketingape.com; Author author@noreply.github.com

Subject: Re: [joomla/joomla-cms] Updating to Joomla 3.8 crashes InnoDB
(#18018)

What mysql version etc
What version of Joomla were you updating from
Was there anything in the mysql logs

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://github.com/
joomla/joomla-cms#18018#issuecomment-330939880>, or mute the
thread<https://github.com/notifications/unsubscribe-
auth/AbRyOUfLeHPNZZ-OsM2e-CJWZDyY8KDKks5skVkngaJpZM4PeH0T>.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#18018 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8TTNW7uF-sZMGjIURCL_BHNTdJ2yks5skWf4gaJpZM4PeH0T
.

Did you get my follow-up email with respect to the table corruption that occurs?

From: Brian Teeman [mailto:notifications@github.com]
Sent: Wednesday, September 20, 2017 3:19 PM
To: joomla/joomla-cms joomla-cms@noreply.github.com
Cc: Steve Dunn sdunn@marketingape.com; Author author@noreply.github.com
Subject: Re: [joomla/joomla-cms] Updating to Joomla 3.8 crashes InnoDB (#18018)

So from that information we can see that your issue is server related and
not to do with the upgrade as akeeba fails before the upgrade starts

On 20 Sep 2017 8:31 pm, "MarketingApe" <notifications@github.commailto:notifications@github.com> wrote:

So first attempt to upgrade to 3.8 following crash, it has a problem while
doing the ackeeba backup prior to installing 3.8. Here is the message
ackeeba produced:
AJAX Loading Error
HTTP Status: 500 (Internal Server
Error)
Internal status: error
XHR ReadyState: 4
Raw server
response:
(HTML containing script tags)
Then, InnoDB and MySql crashes.

From: Brian Teeman [mailto:notifications@github.com]
Sent: Wednesday, September 20, 2017 1:28 PM
To: joomla/joomla-cms <joomla-cms@noreply.github.commailto:joomla-cms@noreply.github.com>
Cc: Steve Dunn <sdunn@marketingape.commailto:sdunn@marketingape.com>; Author <author@noreply.github.commailto:author@noreply.github.com>

Subject: Re: [joomla/joomla-cms] Updating to Joomla 3.8 crashes InnoDB
(#18018)

What mysql version etc
What version of Joomla were you updating from
Was there anything in the mysql logs

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://github.com/
https://github.com/%0b> joomla/joomla-cms#18018#issuecomment-330939880>, or mute the
thread<https://github.com/notifications/unsubscribe-
https://github.com/notifications/unsubscribe-%0b> auth/AbRyOUfLeHPNZZ-OsM2e-CJWZDyY8KDKks5skVkngaJpZM4PeH0T>.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#18018 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8TTNW7uF-sZMGjIURCL_BHNTdJ2yks5skWf4gaJpZM4PeH0T
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub#18018 (comment), or mute the threadhttps://github.com/notifications/unsubscribe-auth/AbRyOX3KYjTjVYfsf8MgsLEd45Wge4g0ks5skXMWgaJpZM4PeH0T.

I'm not the only one having issues with the upgrade. I hope this gets the attention it deserves. Here is the error from MySQL Log:

2017-09-20 15:37:04 21532 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 9599
2017-09-20 15:37:04 7f5032e5f720 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./wmtlaw_jmla37/jycbs_weblinks.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/18018

closing this Issue, please comment at #18020