[MCOL-2017] PrimProc Critical Alarms Created: 2018-12-11 Updated: 2022-11-05 Resolved: 2022-11-05 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | DMLProc |
| Affects Version/s: | 1.2.2 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Major |
| Reporter: | joe piscitella | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Environment: |
ubuntu 16.04 |
||
| Attachments: |
|
| Description |
|
mcsadmin> getAlarmSummary Active Alarm Counts: Critical = 1, Major = 0, Minor = 0, Warning = 0, Info = 0 Active Alarm List: AlarmID = 30 2018-12-11T04:43:12.705281-07:00 labsdb162.lab.llnw.net controllernode[348652]: 12.705229 |0|0|0| E 29 CAL0000: DBRM: error: SessionManager::getSystemState() failed (network) After SQL is run all logs (debug to crit)get spammed with PrimProc messages filling up file system. restart of environment from debug log including start of the PrimProc messages attached 30 minutes after restart |
| Comments |
| Comment by joe piscitella [ 2018-12-11 ] |
|
/var/log/mariadb/columnstore/trace# cat PrimProc.6276.log [0x55ef3e8f68d4] |
| Comment by joe piscitella [ 2018-12-14 ] |
|
resolved - |
| Comment by Todd Stoffel (Inactive) [ 2022-11-05 ] |
|
This item is being closed because it was well passed the expiration date with no activity. If you suspect this was done in error please create a new ticket. |