nds sync problem with iPrintManagerDBSaveData
Frank Langner
since one or two weeks I'm experiencing a weired problem in our network:
nds synchronization is ok until at 1:00 AM our iPrint system creates the
daily iPrintManager database backup (into NDS).
After this, I see:
1.) in iMonitor
"Partition Synchronization Status" shows high value for Maximum Ring
Delta. It is equal to the time differenz between now and 1:00 AM (what
for me is proof that the problem starts with the iPrintManager backup).
Also one server shows a -672 error for the iPrintManager object.
The same server shows a high "Receive Delta", whereas all other servers
(including the master replica server and the current iprint server) show
a high "Send Delta".
When I look into the change cache of one of the servers with high send
delta, the enty with the oldest modification time is iPrintManager again
(modified at 1:00 AM). Looking into "entry synchronization" shows that
some properties of the object have been modified, including
iPrintManagerDBSaveData (a stream). I can look into this stream without
a problem.
2.) in ndsrepair
Checking replica synchronization using "ndsrepair -E" infrequently shows
messages that one of the "good" servers can not synchronize the
iPrintManager object with the "bad" server, like this:
Replica: .goodserver.context 05-08-2009 15:05:15
Server: CN=badserver.OU=context.. 05-08-2009 15:05:59 -672 Remote
Object: CN=iPrintManager.OU=context
These errors come and go, but it seems that no changes are synchronized
from the good servers to the bad server anymore.
I've tried to repair the local replica of the bad server, using
"ndsrepair -R". It finds a defective stream file:
Total objects in partition - T=MYTREE : 3774
Repairing objects - done(1000)
Repairing objects - done(2000)
ERROR: Encountered Error: -672 validating stream file for ID: 00008bf5
Object DN: CN=iPrintManager.OU=mycontext, attribute:
iPrintManagerDBSaveData
Repairing objects - done(3000)
Repairing objects - done(3774)
Total Objects = 3774, UNKNOWN class objects = 4, Total Values = 61765
but can not repair it. The same error is shown when I run ndsrepair
again.
So far, the only temporary solution I found, is to reboot the server.
After this, everything is fine again, until the next backup at 1:00 AM
takes place. Even running ndsrepair on the "bad" server is ok and no
defective stream file is reported anymore.
Therefor my question: how can I solve this kind of error? 3 servers are
OES2 (no sp, but no further updates for eDir or iPrint available), one
server is OES1 and one server is Netware 6.5 SP7 (master replica
server).
Thanks in advance! :-)
Frank
David Gersic
> since one or two weeks I'm experiencing a weired problem in our network:
> nds synchronization is ok until at 1:00 AM our iPrint system creates the
> daily iPrintManager database backup (into NDS).
So what happens if you stop iPrint from doing this? Does it get better?
--
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Knowledge Partner http://forums.novell.com
Please post questions in the newsgroups. No support provided via email.
Frank Langner
> > nds synchronization is ok until at 1:00 AM our iPrint system creates the
> > daily iPrintManager database backup (into NDS).
>
> So what happens if you stop iPrint from doing this? Does it get better?
I've tried to find any information how to disable the backup into NDS,
but with no success. At least I could not find it at the documentation,
TIDs, iManager etc. Do you know you to disable it?
Frank
David Gersic
>> > since one or two weeks I'm experiencing a weired problem in our
>> > network: nds synchronization is ok until at 1:00 AM our iPrint system
>> > creates the daily iPrintManager database backup (into NDS).
>>
>> So what happens if you stop iPrint from doing this? Does it get better?
>
> I've tried to find any information how to disable the backup into NDS,
> but with no success.
Hm. Ok, so being that I'm _not_ an iPrint expert, I found this in TID
#10095107:
The NDPS Manager will make a backup of its database
at 1:00 AM. By default, a copy will be stored on the
file system, and a copy will be pushed up to eDirectory
as a streams file. eDirectory will then replicate the
change in the streams file to all of the servers in the
replica ring. If you disable the backup to NDS option,
your NDPS Manager's database will not be backed up any
more to eDirectory.
which seems to indicate that it can be done. Searching the documentation,
I found:
7.1.1 Understanding the Print Manager Database
Modifying the Database Backup Options
1. At the server console, go to the Available Options
menu for the Print Manager.
2. Select Print Manager Status and Control > Database Options.
3. Modify the desired settings.
4. Use Escape to return to the Available Options menu.
Frank Langner
> I found:
>
> 7.1.1 Understanding the Print Manager Database
>
> Modifying the Database Backup Options
>
> 1. At the server console, go to the Available Options
> menu for the Print Manager.
>
> 2. Select Print Manager Status and Control > Database Options.
>
> 3. Modify the desired settings.
>
> 4. Use Escape to return to the Available Options menu.
Yes, but this is for netware based iPrint, I'm running on OES2 Linux. On
Linux I don't have any GUI for the iprint manager and the same section
in the documentation for iprint-lx does not tell anything on how to
disable the backup.
I also look at imanager and iprint health and could not find a switch.
Neither inside the conf-files of iprint. Maybe I missed something, but
at the moment I can not see how to disable the backup...
Frank
David Gersic
> Yes, but this is for netware based iPrint, I'm running on OES2 Linux. On
> Linux I don't have any GUI for the iprint manager and the same section
> in the documentation for iprint-lx does not tell anything on how to
> disable the backup.
Hm. Ok, good question then. I don't know how to do that either. Let me
ask about this and see what I can find out.
Frank Langner
> ask about this and see what I can find out.
Thank you. At the moment it seems that I have found the origin of the
problem: McAfee LinuxShield 1.5.1. I've disabled the scanner two days
ago and since this time the iprint backup worked without a problem. I
will wait until Monday to re-activate the scanner again, to check
whether the problem will reappear. If so, I will search at this place.
It's a bit surprising, because the scanner is running since some months,
without such problems.
But nether less it would be interesting to know, how the iprint backup
(to nds) can be disabled temporarily.
Frank
David Gersic
>> Hm. Ok, good question then. I don't know how to do that either. Let me
>> ask about this and see what I can find out.
>
> Thank you. At the moment it seems that I have found the origin of the
> problem: McAfee LinuxShield 1.5.1. I've disabled the scanner two days
> ago and since this time the iprint backup worked without a problem. I
Weird, but ok, thanks for the followup.
> But nether less it would be interesting to know, how the iprint backup
> (to nds) can be disabled temporarily.
Don't know, yet. I've asked backline support, but the question hasn't yet
been answered.
Frank Langner
> been answered.
Did you get any answer from support?
Frank
David Gersic
Sorry, yes. It doesn't seem to be possible.
jiten
> On Fri, 29 May 2009 13:10:46 +0000, Frank Langner wrote:
>
>>> Don't know, yet. I've asked backline support, but the question hasn't
>>> yet been answered.
>> Did you get any answer from support?
>
> Sorry, yes. It doesn't seem to be possible.
>
>
Yes currently there is no way you can disable the backup of iPrint
database to nds. iPrintManager does a periodic back of its database to
nds. And it depends on if there is big delta created by iPrintManager
(in case you have added additional printers or kept auditing on for
printer etc.). The problem seems to be genuine but if eDirectory replica
are not syncronized you ll land up in lot of trouble. It would be good
if you raise an SR with NTS and have some body from eDirectory NTS to
look into your setup.
Thanks
Jiten
jiten
Well you can defrag the database (which ll reduce the size of the
database)from
httpa://<dns>/PsmStatus/Misc -> Defrag Database.
This will reduce the size of the deltas. Please let me know if this was
of any help to you.
Thanks
Jiten