System software alerts
This topic presents a list of default software related issues and events for Cloud Pak for Data System.
Software related issues
Issues are stateful alerts, they are ongoing until the problem is fixed.
| Reason Code | Severity | Title | Type | Group |
|---|---|---|---|---|
| 154 | MAJOR | Soft power off action for node failed, could not recover node | SW_SERVICE_REQUESTED | SW |
| 155 | WARNING | RAID5 array needs attention | SW_SERVICE_REQUESTED | SW |
| 158 | MAJOR | NPS replication state change | SW_SERVICE_REQUESTED | SW |
| 159 | MAJOR | NPS regent source disk error | SW_SERVICE_REQUESTED | SW |
| 160 | MAJOR | NPS regent fault | SW_SERVICE_REQUESTED | SW |
| 198 | INFORMATION | Test SW alert | SW_SERVICE_REQUESTED | SW |
| 207 | MINOR | SEL is full and cannot be cleaned | HW_NEEDS_ATTENTION | SW |
| 401 | MAJOR | GPFS node failed to start | SW_NEEDS_ATTENTION | SW |
| 402 | MINOR | GPFS nsd failed to start | SW_NEEDS_ATTENTION | SW |
| 404 | MAJOR, CRITICAL | GPFS local partition failed to be mounted | SW_NEEDS_ATTENTION | SW |
| 405 | MAJOR, CRITICAL | GPFS filesystem failed to be mounted | SW_NEEDS_ATTENTION | SW |
| 407 | CRITICAL, MAJOR | Application component is not healthy | SW_NEEDS_ATTENTION | SW |
| 409 | MAJOR | Unable to start Call Home Daemon | SW_NEEDS_ATTENTION | SW |
| 410 | MINOR | Unable to stop Call Home Daemon | SW_NEEDS_ATTENTION | SW |
| 411 | MAJOR | Heavy swap usage | SW_NEEDS_ATTENTION | SW |
| 412 | MAJOR | Node time not in sync | SW_NEEDS_ATTENTION | SW |
| 415 | MAJOR | Docker service failed | SW_NEEDS_ATTENTION | SW |
| 426 | MAJOR | Firewall service cannot be started | SW_NEEDS_ATTENTION | SW |
| 432 | MAJOR | Application VMs cannot be started on a node | SW_NEEDS_ATTENTION | SW |
| 436 | MAJOR | Failed to collect status from resource manager | SW_NEEDS_ATTENTION | SW |
| 437 | MAJOR | Duplicate containers running | SW_NEEDS_ATTENTION | SW |
| 438 | MAJOR | Service cannot be (re)started | SW_NEEDS_ATTENTION | SW |
| 439 | WARNING | Openshift node is not ready | SW_NEEDS_ATTENTION | SW |
| 440 | CRITICAL, WARNING | Openshift service is not ready | SW_NEEDS_ATTENTION | SW |
| 441 | MAJOR | Incorrect node kernel params | SW_NEEDS_ATTENTION | SW |
| 442 | WARNING | Timezones mismatch between nodes | SW_NEEDS_ATTENTION | SW |
| 443 | CRITICAL | Cannot mount NFS partition on virtual machine | SW_NEEDS_ATTENTION | SW |
| 444 | MAJOR | Unable to start VDB container | SW_NEEDS_ATTENTION | SW |
| 445 | MAJOR | Unable to stop VDB container | SW_NEEDS_ATTENTION | SW |
| 446 | WARNING | ICP4D service is not ready | SW_NEEDS_ATTENTION | SW |
| 447 | MAJOR | GlusterFS component is not healthy | SW_NEEDS_ATTENTION | SW |
| 451 | WARNING | Webconsole service is not ready | SW_NEEDS_ATTENTION | SW |
| 452 | WARNING | NFS partition cannot be exported | SW_NEEDS_ATTENTION | SW |
| 453 | WARNING | Unreachable or missing device for NSD | SW_NEEDS_ATTENTION | SW |
| 455 | MINOR | Failed to cordon a node | SW_NEEDS_ATTENTION | SW |
| 456 | MINOR | Failed to uncordon a node | SW_NEEDS_ATTENTION | SW |
| 457 | WARNING | GPFS node is not CCR-based | SW_NEEDS_ATTENTION | SW |
| 459 | MAJOR | IPS container versions mismatch | SW_NEEDS_ATTENTION | SW |
| 460 | WARNING | Portworx component is not healthy | SW_NEEDS_ATTENTION | SW |
| 463 | WARNING | NPS AEK security event | SW_NEEDS_ATTENTION | SW |
| 464 | WARNING | NPS history capture event | SW_NEEDS_ATTENTION | SW |
| 465 | WARNING | NPS history load event | SW_NEEDS_ATTENTION | SW |
| 466 | WARNING | NPS network interface state changed | SW_NEEDS_ATTENTION | SW |
| 467 | MAJOR | NPS replication commit delta exceeded | SW_NEEDS_ATTENTION | SW |
| 468 | MAJOR | NPS replication configuration conflict | SW_NEEDS_ATTENTION | SW |
| 469 | MAJOR | NPS replication conflicting updates | SW_NEEDS_ATTENTION | SW |
| 470 | MAJOR | NPS replication maximum apply tries | SW_NEEDS_ATTENTION | SW |
| 471 | MAJOR | NPS replication missed metadata heartbeat | SW_NEEDS_ATTENTION | SW |
| 472 | MAJOR | NPS replication multiple master | SW_NEEDS_ATTENTION | SW |
| 473 | MAJOR | NPS replication nodes system time offset error | SW_NEEDS_ATTENTION | SW |
| 474 | MAJOR | NPS replication pts error | SW_NEEDS_ATTENTION | SW |
| 475 | MAJOR | NPS replication pts utilization exceeded | SW_NEEDS_ATTENTION | SW |
| 476 | MAJOR | NPS replication role changed | SW_NEEDS_ATTENTION | SW |
| 477 | MINOR | NPS runaway query | SW_NEEDS_ATTENTION | SW |
| 478 | MINOR | NPS SPU process cored | SW_NEEDS_ATTENTION | SW |
| 479 | WARNING | NPS SPU network interface errors | SW_NEEDS_ATTENTION | SW |
| 480 | WARNING | NPS SPU network interface not bonded | SW_NEEDS_ATTENTION | SW |
| 481 | WARNING | NPS topology imbalance | SW_NEEDS_ATTENTION | SW |
| 482 | MAJOR | NPS transaction limit event | SW_NEEDS_ATTENTION | SW |
| 483 | WARNING | NPS custom event 1 | SW_NEEDS_ATTENTION | SW |
| 484 | WARNING | NPS custom event 2 | SW_NEEDS_ATTENTION | SW |
| 601 | MAJOR | Unable to bring-up floating IP | FLOATING_IP_ISSUE | SW |
| 602 | MAJOR | Unable to bring-down floating IP | FLOATING_IP_ISSUE | SW |
| 603 | MAJOR | Unable to bring-up floating IP - cannot connect to server | FLOATING_IP_ISSUE | SW |
| 604 | MAJOR | Unable to bring-down floating IP - cannot connect to server | FLOATING_IP_ISSUE | SW |
| 605 | MAJOR | Unable to bring-up floating IP | VM_FLOATING_IP_ISSUE | SW |
| 606 | MAJOR | Unable to bring-down floating IP | VM_FLOATING_IP_ISSUE | SW |
| 610 | MAJOR | Floating IP interface is up, but inactive in network manager | FLOATING_IP_ISSUE | SW |
| 613 | MAJOR | NPS application is stuck in transition state | SW_NEEDS_ATTENTION | SW |
| 614 | MAJOR | NPS application is not online | SW_NEEDS_ATTENTION | SW |
| 701 | CRITICAL | Appliance application went down due to disabled node | APPLIANCE_APPLICATION_DOWN | SW |
| 703 | CRITICAL | Appliance application can't start | APPLIANCE_APPLICATION_DOWN | SW |
| 704 | CRITICAL | Appliance application went down | APPLIANCE_APPLICATION_DOWN | SW |
| 859 | INFORMATION | NPS container was migrated | APPLIANCE_EVENT | SW |
| 901 | CRITICAL | Storage utilization above threshold | STORAGE_UTILIZATION | SW |
| 903 | WARNING | NPS hardware disk full | STORAGE_UTILIZATION | SW |
Software events
Events are stateless alerts, that is, they are related to a point-in-time event.| Reason Code | Severity | Title | Type | Group |
|---|---|---|---|---|
| 153 | WARNING | Kernel panic(s) occurred | SW_SERVICE_REQUESTED | SW |
| 301 | WARNING | Action to restore a GPFS component failed | ACTION_FAILED | SW |
| 305 | WARNING | Failed to enable a node | ACTION_FAILED | SW |
| 307 | MAJOR | Application disabling failed | ACTION_FAILED | SW |
| 308 | MAJOR | Application enabling failed | ACTION_FAILED | SW |
| 310 | MAJOR | VM start-up action failed | ACTION_FAILED | SW |
| 311 | MINOR | VM stop action failed | ACTION_FAILED | SW |
| 312 | WARNING | Failed to enable a storage drive | ACTION_FAILED | SW |
| 313 | WARNING | Failed to disable a storage drive | ACTION_FAILED | SW |
| 314 | WARNING | Soft power off failed for node | ACTION_FAILED | SW |
| 315 | MAJOR | Failed to set node personality | ACTION_FAILED | SW |
| 317 | MAJOR | Application initialization has failed | ACTION_FAILED | SW |
| 319 | INFORMATION | Failed to disable a node | ACTION_FAILED | SW |
| 458 | INFORMATION | Node was disabled but VM was not reported as shut down | SW_NEEDS_ATTENTION | SW |
| 501 | CRITICAL | Start-up failed due to container start error | STARTUP_FAILED | SW |
| 502 | CRITICAL | Application start-up timeout | STARTUP_FAILED | SW |
| 503 | CRITICAL | Start-up timeout on waiting for healthy nodes | STARTUP_FAILED | SW |
| 506 | CRITICAL | Application start-up aborted due to VM stop error | STARTUP_FAILED | SW |
| 507 | CRITICAL | Start-up failed due to VM start error | STARTUP_FAILED | SW |
| 801 | INFORMATION | Node disabled by user | APPLIANCE_EVENT | SW |
| 802 | INFORMATION | Node disabled by system | APPLIANCE_EVENT | SW |
| 803 | INFORMATION | Node enabled by user | APPLIANCE_EVENT | SW |
| 804 | INFORMATION | Node enabled by system | APPLIANCE_EVENT | SW |
| 806 | INFORMATION | Node init requested | APPLIANCE_EVENT | SW |
| 807 | INFORMATION | Application start requested | APPLIANCE_EVENT | SW |
| 808 | INFORMATION | Application stop requested | APPLIANCE_EVENT | SW |
| 809 | INFORMATION | Unreachable node restart requested | APPLIANCE_EVENT | SW |
| 810 | INFORMATION | Docker service restarted | APPLIANCE_EVENT | SW |
| 812 | INFORMATION | GPFS issue recovered | APPLIANCE_EVENT | SW |
| 813 | INFORMATION | Application container restarted | APPLIANCE_EVENT | SW |
| 814 | INFORMATION | Application recovered | APPLIANCE_EVENT | SW |
| 820 | INFORMATION | Application disabled by user | APPLIANCE_EVENT | SW |
| 821 | INFORMATION | Application enabled by user | APPLIANCE_EVENT | SW |
| 825 | INFORMATION | Firewall service restarted | APPLIANCE_EVENT | SW |
| 832 | INFORMATION | Maintenance mode enabled | APPLIANCE_EVENT | SW |
| 833 | INFORMATION | Maintenance mode disabled | APPLIANCE_EVENT | SW |
| 834 | INFORMATION | Node restart requested due to docker issues | APPLIANCE_EVENT | SW |
| 835 | INFORMATION | Application VM restarted | APPLIANCE_EVENT | SW |
| 837 | INFORMATION | Storage drive disabled by user | APPLIANCE_EVENT | SW |
| 838 | INFORMATION | Storage drive disabled by system | APPLIANCE_EVENT | SW |
| 839 | INFORMATION | Storage drive enabled by user | APPLIANCE_EVENT | SW |
| 840 | INFORMATION | Storage drive enabled by system | APPLIANCE_EVENT | SW |
| 841 | INFORMATION | Node personality changed by user | APPLIANCE_EVENT | SW |
| 842 | INFORMATION | Successfully fixed kernel parameters | APPLIANCE_EVENT | SW |
| 843 | INFORMATION | YDB disk activated | APPLIANCE_EVENT | SW |
| 844 | INFORMATION | YDB disk deactivated | APPLIANCE_EVENT | SW |
| 845 | INFORMATION | YDB node activation requested | APPLIANCE_EVENT | SW |
| 846 | INFORMATION | YDB node deactivation requested | APPLIANCE_EVENT | SW |
| 847 | INFORMATION | YDB node rebalance requested | APPLIANCE_EVENT | SW |
| 848 | INFORMATION | Application initialization has succeeded | APPLIANCE_EVENT | SW |
| 852 | INFORMATION | SEL cleaned successfully | APPLIANCE_EVENT | SW |
| 853 | INFORMATION | Storage drive disabling requested by user | APPLIANCE_EVENT | SW |
| 854 | INFORMATION | Storage drive enabling requested by user | APPLIANCE_EVENT | SW |
| 855 | INFORMATION | Appliance upgrade enabled | APPLIANCE_EVENT | SW |
| 856 | INFORMATION | Appliance upgrade disabled | APPLIANCE_EVENT | SW |
| 857 | WARNING | Application stop action timed out | APPLIANCE_EVENT | SW |
| 865 | WARNING | NPS wen from online to non-online state | APPLIANCE_EVENT | SW |