Replies: 15 comments 14 replies
-
From the container you will get logs to the console. These are the logs that tell you what EJBCA is doing. |
Beta Was this translation helpful? Give feedback.
-
Hi @primetomas, Thanks for your answer! I have checked the database and it seems indexes are existing: The database is not large. I only have 1 CA and 1 Intermediate CA. The number of issued certs is roundabout 20. So I don't think it is related to the data itself. The container restrictions are visible here: CPU Priority is low, the memory limit is set to 2 GB. Do you think this is not sufficient? Bye |
Beta Was this translation helpful? Give feedback.
-
Can you check the console output to see if anything is going on? 2GB should be enough for such a small environment. We're using the container is very very large deployments without issues. SO something fishy is going on in that environment. |
Beta Was this translation helpful? Give feedback.
-
Hi @primetomas, sorry for the late reply, I was not at home. I have now redirected the output of the console to a file and am tracking when the load will increase. After that I will check the file and provide more information. Thanks for your hints! |
Beta Was this translation helpful? Give feedback.
-
Hi @primetomas, and here we go... In the attached log you can see that ejbca was not able to connect to ldap server (it was offline for some time, backup...) and since then it seems the load increased. Hopefully the log will give you some hints on why this happend. |
Beta Was this translation helpful? Give feedback.
-
You have a publisher queue process worker configured. How did you configure this? Does it run very often? I guess there are many retries or something. But the log looks ok, the service worker finishes saying that it fails to connect to the LDAP server. The service should run again and eventually publish to the LDAP server once it is up and running, unless TCP connections hang for some reason, but it doesn't look like that from the log. (Using LDAP is getting quite rare out there...) |
Beta Was this translation helpful? Give feedback.
-
Hi @primetomas , I had the worker configured to run every 5 minutes but realized that it does not make sense to call it that often. Now changed it to "once per day", let's see if this make the issue appear again. Thanks so far! |
Beta Was this translation helpful? Give feedback.
-
Hi @primetomas, another exception today, this time related to the database server: `2023-03-13 02:00:38,198+0000 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (ConnectionValidator) IJ030027: Destroying connection that is not valid, due to the following exception: org.mariadb.jdbc.Connection@20fa1282: java.sql.SQLNonTransientConnectionException: (conn=103908) Socket error 2023-03-13 02:00:38,203+0000 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (ConnectionValidator) IJ030027: Destroying connection that is not valid, due to the following exception: org.mariadb.jdbc.Connection@118ff1a6: java.sql.SQLNonTransientConnectionException: (conn=103909) Socket error 2023-03-13 02:00:38,205+0000 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (ConnectionValidator) IJ030027: Destroying connection that is not valid, due to the following exception: org.mariadb.jdbc.Connection@18bb9ae0: java.sql.SQLNonTransientConnectionException: (conn=103910) Socket error 2023-03-13 02:00:38,208+0000 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (ConnectionValidator) IJ030027: Destroying connection that is not valid, due to the following exception: org.mariadb.jdbc.Connection@64c79624: java.sql.SQLNonTransientConnectionException: (conn=103911) Socket error 2023-03-13 02:00:38,210+0000 WARN [org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory] (ConnectionValidator) IJ030027: Destroying connection that is not valid, due to the following exception: org.mariadb.jdbc.Connection@45d6310e: java.sql.SQLNonTransientConnectionException: (conn=103912) Socket error After that the load again increased. Is there anything you can determine from the logs what goes wrong here? Thanks! |
Beta Was this translation helpful? Give feedback.
-
As far as I can see nothing is happening in EJBCA. I assume that the database is on a separate container, you don't have any backup jobs or similar that runs by the platform? The container is not RAM constrained, etc? |
Beta Was this translation helpful? Give feedback.
-
Hi @primetomas, thanks for your quick answer! In fact the container WAS RAM constrained to 2GB. I have removed this limit now to see if it gets better. Are there any other settings required for the container to run without issues? Anything I should configure? |
Beta Was this translation helpful? Give feedback.
-
A question that came up. Do you have something making connection checks, or doing an EJBCA Healthcheck? |
Beta Was this translation helpful? Give feedback.
-
No, I am not actively requesting anything from EJBCA regularily. Mostly relying on the push mechanisms. I have an implementation on the servers using a cmp client to update certs. It is executed once a day (in the early morning). It basically checks if the server cert is still valid, which is always the case at the moment. Do you think the cmp endpoint might cause issues? |
Beta Was this translation helpful? Give feedback.
-
I don't think the CMP endpoint would cause any issues. It's used to issue billions of certificates in mission critical systems without known issues. |
Beta Was this translation helpful? Give feedback.
-
Hi, a week ago I updated to EJBCA Community 8.0 and since then the issue did not occur. So it seems something was changed that prevents the problem from happening. Any information of what changes might have solved it? Was there an active analysis concerning this or was it fixed "accidentially"? Thanks! |
Beta Was this translation helpful? Give feedback.
-
Nope, nothing specific that has been done. Generic upgrades of many components of course, dependencies, java, base-os, etc etc. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi guys,
I am facing an issue with the official ejbca community docker installation. I am running it on a Synology NAS and the container starts to have a high load after some time (sometimes 1 day, sometimes more days).
I already tried to deactivate my publishers (Active Directory and custom Unix publishers), but to no avail. It seems to me that this is somehow related with the database connection, but I cannot really prove it. I checked the logs but cannot find anything problematic:
ejbca.zip
I am using a MariaDB database as backend.
Maybe somebody has a hint what to do to avoid ejbca exhausting the CPU that way.
Thanks!
Bye
Beta Was this translation helpful? Give feedback.
All reactions