-
Type:
Bug
-
Status: Open
-
Resolution: Unresolved
-
Affects Version/s: 7.6.3
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Severity:Medium
Issue Description
Artifactory health ping command is giving "OK" response when we remove the SSL certificate of the database(rds-ca-2019-root.pem) which is configured as part of the connection string.
Artifactory version:
6.X and 7.X
Connection Url:
jdbc:postgresql://<rdsdb.amazonaws.com>:<port>/artdb?ssl=true&sslfactory=org.postgresql.ssl.jdbc4.LibPQFactory&sslmode=verify-full&sslrootcert=/root/artifactory/etc/rds-ca-2019-root.pem
Error message in log:
2020-09-17 06:03:39,956 [http-nio-8081-exec-7] [INFO ] (o.a.e.UploadServiceImpl:386) - Deploy to 'generic-local:working-edge.txt' Content-Length: 8935 2020-09-17 06:03:40,003 [http-nio-8081-exec-7] [ERROR] (o.a.r.d.DbStoringRepoMixin:283) - IO error while trying to save resource generic-local:working-edge.txt'': java.io.FileNotFoundException: /root/artifactory-pro/etc/rds-ca-2019-root.pem (No such file or directory) 2020-09-17 06:03:40,006 [http-nio-8081-exec-7] [ERROR] (o.a.r.c.e.m.GlobalExceptionMapper:48) - Cannot deploy file 73d82337-2e73-4edd-b1c9-2df8aab6fc9e_working-edge.txt. Cause: /root/artifactory-pro/etc/rds-ca-2019-root.pem (No such file or directory) org.artifactory.sapi.common.RepositoryRuntimeException: Cannot deploy file 73d82337-2e73-4edd-b1c9-2df8aab6fc9e_working-edge.txt. Cause: /root/artifactory-pro/etc/rds-ca-2019-root.pem (No such file or directory)
Steps to reproduce:
1. Create Artifactory (6.X or 7.X) instance
2. Configure Amazon RDS database over SSL certificate with connection string having the SSL certificate.
3. Perform Artifactory health ping which will give us "OK" response.
4. Rename/Remove the SSL certificate(rds-ca-2019-root.pem) from its location and try to deploy a file which will give us the error
5. Perform Artifactory health ping which still gives us the "OK" response.
