[MCOL-995] SQLSTATE[HY000]: General error: 1815 Internal error: The system is not yet ready to accept queries Created: 2017-10-31 Updated: 2018-05-07 Resolved: 2018-05-07 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | DMLProc |
| Affects Version/s: | 1.0.11 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Critical |
| Reporter: | blank | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
|
| Description |
|
SQLSTATE[HY000]: General error: 1815 Internal error: The system is not yet ready to accept queries |
| Comments |
| Comment by David Thompson (Inactive) [ 2017-10-31 ] |
|
Unfortunately i don't see any log files included in the support report under /var/log/mariadb/columnstore? Were these excluded or are there just none? I It's normal / possible that for a brief period that mysqld can be up before the columnstore backend services. Is your system permanently in this state? |
| Comment by blank [ 2017-10-31 ] |
|
hi, it's columnstore log under /var/log/mariadb/columnstore. |
| Comment by David Thompson (Inactive) [ 2017-11-01 ] |
|
I would normally expect to see some files like info.log, err.log, debug.log etc there. In both files these are missing. Can you confirm they are missing from your install too? What does:
show? |
| Comment by blank [ 2017-11-02 ] |
| Comment by blank [ 2017-11-02 ] |
|
I used the command ' /usr/local/mariadb/columnstore/bin/columnstoreSupport -a' to collect logs. it's the recent logs. |
| Comment by David Thompson (Inactive) [ 2017-11-06 ] |
|
Ok, so strange it seems no log files are created.. Can you run from mcsadmin: Successful Enabling of Logging And see if that starts logging, you should see info.log debug.log etc in /var/log/mariadb/columnstore. If it displays an error let me know. |
| Comment by David Thompson (Inactive) [ 2018-05-07 ] |
|
Not actionable with current information. As discussed mysqld can come up before the columnstore processes and return this error until the system is fully up but if the status shows active then it should not. Did you ever come back to troubleshooting this issue and enabling logs? |