Hi Fabricio, this looks like the openca daemon has crashed or is in some kind of deadlock. Usually, you just have to stop the openca service in order to clean up things, and start it again.
It may take a while to become responsive again (in a VM running on old hardware it may well be a minute and more), but as soon as the service has finished its startup, you should be able to connect via browser again. However, if the reason for the crash is a full disk (or a file system which ran out of inodes), then you first have to clean up e.g. the xml log directory (I usually put everything into a tgz and remove all the xml files and the directories of the current and the past year(s). A proper logrotate mechanism would be useful here... Martin On 09/24/2015 02:53 PM, Fabricio Gimenes wrote: > Hi, > > > > My name is Fabricio. > > > > I'm a problem in openca_socket , which access the apache web presents > seguitne message. > > > > OpenCA Error: Server is not online or does not accept requests > (//var/openca/tmp/openca_socket - //var/openca/tmp/openca_socket). 0 > >
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------
_______________________________________________ Openca-Users mailing list Openca-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openca-users
