OpenCA Error addMessage failed for log slot XML. Cannot create directory [Solved]

Updated on October 31, 2017

Do you see the below error while accessing OpenCA pub page?

Error 64510030 - General Error
OpenCA Error addMessage failed for log slot xml (6512032). Cannot create directory /home/openra/var/log/xml/time/2017/10/30/04/28.
Content-type: text/html

Below is the detailed error message in stderr.log.

PKI Master Alert: Logging error
PKI Master Alert: Aborting all operations
PKI Master Alert: Error: 64510030
PKI Master Alert: Message: addMessage failed for log slot sys_syslog (6511070). Cannot write to syslogdevice.
PKI Master Alert: debugging messages of logging follow
[Sat Sep 16 01:20:54 2017] openca_start: [Sat Sep 16 01:20:54 2017] openca_start: OpenCA: General error trapped 6251026: Aborting connection - you are using a wrong security protocol (http). at /home/openra//modules/perl5/OpenCA/UI/HTML.pm line 179.
[Sat Sep 16 01:20:54 2017] openca_start: Compilation failed in require at ./openca_start line 62.
OpenCA::Logger::Syslog::Sys: Using syslog priority CRIT because no level was specified.

Solution:

Step 1: As the error message clearly says Cannot create directory, navigate to the respective folder and find out if the directory /home/openra/var/log has write permission for web server user (for example, apache user).

Note:

The log directory might differ on your machine. For example, if  OpenCA installed under /usr/local/openca, then lookout for log directory under /usr/local/openca/var/log. In my case, OpenCA is installed in /home/openra/ folder.

Step 2: If the permissions are fine, then the issue might be due to low disk space. Use the below command to check the status of the disk.

df -h 

Filesystem Size Used Avail Use% Mounted on
/dev/sda2 95G 11G 80G 12% /
/dev/sda1 487M 54M 408M 12% /boot
tmpfs 1.7G 0 1.7G 0% /dev/shm
/dev/sda5 186G 186G 0G 100% /home
/dev/sda6 9.5G 163M 8.9G 2% /tmp
/dev/sda3 67G 11G 54G 16% /usr

Ahh! Did you see 100% full for /home partition (That’s the partition I had my OpenCA installed). In your case, OpenCA might have been installed in a different partition. As there’s no enough space left, the OpenCA daemon was not able to create directory for logging. Clear the old backup files, unwanted files or increase the size of the partition without affecting the installation.

That’s it! Go ahead and start OpenCA daemon and it should work.

Was this article helpful?

Related Articles

Leave a Comment