> I recall having a case where acme.sh generated two certs and the deploy > script was called for the second cert, but asterisk was not done starting up > and something similar happened.
To be more clear, "asterisk was not done starting up" from deploying the first certificate and then tried to deploy again for the second certificate. Lonnie > On Feb 22, 2024, at 3:37 PM, Lonnie Abelbeck <li...@lonnie.abelbeck.com> > wrote: > > Hi Michael, > > I had my Jetway NF9HG-2930 die a year or so ago, I know Michael Keuter had a > couple NF9HG-2930s die. Though in my case it would not power up anymore. > > This case does seem to be different. > > Hmmm, is your ACME only a single domain (cert)? > > I recall having a case where acme.sh generated two certs and the deploy > script was called for the second cert, but asterisk was not done starting up > and something similar happened. > > Lonnie > > > > > >> On Feb 22, 2024, at 2:39 PM, Michael Knill >> <michael.kn...@ipcsolutions.com.au> wrote: >> >> Running version 1.5.0 on Jetway NF9HG-2930. >> >> ------------------- >> Feb 22 23:00:42 30390_Ortho-ACT_CM1 daemon.err lighttpd[30995]: >> (server.c.2029) server stopped by UID = 0 PID = 7065 >> Feb 22 23:00:43 30390_Ortho-ACT_CM1 daemon.err lighttpd[7087]: >> (server.c.1436) server started (lighttpd/1.4.51) >> Feb 22 23:00:43 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME >> certificates deployed for HTTPS and 'lighttpd' restarted >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME >> certificates deployed for SIP-TLS and 'asterisk' restart when convenient >> requested >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: >> ERROR[31178]: astobj2_container.c:492 in ao2_iterator_init: FRACK!, Failed >> assertion user_data is NULL (0) >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: >> ERROR[31178]: :0 in : Got 11 backtrace records # 0: >> /usr/sbin/asterisk(__ao2_ref+0x5de) [0x46213e] # 1: >> /usr/sbin/asterisk(ao2_iterator_init+0x2f) [0x464a1f] # 2: >> /usr/lib/asterisk/modules/app_queue.so(+0xef4d) [0x14f159681f4d] # 3: >> /usr/sbin/asterisk() [0x51849e] # 4: /usr/sbin/asterisk() [0x5206a4] # 5: >> /usr/sbin/asterisk() [0x573c60] # 6: >> /usr/sbin/asterisk(ast_taskprocessor_execute+0x16f) [0x591f0f] # 7: >> /usr/sbin/asterisk() [0x591fb0] # 8: /usr/sbin/asterisk() [0x >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: >> ERROR[31178]: app_queue.c:2823 in extension_state_cb: FRACK!, Failed >> assertion user_data is NULL (0) >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 local0.err asterisk[31159]: >> ERROR[31178]: :0 in : Got 11 backtrace records # 0: /usr/sbin/asterisk() >> [0x461502] # 1: /usr/sbin/asterisk(__ao2_iterator_next+0x1d8) [0x464e28] # >> 2: /usr/lib/asterisk/modules/app_queue.so(+0xef9c) [0x14f159681f9c] # 3: >> /usr/sbin/asterisk() [0x51849e] # 4: /usr/sbin/asterisk() [0x5206a4] # 5: >> /usr/sbin/asterisk() [0x573c60] # 6: >> /usr/sbin/asterisk(ast_taskprocessor_execute+0x16f) [0x591f0f] # 7: >> /usr/sbin/asterisk() [0x591fb0] # 8: /usr/sbin/asterisk() [0x5a0c5a] # 9: >> >> ……. more of the same ……... >> >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.info kernel: asterisk[31178]: >> segfault at 58 ip 00000000004f4da0 sp 000014f15a55ba58 error 4 in >> asterisk[43d000+1d6000] >> Feb 22 23:00:44 30390_Ortho-ACT_CM1 user.info kernel: Code: c0 74 1f 85 f6 >> 74 1b 89 f2 48 39 d0 72 14 48 8b 47 68 48 63 f6 48 8b 44 f0 f8 c3 0f 1f 80 >> 00 00 00 00 31 c0 c3 0f 1f 44 00 00 <48> 8b 47 58 c3 66 66 2e 0f 1f 84 00 00 >> 00 00 00 49 89 f9 41 b8 af >> Feb 22 23:00:45 30390_Ortho-ACT_CM1 user.info safe_asterisk: Asterisk exited >> on signal 11. >> Feb 22 23:00:45 30390_Ortho-ACT_CM1 user.info safe_asterisk: Automatically >> restarting Asterisk. >> Feb 22 23:00:46 30390_Ortho-ACT_CM1 user.notice acme-client: New ACME >> certificates deployed for XMPP and 'prosody' restarted >> ------------------- >> >> Im thinking of putting this one in the cloud as this box has been there for >> a while, but wondering if this is a bug or something else? I cant recall >> seeing it before. >> >> Thanks >> Michael Knill >> >> >> _______________________________________________ >> Astlinux-users mailing list >> Astlinux-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to >> pay...@krisk.org. > > > > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
