Martin, My server with this clear, ran the xml cleaning procedure and yet the problem has not been resolved . We can do some more procedure.
Fabricio SSBr | Strong Security Brasil | Fabricio Gimenes Porto | Dpto. Técnico | Tel. +55 11 2897-1566 |Cel. +55 11 9-4558-6564 |fgime...@strongsecurity.com.br As informações contidas nesta mensagem são CONFIDENCIAIS e protegidas pelo sigilo legal. A divulgação, distribuição ou reprodução do teor deste documento depende de autorização do emissor. Caso V. Sa. não seja o destinatário, preposto, ou a pessoa responsável pela entrega desta mensagem, fica, desde já, notificado que qualquer divulgação, distribuição ou reprodução é estritamente proibida, sujeitando-se o infrator às sanções legais. Caso esta comunicação tenha sido recebida por engano, favor nos avisar imediatamente, respondendo esta mensagem. The information contained in this message is CONFIDENTIAL. If the reader of this transmittal is not the intended recipient or an agent responsible for delivering it, you are hereby notified that you have received this communication in error, and that any dissemination, distribution, retention or copy of this communication is strictly prohibited. In this case, please immediately reply this message to the sender. Antes de imprimir pense em seu compromisso com o Meio Ambiente. -----Mensagem original----- De: Martin Hecht [mailto:he...@hlrs.de] Enviada em: Thursday, September 24, 2015 1:36 PM Para: fgime...@strongsecurity.com.br Cc: Users' Help and Suggestions <openca-users@lists.sourceforge.net> Assunto: Re: [Openca-Users] Openca Socket error 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 > > ------------------------------------------------------------------------------ _______________________________________________ Openca-Users mailing list Openca-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openca-users
