MySQL upgrade from 5.6 to 8.0
When trying to start MySQL 8.0 it complained about partially upgraded DD. Furthermore, it complained about not being to open a table S/AD.ibd which no longer exists there because we moved it to S/AD.ibd. We reverted back to MySQL 5.6 and it seems to be running fine now. It looks like it failed during converting the .frm files into the information_schema, and I suppose this is why we were able to revert back to 5.6.
My questions:
1) Does anyone have any idea what this could be?
2) Are there MySQL diagnostic tools I can run against our 5.6 instance to see if there is inconsistent state stored about our AD.ibd table?
Here is the full log if it's of interest:
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2018-06-22T15:02:56.236394Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 1831
2018-06-22T15:02:58.482400Z 1 [ERROR] [MY-011014] [Server] Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.
2018-06-22T15:02:58.864512Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2018-06-22T15:02:58.864621Z 0 [ERROR] [MY-010119] [Server] Aborting
2018-06-22T15:03:00.755015Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.11) MySQL Community Server - GPL.
2018-06-22T15:06:15.015157Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 2225
2018-06-22T15:06:17.585241Z 1 [ERROR] [MY-012592] [InnoDB] InnoDB: Operating system error number 2 in a file operation.
2018-06-22T15:06:17.585309Z 1 [ERROR] [MY-012593] [InnoDB] InnoDB: The error means the system cannot find the path specified.
2018-06-22T15:06:17.585330Z 1 [ERROR] [MY-012216] [InnoDB] InnoDB: Cannot open datafile for read-only: './S/AD.ibd' OS error: 71
2018-06-22T15:06:17.585354Z 1 [Warning] [MY-012019] [InnoDB] InnoDB: Ignoring tablespaceLD/ADbecause it could not be opened.
2018-06-22T15:06:18.511449Z 0 [Warning] [MY-010727] [Server] System table 'plugin' is expected to be transactional.
2018-06-22T15:06:18.627162Z 2 [Warning] [MY-010772] [Server] db.opt file not found for S database. Using default Character set.
mysqld: /export/home/pb2/build/sb_0-28122056-1523171044.09/rpm/BUILD/mysql-8.0.11/mysql-8.0.11/sql/dd/upgrade/table.cc:1076: bool dd::upgrade_57::add_triggers_to_table(THD*, TABLE*, const String_type&, const String_type&): Assertion `t->
get_event() >= t_type && (t->get_event() > t_type || t->get_action_time() >= t_time)' failed.
15:06:19 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
mysql upgrade
asked Jun 25 '18 at 13:26
m1s4mikem1s4mike
162
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
When trying to start MySQL 8.0 it complained about partially upgraded DD. Furthermore, it complained about not being to open a table S/AD.ibd which no longer exists there because we moved it to S/AD.ibd. We reverted back to MySQL 5.6 and it seems to be running fine now. It looks like it failed during converting the .frm files into the information_schema, and I suppose this is why we were able to revert back to 5.6.
My questions:
1) Does anyone have any idea what this could be?
2) Are there MySQL diagnostic tools I can run against our 5.6 instance to see if there is inconsistent state stored about our AD.ibd table?
Here is the full log if it's of interest:
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2018-06-22T15:02:56.236394Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 1831
2018-06-22T15:02:58.482400Z 1 [ERROR] [MY-011014] [Server] Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.
2018-06-22T15:02:58.864512Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2018-06-22T15:02:58.864621Z 0 [ERROR] [MY-010119] [Server] Aborting
2018-06-22T15:03:00.755015Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.11) MySQL Community Server - GPL.
2018-06-22T15:06:15.015157Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 2225
2018-06-22T15:06:17.585241Z 1 [ERROR] [MY-012592] [InnoDB] InnoDB: Operating system error number 2 in a file operation.
2018-06-22T15:06:17.585309Z 1 [ERROR] [MY-012593] [InnoDB] InnoDB: The error means the system cannot find the path specified.
2018-06-22T15:06:17.585330Z 1 [ERROR] [MY-012216] [InnoDB] InnoDB: Cannot open datafile for read-only: './S/AD.ibd' OS error: 71
2018-06-22T15:06:17.585354Z 1 [Warning] [MY-012019] [InnoDB] InnoDB: Ignoring tablespaceLD/ADbecause it could not be opened.
2018-06-22T15:06:18.511449Z 0 [Warning] [MY-010727] [Server] System table 'plugin' is expected to be transactional.
2018-06-22T15:06:18.627162Z 2 [Warning] [MY-010772] [Server] db.opt file not found for S database. Using default Character set.
mysqld: /export/home/pb2/build/sb_0-28122056-1523171044.09/rpm/BUILD/mysql-8.0.11/mysql-8.0.11/sql/dd/upgrade/table.cc:1076: bool dd::upgrade_57::add_triggers_to_table(THD*, TABLE*, const String_type&, const String_type&): Assertion `t->
get_event() >= t_type && (t->get_event() > t_type || t->get_action_time() >= t_time)' failed.
15:06:19 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
mysql upgrade
asked Jun 25 '18 at 13:26
m1s4mikem1s4mike
162
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
When trying to start MySQL 8.0 it complained about partially upgraded DD. Furthermore, it complained about not being to open a table S/AD.ibd which no longer exists there because we moved it to S/AD.ibd. We reverted back to MySQL 5.6 and it seems to be running fine now. It looks like it failed during converting the .frm files into the information_schema, and I suppose this is why we were able to revert back to 5.6.
My questions:
1) Does anyone have any idea what this could be?
2) Are there MySQL diagnostic tools I can run against our 5.6 instance to see if there is inconsistent state stored about our AD.ibd table?
Here is the full log if it's of interest:
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2018-06-22T15:02:56.236394Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 1831
2018-06-22T15:02:58.482400Z 1 [ERROR] [MY-011014] [Server] Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.
2018-06-22T15:02:58.864512Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2018-06-22T15:02:58.864621Z 0 [ERROR] [MY-010119] [Server] Aborting
2018-06-22T15:03:00.755015Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.11) MySQL Community Server - GPL.
2018-06-22T15:06:15.015157Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 2225
2018-06-22T15:06:17.585241Z 1 [ERROR] [MY-012592] [InnoDB] InnoDB: Operating system error number 2 in a file operation.
2018-06-22T15:06:17.585309Z 1 [ERROR] [MY-012593] [InnoDB] InnoDB: The error means the system cannot find the path specified.
2018-06-22T15:06:17.585330Z 1 [ERROR] [MY-012216] [InnoDB] InnoDB: Cannot open datafile for read-only: './S/AD.ibd' OS error: 71
2018-06-22T15:06:17.585354Z 1 [Warning] [MY-012019] [InnoDB] InnoDB: Ignoring tablespaceLD/ADbecause it could not be opened.
2018-06-22T15:06:18.511449Z 0 [Warning] [MY-010727] [Server] System table 'plugin' is expected to be transactional.
2018-06-22T15:06:18.627162Z 2 [Warning] [MY-010772] [Server] db.opt file not found for S database. Using default Character set.
mysqld: /export/home/pb2/build/sb_0-28122056-1523171044.09/rpm/BUILD/mysql-8.0.11/mysql-8.0.11/sql/dd/upgrade/table.cc:1076: bool dd::upgrade_57::add_triggers_to_table(THD*, TABLE*, const String_type&, const String_type&): Assertion `t->
get_event() >= t_type && (t->get_event() > t_type || t->get_action_time() >= t_time)' failed.
15:06:19 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
mysql upgrade
asked Jun 25 '18 at 13:26
m1s4mikem1s4mike
162
When trying to start MySQL 8.0 it complained about partially upgraded DD. Furthermore, it complained about not being to open a table S/AD.ibd which no longer exists there because we moved it to S/AD.ibd. We reverted back to MySQL 5.6 and it seems to be running fine now. It looks like it failed during converting the .frm files into the information_schema, and I suppose this is why we were able to revert back to 5.6.
My questions:
1) Does anyone have any idea what this could be?
2) Are there MySQL diagnostic tools I can run against our 5.6 instance to see if there is inconsistent state stored about our AD.ibd table?
Here is the full log if it's of interest:
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2018-06-22T15:02:56.236394Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 1831
2018-06-22T15:02:58.482400Z 1 [ERROR] [MY-011014] [Server] Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.
2018-06-22T15:02:58.864512Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2018-06-22T15:02:58.864621Z 0 [ERROR] [MY-010119] [Server] Aborting
2018-06-22T15:03:00.755015Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.11) MySQL Community Server - GPL.
2018-06-22T15:06:15.015157Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.11) starting as process 2225
2018-06-22T15:06:17.585241Z 1 [ERROR] [MY-012592] [InnoDB] InnoDB: Operating system error number 2 in a file operation.
2018-06-22T15:06:17.585309Z 1 [ERROR] [MY-012593] [InnoDB] InnoDB: The error means the system cannot find the path specified.
2018-06-22T15:06:17.585330Z 1 [ERROR] [MY-012216] [InnoDB] InnoDB: Cannot open datafile for read-only: './S/AD.ibd' OS error: 71
2018-06-22T15:06:17.585354Z 1 [Warning] [MY-012019] [InnoDB] InnoDB: Ignoring tablespaceLD/ADbecause it could not be opened.
2018-06-22T15:06:18.511449Z 0 [Warning] [MY-010727] [Server] System table 'plugin' is expected to be transactional.
2018-06-22T15:06:18.627162Z 2 [Warning] [MY-010772] [Server] db.opt file not found for S database. Using default Character set.
mysqld: /export/home/pb2/build/sb_0-28122056-1523171044.09/rpm/BUILD/mysql-8.0.11/mysql-8.0.11/sql/dd/upgrade/table.cc:1076: bool dd::upgrade_57::add_triggers_to_table(THD*, TABLE*, const String_type&, const String_type&): Assertion `t->
get_event() >= t_type && (t->get_event() > t_type || t->get_action_time() >= t_time)' failed.
15:06:19 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
mysql upgrade
mysql upgrade
asked Jun 25 '18 at 13:26
m1s4mikem1s4mike
162
asked Jun 25 '18 at 13:26
m1s4mikem1s4mike
162
edited Jun 25 '18 at 14:20
m1s4mike
asked Jun 25 '18 at 13:26
m1s4mikem1s4mike
162
asked Jun 25 '18 at 13:26
m1s4mikem1s4mike
162
asked Jun 25 '18 at 13:26
m1s4mikem1s4mike
162
162
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Don't use / (or certain other things that could confuse the file manager) in a table name.
Perhaps you can rename it?
Update
OK, S is the database name, AD is the table name.
No, you cannot move .ibd files around. There is critical information in ibdata1 that will get confused.
It is possible to do
RENAME TABLE X.AD TO Y.AD
(At least that was possible before 8.0. The internals of 8.0 are radically different; if such a cross-db RENAME TABLE fails, file a bug report with bugs.mysql.com )
answered Jun 26 '18 at 23:50
Rick JamesRick James
41.7k22258
S is the schema and A is the table name. I could rename it in the L schema but i'm still not sure why MySQL thinks table A still exists in the S schema. I was hoping there were diagnostic tools I could run against the MySQL instance which would shed some light on what is going on. Thanks for the response.
– m1s4mike
Jun 27 '18 at 17:02
Aha. I updated my Answer.
– Rick James
Jun 27 '18 at 18:49
I'll try running the RENAME statement and see if the error still appears when trying to upgrade from 5.6 to 8.0. In the meantime, I'll also test out the two back-up strategies we discussed here dba.stackexchange.com/questions/210524/…
– m1s4mike
Jun 27 '18 at 19:24
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f210518%2fmysql-upgrade-from-5-6-to-8-0%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Don't use / (or certain other things that could confuse the file manager) in a table name.
Perhaps you can rename it?
Update
OK, S is the database name, AD is the table name.
No, you cannot move .ibd files around. There is critical information in ibdata1 that will get confused.
It is possible to do
RENAME TABLE X.AD TO Y.AD
(At least that was possible before 8.0. The internals of 8.0 are radically different; if such a cross-db RENAME TABLE fails, file a bug report with bugs.mysql.com )
answered Jun 26 '18 at 23:50
Rick JamesRick James
41.7k22258
S is the schema and A is the table name. I could rename it in the L schema but i'm still not sure why MySQL thinks table A still exists in the S schema. I was hoping there were diagnostic tools I could run against the MySQL instance which would shed some light on what is going on. Thanks for the response.
– m1s4mike
Jun 27 '18 at 17:02
Aha. I updated my Answer.
– Rick James
Jun 27 '18 at 18:49
I'll try running the RENAME statement and see if the error still appears when trying to upgrade from 5.6 to 8.0. In the meantime, I'll also test out the two back-up strategies we discussed here dba.stackexchange.com/questions/210524/…
– m1s4mike
Jun 27 '18 at 19:24
add a comment |
Don't use / (or certain other things that could confuse the file manager) in a table name.
Perhaps you can rename it?
Update
OK, S is the database name, AD is the table name.
No, you cannot move .ibd files around. There is critical information in ibdata1 that will get confused.
It is possible to do
RENAME TABLE X.AD TO Y.AD
(At least that was possible before 8.0. The internals of 8.0 are radically different; if such a cross-db RENAME TABLE fails, file a bug report with bugs.mysql.com )
answered Jun 26 '18 at 23:50
Rick JamesRick James
41.7k22258
S is the schema and A is the table name. I could rename it in the L schema but i'm still not sure why MySQL thinks table A still exists in the S schema. I was hoping there were diagnostic tools I could run against the MySQL instance which would shed some light on what is going on. Thanks for the response.
– m1s4mike
Jun 27 '18 at 17:02
Aha. I updated my Answer.
– Rick James
Jun 27 '18 at 18:49
I'll try running the RENAME statement and see if the error still appears when trying to upgrade from 5.6 to 8.0. In the meantime, I'll also test out the two back-up strategies we discussed here dba.stackexchange.com/questions/210524/…
– m1s4mike
Jun 27 '18 at 19:24
add a comment |
Don't use / (or certain other things that could confuse the file manager) in a table name.
Perhaps you can rename it?
Update
OK, S is the database name, AD is the table name.
No, you cannot move .ibd files around. There is critical information in ibdata1 that will get confused.
It is possible to do
RENAME TABLE X.AD TO Y.AD
(At least that was possible before 8.0. The internals of 8.0 are radically different; if such a cross-db RENAME TABLE fails, file a bug report with bugs.mysql.com )
answered Jun 26 '18 at 23:50
Rick JamesRick James
41.7k22258
Don't use / (or certain other things that could confuse the file manager) in a table name.
Perhaps you can rename it?
Update
OK, S is the database name, AD is the table name.
No, you cannot move .ibd files around. There is critical information in ibdata1 that will get confused.
It is possible to do
RENAME TABLE X.AD TO Y.AD
(At least that was possible before 8.0. The internals of 8.0 are radically different; if such a cross-db RENAME TABLE fails, file a bug report with bugs.mysql.com )
answered Jun 26 '18 at 23:50
Rick JamesRick James
41.7k22258
edited Jun 27 '18 at 18:49
answered Jun 26 '18 at 23:50
Rick JamesRick James
41.7k22258
answered Jun 26 '18 at 23:50
Rick JamesRick James
41.7k22258
answered Jun 26 '18 at 23:50
Rick JamesRick James
41.7k22258
41.7k22258
S is the schema and A is the table name. I could rename it in the L schema but i'm still not sure why MySQL thinks table A still exists in the S schema. I was hoping there were diagnostic tools I could run against the MySQL instance which would shed some light on what is going on. Thanks for the response.
– m1s4mike
Jun 27 '18 at 17:02
Aha. I updated my Answer.
– Rick James
Jun 27 '18 at 18:49
I'll try running the RENAME statement and see if the error still appears when trying to upgrade from 5.6 to 8.0. In the meantime, I'll also test out the two back-up strategies we discussed here dba.stackexchange.com/questions/210524/…
– m1s4mike
Jun 27 '18 at 19:24
add a comment |
S is the schema and A is the table name. I could rename it in the L schema but i'm still not sure why MySQL thinks table A still exists in the S schema. I was hoping there were diagnostic tools I could run against the MySQL instance which would shed some light on what is going on. Thanks for the response.
– m1s4mike
Jun 27 '18 at 17:02
Aha. I updated my Answer.
– Rick James
Jun 27 '18 at 18:49
I'll try running the RENAME statement and see if the error still appears when trying to upgrade from 5.6 to 8.0. In the meantime, I'll also test out the two back-up strategies we discussed here dba.stackexchange.com/questions/210524/…
– m1s4mike
Jun 27 '18 at 19:24
S is the schema and A is the table name. I could rename it in the L schema but i'm still not sure why MySQL thinks table A still exists in the S schema. I was hoping there were diagnostic tools I could run against the MySQL instance which would shed some light on what is going on. Thanks for the response.
– m1s4mike
Jun 27 '18 at 17:02
S is the schema and A is the table name. I could rename it in the L schema but i'm still not sure why MySQL thinks table A still exists in the S schema. I was hoping there were diagnostic tools I could run against the MySQL instance which would shed some light on what is going on. Thanks for the response.
– m1s4mike
Jun 27 '18 at 17:02
Aha. I updated my Answer.
– Rick James
Jun 27 '18 at 18:49
Aha. I updated my Answer.
– Rick James
Jun 27 '18 at 18:49
I'll try running the RENAME statement and see if the error still appears when trying to upgrade from 5.6 to 8.0. In the meantime, I'll also test out the two back-up strategies we discussed here dba.stackexchange.com/questions/210524/…
– m1s4mike
Jun 27 '18 at 19:24
I'll try running the RENAME statement and see if the error still appears when trying to upgrade from 5.6 to 8.0. In the meantime, I'll also test out the two back-up strategies we discussed here dba.stackexchange.com/questions/210524/…
– m1s4mike
Jun 27 '18 at 19:24
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f210518%2fmysql-upgrade-from-5-6-to-8-0%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
