Hi Mathi. I think you’re right in that it’s the expected behavior. When you think about it, it makes sense, just as you described.
Thanks a lot for answering. Best regards. De: Mathi N P [mailto:mathi.np....@gmail.com] Enviado el: jueves, 09 de julio de 2020 12:55 Para: Tocino García, José Tomás [ELIMCO] <elimco.jttoci...@navantia.es> CC: Opensaf-users@lists.sourceforge.net Asunto: <Externo> Re: [users] Component AutoRepair when instantiation failed Navantia Información de Seguridad: Este correo procede de una fuente externa. Extrema las medidas de precaución y no abras ningún enlace o fichero adjunto si no estás convencido de su seguridad y autenticidad. ________________________________ Hi, I think, this is an expected behaviour. It would be a futile attempt to attempt automatic repair of a component that is unable to even get itself started. Most likely such situations would require administrator intervention and manual repair (The AMF state machine should reflect this). The principle here is that AMF attempts(based on configuration) to auto repair only components (registered) that are being monitored. Thanks, Mathi. On Thu, Jun 25, 2020 at 9:05 PM Tocino García, José Tomás [ELIMCO] <elimco.jttoci...@navantia.es<mailto:elimco.jttoci...@navantia.es>> wrote: Hi there. I have a situation where a component fails to instantiate (due to timeout) because it waits on some sockets when it starts, before it even registers with OpenSAF. Given I have the saAmfCompNumMaxInstantiateWithoutDelay set to 5, it tries to re-instantiate it five times before setting its presence state to INSTANTIATION-FAILED. However, I do not know why OpenSAF does not try to repair the component afterwards. On the other hand, if the component successfully instantiates and starts running, and then I kill it (or otherwise fails), OpenSAF correctly auto-repairs it by restarting it, so I guess configuration-wise I have no issues. The SG has its AutoRepair attribute set to true, the Comp has its saAmfCompDisableRestart attribute set to false. Is there a way of forcing an auto-repair on an INSTANTIATION-FAILED component? Thanks! [Navantia] ________________________________ NAVANTIA S.A. S.M.E. Este mensaje y cualquier fichero anexo al mismo contiene información de carácter confidencial dirigida exclusivamente a su(s) destinatario(s) y, en su caso, sometida a secreto profesional. Queda prohibida su difusión, copia o distribución a terceros sin la previa autorización escrita. Si Vd. ha recibido este mensaje por error, se ruega lo comunique inmediatamente por esta misma vía y proceda a su completa eliminación. Puede revisar nuestra política de privacidad en http://www.navantia.es/es/legal/. The information in this e-mail and in any attachments is confidential and, if any, protected by a professional privilege and intended solely for the attention and use of the named address(es). You are hereby notified that any dissemination, copy or distribution of this information is prohibited without the prior written consent. If you have received this communication in error, please notify the sender by reply e-mail and delete it. You can review our privacy policy at http://www.navantia.es/en/legal/. ________________________________ [Navantia] Piense en el medio ambiente. ¿Necesita realmente imprimir este correo? Please care for the environment. Do you really need to print this e-mail? _______________________________________________ Opensaf-users mailing list Opensaf-users@lists.sourceforge.net<mailto:Opensaf-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/opensaf-users _______________________________________________ Opensaf-users mailing list Opensaf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-users
