Admin Emails

In SurgeLDAP v1.0h or higher, SurgeLDAP is setup to send different emails to the admin in varying cases. Each of the cases are explained below, as well as an example email. Each section will also explain what you need to do with this email
Server Started
Everytime SurgeLDAP starts you will receive an email stating if it correctly setup the LDAP database. The layout of this message is as follows:

 
SurgeLDAP - Started
LDAPServer v1.0h (Build 1)
Computer: COMP       Operating System: Windows NT
Report Generated at: Tue, 13 Jan 2004 12:50:13 +1200
-------------------------------------------------

LDAP port on SurgeLDAP have been setup correctly.

-------------------------------------------------

 
The first section is the general information about surgeldap setup on the system with the version information, computer name and operating system.

 
The second section is the information about the start up in this case everything was fine and no problems occured. If any problems do occur you should first consult your surgeldap.log file as it will have more information in this file. If the problem cannot be solved you should contact Netwin LTD at the email address:
support-surgemail@netwinsite.com
Backup/Restore
Everytime SurgeLDAP does a backup or restore of the database SurgeLDAP will send you an email. The layout of this message is as follows:

 
SurgeLDAP - Database Backup - 13-Jan-04 (01.55.45pm)
LDAPServer v1.0h (Build 2)
Computer: COMP       Operating System: Windows NT
Report Generated at: Tue, 13 Jan 2004 13:55:55 +1200
-------------------------------------------------

Compress 20 bin files/directories
Compress 21 schema files/directories
Compress 1 LDIF files/directories

-------------------------------------------------
SurgeLDAP - Database Restore - c:\surgeldap2\backup\13-Jan-04_(11.08.57am)\
LDAPServer v1.0h (Build 2)
Computer: COMP       Operating System: Windows NT
Report Generated at: Tue, 13 Jan 2004 13:56:11 +1200
-------------------------------------------------

Uncompresing 'c:\surgeldap2\backup\13-Jan-04_(11.08.57am)\bins.compress'
Uncompresing 'c:\surgeldap2\backup\13-Jan-04_(11.08.57am)\schema.compress'
Uncompresing 'c:\surgeldap2\backup\13-Jan-04_(11.08.57am)\ldif.compress'

-------------------------------------------------

 
The second section is the information about the backup or restore the above are sucessfull backup/restore emails. If any problems do occur you should first consult your surgeldap.log file as it will have more information in this file. If the problem cannot be solved you should contact Netwin LTD at the email address:
support-surgemail@netwinsite.com
Replicate CRC Checks
Everytime SurgeLDAP does a CRC check either automatically or when asked to via the web admin page SurgeLDAP will send you an email. The layout of this message is as follows:

 
SurgeLDAP - Replicate CRC Check - backup.netwin.co.nz
LDAPServer v1.0h (Build 2)
Computer: COMP       Operating System: Windows NT
Report Generated at: Tue, 13 Jan 2004 13:56:14 +1200
-------------------------------------------------

Replicate CRC Check Against: backup.netwin.co.nz
CRC Log - Dated: 13/01/2004 (13:56:14pm)  (d/m/y)
backup.netwin.co.nz: "dc=netwin,dc=co,dc=nz" : 7 : Missed matched CRC's
        : "cn=hope" : 1 : Missed matched CRC's
        : "cn=john@netwinsite\.com" : 1 : CRC's ok.
        : "cn=lynden@netwin\.co\.nz" : 1 : CRC's ok.
        : "cn=test" : 1 : CRC's ok.
        : "cn=what" : 1 : Missing on Local
        : "cn=william" : 1 : Missing on replicate
        : "fid=1022700684759" : 1 : CRC's ok.
        : "uid=aristia" : 1 : CRC's ok.
backup.netwin.co.nz: "cn=lynden@netwin\.co\.nz,dc=netwin,dc=co,dc=nz" : 1 : Missed
matched CRC's
        : "cn=test" : 1 : Missing on replicate

-------------------------------------------------

 
The above just informs you of any CRC's that don't match, and it's up to the admin to decide what if any action should be taken. the layout is:
replicate_ip : dn (full or relative) : number records at this level : message
In the above example 2 records are missing on the Replicate server that exists on the local server, and 1 on the replicate server that doesn't exist on the replicate server. Also 1 record does not match correctly.

Missing on local:
           cn=what,dc=netwin,dc=co,dc=nz
Missing on Replicate:
           cn=william,dc=netwin,dc=co,dc=nz
           cn=test,cn=lynden@netwin\.co\.nz,dc=netwin,dc=co,dc=nz
Invalid Match:
           cn=hope,dc=netwin,dc=co,dc=nz

In the above case the reason why the 'cn=hope' dn record did not match as the password was changed on the replicate server and not on the local server.
Server Crash
Any time SurgeLDAP encounters an unexpected error you will receive an email. The layout of this message is as follows:

 
SurgeLDAP - Unexpected Signal
LDAPServer v1.0h (Build 1)
Computer: COMP       Operating System: Windows NT
Report Generated at: Tue, 13 Jan 2004 12:50:13 +1200
-------------------------------------------------

SurgeLDAP has encountered a 'Unexpected Signal'. Attached is the lastest
Surgeldap.log file. Please pass this information on to:
<support-surgeldap@netwinsite.com>

-------------------------------------------------

 
Information about the problem that occured willbe displayed and if you get any messages like this you should email them to:
support-surgemail@netwinsite.com
Including any attachments they have.

 
You will also need to manually restart the server again.