HP-UX Host Intrusion Detection System Version 4.3 administrator guide
Table Of Contents
- HP-UX Host Intrusion Detection System Version 4.3 administrator guide
- Table of Contents
- About This Document
- 1 Introduction
- 2 Configuring HP-UX HIDS
- 3 Getting Started with HP-UX HIDS
- 4 Using the System Manager Screen
- Starting the HP-UX HIDS System Manager
- Stopping the HP-UX HIDS System Manager
- System Manager Components
- Starting HP-UX HIDS Agents
- Getting the Status of Agent Hosts
- Resynchronizing Agent Hosts
- Activating Schedules on Agent Hosts
- Stopping Schedules on Agent Hosts
- Halting HP-UX HIDS Agents
- Accessing Other Screens
- 5 Using the Schedule Manager Screen
- The Schedule Manager
- Configuring Surveillance Schedules
- Configuring Surveillance Groups
- Configuring Detection Templates
- Setting Surveillance Schedule Timetables
- Configuring Alert Aggregation
- Configuring Monitor Failed Attempts
- Configuring Duplicate Alert Suppression
- Viewing Surveillance Schedule Details
- Predefined Surveillance Schedules and Groups
- 6 Using the Host Manager Screen
- 7 Using the Network Node Screen
- 8 Using the Preferences Screen
- A Templates and Alerts
- Alert Summary
- UNIX Regular Expressions
- Limitations
- Template Property Types
- Buffer Overflow Template
- Race Condition Template
- Modification of files/directories Template
- Changes to Log File Template
- Creation and Modification of setuid/setgid File Template
- Creation of World-Writable File Template
- Modification of Another User’s File Template
- Login/Logout Template
- Repeated Failed Logins Template
- Repeated Failed su Commands Template
- Log File Monitoring Template
- B Automated Response for Alerts
- C Tuning Schedules and Generating Alert Reports
- D The Agent Configuration File
- E The Surveillance Schedule Text File
- F Error Messages
- G Troubleshooting
- Troubleshooting
- Agent and System Manager cannot communicate with each other
- Agent complains that idds has not been enabled, yet lsdev shows /dev/idds is present
- Agent does not start on system boot
- Agent halts abnormally, leaving ids_* files and message queues
- Agent host appears to hang and/or you see message disk full
- Agent needs further troubleshooting
- Agent does not start after installation
- Agents appear to be stuck in polling status
- Agent displays error if hostname to IP mapping is not registered in name service
- Aggregated alerts targets or details field are truncated and the same aggregated alert has several entries logged in the IDS_ALERTFILE
- Alert date/time sort seems inconsistent
- Alerts are not being displayed in the alert browser
- Buffer overflow triggers false positives
- Duplicate alerts appear in System Manager
- Getting several aggregated alerts for the same process
- GUI runs out of memory after receiving around 19,000 alerts
- The idsadmin Command needs installed agent certificates
- The idsadmin Command notifies of bad certificate when pinging a remote agent
- IDS_checkInstall fails with a kmtune error
- IDS_genAdminKeys or IDS_genAgentCerts does not complete successfully
- IDS_genAdminKeys or idsgui quits early
- Large files in /var/opt/ids
- Log files are filling up
- No Agent Available
- Normal operation of an application generates heavy volume of alerts
- Reflection X rlogin produces multiple login and logout alerts
- Schedule Manager timetable screen appears to hang
- SSH does not perform a clean exit after idsagent is started
- System Manager appears to hang
- System Manager does not let you save files to specific directories
- System Manager does not start after idsgui is started
- System Manager starts with no borders or title bar in X client programs on Windows
- System Manager times out on agent functions such as Activate and Status Poll
- UNKNOWN program and arguments in certain alert messages
- Using HP-UX HIDS with IPFilter and SecureShell
- Unable to Generate Administrator Keys and Agent Certificates on PA–RISC 1.1 Systems
- Troubleshooting
- H HP Software License

F Error Messages
This appendix describes errors and messages that may be produced by the Agent and System
Manager programs. This appendix addresses the following topics:
• “Agent Messages” (page 203)
• “System Manager Messages” (page 207)
Agent Messages
This section describes error messages that are displayed on agent systems.
NOTE: These messages are produced by agent processes. If you see a message that is not
described and you cannot resolve the problem, contact HP support.
Table F-1 Agent Error Messages
ActionMeaningError Message
See if the agent is already running
(ps -ef grep idsagent). If it is,
and you need to restart it, see
“Halting HP-UX HIDS Agents”
(page 54) and “Starting HP-UX
HIDS Agents” (page 51). If the agent
is not running, delete the lock file
and restart the agent.
You attempted to start idsagent and it is
already running. Or idsagent halted
abnormally, leaving the lock file in place.
idsagent: another idsagent
(PID:pid) process is running. Or a
stale lockfile
/var/opt/ids/idsagent.pid exists.
Remove it and attempt to restart -
exiting
Switch to user ids.
You are currently logged in as superuser
(root). For security reasons, HP-UX HIDS
programs cannot be run as superuser.
idsagent: agent processes must
NOT be run as root - exiting
This error often occurs if the IDDS
driver in the kernel is not configured
correctly. Run the
IDS_checkInstall script, contact
HP support.
The idsagent encountered an
unexpected error, it halted the currently
active surveillance schedule.
idsagent: a critical error occurred
on the agent; halting schedule
execution
The idsagent refuses to open the
configuration file if it is not owned
by user:group ids:ids, is not
readable by user ids, or is
world-writable.
Security checks on the configuration file
cfile failed.
idsagent: access checking on
configuration file cfile failed
Check that the directory exists, that
it is owned by user:group ids:ids;
that it has 700 permissions, and that
the /var partition has free space
available.
The idsagent failed to create the /var/
opt/ids/alert.log local alert log file.
idsagent: alert log creation failed
Ensure that dir exists, that it is
owned by user:group ids:ids, and
that it is readable and executable by
user ids.
The idsagent failed to change its current
working directory to dir
idsagent: cannot access its base
directory: dir
Verify that the file exists; that it is
owned by user:group ids:ids; and
that it is readable by user ids.
The idsagent cannot open the
configuration file cfile.
idsagent: cannot open
configuration file cfile
Check accompanying error messages
and correct the problem.
An error occurred while parsing the
ids.cf configuration file. The SSL
certificates may not have been created
properly, meaning that the REMOTEHOST
parameter may not be valid in ids.cf.
idsagent: failed to initialize
configuration module
Agent Messages 203