Menu
▾
▴
astlinux-users — AstLinux Users Mailing List
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(91) |
Feb
(111) |
Mar
(226) |
Apr
(65) |
May
(197) |
Jun
(202) |
Jul
(92) |
Aug
(87) |
Sep
(120) |
Oct
(133) |
Nov
(89) |
Dec
(155) |
| 2008 |
Jan
(251) |
Feb
(136) |
Mar
(174) |
Apr
(149) |
May
(56) |
Jun
(32) |
Jul
(36) |
Aug
(171) |
Sep
(245) |
Oct
(244) |
Nov
(218) |
Dec
(272) |
| 2009 |
Jan
(113) |
Feb
(119) |
Mar
(192) |
Apr
(117) |
May
(93) |
Jun
(46) |
Jul
(80) |
Aug
(54) |
Sep
(109) |
Oct
(70) |
Nov
(145) |
Dec
(110) |
| 2010 |
Jan
(137) |
Feb
(87) |
Mar
(45) |
Apr
(157) |
May
(58) |
Jun
(99) |
Jul
(188) |
Aug
(136) |
Sep
(101) |
Oct
(100) |
Nov
(61) |
Dec
(60) |
| 2011 |
Jan
(84) |
Feb
(43) |
Mar
(70) |
Apr
(17) |
May
(69) |
Jun
(28) |
Jul
(43) |
Aug
(21) |
Sep
(151) |
Oct
(120) |
Nov
(84) |
Dec
(101) |
| 2012 |
Jan
(119) |
Feb
(82) |
Mar
(70) |
Apr
(115) |
May
(66) |
Jun
(131) |
Jul
(70) |
Aug
(65) |
Sep
(66) |
Oct
(86) |
Nov
(197) |
Dec
(81) |
| 2013 |
Jan
(65) |
Feb
(48) |
Mar
(32) |
Apr
(68) |
May
(98) |
Jun
(59) |
Jul
(41) |
Aug
(52) |
Sep
(42) |
Oct
(37) |
Nov
(10) |
Dec
(27) |
| 2014 |
Jan
(61) |
Feb
(34) |
Mar
(30) |
Apr
(52) |
May
(45) |
Jun
(40) |
Jul
(28) |
Aug
(9) |
Sep
(39) |
Oct
(69) |
Nov
(55) |
Dec
(19) |
| 2015 |
Jan
(13) |
Feb
(21) |
Mar
(5) |
Apr
(14) |
May
(30) |
Jun
(51) |
Jul
(31) |
Aug
(12) |
Sep
(29) |
Oct
(15) |
Nov
(24) |
Dec
(16) |
| 2016 |
Jan
(62) |
Feb
(76) |
Mar
(30) |
Apr
(43) |
May
(46) |
Jun
(62) |
Jul
(21) |
Aug
(49) |
Sep
(67) |
Oct
(27) |
Nov
(26) |
Dec
(38) |
| 2017 |
Jan
(7) |
Feb
(12) |
Mar
(69) |
Apr
(59) |
May
(54) |
Jun
(40) |
Jul
(76) |
Aug
(82) |
Sep
(92) |
Oct
(51) |
Nov
(32) |
Dec
(30) |
| 2018 |
Jan
(22) |
Feb
(25) |
Mar
(34) |
Apr
(35) |
May
(37) |
Jun
(21) |
Jul
(69) |
Aug
(55) |
Sep
(17) |
Oct
(67) |
Nov
(9) |
Dec
(5) |
| 2019 |
Jan
(19) |
Feb
(12) |
Mar
(15) |
Apr
(19) |
May
|
Jun
(27) |
Jul
(27) |
Aug
(25) |
Sep
(25) |
Oct
(27) |
Nov
(10) |
Dec
(14) |
| 2020 |
Jan
(22) |
Feb
(20) |
Mar
(36) |
Apr
(40) |
May
(52) |
Jun
(35) |
Jul
(21) |
Aug
(32) |
Sep
(71) |
Oct
(27) |
Nov
(11) |
Dec
(16) |
| 2021 |
Jan
(16) |
Feb
(21) |
Mar
(21) |
Apr
(27) |
May
(17) |
Jun
|
Jul
(2) |
Aug
(22) |
Sep
(23) |
Oct
(7) |
Nov
(11) |
Dec
(28) |
| 2022 |
Jan
(23) |
Feb
(18) |
Mar
(9) |
Apr
(15) |
May
(15) |
Jun
(7) |
Jul
(8) |
Aug
(15) |
Sep
(1) |
Oct
|
Nov
(11) |
Dec
(10) |
| 2023 |
Jan
(14) |
Feb
(10) |
Mar
(11) |
Apr
(13) |
May
(2) |
Jun
(30) |
Jul
(1) |
Aug
(15) |
Sep
(13) |
Oct
(3) |
Nov
(25) |
Dec
(5) |
| 2024 |
Jan
(3) |
Feb
(10) |
Mar
(9) |
Apr
|
May
(1) |
Jun
(15) |
Jul
(7) |
Aug
(10) |
Sep
(3) |
Oct
(8) |
Nov
(6) |
Dec
(15) |
| 2025 |
Jan
(3) |
Feb
(1) |
Mar
(7) |
Apr
(5) |
May
(13) |
Jun
(16) |
Jul
(1) |
Aug
(17) |
Sep
|
Oct
(1) |
Nov
(11) |
Dec
|
|
From: Michael K. <mic...@ip...> - 2024-02-23 03:13:37
|
Whoops I was wrong. It doesn’t seem that we’re generating two certs rather we are just adding multiple domains to the same cert. The commands we use are (after adding the DNS entries): acme-client --issue --dns dns_acmedns -d <access ID>.myportal.tel -d <access ID>.ipcaccess.net acme-client --deploy --deploy-hook astlinux -d <access ID>.myportal.tel -d <access ID>.ipcaccess.net I think we will just leave it to see if it happens again. Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Friday, 23 February 2024 at 8:50 am To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] Asterisk appeared to crash after ACME deploy > 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...@lo...> 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 <mic...@ip...> 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 >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2024-02-22 21:50:31
|
> 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...@lo...> 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 <mic...@ip...> 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 >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2024-02-22 21:48:19
|
Yes good question but we certainly need multiple certs. We basically have a domain for the customer portal and a domain for management access which may not be the same address e.g. management via VPN. Thanks I will add this to the next release. Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Friday, 23 February 2024 at 8:45 am To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] Asterisk appeared to crash after ACME deploy A 60 second delay should do it, but I would question why you need two certs. In my case I was testing something and switched to using only one cert. Lonnie > On Feb 22, 2024, at 3:41 PM, Michael Knill <mic...@ip...> wrote: > > Ah interesting I do have two certs. Should I add a delay before the second deploy script? > > Regards > Michael Knill > > > From: Lonnie Abelbeck <li...@lo...> > Date: Friday, 23 February 2024 at 8:38 am > To: AstLinux Users Mailing List <ast...@li...> > Subject: Re: [Astlinux-users] Asterisk appeared to crash after ACME deploy > > 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 <mic...@ip...> 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 > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2024-02-22 21:45:26
|
A 60 second delay should do it, but I would question why you need two certs. In my case I was testing something and switched to using only one cert. Lonnie > On Feb 22, 2024, at 3:41 PM, Michael Knill <mic...@ip...> wrote: > > Ah interesting I do have two certs. Should I add a delay before the second deploy script? > > Regards > Michael Knill > > > From: Lonnie Abelbeck <li...@lo...> > Date: Friday, 23 February 2024 at 8:38 am > To: AstLinux Users Mailing List <ast...@li...> > Subject: Re: [Astlinux-users] Asterisk appeared to crash after ACME deploy > > 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 <mic...@ip...> 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 > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2024-02-22 21:41:30
|
Ah interesting I do have two certs. Should I add a delay before the second deploy script? Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Friday, 23 February 2024 at 8:38 am To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] Asterisk appeared to crash after ACME deploy 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 <mic...@ip...> 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 > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2024-02-22 21:37:36
|
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 <mic...@ip...> 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 > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2024-02-22 20:55:15
|
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 |
|
From: Michael K. <li...@mk...> - 2024-02-16 12:34:09
|
> Am 15.02.2024 um 15:23 schrieb Lonnie Abelbeck <li...@lo...>: > > Hi Group, > > With the VMware transition from perpetual licensing to new subscription offerings, and the end of free ESXi [1], > > should the VMware support in AstLinux change in any way? > > If you are currently using AstLinux in a VMware instance, will you continue to do so for the future or switch to some other hypervisor? > > There is some extra bloat added to the AstLinux VM ISO to support VMware (ex. open-vm-tools) > > I'm curious how AstLinux VM users are reacting to the VMware transition. > > Lonnie > > [1] https://kb.vmware.com/s/article/2107518 I still have a few bigger customers using VMWare, and they want to stay with it, at least as a mid-term plan. Michael http://www.mksolutions.info |
|
From: Lonnie A. <li...@lo...> - 2024-02-15 14:23:42
|
Hi Group, With the VMware transition from perpetual licensing to new subscription offerings, and the end of free ESXi [1], should the VMware support in AstLinux change in any way? If you are currently using AstLinux in a VMware instance, will you continue to do so for the future or switch to some other hypervisor? There is some extra bloat added to the AstLinux VM ISO to support VMware (ex. open-vm-tools) I'm curious how AstLinux VM users are reacting to the VMware transition. Lonnie [1] https://kb.vmware.com/s/article/2107518 |
|
From: Lonnie A. <li...@lo...> - 2024-01-31 15:56:42
|
Announcing AstLinux Release: 1.5.3 More Info: AstLinux Project https://www.astlinux-project.org/ AstLinux 1.5.3 Highlights: * Asterisk Versions: 16.30.0, 18.20.2, 20.5.2 * Linux Kernel 5.10.205, security and bug fixes * RUNNIX, version bump to runnix-0.6.17 * i40e, enable the Intel 10-Gigabit Ethernet Network Driver (Intel X710/XL710/XXV710/X722 support) * r8125, version 9.012.04, Realtek RTL8125 2.5-Gigabit Ethernet Network Driver * OpenSSH, version bump to 8.4p1, security fixes: CVE-2021-28041, CVE-2021-41617, CVE-2023-48795, CVE-2023-51385 * libcurl (curl) version bump to 8.5.0, security fixes: CVE-2023-46218, CVE-2023-46219 * libxml2, version bump to 2.11.6 * chrony, version bump to 4.5 * php, version 7.2.34, add security fix: CVE-2023-3823 * sngrep, version bump to 1.8.0 * sqlite, version bump to 3.44.2 * udev (eudev), version bump to 3.2.14 * unbound, version bump to 1.19.0 * ca-certificates, update trusted root certificates 2023-12-12 * Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x "Legacy" version, built --without-pjproject and --without-dahdi * Package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.3/docs/ChangeLog.txt All users are encouraged to upgrade, read the ChangeLog for the details. AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2024-01-06 18:41:12
|
Announcing AstLinux Pre-Release: astlinux-1.5-5979-ce0ecf AstLinux Project -> Development https://www.astlinux-project.org/dev.html ** The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Linux Kernel 5.10.205 (version bump), security and bug fixes -- i40e, enable the Intel 10-Gigabit Ethernet Network Driver (Intel X710/XL710/XXV710/X722 support) -- r8125, version 9.012.04, Realtek RTL8125 2.5-Gigabit Ethernet Network Driver -- OpenSSH, version bump to 8.4p1, security fixes: CVE-2021-28041, CVE-2021-41617, CVE-2023-48795, CVE-2023-51385 -- libcurl (curl) version bump to 8.5.0, security fixes: CVE-2023-46218, CVE-2023-46219 -- php, version 7.2.34, add security fix: CVE-2023-3823 -- chrony, version bump to 4.5 -- empty, version bump to 0.6.23c Note: Minor tweaks to any scripts using 'empty' may be needed. Example: empty -w "$expect" -> empty -w "$expect" '' -- sngrep, version bump to 1.8.0 -- sqlite, version bump to 3.44.2 -- unbound, version bump to 1.19.0 -- ca-certificates, update trusted root certificates 2023-12-12 -- Asterisk 16.30.0 ('16se' no change) Last Asterisk 16.x "Legacy" version, built --without-pjproject and --without-dahdi -- Asterisk 18.20.2 (version bump) and 20.5.2 (version bump) Built --with-pjproject and --with-dahdi -- DAHDI, dahdi-linux 3.2.0 (no change) and dahdi-tools 3.2.0 (no change) Add build fix to include "astribank" utilities -- Added rc.conf variable DAHDI_DISABLE, disable DAHDI when set to "yes", defaults to "no". -- Complete Pre-Release ChangeLog: https://astlinux-project.org/beta/astlinux-changelog/ChangeLog.txt The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html AstLinux Team |
|
From: Michael K. <mic...@ip...> - 2024-01-01 01:14:32
|
Hi Group Happy New Year to all. Here’s a weird thing! I had Asterisk crash at EXACTLY the same time and date (23:00:40 on December 30, 2023) on two separate systems! They are both Qotom Q190G4U. At 23:00 Cron runs the ACME Update script. Im not too concerned but certainly weird. Regards Michael Knill |
|
From: Lonnie A. <li...@lo...> - 2023-12-11 14:34:19
|
I looked at the code, in function apply_rules() [1] of the dyndns-host-open-helper. Yes, as you describe, if any of the DNS lookups fail (via the iptables call) the DYNDNS_CHAIN falls-back to any valid pre-existing rules. DNS is known for issues, so much so T-shirts were designed [2], we felt intermittent loss of DNS should not effect the dyndns-host-open plugin functionality. I'm not sure if we want to change the logic to support the special case where DNS is working but one (of several defined) hostnames is failing. In Michael's example, his new configuration error may not have been caught as soon as it was if the failing hostname was ignored. Lonnie [1] https://github.com/astlinux-project/astlinux/blob/84746e877f445144b6e2de02281813d55c0bd1de/package/arnofw/aif/share/arno-iptables-firewall/plugins/dyndns-host-open-helper#L94 [2] https://www.jeffgeerling.com/blog/2022/it-was-dns-t-shirt-on-redshirtjeffcom > On Dec 11, 2023, at 12:18 AM, Michael Knill <mic...@ip...> wrote: > > Ah I have found the problem. > We deleted one of the dyndns-host-open domains from our DNS but not from Astlinux which meant that ALL domains in dyndns-host-open.conf failed for that box? > I must admit that this is not particularly optimal. Is this standard behaviour? > > Regards > Michael Knill > > > From: Michael Keuter <li...@mk...> > Date: Thursday, 7 December 2023 at 7:37 pm > To: AstLinux Users Mailing List <ast...@li...> > Subject: Re: [Astlinux-users] dyndns-host-open plugin update time > > The default time is 900 seconds. You can edit it in the config file. > Make sure it is enabled (at the top). > > Sent from a mobile device. > > Michael Keuter > > > Am 07.12.2023 um 06:25 schrieb Michael Knill <mic...@ip...>: > > > Hi Group > > Just wondering how long it takes the dyndns-host-open plugin to update. I have been waiting for well over a day now and some sites can see the two servers with nslookup but have not updated iptables. > > Any ideas? > > Regards > > Michael Knill > Managing Director > > D: +61 2 6189 1360 > P: +61 2 6140 4656 > E: mic...@ip... > W: ipcsolutions.com.au > > > <image001.png> > Smarter Business Communications > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Dan R. <da...@ry...> - 2023-12-11 13:50:50
|
I may have seen something similar: If I provide dyndns-host-open with a SUBDOMAIN to the DOMAIN that's entered under the Network tab, IPTables doesn't find that subdomain IP address. See the log output below. To be clear, that SUBDOMAIN is _different_ than the HOSTNAME provided under the Network tab and there are no hosts with that DOMAIN listed under "DNS Forwarder Hosts." I found a simple work-around but thought this might be worth mentioning in the context of Michael Knill's observations. Log: user.info firewall: dyndns-host-open: /usr/sbin/iptables: (2) iptables v1.8.4 (legacy): host/network `subdomain.domain.com' not found Try `iptables -h' or 'iptables --help' for more information. Dan On Monday, 11-12-2023 at 1:18 Michael Knill wrote: Ah I have found the problem. We deleted one of the dyndns-host-open domains from our DNS but not from Astlinux which meant that ALL domains in dyndns-host-open.conf failed for that box? I must admit that this is not particularly optimal. Is this standard behaviour? Regards Michael Knill From: Michael Keuter * Date: Thursday, 7 December 2023 at 7:37 pm To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] dyndns-host-open plugin update time The default time is 900 seconds. You can edit it in the config file. Make sure it is enabled (at the top). Sent from a mobile device. Michael Keuter Am 07.12.2023 um 06:25 schrieb Michael Knill : Hi Group Just wondering how long it takes the dyndns-host-open plugin to update. I have been waiting for well over a day now and some sites can see the two servers with nslookup but have not updated iptables. Any ideas? Regards Michael Knill Managing Director D: +61 2 6189 1360 [1] P: +61 2 6140 4656 [2] E: mic...@ip... W: ipcsolutions.com.au [3] _Smarter Business Communications_ _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... Links: ------ [1] tel:+61261891360 [2] tel:+61261404656 [3] https://ipcsolutions.com.au/ |
|
From: Michael K. <mic...@ip...> - 2023-12-11 06:18:40
|
Ah I have found the problem. We deleted one of the dyndns-host-open domains from our DNS but not from Astlinux which meant that ALL domains in dyndns-host-open.conf failed for that box? I must admit that this is not particularly optimal. Is this standard behaviour? Regards Michael Knill From: Michael Keuter <li...@mk...> Date: Thursday, 7 December 2023 at 7:37 pm To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] dyndns-host-open plugin update time The default time is 900 seconds. You can edit it in the config file. Make sure it is enabled (at the top). Sent from a mobile device. Michael Keuter Am 07.12.2023 um 06:25 schrieb Michael Knill <mic...@ip...>: Hi Group Just wondering how long it takes the dyndns-host-open plugin to update. I have been waiting for well over a day now and some sites can see the two servers with nslookup but have not updated iptables. Any ideas? Regards Michael Knill Managing Director D: +61 2 6189 1360<tel:+61261891360> P: +61 2 6140 4656<tel:+61261404656> E: mic...@ip...<mailto:mic...@ip...> W: ipcsolutions.com.au<https://ipcsolutions.com.au/> <image001.png> Smarter Business Communications _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <li...@mk...> - 2023-12-07 08:37:19
|
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">The default time is 900 seconds. You can edit it in the config file.<div>Make sure it is enabled (at the top).<br><br><div dir="ltr">Sent from a mobile device.<div><br></div><div>Michael Keuter</div></div><div dir="ltr"><br><blockquote type="cite">Am 07.12.2023 um 06:25 schrieb Michael Knill <mic...@ip...>:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style>@font-face { font-family: "Cambria Math"; }
@font-face { font-family: Calibri; }
p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0cm; font-size: 11pt; font-family: Calibri, sans-serif; }
span.EmailStyle17 { font-family: Calibri, sans-serif; color: windowtext; }
.MsoChpDefault { font-family: Calibri, sans-serif; }
@page WordSection1 { size: 612pt 792pt; margin: 72pt; }
div.WordSection1 { page: WordSection1; }</style>
<div class="WordSection1">
<p class="MsoNormal">Hi Group<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Just wondering how long it takes the dyndns-host-open plugin to update. I have been waiting for well over a day now and some sites can see the two servers with nslookup but have not updated iptables.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Any ideas?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB">Regards</span><span style="font-size:12.0pt;color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"> </span><span style="font-size:12.0pt;color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB">Michael Knill</span></b><span style="font-size:12.0pt;color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB">Managing Director</span><span style="font-size:12.0pt;color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"> </span><span style="font-size:12.0pt;color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB">D: <a href="tel:+61261891360"><span style="color:#0078D7">+61 2 6189 1360</span></a></span><span style="font-size:12.0pt;color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB">P: <a href="tel:+61261404656"><span style="color:#0078D7">+61 2 6140 4656</span></a></span><span style="font-size:12.0pt;color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB">E: </span><span style="font-size:12.0pt;color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"><a href="mailto:mic...@ip..." title="mailto:mic...@ip..."><span style="font-size:11.0pt;color:#0078D7">mic...@ip...</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB">W: </span><span style="font-size:12.0pt;color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"><a href="https://ipcsolutions.com.au/" title="https://ipcsolutions.com.au/"><span style="font-size:11.0pt;color:#0078D7">ipcsolutions.com.au</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:5.0pt;color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"> </span><span style="font-size:12.0pt;color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"> <div><image001.png></div></span><span style="font-size:12.0pt;color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span lang="EN-GB" style="color:black;mso-ligatures:none;mso-fareast-language:EN-GB">Smarter Business Communications</span></i><span style="font-size:12.0pt;color:#212121;mso-ligatures:none;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<span>_______________________________________________</span><br><span>Astlinux-users mailing list</span><br><span>Ast...@li...</span><br><span>https://lists.sourceforge.net/lists/listinfo/astlinux-users</span><br><span></span><br><span>Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....</span></div></blockquote></div></body></html> |
|
From: Michael K. <mic...@ip...> - 2023-12-07 05:23:50
|
Hi Group Just wondering how long it takes the dyndns-host-open plugin to update. I have been waiting for well over a day now and some sites can see the two servers with nslookup but have not updated iptables. Any ideas? Regards Michael Knill Managing Director D: +61 2 6189 1360<tel:+61261891360> P: +61 2 6140 4656<tel:+61261404656> E: mic...@ip...<mailto:mic...@ip...> W: ipcsolutions.com.au<https://ipcsolutions.com.au/> [Icon Description automatically generated] Smarter Business Communications |
|
From: Fernando F. <ffu...@da...> - 2023-11-20 20:28:10
|
I have been a long-term GL.iNet user, and is rock solid. -- Fernando Fuentes ffu...@tx... http://www.txweather.org On Thu, Nov 16, 2023, at 1:32 PM, Michael Knill wrote: > Thanks all for replying. Looks like it’s a go then. > > I will use the Brume 2 Aluminium as a gateway but have also considered using the Mango to provide network monitoring and remote access only. > You can also use a PoE to USB 5v splitter so you don’t even need a power supply. > > Such a nice solution. Send out a PoE switch, phones and gateway to a partner or directly to a customer preconfigured to VPN into their Astlinux system in the cloud for a plug and play solution. The solution provides monitoring of network connectivity and remote access to all devices. So much more than what a standard cloud provider can do. > > Thanks all. > > Regards > Michael Knill > > > *From: *Lonnie Abelbeck <li...@lo...> > *Date: *Thursday, 16 November 2023 at 11:44 pm > *To: *AstLinux Users Mailing List <ast...@li...> > *Subject: *Re: [Astlinux-users] GL.iNet. How good is it? > I have always heard good things about the GL.iNet products, but never personally tested one. > > Are you considering the older (inexpensive) Mango/Shadow or the newer Brume 2 gateway ? > > Their continued firmware support looks good. [1] > > GL.iNet embraced WireGuard early on, which was a perfect match for their lower-end CPUs. > > Lonnie > > [1] https://dl.gl-inet.com/ > > > > > On Nov 16, 2023, at 5:01 AM, Michael Keuter <li...@mk...> wrote: > > > > Hi Michael, > > > > I have a few of them privately as travelrouter (Creta + Beryl), and 2 of them at customers (Creta), but only for remote VPN use. > > I have tested them not with AstLinux yet. They are running stable, and they are based on OpenWRT (but an older version). > > > > Michael > > > > http://www.mksolutions.info > > > >> Am 16.11.2023 um 10:12 schrieb Michael Knill <mic...@ip...>: > >> > >> Hi All > >> I am looking to start using these as my telephony gateway VPN router device e.g. phones within a clients network using this gateway to connect via Wireguard VPN to the cloud Astlinux system. > >> It looks perfect and initial playing has been positive. You can even cloud manage it which is a bonus. > >> Just checking if anyone has had any experience with GL.iNet products and this is not too good to be true. > >> Regards > >> Michael Knill > > > > > > > > > > > > > > _______________________________________________ > > Astlinux-users mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Dr. P. V. <pv...@uo...> - 2023-11-18 00:45:55
|
Hi Lonnie, thanks for even more detailed advice. Looks like I should go path 3) and 3a). Regards, Peter On Fri, 2023-11-17 at 15:03 -0600, Lonnie Abelbeck wrote: > +1 what Michael said ... my thoughts. > > Given, currently using ast16: > > 1) If currently using chan_pjsip, migrate to ast18. > > 2) If currently using dahdi (ex. pcie telephony card), migrate to ast18. > > 3) Else next step, change the "ast16" to "ast16se", ex. > -- > Prefs -> System & Staff Tab Options: Repository URL: > https://mirror.astlinux-project.org/ast16se-firmware-1.x > -- > This should be quick and painless and will give you the latest security fixes > in the packages with 1.5.2. > > 3a) Consider migrating to "ast18" when you have time to research the > differences and testing. > > > Additionally, it is recommended any "ast13se" systems be migrated to at least > "ast16se". Relatively painless, but still requires some research and testing > as with any version change of Asterisk. > > > Lonnie > > > > > On Nov 17, 2023, at 12:21 PM, Dr. Peter Voigt <pv...@uo...> wrote: > > > > Hi Michael, > > > > thanks for feedback. I will try the upgrade to ast18 as soon as I've some > > time > > left necessary to deal with obviously arising error messages and required > > configuration changes. May be I'll have to contact the list again, if > > something > > goes wrong. > > > > > > On Fri, 2023-11-17 at 19:06 +0100, Michael Keuter wrote: > > > Hi Peter, > > > > > > it is just a matter of changing the repository URL (you must run a lower > > > version). > > > > > > I would suggest you choose ast18 cause Asterisk is EOL now. > > > 20 is not well tested yet, it runs fine for me though. > > > There was much changed between 16 and 18 (a few missing new config files > > > => > > > error messages.) > > > The originals are in "/stat/etc/asterisk/". > > > > > > > Am 17.11.2023 um 18:21 schrieb Dr. Peter Voigt <pv...@uo...>: > > > > > > > > I am currently on the ast16 branch and ask myself, if I should switch to > > > > ast16se > > > > or to one of the higher version branches ast18/ast20. > > > > > > > > And another question: Is upgrading just a matter of changing the > > > > repository > > > > URL > > > > according to > > > > https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version > > > > or will I have to adapt or re-create my Asterisk configuration? > > > > > > > > Regards, > > > > Peter > > > > > > > > > > > > On Thu, 2023-11-16 at 07:33 -0600, Lonnie Abelbeck wrote: > > > > > Announcing AstLinux Release: 1.5.2 > > > > > > > > > > More Info: AstLinux Project > > > > > https://www.astlinux-project.org/ > > > > > > > > > > Changes to supported firmware builds: > > > > > * Previous 'ast13se' and 'ast16' firmware branches are no longer > > > > > updated. > > > > > * New 'ast16se' firmware branch, Asterisk 16.x built --without- > > > > > pjproject > > > > > and - > > > > > -without-dahdi > > > > > * Previous 'ast18' firmware branch, Asterisk 18.x built --with- > > > > > pjproject > > > > > and - > > > > > -with-dahdi > > > > > * New 'ast20' firmware branch, Asterisk 20.x built --with-pjproject > > > > > and -- > > > > > with-dahdi > > > > > > > > > > AstLinux 1.5.2 Highlights: > > > > > * Asterisk Versions: 16.30.0, 18.20.0, 20.5.0 > > > > > > > > > > * Linux Kernel 5.10.197, security and bug fixes > > > > > * RUNNIX, version bump to runnix-0.6.16 > > > > > * OpenSSL, version bump to 1.1.1w, security fixes: CVE-2023-3446, CVE- > > > > > 2023- > > > > > 3817 > > > > > * libcurl (curl) version bump to 8.4.0, security fixes: CVE-2023- > > > > > 38039, > > > > > CVE- > > > > > 2023-38545, CVE-2023-38546 > > > > > * LibreTLS, version bump to 3.8.1 > > > > > * libpng, version bump to 1.6.40 > > > > > * libsodium, version bump to 1.0.19 > > > > > * libxml2, version bump to 2.11.5 > > > > > * chrony, version bump to 4.4 > > > > > * ne, version bump to 3.3.3 > > > > > * msmtp, version bump to 1.8.25 > > > > > * netsnmp, version bump to 5.9.4 > > > > > * pjsip version bump to 2.13.1 > > > > > * screen, version 4.9.1, security fix: CVE-2023-24626 > > > > > * sqlite, version bump to 3.43.2 > > > > > * sqliteodbc, version bump to 0.99991 > > > > > * tiff, version bump to 4.6.0 > > > > > * unbound, version bump to 1.18.0 > > > > > * unixodbc, version bump to 2.3.12 > > > > > * vnStat, version bump to 2.11 > > > > > * zabbix, version bump to 4.0.50 > > > > > * Asterisk '16se' (stable edition) version 16.30.0 is the last > > > > > Asterisk > > > > > 16.x > > > > > "Legacy" version, built --without-pjproject and --without-dahdi > > > > > * Package upgrades providing important security and bug fixes > > > > > > > > > > Full ChangeLog: > > > > > https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.2/docs/ChangeLog.txt > > > > > > > > > > All users are encouraged to upgrade, read the ChangeLog for the > > > > > details. > > > > > > > > > > AstLinux Team > > > > > > Michael > > > > > > http://www.mksolutions.info > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Astlinux-users mailing list > > > Ast...@li... > > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > > > Donations to support AstLinux are graciously accepted via PayPal to > > > pa...@kr.... > > > > > > _______________________________________________ > > Astlinux-users mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > > Donations to support AstLinux are graciously accepted via PayPal to > > pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2023-11-17 21:03:55
|
+1 what Michael said ... my thoughts. Given, currently using ast16: 1) If currently using chan_pjsip, migrate to ast18. 2) If currently using dahdi (ex. pcie telephony card), migrate to ast18. 3) Else next step, change the "ast16" to "ast16se", ex. -- Prefs -> System & Staff Tab Options: Repository URL: https://mirror.astlinux-project.org/ast16se-firmware-1.x -- This should be quick and painless and will give you the latest security fixes in the packages with 1.5.2. 3a) Consider migrating to "ast18" when you have time to research the differences and testing. Additionally, it is recommended any "ast13se" systems be migrated to at least "ast16se". Relatively painless, but still requires some research and testing as with any version change of Asterisk. Lonnie > On Nov 17, 2023, at 12:21 PM, Dr. Peter Voigt <pv...@uo...> wrote: > > Hi Michael, > > thanks for feedback. I will try the upgrade to ast18 as soon as I've some time > left necessary to deal with obviously arising error messages and required > configuration changes. May be I'll have to contact the list again, if something > goes wrong. > > > On Fri, 2023-11-17 at 19:06 +0100, Michael Keuter wrote: >> Hi Peter, >> >> it is just a matter of changing the repository URL (you must run a lower >> version). >> >> I would suggest you choose ast18 cause Asterisk is EOL now. >> 20 is not well tested yet, it runs fine for me though. >> There was much changed between 16 and 18 (a few missing new config files => >> error messages.) >> The originals are in "/stat/etc/asterisk/". >> >>> Am 17.11.2023 um 18:21 schrieb Dr. Peter Voigt <pv...@uo...>: >>> >>> I am currently on the ast16 branch and ask myself, if I should switch to >>> ast16se >>> or to one of the higher version branches ast18/ast20. >>> >>> And another question: Is upgrading just a matter of changing the repository >>> URL >>> according to >>> https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version >>> or will I have to adapt or re-create my Asterisk configuration? >>> >>> Regards, >>> Peter >>> >>> >>> On Thu, 2023-11-16 at 07:33 -0600, Lonnie Abelbeck wrote: >>>> Announcing AstLinux Release: 1.5.2 >>>> >>>> More Info: AstLinux Project >>>> https://www.astlinux-project.org/ >>>> >>>> Changes to supported firmware builds: >>>> * Previous 'ast13se' and 'ast16' firmware branches are no longer updated. >>>> * New 'ast16se' firmware branch, Asterisk 16.x built --without-pjproject >>>> and - >>>> -without-dahdi >>>> * Previous 'ast18' firmware branch, Asterisk 18.x built --with-pjproject >>>> and - >>>> -with-dahdi >>>> * New 'ast20' firmware branch, Asterisk 20.x built --with-pjproject and -- >>>> with-dahdi >>>> >>>> AstLinux 1.5.2 Highlights: >>>> * Asterisk Versions: 16.30.0, 18.20.0, 20.5.0 >>>> >>>> * Linux Kernel 5.10.197, security and bug fixes >>>> * RUNNIX, version bump to runnix-0.6.16 >>>> * OpenSSL, version bump to 1.1.1w, security fixes: CVE-2023-3446, CVE- >>>> 2023- >>>> 3817 >>>> * libcurl (curl) version bump to 8.4.0, security fixes: CVE-2023-38039, >>>> CVE- >>>> 2023-38545, CVE-2023-38546 >>>> * LibreTLS, version bump to 3.8.1 >>>> * libpng, version bump to 1.6.40 >>>> * libsodium, version bump to 1.0.19 >>>> * libxml2, version bump to 2.11.5 >>>> * chrony, version bump to 4.4 >>>> * ne, version bump to 3.3.3 >>>> * msmtp, version bump to 1.8.25 >>>> * netsnmp, version bump to 5.9.4 >>>> * pjsip version bump to 2.13.1 >>>> * screen, version 4.9.1, security fix: CVE-2023-24626 >>>> * sqlite, version bump to 3.43.2 >>>> * sqliteodbc, version bump to 0.99991 >>>> * tiff, version bump to 4.6.0 >>>> * unbound, version bump to 1.18.0 >>>> * unixodbc, version bump to 2.3.12 >>>> * vnStat, version bump to 2.11 >>>> * zabbix, version bump to 4.0.50 >>>> * Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk >>>> 16.x >>>> "Legacy" version, built --without-pjproject and --without-dahdi >>>> * Package upgrades providing important security and bug fixes >>>> >>>> Full ChangeLog: >>>> https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.2/docs/ChangeLog.txt >>>> >>>> All users are encouraged to upgrade, read the ChangeLog for the details. >>>> >>>> AstLinux Team >> >> Michael >> >> http://www.mksolutions.info >> >> >> >> >> >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to >> pa...@kr.... > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Dr. P. V. <pv...@uo...> - 2023-11-17 18:21:42
|
Hi Michael, thanks for feedback. I will try the upgrade to ast18 as soon as I've some time left necessary to deal with obviously arising error messages and required configuration changes. May be I'll have to contact the list again, if something goes wrong. On Fri, 2023-11-17 at 19:06 +0100, Michael Keuter wrote: > Hi Peter, > > it is just a matter of changing the repository URL (you must run a lower > version). > > I would suggest you choose ast18 cause Asterisk is EOL now. > 20 is not well tested yet, it runs fine for me though. > There was much changed between 16 and 18 (a few missing new config files => > error messages.) > The originals are in "/stat/etc/asterisk/". > > > Am 17.11.2023 um 18:21 schrieb Dr. Peter Voigt <pv...@uo...>: > > > > I am currently on the ast16 branch and ask myself, if I should switch to > > ast16se > > or to one of the higher version branches ast18/ast20. > > > > And another question: Is upgrading just a matter of changing the repository > > URL > > according to > > https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version > > or will I have to adapt or re-create my Asterisk configuration? > > > > Regards, > > Peter > > > > > > On Thu, 2023-11-16 at 07:33 -0600, Lonnie Abelbeck wrote: > > > Announcing AstLinux Release: 1.5.2 > > > > > > More Info: AstLinux Project > > > https://www.astlinux-project.org/ > > > > > > Changes to supported firmware builds: > > > * Previous 'ast13se' and 'ast16' firmware branches are no longer updated. > > > * New 'ast16se' firmware branch, Asterisk 16.x built --without-pjproject > > > and - > > > -without-dahdi > > > * Previous 'ast18' firmware branch, Asterisk 18.x built --with-pjproject > > > and - > > > -with-dahdi > > > * New 'ast20' firmware branch, Asterisk 20.x built --with-pjproject and -- > > > with-dahdi > > > > > > AstLinux 1.5.2 Highlights: > > > * Asterisk Versions: 16.30.0, 18.20.0, 20.5.0 > > > > > > * Linux Kernel 5.10.197, security and bug fixes > > > * RUNNIX, version bump to runnix-0.6.16 > > > * OpenSSL, version bump to 1.1.1w, security fixes: CVE-2023-3446, CVE- > > > 2023- > > > 3817 > > > * libcurl (curl) version bump to 8.4.0, security fixes: CVE-2023-38039, > > > CVE- > > > 2023-38545, CVE-2023-38546 > > > * LibreTLS, version bump to 3.8.1 > > > * libpng, version bump to 1.6.40 > > > * libsodium, version bump to 1.0.19 > > > * libxml2, version bump to 2.11.5 > > > * chrony, version bump to 4.4 > > > * ne, version bump to 3.3.3 > > > * msmtp, version bump to 1.8.25 > > > * netsnmp, version bump to 5.9.4 > > > * pjsip version bump to 2.13.1 > > > * screen, version 4.9.1, security fix: CVE-2023-24626 > > > * sqlite, version bump to 3.43.2 > > > * sqliteodbc, version bump to 0.99991 > > > * tiff, version bump to 4.6.0 > > > * unbound, version bump to 1.18.0 > > > * unixodbc, version bump to 2.3.12 > > > * vnStat, version bump to 2.11 > > > * zabbix, version bump to 4.0.50 > > > * Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk > > > 16.x > > > "Legacy" version, built --without-pjproject and --without-dahdi > > > * Package upgrades providing important security and bug fixes > > > > > > Full ChangeLog: > > > https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.2/docs/ChangeLog.txt > > > > > > All users are encouraged to upgrade, read the ChangeLog for the details. > > > > > > AstLinux Team > > Michael > > http://www.mksolutions.info > > > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... |
|
From: Michael K. <li...@mk...> - 2023-11-17 18:13:37
|
Sorry. Michael http://www.mksolutions.info > Am 17.11.2023 um 19:06 schrieb Michael Keuter <li...@mk...>: > > Hi Peter, > > it is just a matter of changing the repository URL (you must run a lower version). > > I would suggest you choose ast18 cause Asterisk is EOL now. > 20 is not well tested yet, it runs fine for me though. > There was much changed between 16 and 18 (a few missing new config files => error messages.) I meant NOT much changed :-). > The originals are in "/stat/etc/asterisk/". > >> Am 17.11.2023 um 18:21 schrieb Dr. Peter Voigt <pv...@uo...>: >> >> I am currently on the ast16 branch and ask myself, if I should switch to ast16se >> or to one of the higher version branches ast18/ast20. >> >> And another question: Is upgrading just a matter of changing the repository URL >> according to >> https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version >> or will I have to adapt or re-create my Asterisk configuration? >> >> Regards, >> Peter >> >> >> On Thu, 2023-11-16 at 07:33 -0600, Lonnie Abelbeck wrote: >>> Announcing AstLinux Release: 1.5.2 >>> >>> More Info: AstLinux Project >>> https://www.astlinux-project.org/ >>> >>> Changes to supported firmware builds: >>> * Previous 'ast13se' and 'ast16' firmware branches are no longer updated. >>> * New 'ast16se' firmware branch, Asterisk 16.x built --without-pjproject and - >>> -without-dahdi >>> * Previous 'ast18' firmware branch, Asterisk 18.x built --with-pjproject and - >>> -with-dahdi >>> * New 'ast20' firmware branch, Asterisk 20.x built --with-pjproject and -- >>> with-dahdi >>> >>> AstLinux 1.5.2 Highlights: >>> * Asterisk Versions: 16.30.0, 18.20.0, 20.5.0 >>> >>> * Linux Kernel 5.10.197, security and bug fixes >>> * RUNNIX, version bump to runnix-0.6.16 >>> * OpenSSL, version bump to 1.1.1w, security fixes: CVE-2023-3446, CVE-2023- >>> 3817 >>> * libcurl (curl) version bump to 8.4.0, security fixes: CVE-2023-38039, CVE- >>> 2023-38545, CVE-2023-38546 >>> * LibreTLS, version bump to 3.8.1 >>> * libpng, version bump to 1.6.40 >>> * libsodium, version bump to 1.0.19 >>> * libxml2, version bump to 2.11.5 >>> * chrony, version bump to 4.4 >>> * ne, version bump to 3.3.3 >>> * msmtp, version bump to 1.8.25 >>> * netsnmp, version bump to 5.9.4 >>> * pjsip version bump to 2.13.1 >>> * screen, version 4.9.1, security fix: CVE-2023-24626 >>> * sqlite, version bump to 3.43.2 >>> * sqliteodbc, version bump to 0.99991 >>> * tiff, version bump to 4.6.0 >>> * unbound, version bump to 1.18.0 >>> * unixodbc, version bump to 2.3.12 >>> * vnStat, version bump to 2.11 >>> * zabbix, version bump to 4.0.50 >>> * Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x >>> "Legacy" version, built --without-pjproject and --without-dahdi >>> * Package upgrades providing important security and bug fixes >>> >>> Full ChangeLog: >>> https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.2/docs/ChangeLog.txt >>> >>> All users are encouraged to upgrade, read the ChangeLog for the details. >>> >>> AstLinux Team > > Michael > > http://www.mksolutions.info > > > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <li...@mk...> - 2023-11-17 18:12:37
|
Asterisk 16 is EOL now. Michael http://www.mksolutions.info > Am 17.11.2023 um 19:06 schrieb Michael Keuter <li...@mk...>: > > Hi Peter, > > it is just a matter of changing the repository URL (you must run a lower version). > > I would suggest you choose ast18 cause Asterisk is EOL now. > 20 is not well tested yet, it runs fine for me though. > There was much changed between 16 and 18 (a few missing new config files => error messages.) > The originals are in "/stat/etc/asterisk/". > >> Am 17.11.2023 um 18:21 schrieb Dr. Peter Voigt <pv...@uo...>: >> >> I am currently on the ast16 branch and ask myself, if I should switch to ast16se >> or to one of the higher version branches ast18/ast20. >> >> And another question: Is upgrading just a matter of changing the repository URL >> according to >> https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version >> or will I have to adapt or re-create my Asterisk configuration? >> >> Regards, >> Peter >> >> >> On Thu, 2023-11-16 at 07:33 -0600, Lonnie Abelbeck wrote: >>> Announcing AstLinux Release: 1.5.2 >>> >>> More Info: AstLinux Project >>> https://www.astlinux-project.org/ >>> >>> Changes to supported firmware builds: >>> * Previous 'ast13se' and 'ast16' firmware branches are no longer updated. >>> * New 'ast16se' firmware branch, Asterisk 16.x built --without-pjproject and - >>> -without-dahdi >>> * Previous 'ast18' firmware branch, Asterisk 18.x built --with-pjproject and - >>> -with-dahdi >>> * New 'ast20' firmware branch, Asterisk 20.x built --with-pjproject and -- >>> with-dahdi >>> >>> AstLinux 1.5.2 Highlights: >>> * Asterisk Versions: 16.30.0, 18.20.0, 20.5.0 >>> >>> * Linux Kernel 5.10.197, security and bug fixes >>> * RUNNIX, version bump to runnix-0.6.16 >>> * OpenSSL, version bump to 1.1.1w, security fixes: CVE-2023-3446, CVE-2023- >>> 3817 >>> * libcurl (curl) version bump to 8.4.0, security fixes: CVE-2023-38039, CVE- >>> 2023-38545, CVE-2023-38546 >>> * LibreTLS, version bump to 3.8.1 >>> * libpng, version bump to 1.6.40 >>> * libsodium, version bump to 1.0.19 >>> * libxml2, version bump to 2.11.5 >>> * chrony, version bump to 4.4 >>> * ne, version bump to 3.3.3 >>> * msmtp, version bump to 1.8.25 >>> * netsnmp, version bump to 5.9.4 >>> * pjsip version bump to 2.13.1 >>> * screen, version 4.9.1, security fix: CVE-2023-24626 >>> * sqlite, version bump to 3.43.2 >>> * sqliteodbc, version bump to 0.99991 >>> * tiff, version bump to 4.6.0 >>> * unbound, version bump to 1.18.0 >>> * unixodbc, version bump to 2.3.12 >>> * vnStat, version bump to 2.11 >>> * zabbix, version bump to 4.0.50 >>> * Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x >>> "Legacy" version, built --without-pjproject and --without-dahdi >>> * Package upgrades providing important security and bug fixes >>> >>> Full ChangeLog: >>> https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.2/docs/ChangeLog.txt >>> >>> All users are encouraged to upgrade, read the ChangeLog for the details. >>> >>> AstLinux Team > > Michael > > http://www.mksolutions.info > > > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <li...@mk...> - 2023-11-17 18:06:59
|
Hi Peter, it is just a matter of changing the repository URL (you must run a lower version). I would suggest you choose ast18 cause Asterisk is EOL now. 20 is not well tested yet, it runs fine for me though. There was much changed between 16 and 18 (a few missing new config files => error messages.) The originals are in "/stat/etc/asterisk/". > Am 17.11.2023 um 18:21 schrieb Dr. Peter Voigt <pv...@uo...>: > > I am currently on the ast16 branch and ask myself, if I should switch to ast16se > or to one of the higher version branches ast18/ast20. > > And another question: Is upgrading just a matter of changing the repository URL > according to > https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version > or will I have to adapt or re-create my Asterisk configuration? > > Regards, > Peter > > > On Thu, 2023-11-16 at 07:33 -0600, Lonnie Abelbeck wrote: >> Announcing AstLinux Release: 1.5.2 >> >> More Info: AstLinux Project >> https://www.astlinux-project.org/ >> >> Changes to supported firmware builds: >> * Previous 'ast13se' and 'ast16' firmware branches are no longer updated. >> * New 'ast16se' firmware branch, Asterisk 16.x built --without-pjproject and - >> -without-dahdi >> * Previous 'ast18' firmware branch, Asterisk 18.x built --with-pjproject and - >> -with-dahdi >> * New 'ast20' firmware branch, Asterisk 20.x built --with-pjproject and -- >> with-dahdi >> >> AstLinux 1.5.2 Highlights: >> * Asterisk Versions: 16.30.0, 18.20.0, 20.5.0 >> >> * Linux Kernel 5.10.197, security and bug fixes >> * RUNNIX, version bump to runnix-0.6.16 >> * OpenSSL, version bump to 1.1.1w, security fixes: CVE-2023-3446, CVE-2023- >> 3817 >> * libcurl (curl) version bump to 8.4.0, security fixes: CVE-2023-38039, CVE- >> 2023-38545, CVE-2023-38546 >> * LibreTLS, version bump to 3.8.1 >> * libpng, version bump to 1.6.40 >> * libsodium, version bump to 1.0.19 >> * libxml2, version bump to 2.11.5 >> * chrony, version bump to 4.4 >> * ne, version bump to 3.3.3 >> * msmtp, version bump to 1.8.25 >> * netsnmp, version bump to 5.9.4 >> * pjsip version bump to 2.13.1 >> * screen, version 4.9.1, security fix: CVE-2023-24626 >> * sqlite, version bump to 3.43.2 >> * sqliteodbc, version bump to 0.99991 >> * tiff, version bump to 4.6.0 >> * unbound, version bump to 1.18.0 >> * unixodbc, version bump to 2.3.12 >> * vnStat, version bump to 2.11 >> * zabbix, version bump to 4.0.50 >> * Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x >> "Legacy" version, built --without-pjproject and --without-dahdi >> * Package upgrades providing important security and bug fixes >> >> Full ChangeLog: >> https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.2/docs/ChangeLog.txt >> >> All users are encouraged to upgrade, read the ChangeLog for the details. >> >> AstLinux Team Michael http://www.mksolutions.info |
|
From: Dr. P. V. <pv...@uo...> - 2023-11-17 17:45:17
|
I am currently on the ast16 branch and ask myself, if I should switch to ast16se or to one of the higher version branches ast18/ast20. And another question: Is upgrading just a matter of changing the repository URL according to https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version or will I have to adapt or re-create my Asterisk configuration? Regards, Peter On Thu, 2023-11-16 at 07:33 -0600, Lonnie Abelbeck wrote: > Announcing AstLinux Release: 1.5.2 > > More Info: AstLinux Project > https://www.astlinux-project.org/ > > Changes to supported firmware builds: > * Previous 'ast13se' and 'ast16' firmware branches are no longer updated. > * New 'ast16se' firmware branch, Asterisk 16.x built --without-pjproject and - > -without-dahdi > * Previous 'ast18' firmware branch, Asterisk 18.x built --with-pjproject and - > -with-dahdi > * New 'ast20' firmware branch, Asterisk 20.x built --with-pjproject and -- > with-dahdi > > AstLinux 1.5.2 Highlights: > * Asterisk Versions: 16.30.0, 18.20.0, 20.5.0 > > * Linux Kernel 5.10.197, security and bug fixes > * RUNNIX, version bump to runnix-0.6.16 > * OpenSSL, version bump to 1.1.1w, security fixes: CVE-2023-3446, CVE-2023- > 3817 > * libcurl (curl) version bump to 8.4.0, security fixes: CVE-2023-38039, CVE- > 2023-38545, CVE-2023-38546 > * LibreTLS, version bump to 3.8.1 > * libpng, version bump to 1.6.40 > * libsodium, version bump to 1.0.19 > * libxml2, version bump to 2.11.5 > * chrony, version bump to 4.4 > * ne, version bump to 3.3.3 > * msmtp, version bump to 1.8.25 > * netsnmp, version bump to 5.9.4 > * pjsip version bump to 2.13.1 > * screen, version 4.9.1, security fix: CVE-2023-24626 > * sqlite, version bump to 3.43.2 > * sqliteodbc, version bump to 0.99991 > * tiff, version bump to 4.6.0 > * unbound, version bump to 1.18.0 > * unixodbc, version bump to 2.3.12 > * vnStat, version bump to 2.11 > * zabbix, version bump to 4.0.50 > * Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x > "Legacy" version, built --without-pjproject and --without-dahdi > * Package upgrades providing important security and bug fixes > > Full ChangeLog: > https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.2/docs/ChangeLog.txt > > All users are encouraged to upgrade, read the ChangeLog for the details. > > AstLinux Team > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... |
63 messages has been excluded from this view by a project administrator.
