System Administrator Guide > System Administrator Guide > Troubleshooting Ingres > Troubleshoot Startup, Shutdown, or Configuration Problems > Detect Ingres Startup Problems on System Reboot (UNIX)
Was this helpful?
Detect Ingres Startup Problems on System Reboot (UNIX)
To detect Ingres startup problems on system reboot on UNIX, follow these steps:
1. The most common cause of startup failure following a reboot is failure to include the startup command ingstart in the boot script for your machine. (The boot file is vendor-specific but can be named “/etc/rc” or “etc/rc.local”.) This file contains the commands that are to be executed immediately after a reboot.
Make sure that the following line appears in the boot script:
su userid -c "ii_system/ingres/utility/ingstart ii_system" /dev/console
where:
userid refers to the user that owns the installation
ii_system refers to the value of II_SYSTEM for your installation.
2. Make sure that /dev/kmem is readable to the user that owns the installation. If this is a security problem for your machine, you can add this user as a member of /dev/kmem’s group and make the /dev/kmem group readable.
Issue the following command at the operating system prompt:
chmod g+w /dev/kmem
The user that owns the installation must be able to read /dev/kmem or the kernel resource checks in ingstart fails.
3. Run ingstart. If the installation still does not start, contact technical support, as described in What You Need Before Contacting Actian Support.
Last modified date: 01/30/2023