How to Share log files with Support in Domino 3.6.x

Version:

Domino 3.6.  Note that Domino 3.6 is EOL and no longer supported except by prior contractual agreement.

Issue:

The nucleus services on 3.6.x are deployed as a standalone container on either the central node or on a dedicated frontend node.  Logs in Domino 3.6 are persisted to disk and their locations are deployment specific. They are usually under /opt or /domino. Note that frontend logs and dispatcher logs are both named application.log and are located on their individual central or frontend hosts.

Also, the logs files are set to rotate every hr or so (again deployment specific), meaning it will be best to grab them immediately after the problem occurs.

Notes/Information:

If you are familiar with moving files from your deployment follow the steps you know.  If not a brief, generalized guideline is below, but reach out to support for assistance if needed.

• ssh into appropriate node from your bastion or directly if allowed
• cd to the logs location (mentioned above)
• next we archive the files and compress them :
  • # tar -clf - . | gzip --best > ../"archive-name.tar.gz"
• next we copy the compressed archive to the bastion host :- (from the bastion) scp ubuntu@ip:path/to/file path/to/local (make sure you have apt permissions to the remote file)
• use pscp to copy the archive from bastion to local workstation (or you could use the mail builtin from dispatcher node, you could also do a curl to your smtp server and generate an email using that )
• send the file across to the support via email or by uploading it to a Domino deployment accessible by both the parties.