test

Sun Gathering Debug Data for Sun Java System Calendar Server

ProcedureTo Collect Required Debug Data for Any Calendar Server Problem

All problems described in this technical note need basic information collected about when the problem occurred and about the system having the problem. Use this task to collect that basic information.

  1. Note the day(s) and time(s) the problem occurred.

  2. Provide a graphical representation of your deployment. Include all hosts and IP addresses, host names, operating system versions, role they perform, and other important systems such as load balancers, firewalls, and so forth. Also include the following information:

    • Calendar Server topology. For example, describe front-end and back-end Calendar servers, if you have them.

    • LDAP Directory topology. Describe your Directory Server deployment features such as replicated directories. Are any caches enabled?

    • Calendar Server features. Describe other Calendar Server features you have configured. These include, at a minimum, virtual domains, SSL, SSO, and LDAP cache..

  3. Note the operating system.

    Solaris OS

    uname -a

    HP-UX

    uname -r

    Linux

    more /etc/redhat-release

    Windows

    C:\Program Files\Common files\Microsoft Shared\MSInfo\msinfo32.exe /report C:\report.txt

  4. Note the patch level.

    Solaris OS

    showrev -p | grep SUNWics5

    HP-UX

    swlist

    Linux

    rpm -qa

    Windows

    Already provided in the C:\report.txt file above.

    Note –

    If possible, also provide explorer information (SUNWexplo) of the machine having the problem. Edit the ics.conf file and increase the log level by using the logfile.loglevel = "Debug" parameter.

  5. Note the version of Calendar Server.

    Be sure to send the entire screen output of the command.

    UNIX and Linux

    cd cal-svr-base./cal/bin/csstart version

    Windows

    cd cal-svr-base\cal\bin\csstart.exe version

  6. Create a tar file of the Calendar Server configuration directory.

    UNIX and Linux

    Create a tar file of the cal-svr-base/cal/bin/config directory.

    Windows

    Create a tar file of the cal-svr-base\cal\bin\config directory.

    Note –

    Always be sure to include the ics.conf file.

  7. Get the start, stop, http, admin, and notifyd processes log files.

    The logfile.logdir parameter in the ics.conf file specifies the paths of these log files.

    Note –

    If possible, provide just the relevant extracts of log files for the same time period that show the problem, with sufficient context to see what else was occurring during the error occurrence and shortly before. Thus for relatively short log files, send the entire log file, whereas for long-running hence large log files, an extract might be more appropriate, though be sure to include all the material from the time of the error as well as at least some lead-in logging from before the error apparently occurred.

  8. Get the Access, Errors, and Audit logs from the Directory Server used by Calendar Server.

    The paths of these files are specified by the following parameters in the Directory Server dse.ldif file:

    • nssldap-accesslog

    • nssldap-errorlog

    • nssldap-auditlog

    UNIX and Linux

    server-root/slapd-identifier/logs/access

    server-root/slapd-identifier/logs/errors

    server-root/slapd-identifier/logs/audit (if enabled)

    Windows

    server-root\slapd-identifier\logs\access

    server-root\slapd-identifier\logs\errors

    server-root\slapd-identifier\logs\audit (if enabled)