The following list describes the error messages produced by S-TAP, in alphabetical sequence. Items shown in italicized text are variable. The messages are shaded, and the description is shown on a clear background.
Cant read inifile .../guard_tap.ini: Cannot resolve hostname xxx for the IP address parameter sqlguard_ip in section SQLGUARD_x. Reverting to .../guard_tap.ini.bak
The S-TAP configuration file (guard_tap.ini) has errors, which is most likely to happen when it has been edited manually. When this happens, S-TAP attempts to restart from the last known good backup file (if one is available).
bind: Address already in use [DB
server name or IP]
Cant bind listening socket for tee: Address already in use
A port that an S-TAP TEE is trying to use is already in use. For example, if you configure a TEE to listen on port 4100, and Sybase is already listening on that port, you will receive this message. This message is issued only when the S-TAP TEE process is starting.
connect: Network is unreachable
The standard message received when trying to reach a host that is not accessible. In 99% of the cases this means that the Guardium appliance down (is not answering ping requests).
Delayed server connection error: Connection refused
The Guardium appliance is refusing a connection request from this S-TAP. That Guardium appliance either has no inspection engine running (not likely), or it is not configured to accept S-TAP connections (check the unit_type setting for that Guardium unit).
Deleting connection on unknown pid:n
Not an error message; please disregard.
Got a connection from a remote machine, ignoring
S-TAP has received a connection request (to a TEE port) from an application at a remote host, and is ignoring that request. The Tee should only used for local connections.
Got new configuration
The Guardium administrator has updated the configuration while logged into the Guardium appliance, and the updated configuration file has been received by the S-TAP.
Guard Tee is accepting connections on port 12346
Normal TEE process start-up message (appears only when the TEE is installed).
Guardium TAP starting
Normal S-TAP process start-up message.
read from socket: Connection reset by peer
The database server or database client is down. For example, someone ran an Oracle sqlplus session and used ctrl-C to exit. This message does not indicate a problem.
Server wasn’t heard from for 180 sec, closing and re-opening
S-TAP has not received a heartbeat signal from the Guardium appliance for 180 seconds. It will attempt to reconnect with the server. No data is lost since it is cached in the buffer file .
SQLguard socket read: Connection reset by peer
The Guardium appliance closed the connection to the S-TAP. This happens when the Guardium appliance restarts, or when the Guardium appliance inspection engine automatically goes down and comes up again (in which case, it does not indicate a problem).
waitpid: No child processes
Not an error message; please disregard.
killed n
The S-TAP hunter process has killed an unauthorized connection identified by n.