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
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Ionel C. <ion...@me...> - 2023-11-16 12:54:31
|
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><span style="-webkit-text-size-adjust: auto;">I have 4 variations of these routers. Rock solid and very very stable. The VPNs (wire guard & OpenVPN) work very well as I do tunnels to my UDMP-SE from Europe and Asia. My kid is using the travel version to vpn home and bypass the Netflix password sharing insanity, like he is not family? I also use one for travel and do VPN from China to bypass their great firewall. It runs on OpenWRT and you can add a lot of custom packages, even asterisk.</span><div><br style="-webkit-text-size-adjust: auto;"><div dir="ltr"><div dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);">Regards</span></div><div dir="ltr"><span style="background-color: rgba(255, 255, 255, 0);">Ionel </span></div><div dir="ltr"><br></div></div><div dir="ltr"><br><blockquote type="cite">On Nov 16, 2023, at 3:44 AM, Michael Knill <mic...@ip...> wrote:<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 All<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal">It looks perfect and initial playing has been positive. You can even cloud manage it which is a bonus.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Just checking if anyone has had any experience with GL.iNet products and this is not too good to be true.<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: Lonnie A. <li...@lo...> - 2023-11-16 12:43:31
|
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.... |
|
From: Michael K. <li...@mk...> - 2023-11-16 11:01:54
|
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 |
|
From: Michael K. <mic...@ip...> - 2023-11-16 09:44:10
|
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 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: Gerard v. T. <ger...@gm...> - 2023-11-05 16:04:53
|
Hi Michael, Thanks! I didn't know it was possible to switch between board-types, this certainly is an option for me. I was also thinking about building the box from scratch using the latest Astlinux, this box is not very complicated and only has a few config-files changed. Another option would be to switch over to my second vm, which is now running 1.5.1. I have set it up to get more experience in moving from SIP to PJSIP, so the right moment has come to spend more time on this. Thanks for your help! Kind regards, Gerard Op zo 5 nov 2023 om 13:41 schreef Michael Keuter <li...@mk...>: > > > > Am 05.11.2023 um 10:17 schrieb Gerard van Til <ger...@gm...>: > > > > Thanks Lonnie, > > > > Where I was sure that I downloaded the right image long ago, it seems > this box is indeed running on the generic firmware. I see > "astlinux=genx86_64" instead of the vm-Board-Type. > > Now I have my GUI back, this also shows on the status page. > > > > I have another Hyper-V vm running astlinux-1.4.8, and that machine has > the genx86_64-vm board type, so I can (in the GUI) see the difference > between these two boxes now. > > I also just upgraded that machine from 1.4.8 to 1.5.1 successfully. > > > > Thanks again for your help and super fast response. If you want me to do > some more tests, let me know, otherwise this issue has been solved, > > > > Regards, > > Gerard > > > > > > Op za 4 nov 2023 om 22:44 schreef Lonnie Abelbeck < > li...@lo...>: > > Hi Gerard, > > > > AstLinux Hyper-V support [1] needs a Board Type of "genx86_64-vm", so > check by typing "cat /proc/cmdline" in the CLI and look for the string " > astlinux=genx86_64-vm " as that is what you want. If you only have the > string " astlinux=genx86_64 " then that is the issue. > > > > The (non-VM) Board Type of "genx86_64" may have been able to run Hyper-V > at some point, you really need a Board Type of "genx86_64-vm". The VM > version has specific hv_netvsc and hv_utils modules that support Hyper-V > virtual IO drivers. > > > > Note, your upgrade did not change the board type, so you can test the > above with the old astlinux-1.3.8 version. > > > > Let us know if this is the issue, before any more diagnosis. > > > > Lonnie > > > > [1] https://doc.astlinux-project.org/userdoc:guest_vm_hyperv > > > > > > > > > On Nov 4, 2023, at 3:27 PM, Gerard van Til <ger...@gm...> > wrote: > > > > > > Thanks Michael and Lonnie (I already hoped to receive answers from > both of you :-)). > > > > > > @Lonnie: unfortunately, I cannot access the GUI anymore, so we'll have > to deal with Linux commands > > > I entered the commands you asked for, and because I have console-only > access, I'll have to send the answers as screenshot: > > > > > > <image.png> > > > > > > @Michael: "upgrade-run-image show" shows me that I upgraded from 1.3.8 > to 1.4.4. > > > Current version is: astlinux-1.4.4 > > > Previous saved version is: astlinux-1.3.8 > > > > > > I did a revert using the second command Michael provided, and that > worked: the system is back again. Thanks! > > > I created a snapshot of this machine before the revert, so we can > investigate further what happened if you want. But I guess I can reproduce > this behaviour by upgrading again. > > > The (virtual) network adapter in this machine is a legacy one > according to Hyper-V: "Realtek PCIe GBE Family controller". Maybe that is > related to the issue? > > > > > > Thanks both! > > > Regards; > > > Gerard > > > > > > Op za 4 nov 2023 om 18:32 schreef Michael Keuter < > li...@mk...>: > > > > > > > > > > Am 04.11.2023 um 18:16 schrieb Lonnie Abelbeck < > li...@lo...>: > > > > > > > >> > > > >> On Nov 4, 2023, at 11:12 AM, Gerard van Til <ger...@gm...> > wrote: > > > >> > > > >> Goodafternoon, > > > >> > > > >> I just upgraded my AstLinux using the UI, but after rebooting, my > eth0 seems to be gone, so I have no internet access anymore. Luckily, this > AstLinux is running on a virtual machine under Windows Hyper-V, and I can > access it using the Hyper-V manager. I can login with the root user, and > should be able to enter commands. If anyone can help me with the Linux > commands to restore this box to its previous version before the upgrade, > that would be great! > > > >> > > > >> Regards; > > > >> Gerard / Netherlands > > > > > > > > Hi Gerard, > > > > > > > > First answering your last question, to revert back to the pervious > version, simply: > > > > > > > > System tab -> System Firmware Upgrade: [ Revert to Previous ] - { > Firmware } - _x_ Confirm > > > > > > > > System tab -> Reboot/Restart System: [ Now ] - { Reboot } - _x_ > Confirm > > > > > > > > > > > > Before you do that, let's try to understand the issue. > > > > > > > > Are you at the latest AstLinux 1.5.1 ? > > > > > > > > What is the output of: > > > > -- > > > > lscpu | grep -i '^hypervisor vendor:' > > > > -- > > > > > > > > What is the output of: > > > > -- > > > > lsmod > > > > -- > > > > > > > > > > > > Sadly I have no way to test Hyper-V, so your help is appreciated. > > > > > > > > Lonnie > > > > > > If you cannot access the GUI, the same can be done from the command > line: > > > > > > Check installed versions: > > > > > > -- > > > upgrade-run-image show > > > -- > > > > > > Revert to former version: > > > > > > -- > > > upgrade-run-image revert > > > reboot > > > -- > > > > > > Good luck > > > > > > Michael > > Hi Gerad, > > you'll might find our Wiki article about switching board types useful: > > https://doc.astlinux-project.org/devdoc:devdoc_switch_genx86_64_and_vm > > 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-05 12:41:11
|
> Am 05.11.2023 um 10:17 schrieb Gerard van Til <ger...@gm...>: > > Thanks Lonnie, > > Where I was sure that I downloaded the right image long ago, it seems this box is indeed running on the generic firmware. I see "astlinux=genx86_64" instead of the vm-Board-Type. > Now I have my GUI back, this also shows on the status page. > > I have another Hyper-V vm running astlinux-1.4.8, and that machine has the genx86_64-vm board type, so I can (in the GUI) see the difference between these two boxes now. > I also just upgraded that machine from 1.4.8 to 1.5.1 successfully. > > Thanks again for your help and super fast response. If you want me to do some more tests, let me know, otherwise this issue has been solved, > > Regards, > Gerard > > > Op za 4 nov 2023 om 22:44 schreef Lonnie Abelbeck <li...@lo...>: > Hi Gerard, > > AstLinux Hyper-V support [1] needs a Board Type of "genx86_64-vm", so check by typing "cat /proc/cmdline" in the CLI and look for the string " astlinux=genx86_64-vm " as that is what you want. If you only have the string " astlinux=genx86_64 " then that is the issue. > > The (non-VM) Board Type of "genx86_64" may have been able to run Hyper-V at some point, you really need a Board Type of "genx86_64-vm". The VM version has specific hv_netvsc and hv_utils modules that support Hyper-V virtual IO drivers. > > Note, your upgrade did not change the board type, so you can test the above with the old astlinux-1.3.8 version. > > Let us know if this is the issue, before any more diagnosis. > > Lonnie > > [1] https://doc.astlinux-project.org/userdoc:guest_vm_hyperv > > > > > On Nov 4, 2023, at 3:27 PM, Gerard van Til <ger...@gm...> wrote: > > > > Thanks Michael and Lonnie (I already hoped to receive answers from both of you :-)). > > > > @Lonnie: unfortunately, I cannot access the GUI anymore, so we'll have to deal with Linux commands > > I entered the commands you asked for, and because I have console-only access, I'll have to send the answers as screenshot: > > > > <image.png> > > > > @Michael: "upgrade-run-image show" shows me that I upgraded from 1.3.8 to 1.4.4. > > Current version is: astlinux-1.4.4 > > Previous saved version is: astlinux-1.3.8 > > > > I did a revert using the second command Michael provided, and that worked: the system is back again. Thanks! > > I created a snapshot of this machine before the revert, so we can investigate further what happened if you want. But I guess I can reproduce this behaviour by upgrading again. > > The (virtual) network adapter in this machine is a legacy one according to Hyper-V: "Realtek PCIe GBE Family controller". Maybe that is related to the issue? > > > > Thanks both! > > Regards; > > Gerard > > > > Op za 4 nov 2023 om 18:32 schreef Michael Keuter <li...@mk...>: > > > > > > > Am 04.11.2023 um 18:16 schrieb Lonnie Abelbeck <li...@lo...>: > > > > > >> > > >> On Nov 4, 2023, at 11:12 AM, Gerard van Til <ger...@gm...> wrote: > > >> > > >> Goodafternoon, > > >> > > >> I just upgraded my AstLinux using the UI, but after rebooting, my eth0 seems to be gone, so I have no internet access anymore. Luckily, this AstLinux is running on a virtual machine under Windows Hyper-V, and I can access it using the Hyper-V manager. I can login with the root user, and should be able to enter commands. If anyone can help me with the Linux commands to restore this box to its previous version before the upgrade, that would be great! > > >> > > >> Regards; > > >> Gerard / Netherlands > > > > > > Hi Gerard, > > > > > > First answering your last question, to revert back to the pervious version, simply: > > > > > > System tab -> System Firmware Upgrade: [ Revert to Previous ] - { Firmware } - _x_ Confirm > > > > > > System tab -> Reboot/Restart System: [ Now ] - { Reboot } - _x_ Confirm > > > > > > > > > Before you do that, let's try to understand the issue. > > > > > > Are you at the latest AstLinux 1.5.1 ? > > > > > > What is the output of: > > > -- > > > lscpu | grep -i '^hypervisor vendor:' > > > -- > > > > > > What is the output of: > > > -- > > > lsmod > > > -- > > > > > > > > > Sadly I have no way to test Hyper-V, so your help is appreciated. > > > > > > Lonnie > > > > If you cannot access the GUI, the same can be done from the command line: > > > > Check installed versions: > > > > -- > > upgrade-run-image show > > -- > > > > Revert to former version: > > > > -- > > upgrade-run-image revert > > reboot > > -- > > > > Good luck > > > > Michael Hi Gerad, you'll might find our Wiki article about switching board types useful: https://doc.astlinux-project.org/devdoc:devdoc_switch_genx86_64_and_vm Michael http://www.mksolutions.info |
|
From: Gerard v. T. <ger...@gm...> - 2023-11-05 09:17:35
|
Thanks Lonnie, Where I was sure that I downloaded the right image long ago, it seems this box is indeed running on the generic firmware. I see "astlinux=genx86_64" instead of the vm-Board-Type. Now I have my GUI back, this also shows on the status page. I have another Hyper-V vm running astlinux-1.4.8, and that machine has the genx86_64-vm board type, so I can (in the GUI) see the difference between these two boxes now. I also just upgraded that machine from 1.4.8 to 1.5.1 successfully. Thanks again for your help and super fast response. If you want me to do some more tests, let me know, otherwise this issue has been solved, Regards, Gerard Op za 4 nov 2023 om 22:44 schreef Lonnie Abelbeck <li...@lo... >: > Hi Gerard, > > AstLinux Hyper-V support [1] needs a Board Type of "genx86_64-vm", so > check by typing "cat /proc/cmdline" in the CLI and look for the string " > astlinux=genx86_64-vm " as that is what you want. If you only have the > string " astlinux=genx86_64 " then that is the issue. > > The (non-VM) Board Type of "genx86_64" may have been able to run Hyper-V > at some point, you really need a Board Type of "genx86_64-vm". The VM > version has specific hv_netvsc and hv_utils modules that support Hyper-V > virtual IO drivers. > > Note, your upgrade did not change the board type, so you can test the > above with the old astlinux-1.3.8 version. > > Let us know if this is the issue, before any more diagnosis. > > Lonnie > > [1] https://doc.astlinux-project.org/userdoc:guest_vm_hyperv > > > > > On Nov 4, 2023, at 3:27 PM, Gerard van Til <ger...@gm...> > wrote: > > > > Thanks Michael and Lonnie (I already hoped to receive answers from both > of you :-)). > > > > @Lonnie: unfortunately, I cannot access the GUI anymore, so we'll have > to deal with Linux commands > > I entered the commands you asked for, and because I have console-only > access, I'll have to send the answers as screenshot: > > > > <image.png> > > > > @Michael: "upgrade-run-image show" shows me that I upgraded from 1.3.8 > to 1.4.4. > > Current version is: astlinux-1.4.4 > > Previous saved version is: astlinux-1.3.8 > > > > I did a revert using the second command Michael provided, and that > worked: the system is back again. Thanks! > > I created a snapshot of this machine before the revert, so we can > investigate further what happened if you want. But I guess I can reproduce > this behaviour by upgrading again. > > The (virtual) network adapter in this machine is a legacy one according > to Hyper-V: "Realtek PCIe GBE Family controller". Maybe that is related to > the issue? > > > > Thanks both! > > Regards; > > Gerard > > > > Op za 4 nov 2023 om 18:32 schreef Michael Keuter <li...@mk... > >: > > > > > > > Am 04.11.2023 um 18:16 schrieb Lonnie Abelbeck < > li...@lo...>: > > > > > >> > > >> On Nov 4, 2023, at 11:12 AM, Gerard van Til <ger...@gm...> > wrote: > > >> > > >> Goodafternoon, > > >> > > >> I just upgraded my AstLinux using the UI, but after rebooting, my > eth0 seems to be gone, so I have no internet access anymore. Luckily, this > AstLinux is running on a virtual machine under Windows Hyper-V, and I can > access it using the Hyper-V manager. I can login with the root user, and > should be able to enter commands. If anyone can help me with the Linux > commands to restore this box to its previous version before the upgrade, > that would be great! > > >> > > >> Regards; > > >> Gerard / Netherlands > > > > > > Hi Gerard, > > > > > > First answering your last question, to revert back to the pervious > version, simply: > > > > > > System tab -> System Firmware Upgrade: [ Revert to Previous ] - { > Firmware } - _x_ Confirm > > > > > > System tab -> Reboot/Restart System: [ Now ] - { Reboot } - _x_ Confirm > > > > > > > > > Before you do that, let's try to understand the issue. > > > > > > Are you at the latest AstLinux 1.5.1 ? > > > > > > What is the output of: > > > -- > > > lscpu | grep -i '^hypervisor vendor:' > > > -- > > > > > > What is the output of: > > > -- > > > lsmod > > > -- > > > > > > > > > Sadly I have no way to test Hyper-V, so your help is appreciated. > > > > > > Lonnie > > > > If you cannot access the GUI, the same can be done from the command line: > > > > Check installed versions: > > > > -- > > upgrade-run-image show > > -- > > > > Revert to former version: > > > > -- > > upgrade-run-image revert > > reboot > > -- > > > > Good luck > > > > 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-04 21:43:51
|
Hi Gerard, AstLinux Hyper-V support [1] needs a Board Type of "genx86_64-vm", so check by typing "cat /proc/cmdline" in the CLI and look for the string " astlinux=genx86_64-vm " as that is what you want. If you only have the string " astlinux=genx86_64 " then that is the issue. The (non-VM) Board Type of "genx86_64" may have been able to run Hyper-V at some point, you really need a Board Type of "genx86_64-vm". The VM version has specific hv_netvsc and hv_utils modules that support Hyper-V virtual IO drivers. Note, your upgrade did not change the board type, so you can test the above with the old astlinux-1.3.8 version. Let us know if this is the issue, before any more diagnosis. Lonnie [1] https://doc.astlinux-project.org/userdoc:guest_vm_hyperv > On Nov 4, 2023, at 3:27 PM, Gerard van Til <ger...@gm...> wrote: > > Thanks Michael and Lonnie (I already hoped to receive answers from both of you :-)). > > @Lonnie: unfortunately, I cannot access the GUI anymore, so we'll have to deal with Linux commands > I entered the commands you asked for, and because I have console-only access, I'll have to send the answers as screenshot: > > <image.png> > > @Michael: "upgrade-run-image show" shows me that I upgraded from 1.3.8 to 1.4.4. > Current version is: astlinux-1.4.4 > Previous saved version is: astlinux-1.3.8 > > I did a revert using the second command Michael provided, and that worked: the system is back again. Thanks! > I created a snapshot of this machine before the revert, so we can investigate further what happened if you want. But I guess I can reproduce this behaviour by upgrading again. > The (virtual) network adapter in this machine is a legacy one according to Hyper-V: "Realtek PCIe GBE Family controller". Maybe that is related to the issue? > > Thanks both! > Regards; > Gerard > > Op za 4 nov 2023 om 18:32 schreef Michael Keuter <li...@mk...>: > > > > Am 04.11.2023 um 18:16 schrieb Lonnie Abelbeck <li...@lo...>: > > > >> > >> On Nov 4, 2023, at 11:12 AM, Gerard van Til <ger...@gm...> wrote: > >> > >> Goodafternoon, > >> > >> I just upgraded my AstLinux using the UI, but after rebooting, my eth0 seems to be gone, so I have no internet access anymore. Luckily, this AstLinux is running on a virtual machine under Windows Hyper-V, and I can access it using the Hyper-V manager. I can login with the root user, and should be able to enter commands. If anyone can help me with the Linux commands to restore this box to its previous version before the upgrade, that would be great! > >> > >> Regards; > >> Gerard / Netherlands > > > > Hi Gerard, > > > > First answering your last question, to revert back to the pervious version, simply: > > > > System tab -> System Firmware Upgrade: [ Revert to Previous ] - { Firmware } - _x_ Confirm > > > > System tab -> Reboot/Restart System: [ Now ] - { Reboot } - _x_ Confirm > > > > > > Before you do that, let's try to understand the issue. > > > > Are you at the latest AstLinux 1.5.1 ? > > > > What is the output of: > > -- > > lscpu | grep -i '^hypervisor vendor:' > > -- > > > > What is the output of: > > -- > > lsmod > > -- > > > > > > Sadly I have no way to test Hyper-V, so your help is appreciated. > > > > Lonnie > > If you cannot access the GUI, the same can be done from the command line: > > Check installed versions: > > -- > upgrade-run-image show > -- > > Revert to former version: > > -- > upgrade-run-image revert > reboot > -- > > Good luck > > 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: Gerard v. T. <ger...@gm...> - 2023-11-04 20:27:51
|
Thanks Michael and Lonnie (I already hoped to receive answers from both of
you :-)).
@Lonnie: unfortunately, I cannot access the GUI anymore, so we'll have to
deal with Linux commands
I entered the commands you asked for, and because I have console-only
access, I'll have to send the answers as screenshot:
[image: image.png]
@Michael: "upgrade-run-image show" shows me that I upgraded from 1.3.8 to
1.4.4.
Current version is: astlinux-1.4.4
Previous saved version is: astlinux-1.3.8
I did a revert using the second command Michael provided, and that worked:
the system is back again. Thanks!
I created a snapshot of this machine before the revert, so we can
investigate further what happened if you want. But I guess I can reproduce
this behaviour by upgrading again.
The (virtual) network adapter in this machine is a legacy one according to
Hyper-V: "Realtek PCIe GBE Family controller". Maybe that is related to
the issue?
Thanks both!
Regards;
Gerard
Op za 4 nov 2023 om 18:32 schreef Michael Keuter <li...@mk...>:
>
>
> > Am 04.11.2023 um 18:16 schrieb Lonnie Abelbeck <
> li...@lo...>:
> >
> >>
> >> On Nov 4, 2023, at 11:12 AM, Gerard van Til <ger...@gm...>
> wrote:
> >>
> >> Goodafternoon,
> >>
> >> I just upgraded my AstLinux using the UI, but after rebooting, my eth0
> seems to be gone, so I have no internet access anymore. Luckily, this
> AstLinux is running on a virtual machine under Windows Hyper-V, and I can
> access it using the Hyper-V manager. I can login with the root user, and
> should be able to enter commands. If anyone can help me with the Linux
> commands to restore this box to its previous version before the upgrade,
> that would be great!
> >>
> >> Regards;
> >> Gerard / Netherlands
> >
> > Hi Gerard,
> >
> > First answering your last question, to revert back to the pervious
> version, simply:
> >
> > System tab -> System Firmware Upgrade: [ Revert to Previous ] - {
> Firmware } - _x_ Confirm
> >
> > System tab -> Reboot/Restart System: [ Now ] - { Reboot } - _x_ Confirm
> >
> >
> > Before you do that, let's try to understand the issue.
> >
> > Are you at the latest AstLinux 1.5.1 ?
> >
> > What is the output of:
> > --
> > lscpu | grep -i '^hypervisor vendor:'
> > --
> >
> > What is the output of:
> > --
> > lsmod
> > --
> >
> >
> > Sadly I have no way to test Hyper-V, so your help is appreciated.
> >
> > Lonnie
>
> If you cannot access the GUI, the same can be done from the command line:
>
> Check installed versions:
>
> --
> upgrade-run-image show
> --
>
> Revert to former version:
>
> --
> upgrade-run-image revert
> reboot
> --
>
> Good luck
>
> 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-04 17:32:11
|
> Am 04.11.2023 um 18:16 schrieb Lonnie Abelbeck <li...@lo...>:
>
>>
>> On Nov 4, 2023, at 11:12 AM, Gerard van Til <ger...@gm...> wrote:
>>
>> Goodafternoon,
>>
>> I just upgraded my AstLinux using the UI, but after rebooting, my eth0 seems to be gone, so I have no internet access anymore. Luckily, this AstLinux is running on a virtual machine under Windows Hyper-V, and I can access it using the Hyper-V manager. I can login with the root user, and should be able to enter commands. If anyone can help me with the Linux commands to restore this box to its previous version before the upgrade, that would be great!
>>
>> Regards;
>> Gerard / Netherlands
>
> Hi Gerard,
>
> First answering your last question, to revert back to the pervious version, simply:
>
> System tab -> System Firmware Upgrade: [ Revert to Previous ] - { Firmware } - _x_ Confirm
>
> System tab -> Reboot/Restart System: [ Now ] - { Reboot } - _x_ Confirm
>
>
> Before you do that, let's try to understand the issue.
>
> Are you at the latest AstLinux 1.5.1 ?
>
> What is the output of:
> --
> lscpu | grep -i '^hypervisor vendor:'
> --
>
> What is the output of:
> --
> lsmod
> --
>
>
> Sadly I have no way to test Hyper-V, so your help is appreciated.
>
> Lonnie
If you cannot access the GUI, the same can be done from the command line:
Check installed versions:
--
upgrade-run-image show
--
Revert to former version:
--
upgrade-run-image revert
reboot
--
Good luck
Michael
http://www.mksolutions.info
|
|
From: Lonnie A. <li...@lo...> - 2023-11-04 17:16:55
|
> On Nov 4, 2023, at 11:12 AM, Gerard van Til <ger...@gm...> wrote:
>
> Goodafternoon,
>
> I just upgraded my AstLinux using the UI, but after rebooting, my eth0 seems to be gone, so I have no internet access anymore. Luckily, this AstLinux is running on a virtual machine under Windows Hyper-V, and I can access it using the Hyper-V manager. I can login with the root user, and should be able to enter commands. If anyone can help me with the Linux commands to restore this box to its previous version before the upgrade, that would be great!
>
> Regards;
> Gerard / Netherlands
Hi Gerard,
First answering your last question, to revert back to the pervious version, simply:
System tab -> System Firmware Upgrade: [ Revert to Previous ] - { Firmware } - _x_ Confirm
System tab -> Reboot/Restart System: [ Now ] - { Reboot } - _x_ Confirm
Before you do that, let's try to understand the issue.
Are you at the latest AstLinux 1.5.1 ?
What is the output of:
--
lscpu | grep -i '^hypervisor vendor:'
--
What is the output of:
--
lsmod
--
Sadly I have no way to test Hyper-V, so your help is appreciated.
Lonnie
|
|
From: Gerard v. T. <ger...@gm...> - 2023-11-04 16:12:29
|
Goodafternoon, I just upgraded my AstLinux using the UI, but after rebooting, my eth0 seems to be gone, so I have no internet access anymore. Luckily, this AstLinux is running on a virtual machine under Windows Hyper-V, and I can access it using the Hyper-V manager. I can login with the root user, and should be able to enter commands. If anyone can help me with the Linux commands to restore this box to its previous version before the upgrade, that would be great! Regards; Gerard / Netherlands |
|
From: Lonnie A. <li...@lo...> - 2023-10-21 20:45:59
|
Thanks for the report. Much Appreciated. > On Oct 21, 2023, at 1:52 PM, Gonzalo Ibáñez <gon...@ho...> wrote: > > So far so good; testing Asterisk 20 branch with dahdi enabled. > > g729 binaries compiled for Asterisk 18 work ok with Asterisk 20. > > Thanks to 'ignorestatechanges' and 'ignoredialchanges' variables in cdr.conf I got rid of multiple cdr logs for a single call. > > Regards. > |
|
From: Gonzalo I. <gon...@ho...> - 2023-10-21 18:52:19
|
So far so good; testing Asterisk 20 branch with dahdi enabled. g729 binaries compiled for Asterisk 18 work ok with Asterisk 20. Thanks to 'ignorestatechanges' and 'ignoredialchanges' variables in cdr.conf I got rid of multiple cdr logs for a single call. Regards. ________________________________ |
|
From: Lonnie A. <li...@lo...> - 2023-10-08 17:53:00
|
Announcing AstLinux Pre-Release: astlinux-1.5-5906-4212c3 AstLinux Project -> Development https://www.astlinux-project.org/dev.html ** IMPORTANT NOTICE -- 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 ** 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.197 (version bump), security and bug fixes -- OpenSSL, version bump to 1.1.1w, security fixes: CVE-2023-3446, CVE-2023-3817 -- chrony, version bump to 4.4 -- cron (busybox), add logging methods and levels. The defaults remain the same as previous. New rc.conf variables: CRON_LOG_METHOD and CRON_LOG_LEVEL -- libcurl (curl) version bump to 8.3.0, security fix: CVE-2023-38039 -- libxml2, version bump to 2.11.5 -- msmtp, version bump to 1.8.24 -- netsnmp, version bump to 5.9.4 -- screen, version 4.9.1, security fix: CVE-2023-24626 -- smartctl (smartmontools), version bump to 7.4, drivedb.h snapshot 2023-08-19 -- sqlite, version bump to 3.43.1 -- tinyproxy, version 1.11.1, now included in the standard builds, but disabled by default -- unixodbc, version bump to 2.3.12 -- upgrade-run-image, limit "noram" loop mount from being removed during upgrade. -- unbound, version bump to 1.18.0 -- vnStat, version bump to 2.11 -- zlib, version bump to 1.3 -- ca-certificates, update trusted root certificates 2023-08-22 -- Asterisk 16.30.0 ('16se' version bump) Last Asterisk 16.x "Legacy" version, built --without-pjproject and --without-dahdi -- Asterisk 18.19.0 (version bump) and 20.4.0 (new version) Built --with-pjproject and --with-dahdi Disable: STIR/SHAKEN support -- 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". -- pjsip 2.13.1 (version bump) -- libpri, version bump to 1.6.1 -- 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...> - 2023-09-29 22:44:15
|
Thanks Lonnie Very much appreciated. Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Friday, 29 September 2023 at 4:43 am To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] Stopping logging of Crontab Hi Michael, Looking at the /etc/init.d/crond init script, here [1] If the line "crond" was changed to "crond -L /var/log/crond.log" it would disable syslog and use that file ... but may need rotating if it gets large. If the line "crond" was changed to "crond -L /dev/null" it would disable syslog and disable logging (ie. to /dev/null). BTW, I manually tested both cases to be certain. Lonnie [1] https://github.com/astlinux-project/astlinux/blob/09e87eff8bca82bf4afab8dbe09560737dd80d5c/project/astlinux/target_skeleton/etc/init.d/crond#L38 > On Sep 27, 2023, at 8:01 PM, Michael Knill <mic...@ip...> wrote: > > Hi group > > Replying to this email again. I do understand below but just wondering if there is any way to turn off Cron logging totally or send to a separate log file? > > Regards > Michael Knill > > > From: Lonnie Abelbeck <li...@lo...> > Date: Friday, 31 March 2023 at 1:01 am > To: AstLinux Users Mailing List <ast...@li...> > Subject: Re: [Astlinux-users] Stopping logging of Crontab > > Hi Michael, > > The (busybox) crond daemon has a syslog level setting which defaults to 8, the least verbose log level. So no help there. > > Using the filter for the Status Tab, is a reasonable idea. > > > Personally, when executing shell commands on a regular interval of seconds/minutes, I prefer to use a bash shell script and the sleep builtin. (Using the sleep builtin keeps from spawning a new process whenever 'sleep' is called). > > The simplest example of this is the 'msmtpqueue' bash script [1] > > Basic code setup and loop: > -- > #!/bin/bash > > LOCKFILE="/var/lock/foobar.lock" > > # Robust 'bash' method of creating/testing for a lockfile > if ! ( set -o noclobber; echo "$$" > "$LOCKFILE" ) 2>/dev/null; then > echo "foobar: already running, lockfile \"$LOCKFILE\" exists, process id: $(cat "$LOCKFILE")." > return 9 > fi > > # Load 'sleep' builtin if it exists > if [ -f /usr/lib/bash/sleep ]; then > enable -f /usr/lib/bash/sleep sleep > fi > > #seconds to wait > wait=300 > > trap 'rm -f "$LOCKFILE"; exit $?' INT TERM EXIT > > while true; do > # do stuff > > sleep $wait > done > > rm -f "$LOCKFILE" > trap - INT TERM EXIT > -- > > Look at the actual code [1] for finer details. Another fairly simple example, asterisk-sip-monitor [2] which adds a PID file that can be removed to exit the script. > > Lonnie > > [1] https://github.com/astlinux-project/astlinux/blob/master/package/msmtp/msmtpqueue.sh > > [2] https://github.com/astlinux-project/astlinux/blob/master/package/asterisk/asterisk-sip-monitor > > > > > > > On Mar 29, 2023, at 11:39 PM, Michael Knill <mic...@ip...> wrote: > > > > Short of putting in a filter for the Status Tab, is there any way to stop Crontab logging to Syslog. > > I now have a process that is run every 10 minutes and its annoying that it logs to Syslog each time. > > > > Regards > > > > Michael Knill > > Managing Director > > > > D: +61 2 6189 1360 > > P: +61 2 6140 4656 > > E: mic...@ip... > > W: ipcsolutions.com.au > > > > > > _______________________________________________ > 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-09-28 18:42:51
|
Hi Michael, Looking at the /etc/init.d/crond init script, here [1] If the line "crond" was changed to "crond -L /var/log/crond.log" it would disable syslog and use that file ... but may need rotating if it gets large. If the line "crond" was changed to "crond -L /dev/null" it would disable syslog and disable logging (ie. to /dev/null). BTW, I manually tested both cases to be certain. Lonnie [1] https://github.com/astlinux-project/astlinux/blob/09e87eff8bca82bf4afab8dbe09560737dd80d5c/project/astlinux/target_skeleton/etc/init.d/crond#L38 > On Sep 27, 2023, at 8:01 PM, Michael Knill <mic...@ip...> wrote: > > Hi group > > Replying to this email again. I do understand below but just wondering if there is any way to turn off Cron logging totally or send to a separate log file? > > Regards > Michael Knill > > > From: Lonnie Abelbeck <li...@lo...> > Date: Friday, 31 March 2023 at 1:01 am > To: AstLinux Users Mailing List <ast...@li...> > Subject: Re: [Astlinux-users] Stopping logging of Crontab > > Hi Michael, > > The (busybox) crond daemon has a syslog level setting which defaults to 8, the least verbose log level. So no help there. > > Using the filter for the Status Tab, is a reasonable idea. > > > Personally, when executing shell commands on a regular interval of seconds/minutes, I prefer to use a bash shell script and the sleep builtin. (Using the sleep builtin keeps from spawning a new process whenever 'sleep' is called). > > The simplest example of this is the 'msmtpqueue' bash script [1] > > Basic code setup and loop: > -- > #!/bin/bash > > LOCKFILE="/var/lock/foobar.lock" > > # Robust 'bash' method of creating/testing for a lockfile > if ! ( set -o noclobber; echo "$$" > "$LOCKFILE" ) 2>/dev/null; then > echo "foobar: already running, lockfile \"$LOCKFILE\" exists, process id: $(cat "$LOCKFILE")." > return 9 > fi > > # Load 'sleep' builtin if it exists > if [ -f /usr/lib/bash/sleep ]; then > enable -f /usr/lib/bash/sleep sleep > fi > > #seconds to wait > wait=300 > > trap 'rm -f "$LOCKFILE"; exit $?' INT TERM EXIT > > while true; do > # do stuff > > sleep $wait > done > > rm -f "$LOCKFILE" > trap - INT TERM EXIT > -- > > Look at the actual code [1] for finer details. Another fairly simple example, asterisk-sip-monitor [2] which adds a PID file that can be removed to exit the script. > > Lonnie > > [1] https://github.com/astlinux-project/astlinux/blob/master/package/msmtp/msmtpqueue.sh > > [2] https://github.com/astlinux-project/astlinux/blob/master/package/asterisk/asterisk-sip-monitor > > > > > > > On Mar 29, 2023, at 11:39 PM, Michael Knill <mic...@ip...> wrote: > > > > Short of putting in a filter for the Status Tab, is there any way to stop Crontab logging to Syslog. > > I now have a process that is run every 10 minutes and its annoying that it logs to Syslog each time. > > > > Regards > > > > Michael Knill > > Managing Director > > > > D: +61 2 6189 1360 > > P: +61 2 6140 4656 > > E: mic...@ip... > > W: ipcsolutions.com.au > > > > > > _______________________________________________ > 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...> - 2023-09-28 01:01:36
|
Hi group Replying to this email again. I do understand below but just wondering if there is any way to turn off Cron logging totally or send to a separate log file? Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Date: Friday, 31 March 2023 at 1:01 am To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] Stopping logging of Crontab Hi Michael, The (busybox) crond daemon has a syslog level setting which defaults to 8, the least verbose log level. So no help there. Using the filter for the Status Tab, is a reasonable idea. Personally, when executing shell commands on a regular interval of seconds/minutes, I prefer to use a bash shell script and the sleep builtin. (Using the sleep builtin keeps from spawning a new process whenever 'sleep' is called). The simplest example of this is the 'msmtpqueue' bash script [1] Basic code setup and loop: -- #!/bin/bash LOCKFILE="/var/lock/foobar.lock" # Robust 'bash' method of creating/testing for a lockfile if ! ( set -o noclobber; echo "$$" > "$LOCKFILE" ) 2>/dev/null; then echo "foobar: already running, lockfile \"$LOCKFILE\" exists, process id: $(cat "$LOCKFILE")." return 9 fi # Load 'sleep' builtin if it exists if [ -f /usr/lib/bash/sleep ]; then enable -f /usr/lib/bash/sleep sleep fi #seconds to wait wait=300 trap 'rm -f "$LOCKFILE"; exit $?' INT TERM EXIT while true; do # do stuff sleep $wait done rm -f "$LOCKFILE" trap - INT TERM EXIT -- Look at the actual code [1] for finer details. Another fairly simple example, asterisk-sip-monitor [2] which adds a PID file that can be removed to exit the script. Lonnie [1] https://github.com/astlinux-project/astlinux/blob/master/package/msmtp/msmtpqueue.sh [2] https://github.com/astlinux-project/astlinux/blob/master/package/asterisk/asterisk-sip-monitor > On Mar 29, 2023, at 11:39 PM, Michael Knill <mic...@ip...> wrote: > > Short of putting in a filter for the Status Tab, is there any way to stop Crontab logging to Syslog. > I now have a process that is run every 10 minutes and its annoying that it logs to Syslog each time. > > Regards > > Michael Knill > Managing Director > > D: +61 2 6189 1360 > P: +61 2 6140 4656 > E: mic...@ip... > W: ipcsolutions.com.au > _______________________________________________ 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: Silver <ne...@gm...> - 2023-09-27 09:02:43
|
Hello, Sorry I'm again I have bad alix board with 1 Lan and VGA i would like to replace it trough Alix2e13 and simple clone the USB Stick. But I have trouble with new Astlinux installer, I can install on Alix1 but not on Alix2e13 The idea was only restore USB Stick with last backupimage but this not work because Alix2e13 won't boot from USB, Alix2e13 only bootig from SD card and I don't have serial console. If I restore my last backup image to CF card can I edit runix config to use it with serial console? regards Nedi |
|
From: nedi <ne...@gm...> - 2023-09-26 22:16:22
|
Hello Michael, Thanks I tried using the same USB stick on an old Alix board, and my serial connection works with a baud rate of 19200. However, when I use the Alix2e13 board, I'm only getting strange characters. After changing the baud rate to 38400, it works correctly. I've noticed that the Alix2e13 board's serial connection only works with a baud rate of 38400.I can see the boot process and error message when I try to boot from my USB install drive on the Alix2e13 board, I encounter the error message "01f0 no drive found! No booting device available." Interestingly, the same USB drive successfully boots on the Alix1 board. Any ideas on how to resolve this issue? if I use a CF Card wit installer ( serial iso ) , I can boot must change to 19200 baud and the installer on the Alix2e13 board works but I cant install on this boar without USB boot stick that work. Tomorow i will try install it on alix1 board to the cf card and after instal try it in Alix2e13. I would prefer to use a USB stick. Is there a way to run the Alix1 image on CF Card to the Alix2e13 board and make the necessary changes to enable booting and troubleshoot through the terminal? nedi > Am 26.09.2023 um 21:53 schrieb Michael Keuter <li...@mk...>: > > <screen-baud-rate-output.png> > Screen command set baud rate for terminal communication > cyberciti.biz > <https://www.cyberciti.biz/faq/unix-linux-apple-osx-bsd-screen-set-baud-rate/>Screen command set baud rate for terminal communication <https://www.cyberciti.biz/faq/unix-linux-apple-osx-bsd-screen-set-baud-rate/> > cyberciti.biz <https://www.cyberciti.biz/faq/unix-linux-apple-osx-bsd-screen-set-baud-rate/> > 19200 8N1 is the right baudrate for Alix on the 1.2.10 ISO. > > userdoc:legacy-installer-iso [AstLinux Documentation] > doc.astlinux-project.org > <apple-touch-icon.png> > <http://doc.astlinux-project.org/userdoc:legacy-installer-iso>userdoc:legacy-installer-iso [AstLinux Documentation] <http://doc.astlinux-project.org/userdoc:legacy-installer-iso> > doc.astlinux-project.org <http://doc.astlinux-project.org/userdoc:legacy-installer-iso> <apple-touch-icon.png> <http://doc.astlinux-project.org/userdoc:legacy-installer-iso> > > Sent from a mobile device. > > Michael Keuter > >> Am 26.09.2023 um 21:33 schrieb nedi <ne...@gm...>: >> >> Hello Michael, >> >> I've tried everything, but I can't seem to read the USB stick. >> >> I have two Alix devices with 3 LAN ports and a serial connection (Alix2e13). I'm interested in migrating all the settings to the same AstLinux version. Is this possible? >> >> I attempted to use the AstLinux 1.2.10 serial ISO with a serial terminal, but I'm only getting strange characters when trying to access AstLinux via a serial connection on my Mac using both the "serial" app and the Mac Terminal. >> >> I have a USB-to-serial adapter and I've tried the following commands: >> >> • screen /dev/cu.usbserial 19200 >> • screen /dev/cu.usbserial 19200,cs8 >> • screen /dev/cu.usbserial 19200n8 >> • screen /dev/cu.usbserial 115200 >> Is this the correct ISO for the Alix2e13? Also, is it possible to restore the last backup on this new installation? >> >> Best regards, Nedi >>> Am 26.09.2023 um 11:23 schrieb Michael Keuter <li...@mk...>: >>> >>> >>>> Am 26.09.2023 um 10:53 schrieb nedi <ne...@gm...>: >>>> >>>> Hello, >>>> >>>> I have an Astlinux installation using the old astlinux astlinux-1.2.8 i586 - Asterisk 1.8.32.3 and alix board. >>>> Astlinus is on Kingston USB stick. The customer do a hard power-down by unplugging the power cord and the pbx won't boot. has anyone the soulution to fix that. >>>> on boot I get errors >>>> squashfs error unable to read dpage ,block xxxx >>>> and read on /mnt/root/bzimage failed :input output error >>>> >>>> I hope someone can help me to fix that without new install >>>> regards nedi >>> >>> >>> In the Syslinux bootloader you can select "shell" (instead of the default "runnix") to skip booting into AstLinux and try to repair the filesystem with "fsck": >>> >>> https://doc.astlinux-project.org/userdoc:system-boot-process >>> >>> 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. <li...@mk...> - 2023-09-26 19:53:53
|
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div style="display: block;" class=""><div style="-webkit-user-select: all; -webkit-user-drag: element; display: inline-block;" class="apple-rich-link" draggable="true" role="link" data-url="https://www.cyberciti.biz/faq/unix-linux-apple-osx-bsd-screen-set-baud-rate/"><a style="border-radius:10px;font-family:-apple-system, Helvetica, Arial, sans-serif;display:block;-webkit-user-select:none;width:228px;user-select:none;-webkit-user-modify:read-only;user-modify:read-only;overflow:hidden;text-decoration:none;" class="lp-rich-link" rel="nofollow" href="https://www.cyberciti.biz/faq/unix-linux-apple-osx-bsd-screen-set-baud-rate/" dir="ltr" role="button" draggable="false" width="228"><table style="table-layout:fixed;border-collapse:collapse;width:228px;background-color:#DFDFE1;font-family:-apple-system, Helvetica, Arial, sans-serif;" class="lp-rich-link-emailBaseTable" cellpadding="0" cellspacing="0" border="0" width="228"><tbody><tr><td vertical-align="center" align="center"><img style="width:228px;filter:brightness(0.97);height:285px;" width="228" height="285" draggable="false" class="lp-rich-link-mediaImage" alt="screen-baud-rate-output.png" src="cid:CF9B07A9-0BE4-4422-87C2-FD35EB00417D"></td></tr><tr><td vertical-align="center"><table bgcolor="#DFDFE1" cellpadding="0" cellspacing="0" width="228" style="font-family:-apple-system, Helvetica, Arial, sans-serif;table-layout:fixed;background-color:rgba(223, 223, 225, 1);" class="lp-rich-link-captionBar"><tbody><tr><td style="padding:8px 0px 8px 0px;" class="lp-rich-link-captionBar-textStackItem"><div style="max-width:100%;margin:0px 16px 0px 16px;overflow:hidden;" class="lp-rich-link-captionBar-textStack"><div style="word-wrap:break-word;font-weight:500;font-size:12px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-topCaption-leading"><a rel="nofollow" href="https://www.cyberciti.biz/faq/unix-linux-apple-osx-bsd-screen-set-baud-rate/" style="text-decoration: none" draggable="false"><font color="#000000" style="color: rgba(0, 0, 0, 1);">Screen command set baud rate for terminal communication</font></a></div><div style="word-wrap:break-word;font-weight:400;font-size:11px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-bottomCaption-leading"><a rel="nofollow" href="https://www.cyberciti.biz/faq/unix-linux-apple-osx-bsd-screen-set-baud-rate/" style="text-decoration: none" draggable="false"><font color="#A2A2A9" style="color: rgba(60, 60, 67, 0.6);">cyberciti.biz</font></a></div></div></td></tr></tbody></table></td></tr></tbody></table></a></div></div><br>19200 8N1 is the right baudrate for Alix on the 1.2.10 ISO.<div><br></div><div><div style="display: block;" class=""><div style="-webkit-user-select: all; -webkit-user-drag: element; display: inline-block;" class="apple-rich-link" draggable="true" role="link" data-url="http://doc.astlinux-project.org/userdoc:legacy-installer-iso"><a style="border-radius:10px;font-family:-apple-system, Helvetica, Arial, sans-serif;display:block;-webkit-user-select:none;width:300px;user-select:none;-webkit-user-modify:read-only;user-modify:read-only;overflow:hidden;text-decoration:none;" class="lp-rich-link" rel="nofollow" href="http://doc.astlinux-project.org/userdoc:legacy-installer-iso" dir="ltr" role="button" draggable="false" width="300"><table style="table-layout:fixed;border-collapse:collapse;width:300px;background-color:#DFDFE1;font-family:-apple-system, Helvetica, Arial, sans-serif;" class="lp-rich-link-emailBaseTable" cellpadding="0" cellspacing="0" border="0" width="300"><tbody><tr><td vertical-align="center"><table bgcolor="#DFDFE1" cellpadding="0" cellspacing="0" width="300" style="font-family:-apple-system, Helvetica, Arial, sans-serif;table-layout:fixed;background-color:rgba(223, 223, 225, 1);" class="lp-rich-link-captionBar"><tbody><tr><td style="padding:8px 0px 8px 0px;" class="lp-rich-link-captionBar-textStackItem"><div style="max-width:100%;margin:0px 16px 0px 16px;overflow:hidden;" class="lp-rich-link-captionBar-textStack"><div style="word-wrap:break-word;font-weight:500;font-size:12px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-topCaption-leading"><a rel="nofollow" href="http://doc.astlinux-project.org/userdoc:legacy-installer-iso" style="text-decoration: none" draggable="false"><font color="#000000" style="color: rgba(0, 0, 0, 1);">userdoc:legacy-installer-iso [AstLinux Documentation]</font></a></div><div style="word-wrap:break-word;font-weight:400;font-size:11px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-bottomCaption-leading"><a rel="nofollow" href="http://doc.astlinux-project.org/userdoc:legacy-installer-iso" style="text-decoration: none" draggable="false"><font color="#A2A2A9" style="color: rgba(60, 60, 67, 0.6);">doc.astlinux-project.org</font></a></div></div></td><td style="padding:6px 12px 6px 0px;" class="lp-rich-link-captionBar-rightIconItem" width="36"><a rel="nofollow" href="http://doc.astlinux-project.org/userdoc:legacy-installer-iso" draggable="false"><img style="pointer-events:none !important;display:inline-block;width:36px;height:36px;border-radius:3px;" width="36" height="36" draggable="false" class="lp-rich-link-captionBar-rightIcon" alt="apple-touch-icon.png" src="cid:C6011457-AEE3-4F40-B4A5-643C4C38B9E1"></a></td></tr></tbody></table></td></tr></tbody></table></a></div><br></div><div><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 26.09.2023 um 21:33 schrieb nedi <ne...@gm...>:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>Hello Michael,</span><br><span></span><br><span>I've tried everything, but I can't seem to read the USB stick.</span><br><span></span><br><span>I have two Alix devices with 3 LAN ports and a serial connection (Alix2e13). I'm interested in migrating all the settings to the same AstLinux version. Is this possible?</span><br><span></span><br><span>I attempted to use the AstLinux 1.2.10 serial ISO with a serial terminal, but I'm only getting strange characters when trying to access AstLinux via a serial connection on my Mac using both the "serial" app and the Mac Terminal.</span><br><span></span><br><span>I have a USB-to-serial adapter and I've tried the following commands:</span><br><span></span><br><span> • screen /dev/cu.usbserial 19200</span><br><span> • screen /dev/cu.usbserial 19200,cs8</span><br><span> • screen /dev/cu.usbserial 19200n8</span><br><span> • screen /dev/cu.usbserial 115200</span><br><span>Is this the correct ISO for the Alix2e13? Also, is it possible to restore the last backup on this new installation?</span><br><span></span><br><span>Best regards, Nedi</span><br><blockquote type="cite"><span>Am 26.09.2023 um 11:23 schrieb Michael Keuter <li...@mk...>:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>Am 26.09.2023 um 10:53 schrieb nedi <ne...@gm...>:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Hello,</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I have an Astlinux installation using the old astlinux astlinux-1.2.8 i586 - Asterisk 1.8.32.3 and alix board. </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Astlinus is on Kingston USB stick. The customer do a hard power-down by unplugging the power cord and the pbx won't boot. has anyone the soulution to fix that. </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>on boot I get errors</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>squashfs error unable to read dpage ,block xxxx</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>and read on /mnt/root/bzimage failed :input output error</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I hope someone can help me to fix that without new install</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>regards nedi </span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>In the Syslinux bootloader you can select "shell" (instead of the default "runnix") to skip booting into AstLinux and try to repair the filesystem with "fsck":</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>https://doc.astlinux-project.org/userdoc:system-boot-process</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Michael</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>http://www.mksolutions.info</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>_______________________________________________</span><br></blockquote><blockquote type="cite"><span>Astlinux-users mailing list</span><br></blockquote><blockquote type="cite"><span>Ast...@li...</span><br></blockquote><blockquote type="cite"><span>https://lists.sourceforge.net/lists/listinfo/astlinux-users</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....</span><br></blockquote><span></span><br><span></span><br><span></span><br><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></div></body></html> |
|
From: nedi <ne...@gm...> - 2023-09-26 19:32:07
|
Hello Michael, I've tried everything, but I can't seem to read the USB stick. I have two Alix devices with 3 LAN ports and a serial connection (Alix2e13). I'm interested in migrating all the settings to the same AstLinux version. Is this possible? I attempted to use the AstLinux 1.2.10 serial ISO with a serial terminal, but I'm only getting strange characters when trying to access AstLinux via a serial connection on my Mac using both the "serial" app and the Mac Terminal. I have a USB-to-serial adapter and I've tried the following commands: • screen /dev/cu.usbserial 19200 • screen /dev/cu.usbserial 19200,cs8 • screen /dev/cu.usbserial 19200n8 • screen /dev/cu.usbserial 115200 Is this the correct ISO for the Alix2e13? Also, is it possible to restore the last backup on this new installation? Best regards, Nedi > Am 26.09.2023 um 11:23 schrieb Michael Keuter <li...@mk...>: > > >> Am 26.09.2023 um 10:53 schrieb nedi <ne...@gm...>: >> >> Hello, >> >> I have an Astlinux installation using the old astlinux astlinux-1.2.8 i586 - Asterisk 1.8.32.3 and alix board. >> Astlinus is on Kingston USB stick. The customer do a hard power-down by unplugging the power cord and the pbx won't boot. has anyone the soulution to fix that. >> on boot I get errors >> squashfs error unable to read dpage ,block xxxx >> and read on /mnt/root/bzimage failed :input output error >> >> I hope someone can help me to fix that without new install >> regards nedi > > > In the Syslinux bootloader you can select "shell" (instead of the default "runnix") to skip booting into AstLinux and try to repair the filesystem with "fsck": > > https://doc.astlinux-project.org/userdoc:system-boot-process > > 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-09-26 09:54:25
|
> Am 26.09.2023 um 10:53 schrieb nedi <ne...@gm...>: > > Hello, > > I have an Astlinux installation using the old astlinux astlinux-1.2.8 i586 - Asterisk 1.8.32.3 and alix board. > Astlinus is on Kingston USB stick. The customer do a hard power-down by unplugging the power cord and the pbx won't boot. has anyone the soulution to fix that. > on boot I get errors > squashfs error unable to read dpage ,block xxxx > and read on /mnt/root/bzimage failed :input output error > > I hope someone can help me to fix that without new install > regards nedi In the Syslinux bootloader you can select "shell" (instead of the default "runnix") to skip booting into AstLinux and try to repair the filesystem with "fsck": https://doc.astlinux-project.org/userdoc:system-boot-process Michael http://www.mksolutions.info |
|
From: nedi <ne...@gm...> - 2023-09-26 09:07:15
|
Hello, I have an Astlinux installation using the old astlinux astlinux-1.2.8 i586 - Asterisk 1.8.32.3 and alix board. Astlinus is on Kingston USB stick. The customer do a hard power-down by unplugging the power cord and the pbx won't boot. has anyone the soulution to fix that. on boot I get errors squashfs error unable to read dpage ,block xxxx and read on /mnt/root/bzimage failed :input output error I hope someone can help me to fix that without new install regards nedi |
|
From: Lonnie A. <li...@lo...> - 2023-09-20 17:02:44
|
Try looking via: -- grep -rs 'SYSLOGHOST=' /etc/ grep -rs 'SYSLOGHOST=' /mnt/kd/ grep -rs 'SYSLOGHOST=' /mnt/asturw/ -- Lonnie > On Sep 20, 2023, at 11:56 AM, Ionel Chila via Astlinux-users <ast...@li...> wrote: > > Thanks Lonnie and that is where I am going crazy LOL. In my rc.conf I have nothing defined for SYSLOGHOST= > > Not sure if I plugged that value somewhere else? Or I have a startup script I know is running and sending logs to my .77 :) > > > >> On Sep 20, 2023, at 11:43 AM, Lonnie Abelbeck <li...@lo...> wrote: >> >> >> >>> On Sep 20, 2023, at 10:37 AM, Ionel Chila via Astlinux-users <ast...@li...> wrote: >>> >>> For the love of my life I can't find the settings from my syslog that is currently sending logs to an external server. Can't find the config file nor anyweher in the web gui menu? Am I going crazy here? >>> I know I am sending stuff out :) >>> >>> HOME-PBX init.d # ps -ef |grep syslog >>> 310 root syslogd -s 1024 -b 2 >>> 935 root syslogd -R 192.168.0.77:514 -L -O /var/log/messages >> >> Hi Ionel, >> >> You have the SYSLOGHOST variable defined (ie. SYSLOGHOST="192.168.0.77:514") >> >> For documentation reference look in /stat/etc/rc.conf [1] >> >> Lonnie >> >> [1] https://github.com/astlinux-project/astlinux/blob/0c813dffa5d59ffa34d39624eb6a63ae7662a535/project/astlinux/target_skeleton/stat/etc/rc.conf#L476 >> >> >> >> _______________________________________________ >> 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.... |
63 messages has been excluded from this view by a project administrator.
