Re: Problems with iprop

[Dr A V Le Blanc <LeBlanc@mcc.ac.uk>]

On Thu, Jul 26, 2007 at 02:39:47PM -0500, Love Hörnquist Åstrand wrote:
> I'm sorry iprop is in such sorry state. I going to look it over in  
> the next few months, and would be very happy if there was ways I can  
> reproduce the problems you are seeing that.
> 
> If you can't, I've got to start to run in on a large production realm  
> close to me and see if that reproduce the problems for me.

Yesterday I followed Henry Hotz's advice and stopped the master,
zeroed the log, stopped the clients, zeroed the log, and copied
the database across to be sure it was the same.  This morning already
one slave server had over 87000 kadm5_log_replay error messages in
an hour and a half, and full disks on the slave servers.  I moved
back to the Debian 0.7.2.dfsg.1-10, but it does not seem to have
helped.  Should I try dumping the master database and reloading
it from the dump?  Or should I just give up on iprop for the
time being?

Incidentally, Henry Hotz mentioned the truncate_log and iprop-log
commands for the 0.7 and 0.8 servers respectively.  I do have the
truncate_log command in 0.7, but there's no man page, and it's
not in the info file.  Are there any guidelines for using it?

     -- Owen