<P>Hi all,
<P>I sent out an email a few weeks ago in regards to the database propagation eating up the disk space in the slave kdc (please see the email below for details). I tried the latest 1.2.7 Kerberos binaries, but the problem still exists. After some debugging and tracing, I realized that the kpropd process actually calls "kdb5_util load" The load function is implemented in the "dump.c" file under the src/kadmin/dbutil directory. So, after some more debugging with the "load_db" function, I believe the problem lies with the "krb5_db_rename()" function on ~line 2366. I'm not familiar with the code base, so I don't understand what this function is doing. All I know is that it causes the disk space to go up by about 4K bytes for every 2-3 kdb5_util loads. This causes a problem with our systems because after so many propagations, the slave kdc's disk space fills up and crashes. Does anyone have any clues about this issue? !
; Is there a website that I can report this bug?
<P>Thanks,<BR>Monica
<P>
<P> <B><I>Monica Lau <mllau2002@yahoo.com></I></B> wrote:
<BLOCKQUOTE style="BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px">
<P>Hi all,</P>
<P>I have a master kdc and a slave kdc. In the master kdc, I run a script that executes kprop to propagate the database to the slave every 2 seconds (for testing purposes). On the slave kdc, I run the "df" command periodically. I noticed that the disk space percentage usage climbs up slowly. Eventually, it goes up to 100%, and my slave machine crashes. I don't understand how/why kprop could cause the disk space in the slave machine to go up because the master database is always the same size. If I stop the propagation, the disk space in the slave doesn't go down, until I reboot the machine. </P>
<P>This is sample output from the "df" command:</P>
<P>Filesystem 1k-blocks Used Available Use% Mounted on<BR>/dev/mtdblock3 14976 13436 1540 90% /</P>
<P>This is sample output from the "mount" command:</P>
<P>/dev/mtdblock3 on / type jffs2 (rw)<BR>/proc on /proc type proc (rw)<BR>none on /dev/pts type devpts (rw)<BR>/dev/ram1 on /tmp type ramfs (rw)<BR>/dev/ram2 on /var type ramfs (rw)</P>
<P>Perhaps, this is a different problem that doesn't have anything to do with kprop, but I only see this happening when I run the kprop script. Does anyone have any clues about this strange problem? I'm not familiar with how the kprop process works. If someone can give me a general overview of the process that occurs when the master database is propagated to the slave kdc, that would be tremenously helpful. Thanks for your time and help.</P>
<P>Monica</P>
<P><BR>
<HR SIZE=1>
Do you Yahoo!?<BR><A href="http://webhosting.yahoo.com/ps/wh3/prod/">Yahoo! Web Hosting</A> - establish your business online</BLOCKQUOTE><p><br><hr size=1>Do you Yahoo!?<br>
<a href="http://rd.yahoo.com/platinum/evt=8162/*http://platinum.yahoo.com/splash.html">Yahoo! Platinum</a> - Watch CBS' NCAA March Madness, <a href="http://rd.yahoo.com/platinum/evt=8162/*http://platinum.yahoo.com/splash.html">live on your desktop</a>!