Filter
Top Products
Propagating the Kerberos Server
Monitoring Propagation
Chapter 9264
[hostname of peer] Can’t connect to subscriber to
propagate principal database information
[hostname of peer] could not get service ticket
[hostname of peer] full_dump failed
[hostname of peer] not enough memory to allocate work buffer
Not enough free system resources to run or start the
propagation system.
Propagation system aborting.
Not enough system resources free to read from propagation
queue
Propagation system aborting.
Out of memory
For more information on resolving the problems, see “Propagation
Failure” on page 269.
Monitoring Propagation Queue Files
The propagation queue file, prop_q, contains the database changes that
occur on the primary security server. The kpropd daemon reads the
prop_q file that lists all principals that have changed since the last
propagation cycle. At the end of a successful propagation cycle, all the
security servers have up-to-date principal databases.
To indicate successful propagation, kpropd creates a zero-length file,
prop_
hostname
_ok, where
hostname
specifies the security server to
which the data is propagated. If the propagation fails, a prop_
hostname
file is created and all the unpropagated changes are saved to the file.
After propagating these changes to the secondary security servers, the
contents of the queue file, prop_
hostname
, are deleted. If the
prop_
hostname
or the prop_
hostname
_ok file exists for a specific host,
kpropd dumps the entire primary database to the secondary security
server without a queue file.
Monitoring Old File Date and Large File Size
In rare cases, a propagation failure or stall may occur without indicating
an error message in the syslog file. Undertake additional monitoring
measures to check for proper functioning of the propagation system. You
can monitor the propagation queue files for unusual characteristics, such
as old file creation date or large file size. Under normal conditions, these
files are created, deleted, and appended many times in a day. For
example, if a prop_q.wrk file exists with a file creation date older than
24 hours from current time, or if the prop_q file size is unusually large,
the propagation cycle may be stalled.