Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
2043 views

after automate switch to winter time - have 23 Errors (DS)

NW65SP8 (Server with Master Repl)
Automate was changed time (to winter-time)..
All ok, but dsreapire -a discovery 23 Errors:
Example:
/****************************************************************************/

NetWare 1602.00 Directory Services Repair 20503.09, DS 20503.15

Log file for server ".GRAD.dntsk.ami" in tree "AMI"

Repairing Local Database

Start: Sunday, 30 October 2011 8:58:03 Local Time



** All disk amounts are approximations **

Disk space currently available: 11836 MB

->DSRepair may need to use: 297 MB

->Disk space remaining after operation: 11836 MB



Current transaction ID is 0x17278F01. Allowed limit of transaction is 0xFFFFE000
Physical Check

Repair Trees - Scan Values

Repair Trees - Sorting Values

Repair Trees - Scan Entries

Repair Trees - Sorting Entries

Repair Trees - Check Values

Repair Trees - Check Entries

Total Objects in Database: 8231

Total Objects in Schema : 3880

Total External References: 1

Total Objects in Replicas: 4338

Schema Check


Repairing objects in a replica

Start: Sunday, 30 October 2011 8:58:15 Local Time

[1 of 2] Master : T=AMI
Total objects in partition - T=AMI : 4216


ERROR: Modification time was incorrect, it has been updated

Object ID: 0000AE8B, DN: OU=gwercog.OU=gwkujb.OU=dntsk.O=ami.T=AMI





ERROR: Modification time was incorrect, it has been updated

Object ID: 0000AF67, DN: CN=Http Server - ercog.OU=gwercog.OU=gwkujb.OU=dntsk.O=ami.T=AMI



........
Total Objects = 1, UNKNOWN class objects = 0, Total Values = 128

Total partition and object events rejected during repair = 10

Total partition and object events rejected during repair = 10

Finish: Sunday, 30 October 2011 8:58:22 Local Time

Total repair time: 0:00:19

Checking mail directories

Checking stream syntax files

Repair process completed, total errors found = 23

( ERCOG - OES2 Server )

How i can reapir this errors ?

Serg
Labels (1)
0 Likes
15 Replies
Absent Member.
Absent Member.

They have already been repaired:
ERROR: Modification time was incorrect, it has been updated

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Absent Member.
Absent Member.

No It is not corrected.
This morning has once again launched dsrepair-a and has received these errors:
** Automated Repair Mode **
Repairing Local Database
Start: Monday, 31 October 2011 8:47:57 Local Time
....
Repairing objects in a replica
Start: Monday, 31 October 2011 8:48:22 Local Time
[1 of 2] Master : T=AMI
Total objects in partition - T=AMI : 4187

ERROR: Modification time was incorrect, it has been updated
Object ID: 0000AE8B, DN: OU=gwercog.OU=gwkujb.OU=dntsk.O=ami.T=AMI


ERROR: Modification time was incorrect, it has been updated
Object ID: 0000AF67, DN: CN=Http Server - ercog.OU=gwercog.OU=gwkujb.OU=dntsk.O=ami.T=AMI
....


Serg
0 Likes
Absent Member.
Absent Member.

Serg,

On 10/31/11 07:56, skoltogyan wrote:

> No It is not corrected.


Have you checked that all of your servers are in (time) sync? It smells as if
one of these is still an hour off.

Peter
0 Likes
Absent Member.
Absent Member.

schwindp;2150105 wrote:
Serg,

On 10/31/11 07:56, skoltogyan wrote:

> No It is not corrected.


Have you checked that all of your servers are in (time) sync? It smells as if
one of these is still an hour off.

Peter


Yes. I`m checked. All time sync OK...

Serg
0 Likes
Absent Member.
Absent Member.

Load DSrepair on the server holding the Master of the affected partition. From the first menu run a TimeSync Check and a Report Sync Status. When finished, exit DSrepair and post the relevant portion of SYS:SYSTEM/dsrepair.log here, thanks.

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Absent Member.
Absent Member.

ataubman;2150336 wrote:
Load DSrepair on the server holding the Master of the affected partition. From the first menu run a TimeSync Check and a Report Sync Status. When finished, exit DSrepair and post the relevant portion of SYS:SYSTEM/dsrepair.log here, thanks.


****************************************************************************/

NetWare 1602.00 Directory Services Repair 20503.09, DS 20503.15

Log file for server ".GRAD.dntsk.ami" in tree "AMI"

Time synchronization and server status information

Start: Tuesday, 1 November 2011 22:58:07 Local Time



---------------------------+---------+---------+-----------+--------+-------

DS.NLM Replica Time Time is Time

Server name Version Depth Source in sync +/-

---------------------------+---------+---------+-----------+--------+-------

.BIO.shorsa46.dntsk.ami 20503.15 0 Secondary Yes 0

.ercog.gwercog.gwkujb.... 20506.04 0 Non-NetWare Yes 0

.gw.gwmailsrv.gwkujb.d... 20506.07 0 Non-NetWare Yes 0

.BRD1.srvvpn.dntsk.ami 20216.89 0 Secondary Yes 0

.srv6.srvidm.dntsk.ami 20506.07 0 Non-NetWare Yes 0

.GRAD.dntsk.ami 20503.15 0 Secondary Yes 0

---------------------------+---------+---------+-----------+--------+-------



*** END ***



/****************************************************************************/

NetWare 1602.00 Directory Services Repair 20503.09, DS 20503.15

Log file for server ".GRAD.dntsk.ami" in tree "AMI"

Start: Tuesday, 1 November 2011 22:58:17 Local Time

Retrieve replica status



Partition: .[Root].

Replica: .BIO.shorsa46.dntsk.ami 1/11/2011 22:58:12

Replica: .ercog.gwercog.gwkujb.dntsk.ami 1/11/2011 22:58:11

Replica: .gw.gwmailsrv.gwkujb.dntsk.ami 1/11/2011 22:58:15

Replica: .BRD1.srvvpn.dntsk.ami 1/11/2011 22:58:14

Replica: .srv6.srvidm.dntsk.ami 1/11/2011 22:58:11

Replica: .GRAD.dntsk.ami 1/11/2011 22:58:10

All servers synchronized up to time: 1/11/2011 22:58:10



Partition: .drv1test.driversidm.srvidm.dntsk.ami

Replica: .BIO.shorsa46.dntsk.ami 1/11/2011 22:44:45

Replica: .ercog.gwercog.gwkujb.dntsk.ami 1/11/2011 22:44:29

Replica: .gw.gwmailsrv.gwkujb.dntsk.ami 1/11/2011 22:44:30

Replica: .BRD1.srvvpn.dntsk.ami 1/11/2011 22:44:43

Replica: .srv6.srvidm.dntsk.ami 1/11/2011 22:44:36

Replica: .GRAD.dntsk.ami 1/11/2011 22:44:39

All servers synchronized up to time: 1/11/2011 22:44:29



Finish: Tuesday, 1 November 2011 22:58:18 Local Time



*** END ***
0 Likes
Absent Member.
Absent Member.

You time is in sync, but your time server setup is not valid. On one of the NetWare "Secondary" servers, load monitor - server parameters - time, and change SECONDARY to SINGLE in two places. Exit monitor and bounce timesync.nlm

The other two NW server should either have Configured Sources off (and Service Advertising on), or have CS on and pointing to the new SINGLE's IP address.

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Absent Member.
Absent Member.

ataubman;2150614 wrote:
You time is in sync, but your time server setup is not valid. On one of the NetWare "Secondary" servers, load monitor - server parameters - time, and change SECONDARY to SINGLE in two places. Exit monitor and bounce timesync.nlm

The other two NW server should either have Configured Sources off (and Service Advertising on), or have CS on and pointing to the new SINGLE's IP address.


All servers are adjusted so what to take time from two external time servers:
NTP1: sles 172.16.16.151:123
NTP2: sles 192.168.252.13:123

Server GRAD (nw65sp8 with MASTER repl):
TIMESYNC Configured Sources ON
TIMESYNC Service Advertising ON
TIMESYNC Time Sources 172.16.16.151:123; 192.168.252.13:123
TIMESYNC Type SECONDARY
Default Time Server Type SECONDARY

Server BIO (nw65sp8 with R/W repl)
TIMESYNC Configured Sources ON
TIMESYNC Service Advertising ON
TIMESYNC Time Sources 172.16.16.151:123; 192.168.252.13:123
TIMESYNC Type SECONDARY
Default Time Server Type SECONDARY

What isn't true?

Serg
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

On Wed, 02 Nov 2011 07:36:02 +0000, skoltogyan wrote:

> ataubman;2150614 Wrote:
>> You time is in sync, but your time server setup is not valid. On one of
>> the NetWare "Secondary" servers, load monitor - server parameters -
>> time, and change SECONDARY to SINGLE in two places. Exit monitor and
>> bounce timesync.nlm
>>
>> The other two NW server should either have Configured Sources off (and
>> Service Advertising on), or have CS on and pointing to the new SINGLE's
>> IP address.

>
> All servers are adjusted so what to take time from two external time
> servers:
> NTP1: sles 172.16.16.151:123
> NTP2: sles 192.168.252.13:123
>
> Server GRAD (nw65sp8 with MASTER repl): TIMESYNC Configured Sources ON
> TIMESYNC Service Advertising ON
> TIMESYNC Time Sources 172.16.16.151:123; 192.168.252.13:123 TIMESYNC
> Type SECONDARY
> Default Time Server Type SECONDARY
>
> Server BIO (nw65sp8 with R/W repl)
> TIMESYNC Configured Sources ON
> TIMESYNC Service Advertising ON
> TIMESYNC Time Sources 172.16.16.151:123; 192.168.252.13:123 TIMESYNC
> Type SECONDARY
> Default Time Server Type SECONDARY
>
> What isn't true?



That you're using NTP is good, which is why your time is correct. But,
what's wrong is that for NetWare / Timesync.nlm, your configuration is
not valid. "Secondary" servers must have a "Single Reference" to talk to,
(or must have a "Reference" and several "Primary") otherwise they will
not consider themselves to be in sync, even if the time is actually
correct.

Change one server (eg: GRAD) to "Single". It will get its time from your
NTP servers. Change the other (eg: BIO) configured sources to point it at
GRAD.


--
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Knowledge Partner http://forums.novell.com

Please post questions in the newsgroups. No support provided via email.

0 Likes
Absent Member.
Absent Member.

>Change the other (eg: BIO) configured sources to point it at
>GRAD.
remove record:
172.16.16.151:123;192.168.252.13:123
and
add record
172.16.16.254

?
0 Likes
Absent Member.
Absent Member.

If that last IP address is GRAD's, yes, make that chance to BIO. Plus you need to change SECONDARY to SINGLE in two places in GRAD's Monitor, as I explained earlier.

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.