Appliance software alerts
This topic presents a list of default software related issues and events for IBM® Integrated Analytics System.
Software related issues
Issues are stateful alerts, they are ongoing until the problem is fixed.
| Group | Type | Reason Code | Title | Severity |
|---|---|---|---|---|
| SW | SW_SERVICE_REQUESTED | 151 | Cannot activate tuned.service | MAJOR |
| SW | SW_SERVICE_REQUESTED | 154 | Soft power off action for node failed, could not recover node | MAJOR |
| SW | SW_SERVICE_REQUESTED | 155 | RAID5 array needs attention | WARNING |
| SW | SW_SERVICE_REQUESTED | 156 | Mounts count exceeds threshold | WARNING, MAJOR |
| SW | SW_SERVICE_REQUESTED | 198 | Test SW alert | INFORMATION |
| SW | HW_NEEDS_ATTENTION | 205 | Low fibre channel path count | MAJOR |
| SW | HW_NEEDS_ATTENTION | 207 | SEL is full and cannot be cleaned | MINOR |
| SW | DB_SERVICE_REQUESTED | 251 | Invalid log path | INFORMATION, WARNING, MAJOR |
| SW | DB_NEEDS_ATTENTION | 351 | Database availability issue | INFORMATION, WARNING, MAJOR |
| SW | DB_NEEDS_ATTENTION | 352 | Physical memory usage threshold exceeded | INFORMATION, WARNING, MAJOR |
| SW | DB_NEEDS_ATTENTION | 353 | Virtual memory usage threshold exceeded | INFORMATION, WARNING, MAJOR |
| SW | DB_NEEDS_ATTENTION | 354 | File system utilization threshold exceeded | INFORMATION, WARNING, MAJOR |
| SW | DB_NEEDS_ATTENTION | 355 | Maximum log space exceeded | INFORMATION, WARNING, MAJOR |
| SW | DB_NEEDS_ATTENTION | 356 | Table space container utilization threshold exceeded | INFORMATION, WARNING, MAJOR |
| SW | DB_NEEDS_ATTENTION | 357 | Statement performance issue | INFORMATION, WARNING, MAJOR |
| SW | DB_NEEDS_ATTENTION | 399 | Other database issue | INFORMATION, WARNING, MAJOR |
| SW | SW_NEEDS_ATTENTION | 401 | GPFS node failed to start | MAJOR |
| SW | SW_NEEDS_ATTENTION | 402 | GPFS nsd failed to start | MINOR |
| SW | SW_NEEDS_ATTENTION | 403 | Application container cannot be started on a node | MAJOR |
| SW | SW_NEEDS_ATTENTION | 404 | GPFS local partition failed to be mounted | MAJOR, CRITICAL |
| SW | SW_NEEDS_ATTENTION | 405 | GPFS filesystem failed to be mounted | MAJOR, CRITICAL |
| SW | SW_NEEDS_ATTENTION | 406 | NTP Daemon not sync on external | WARNING |
| SW | SW_NEEDS_ATTENTION | 407 | Application component is not healthy | CRITICAL, MAJOR |
| SW | SW_NEEDS_ATTENTION | 408 | NTP Daemon is down | WARNING |
| SW | SW_NEEDS_ATTENTION | 409 | Unable to start Call Home Daemon | MAJOR |
| SW | SW_NEEDS_ATTENTION | 410 | Unable to stop Call Home Daemon | MINOR |
| SW | SW_NEEDS_ATTENTION | 411 | Heavy swap usage | CRITICAL |
| SW | SW_NEEDS_ATTENTION | 412 | Node time not in sync | MAJOR |
| SW | SW_NEEDS_ATTENTION | 413 | Directory service cannot be started | MAJOR |
| SW | SW_NEEDS_ATTENTION | 414 | Security daemon cannot be started | MAJOR |
| SW | SW_NEEDS_ATTENTION | 415 | Docker service failed | MAJOR |
| SW | SW_NEEDS_ATTENTION | 416 | Unable to start WebConsole container | MAJOR |
| SW | SW_NEEDS_ATTENTION | 417 | Unable to stop WebConsole container | MAJOR |
| SW | SW_NEEDS_ATTENTION | 418 | WebConsole is down | MAJOR |
| SW | SW_NEEDS_ATTENTION | 419 | Grow on demand limit not satisfied | CRITICAL |
| SW | SW_NEEDS_ATTENTION | 421 | Unable to start Lift container | MAJOR |
| SW | SW_NEEDS_ATTENTION | 422 | Unable to stop Lift container | MAJOR |
| SW | SW_NEEDS_ATTENTION | 423 | Lift down | MAJOR |
| SW | SW_NEEDS_ATTENTION | 424 | Token and auth service cannot be started | MAJOR |
| SW | SW_NEEDS_ATTENTION | 425 | DR management service cannot be started | MAJOR |
| SW | SW_NEEDS_ATTENTION | 426 | Firewall service cannot be started | MAJOR |
| SW | SW_NEEDS_ATTENTION | 427 | Unable to start IDAA Gateway container | MAJOR |
| SW | SW_NEEDS_ATTENTION | 428 | Unable to stop IDAA Gateway container | MAJOR |
| SW | SW_NEEDS_ATTENTION | 429 | IDAA Gateway down | MAJOR |
| SW | SW_NEEDS_ATTENTION | 432 | Application VMs cannot be started on a node | |
| SW | SW_NEEDS_ATTENTION | 433 | Primary SKLM proxy service cannot be started | MAJOR |
| SW | SW_NEEDS_ATTENTION | 434 | Secondary SKLM proxy service cannot be started | MAJOR |
| SW | SW_NEEDS_ATTENTION | 435 | Gateway not in routing table | WARNING |
| SW | SW_NEEDS_ATTENTION | 436 | Failed to collect status from resource manager | MAJOR |
| SW | SW_NEEDS_ATTENTION | 437 | Duplicate containers running | MAJOR |
| SW | SW_NEEDS_ATTENTION | 438 | Service cannot be (re)started | MAJOR |
| SW | SW_NEEDS_ATTENTION | 439 | Openshift node is not ready | |
| SW | SW_NEEDS_ATTENTION | 440 | Openshift service is not ready | |
| SW | SW_NEEDS_ATTENTION | 441 | Incorrect node kernel params | |
| SW | SW_NEEDS_ATTENTION | 442 | Timezones mismatch between nodes | WARNING |
| SW | SW_NEEDS_ATTENTION | 443 | Cannot mount NFS partition on virtual machine | |
| SW | SW_NEEDS_ATTENTION | 444 | Unable to start VDB container | |
| SW | SW_NEEDS_ATTENTION | 445 | Unable to stop VDB container | |
| SW | SW_NEEDS_ATTENTION | 446 | ICP4D service is not ready | |
| SW | SW_NEEDS_ATTENTION | 447 | GlusterFS component is not healthy | MAJOR |
| SW | SW_NEEDS_ATTENTION | 448 | NFS partition requires container restart | WARNING |
| SW | SW_NEEDS_ATTENTION | 449 | NFS server does not respond | WARNING |
| SW | SW_NEEDS_ATTENTION | 450 | NFS partition cannot be mounted properly | WARNING |
| SW | SW_NEEDS_ATTENTION | 451 | Webconsole service is not ready | WARNING |
| SW | SW_NEEDS_ATTENTION | 452 | NFS partition cannot be exported | WARNING |
| SW | SW_NEEDS_ATTENTION | 453 | Unreacheable or missing device for NSD | WARNING |
| SW | SW_NEEDS_ATTENTION | 454 | Failed to restart a process with high number of mounts | MAJOR |
| SW | SW_NEEDS_ATTENTION | 455 | Failed to cordon a node | |
| SW | SW_NEEDS_ATTENTION | 456 | Failed to uncordon a node | |
| SW | SW_NEEDS_ATTENTION | 457 | GPFS node is not CCR-based | |
| SW | FLOATING_IP_ISSUE | 601 | Unable to bring-up floating IP | MAJOR |
| SW | FLOATING_IP_ISSUE | 602 | Unable to bring-down floating IP | MAJOR |
| SW | FLOATING_IP_ISSUE | 603 | Unable to bring-up floating IP - cannot connect to server | MAJOR |
| SW | FLOATING_IP_ISSUE | 604 | Unable to bring-down floating IP - cannot connect to server | MAJOR |
| SW | VM_FLOATING_IP_ISSUE | 605 | Unable to bring-up floating IP | |
| SW | VM_FLOATING_IP_ISSUE | 606 | Unable to bring-down floating IP | |
| SW | APPLIANCE_APPLICATION_DOWN | 701 | Appliance application went down due to disabled node | CRITICAL |
| SW | APPLIANCE_APPLICATION_DOWN | 703 | Appliance application can't start | CRITICAL |
| SW | APPLIANCE_APPLICATION_DOWN | 704 | Appliance application went down | CRITICAL |
| SW | STORAGE_UTILIZATION | 901 | Storage utilization above threshold | CRITICAL |
| SW | STORAGE_UTILIZATION | 902 | Present snapshots reduce available storage | WARNING |
Software events
Events are stateless alerts, that is, they are related to a point-in-time event.| Group | Type | Reason Code | Title | Severity |
|---|---|---|---|---|
| SW | SW_SERVICE_REQUESTED | 152 | FODC dump collected | INFORMATION |
| SW | SW_SERVICE_REQUESTED | 153 | Kernel panic(s) occurred | WARNING |
| SW | ACTION_FAILED | 301 | Action to restore a GPFS component failed | WARNING |
| SW | ACTION_FAILED | 302 | Container start-up action failed | MAJOR |
| SW | ACTION_FAILED | 303 | Container stop action failed | MINOR |
| SW | ACTION_FAILED | 304 | Action to restore NTP synchronization failed | WARNING |
| SW | ACTION_FAILED | 305 | Failed to enable a node | WARNING |
| SW | ACTION_FAILED | 306 | NTP cannot sync with external | MINOR |
| SW | ACTION_FAILED | 307 | Application disabling failed | MAJOR |
| SW | ACTION_FAILED | 308 | Application enabling failed | MAJOR |
| SW | ACTION_FAILED | 309 | WebConsole container stop action failed | MAJOR |
| SW | ACTION_FAILED | 310 | VM start-up action failed | |
| SW | ACTION_FAILED | 311 | VM stop action failed | |
| SW | ACTION_FAILED | 312 | Failed to enable a storage drive | |
| SW | ACTION_FAILED | 313 | Failed to disable a storage drive | |
| SW | ACTION_FAILED | 314 | Soft power off failed for node | WARNING |
| SW | ACTION_FAILED | 315 | Failed to set node personality | |
| SW | ACTION_FAILED | 316 | Failed to mount external NFS partition | WARNING |
| SW | ACTION_FAILED | 317 | Application initialization has failed | MAJOR |
| SW | ACTION_FAILED | 318 | Failed to reduce process's mounts number | MAJOR |
| SW | ACTION_FAILED | 319 | Failed to disable a node | |
| SW | SW_NEEDS_ATTENTION | 420 | Detection of change GoD | MINOR |
| SW | SW_NEEDS_ATTENTION | 458 | Node was disabled but vm did not reported shutdown | |
| SW | STARTUP_FAILED | 501 | Start-up failed due to container start error | CRITICAL |
| SW | STARTUP_FAILED | 502 | Application start-up timeout | CRITICAL |
| SW | STARTUP_FAILED | 503 | Start-up timeout on waiting for healthy nodes | CRITICAL |
| SW | STARTUP_FAILED | 504 | Start-up failed (db2 HA failed) | CRITICAL |
| SW | STARTUP_FAILED | 505 | Application start-up aborted due to FSN thermal issues | CRITICAL |
| SW | STARTUP_FAILED | 506 | Application start-up aborted due to VM stop error | |
| SW | APPLIANCE_APPLICATION_DOWN | 702 | Appliance application went down due to FSN thermal issues | CRITICAL |
| SW | APPLIANCE_EVENT | 801 | Node disabled by user | INFORMATION |
| SW | APPLIANCE_EVENT | 802 | Node disabled by system | INFORMATION |
| SW | APPLIANCE_EVENT | 803 | Node enabled by user | INFORMATION |
| SW | APPLIANCE_EVENT | 804 | Node enabled by system | INFORMATION |
| SW | APPLIANCE_EVENT | 805 | Node rebalance requested | INFORMATION |
| SW | APPLIANCE_EVENT | 806 | Node init requested | INFORMATION |
| SW | APPLIANCE_EVENT | 807 | Application start requested | INFORMATION |
| SW | APPLIANCE_EVENT | 808 | Application stop requested | INFORMATION |
| SW | APPLIANCE_EVENT | 809 | Unreachable node restart requested | INFORMATION |
| SW | APPLIANCE_EVENT | 810 | Docker service restarted | INFORMATION |
| SW | APPLIANCE_EVENT | 811 | NTPD service recovered | INFORMATION |
| SW | APPLIANCE_EVENT | 812 | GPFS issue recovered | INFORMATION |
| SW | APPLIANCE_EVENT | 813 | Application container restarted | INFORMATION |
| SW | APPLIANCE_EVENT | 814 | Application recovered | INFORMATION |
| SW | APPLIANCE_EVENT | 815 | FC port retrained | INFORMATION |
| SW | APPLIANCE_EVENT | 816 | Directory service restarted | INFORMATION |
| SW | APPLIANCE_EVENT | 817 | Security daemon restarted | INFORMATION |
| SW | APPLIANCE_EVENT | 818 | Node time synchronized | INFORMATION |
| SW | APPLIANCE_EVENT | 819 | WebConsole container restarted | INFORMATION |
| SW | APPLIANCE_EVENT | 820 | Application disabled by user | INFORMATION |
| SW | APPLIANCE_EVENT | 821 | Application enabled by user | INFORMATION |
| SW | APPLIANCE_EVENT | 822 | CPU clock tuned successfully | INFORMATION |
| SW | APPLIANCE_EVENT | 823 | Successfully activated tuned.service | INFORMATION |
| SW | APPLIANCE_EVENT | 824 | Lift container restarted | INFORMATION |
| SW | APPLIANCE_EVENT | 825 | Firewall service restarted | INFORMATION |
| SW | APPLIANCE_EVENT | 826 | Application container(s) restart requested by db2 HA | INFORMATION |
| SW | APPLIANCE_EVENT | 827 | Node suspended | INFORMATION |
| SW | APPLIANCE_EVENT | 828 | Node resumed | INFORMATION |
| SW | APPLIANCE_EVENT | 829 | Node is ready to be resumed | INFORMATION |
| SW | APPLIANCE_EVENT | 830 | CPU configuration updated | INFORMATION |
| SW | APPLIANCE_EVENT | 831 | Db2 crash recovery in progress | INFORMATION |
| SW | APPLIANCE_EVENT | 832 | Maintenance mode enabled | INFORMATION |
| SW | APPLIANCE_EVENT | 833 | Maintenance mode disabled | INFORMATION |
| SW | APPLIANCE_EVENT | 834 | Node restart requested due to docker issues | INFORMATION |
| SW | APPLIANCE_EVENT | 835 | Application VM restarted | |
| SW | APPLIANCE_EVENT | 836 | Application container(s) restart requested by user | INFORMATION |
| SW | APPLIANCE_EVENT | 837 | Storage drive disabled by user | |
| SW | APPLIANCE_EVENT | 838 | Storage drive disabled by system | |
| SW | APPLIANCE_EVENT | 839 | Storage drive enabled by user | |
| SW | APPLIANCE_EVENT | 840 | Storage drive enabled by system | |
| SW | APPLIANCE_EVENT | 841 | Node personality changed by user | |
| SW | APPLIANCE_EVENT | 842 | Successfully fixed kernel parameters | |
| SW | APPLIANCE_EVENT | 843 | YDB disk activated | |
| SW | APPLIANCE_EVENT | 844 | YDB disk deactivated | |
| SW | APPLIANCE_EVENT | 845 | YDB node activation requested | |
| SW | APPLIANCE_EVENT | 846 | YDB node deactivation requested | |
| SW | APPLIANCE_EVENT | 847 | YDB node rebalance requested | |
| SW | APPLIANCE_EVENT | 848 | Application initialization has succeeded | INFORMATION |
| SW | APPLIANCE_EVENT | 852 | SEL cleaned successfully | |
| SW | APPLIANCE_EVENT | 853 | Storage drive disabling requested by user | INFORMATION |
| SW | APPLIANCE_EVENT | 854 | Storage drive enabling requested by user | INFORMATION |
| SW | APPLIANCE_EVENT | 855 | Appliance upgrade enabled | |
| SW | APPLIANCE_EVENT | 856 | Appliance upgrade disabled | |
| SW | APPLIANCE_EVENT | 857 | Application stop action timed out |