Can't chdir to `path'
the directorypath
could not be created/used. This may be a permission problem. Check the permissions ofpath
ifpath
does actually exist. The problem may be in a path component, not necessarily in the last element of the path.
Can't open `<fname>' to read (or write)
When aGET
orPUT
command fails because the target file could not be read or written, stealth terminates afer logging this message. The file may not exist or you may not not have sufficient permissions to read or write it.
could not open <logname>
This message is generated when the mentioned log-file cannot be written to. Check the permissions of the file, and check if the path to the file exists. The problem may be in a path component, not necessarily in the last element of the path or in the file itself.
Can't read `<run-file>'
The daemon's run-file could not be read. Check if there is indeed a stealth daemon process using this run-filefile exists; if the run-file actually exists (typo in its specification?), and if you have read permissions for it.
Can't send signal <signal-name> to process `<pid>'
The indicated signal (eitherSIGTERM
orSIGUSR1
) could not be sent to the daemon process. Check if a stealth daemon process having process ID<pid>
really exist.
Corrupt line in policy file: ...
The apparently corrupted line is shown. The line is corrupted if the line could not be split into an initial word and its remainder. Normally this should not happen. As the line is mentioned, the message itself should assist you in your repairs.
could not write <run-file name>
The specified run-file could not be written to. Check its permissions and whether it actually exists.
--daemon: missing run-file or policy file
The--daemon
option requires an absolute filename to a run-file, and the call also requires a policy file. Most likely the path to the run-file was not specified, thus confusing the policy file with the run-file. The run-file is often created in the/run
directory.
--daemon <run-file>: must use an absolute file name
The--daemon
option requires a full (absolute) path to the run-file name. Most likely the name of the run-file was not specified, thus confusing the policy file with the skip-file. The run-file is often created in the/run
directory.
Inserting command `...' failed.
the mentioned command could not be sent to a child-process (sh
orssh
). Check the availability of thessh
connection to the client, and whether you have permissions to execute the specified command.
Invalid --random-interval specified
The --random-interval option was given an invalid (too large or negative) argument.
incompatible options: ....
Only one option related to a stealth daemon process can be specified at
a time. E.g., you cannot specify --daemon --rerun --suspend
in one
command. If incompatible options are specified stealth terminates after reporting
which (incompatible) options were received.
--max-size incompatible with IPC calls
The--max-size
option can can only be used when stealth is also receiving a policy file. It cannot be used in combination with the Inter Process Communication (IPC) options--reload, --rerun, --resume, --suspend
or--terminate
.
--max-size <value>: invalid option value
An invalid specification for --max-size
was received. Refer to
the man-page or manual for information about valid options.
No exit value for <cmd> ...
No exit value was received for the logged command, after which stealth terminates.
--<option name> is only valid for a stealth foreground process
The specified option is incompatible with the--daemon
option. Either do not specify--daemon
or omit the offending option.
--random-interval requires --repeat
The--random-interval
option can only be used when the--repeat
option has also been specified.
--run-command 0: not a valid (natural) command number
The --run-command
option requires an argument, which is a
positive, integral value.
--run-command <nr>: invalid command number
The --run-command
option requires an argument, which is a
positive, integral value at most equal to the number of commands listed in the
policy file.
--skip-files incompatible with IPC calls
The--skip-files
option can only be used when stealth is also receiving a policy file. It cannot be used in combination with the Inter Process Communication (IPC) options--reload, --rerun, --resume, --suspend
or--terminate
.
--skip-files: missing skip-file or policy file
The --skip-files
option requires a skip-files absolute filename,
and the call also requires a policy file. Most likely the name of the
skip-file was not specified, thus confusing the policy file with the
skip-file.
--skip-files <filename>: must use an absolute file name
The --skip-files
option requires a full (absolute) path to the
skip-file name. Most likely the name of the skip-file was not specified, thus
confusing the policy file with the skip-file.
Stealth V 3.00.00 terminated
Some pre-3.00.00 options were discontinued starting at stealth version 3.00.00. Two of these options are--suppress
and--keep-alive
. If these options are used, their use is reported and stealth terminates with the above message.
--stdout incompatible with --daemon
The --stdout
option can only be used when stealth is not started as
a daemon process.
syslog facility <facility> not supported
The option--syslog-facility
requires the name of a standard syslog(1) facility. Supported facilities areDAEMON, LOCAL0
throughLOCAL7
andUSER
. See, e.g., the syslog(3) man-page for an overview of their definitions.
--syslog* options incompatible with IPC calls
--syslog*
options can can only be used when stealth is also receiving a policy file. It cannot be used in combination with the Inter Process Communication (IPC) options--reload, --rerun, --resume, --suspend
or--terminate
.
syslog priority <priority> not supported
The option--syslog-priority
requires the name of a standard syslog(1) priority. All standard priorities are supported. See, e.g., the syslog(3) man-page for an overview of available priorities. The prefixes used with the priorities in this man-page (i.e.,LOG_
should not be used when specifying the--syslog-priority
. E.g., use--syslog-priority WARNING
rather than--syslog-priority LOG-WARNING
)
terminated: non-zero exit value for `...'
A local command (not using the CHECK
keyword), returned with a
non-zero exit. This will terminate further processing of the policy
file. Inspect and/or rerun the command `by hand' to find indications about
what went wrong. The report file or the standard error stream may also contain
additional information about the reason of the failure.
Unable to create the logfile `...'
the mentioned log file could not be created. Check the permissions of the file, check if the path to the file exists. The problem may be in a path component, not necessarily in the last element of the path or in the file itself.
USE SSH ... entry missing in the policy file
there is no default for theUSE SSH
specification in the policy file. The specification could not be found. Provide a specification like:USE SSH ssh -q root@localhost