Troubleshooting

---

Invalid SSL Certificate in SEAL MongoDB

If your system crashes with a fatal assertion 28652, the reason may be an invalid SSL certificate for SEAL MongoDB.

Check the validity of the SSL certificate as follows:

1. In an editor, open the MongoDB configuration file:

   • Linux:

     /opt/seal/etc/mongod.conf
     

   • Windows:

     C:\ProgramData\SEAL Systems\config\mongod.conf
     

2. Replace the line:

   CAFile: C:\ProgramData\SEAL Systems\config\tls\ca.pem
   

   by the following line:

   allowInvalidCertificates: true
   

3. Save the configuration file.

4. Restart MongoDB:

   • Linux:

     sudo systemctl restart mongod
     

   • Windows:

     restart-service seal-mongodb
     

If you can verify the problem this way, continue as follows.

Solution:

1. Check, whether the date is set correctly in the system time.

2. Check the validity of the PEM file.

   Hint - checking PEM files

   You can use the openssl commands to explore the details of a certificate, e. g.

   openssl x509 -in mycert.pem -text -noout
   

   If you do not have installed openssl, you can use a web tool to check the certificate.

3. If necessary, replace the the invalid certificate file with a new PEM file.

4. Undo the previous temporary changes in the SEAL MongoDB configuration file.

5. Restart MongoDB.

---

MongoDB Allocates too Much Disk Space

MongoDB gets too big, because it does not automatically release unneeded disk space to the operating system.

Solution:

The compact database command attempts to reduce the disk space, see original documentation.

---