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
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dan R. <da...@ry...> - 2020-01-23 22:17:50
|
Hi Michael,Thanks for the reply.I guess my question is really how best to routinely run a SIP PCAP on all incoming/outgoing calls, for later analysis if necessary. I have a provider that offers this and have found it useful for troublesooting isolated problems. I'm not worried about deleting SIP capture files. I'm just uncertain how to create them.Dan -------- Original message --------From: Michael Knill <mic...@ip...> Date: 1/23/20 2:56 PM (GMT-05:00) To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] Regular Use of sngrep Well I'm obviously ignorant of the tools available in Astlinux and I really wish I knew about this one earlier after I tried it. Couldn't you just run it to do a PCAP capture only from a specific peer, specifying limits and rotating the calls after the limit is reached? You could then do analysis via Wireshark. My 2c worth. Regards Michael Knill From: Dan Ryson <da...@ry...> Reply to: AstLinux List <ast...@li...> Date: Friday, 24 January 2020 at 3:15 am To: AstLinux List <ast...@li...> Subject: [Astlinux-users] Regular Use of sngrep Greetings all! It occurs to me that I've only been using the powerful sngrep tool to troubleshooting repeatable problems, not prior intermittent problems that are much harder to reproduce and catch. Is there an AstLinux recommended best-practice for routinely running SIP packet capture to permit sngrep diagnosis of historic calls? Thanks in advance for your thoughts. Dan |
|
From: Michael K. <mic...@ip...> - 2020-01-23 19:56:32
|
Well I'm obviously ignorant of the tools available in Astlinux and I really wish I knew about this one earlier after I tried it. Couldn't you just run it to do a PCAP capture only from a specific peer, specifying limits and rotating the calls after the limit is reached? You could then do analysis via Wireshark. My 2c worth. Regards Michael Knill From: Dan Ryson <da...@ry...> Reply to: AstLinux List <ast...@li...> Date: Friday, 24 January 2020 at 3:15 am To: AstLinux List <ast...@li...> Subject: [Astlinux-users] Regular Use of sngrep Greetings all! It occurs to me that I've only been using the powerful sngrep tool to troubleshooting repeatable problems, not prior intermittent problems that are much harder to reproduce and catch. Is there an AstLinux recommended best-practice for routinely running SIP packet capture to permit sngrep diagnosis of historic calls? Thanks in advance for your thoughts. Dan |
|
From: Dan R. <da...@ry...> - 2020-01-23 16:15:11
|
Greetings all! It occurs to me that I've only been using the powerful sngrep tool to troubleshooting repeatable problems, not prior intermittent problems that are much harder to reproduce and catch. Is there an AstLinux recommended best-practice for routinely running SIP packet capture to permit sngrep diagnosis of historic calls? Thanks in advance for your thoughts. Dan |
|
From: Michael K. <mic...@ip...> - 2020-01-20 23:38:35
|
Thanks Michael
Yes Wireguard works well for this however it kills battery life if its on all the time.
Regards
Michael Knill
On 20/1/20, 10:57 pm, "Michael Keuter" <li...@mk...> wrote:
> Am 20.01.2020 um 01:46 schrieb Michael Knill <mic...@ip...>:
>
> Hmm bit of a pointless question as enabling TCP or TLS will override the Push service for incoming calls anyway.
> Not sure how I can secure a UDP signalling connection to Astlinux on a roaming device. Oh well.
>
> Regards
> Michael Knill
You only can secure an UDP SIP connection with a VPN.
> From: Michael Knill <mic...@ip...>
> Reply to: AstLinux List <ast...@li...>
> Date: Monday, 20 January 2020 at 11:38 am
> To: AstLinux List <ast...@li...>
> Subject: [Astlinux-users] TLS Certificate
>
> Hi Group
>
> Just a quick question.
> I'm looking at using the Bria Enterprise mobile client with Push Notification on Astlinux but I want to enable TLS with ‘Verify TLS Certificate’ enabled.
> I have wildcard certificates installed on my systems for HTTPS e.g. .pem. Should I be able to use these for SIP TLS as well?
> I guess I could always use the self signed Certificate and install on the phone (yuk).
>
> Regards
> Michael Knill
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...> - 2020-01-20 11:57:38
|
> Am 20.01.2020 um 01:46 schrieb Michael Knill <mic...@ip...>: > > Hmm bit of a pointless question as enabling TCP or TLS will override the Push service for incoming calls anyway. > Not sure how I can secure a UDP signalling connection to Astlinux on a roaming device. Oh well. > > Regards > Michael Knill You only can secure an UDP SIP connection with a VPN. > From: Michael Knill <mic...@ip...> > Reply to: AstLinux List <ast...@li...> > Date: Monday, 20 January 2020 at 11:38 am > To: AstLinux List <ast...@li...> > Subject: [Astlinux-users] TLS Certificate > > Hi Group > > Just a quick question. > I'm looking at using the Bria Enterprise mobile client with Push Notification on Astlinux but I want to enable TLS with ‘Verify TLS Certificate’ enabled. > I have wildcard certificates installed on my systems for HTTPS e.g. .pem. Should I be able to use these for SIP TLS as well? > I guess I could always use the self signed Certificate and install on the phone (yuk). > > Regards > Michael Knill Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2020-01-20 00:46:24
|
Hmm bit of a pointless question as enabling TCP or TLS will override the Push service for incoming calls anyway. Not sure how I can secure a UDP signalling connection to Astlinux on a roaming device. Oh well. Regards Michael Knill From: Michael Knill <mic...@ip...> Reply to: AstLinux List <ast...@li...> Date: Monday, 20 January 2020 at 11:38 am To: AstLinux List <ast...@li...> Subject: [Astlinux-users] TLS Certificate Hi Group Just a quick question. I'm looking at using the Bria Enterprise mobile client with Push Notification on Astlinux but I want to enable TLS with ‘Verify TLS Certificate’ enabled. I have wildcard certificates installed on my systems for HTTPS e.g. .pem. Should I be able to use these for SIP TLS as well? I guess I could always use the self signed Certificate and install on the phone (yuk). Regards Michael Knill |
|
From: Michael K. <mic...@ip...> - 2020-01-20 00:37:43
|
Hi Group Just a quick question. I'm looking at using the Bria Enterprise mobile client with Push Notification on Astlinux but I want to enable TLS with ‘Verify TLS Certificate’ enabled. I have wildcard certificates installed on my systems for HTTPS e.g. .pem. Should I be able to use these for SIP TLS as well? I guess I could always use the self signed Certificate and install on the phone (yuk). Regards Michael Knill |
|
From: Michael K. <mic...@ip...> - 2020-01-19 18:42:33
|
Thanks Lonnie. Private repo it is. Hmm good idea Michael. I think I will do that. Thanks. Regards Michael Knill From: Michael Keuter <li...@mk...> Reply to: AstLinux List <ast...@li...> Date: Monday, 20 January 2020 at 3:48 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Getting 'Firmware verification failed' on some boxes when I try to upgrade Am 19.01.2020 um 07:56 schrieb Michael Knill <mic...@ip...<mailto:mic...@ip...>>: Maybe one day! So any chance you would consider putting previous releases into their own subdirectory? E.g. current release is http://mirror.astlinux-project.org/ast13se-firmware-1.x/<board type> or specific version is http://mirror.astlinux-project.org/ast13se-firmware-1.x/<board type>/<version> If you would do it the other way round for your own repo: .../version/board-type/ then you could include the version number in your "Repository URL" in the Prefs and it would work as before. You would need a "board-type" folder structure for every release in that case. I wouldn't bother with my own repository if that was the case! Regards Michael Knill On 19/1/20, 9:48 am, "Lonnie Abelbeck" <li...@lo...<mailto:li...@lo...>> wrote: Hi Michael, I have been using a Private Repository ... I just copy in the upgrade files from the official Astlinux Repository. Ahh, OK ... simple enough. I was thinking you were somehow adding your "special sauce" to the official images to create custom images, which I did not know how you could do that without building images yourself. Lonnie On Jan 18, 2020, at 4:40 PM, Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote: Thanks guys I was not aware of that doco to convert to a vm board type. Excellent I will do this and then it should all work. Lonnie I have been using a Private Repository for years now and have never had a problem. The main reason for using it was purely to determine the 'Current' release for my systems and the ability to upgrade(or downgrade) to any version I want by appending the version directory to the repository URL. I just copy in the upgrade files from the official Astlinux Repository. I would be happy to use the Astlinux repository if I could do the above. Regards Michael Knill On 19/1/20, 1:36 am, "Lonnie Abelbeck" <li...@lo...<mailto:li...@lo...>> wrote: On Jan 18, 2020, at 6:06 AM, Michael Keuter <li...@mk...<mailto:li...@mk...>> wrote: Am 18.01.2020 um 01:15 schrieb Michael Knill <mic...@ip...<mailto:mic...@ip...>>: Hi group Strangely it appears that with all my genx86_64 systems, on multiple astlinux versions, I am unable to perform an upgrade from my private repository as it comes up with ‘Firmware verification failed’. genx86_vm and genx86_64-serial upgrades work fine. I have tried upgrading to both 1.3.6 and 1.3.7.1 and it does the same thing. I have downloaded it multiple times into the repository so I don't believe the sha1 file is corrupted. It does work however when I point the repository to http://mirror.astlinux-project.org/ast13se-firmware-1.x so this indicates that there must be something wrong with my repository and I cant for the life of me work out what. So my questions are: • Any ideas what this could be and what to try to fix it? • How do I show the board type for a system (before it was shown on login)? • Is there a way I can upgrade to a specific version using the Astlinux repository? • How can I move to a different board type e.g. all my genx86_64 systems are on vm’s so they really should be a genx86_vm board type? Sorry for the lots of questions. Thanks all. Regards Michael Knill Hi Michael, short answers to 3. + 4.: 3. it depends on the "ver" file in the repo folder which contains the (latest) version. E.g. "astlinux-1.3.7.1". 4. You can switch on the commandline between genx86_64 and genx86_64-vm (but not between serial and vga): https://doc.astlinux.org/devdoc:devdoc_switch_genx86_64_and_vm Michael +1 and for completeness I'll add this link: Create a Private Repository https://doc.astlinux-project.org/devdoc:devdoc_create_repository Michael (Knill), you mentioned you are not building your own images (yet), so that begs the question ... how are you generating custom images for your private repository ? Lonnie Michael http://www.mksolutions.info |
|
From: Michael K. <li...@mk...> - 2020-01-19 16:48:14
|
> Am 19.01.2020 um 07:56 schrieb Michael Knill <mic...@ip... <mailto:mic...@ip...>>: > > Maybe one day! > > So any chance you would consider putting previous releases into their own subdirectory? > E.g. current release is http://mirror.astlinux-project.org/ast13se-firmware-1.x <http://mirror.astlinux-project.org/ast13se-firmware-1.x>/<board type> or specific version is http://mirror.astlinux-project.org/ast13se-firmware-1.x <http://mirror.astlinux-project.org/ast13se-firmware-1.x>/<board type>/<version> If you would do it the other way round for your own repo: .../version/board-type/ then you could include the version number in your "Repository URL" in the Prefs and it would work as before. You would need a "board-type" folder structure for every release in that case. > I wouldn't bother with my own repository if that was the case! > > Regards > Michael Knill > > On 19/1/20, 9:48 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Hi Michael, > >> I have been using a Private Repository ... > >> I just copy in the upgrade files from the official Astlinux Repository. > > Ahh, OK ... simple enough. > > I was thinking you were somehow adding your "special sauce" to the official images to create custom images, which I did not know how you could do that without building images yourself. > > Lonnie > > > >> On Jan 18, 2020, at 4:40 PM, Michael Knill <mic...@ip...> wrote: >> >> Thanks guys >> >> I was not aware of that doco to convert to a vm board type. Excellent I will do this and then it should all work. >> >> Lonnie I have been using a Private Repository for years now and have never had a problem. The main reason for using it was purely to determine the 'Current' release for my systems and the ability to upgrade(or downgrade) to any version I want by appending the version directory to the repository URL. I just copy in the upgrade files from the official Astlinux Repository. >> I would be happy to use the Astlinux repository if I could do the above. >> >> Regards >> Michael Knill >> >> On 19/1/20, 1:36 am, "Lonnie Abelbeck" <li...@lo...> wrote: >> >> >> >>> On Jan 18, 2020, at 6:06 AM, Michael Keuter <li...@mk...> wrote: >>> >>> >>> >>>> Am 18.01.2020 um 01:15 schrieb Michael Knill <mic...@ip...>: >>>> >>>> Hi group >>>> >>>> Strangely it appears that with all my genx86_64 systems, on multiple astlinux versions, I am unable to perform an upgrade from my private repository as it comes up with ‘Firmware verification failed’. genx86_vm and genx86_64-serial upgrades work fine. >>>> >>>> I have tried upgrading to both 1.3.6 and 1.3.7.1 and it does the same thing. I have downloaded it multiple times into the repository so I don't believe the sha1 file is corrupted. >>>> It does work however when I point the repository to http://mirror.astlinux-project.org/ast13se-firmware-1.x so this indicates that there must be something wrong with my repository and I cant for the life of me work out what. >>>> >>>> So my questions are: >>>> • Any ideas what this could be and what to try to fix it? >>>> • How do I show the board type for a system (before it was shown on login)? >>>> • Is there a way I can upgrade to a specific version using the Astlinux repository? >>>> • How can I move to a different board type e.g. all my genx86_64 systems are on vm’s so they really should be a genx86_vm board type? >>>> >>>> Sorry for the lots of questions. Thanks all. >>>> >>>> Regards >>>> Michael Knill >>> >>> Hi Michael, >>> >>> short answers to 3. + 4.: >>> >>> 3. it depends on the "ver" file in the repo folder which contains the (latest) version. E.g. "astlinux-1.3.7.1". >>> >>> 4. You can switch on the commandline between genx86_64 and genx86_64-vm (but not between serial and vga): >>> >>> https://doc.astlinux.org/devdoc:devdoc_switch_genx86_64_and_vm >>> >>> >>> Michael >> >> +1 and for completeness I'll add this link: >> >> Create a Private Repository >> https://doc.astlinux-project.org/devdoc:devdoc_create_repository >> >> Michael (Knill), you mentioned you are not building your own images (yet), so that begs the question ... how are you generating custom images for your private repository ? >> >> Lonnie Michael http://www.mksolutions.info |
|
From: Lonnie A. <li...@lo...> - 2020-01-19 12:54:26
|
> On Jan 19, 2020, at 12:56 AM, Michael Knill <mic...@ip...> wrote: > > Maybe one day! > > So any chance you would consider putting previous releases into their own subdirectory? No, sorry. A private repo, as you do, is your best solution. Lonnie > E.g. current release is http://mirror.astlinux-project.org/ast13se-firmware-1.x/<board type> or specific version is http://mirror.astlinux-project.org/ast13se-firmware-1.x/<board type>/<version> > > I wouldn't bother with my own repository if that was the case! > > Regards > Michael Knill > > On 19/1/20, 9:48 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Hi Michael, > >> I have been using a Private Repository ... > >> I just copy in the upgrade files from the official Astlinux Repository. > > Ahh, OK ... simple enough. > > I was thinking you were somehow adding your "special sauce" to the official images to create custom images, which I did not know how you could do that without building images yourself. > > Lonnie > > > >> On Jan 18, 2020, at 4:40 PM, Michael Knill <mic...@ip...> wrote: >> >> Thanks guys >> >> I was not aware of that doco to convert to a vm board type. Excellent I will do this and then it should all work. >> >> Lonnie I have been using a Private Repository for years now and have never had a problem. The main reason for using it was purely to determine the 'Current' release for my systems and the ability to upgrade(or downgrade) to any version I want by appending the version directory to the repository URL. I just copy in the upgrade files from the official Astlinux Repository. >> I would be happy to use the Astlinux repository if I could do the above. >> >> Regards >> Michael Knill >> >> On 19/1/20, 1:36 am, "Lonnie Abelbeck" <li...@lo...> wrote: >> >> >> >>> On Jan 18, 2020, at 6:06 AM, Michael Keuter <li...@mk...> wrote: >>> >>> >>> >>>> Am 18.01.2020 um 01:15 schrieb Michael Knill <mic...@ip...>: >>>> >>>> Hi group >>>> >>>> Strangely it appears that with all my genx86_64 systems, on multiple astlinux versions, I am unable to perform an upgrade from my private repository as it comes up with ‘Firmware verification failed’. genx86_vm and genx86_64-serial upgrades work fine. >>>> >>>> I have tried upgrading to both 1.3.6 and 1.3.7.1 and it does the same thing. I have downloaded it multiple times into the repository so I don't believe the sha1 file is corrupted. >>>> It does work however when I point the repository to http://mirror.astlinux-project.org/ast13se-firmware-1.x so this indicates that there must be something wrong with my repository and I cant for the life of me work out what. >>>> >>>> So my questions are: >>>> • Any ideas what this could be and what to try to fix it? >>>> • How do I show the board type for a system (before it was shown on login)? >>>> • Is there a way I can upgrade to a specific version using the Astlinux repository? >>>> • How can I move to a different board type e.g. all my genx86_64 systems are on vm’s so they really should be a genx86_vm board type? >>>> >>>> Sorry for the lots of questions. Thanks all. >>>> >>>> Regards >>>> Michael Knill >>> >>> Hi Michael, >>> >>> short answers to 3. + 4.: >>> >>> 3. it depends on the "ver" file in the repo folder which contains the (latest) version. E.g. "astlinux-1.3.7.1". >>> >>> 4. You can switch on the commandline between genx86_64 and genx86_64-vm (but not between serial and vga): >>> >>> https://doc.astlinux.org/devdoc:devdoc_switch_genx86_64_and_vm >>> >>> >>> Michael >> >> +1 and for completeness I'll add this link: >> >> Create a Private Repository >> https://doc.astlinux-project.org/devdoc:devdoc_create_repository >> >> Michael (Knill), you mentioned you are not building your own images (yet), so that begs the question ... how are you generating custom images for your private repository ? >> >> Lonnie >> >> >> >> >> _______________________________________________ >> 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: Michael K. <mic...@ip...> - 2020-01-19 06:57:06
|
Maybe one day! So any chance you would consider putting previous releases into their own subdirectory? E.g. current release is http://mirror.astlinux-project.org/ast13se-firmware-1.x/<board type> or specific version is http://mirror.astlinux-project.org/ast13se-firmware-1.x/<board type>/<version> I wouldn't bother with my own repository if that was the case! Regards Michael Knill On 19/1/20, 9:48 am, "Lonnie Abelbeck" <li...@lo...> wrote: Hi Michael, > I have been using a Private Repository ... > I just copy in the upgrade files from the official Astlinux Repository. Ahh, OK ... simple enough. I was thinking you were somehow adding your "special sauce" to the official images to create custom images, which I did not know how you could do that without building images yourself. Lonnie > On Jan 18, 2020, at 4:40 PM, Michael Knill <mic...@ip...> wrote: > > Thanks guys > > I was not aware of that doco to convert to a vm board type. Excellent I will do this and then it should all work. > > Lonnie I have been using a Private Repository for years now and have never had a problem. The main reason for using it was purely to determine the 'Current' release for my systems and the ability to upgrade(or downgrade) to any version I want by appending the version directory to the repository URL. I just copy in the upgrade files from the official Astlinux Repository. > I would be happy to use the Astlinux repository if I could do the above. > > Regards > Michael Knill > > On 19/1/20, 1:36 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > > >> On Jan 18, 2020, at 6:06 AM, Michael Keuter <li...@mk...> wrote: >> >> >> >>> Am 18.01.2020 um 01:15 schrieb Michael Knill <mic...@ip...>: >>> >>> Hi group >>> >>> Strangely it appears that with all my genx86_64 systems, on multiple astlinux versions, I am unable to perform an upgrade from my private repository as it comes up with ‘Firmware verification failed’. genx86_vm and genx86_64-serial upgrades work fine. >>> >>> I have tried upgrading to both 1.3.6 and 1.3.7.1 and it does the same thing. I have downloaded it multiple times into the repository so I don't believe the sha1 file is corrupted. >>> It does work however when I point the repository to http://mirror.astlinux-project.org/ast13se-firmware-1.x so this indicates that there must be something wrong with my repository and I cant for the life of me work out what. >>> >>> So my questions are: >>> • Any ideas what this could be and what to try to fix it? >>> • How do I show the board type for a system (before it was shown on login)? >>> • Is there a way I can upgrade to a specific version using the Astlinux repository? >>> • How can I move to a different board type e.g. all my genx86_64 systems are on vm’s so they really should be a genx86_vm board type? >>> >>> Sorry for the lots of questions. Thanks all. >>> >>> Regards >>> Michael Knill >> >> Hi Michael, >> >> short answers to 3. + 4.: >> >> 3. it depends on the "ver" file in the repo folder which contains the (latest) version. E.g. "astlinux-1.3.7.1". >> >> 4. You can switch on the commandline between genx86_64 and genx86_64-vm (but not between serial and vga): >> >> https://doc.astlinux.org/devdoc:devdoc_switch_genx86_64_and_vm >> >> >> Michael > > +1 and for completeness I'll add this link: > > Create a Private Repository > https://doc.astlinux-project.org/devdoc:devdoc_create_repository > > Michael (Knill), you mentioned you are not building your own images (yet), so that begs the question ... how are you generating custom images for your private repository ? > > Lonnie > > > > > _______________________________________________ > 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...> - 2020-01-18 22:48:00
|
Hi Michael, > I have been using a Private Repository ... > I just copy in the upgrade files from the official Astlinux Repository. Ahh, OK ... simple enough. I was thinking you were somehow adding your "special sauce" to the official images to create custom images, which I did not know how you could do that without building images yourself. Lonnie > On Jan 18, 2020, at 4:40 PM, Michael Knill <mic...@ip...> wrote: > > Thanks guys > > I was not aware of that doco to convert to a vm board type. Excellent I will do this and then it should all work. > > Lonnie I have been using a Private Repository for years now and have never had a problem. The main reason for using it was purely to determine the 'Current' release for my systems and the ability to upgrade(or downgrade) to any version I want by appending the version directory to the repository URL. I just copy in the upgrade files from the official Astlinux Repository. > I would be happy to use the Astlinux repository if I could do the above. > > Regards > Michael Knill > > On 19/1/20, 1:36 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > > >> On Jan 18, 2020, at 6:06 AM, Michael Keuter <li...@mk...> wrote: >> >> >> >>> Am 18.01.2020 um 01:15 schrieb Michael Knill <mic...@ip...>: >>> >>> Hi group >>> >>> Strangely it appears that with all my genx86_64 systems, on multiple astlinux versions, I am unable to perform an upgrade from my private repository as it comes up with ‘Firmware verification failed’. genx86_vm and genx86_64-serial upgrades work fine. >>> >>> I have tried upgrading to both 1.3.6 and 1.3.7.1 and it does the same thing. I have downloaded it multiple times into the repository so I don't believe the sha1 file is corrupted. >>> It does work however when I point the repository to http://mirror.astlinux-project.org/ast13se-firmware-1.x so this indicates that there must be something wrong with my repository and I cant for the life of me work out what. >>> >>> So my questions are: >>> • Any ideas what this could be and what to try to fix it? >>> • How do I show the board type for a system (before it was shown on login)? >>> • Is there a way I can upgrade to a specific version using the Astlinux repository? >>> • How can I move to a different board type e.g. all my genx86_64 systems are on vm’s so they really should be a genx86_vm board type? >>> >>> Sorry for the lots of questions. Thanks all. >>> >>> Regards >>> Michael Knill >> >> Hi Michael, >> >> short answers to 3. + 4.: >> >> 3. it depends on the "ver" file in the repo folder which contains the (latest) version. E.g. "astlinux-1.3.7.1". >> >> 4. You can switch on the commandline between genx86_64 and genx86_64-vm (but not between serial and vga): >> >> https://doc.astlinux.org/devdoc:devdoc_switch_genx86_64_and_vm >> >> >> Michael > > +1 and for completeness I'll add this link: > > Create a Private Repository > https://doc.astlinux-project.org/devdoc:devdoc_create_repository > > Michael (Knill), you mentioned you are not building your own images (yet), so that begs the question ... how are you generating custom images for your private repository ? > > Lonnie > > > > > _______________________________________________ > 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...> - 2020-01-18 22:40:39
|
Thanks guys
I was not aware of that doco to convert to a vm board type. Excellent I will do this and then it should all work.
Lonnie I have been using a Private Repository for years now and have never had a problem. The main reason for using it was purely to determine the 'Current' release for my systems and the ability to upgrade(or downgrade) to any version I want by appending the version directory to the repository URL. I just copy in the upgrade files from the official Astlinux Repository.
I would be happy to use the Astlinux repository if I could do the above.
Regards
Michael Knill
On 19/1/20, 1:36 am, "Lonnie Abelbeck" <li...@lo...> wrote:
> On Jan 18, 2020, at 6:06 AM, Michael Keuter <li...@mk...> wrote:
>
>
>
>> Am 18.01.2020 um 01:15 schrieb Michael Knill <mic...@ip...>:
>>
>> Hi group
>>
>> Strangely it appears that with all my genx86_64 systems, on multiple astlinux versions, I am unable to perform an upgrade from my private repository as it comes up with ‘Firmware verification failed’. genx86_vm and genx86_64-serial upgrades work fine.
>>
>> I have tried upgrading to both 1.3.6 and 1.3.7.1 and it does the same thing. I have downloaded it multiple times into the repository so I don't believe the sha1 file is corrupted.
>> It does work however when I point the repository to http://mirror.astlinux-project.org/ast13se-firmware-1.x so this indicates that there must be something wrong with my repository and I cant for the life of me work out what.
>>
>> So my questions are:
>> • Any ideas what this could be and what to try to fix it?
>> • How do I show the board type for a system (before it was shown on login)?
>> • Is there a way I can upgrade to a specific version using the Astlinux repository?
>> • How can I move to a different board type e.g. all my genx86_64 systems are on vm’s so they really should be a genx86_vm board type?
>>
>> Sorry for the lots of questions. Thanks all.
>>
>> Regards
>> Michael Knill
>
> Hi Michael,
>
> short answers to 3. + 4.:
>
> 3. it depends on the "ver" file in the repo folder which contains the (latest) version. E.g. "astlinux-1.3.7.1".
>
> 4. You can switch on the commandline between genx86_64 and genx86_64-vm (but not between serial and vga):
>
> https://doc.astlinux.org/devdoc:devdoc_switch_genx86_64_and_vm
>
>
> Michael
+1 and for completeness I'll add this link:
Create a Private Repository
https://doc.astlinux-project.org/devdoc:devdoc_create_repository
Michael (Knill), you mentioned you are not building your own images (yet), so that begs the question ... how are you generating custom images for your private repository ?
Lonnie
_______________________________________________
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...> - 2020-01-18 14:35:46
|
> On Jan 18, 2020, at 6:06 AM, Michael Keuter <li...@mk...> wrote: > > > >> Am 18.01.2020 um 01:15 schrieb Michael Knill <mic...@ip...>: >> >> Hi group >> >> Strangely it appears that with all my genx86_64 systems, on multiple astlinux versions, I am unable to perform an upgrade from my private repository as it comes up with ‘Firmware verification failed’. genx86_vm and genx86_64-serial upgrades work fine. >> >> I have tried upgrading to both 1.3.6 and 1.3.7.1 and it does the same thing. I have downloaded it multiple times into the repository so I don't believe the sha1 file is corrupted. >> It does work however when I point the repository to http://mirror.astlinux-project.org/ast13se-firmware-1.x so this indicates that there must be something wrong with my repository and I cant for the life of me work out what. >> >> So my questions are: >> • Any ideas what this could be and what to try to fix it? >> • How do I show the board type for a system (before it was shown on login)? >> • Is there a way I can upgrade to a specific version using the Astlinux repository? >> • How can I move to a different board type e.g. all my genx86_64 systems are on vm’s so they really should be a genx86_vm board type? >> >> Sorry for the lots of questions. Thanks all. >> >> Regards >> Michael Knill > > Hi Michael, > > short answers to 3. + 4.: > > 3. it depends on the "ver" file in the repo folder which contains the (latest) version. E.g. "astlinux-1.3.7.1". > > 4. You can switch on the commandline between genx86_64 and genx86_64-vm (but not between serial and vga): > > https://doc.astlinux.org/devdoc:devdoc_switch_genx86_64_and_vm > > > Michael +1 and for completeness I'll add this link: Create a Private Repository https://doc.astlinux-project.org/devdoc:devdoc_create_repository Michael (Knill), you mentioned you are not building your own images (yet), so that begs the question ... how are you generating custom images for your private repository ? Lonnie |
|
From: Michael K. <li...@mk...> - 2020-01-18 12:06:56
|
> Am 18.01.2020 um 01:15 schrieb Michael Knill <mic...@ip...>: > > Hi group > > Strangely it appears that with all my genx86_64 systems, on multiple astlinux versions, I am unable to perform an upgrade from my private repository as it comes up with ‘Firmware verification failed’. genx86_vm and genx86_64-serial upgrades work fine. > > I have tried upgrading to both 1.3.6 and 1.3.7.1 and it does the same thing. I have downloaded it multiple times into the repository so I don't believe the sha1 file is corrupted. > It does work however when I point the repository to http://mirror.astlinux-project.org/ast13se-firmware-1.x so this indicates that there must be something wrong with my repository and I cant for the life of me work out what. > > So my questions are: > • Any ideas what this could be and what to try to fix it? > • How do I show the board type for a system (before it was shown on login)? > • Is there a way I can upgrade to a specific version using the Astlinux repository? > • How can I move to a different board type e.g. all my genx86_64 systems are on vm’s so they really should be a genx86_vm board type? > > Sorry for the lots of questions. Thanks all. > > Regards > Michael Knill Hi Michael, short answers to 3. + 4.: 3. it depends on the "ver" file in the repo folder which contains the (latest) version. E.g. "astlinux-1.3.7.1". 4. You can switch on the commandline between genx86_64 and genx86_64-vm (but not between serial and vga): https://doc.astlinux.org/devdoc:devdoc_switch_genx86_64_and_vm Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2020-01-18 00:15:54
|
Hi group Strangely it appears that with all my genx86_64 systems, on multiple astlinux versions, I am unable to perform an upgrade from my private repository as it comes up with ‘Firmware verification failed’. genx86_vm and genx86_64-serial upgrades work fine. I have tried upgrading to both 1.3.6 and 1.3.7.1 and it does the same thing. I have downloaded it multiple times into the repository so I don't believe the sha1 file is corrupted. It does work however when I point the repository to http://mirror.astlinux-project.org/ast13se-firmware-1.x so this indicates that there must be something wrong with my repository and I cant for the life of me work out what. So my questions are: 1. Any ideas what this could be and what to try to fix it? 2. How do I show the board type for a system (before it was shown on login)? 3. Is there a way I can upgrade to a specific version using the Astlinux repository? 4. How can I move to a different board type e.g. all my genx86_64 systems are on vm’s so they really should be a genx86_vm board type? Sorry for the lots of questions. Thanks all. Regards Michael Knill |
|
From: Michael K. <mic...@ip...> - 2019-12-31 05:48:27
|
Just an FYI, the Zabbix client still has a memory leak issue in Astlinux 1.3.7.1.
Regards
Michael Knill
On 20/12/19, 7:11 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Michael,
The latest official AstLinux release 1.3.7.1 has Zabbix LTS 3.0.28 (2019-05-28).
The newer Zabbix LTS 4.0 most likely would require new server agent/proxy changes.
Since not many people use Zabbix (as it can be complicated), we are staying with Zabbix LTS 3.0.28.
Lonnie
> On Dec 19, 2019, at 1:56 PM, Michael Knill <mic...@ip...> wrote:
>
> Any particular reason why we are using the 3.0.xx series?
>
> Regards
> Michael Knill
>
> On 19/12/19, 10:07 pm, "Michael Keuter" <li...@mk...> wrote:
>
> BTW: There are much newer Zabbix versions than our 3.0.xx series.
>
> https://sourceforge.net/projects/zabbix/files/ZABBIX%20Latest%20Stable/
>
>> Am 19.12.2019 um 11:29 schrieb Michael Knill <mic...@ip...>:
>>
>> Actually looking at the Zabbix graphs, it is gradual over a fairly long period of time e.g. months.
>> There is a bug ZBX-10486 which is for the version we are using (3.0.14) but I'm not sure it's the exact same cause.
>> Might be worth trying 1.3.7 to see if the later version solves the issue.
>>
>> Regards
>> Michael Knill
>>
>> On 18/12/19, 10:59 am, "Michael Knill" <mic...@ip...> wrote:
>>
>> I haven’t had a crash yet as ironically Zabbix notifies me that the memory is low and I just hop in and restart the Zabbix agent and its all good.
>> Yes htop shows the 3 listeners at the top of the list. It was 450M each at one of my sites I checked.
>> I think there may be only certain events that cause the memory leak as it does not seem to gradually increase although I cant confirm this.
>>
>> Off to the Zabbix forums ☹
>>
>> Regards
>> Michael Knill
>>
>> On 18/12/19, 10:36 am, "Lonnie Abelbeck" <li...@lo...> wrote:
>>
>> Hi Michael,
>>
>> Darrick has seen similar memory-leak behavior for years with Zabbix.
>>
>> Are you seeing your box running out of RAM and crashing ?
>>
>> What does "htop" show, is the top "Mem" line slowly getting bigger and bigger ?
>>
>> Restarting Zabbix every evening might be solution, but not ideal.
>>
>> It will be interisting what the forums suggest.
>>
>> Lonnie
>>
>>
>>
>>
>>
>>> On Dec 17, 2019, at 2:57 PM, Michael Knill <mic...@ip...> wrote:
>>>
>>> Hi Group
>>>
>>> I am progressively rolling out Zabbix to my sites and I am beginning to experiencing memory leaks or high memory usage on the zabbix_agentd listener processes (all 3).
>>> Just wondering if anyone has experienced this?
>>> Any ideas on how I should troubleshoot?
>>> Could it be one of the scripts I am running although they are pretty basic?
>>>
>>> top -m
>>> Mem total:1935568 anon:668256 map:17612 free:983896
>>> slab:27716 buf:5036 cache:225908 dirty:16 write:0
>>> Swap total:0 free:0
>>> PID^^^VSZ^VSZRW RSS (SHR) DIRTY (SHR) STACK COMMAND
>>> 2527 2530m 86892 54924 3436 54920 3432 128 /usr/sbin/asterisk -f -p -c
>>> 9459 222m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #3 [waiting for connection]
>>> 9457 221m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #1 [waiting for connection]
>>> 9458 221m 189m 190m 2008 190m 2004 132 zabbix_agentd: listener #2 [waiting for connection]
>>>
>>> Thnaks
>>>
>>> Regards
>>> Michael Knill
>
>
> 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: Michael K. <mic...@ip...> - 2019-12-19 20:48:05
|
Thanks Lonnie
Yes it is a bit complicated to set up but we have already put the effort in ☹
I will try 3.0.28 and if no joy then I will need to move to 4.0 or probably just use Monit for notification purposes.
Thanks all for your help.
Regards
Michael Knill
On 20/12/19, 7:11 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Michael,
The latest official AstLinux release 1.3.7.1 has Zabbix LTS 3.0.28 (2019-05-28).
The newer Zabbix LTS 4.0 most likely would require new server agent/proxy changes.
Since not many people use Zabbix (as it can be complicated), we are staying with Zabbix LTS 3.0.28.
Lonnie
> On Dec 19, 2019, at 1:56 PM, Michael Knill <mic...@ip...> wrote:
>
> Any particular reason why we are using the 3.0.xx series?
>
> Regards
> Michael Knill
>
> On 19/12/19, 10:07 pm, "Michael Keuter" <li...@mk...> wrote:
>
> BTW: There are much newer Zabbix versions than our 3.0.xx series.
>
> https://sourceforge.net/projects/zabbix/files/ZABBIX%20Latest%20Stable/
>
>> Am 19.12.2019 um 11:29 schrieb Michael Knill <mic...@ip...>:
>>
>> Actually looking at the Zabbix graphs, it is gradual over a fairly long period of time e.g. months.
>> There is a bug ZBX-10486 which is for the version we are using (3.0.14) but I'm not sure it's the exact same cause.
>> Might be worth trying 1.3.7 to see if the later version solves the issue.
>>
>> Regards
>> Michael Knill
>>
>> On 18/12/19, 10:59 am, "Michael Knill" <mic...@ip...> wrote:
>>
>> I haven’t had a crash yet as ironically Zabbix notifies me that the memory is low and I just hop in and restart the Zabbix agent and its all good.
>> Yes htop shows the 3 listeners at the top of the list. It was 450M each at one of my sites I checked.
>> I think there may be only certain events that cause the memory leak as it does not seem to gradually increase although I cant confirm this.
>>
>> Off to the Zabbix forums ☹
>>
>> Regards
>> Michael Knill
>>
>> On 18/12/19, 10:36 am, "Lonnie Abelbeck" <li...@lo...> wrote:
>>
>> Hi Michael,
>>
>> Darrick has seen similar memory-leak behavior for years with Zabbix.
>>
>> Are you seeing your box running out of RAM and crashing ?
>>
>> What does "htop" show, is the top "Mem" line slowly getting bigger and bigger ?
>>
>> Restarting Zabbix every evening might be solution, but not ideal.
>>
>> It will be interisting what the forums suggest.
>>
>> Lonnie
>>
>>
>>
>>
>>
>>> On Dec 17, 2019, at 2:57 PM, Michael Knill <mic...@ip...> wrote:
>>>
>>> Hi Group
>>>
>>> I am progressively rolling out Zabbix to my sites and I am beginning to experiencing memory leaks or high memory usage on the zabbix_agentd listener processes (all 3).
>>> Just wondering if anyone has experienced this?
>>> Any ideas on how I should troubleshoot?
>>> Could it be one of the scripts I am running although they are pretty basic?
>>>
>>> top -m
>>> Mem total:1935568 anon:668256 map:17612 free:983896
>>> slab:27716 buf:5036 cache:225908 dirty:16 write:0
>>> Swap total:0 free:0
>>> PID^^^VSZ^VSZRW RSS (SHR) DIRTY (SHR) STACK COMMAND
>>> 2527 2530m 86892 54924 3436 54920 3432 128 /usr/sbin/asterisk -f -p -c
>>> 9459 222m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #3 [waiting for connection]
>>> 9457 221m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #1 [waiting for connection]
>>> 9458 221m 189m 190m 2008 190m 2004 132 zabbix_agentd: listener #2 [waiting for connection]
>>>
>>> Thnaks
>>>
>>> Regards
>>> Michael Knill
>
>
> 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...> - 2019-12-19 20:11:01
|
Michael, The latest official AstLinux release 1.3.7.1 has Zabbix LTS 3.0.28 (2019-05-28). The newer Zabbix LTS 4.0 most likely would require new server agent/proxy changes. Since not many people use Zabbix (as it can be complicated), we are staying with Zabbix LTS 3.0.28. Lonnie > On Dec 19, 2019, at 1:56 PM, Michael Knill <mic...@ip...> wrote: > > Any particular reason why we are using the 3.0.xx series? > > Regards > Michael Knill > > On 19/12/19, 10:07 pm, "Michael Keuter" <li...@mk...> wrote: > > BTW: There are much newer Zabbix versions than our 3.0.xx series. > > https://sourceforge.net/projects/zabbix/files/ZABBIX%20Latest%20Stable/ > >> Am 19.12.2019 um 11:29 schrieb Michael Knill <mic...@ip...>: >> >> Actually looking at the Zabbix graphs, it is gradual over a fairly long period of time e.g. months. >> There is a bug ZBX-10486 which is for the version we are using (3.0.14) but I'm not sure it's the exact same cause. >> Might be worth trying 1.3.7 to see if the later version solves the issue. >> >> Regards >> Michael Knill >> >> On 18/12/19, 10:59 am, "Michael Knill" <mic...@ip...> wrote: >> >> I haven’t had a crash yet as ironically Zabbix notifies me that the memory is low and I just hop in and restart the Zabbix agent and its all good. >> Yes htop shows the 3 listeners at the top of the list. It was 450M each at one of my sites I checked. >> I think there may be only certain events that cause the memory leak as it does not seem to gradually increase although I cant confirm this. >> >> Off to the Zabbix forums ☹ >> >> Regards >> Michael Knill >> >> On 18/12/19, 10:36 am, "Lonnie Abelbeck" <li...@lo...> wrote: >> >> Hi Michael, >> >> Darrick has seen similar memory-leak behavior for years with Zabbix. >> >> Are you seeing your box running out of RAM and crashing ? >> >> What does "htop" show, is the top "Mem" line slowly getting bigger and bigger ? >> >> Restarting Zabbix every evening might be solution, but not ideal. >> >> It will be interisting what the forums suggest. >> >> Lonnie >> >> >> >> >> >>> On Dec 17, 2019, at 2:57 PM, Michael Knill <mic...@ip...> wrote: >>> >>> Hi Group >>> >>> I am progressively rolling out Zabbix to my sites and I am beginning to experiencing memory leaks or high memory usage on the zabbix_agentd listener processes (all 3). >>> Just wondering if anyone has experienced this? >>> Any ideas on how I should troubleshoot? >>> Could it be one of the scripts I am running although they are pretty basic? >>> >>> top -m >>> Mem total:1935568 anon:668256 map:17612 free:983896 >>> slab:27716 buf:5036 cache:225908 dirty:16 write:0 >>> Swap total:0 free:0 >>> PID^^^VSZ^VSZRW RSS (SHR) DIRTY (SHR) STACK COMMAND >>> 2527 2530m 86892 54924 3436 54920 3432 128 /usr/sbin/asterisk -f -p -c >>> 9459 222m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #3 [waiting for connection] >>> 9457 221m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #1 [waiting for connection] >>> 9458 221m 189m 190m 2008 190m 2004 132 zabbix_agentd: listener #2 [waiting for connection] >>> >>> Thnaks >>> >>> Regards >>> Michael Knill > > > 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: Michael K. <mic...@ip...> - 2019-12-19 19:56:59
|
Any particular reason why we are using the 3.0.xx series?
Regards
Michael Knill
On 19/12/19, 10:07 pm, "Michael Keuter" <li...@mk...> wrote:
BTW: There are much newer Zabbix versions than our 3.0.xx series.
https://sourceforge.net/projects/zabbix/files/ZABBIX%20Latest%20Stable/
> Am 19.12.2019 um 11:29 schrieb Michael Knill <mic...@ip...>:
>
> Actually looking at the Zabbix graphs, it is gradual over a fairly long period of time e.g. months.
> There is a bug ZBX-10486 which is for the version we are using (3.0.14) but I'm not sure it's the exact same cause.
> Might be worth trying 1.3.7 to see if the later version solves the issue.
>
> Regards
> Michael Knill
>
> On 18/12/19, 10:59 am, "Michael Knill" <mic...@ip...> wrote:
>
> I haven’t had a crash yet as ironically Zabbix notifies me that the memory is low and I just hop in and restart the Zabbix agent and its all good.
> Yes htop shows the 3 listeners at the top of the list. It was 450M each at one of my sites I checked.
> I think there may be only certain events that cause the memory leak as it does not seem to gradually increase although I cant confirm this.
>
> Off to the Zabbix forums ☹
>
> Regards
> Michael Knill
>
> On 18/12/19, 10:36 am, "Lonnie Abelbeck" <li...@lo...> wrote:
>
> Hi Michael,
>
> Darrick has seen similar memory-leak behavior for years with Zabbix.
>
> Are you seeing your box running out of RAM and crashing ?
>
> What does "htop" show, is the top "Mem" line slowly getting bigger and bigger ?
>
> Restarting Zabbix every evening might be solution, but not ideal.
>
> It will be interisting what the forums suggest.
>
> Lonnie
>
>
>
>
>
>> On Dec 17, 2019, at 2:57 PM, Michael Knill <mic...@ip...> wrote:
>>
>> Hi Group
>>
>> I am progressively rolling out Zabbix to my sites and I am beginning to experiencing memory leaks or high memory usage on the zabbix_agentd listener processes (all 3).
>> Just wondering if anyone has experienced this?
>> Any ideas on how I should troubleshoot?
>> Could it be one of the scripts I am running although they are pretty basic?
>>
>> top -m
>> Mem total:1935568 anon:668256 map:17612 free:983896
>> slab:27716 buf:5036 cache:225908 dirty:16 write:0
>> Swap total:0 free:0
>> PID^^^VSZ^VSZRW RSS (SHR) DIRTY (SHR) STACK COMMAND
>> 2527 2530m 86892 54924 3436 54920 3432 128 /usr/sbin/asterisk -f -p -c
>> 9459 222m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #3 [waiting for connection]
>> 9457 221m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #1 [waiting for connection]
>> 9458 221m 189m 190m 2008 190m 2004 132 zabbix_agentd: listener #2 [waiting for connection]
>>
>> Thnaks
>>
>> Regards
>> Michael Knill
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: darricklegacy <dha...@dj...> - 2019-12-19 17:15:52
|
Hi Michael, We haven’t replaced it at this point. The server I was hosting the database on crashed and it just hasn’t been a priority. We mostly use it to monitor network traffic. We’ve since moved to a policy where the AstLinus box is not the edge device so that data isn’t valid. We use SmokePing to monitor the internet connectivity instead. Much smaller footprint, but it only provides a fraction of the data. Darrick From: Michael Knill <mic...@ip...> Reply-To: AstLinux Users <ast...@li...> Date: Tuesday, December 17, 2019 at 6:53 PM To: AstLinux Users <ast...@li...> Subject: Re: [Astlinux-users] Zabbix Memory Leak Thanks Darrick Hmm that's annoying. All this time we put into it and it does this. May I ask what you are using now (if anything)? Thanks Darrick Hmm that's annoying. All this time we put into it and it does this. May I ask what you are using now (if anything)? Regards Michael Knill From: darricklegacy <dha...@dj...> Reply to: AstLinux List <ast...@li...> Date: Wednesday, 18 December 2019 at 11:07 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Zabbix Memory Leak Hi Michael, We’re no longer using Zabbix, but we ran into similar issues we resolved by having a weekly cron job to restart Zabbix. You can see the memory leak in your Zabbix graph. Darrick From: Michael Knill <mic...@ip...> Reply-To: AstLinux Users <ast...@li...> Date: Tuesday, December 17, 2019 at 3:50 PM To: AstLinux Users <ast...@li...> Subject: Re: [Astlinux-users] Zabbix Memory Leak Other than reporting on the Zabbix forums which I plan on doing soon. Regards Michael Knill From: Michael Knill <mic...@ip...> Reply to: AstLinux List <ast...@li...> Date: Wednesday, 18 December 2019 at 7:58 am To: AstLinux List <ast...@li...> Subject: [Astlinux-users] Zabbix Memory Leak Hi Group I am progressively rolling out Zabbix to my sites and I am beginning to experiencing memory leaks or high memory usage on the zabbix_agentd listener processes (all 3). Just wondering if anyone has experienced this? Any ideas on how I should troubleshoot? Could it be one of the scripts I am running although they are pretty basic? top -m Mem total:1935568 anon:668256 map:17612 free:983896 slab:27716 buf:5036 cache:225908 dirty:16 write:0 Swap total:0 free:0 PID^^^VSZ^VSZRW RSS (SHR) DIRTY (SHR) STACK COMMAND 2527 2530m 86892 54924 3436 54920 3432 128 /usr/sbin/asterisk -f -p -c 9459 222m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #3 [waiting for connection] 9457 221m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #1 [waiting for connection] 9458 221m 189m 190m 2008 190m 2004 132 zabbix_agentd: listener #2 [waiting for connection] Thnaks Regards Michael Knill |
|
From: Michael K. <li...@mk...> - 2019-12-19 11:07:25
|
BTW: There are much newer Zabbix versions than our 3.0.xx series. https://sourceforge.net/projects/zabbix/files/ZABBIX%20Latest%20Stable/ > Am 19.12.2019 um 11:29 schrieb Michael Knill <mic...@ip...>: > > Actually looking at the Zabbix graphs, it is gradual over a fairly long period of time e.g. months. > There is a bug ZBX-10486 which is for the version we are using (3.0.14) but I'm not sure it's the exact same cause. > Might be worth trying 1.3.7 to see if the later version solves the issue. > > Regards > Michael Knill > > On 18/12/19, 10:59 am, "Michael Knill" <mic...@ip...> wrote: > > I haven’t had a crash yet as ironically Zabbix notifies me that the memory is low and I just hop in and restart the Zabbix agent and its all good. > Yes htop shows the 3 listeners at the top of the list. It was 450M each at one of my sites I checked. > I think there may be only certain events that cause the memory leak as it does not seem to gradually increase although I cant confirm this. > > Off to the Zabbix forums ☹ > > Regards > Michael Knill > > On 18/12/19, 10:36 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Hi Michael, > > Darrick has seen similar memory-leak behavior for years with Zabbix. > > Are you seeing your box running out of RAM and crashing ? > > What does "htop" show, is the top "Mem" line slowly getting bigger and bigger ? > > Restarting Zabbix every evening might be solution, but not ideal. > > It will be interisting what the forums suggest. > > Lonnie > > > > > >> On Dec 17, 2019, at 2:57 PM, Michael Knill <mic...@ip...> wrote: >> >> Hi Group >> >> I am progressively rolling out Zabbix to my sites and I am beginning to experiencing memory leaks or high memory usage on the zabbix_agentd listener processes (all 3). >> Just wondering if anyone has experienced this? >> Any ideas on how I should troubleshoot? >> Could it be one of the scripts I am running although they are pretty basic? >> >> top -m >> Mem total:1935568 anon:668256 map:17612 free:983896 >> slab:27716 buf:5036 cache:225908 dirty:16 write:0 >> Swap total:0 free:0 >> PID^^^VSZ^VSZRW RSS (SHR) DIRTY (SHR) STACK COMMAND >> 2527 2530m 86892 54924 3436 54920 3432 128 /usr/sbin/asterisk -f -p -c >> 9459 222m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #3 [waiting for connection] >> 9457 221m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #1 [waiting for connection] >> 9458 221m 189m 190m 2008 190m 2004 132 zabbix_agentd: listener #2 [waiting for connection] >> >> Thnaks >> >> Regards >> Michael Knill Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2019-12-19 10:29:15
|
Actually looking at the Zabbix graphs, it is gradual over a fairly long period of time e.g. months.
There is a bug ZBX-10486 which is for the version we are using (3.0.14) but I'm not sure it's the exact same cause.
Might be worth trying 1.3.7 to see if the later version solves the issue.
Regards
Michael Knill
On 18/12/19, 10:59 am, "Michael Knill" <mic...@ip...> wrote:
I haven’t had a crash yet as ironically Zabbix notifies me that the memory is low and I just hop in and restart the Zabbix agent and its all good.
Yes htop shows the 3 listeners at the top of the list. It was 450M each at one of my sites I checked.
I think there may be only certain events that cause the memory leak as it does not seem to gradually increase although I cant confirm this.
Off to the Zabbix forums ☹
Regards
Michael Knill
On 18/12/19, 10:36 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Hi Michael,
Darrick has seen similar memory-leak behavior for years with Zabbix.
Are you seeing your box running out of RAM and crashing ?
What does "htop" show, is the top "Mem" line slowly getting bigger and bigger ?
Restarting Zabbix every evening might be solution, but not ideal.
It will be interisting what the forums suggest.
Lonnie
> On Dec 17, 2019, at 2:57 PM, Michael Knill <mic...@ip...> wrote:
>
> Hi Group
>
> I am progressively rolling out Zabbix to my sites and I am beginning to experiencing memory leaks or high memory usage on the zabbix_agentd listener processes (all 3).
> Just wondering if anyone has experienced this?
> Any ideas on how I should troubleshoot?
> Could it be one of the scripts I am running although they are pretty basic?
>
> top -m
> Mem total:1935568 anon:668256 map:17612 free:983896
> slab:27716 buf:5036 cache:225908 dirty:16 write:0
> Swap total:0 free:0
> PID^^^VSZ^VSZRW RSS (SHR) DIRTY (SHR) STACK COMMAND
> 2527 2530m 86892 54924 3436 54920 3432 128 /usr/sbin/asterisk -f -p -c
> 9459 222m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #3 [waiting for connection]
> 9457 221m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #1 [waiting for connection]
> 9458 221m 189m 190m 2008 190m 2004 132 zabbix_agentd: listener #2 [waiting for connection]
>
> Thnaks
>
> 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: Michael K. <mic...@ip...> - 2019-12-18 00:53:34
|
Thanks Darrick Hmm that's annoying. All this time we put into it and it does this. May I ask what you are using now (if anything)? Regards Michael Knill From: darricklegacy <dha...@dj...> Reply to: AstLinux List <ast...@li...> Date: Wednesday, 18 December 2019 at 11:07 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Zabbix Memory Leak Hi Michael, We’re no longer using Zabbix, but we ran into similar issues we resolved by having a weekly cron job to restart Zabbix. You can see the memory leak in your Zabbix graph. Darrick From: Michael Knill <mic...@ip...> Reply-To: AstLinux Users <ast...@li...> Date: Tuesday, December 17, 2019 at 3:50 PM To: AstLinux Users <ast...@li...> Subject: Re: [Astlinux-users] Zabbix Memory Leak Other than reporting on the Zabbix forums which I plan on doing soon. Regards Michael Knill From: Michael Knill <mic...@ip...> Reply to: AstLinux List <ast...@li...> Date: Wednesday, 18 December 2019 at 7:58 am To: AstLinux List <ast...@li...> Subject: [Astlinux-users] Zabbix Memory Leak Hi Group I am progressively rolling out Zabbix to my sites and I am beginning to experiencing memory leaks or high memory usage on the zabbix_agentd listener processes (all 3). Just wondering if anyone has experienced this? Any ideas on how I should troubleshoot? Could it be one of the scripts I am running although they are pretty basic? top -m Mem total:1935568 anon:668256 map:17612 free:983896 slab:27716 buf:5036 cache:225908 dirty:16 write:0 Swap total:0 free:0 PID^^^VSZ^VSZRW RSS (SHR) DIRTY (SHR) STACK COMMAND 2527 2530m 86892 54924 3436 54920 3432 128 /usr/sbin/asterisk -f -p -c 9459 222m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #3 [waiting for connection] 9457 221m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #1 [waiting for connection] 9458 221m 189m 190m 2008 190m 2004 132 zabbix_agentd: listener #2 [waiting for connection] Thnaks Regards Michael Knill |
|
From: darricklegacy <dha...@dj...> - 2019-12-18 00:07:08
|
Other than reporting on the Zabbix forums which I plan on doing soon. Regards Michael Knill From: Michael Knill <mic...@ip...> Reply to: AstLinux List <ast...@li...> Date: Wednesday, 18 December 2019 at 7:58 am To: AstLinux List <ast...@li...> Subject: [Astlinux-users] Zabbix Memory Leak Hi Group I am progressively rolling out Zabbix to my sites and I am beginning to experiencing memory leaks or high memory usage on the zabbix_agentd listener processes (all 3). Just wondering if anyone has experienced this? Any ideas on how I should troubleshoot? Could it be one of the scripts I am running although they are pretty basic? top -m Mem total:1935568 anon:668256 map:17612 free:983896 slab:27716 buf:5036 cache:225908 dirty:16 write:0 Swap total:0 free:0 PID^^^VSZ^VSZRW RSS (SHR) DIRTY (SHR) STACK COMMAND 2527 2530m 86892 54924 3436 54920 3432 128 /usr/sbin/asterisk -f -p -c 9459 222m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #3 [waiting for connection] 9457 221m 190m 191m 2008 191m 2004 132 zabbix_agentd: listener #1 [waiting for connection] 9458 221m 189m 190m 2008 190m 2004 132 zabbix_agentd: listener #2 [waiting for connection] Thnaks Regards Michael Knill |
63 messages has been excluded from this view by a project administrator.
