Comment 2 for bug 1581493
Revision history for this message
| Kyrylo Galanov (kgalanov) wrote Re: Unable to connect to WSGI daemon process 'keystone_main' | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Apparently MySQL crashed. Unfortunately, I can see the log file of the last run only.
Could you please reproduce it on the environment and ping me?
---
2016-05-10 02:37:29 18550 [Note] InnoDB: 5.6.23 started; log sequence number 1625977
02:37:29 UTC - mysqld got signal 11 ;
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.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.