From rbalashevich at gmail.com Tue Jun 2 23:43:38 2020 From: rbalashevich at gmail.com (Roman Balashevich) Date: Tue, 2 Jun 2020 23:43:38 +0300 Subject: Ole hadash is in need of DDR2 RAM Message-ID: Hello all. Friends, any advice? Where is possible to find legacy PC2-6400 DDR2 RAM modules in Gush Dan? After my Aliyah around a year ago... I've got an old PC on a funny occasion. There are 2*1GB sticks here, but it is not enough for my Ubuntu. Maybe someone here can help? This OEM dektop board is MSI MS-7525, supports maximum 2*2GB. Btw, I'm in Petah Tikva. From efraim at flashner.co.il Thu Jun 4 17:06:10 2020 From: efraim at flashner.co.il (Efraim Flashner) Date: Thu, 4 Jun 2020 17:06:10 +0300 Subject: Ole hadash is in need of DDR2 RAM In-Reply-To: References: Message-ID: <20200604140610.GF7397@E5400> I ordered from Ali Express when I needed some 2GB sticks almost a year ago. $7.44 for 2. I haven't looked closer to see if it's available here though. On Tue, Jun 02, 2020 at 11:43:38PM +0300, Roman Balashevich wrote: > Hello all. > Friends, any advice? > Where is possible to find legacy PC2-6400 DDR2 RAM modules in Gush Dan? > After my Aliyah around a year ago... I've got an old PC on a funny occasion. > There are 2*1GB sticks here, but it is not enough for my Ubuntu. > Maybe someone here can help? This OEM dektop board is MSI MS-7525, > supports maximum 2*2GB. Btw, I'm in Petah Tikva. > > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il -- Efraim Flashner ????? ????? GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From uri at speedy.net Wed Jun 10 17:13:02 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Wed, 10 Jun 2020 17:13:02 +0300 Subject: Web hosting providers (OT) Message-ID: Hi, I'm thinking about the option to deploy a new server for testing speed at https://www.speedtest.net/ . Do you know which hosting providers you recommend with inexpensive but strong servers? I'm using Digital Ocean, and in the past I used CloudSigma, Amazon EC2 and Rackspace. What's important to me is the price and the good performance, and good network speed. I read on https://www.speedtest.net/speedtest-servers and checked the minimal hardware they want (https://support.ookla.com/hc/en-us/articles/234578628: Recommended Quad Core 8GB 2Gbps 1GB) - do they mean a dedicated CPU or can I used shared CPU like in Digital Ocean? And how much will such a server cost me? And by the way, I'm looking for locations where they don't have many servers, such as Geneva or Seoul. But it all depends on the cost also, I might prefer a cheaper server in a location where they have many servers. What do you recommend? I currently have a few servers hosted at Digital Ocean in Amsterdam, and I might use one of them - but it will need to be upgraded in memory and CPU. I think it's not a good idea to use my production server, but I'm thinking about using my staging server. Do you think it's a good idea? The operating system I feel most comfortable with for servers is Ubuntu (LTS). By the way, I'm thinking maybe to buy a new computer, but I'm using MS-Excel and Word, so I guess I'm stuck with Microsoft Windows. By the way it's a genius way to promote Windows - by making people to need Word and Excel (and Powerpoint). And I'm also using TortoiseGit. Please don't recommend to me alternatives for Word or Excel which are not the real thing (been there, done that). I have bash shell on Windows and I can do many things from the shell, so I feel like using Linux even on Windows. Thanks, Uri. ???? uri at speedy.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Wed Jun 10 17:28:07 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Wed, 10 Jun 2020 17:28:07 +0300 Subject: Ubuntu Message-ID: Hi, I'm sorry for posting twice in the same day to the same mailing list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a few production servers (one of them I upgraded a few months ago from 14.04). How important it is to upgrade the OS version, or can I keep it like this? I'm afraid that things will break up if I upgrade. And if I upgrade, should I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently released, it might have bugs which will be fixed later, and I prefer not to use the first version of 20.04 but to wait about one year before I use it. Is there a risk with keeping using 18.04.3? Or should I upgrade at least to 18.04.4? Thanks, Uri. ???? uri at speedy.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From geoffreymendelson at gmail.com Wed Jun 10 17:34:02 2020 From: geoffreymendelson at gmail.com (Geoffrey Mendelson) Date: Wed, 10 Jun 2020 17:34:02 +0300 Subject: Ubuntu In-Reply-To: References: Message-ID: <8f12a429-faaf-4f1d-8df2-cce5260e910e@Spark> I am running ubuntu lts 10.something on a server I am afraid will break. Geoff. -- Geoffrey S. Mendelson, N3OWJ/4X1GM/KBUH7245/KBUW5379 Jerusalem, Israel On Jun 10, 2020, 5:30 PM +0300, ???? , wrote: > Hi, > > I'm sorry for posting twice in the same day to the same mailing list. But I have a question: I'm using?Ubuntu 18.04.3 LTS for a few production servers (one of them I upgraded a?few months ago from 14.04). How important it is to upgrade the OS version, or can I keep it like this? I'm afraid that things will break up if I upgrade. And if I upgrade, should I upgrade to?Ubuntu 18.04.4 or 20.04? I think since?20.04 has been recently released, it might have bugs which will be fixed later, and I prefer not to use the first version of 20.04 but to wait about one year before I use it. Is there a risk with keeping using 18.04.3? Or should I upgrade?at least to 18.04.4? > > Thanks, > Uri. > ???? > uri at speedy.net > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Wed Jun 10 17:35:16 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Wed, 10 Jun 2020 17:35:16 +0300 Subject: Ubuntu In-Reply-To: <8f12a429-faaf-4f1d-8df2-cce5260e910e@Spark> References: <8f12a429-faaf-4f1d-8df2-cce5260e910e@Spark> Message-ID: Hi, Actually I had a website running on Ubuntu 10.04 LTS from 2012 to 2019 and it didn't break, and I didn't upgrade. ???? uri at speedy.net On Wed, Jun 10, 2020 at 5:34 PM Geoffrey Mendelson < geoffreymendelson at gmail.com> wrote: > I am running ubuntu lts 10.something on a server I am afraid will break. > > Geoff. > > -- > Geoffrey S. Mendelson, N3OWJ/4X1GM/KBUH7245/KBUW5379 Jerusalem, Israel > On Jun 10, 2020, 5:30 PM +0300, ???? , wrote: > > Hi, > > I'm sorry for posting twice in the same day to the same mailing list. But > I have a question: I'm using Ubuntu 18.04.3 LTS for a few production > servers (one of them I upgraded a few months ago from 14.04). How important > it is to upgrade the OS version, or can I keep it like this? I'm afraid > that things will break up if I upgrade. And if I upgrade, should I upgrade > to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently released, > it might have bugs which will be fixed later, and I prefer not to use the > first version of 20.04 but to wait about one year before I use it. Is there > a risk with keeping using 18.04.3? Or should I upgrade at least to 18.04.4? > > Thanks, > Uri. > ???? > uri at speedy.net > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shlomif at gmail.com Wed Jun 10 18:19:05 2020 From: shlomif at gmail.com (Shlomi Fish) Date: Wed, 10 Jun 2020 18:19:05 +0300 Subject: Ubuntu In-Reply-To: References: Message-ID: Hi Uri! ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? > Hi, > > I'm sorry for posting twice in the same day to the same mailing list. But > I have a question: I'm using Ubuntu 18.04.3 LTS for a few production > servers (one of them I upgraded a few months ago from 14.04). How important > it is to upgrade the OS version, or can I keep it like this? I'm afraid > that things will break up if I upgrade. And if I upgrade, should I upgrade > to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently released, > it might have bugs which will be fixed later, and I prefer not to use the > first version of 20.04 but to wait about one year before I use it. Is there > a risk with keeping using 18.04.3? Or should I upgrade at least to 18.04.4? > > I've answered the general question here: https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality Quoting it: Will a change I would like to do break some functionality? As the aphorism goes: The difference between theory and practice is that in theory, there is no difference between theory and practice, while in practice, there is.. There is usually a risk, however small, that a change will break some functionality. With good tooling (such as https://en.wikipedia.org/wiki/Version_control , https://en.wikipedia.org/wiki/Virtual_machine and https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should be relatively easy to revert a change which introduced regressions, and you should do adequate testing. A change may have to be avoided due to being estimated as too time or money consuming, or as having too little gain. However, promising changes should be attempted because: 1. "No guts - no glory." 2. What does "if it ain't broke, don't fix it" really mean? 3. If you never change anything, your project won't progress. ---------- While you may break some functionality by updating to 18.04.04 , you also risk being affected by known security vulnerabilities (which may also break functionality sooner or later). There is a concept of https://en.wikipedia.org/wiki/Technical_debt . Regarding updating to 20.04, it is likely more time consuming and may have more breaking changes, and you may not need all the newest and shiniest software versions there, and you may wish to only update to ubuntu 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being unusable or unstable, but I'm quite out of the loop. Good luck! > Thanks, > Uri. > ???? > uri at speedy.net > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > -- Shlomi Fish https://www.shlomifish.org/ Buddha has the Chuck Norris nature. Please reply to list if it's a mailing list post - http://shlom.in/reply . -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Wed Jun 10 18:31:54 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Wed, 10 Jun 2020 18:31:54 +0300 Subject: Ubuntu In-Reply-To: References: Message-ID: Thank you, Shlomi. I like the difference between theory and practice. ???? uri at speedy.net On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish wrote: > Hi Uri! > > ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? > >> Hi, >> >> I'm sorry for posting twice in the same day to the same mailing list. But >> I have a question: I'm using Ubuntu 18.04.3 LTS for a few production >> servers (one of them I upgraded a few months ago from 14.04). How important >> it is to upgrade the OS version, or can I keep it like this? I'm afraid >> that things will break up if I upgrade. And if I upgrade, should I upgrade >> to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently released, >> it might have bugs which will be fixed later, and I prefer not to use the >> first version of 20.04 but to wait about one year before I use it. Is there >> a risk with keeping using 18.04.3? Or should I upgrade at least to 18.04.4? >> >> > I've answered the general question here: > > > https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality > > Quoting it: > > Will a change I would like to do break some functionality? > > As the aphorism > > goes: The difference between theory and practice is that in theory, there > is no difference between theory and practice, while in practice, there is.. > There is usually a risk, however small, that a change will break some > functionality. With good tooling (such as > https://en.wikipedia.org/wiki/Version_control , > https://en.wikipedia.org/wiki/Virtual_machine and > https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should be > relatively easy to revert a change which introduced regressions, and you > should do adequate testing. > > A change may have to be avoided due to being estimated as too time or > money consuming, or as having too little gain. However, promising changes > should be attempted because: > > 1. "No guts - no glory." > 2. What does "if it ain't broke, don't fix it" really mean? > > 3. If you never change anything, your project won't progress. > > ---------- > While you may break some functionality by updating to 18.04.04 , you also > risk being affected by known security vulnerabilities (which may also break > functionality sooner or later). There is a concept of > https://en.wikipedia.org/wiki/Technical_debt . > > Regarding updating to 20.04, it is likely more time consuming and may have > more breaking changes, and you may not need all the newest and shiniest > software versions there, and you may wish to only update to ubuntu > 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being > unusable or unstable, but I'm quite out of the loop. > > Good luck! > > > >> Thanks, >> Uri. >> ???? >> uri at speedy.net >> _______________________________________________ >> Linux-il mailing list >> Linux-il at cs.huji.ac.il >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >> > > > -- > Shlomi Fish https://www.shlomifish.org/ > > Buddha has the Chuck Norris nature. > > Please reply to list if it's a mailing list post - http://shlom.in/reply . > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Wed Jun 10 18:42:14 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Wed, 10 Jun 2020 18:42:14 +0300 Subject: Ubuntu In-Reply-To: References: Message-ID: Hi, Actually I have a staging server which I can upgrade first to 18.04.4 to see if it works, or if something breaks. But I didn't find it on Google - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without upgrading it to 20.04? ???? uri at speedy.net On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish wrote: > Hi Uri! > > ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? > >> Hi, >> >> I'm sorry for posting twice in the same day to the same mailing list. But >> I have a question: I'm using Ubuntu 18.04.3 LTS for a few production >> servers (one of them I upgraded a few months ago from 14.04). How important >> it is to upgrade the OS version, or can I keep it like this? I'm afraid >> that things will break up if I upgrade. And if I upgrade, should I upgrade >> to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently released, >> it might have bugs which will be fixed later, and I prefer not to use the >> first version of 20.04 but to wait about one year before I use it. Is there >> a risk with keeping using 18.04.3? Or should I upgrade at least to 18.04.4? >> >> > I've answered the general question here: > > > https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality > > Quoting it: > > Will a change I would like to do break some functionality? > > As the aphorism > > goes: The difference between theory and practice is that in theory, there > is no difference between theory and practice, while in practice, there is.. > There is usually a risk, however small, that a change will break some > functionality. With good tooling (such as > https://en.wikipedia.org/wiki/Version_control , > https://en.wikipedia.org/wiki/Virtual_machine and > https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should be > relatively easy to revert a change which introduced regressions, and you > should do adequate testing. > > A change may have to be avoided due to being estimated as too time or > money consuming, or as having too little gain. However, promising changes > should be attempted because: > > 1. "No guts - no glory." > 2. What does "if it ain't broke, don't fix it" really mean? > > 3. If you never change anything, your project won't progress. > > ---------- > While you may break some functionality by updating to 18.04.04 , you also > risk being affected by known security vulnerabilities (which may also break > functionality sooner or later). There is a concept of > https://en.wikipedia.org/wiki/Technical_debt . > > Regarding updating to 20.04, it is likely more time consuming and may have > more breaking changes, and you may not need all the newest and shiniest > software versions there, and you may wish to only update to ubuntu > 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being > unusable or unstable, but I'm quite out of the loop. > > Good luck! > > > >> Thanks, >> Uri. >> ???? >> uri at speedy.net >> _______________________________________________ >> Linux-il mailing list >> Linux-il at cs.huji.ac.il >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >> > > > -- > Shlomi Fish https://www.shlomifish.org/ > > Buddha has the Chuck Norris nature. > > Please reply to list if it's a mailing list post - http://shlom.in/reply . > -------------- next part -------------- An HTML attachment was scrubbed... URL: From michabailey at gmail.com Wed Jun 10 22:29:35 2020 From: michabailey at gmail.com (Micha Bailey) Date: Wed, 10 Jun 2020 22:29:35 +0300 Subject: Ubuntu In-Reply-To: References: Message-ID: Regarding the upgrade to Focal (20.04): There?s no reason to rush. Bionic (18.04) is supported, if I?m not mistaken, until 2023. In fact, Bionic (LTS) users aren?t even offered the upgrade (i.e. you need to go out of your way to get it) until 20.04.1 is out in a few months. Regarding the upgrade to 18.04.4, I could be mistaken, but my understanding is that point releases aren?t new versions of Ubuntu per se. At point releases, new isos are spun with up-to-date packages, but it?s still the same version. Assuming you make a habit of installing updates regularly (which you obviously should be), you will effectively automatically be on 18.04.4. On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: > Hi, > > Actually I have a staging server which I can upgrade first to 18.04.4 to > see if it works, or if something breaks. But I didn't find it on Google - > how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without upgrading > it to 20.04? > > ???? > uri at speedy.net > > > On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish wrote: > >> Hi Uri! >> >> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? >> >>> Hi, >>> >>> I'm sorry for posting twice in the same day to the same mailing list. >>> But I have a question: I'm using Ubuntu 18.04.3 LTS for a few production >>> servers (one of them I upgraded a few months ago from 14.04). How important >>> it is to upgrade the OS version, or can I keep it like this? I'm afraid >>> that things will break up if I upgrade. And if I upgrade, should I upgrade >>> to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently released, >>> it might have bugs which will be fixed later, and I prefer not to use the >>> first version of 20.04 but to wait about one year before I use it. Is there >>> a risk with keeping using 18.04.3? Or should I upgrade at least to 18.04.4? >>> >>> >> I've answered the general question here: >> >> >> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >> >> Quoting it: >> >> Will a change I would like to do break some functionality? >> >> As the aphorism >> >> goes: The difference between theory and practice is that in theory, >> there is no difference between theory and practice, while in practice, >> there is.. There is usually a risk, however small, that a change will >> break some functionality. With good tooling (such as >> https://en.wikipedia.org/wiki/Version_control , >> https://en.wikipedia.org/wiki/Virtual_machine and >> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should be >> relatively easy to revert a change which introduced regressions, and you >> should do adequate testing. >> >> A change may have to be avoided due to being estimated as too time or >> money consuming, or as having too little gain. However, promising changes >> should be attempted because: >> >> 1. "No guts - no glory." >> 2. What does "if it ain't broke, don't fix it" really mean? >> >> 3. If you never change anything, your project won't progress. >> >> ---------- >> While you may break some functionality by updating to 18.04.04 , you also >> risk being affected by known security vulnerabilities (which may also break >> functionality sooner or later). There is a concept of >> https://en.wikipedia.org/wiki/Technical_debt . >> >> Regarding updating to 20.04, it is likely more time consuming and may >> have more breaking changes, and you may not need all the newest and >> shiniest software versions there, and you may wish to only update to ubuntu >> 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being >> unusable or unstable, but I'm quite out of the loop. >> >> Good luck! >> >> >> >>> Thanks, >>> Uri. >>> ???? >>> uri at speedy.net >>> _______________________________________________ >>> Linux-il mailing list >>> Linux-il at cs.huji.ac.il >>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>> >> >> >> -- >> Shlomi Fish https://www.shlomifish.org/ >> >> Buddha has the Chuck Norris nature. >> >> Please reply to list if it's a mailing list post - http://shlom.in/reply >> . >> > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 06:29:00 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 06:29:00 +0300 Subject: Ubuntu In-Reply-To: References: Message-ID: Hi, Thanks for your suggestion, I decided to upgrade to 18.04.4 and I ran a few times the following commands (from root): sudo apt autoremove sudo apt-get update sudo apt-get upgrade sudo apt update sudo apt upgrade I have 4 servers and I upgraded all of them and 3 of them are working properly, however one server apache is not working, I can't restart apache (with "sudo systemctl restart apache2" - it's not responding) and the website is not working. How can I fix it now? The server didn't respond after reboot once (after 2 reboots) and I had to shut it down and restart it again. Thanks, Uri ???? uri at speedy.net On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey wrote: > Regarding the upgrade to Focal (20.04): There?s no reason to rush. Bionic > (18.04) is supported, if I?m not mistaken, until 2023. In fact, Bionic > (LTS) users aren?t even offered the upgrade (i.e. you need to go out of > your way to get it) until 20.04.1 is out in a few months. > > Regarding the upgrade to 18.04.4, I could be mistaken, but my > understanding is that point releases aren?t new versions of Ubuntu per se. > At point releases, new isos are spun with up-to-date packages, but it?s > still the same version. Assuming you make a habit of installing updates > regularly (which you obviously should be), you will effectively > automatically be on 18.04.4. > > On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: > >> Hi, >> >> Actually I have a staging server which I can upgrade first to 18.04.4 to >> see if it works, or if something breaks. But I didn't find it on Google - >> how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without upgrading >> it to 20.04? >> >> ???? >> uri at speedy.net >> >> >> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish wrote: >> >>> Hi Uri! >>> >>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? >>> >>>> Hi, >>>> >>>> I'm sorry for posting twice in the same day to the same mailing list. >>>> But I have a question: I'm using Ubuntu 18.04.3 LTS for a few production >>>> servers (one of them I upgraded a few months ago from 14.04). How important >>>> it is to upgrade the OS version, or can I keep it like this? I'm afraid >>>> that things will break up if I upgrade. And if I upgrade, should I upgrade >>>> to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently released, >>>> it might have bugs which will be fixed later, and I prefer not to use the >>>> first version of 20.04 but to wait about one year before I use it. Is there >>>> a risk with keeping using 18.04.3? Or should I upgrade at least to 18.04.4? >>>> >>>> >>> I've answered the general question here: >>> >>> >>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>> >>> Quoting it: >>> >>> Will a change I would like to do break some functionality? >>> >>> As the aphorism >>> >>> goes: The difference between theory and practice is that in theory, >>> there is no difference between theory and practice, while in practice, >>> there is.. There is usually a risk, however small, that a change will >>> break some functionality. With good tooling (such as >>> https://en.wikipedia.org/wiki/Version_control , >>> https://en.wikipedia.org/wiki/Virtual_machine and >>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should be >>> relatively easy to revert a change which introduced regressions, and you >>> should do adequate testing. >>> >>> A change may have to be avoided due to being estimated as too time or >>> money consuming, or as having too little gain. However, promising changes >>> should be attempted because: >>> >>> 1. "No guts - no glory." >>> 2. What does "if it ain't broke, don't fix it" really mean? >>> >>> 3. If you never change anything, your project won't progress. >>> >>> ---------- >>> While you may break some functionality by updating to 18.04.04 , you >>> also risk being affected by known security vulnerabilities (which may also >>> break functionality sooner or later). There is a concept of >>> https://en.wikipedia.org/wiki/Technical_debt . >>> >>> Regarding updating to 20.04, it is likely more time consuming and may >>> have more breaking changes, and you may not need all the newest and >>> shiniest software versions there, and you may wish to only update to ubuntu >>> 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being >>> unusable or unstable, but I'm quite out of the loop. >>> >>> Good luck! >>> >>> >>> >>>> Thanks, >>>> Uri. >>>> ???? >>>> uri at speedy.net >>>> _______________________________________________ >>>> Linux-il mailing list >>>> Linux-il at cs.huji.ac.il >>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>> >>> >>> >>> -- >>> Shlomi Fish https://www.shlomifish.org/ >>> >>> Buddha has the Chuck Norris nature. >>> >>> Please reply to list if it's a mailing list post - http://shlom.in/reply >>> . >>> >> _______________________________________________ >> Linux-il mailing list >> Linux-il at cs.huji.ac.il >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 07:09:53 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 07:09:53 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: Message-ID: Hi, Running the command "sudo apachectl configtest" returns "Syntax OK". Running "sudo systemctl restart apache2" doesn't respond. But a few minutes ago it worked and the website worked. I rebooted again and now again it's not working. The problem is that apache doesn't restart after rebooting. ???? uri at speedy.net ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? > Hi, > > Thanks for your suggestion, I decided to upgrade to 18.04.4 and I ran a > few times the following commands (from root): > > sudo apt autoremove > sudo apt-get update > sudo apt-get upgrade > sudo apt update > sudo apt upgrade > > I have 4 servers and I upgraded all of them and 3 of them are working > properly, however one server apache is not working, I can't restart apache > (with "sudo systemctl restart apache2" - it's not responding) and the > website is not working. How can I fix it now? > > The server didn't respond after reboot once (after 2 reboots) and I had to > shut it down and restart it again. > > Thanks, > Uri > ???? > uri at speedy.net > > > On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey > wrote: > >> Regarding the upgrade to Focal (20.04): There?s no reason to rush. Bionic >> (18.04) is supported, if I?m not mistaken, until 2023. In fact, Bionic >> (LTS) users aren?t even offered the upgrade (i.e. you need to go out of >> your way to get it) until 20.04.1 is out in a few months. >> >> Regarding the upgrade to 18.04.4, I could be mistaken, but my >> understanding is that point releases aren?t new versions of Ubuntu per se. >> At point releases, new isos are spun with up-to-date packages, but it?s >> still the same version. Assuming you make a habit of installing updates >> regularly (which you obviously should be), you will effectively >> automatically be on 18.04.4. >> >> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >> >>> Hi, >>> >>> Actually I have a staging server which I can upgrade first to 18.04.4 to >>> see if it works, or if something breaks. But I didn't find it on Google - >>> how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without upgrading >>> it to 20.04? >>> >>> ???? >>> uri at speedy.net >>> >>> >>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish wrote: >>> >>>> Hi Uri! >>>> >>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? >>>> >>>>> Hi, >>>>> >>>>> I'm sorry for posting twice in the same day to the same mailing list. >>>>> But I have a question: I'm using Ubuntu 18.04.3 LTS for a few production >>>>> servers (one of them I upgraded a few months ago from 14.04). How important >>>>> it is to upgrade the OS version, or can I keep it like this? I'm afraid >>>>> that things will break up if I upgrade. And if I upgrade, should I upgrade >>>>> to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently released, >>>>> it might have bugs which will be fixed later, and I prefer not to use the >>>>> first version of 20.04 but to wait about one year before I use it. Is there >>>>> a risk with keeping using 18.04.3? Or should I upgrade at least to 18.04.4? >>>>> >>>>> >>>> I've answered the general question here: >>>> >>>> >>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>>> >>>> Quoting it: >>>> >>>> Will a change I would like to do break some functionality? >>>> >>>> As the aphorism >>>> >>>> goes: The difference between theory and practice is that in theory, >>>> there is no difference between theory and practice, while in practice, >>>> there is.. There is usually a risk, however small, that a change will >>>> break some functionality. With good tooling (such as >>>> https://en.wikipedia.org/wiki/Version_control , >>>> https://en.wikipedia.org/wiki/Virtual_machine and >>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should be >>>> relatively easy to revert a change which introduced regressions, and you >>>> should do adequate testing. >>>> >>>> A change may have to be avoided due to being estimated as too time or >>>> money consuming, or as having too little gain. However, promising changes >>>> should be attempted because: >>>> >>>> 1. "No guts - no glory." >>>> 2. What does "if it ain't broke, don't fix it" really mean? >>>> >>>> 3. If you never change anything, your project won't progress. >>>> >>>> ---------- >>>> While you may break some functionality by updating to 18.04.04 , you >>>> also risk being affected by known security vulnerabilities (which may also >>>> break functionality sooner or later). There is a concept of >>>> https://en.wikipedia.org/wiki/Technical_debt . >>>> >>>> Regarding updating to 20.04, it is likely more time consuming and may >>>> have more breaking changes, and you may not need all the newest and >>>> shiniest software versions there, and you may wish to only update to ubuntu >>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being >>>> unusable or unstable, but I'm quite out of the loop. >>>> >>>> Good luck! >>>> >>>> >>>> >>>>> Thanks, >>>>> Uri. >>>>> ???? >>>>> uri at speedy.net >>>>> _______________________________________________ >>>>> Linux-il mailing list >>>>> Linux-il at cs.huji.ac.il >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> >>>> >>>> >>>> -- >>>> Shlomi Fish https://www.shlomifish.org/ >>>> >>>> Buddha has the Chuck Norris nature. >>>> >>>> Please reply to list if it's a mailing list post - >>>> http://shlom.in/reply . >>>> >>> _______________________________________________ >>> Linux-il mailing list >>> Linux-il at cs.huji.ac.il >>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From eli at netmask.it Thu Jun 11 07:23:22 2020 From: eli at netmask.it (Eli Marmor) Date: Thu, 11 Jun 2020 07:23:22 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: Message-ID: Please run: apachectl start from the command line, and copy the response to this list. If there is no error, please copy the relevant lines from the error.log of apache2. On Thu, Jun 11, 2020, 7:12 AM ???? wrote: > Hi, > > Running the command "sudo apachectl configtest" returns "Syntax OK". > > Running "sudo systemctl restart apache2" doesn't respond. But a few > minutes ago it worked and the website worked. I rebooted again and now > again it's not working. The problem is that apache doesn't restart after > rebooting. > > ???? > uri at speedy.net > > > ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? > >> Hi, >> >> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I ran a >> few times the following commands (from root): >> >> sudo apt autoremove >> sudo apt-get update >> sudo apt-get upgrade >> sudo apt update >> sudo apt upgrade >> >> I have 4 servers and I upgraded all of them and 3 of them are working >> properly, however one server apache is not working, I can't restart apache >> (with "sudo systemctl restart apache2" - it's not responding) and the >> website is not working. How can I fix it now? >> >> The server didn't respond after reboot once (after 2 reboots) and I had >> to shut it down and restart it again. >> >> Thanks, >> Uri >> ???? >> uri at speedy.net >> >> >> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey >> wrote: >> >>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. >>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In fact, >>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need to go out >>> of your way to get it) until 20.04.1 is out in a few months. >>> >>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >>> understanding is that point releases aren?t new versions of Ubuntu per se. >>> At point releases, new isos are spun with up-to-date packages, but it?s >>> still the same version. Assuming you make a habit of installing updates >>> regularly (which you obviously should be), you will effectively >>> automatically be on 18.04.4. >>> >>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >>> >>>> Hi, >>>> >>>> Actually I have a staging server which I can upgrade first to 18.04.4 >>>> to see if it works, or if something breaks. But I didn't find it on Google >>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without upgrading >>>> it to 20.04? >>>> >>>> ???? >>>> uri at speedy.net >>>> >>>> >>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish wrote: >>>> >>>>> Hi Uri! >>>>> >>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? >>>>> >>>>>> Hi, >>>>>> >>>>>> I'm sorry for posting twice in the same day to the same mailing list. >>>>>> But I have a question: I'm using Ubuntu 18.04.3 LTS for a few production >>>>>> servers (one of them I upgraded a few months ago from 14.04). How important >>>>>> it is to upgrade the OS version, or can I keep it like this? I'm afraid >>>>>> that things will break up if I upgrade. And if I upgrade, should I upgrade >>>>>> to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently released, >>>>>> it might have bugs which will be fixed later, and I prefer not to use the >>>>>> first version of 20.04 but to wait about one year before I use it. Is there >>>>>> a risk with keeping using 18.04.3? Or should I upgrade at least to 18.04.4? >>>>>> >>>>>> >>>>> I've answered the general question here: >>>>> >>>>> >>>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>>>> >>>>> Quoting it: >>>>> >>>>> Will a change I would like to do break some functionality? >>>>> >>>>> As the aphorism >>>>> >>>>> goes: The difference between theory and practice is that in theory, >>>>> there is no difference between theory and practice, while in practice, >>>>> there is.. There is usually a risk, however small, that a change will >>>>> break some functionality. With good tooling (such as >>>>> https://en.wikipedia.org/wiki/Version_control , >>>>> https://en.wikipedia.org/wiki/Virtual_machine and >>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should be >>>>> relatively easy to revert a change which introduced regressions, and you >>>>> should do adequate testing. >>>>> >>>>> A change may have to be avoided due to being estimated as too time or >>>>> money consuming, or as having too little gain. However, promising changes >>>>> should be attempted because: >>>>> >>>>> 1. "No guts - no glory." >>>>> 2. What does "if it ain't broke, don't fix it" really mean? >>>>> >>>>> 3. If you never change anything, your project won't progress. >>>>> >>>>> ---------- >>>>> While you may break some functionality by updating to 18.04.04 , you >>>>> also risk being affected by known security vulnerabilities (which may also >>>>> break functionality sooner or later). There is a concept of >>>>> https://en.wikipedia.org/wiki/Technical_debt . >>>>> >>>>> Regarding updating to 20.04, it is likely more time consuming and may >>>>> have more breaking changes, and you may not need all the newest and >>>>> shiniest software versions there, and you may wish to only update to ubuntu >>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being >>>>> unusable or unstable, but I'm quite out of the loop. >>>>> >>>>> Good luck! >>>>> >>>>> >>>>> >>>>>> Thanks, >>>>>> Uri. >>>>>> ???? >>>>>> uri at speedy.net >>>>>> _______________________________________________ >>>>>> Linux-il mailing list >>>>>> Linux-il at cs.huji.ac.il >>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>> >>>>> >>>>> >>>>> -- >>>>> Shlomi Fish https://www.shlomifish.org/ >>>>> >>>>> Buddha has the Chuck Norris nature. >>>>> >>>>> Please reply to list if it's a mailing list post - >>>>> http://shlom.in/reply . >>>>> >>>> _______________________________________________ >>>> Linux-il mailing list >>>> Linux-il at cs.huji.ac.il >>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>> >>> _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 07:27:06 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 07:27:06 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: Message-ID: # apachectl start Invoking 'systemctl start apache2'. Use 'systemctl status apache2' for more info. ???? uri at speedy.net On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: > Please run: > apachectl start > from the command line, and copy the response to this list. > If there is no error, please copy the relevant lines from the error.log of > apache2. > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: > >> Hi, >> >> Running the command "sudo apachectl configtest" returns "Syntax OK". >> >> Running "sudo systemctl restart apache2" doesn't respond. But a few >> minutes ago it worked and the website worked. I rebooted again and now >> again it's not working. The problem is that apache doesn't restart after >> rebooting. >> >> ???? >> uri at speedy.net >> >> >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? >> >>> Hi, >>> >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I ran a >>> few times the following commands (from root): >>> >>> sudo apt autoremove >>> sudo apt-get update >>> sudo apt-get upgrade >>> sudo apt update >>> sudo apt upgrade >>> >>> I have 4 servers and I upgraded all of them and 3 of them are working >>> properly, however one server apache is not working, I can't restart apache >>> (with "sudo systemctl restart apache2" - it's not responding) and the >>> website is not working. How can I fix it now? >>> >>> The server didn't respond after reboot once (after 2 reboots) and I had >>> to shut it down and restart it again. >>> >>> Thanks, >>> Uri >>> ???? >>> uri at speedy.net >>> >>> >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey >>> wrote: >>> >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In fact, >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need to go out >>>> of your way to get it) until 20.04.1 is out in a few months. >>>> >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >>>> understanding is that point releases aren?t new versions of Ubuntu per se. >>>> At point releases, new isos are spun with up-to-date packages, but it?s >>>> still the same version. Assuming you make a habit of installing updates >>>> regularly (which you obviously should be), you will effectively >>>> automatically be on 18.04.4. >>>> >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >>>> >>>>> Hi, >>>>> >>>>> Actually I have a staging server which I can upgrade first to 18.04.4 >>>>> to see if it works, or if something breaks. But I didn't find it on Google >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without upgrading >>>>> it to 20.04? >>>>> >>>>> ???? >>>>> uri at speedy.net >>>>> >>>>> >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish wrote: >>>>> >>>>>> Hi Uri! >>>>>> >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I'm sorry for posting twice in the same day to the same mailing >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a few >>>>>>> production servers (one of them I upgraded a few months ago from 14.04). >>>>>>> How important it is to upgrade the OS version, or can I keep it like this? >>>>>>> I'm afraid that things will break up if I upgrade. And if I upgrade, should >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently >>>>>>> released, it might have bugs which will be fixed later, and I prefer not to >>>>>>> use the first version of 20.04 but to wait about one year before I use it. >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade at least to >>>>>>> 18.04.4? >>>>>>> >>>>>>> >>>>>> I've answered the general question here: >>>>>> >>>>>> >>>>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>>>>> >>>>>> Quoting it: >>>>>> >>>>>> Will a change I would like to do break some functionality? >>>>>> >>>>>> As the aphorism >>>>>> >>>>>> goes: The difference between theory and practice is that in theory, >>>>>> there is no difference between theory and practice, while in practice, >>>>>> there is.. There is usually a risk, however small, that a change >>>>>> will break some functionality. With good tooling (such as >>>>>> https://en.wikipedia.org/wiki/Version_control , >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should be >>>>>> relatively easy to revert a change which introduced regressions, and you >>>>>> should do adequate testing. >>>>>> >>>>>> A change may have to be avoided due to being estimated as too time or >>>>>> money consuming, or as having too little gain. However, promising changes >>>>>> should be attempted because: >>>>>> >>>>>> 1. "No guts - no glory." >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? >>>>>> >>>>>> 3. If you never change anything, your project won't progress. >>>>>> >>>>>> ---------- >>>>>> While you may break some functionality by updating to 18.04.04 , you >>>>>> also risk being affected by known security vulnerabilities (which may also >>>>>> break functionality sooner or later). There is a concept of >>>>>> https://en.wikipedia.org/wiki/Technical_debt . >>>>>> >>>>>> Regarding updating to 20.04, it is likely more time consuming and may >>>>>> have more breaking changes, and you may not need all the newest and >>>>>> shiniest software versions there, and you may wish to only update to ubuntu >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being >>>>>> unusable or unstable, but I'm quite out of the loop. >>>>>> >>>>>> Good luck! >>>>>> >>>>>> >>>>>> >>>>>>> Thanks, >>>>>>> Uri. >>>>>>> ???? >>>>>>> uri at speedy.net >>>>>>> _______________________________________________ >>>>>>> Linux-il mailing list >>>>>>> Linux-il at cs.huji.ac.il >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Shlomi Fish https://www.shlomifish.org/ >>>>>> >>>>>> Buddha has the Chuck Norris nature. >>>>>> >>>>>> Please reply to list if it's a mailing list post - >>>>>> http://shlom.in/reply . >>>>>> >>>>> _______________________________________________ >>>>> Linux-il mailing list >>>>> Linux-il at cs.huji.ac.il >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> >>>> _______________________________________________ >> Linux-il mailing list >> Linux-il at cs.huji.ac.il >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 07:27:50 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 07:27:50 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: Message-ID: Website is working now. But if I reboot the server again, I expect it to stop working. ???? uri at speedy.net On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: > Please run: > apachectl start > from the command line, and copy the response to this list. > If there is no error, please copy the relevant lines from the error.log of > apache2. > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: > >> Hi, >> >> Running the command "sudo apachectl configtest" returns "Syntax OK". >> >> Running "sudo systemctl restart apache2" doesn't respond. But a few >> minutes ago it worked and the website worked. I rebooted again and now >> again it's not working. The problem is that apache doesn't restart after >> rebooting. >> >> ???? >> uri at speedy.net >> >> >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? >> >>> Hi, >>> >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I ran a >>> few times the following commands (from root): >>> >>> sudo apt autoremove >>> sudo apt-get update >>> sudo apt-get upgrade >>> sudo apt update >>> sudo apt upgrade >>> >>> I have 4 servers and I upgraded all of them and 3 of them are working >>> properly, however one server apache is not working, I can't restart apache >>> (with "sudo systemctl restart apache2" - it's not responding) and the >>> website is not working. How can I fix it now? >>> >>> The server didn't respond after reboot once (after 2 reboots) and I had >>> to shut it down and restart it again. >>> >>> Thanks, >>> Uri >>> ???? >>> uri at speedy.net >>> >>> >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey >>> wrote: >>> >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In fact, >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need to go out >>>> of your way to get it) until 20.04.1 is out in a few months. >>>> >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >>>> understanding is that point releases aren?t new versions of Ubuntu per se. >>>> At point releases, new isos are spun with up-to-date packages, but it?s >>>> still the same version. Assuming you make a habit of installing updates >>>> regularly (which you obviously should be), you will effectively >>>> automatically be on 18.04.4. >>>> >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >>>> >>>>> Hi, >>>>> >>>>> Actually I have a staging server which I can upgrade first to 18.04.4 >>>>> to see if it works, or if something breaks. But I didn't find it on Google >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without upgrading >>>>> it to 20.04? >>>>> >>>>> ???? >>>>> uri at speedy.net >>>>> >>>>> >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish wrote: >>>>> >>>>>> Hi Uri! >>>>>> >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I'm sorry for posting twice in the same day to the same mailing >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a few >>>>>>> production servers (one of them I upgraded a few months ago from 14.04). >>>>>>> How important it is to upgrade the OS version, or can I keep it like this? >>>>>>> I'm afraid that things will break up if I upgrade. And if I upgrade, should >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently >>>>>>> released, it might have bugs which will be fixed later, and I prefer not to >>>>>>> use the first version of 20.04 but to wait about one year before I use it. >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade at least to >>>>>>> 18.04.4? >>>>>>> >>>>>>> >>>>>> I've answered the general question here: >>>>>> >>>>>> >>>>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>>>>> >>>>>> Quoting it: >>>>>> >>>>>> Will a change I would like to do break some functionality? >>>>>> >>>>>> As the aphorism >>>>>> >>>>>> goes: The difference between theory and practice is that in theory, >>>>>> there is no difference between theory and practice, while in practice, >>>>>> there is.. There is usually a risk, however small, that a change >>>>>> will break some functionality. With good tooling (such as >>>>>> https://en.wikipedia.org/wiki/Version_control , >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should be >>>>>> relatively easy to revert a change which introduced regressions, and you >>>>>> should do adequate testing. >>>>>> >>>>>> A change may have to be avoided due to being estimated as too time or >>>>>> money consuming, or as having too little gain. However, promising changes >>>>>> should be attempted because: >>>>>> >>>>>> 1. "No guts - no glory." >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? >>>>>> >>>>>> 3. If you never change anything, your project won't progress. >>>>>> >>>>>> ---------- >>>>>> While you may break some functionality by updating to 18.04.04 , you >>>>>> also risk being affected by known security vulnerabilities (which may also >>>>>> break functionality sooner or later). There is a concept of >>>>>> https://en.wikipedia.org/wiki/Technical_debt . >>>>>> >>>>>> Regarding updating to 20.04, it is likely more time consuming and may >>>>>> have more breaking changes, and you may not need all the newest and >>>>>> shiniest software versions there, and you may wish to only update to ubuntu >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being >>>>>> unusable or unstable, but I'm quite out of the loop. >>>>>> >>>>>> Good luck! >>>>>> >>>>>> >>>>>> >>>>>>> Thanks, >>>>>>> Uri. >>>>>>> ???? >>>>>>> uri at speedy.net >>>>>>> _______________________________________________ >>>>>>> Linux-il mailing list >>>>>>> Linux-il at cs.huji.ac.il >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Shlomi Fish https://www.shlomifish.org/ >>>>>> >>>>>> Buddha has the Chuck Norris nature. >>>>>> >>>>>> Please reply to list if it's a mailing list post - >>>>>> http://shlom.in/reply . >>>>>> >>>>> _______________________________________________ >>>>> Linux-il mailing list >>>>> Linux-il at cs.huji.ac.il >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> >>>> _______________________________________________ >> Linux-il mailing list >> Linux-il at cs.huji.ac.il >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 07:31:31 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 07:31:31 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: Message-ID: Hi, I estimate it's about 15 to 20 minutes after reboot that I can start apache successfully. Otherwise, I can't start apache. ???? uri at speedy.net On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: > Please run: > apachectl start > from the command line, and copy the response to this list. > If there is no error, please copy the relevant lines from the error.log of > apache2. > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: > >> Hi, >> >> Running the command "sudo apachectl configtest" returns "Syntax OK". >> >> Running "sudo systemctl restart apache2" doesn't respond. But a few >> minutes ago it worked and the website worked. I rebooted again and now >> again it's not working. The problem is that apache doesn't restart after >> rebooting. >> >> ???? >> uri at speedy.net >> >> >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? >> >>> Hi, >>> >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I ran a >>> few times the following commands (from root): >>> >>> sudo apt autoremove >>> sudo apt-get update >>> sudo apt-get upgrade >>> sudo apt update >>> sudo apt upgrade >>> >>> I have 4 servers and I upgraded all of them and 3 of them are working >>> properly, however one server apache is not working, I can't restart apache >>> (with "sudo systemctl restart apache2" - it's not responding) and the >>> website is not working. How can I fix it now? >>> >>> The server didn't respond after reboot once (after 2 reboots) and I had >>> to shut it down and restart it again. >>> >>> Thanks, >>> Uri >>> ???? >>> uri at speedy.net >>> >>> >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey >>> wrote: >>> >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In fact, >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need to go out >>>> of your way to get it) until 20.04.1 is out in a few months. >>>> >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >>>> understanding is that point releases aren?t new versions of Ubuntu per se. >>>> At point releases, new isos are spun with up-to-date packages, but it?s >>>> still the same version. Assuming you make a habit of installing updates >>>> regularly (which you obviously should be), you will effectively >>>> automatically be on 18.04.4. >>>> >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >>>> >>>>> Hi, >>>>> >>>>> Actually I have a staging server which I can upgrade first to 18.04.4 >>>>> to see if it works, or if something breaks. But I didn't find it on Google >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without upgrading >>>>> it to 20.04? >>>>> >>>>> ???? >>>>> uri at speedy.net >>>>> >>>>> >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish wrote: >>>>> >>>>>> Hi Uri! >>>>>> >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I'm sorry for posting twice in the same day to the same mailing >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a few >>>>>>> production servers (one of them I upgraded a few months ago from 14.04). >>>>>>> How important it is to upgrade the OS version, or can I keep it like this? >>>>>>> I'm afraid that things will break up if I upgrade. And if I upgrade, should >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently >>>>>>> released, it might have bugs which will be fixed later, and I prefer not to >>>>>>> use the first version of 20.04 but to wait about one year before I use it. >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade at least to >>>>>>> 18.04.4? >>>>>>> >>>>>>> >>>>>> I've answered the general question here: >>>>>> >>>>>> >>>>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>>>>> >>>>>> Quoting it: >>>>>> >>>>>> Will a change I would like to do break some functionality? >>>>>> >>>>>> As the aphorism >>>>>> >>>>>> goes: The difference between theory and practice is that in theory, >>>>>> there is no difference between theory and practice, while in practice, >>>>>> there is.. There is usually a risk, however small, that a change >>>>>> will break some functionality. With good tooling (such as >>>>>> https://en.wikipedia.org/wiki/Version_control , >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should be >>>>>> relatively easy to revert a change which introduced regressions, and you >>>>>> should do adequate testing. >>>>>> >>>>>> A change may have to be avoided due to being estimated as too time or >>>>>> money consuming, or as having too little gain. However, promising changes >>>>>> should be attempted because: >>>>>> >>>>>> 1. "No guts - no glory." >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? >>>>>> >>>>>> 3. If you never change anything, your project won't progress. >>>>>> >>>>>> ---------- >>>>>> While you may break some functionality by updating to 18.04.04 , you >>>>>> also risk being affected by known security vulnerabilities (which may also >>>>>> break functionality sooner or later). There is a concept of >>>>>> https://en.wikipedia.org/wiki/Technical_debt . >>>>>> >>>>>> Regarding updating to 20.04, it is likely more time consuming and may >>>>>> have more breaking changes, and you may not need all the newest and >>>>>> shiniest software versions there, and you may wish to only update to ubuntu >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being >>>>>> unusable or unstable, but I'm quite out of the loop. >>>>>> >>>>>> Good luck! >>>>>> >>>>>> >>>>>> >>>>>>> Thanks, >>>>>>> Uri. >>>>>>> ???? >>>>>>> uri at speedy.net >>>>>>> _______________________________________________ >>>>>>> Linux-il mailing list >>>>>>> Linux-il at cs.huji.ac.il >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Shlomi Fish https://www.shlomifish.org/ >>>>>> >>>>>> Buddha has the Chuck Norris nature. >>>>>> >>>>>> Please reply to list if it's a mailing list post - >>>>>> http://shlom.in/reply . >>>>>> >>>>> _______________________________________________ >>>>> Linux-il mailing list >>>>> Linux-il at cs.huji.ac.il >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> >>>> _______________________________________________ >> Linux-il mailing list >> Linux-il at cs.huji.ac.il >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 08:05:10 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 08:05:10 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: Message-ID: I ran the commands again and found out there are errors: root at www:~# sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root at www:~# sudo apt-get update Hit:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Err:3 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic InRelease 403 Forbidden [IP: 91.189.95.83 80] Hit:4 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:5 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease Hit:6 http://mirrors.digitalocean.com/ubuntu bionic InRelease Hit:7 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease Reading package lists... Done E: Failed to fetch http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease 403 Forbidden [IP: 91.189.95.83 80] E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic InRelease' is no longer signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. root at www:~# sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root at www:~# sudo apt update Hit:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease Err:4 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic InRelease 403 Forbidden [IP: 91.189.95.83 80] Hit:5 http://mirrors.digitalocean.com/ubuntu bionic InRelease Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease Hit:7 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease Reading package lists... Done E: Failed to fetch http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease 403 Forbidden [IP: 91.189.95.83 80] E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic InRelease' is no longer signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. root at www:~# sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ???? uri at speedy.net On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: > Please run: > apachectl start > from the command line, and copy the response to this list. > If there is no error, please copy the relevant lines from the error.log of > apache2. > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: > >> Hi, >> >> Running the command "sudo apachectl configtest" returns "Syntax OK". >> >> Running "sudo systemctl restart apache2" doesn't respond. But a few >> minutes ago it worked and the website worked. I rebooted again and now >> again it's not working. The problem is that apache doesn't restart after >> rebooting. >> >> ???? >> uri at speedy.net >> >> >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? >> >>> Hi, >>> >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I ran a >>> few times the following commands (from root): >>> >>> sudo apt autoremove >>> sudo apt-get update >>> sudo apt-get upgrade >>> sudo apt update >>> sudo apt upgrade >>> >>> I have 4 servers and I upgraded all of them and 3 of them are working >>> properly, however one server apache is not working, I can't restart apache >>> (with "sudo systemctl restart apache2" - it's not responding) and the >>> website is not working. How can I fix it now? >>> >>> The server didn't respond after reboot once (after 2 reboots) and I had >>> to shut it down and restart it again. >>> >>> Thanks, >>> Uri >>> ???? >>> uri at speedy.net >>> >>> >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey >>> wrote: >>> >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In fact, >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need to go out >>>> of your way to get it) until 20.04.1 is out in a few months. >>>> >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >>>> understanding is that point releases aren?t new versions of Ubuntu per se. >>>> At point releases, new isos are spun with up-to-date packages, but it?s >>>> still the same version. Assuming you make a habit of installing updates >>>> regularly (which you obviously should be), you will effectively >>>> automatically be on 18.04.4. >>>> >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >>>> >>>>> Hi, >>>>> >>>>> Actually I have a staging server which I can upgrade first to 18.04.4 >>>>> to see if it works, or if something breaks. But I didn't find it on Google >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without upgrading >>>>> it to 20.04? >>>>> >>>>> ???? >>>>> uri at speedy.net >>>>> >>>>> >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish wrote: >>>>> >>>>>> Hi Uri! >>>>>> >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I'm sorry for posting twice in the same day to the same mailing >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a few >>>>>>> production servers (one of them I upgraded a few months ago from 14.04). >>>>>>> How important it is to upgrade the OS version, or can I keep it like this? >>>>>>> I'm afraid that things will break up if I upgrade. And if I upgrade, should >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently >>>>>>> released, it might have bugs which will be fixed later, and I prefer not to >>>>>>> use the first version of 20.04 but to wait about one year before I use it. >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade at least to >>>>>>> 18.04.4? >>>>>>> >>>>>>> >>>>>> I've answered the general question here: >>>>>> >>>>>> >>>>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>>>>> >>>>>> Quoting it: >>>>>> >>>>>> Will a change I would like to do break some functionality? >>>>>> >>>>>> As the aphorism >>>>>> >>>>>> goes: The difference between theory and practice is that in theory, >>>>>> there is no difference between theory and practice, while in practice, >>>>>> there is.. There is usually a risk, however small, that a change >>>>>> will break some functionality. With good tooling (such as >>>>>> https://en.wikipedia.org/wiki/Version_control , >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should be >>>>>> relatively easy to revert a change which introduced regressions, and you >>>>>> should do adequate testing. >>>>>> >>>>>> A change may have to be avoided due to being estimated as too time or >>>>>> money consuming, or as having too little gain. However, promising changes >>>>>> should be attempted because: >>>>>> >>>>>> 1. "No guts - no glory." >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? >>>>>> >>>>>> 3. If you never change anything, your project won't progress. >>>>>> >>>>>> ---------- >>>>>> While you may break some functionality by updating to 18.04.04 , you >>>>>> also risk being affected by known security vulnerabilities (which may also >>>>>> break functionality sooner or later). There is a concept of >>>>>> https://en.wikipedia.org/wiki/Technical_debt . >>>>>> >>>>>> Regarding updating to 20.04, it is likely more time consuming and may >>>>>> have more breaking changes, and you may not need all the newest and >>>>>> shiniest software versions there, and you may wish to only update to ubuntu >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being >>>>>> unusable or unstable, but I'm quite out of the loop. >>>>>> >>>>>> Good luck! >>>>>> >>>>>> >>>>>> >>>>>>> Thanks, >>>>>>> Uri. >>>>>>> ???? >>>>>>> uri at speedy.net >>>>>>> _______________________________________________ >>>>>>> Linux-il mailing list >>>>>>> Linux-il at cs.huji.ac.il >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Shlomi Fish https://www.shlomifish.org/ >>>>>> >>>>>> Buddha has the Chuck Norris nature. >>>>>> >>>>>> Please reply to list if it's a mailing list post - >>>>>> http://shlom.in/reply . >>>>>> >>>>> _______________________________________________ >>>>> Linux-il mailing list >>>>> Linux-il at cs.huji.ac.il >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> >>>> _______________________________________________ >> Linux-il mailing list >> Linux-il at cs.huji.ac.il >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tzafrir at cohens.org.il Thu Jun 11 08:42:48 2020 From: tzafrir at cohens.org.il (Tzafrir Cohen) Date: Thu, 11 Jun 2020 08:42:48 +0300 Subject: Ubuntu In-Reply-To: References: Message-ID: On 11/06/2020 6:29, ???? wrote: > Hi, > > Thanks for your suggestion, I decided to upgrade to?18.04.4 and I ran a > few times the following commands?(from root): > > sudo apt autoremove > sudo apt-get update > sudo apt-get upgrade > sudo apt update > sudo apt upgrade apt is basically a wrapper around apt-get and apt-cache. Running both apt-get and apt is pointless. It is also recommended to run autoremove after an upgrade (more useful than before). -- Tzafrir From uri at speedy.net Thu Jun 11 09:05:02 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 09:05:02 +0300 Subject: Ubuntu In-Reply-To: References: Message-ID: Hi, I ran autoremove both before and after the upgrade. ???? uri at speedy.net On Thu, Jun 11, 2020 at 8:43 AM Tzafrir Cohen wrote: > On 11/06/2020 6:29, ???? wrote: > > Hi, > > > > Thanks for your suggestion, I decided to upgrade to 18.04.4 and I ran a > > few times the following commands (from root): > > > > sudo apt autoremove > > sudo apt-get update > > sudo apt-get upgrade > > sudo apt update > > sudo apt upgrade > > apt is basically a wrapper around apt-get and apt-cache. Running both > apt-get and apt is pointless. > > It is also recommended to run autoremove after an upgrade (more useful > than before). > > -- Tzafrir > > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > -------------- next part -------------- An HTML attachment was scrubbed... URL: From efraim at flashner.co.il Thu Jun 11 09:38:05 2020 From: efraim at flashner.co.il (Efraim Flashner) Date: Thu, 11 Jun 2020 09:38:05 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: Message-ID: <20200611063805.GE963@E5400> Not sure why apache is only starting some time after you reboot. What does the output of 'systemctl status apache2.service' look like? On Thu, Jun 11, 2020 at 07:31:31AM +0300, ???? wrote: > Hi, > > I estimate it's about 15 to 20 minutes after reboot that I can start apache > successfully. Otherwise, I can't start apache. > > ???? > uri at speedy.net > > > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: > > > Please run: > > apachectl start > > from the command line, and copy the response to this list. > > If there is no error, please copy the relevant lines from the error.log of > > apache2. > > > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: > > > >> Hi, > >> > >> Running the command "sudo apachectl configtest" returns "Syntax OK". > >> > >> Running "sudo systemctl restart apache2" doesn't respond. But a few > >> minutes ago it worked and the website worked. I rebooted again and now > >> again it's not working. The problem is that apache doesn't restart after > >> rebooting. > >> > >> ???? > >> uri at speedy.net > >> > >> > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? > >> > >>> Hi, > >>> > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I ran a > >>> few times the following commands (from root): > >>> > >>> sudo apt autoremove > >>> sudo apt-get update > >>> sudo apt-get upgrade > >>> sudo apt update > >>> sudo apt upgrade > >>> > >>> I have 4 servers and I upgraded all of them and 3 of them are working > >>> properly, however one server apache is not working, I can't restart apache > >>> (with "sudo systemctl restart apache2" - it's not responding) and the > >>> website is not working. How can I fix it now? > >>> > >>> The server didn't respond after reboot once (after 2 reboots) and I had > >>> to shut it down and restart it again. > >>> > >>> Thanks, > >>> Uri > >>> ???? > >>> uri at speedy.net > >>> > >>> > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey > >>> wrote: > >>> > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In fact, > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need to go out > >>>> of your way to get it) until 20.04.1 is out in a few months. > >>>> > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my > >>>> understanding is that point releases aren?t new versions of Ubuntu per se. > >>>> At point releases, new isos are spun with up-to-date packages, but it?s > >>>> still the same version. Assuming you make a habit of installing updates > >>>> regularly (which you obviously should be), you will effectively > >>>> automatically be on 18.04.4. > >>>> > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: > >>>> > >>>>> Hi, > >>>>> > >>>>> Actually I have a staging server which I can upgrade first to 18.04.4 > >>>>> to see if it works, or if something breaks. But I didn't find it on Google > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without upgrading > >>>>> it to 20.04? > >>>>> > >>>>> ???? > >>>>> uri at speedy.net > >>>>> > >>>>> > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish wrote: > >>>>> > >>>>>> Hi Uri! > >>>>>> > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? > >>>>>> > >>>>>>> Hi, > >>>>>>> > >>>>>>> I'm sorry for posting twice in the same day to the same mailing > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a few > >>>>>>> production servers (one of them I upgraded a few months ago from 14.04). > >>>>>>> How important it is to upgrade the OS version, or can I keep it like this? > >>>>>>> I'm afraid that things will break up if I upgrade. And if I upgrade, should > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently > >>>>>>> released, it might have bugs which will be fixed later, and I prefer not to > >>>>>>> use the first version of 20.04 but to wait about one year before I use it. > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade at least to > >>>>>>> 18.04.4? > >>>>>>> > >>>>>>> > >>>>>> I've answered the general question here: > >>>>>> > >>>>>> > >>>>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality > >>>>>> > >>>>>> Quoting it: > >>>>>> > >>>>>> Will a change I would like to do break some functionality? > >>>>>> > >>>>>> As the aphorism > >>>>>> > >>>>>> goes: The difference between theory and practice is that in theory, > >>>>>> there is no difference between theory and practice, while in practice, > >>>>>> there is.. There is usually a risk, however small, that a change > >>>>>> will break some functionality. With good tooling (such as > >>>>>> https://en.wikipedia.org/wiki/Version_control , > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should be > >>>>>> relatively easy to revert a change which introduced regressions, and you > >>>>>> should do adequate testing. > >>>>>> > >>>>>> A change may have to be avoided due to being estimated as too time or > >>>>>> money consuming, or as having too little gain. However, promising changes > >>>>>> should be attempted because: > >>>>>> > >>>>>> 1. "No guts - no glory." > >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? > >>>>>> > >>>>>> 3. If you never change anything, your project won't progress. > >>>>>> > >>>>>> ---------- > >>>>>> While you may break some functionality by updating to 18.04.04 , you > >>>>>> also risk being affected by known security vulnerabilities (which may also > >>>>>> break functionality sooner or later). There is a concept of > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . > >>>>>> > >>>>>> Regarding updating to 20.04, it is likely more time consuming and may > >>>>>> have more breaking changes, and you may not need all the newest and > >>>>>> shiniest software versions there, and you may wish to only update to ubuntu > >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being > >>>>>> unusable or unstable, but I'm quite out of the loop. > >>>>>> > >>>>>> Good luck! > >>>>>> > >>>>>> > >>>>>> > >>>>>>> Thanks, > >>>>>>> Uri. > >>>>>>> ???? > >>>>>>> uri at speedy.net > >>>>>>> _______________________________________________ > >>>>>>> Linux-il mailing list > >>>>>>> Linux-il at cs.huji.ac.il > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > >>>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Shlomi Fish https://www.shlomifish.org/ > >>>>>> > >>>>>> Buddha has the Chuck Norris nature. > >>>>>> > >>>>>> Please reply to list if it's a mailing list post - > >>>>>> http://shlom.in/reply . > >>>>>> > >>>>> _______________________________________________ > >>>>> Linux-il mailing list > >>>>> Linux-il at cs.huji.ac.il > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > >>>>> > >>>> _______________________________________________ > >> Linux-il mailing list > >> Linux-il at cs.huji.ac.il > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > >> > > > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il -- Efraim Flashner ????? ????? GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From efraim at flashner.co.il Thu Jun 11 09:38:39 2020 From: efraim at flashner.co.il (Efraim Flashner) Date: Thu, 11 Jun 2020 09:38:39 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: Message-ID: <20200611063839.GF963@E5400> If you no longer need python-3.6 then you can remove that PPA from your list of sources. On Thu, Jun 11, 2020 at 08:05:10AM +0300, ???? wrote: > I ran the commands again and found out there are errors: > > root at www:~# sudo apt autoremove > Reading package lists... Done > Building dependency tree > Reading state information... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > root at www:~# sudo apt-get update > Hit:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease > Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] > Err:3 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic InRelease > 403 Forbidden [IP: 91.189.95.83 80] > Hit:4 http://archive.ubuntu.com/ubuntu bionic InRelease > Hit:5 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease > Hit:6 http://mirrors.digitalocean.com/ubuntu bionic InRelease > Hit:7 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease > Reading package lists... Done > E: Failed to fetch > http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease > 403 Forbidden [IP: 91.189.95.83 80] > E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu > bionic InRelease' is no longer signed. > N: Updating from such a repository can't be done securely, and is therefore > disabled by default. > N: See apt-secure(8) manpage for repository creation and user configuration > details. > root at www:~# sudo apt-get upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > root at www:~# sudo apt update > Hit:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease > Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease > Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease > Err:4 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic InRelease > 403 Forbidden [IP: 91.189.95.83 80] > Hit:5 http://mirrors.digitalocean.com/ubuntu bionic InRelease > Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease > Hit:7 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease > Reading package lists... Done > E: Failed to fetch > http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease > 403 Forbidden [IP: 91.189.95.83 80] > E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu > bionic InRelease' is no longer signed. > N: Updating from such a repository can't be done securely, and is therefore > disabled by default. > N: See apt-secure(8) manpage for repository creation and user configuration > details. > root at www:~# sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > ???? > uri at speedy.net > > > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: > > > Please run: > > apachectl start > > from the command line, and copy the response to this list. > > If there is no error, please copy the relevant lines from the error.log of > > apache2. > > > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: > > > >> Hi, > >> > >> Running the command "sudo apachectl configtest" returns "Syntax OK". > >> > >> Running "sudo systemctl restart apache2" doesn't respond. But a few > >> minutes ago it worked and the website worked. I rebooted again and now > >> again it's not working. The problem is that apache doesn't restart after > >> rebooting. > >> > >> ???? > >> uri at speedy.net > >> > >> > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? > >> > >>> Hi, > >>> > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I ran a > >>> few times the following commands (from root): > >>> > >>> sudo apt autoremove > >>> sudo apt-get update > >>> sudo apt-get upgrade > >>> sudo apt update > >>> sudo apt upgrade > >>> > >>> I have 4 servers and I upgraded all of them and 3 of them are working > >>> properly, however one server apache is not working, I can't restart apache > >>> (with "sudo systemctl restart apache2" - it's not responding) and the > >>> website is not working. How can I fix it now? > >>> > >>> The server didn't respond after reboot once (after 2 reboots) and I had > >>> to shut it down and restart it again. > >>> > >>> Thanks, > >>> Uri > >>> ???? > >>> uri at speedy.net > >>> > >>> > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey > >>> wrote: > >>> > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In fact, > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need to go out > >>>> of your way to get it) until 20.04.1 is out in a few months. > >>>> > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my > >>>> understanding is that point releases aren?t new versions of Ubuntu per se. > >>>> At point releases, new isos are spun with up-to-date packages, but it?s > >>>> still the same version. Assuming you make a habit of installing updates > >>>> regularly (which you obviously should be), you will effectively > >>>> automatically be on 18.04.4. > >>>> > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: > >>>> > >>>>> Hi, > >>>>> > >>>>> Actually I have a staging server which I can upgrade first to 18.04.4 > >>>>> to see if it works, or if something breaks. But I didn't find it on Google > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without upgrading > >>>>> it to 20.04? > >>>>> > >>>>> ???? > >>>>> uri at speedy.net > >>>>> > >>>>> > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish wrote: > >>>>> > >>>>>> Hi Uri! > >>>>>> > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? > >>>>>> > >>>>>>> Hi, > >>>>>>> > >>>>>>> I'm sorry for posting twice in the same day to the same mailing > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a few > >>>>>>> production servers (one of them I upgraded a few months ago from 14.04). > >>>>>>> How important it is to upgrade the OS version, or can I keep it like this? > >>>>>>> I'm afraid that things will break up if I upgrade. And if I upgrade, should > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently > >>>>>>> released, it might have bugs which will be fixed later, and I prefer not to > >>>>>>> use the first version of 20.04 but to wait about one year before I use it. > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade at least to > >>>>>>> 18.04.4? > >>>>>>> > >>>>>>> > >>>>>> I've answered the general question here: > >>>>>> > >>>>>> > >>>>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality > >>>>>> > >>>>>> Quoting it: > >>>>>> > >>>>>> Will a change I would like to do break some functionality? > >>>>>> > >>>>>> As the aphorism > >>>>>> > >>>>>> goes: The difference between theory and practice is that in theory, > >>>>>> there is no difference between theory and practice, while in practice, > >>>>>> there is.. There is usually a risk, however small, that a change > >>>>>> will break some functionality. With good tooling (such as > >>>>>> https://en.wikipedia.org/wiki/Version_control , > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should be > >>>>>> relatively easy to revert a change which introduced regressions, and you > >>>>>> should do adequate testing. > >>>>>> > >>>>>> A change may have to be avoided due to being estimated as too time or > >>>>>> money consuming, or as having too little gain. However, promising changes > >>>>>> should be attempted because: > >>>>>> > >>>>>> 1. "No guts - no glory." > >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? > >>>>>> > >>>>>> 3. If you never change anything, your project won't progress. > >>>>>> > >>>>>> ---------- > >>>>>> While you may break some functionality by updating to 18.04.04 , you > >>>>>> also risk being affected by known security vulnerabilities (which may also > >>>>>> break functionality sooner or later). There is a concept of > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . > >>>>>> > >>>>>> Regarding updating to 20.04, it is likely more time consuming and may > >>>>>> have more breaking changes, and you may not need all the newest and > >>>>>> shiniest software versions there, and you may wish to only update to ubuntu > >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being > >>>>>> unusable or unstable, but I'm quite out of the loop. > >>>>>> > >>>>>> Good luck! > >>>>>> > >>>>>> > >>>>>> > >>>>>>> Thanks, > >>>>>>> Uri. > >>>>>>> ???? > >>>>>>> uri at speedy.net > >>>>>>> _______________________________________________ > >>>>>>> Linux-il mailing list > >>>>>>> Linux-il at cs.huji.ac.il > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > >>>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Shlomi Fish https://www.shlomifish.org/ > >>>>>> > >>>>>> Buddha has the Chuck Norris nature. > >>>>>> > >>>>>> Please reply to list if it's a mailing list post - > >>>>>> http://shlom.in/reply . > >>>>>> > >>>>> _______________________________________________ > >>>>> Linux-il mailing list > >>>>> Linux-il at cs.huji.ac.il > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > >>>>> > >>>> _______________________________________________ > >> Linux-il mailing list > >> Linux-il at cs.huji.ac.il > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > >> > > > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il -- Efraim Flashner ????? ????? GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From uri at speedy.net Thu Jun 11 09:38:48 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 09:38:48 +0300 Subject: Ubuntu - apache is not working In-Reply-To: <20200611063839.GF963@E5400> References: <20200611063839.GF963@E5400> Message-ID: How do I remove it? ???? uri at speedy.net On Thu, Jun 11, 2020 at 9:39 AM Efraim Flashner wrote: > If you no longer need python-3.6 then you can remove that PPA from your > list of sources. > > On Thu, Jun 11, 2020 at 08:05:10AM +0300, ???? wrote: > > I ran the commands again and found out there are errors: > > > > root at www:~# sudo apt autoremove > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > root at www:~# sudo apt-get update > > Hit:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease > > Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 > kB] > > Err:3 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic > InRelease > > 403 Forbidden [IP: 91.189.95.83 80] > > Hit:4 http://archive.ubuntu.com/ubuntu bionic InRelease > > Hit:5 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease > > Hit:6 http://mirrors.digitalocean.com/ubuntu bionic InRelease > > Hit:7 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease > > Reading package lists... Done > > E: Failed to fetch > > > http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease > > 403 Forbidden [IP: 91.189.95.83 80] > > E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu > > bionic InRelease' is no longer signed. > > N: Updating from such a repository can't be done securely, and is > therefore > > disabled by default. > > N: See apt-secure(8) manpage for repository creation and user > configuration > > details. > > root at www:~# sudo apt-get upgrade > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Calculating upgrade... Done > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > root at www:~# sudo apt update > > Hit:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease > > Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease > > Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease > > Err:4 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic > InRelease > > 403 Forbidden [IP: 91.189.95.83 80] > > Hit:5 http://mirrors.digitalocean.com/ubuntu bionic InRelease > > Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease > > Hit:7 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease > > Reading package lists... Done > > E: Failed to fetch > > > http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease > > 403 Forbidden [IP: 91.189.95.83 80] > > E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu > > bionic InRelease' is no longer signed. > > N: Updating from such a repository can't be done securely, and is > therefore > > disabled by default. > > N: See apt-secure(8) manpage for repository creation and user > configuration > > details. > > root at www:~# sudo apt upgrade > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Calculating upgrade... Done > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > > > ???? > > uri at speedy.net > > > > > > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: > > > > > Please run: > > > apachectl start > > > from the command line, and copy the response to this list. > > > If there is no error, please copy the relevant lines from the > error.log of > > > apache2. > > > > > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: > > > > > >> Hi, > > >> > > >> Running the command "sudo apachectl configtest" returns "Syntax OK". > > >> > > >> Running "sudo systemctl restart apache2" doesn't respond. But a few > > >> minutes ago it worked and the website worked. I rebooted again and now > > >> again it's not working. The problem is that apache doesn't restart > after > > >> rebooting. > > >> > > >> ???? > > >> uri at speedy.net > > >> > > >> > > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? > > >> > > >>> Hi, > > >>> > > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I > ran a > > >>> few times the following commands (from root): > > >>> > > >>> sudo apt autoremove > > >>> sudo apt-get update > > >>> sudo apt-get upgrade > > >>> sudo apt update > > >>> sudo apt upgrade > > >>> > > >>> I have 4 servers and I upgraded all of them and 3 of them are working > > >>> properly, however one server apache is not working, I can't restart > apache > > >>> (with "sudo systemctl restart apache2" - it's not responding) and the > > >>> website is not working. How can I fix it now? > > >>> > > >>> The server didn't respond after reboot once (after 2 reboots) and I > had > > >>> to shut it down and restart it again. > > >>> > > >>> Thanks, > > >>> Uri > > >>> ???? > > >>> uri at speedy.net > > >>> > > >>> > > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey > > > >>> wrote: > > >>> > > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. > > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In > fact, > > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need > to go out > > >>>> of your way to get it) until 20.04.1 is out in a few months. > > >>>> > > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my > > >>>> understanding is that point releases aren?t new versions of Ubuntu > per se. > > >>>> At point releases, new isos are spun with up-to-date packages, but > it?s > > >>>> still the same version. Assuming you make a habit of installing > updates > > >>>> regularly (which you obviously should be), you will effectively > > >>>> automatically be on 18.04.4. > > >>>> > > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: > > >>>> > > >>>>> Hi, > > >>>>> > > >>>>> Actually I have a staging server which I can upgrade first to > 18.04.4 > > >>>>> to see if it works, or if something breaks. But I didn't find it > on Google > > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without > upgrading > > >>>>> it to 20.04? > > >>>>> > > >>>>> ???? > > >>>>> uri at speedy.net > > >>>>> > > >>>>> > > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish > wrote: > > >>>>> > > >>>>>> Hi Uri! > > >>>>>> > > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? > > >>>>>> > > >>>>>>> Hi, > > >>>>>>> > > >>>>>>> I'm sorry for posting twice in the same day to the same mailing > > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a > few > > >>>>>>> production servers (one of them I upgraded a few months ago from > 14.04). > > >>>>>>> How important it is to upgrade the OS version, or can I keep it > like this? > > >>>>>>> I'm afraid that things will break up if I upgrade. And if I > upgrade, should > > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has > been recently > > >>>>>>> released, it might have bugs which will be fixed later, and I > prefer not to > > >>>>>>> use the first version of 20.04 but to wait about one year before > I use it. > > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade > at least to > > >>>>>>> 18.04.4? > > >>>>>>> > > >>>>>>> > > >>>>>> I've answered the general question here: > > >>>>>> > > >>>>>> > > >>>>>> > https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality > > >>>>>> > > >>>>>> Quoting it: > > >>>>>> > > >>>>>> Will a change I would like to do break some functionality? > > >>>>>> > > >>>>>> As the aphorism > > >>>>>> < > https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 > > > > >>>>>> goes: The difference between theory and practice is that in > theory, > > >>>>>> there is no difference between theory and practice, while in > practice, > > >>>>>> there is.. There is usually a risk, however small, that a change > > >>>>>> will break some functionality. With good tooling (such as > > >>>>>> https://en.wikipedia.org/wiki/Version_control , > > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and > > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it > should be > > >>>>>> relatively easy to revert a change which introduced regressions, > and you > > >>>>>> should do adequate testing. > > >>>>>> > > >>>>>> A change may have to be avoided due to being estimated as too > time or > > >>>>>> money consuming, or as having too little gain. However, promising > changes > > >>>>>> should be attempted because: > > >>>>>> > > >>>>>> 1. "No guts - no glory." > > >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? > > >>>>>> < > https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html > > > > >>>>>> 3. If you never change anything, your project won't progress. > > >>>>>> > > >>>>>> ---------- > > >>>>>> While you may break some functionality by updating to 18.04.04 , > you > > >>>>>> also risk being affected by known security vulnerabilities (which > may also > > >>>>>> break functionality sooner or later). There is a concept of > > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . > > >>>>>> > > >>>>>> Regarding updating to 20.04, it is likely more time consuming and > may > > >>>>>> have more breaking changes, and you may not need all the newest > and > > >>>>>> shiniest software versions there, and you may wish to only update > to ubuntu > > >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu > 20.04 being > > >>>>>> unusable or unstable, but I'm quite out of the loop. > > >>>>>> > > >>>>>> Good luck! > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>>> Thanks, > > >>>>>>> Uri. > > >>>>>>> ???? > > >>>>>>> uri at speedy.net > > >>>>>>> _______________________________________________ > > >>>>>>> Linux-il mailing list > > >>>>>>> Linux-il at cs.huji.ac.il > > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >>>>>>> > > >>>>>> > > >>>>>> > > >>>>>> -- > > >>>>>> Shlomi Fish https://www.shlomifish.org/ > > >>>>>> > > >>>>>> Buddha has the Chuck Norris nature. > > >>>>>> > > >>>>>> Please reply to list if it's a mailing list post - > > >>>>>> http://shlom.in/reply . > > >>>>>> > > >>>>> _______________________________________________ > > >>>>> Linux-il mailing list > > >>>>> Linux-il at cs.huji.ac.il > > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >>>>> > > >>>> _______________________________________________ > > >> Linux-il mailing list > > >> Linux-il at cs.huji.ac.il > > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >> > > > > > > _______________________________________________ > > Linux-il mailing list > > Linux-il at cs.huji.ac.il > > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > > -- > Efraim Flashner ????? ????? > GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 > Confidentiality cannot be guaranteed on emails sent or received unencrypted > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 09:39:12 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 09:39:12 +0300 Subject: Ubuntu - apache is not working In-Reply-To: <20200611063839.GF963@E5400> References: <20200611063839.GF963@E5400> Message-ID: I think I need Python. ???? uri at speedy.net On Thu, Jun 11, 2020 at 9:39 AM Efraim Flashner wrote: > If you no longer need python-3.6 then you can remove that PPA from your > list of sources. > > On Thu, Jun 11, 2020 at 08:05:10AM +0300, ???? wrote: > > I ran the commands again and found out there are errors: > > > > root at www:~# sudo apt autoremove > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > root at www:~# sudo apt-get update > > Hit:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease > > Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 > kB] > > Err:3 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic > InRelease > > 403 Forbidden [IP: 91.189.95.83 80] > > Hit:4 http://archive.ubuntu.com/ubuntu bionic InRelease > > Hit:5 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease > > Hit:6 http://mirrors.digitalocean.com/ubuntu bionic InRelease > > Hit:7 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease > > Reading package lists... Done > > E: Failed to fetch > > > http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease > > 403 Forbidden [IP: 91.189.95.83 80] > > E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu > > bionic InRelease' is no longer signed. > > N: Updating from such a repository can't be done securely, and is > therefore > > disabled by default. > > N: See apt-secure(8) manpage for repository creation and user > configuration > > details. > > root at www:~# sudo apt-get upgrade > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Calculating upgrade... Done > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > root at www:~# sudo apt update > > Hit:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease > > Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease > > Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease > > Err:4 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic > InRelease > > 403 Forbidden [IP: 91.189.95.83 80] > > Hit:5 http://mirrors.digitalocean.com/ubuntu bionic InRelease > > Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease > > Hit:7 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease > > Reading package lists... Done > > E: Failed to fetch > > > http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease > > 403 Forbidden [IP: 91.189.95.83 80] > > E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu > > bionic InRelease' is no longer signed. > > N: Updating from such a repository can't be done securely, and is > therefore > > disabled by default. > > N: See apt-secure(8) manpage for repository creation and user > configuration > > details. > > root at www:~# sudo apt upgrade > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Calculating upgrade... Done > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > > > ???? > > uri at speedy.net > > > > > > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: > > > > > Please run: > > > apachectl start > > > from the command line, and copy the response to this list. > > > If there is no error, please copy the relevant lines from the > error.log of > > > apache2. > > > > > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: > > > > > >> Hi, > > >> > > >> Running the command "sudo apachectl configtest" returns "Syntax OK". > > >> > > >> Running "sudo systemctl restart apache2" doesn't respond. But a few > > >> minutes ago it worked and the website worked. I rebooted again and now > > >> again it's not working. The problem is that apache doesn't restart > after > > >> rebooting. > > >> > > >> ???? > > >> uri at speedy.net > > >> > > >> > > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? > > >> > > >>> Hi, > > >>> > > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I > ran a > > >>> few times the following commands (from root): > > >>> > > >>> sudo apt autoremove > > >>> sudo apt-get update > > >>> sudo apt-get upgrade > > >>> sudo apt update > > >>> sudo apt upgrade > > >>> > > >>> I have 4 servers and I upgraded all of them and 3 of them are working > > >>> properly, however one server apache is not working, I can't restart > apache > > >>> (with "sudo systemctl restart apache2" - it's not responding) and the > > >>> website is not working. How can I fix it now? > > >>> > > >>> The server didn't respond after reboot once (after 2 reboots) and I > had > > >>> to shut it down and restart it again. > > >>> > > >>> Thanks, > > >>> Uri > > >>> ???? > > >>> uri at speedy.net > > >>> > > >>> > > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey > > > >>> wrote: > > >>> > > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. > > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In > fact, > > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need > to go out > > >>>> of your way to get it) until 20.04.1 is out in a few months. > > >>>> > > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my > > >>>> understanding is that point releases aren?t new versions of Ubuntu > per se. > > >>>> At point releases, new isos are spun with up-to-date packages, but > it?s > > >>>> still the same version. Assuming you make a habit of installing > updates > > >>>> regularly (which you obviously should be), you will effectively > > >>>> automatically be on 18.04.4. > > >>>> > > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: > > >>>> > > >>>>> Hi, > > >>>>> > > >>>>> Actually I have a staging server which I can upgrade first to > 18.04.4 > > >>>>> to see if it works, or if something breaks. But I didn't find it > on Google > > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without > upgrading > > >>>>> it to 20.04? > > >>>>> > > >>>>> ???? > > >>>>> uri at speedy.net > > >>>>> > > >>>>> > > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish > wrote: > > >>>>> > > >>>>>> Hi Uri! > > >>>>>> > > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? > > >>>>>> > > >>>>>>> Hi, > > >>>>>>> > > >>>>>>> I'm sorry for posting twice in the same day to the same mailing > > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a > few > > >>>>>>> production servers (one of them I upgraded a few months ago from > 14.04). > > >>>>>>> How important it is to upgrade the OS version, or can I keep it > like this? > > >>>>>>> I'm afraid that things will break up if I upgrade. And if I > upgrade, should > > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has > been recently > > >>>>>>> released, it might have bugs which will be fixed later, and I > prefer not to > > >>>>>>> use the first version of 20.04 but to wait about one year before > I use it. > > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade > at least to > > >>>>>>> 18.04.4? > > >>>>>>> > > >>>>>>> > > >>>>>> I've answered the general question here: > > >>>>>> > > >>>>>> > > >>>>>> > https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality > > >>>>>> > > >>>>>> Quoting it: > > >>>>>> > > >>>>>> Will a change I would like to do break some functionality? > > >>>>>> > > >>>>>> As the aphorism > > >>>>>> < > https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 > > > > >>>>>> goes: The difference between theory and practice is that in > theory, > > >>>>>> there is no difference between theory and practice, while in > practice, > > >>>>>> there is.. There is usually a risk, however small, that a change > > >>>>>> will break some functionality. With good tooling (such as > > >>>>>> https://en.wikipedia.org/wiki/Version_control , > > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and > > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it > should be > > >>>>>> relatively easy to revert a change which introduced regressions, > and you > > >>>>>> should do adequate testing. > > >>>>>> > > >>>>>> A change may have to be avoided due to being estimated as too > time or > > >>>>>> money consuming, or as having too little gain. However, promising > changes > > >>>>>> should be attempted because: > > >>>>>> > > >>>>>> 1. "No guts - no glory." > > >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? > > >>>>>> < > https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html > > > > >>>>>> 3. If you never change anything, your project won't progress. > > >>>>>> > > >>>>>> ---------- > > >>>>>> While you may break some functionality by updating to 18.04.04 , > you > > >>>>>> also risk being affected by known security vulnerabilities (which > may also > > >>>>>> break functionality sooner or later). There is a concept of > > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . > > >>>>>> > > >>>>>> Regarding updating to 20.04, it is likely more time consuming and > may > > >>>>>> have more breaking changes, and you may not need all the newest > and > > >>>>>> shiniest software versions there, and you may wish to only update > to ubuntu > > >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu > 20.04 being > > >>>>>> unusable or unstable, but I'm quite out of the loop. > > >>>>>> > > >>>>>> Good luck! > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>>> Thanks, > > >>>>>>> Uri. > > >>>>>>> ???? > > >>>>>>> uri at speedy.net > > >>>>>>> _______________________________________________ > > >>>>>>> Linux-il mailing list > > >>>>>>> Linux-il at cs.huji.ac.il > > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >>>>>>> > > >>>>>> > > >>>>>> > > >>>>>> -- > > >>>>>> Shlomi Fish https://www.shlomifish.org/ > > >>>>>> > > >>>>>> Buddha has the Chuck Norris nature. > > >>>>>> > > >>>>>> Please reply to list if it's a mailing list post - > > >>>>>> http://shlom.in/reply . > > >>>>>> > > >>>>> _______________________________________________ > > >>>>> Linux-il mailing list > > >>>>> Linux-il at cs.huji.ac.il > > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >>>>> > > >>>> _______________________________________________ > > >> Linux-il mailing list > > >> Linux-il at cs.huji.ac.il > > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >> > > > > > > _______________________________________________ > > Linux-il mailing list > > Linux-il at cs.huji.ac.il > > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > > -- > Efraim Flashner ????? ????? > GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 > Confidentiality cannot be guaranteed on emails sent or received unencrypted > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 09:39:58 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 09:39:58 +0300 Subject: Ubuntu - apache is not working In-Reply-To: <20200611063805.GE963@E5400> References: <20200611063805.GE963@E5400> Message-ID: # systemctl status apache2.service ? apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d ??apache2-systemd.conf Active: active (running) since Thu 2020-06-11 06:27:34 CEST; 2h 13min ago Process: 1231 ExecStop=/usr/sbin/apachectl stop (code=exited, status=0/SUCCESS) Process: 1246 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS) Main PID: 1250 (apache2) CGroup: /system.slice/apache2.service ??1250 /usr/sbin/apache2 -k start ??1251 /usr/sbin/apache2 -k start ??1252 /usr/sbin/apache2 -k start ??1255 /usr/sbin/apache2 -k start ??1261 /usr/sbin/apache2 -k start ??1262 /usr/sbin/apache2 -k start ??1265 /usr/sbin/apache2 -k start ??3475 /usr/sbin/apache2 -k start ??3526 /usr/sbin/apache2 -k start ??3527 /usr/sbin/apache2 -k start ??3660 /usr/sbin/apache2 -k start Jun 11 06:27:34 www.speedypedia.info systemd[1]: Starting The Apache HTTP Server... Jun 11 06:27:34 www.speedypedia.info systemd[1]: Started The Apache HTTP Server. ???? uri at speedy.net On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner wrote: > Not sure why apache is only starting some time after you reboot. What > does the output of 'systemctl status apache2.service' look like? > > On Thu, Jun 11, 2020 at 07:31:31AM +0300, ???? wrote: > > Hi, > > > > I estimate it's about 15 to 20 minutes after reboot that I can start > apache > > successfully. Otherwise, I can't start apache. > > > > ???? > > uri at speedy.net > > > > > > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: > > > > > Please run: > > > apachectl start > > > from the command line, and copy the response to this list. > > > If there is no error, please copy the relevant lines from the > error.log of > > > apache2. > > > > > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: > > > > > >> Hi, > > >> > > >> Running the command "sudo apachectl configtest" returns "Syntax OK". > > >> > > >> Running "sudo systemctl restart apache2" doesn't respond. But a few > > >> minutes ago it worked and the website worked. I rebooted again and now > > >> again it's not working. The problem is that apache doesn't restart > after > > >> rebooting. > > >> > > >> ???? > > >> uri at speedy.net > > >> > > >> > > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? > > >> > > >>> Hi, > > >>> > > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I > ran a > > >>> few times the following commands (from root): > > >>> > > >>> sudo apt autoremove > > >>> sudo apt-get update > > >>> sudo apt-get upgrade > > >>> sudo apt update > > >>> sudo apt upgrade > > >>> > > >>> I have 4 servers and I upgraded all of them and 3 of them are working > > >>> properly, however one server apache is not working, I can't restart > apache > > >>> (with "sudo systemctl restart apache2" - it's not responding) and the > > >>> website is not working. How can I fix it now? > > >>> > > >>> The server didn't respond after reboot once (after 2 reboots) and I > had > > >>> to shut it down and restart it again. > > >>> > > >>> Thanks, > > >>> Uri > > >>> ???? > > >>> uri at speedy.net > > >>> > > >>> > > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey > > > >>> wrote: > > >>> > > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. > > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In > fact, > > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need > to go out > > >>>> of your way to get it) until 20.04.1 is out in a few months. > > >>>> > > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my > > >>>> understanding is that point releases aren?t new versions of Ubuntu > per se. > > >>>> At point releases, new isos are spun with up-to-date packages, but > it?s > > >>>> still the same version. Assuming you make a habit of installing > updates > > >>>> regularly (which you obviously should be), you will effectively > > >>>> automatically be on 18.04.4. > > >>>> > > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: > > >>>> > > >>>>> Hi, > > >>>>> > > >>>>> Actually I have a staging server which I can upgrade first to > 18.04.4 > > >>>>> to see if it works, or if something breaks. But I didn't find it > on Google > > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without > upgrading > > >>>>> it to 20.04? > > >>>>> > > >>>>> ???? > > >>>>> uri at speedy.net > > >>>>> > > >>>>> > > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish > wrote: > > >>>>> > > >>>>>> Hi Uri! > > >>>>>> > > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? > > >>>>>> > > >>>>>>> Hi, > > >>>>>>> > > >>>>>>> I'm sorry for posting twice in the same day to the same mailing > > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a > few > > >>>>>>> production servers (one of them I upgraded a few months ago from > 14.04). > > >>>>>>> How important it is to upgrade the OS version, or can I keep it > like this? > > >>>>>>> I'm afraid that things will break up if I upgrade. And if I > upgrade, should > > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has > been recently > > >>>>>>> released, it might have bugs which will be fixed later, and I > prefer not to > > >>>>>>> use the first version of 20.04 but to wait about one year before > I use it. > > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade > at least to > > >>>>>>> 18.04.4? > > >>>>>>> > > >>>>>>> > > >>>>>> I've answered the general question here: > > >>>>>> > > >>>>>> > > >>>>>> > https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality > > >>>>>> > > >>>>>> Quoting it: > > >>>>>> > > >>>>>> Will a change I would like to do break some functionality? > > >>>>>> > > >>>>>> As the aphorism > > >>>>>> < > https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 > > > > >>>>>> goes: The difference between theory and practice is that in > theory, > > >>>>>> there is no difference between theory and practice, while in > practice, > > >>>>>> there is.. There is usually a risk, however small, that a change > > >>>>>> will break some functionality. With good tooling (such as > > >>>>>> https://en.wikipedia.org/wiki/Version_control , > > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and > > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it > should be > > >>>>>> relatively easy to revert a change which introduced regressions, > and you > > >>>>>> should do adequate testing. > > >>>>>> > > >>>>>> A change may have to be avoided due to being estimated as too > time or > > >>>>>> money consuming, or as having too little gain. However, promising > changes > > >>>>>> should be attempted because: > > >>>>>> > > >>>>>> 1. "No guts - no glory." > > >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? > > >>>>>> < > https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html > > > > >>>>>> 3. If you never change anything, your project won't progress. > > >>>>>> > > >>>>>> ---------- > > >>>>>> While you may break some functionality by updating to 18.04.04 , > you > > >>>>>> also risk being affected by known security vulnerabilities (which > may also > > >>>>>> break functionality sooner or later). There is a concept of > > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . > > >>>>>> > > >>>>>> Regarding updating to 20.04, it is likely more time consuming and > may > > >>>>>> have more breaking changes, and you may not need all the newest > and > > >>>>>> shiniest software versions there, and you may wish to only update > to ubuntu > > >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu > 20.04 being > > >>>>>> unusable or unstable, but I'm quite out of the loop. > > >>>>>> > > >>>>>> Good luck! > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>>> Thanks, > > >>>>>>> Uri. > > >>>>>>> ???? > > >>>>>>> uri at speedy.net > > >>>>>>> _______________________________________________ > > >>>>>>> Linux-il mailing list > > >>>>>>> Linux-il at cs.huji.ac.il > > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >>>>>>> > > >>>>>> > > >>>>>> > > >>>>>> -- > > >>>>>> Shlomi Fish https://www.shlomifish.org/ > > >>>>>> > > >>>>>> Buddha has the Chuck Norris nature. > > >>>>>> > > >>>>>> Please reply to list if it's a mailing list post - > > >>>>>> http://shlom.in/reply . > > >>>>>> > > >>>>> _______________________________________________ > > >>>>> Linux-il mailing list > > >>>>> Linux-il at cs.huji.ac.il > > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >>>>> > > >>>> _______________________________________________ > > >> Linux-il mailing list > > >> Linux-il at cs.huji.ac.il > > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >> > > > > > > _______________________________________________ > > Linux-il mailing list > > Linux-il at cs.huji.ac.il > > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > > -- > Efraim Flashner ????? ????? > GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 > Confidentiality cannot be guaranteed on emails sent or received unencrypted > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 09:40:35 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 09:40:35 +0300 Subject: Ubuntu - apache is not working In-Reply-To: <20200611063805.GE963@E5400> References: <20200611063805.GE963@E5400> Message-ID: Do you want me to run that again after reboot? ???? uri at speedy.net On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner wrote: > Not sure why apache is only starting some time after you reboot. What > does the output of 'systemctl status apache2.service' look like? > > On Thu, Jun 11, 2020 at 07:31:31AM +0300, ???? wrote: > > Hi, > > > > I estimate it's about 15 to 20 minutes after reboot that I can start > apache > > successfully. Otherwise, I can't start apache. > > > > ???? > > uri at speedy.net > > > > > > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: > > > > > Please run: > > > apachectl start > > > from the command line, and copy the response to this list. > > > If there is no error, please copy the relevant lines from the > error.log of > > > apache2. > > > > > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: > > > > > >> Hi, > > >> > > >> Running the command "sudo apachectl configtest" returns "Syntax OK". > > >> > > >> Running "sudo systemctl restart apache2" doesn't respond. But a few > > >> minutes ago it worked and the website worked. I rebooted again and now > > >> again it's not working. The problem is that apache doesn't restart > after > > >> rebooting. > > >> > > >> ???? > > >> uri at speedy.net > > >> > > >> > > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? > > >> > > >>> Hi, > > >>> > > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I > ran a > > >>> few times the following commands (from root): > > >>> > > >>> sudo apt autoremove > > >>> sudo apt-get update > > >>> sudo apt-get upgrade > > >>> sudo apt update > > >>> sudo apt upgrade > > >>> > > >>> I have 4 servers and I upgraded all of them and 3 of them are working > > >>> properly, however one server apache is not working, I can't restart > apache > > >>> (with "sudo systemctl restart apache2" - it's not responding) and the > > >>> website is not working. How can I fix it now? > > >>> > > >>> The server didn't respond after reboot once (after 2 reboots) and I > had > > >>> to shut it down and restart it again. > > >>> > > >>> Thanks, > > >>> Uri > > >>> ???? > > >>> uri at speedy.net > > >>> > > >>> > > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey > > > >>> wrote: > > >>> > > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. > > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In > fact, > > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need > to go out > > >>>> of your way to get it) until 20.04.1 is out in a few months. > > >>>> > > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my > > >>>> understanding is that point releases aren?t new versions of Ubuntu > per se. > > >>>> At point releases, new isos are spun with up-to-date packages, but > it?s > > >>>> still the same version. Assuming you make a habit of installing > updates > > >>>> regularly (which you obviously should be), you will effectively > > >>>> automatically be on 18.04.4. > > >>>> > > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: > > >>>> > > >>>>> Hi, > > >>>>> > > >>>>> Actually I have a staging server which I can upgrade first to > 18.04.4 > > >>>>> to see if it works, or if something breaks. But I didn't find it > on Google > > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without > upgrading > > >>>>> it to 20.04? > > >>>>> > > >>>>> ???? > > >>>>> uri at speedy.net > > >>>>> > > >>>>> > > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish > wrote: > > >>>>> > > >>>>>> Hi Uri! > > >>>>>> > > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? > > >>>>>> > > >>>>>>> Hi, > > >>>>>>> > > >>>>>>> I'm sorry for posting twice in the same day to the same mailing > > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a > few > > >>>>>>> production servers (one of them I upgraded a few months ago from > 14.04). > > >>>>>>> How important it is to upgrade the OS version, or can I keep it > like this? > > >>>>>>> I'm afraid that things will break up if I upgrade. And if I > upgrade, should > > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has > been recently > > >>>>>>> released, it might have bugs which will be fixed later, and I > prefer not to > > >>>>>>> use the first version of 20.04 but to wait about one year before > I use it. > > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade > at least to > > >>>>>>> 18.04.4? > > >>>>>>> > > >>>>>>> > > >>>>>> I've answered the general question here: > > >>>>>> > > >>>>>> > > >>>>>> > https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality > > >>>>>> > > >>>>>> Quoting it: > > >>>>>> > > >>>>>> Will a change I would like to do break some functionality? > > >>>>>> > > >>>>>> As the aphorism > > >>>>>> < > https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 > > > > >>>>>> goes: The difference between theory and practice is that in > theory, > > >>>>>> there is no difference between theory and practice, while in > practice, > > >>>>>> there is.. There is usually a risk, however small, that a change > > >>>>>> will break some functionality. With good tooling (such as > > >>>>>> https://en.wikipedia.org/wiki/Version_control , > > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and > > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it > should be > > >>>>>> relatively easy to revert a change which introduced regressions, > and you > > >>>>>> should do adequate testing. > > >>>>>> > > >>>>>> A change may have to be avoided due to being estimated as too > time or > > >>>>>> money consuming, or as having too little gain. However, promising > changes > > >>>>>> should be attempted because: > > >>>>>> > > >>>>>> 1. "No guts - no glory." > > >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? > > >>>>>> < > https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html > > > > >>>>>> 3. If you never change anything, your project won't progress. > > >>>>>> > > >>>>>> ---------- > > >>>>>> While you may break some functionality by updating to 18.04.04 , > you > > >>>>>> also risk being affected by known security vulnerabilities (which > may also > > >>>>>> break functionality sooner or later). There is a concept of > > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . > > >>>>>> > > >>>>>> Regarding updating to 20.04, it is likely more time consuming and > may > > >>>>>> have more breaking changes, and you may not need all the newest > and > > >>>>>> shiniest software versions there, and you may wish to only update > to ubuntu > > >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu > 20.04 being > > >>>>>> unusable or unstable, but I'm quite out of the loop. > > >>>>>> > > >>>>>> Good luck! > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>>> Thanks, > > >>>>>>> Uri. > > >>>>>>> ???? > > >>>>>>> uri at speedy.net > > >>>>>>> _______________________________________________ > > >>>>>>> Linux-il mailing list > > >>>>>>> Linux-il at cs.huji.ac.il > > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >>>>>>> > > >>>>>> > > >>>>>> > > >>>>>> -- > > >>>>>> Shlomi Fish https://www.shlomifish.org/ > > >>>>>> > > >>>>>> Buddha has the Chuck Norris nature. > > >>>>>> > > >>>>>> Please reply to list if it's a mailing list post - > > >>>>>> http://shlom.in/reply . > > >>>>>> > > >>>>> _______________________________________________ > > >>>>> Linux-il mailing list > > >>>>> Linux-il at cs.huji.ac.il > > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >>>>> > > >>>> _______________________________________________ > > >> Linux-il mailing list > > >> Linux-il at cs.huji.ac.il > > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >> > > > > > > _______________________________________________ > > Linux-il mailing list > > Linux-il at cs.huji.ac.il > > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > > -- > Efraim Flashner ????? ????? > GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 > Confidentiality cannot be guaranteed on emails sent or received unencrypted > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 09:44:13 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 09:44:13 +0300 Subject: Ubuntu - apache is not working In-Reply-To: <20200611063805.GE963@E5400> References: <20200611063805.GE963@E5400> Message-ID: Here, after reboot (and apache is not working again): # systemctl status apache2.service ? apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d ??apache2-systemd.conf Active: activating (start) since Thu 2020-06-11 08:43:03 CEST; 1min 26s ago Cntrl PID: 577 (apachectl) CGroup: /system.slice/apache2.service ??577 /bin/sh /usr/sbin/apachectl start ??600 /usr/sbin/apache2 -k start Jun 11 08:43:03 www.speedypedia.info systemd[1]: Starting The Apache HTTP Server... ???? uri at speedy.net On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner wrote: > Not sure why apache is only starting some time after you reboot. What > does the output of 'systemctl status apache2.service' look like? > > On Thu, Jun 11, 2020 at 07:31:31AM +0300, ???? wrote: > > Hi, > > > > I estimate it's about 15 to 20 minutes after reboot that I can start > apache > > successfully. Otherwise, I can't start apache. > > > > ???? > > uri at speedy.net > > > > > > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: > > > > > Please run: > > > apachectl start > > > from the command line, and copy the response to this list. > > > If there is no error, please copy the relevant lines from the > error.log of > > > apache2. > > > > > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: > > > > > >> Hi, > > >> > > >> Running the command "sudo apachectl configtest" returns "Syntax OK". > > >> > > >> Running "sudo systemctl restart apache2" doesn't respond. But a few > > >> minutes ago it worked and the website worked. I rebooted again and now > > >> again it's not working. The problem is that apache doesn't restart > after > > >> rebooting. > > >> > > >> ???? > > >> uri at speedy.net > > >> > > >> > > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? > > >> > > >>> Hi, > > >>> > > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I > ran a > > >>> few times the following commands (from root): > > >>> > > >>> sudo apt autoremove > > >>> sudo apt-get update > > >>> sudo apt-get upgrade > > >>> sudo apt update > > >>> sudo apt upgrade > > >>> > > >>> I have 4 servers and I upgraded all of them and 3 of them are working > > >>> properly, however one server apache is not working, I can't restart > apache > > >>> (with "sudo systemctl restart apache2" - it's not responding) and the > > >>> website is not working. How can I fix it now? > > >>> > > >>> The server didn't respond after reboot once (after 2 reboots) and I > had > > >>> to shut it down and restart it again. > > >>> > > >>> Thanks, > > >>> Uri > > >>> ???? > > >>> uri at speedy.net > > >>> > > >>> > > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey > > > >>> wrote: > > >>> > > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. > > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In > fact, > > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need > to go out > > >>>> of your way to get it) until 20.04.1 is out in a few months. > > >>>> > > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my > > >>>> understanding is that point releases aren?t new versions of Ubuntu > per se. > > >>>> At point releases, new isos are spun with up-to-date packages, but > it?s > > >>>> still the same version. Assuming you make a habit of installing > updates > > >>>> regularly (which you obviously should be), you will effectively > > >>>> automatically be on 18.04.4. > > >>>> > > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: > > >>>> > > >>>>> Hi, > > >>>>> > > >>>>> Actually I have a staging server which I can upgrade first to > 18.04.4 > > >>>>> to see if it works, or if something breaks. But I didn't find it > on Google > > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without > upgrading > > >>>>> it to 20.04? > > >>>>> > > >>>>> ???? > > >>>>> uri at speedy.net > > >>>>> > > >>>>> > > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish > wrote: > > >>>>> > > >>>>>> Hi Uri! > > >>>>>> > > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? > > >>>>>> > > >>>>>>> Hi, > > >>>>>>> > > >>>>>>> I'm sorry for posting twice in the same day to the same mailing > > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a > few > > >>>>>>> production servers (one of them I upgraded a few months ago from > 14.04). > > >>>>>>> How important it is to upgrade the OS version, or can I keep it > like this? > > >>>>>>> I'm afraid that things will break up if I upgrade. And if I > upgrade, should > > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has > been recently > > >>>>>>> released, it might have bugs which will be fixed later, and I > prefer not to > > >>>>>>> use the first version of 20.04 but to wait about one year before > I use it. > > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade > at least to > > >>>>>>> 18.04.4? > > >>>>>>> > > >>>>>>> > > >>>>>> I've answered the general question here: > > >>>>>> > > >>>>>> > > >>>>>> > https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality > > >>>>>> > > >>>>>> Quoting it: > > >>>>>> > > >>>>>> Will a change I would like to do break some functionality? > > >>>>>> > > >>>>>> As the aphorism > > >>>>>> < > https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 > > > > >>>>>> goes: The difference between theory and practice is that in > theory, > > >>>>>> there is no difference between theory and practice, while in > practice, > > >>>>>> there is.. There is usually a risk, however small, that a change > > >>>>>> will break some functionality. With good tooling (such as > > >>>>>> https://en.wikipedia.org/wiki/Version_control , > > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and > > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it > should be > > >>>>>> relatively easy to revert a change which introduced regressions, > and you > > >>>>>> should do adequate testing. > > >>>>>> > > >>>>>> A change may have to be avoided due to being estimated as too > time or > > >>>>>> money consuming, or as having too little gain. However, promising > changes > > >>>>>> should be attempted because: > > >>>>>> > > >>>>>> 1. "No guts - no glory." > > >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? > > >>>>>> < > https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html > > > > >>>>>> 3. If you never change anything, your project won't progress. > > >>>>>> > > >>>>>> ---------- > > >>>>>> While you may break some functionality by updating to 18.04.04 , > you > > >>>>>> also risk being affected by known security vulnerabilities (which > may also > > >>>>>> break functionality sooner or later). There is a concept of > > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . > > >>>>>> > > >>>>>> Regarding updating to 20.04, it is likely more time consuming and > may > > >>>>>> have more breaking changes, and you may not need all the newest > and > > >>>>>> shiniest software versions there, and you may wish to only update > to ubuntu > > >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu > 20.04 being > > >>>>>> unusable or unstable, but I'm quite out of the loop. > > >>>>>> > > >>>>>> Good luck! > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>>> Thanks, > > >>>>>>> Uri. > > >>>>>>> ???? > > >>>>>>> uri at speedy.net > > >>>>>>> _______________________________________________ > > >>>>>>> Linux-il mailing list > > >>>>>>> Linux-il at cs.huji.ac.il > > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >>>>>>> > > >>>>>> > > >>>>>> > > >>>>>> -- > > >>>>>> Shlomi Fish https://www.shlomifish.org/ > > >>>>>> > > >>>>>> Buddha has the Chuck Norris nature. > > >>>>>> > > >>>>>> Please reply to list if it's a mailing list post - > > >>>>>> http://shlom.in/reply . > > >>>>>> > > >>>>> _______________________________________________ > > >>>>> Linux-il mailing list > > >>>>> Linux-il at cs.huji.ac.il > > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >>>>> > > >>>> _______________________________________________ > > >> Linux-il mailing list > > >> Linux-il at cs.huji.ac.il > > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >> > > > > > > _______________________________________________ > > Linux-il mailing list > > Linux-il at cs.huji.ac.il > > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > > -- > Efraim Flashner ????? ????? > GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 > Confidentiality cannot be guaranteed on emails sent or received unencrypted > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 09:45:46 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 09:45:46 +0300 Subject: Ubuntu - apache is not working In-Reply-To: <20200611063805.GE963@E5400> References: <20200611063805.GE963@E5400> Message-ID: # systemctl status apache2.service ? apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d ??apache2-systemd.conf Active: failed (Result: timeout) since Thu 2020-06-11 08:44:35 CEST; 2min 1s ago Process: 577 ExecStart=/usr/sbin/apachectl start (code=killed, signal=TERM) Jun 11 08:43:03 www.speedypedia.info systemd[1]: Starting The Apache HTTP Server... Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: Start operation timed out. Terminating. Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: Failed with result 'timeout'. Jun 11 08:44:35 www.speedypedia.info systemd[1]: Failed to start The Apache HTTP Server. ???? uri at speedy.net On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner wrote: > Not sure why apache is only starting some time after you reboot. What > does the output of 'systemctl status apache2.service' look like? > > On Thu, Jun 11, 2020 at 07:31:31AM +0300, ???? wrote: > > Hi, > > > > I estimate it's about 15 to 20 minutes after reboot that I can start > apache > > successfully. Otherwise, I can't start apache. > > > > ???? > > uri at speedy.net > > > > > > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: > > > > > Please run: > > > apachectl start > > > from the command line, and copy the response to this list. > > > If there is no error, please copy the relevant lines from the > error.log of > > > apache2. > > > > > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: > > > > > >> Hi, > > >> > > >> Running the command "sudo apachectl configtest" returns "Syntax OK". > > >> > > >> Running "sudo systemctl restart apache2" doesn't respond. But a few > > >> minutes ago it worked and the website worked. I rebooted again and now > > >> again it's not working. The problem is that apache doesn't restart > after > > >> rebooting. > > >> > > >> ???? > > >> uri at speedy.net > > >> > > >> > > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? > > >> > > >>> Hi, > > >>> > > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I > ran a > > >>> few times the following commands (from root): > > >>> > > >>> sudo apt autoremove > > >>> sudo apt-get update > > >>> sudo apt-get upgrade > > >>> sudo apt update > > >>> sudo apt upgrade > > >>> > > >>> I have 4 servers and I upgraded all of them and 3 of them are working > > >>> properly, however one server apache is not working, I can't restart > apache > > >>> (with "sudo systemctl restart apache2" - it's not responding) and the > > >>> website is not working. How can I fix it now? > > >>> > > >>> The server didn't respond after reboot once (after 2 reboots) and I > had > > >>> to shut it down and restart it again. > > >>> > > >>> Thanks, > > >>> Uri > > >>> ???? > > >>> uri at speedy.net > > >>> > > >>> > > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey > > > >>> wrote: > > >>> > > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. > > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In > fact, > > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need > to go out > > >>>> of your way to get it) until 20.04.1 is out in a few months. > > >>>> > > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my > > >>>> understanding is that point releases aren?t new versions of Ubuntu > per se. > > >>>> At point releases, new isos are spun with up-to-date packages, but > it?s > > >>>> still the same version. Assuming you make a habit of installing > updates > > >>>> regularly (which you obviously should be), you will effectively > > >>>> automatically be on 18.04.4. > > >>>> > > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: > > >>>> > > >>>>> Hi, > > >>>>> > > >>>>> Actually I have a staging server which I can upgrade first to > 18.04.4 > > >>>>> to see if it works, or if something breaks. But I didn't find it > on Google > > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without > upgrading > > >>>>> it to 20.04? > > >>>>> > > >>>>> ???? > > >>>>> uri at speedy.net > > >>>>> > > >>>>> > > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish > wrote: > > >>>>> > > >>>>>> Hi Uri! > > >>>>>> > > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? > > >>>>>> > > >>>>>>> Hi, > > >>>>>>> > > >>>>>>> I'm sorry for posting twice in the same day to the same mailing > > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a > few > > >>>>>>> production servers (one of them I upgraded a few months ago from > 14.04). > > >>>>>>> How important it is to upgrade the OS version, or can I keep it > like this? > > >>>>>>> I'm afraid that things will break up if I upgrade. And if I > upgrade, should > > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has > been recently > > >>>>>>> released, it might have bugs which will be fixed later, and I > prefer not to > > >>>>>>> use the first version of 20.04 but to wait about one year before > I use it. > > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade > at least to > > >>>>>>> 18.04.4? > > >>>>>>> > > >>>>>>> > > >>>>>> I've answered the general question here: > > >>>>>> > > >>>>>> > > >>>>>> > https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality > > >>>>>> > > >>>>>> Quoting it: > > >>>>>> > > >>>>>> Will a change I would like to do break some functionality? > > >>>>>> > > >>>>>> As the aphorism > > >>>>>> < > https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 > > > > >>>>>> goes: The difference between theory and practice is that in > theory, > > >>>>>> there is no difference between theory and practice, while in > practice, > > >>>>>> there is.. There is usually a risk, however small, that a change > > >>>>>> will break some functionality. With good tooling (such as > > >>>>>> https://en.wikipedia.org/wiki/Version_control , > > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and > > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it > should be > > >>>>>> relatively easy to revert a change which introduced regressions, > and you > > >>>>>> should do adequate testing. > > >>>>>> > > >>>>>> A change may have to be avoided due to being estimated as too > time or > > >>>>>> money consuming, or as having too little gain. However, promising > changes > > >>>>>> should be attempted because: > > >>>>>> > > >>>>>> 1. "No guts - no glory." > > >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? > > >>>>>> < > https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html > > > > >>>>>> 3. If you never change anything, your project won't progress. > > >>>>>> > > >>>>>> ---------- > > >>>>>> While you may break some functionality by updating to 18.04.04 , > you > > >>>>>> also risk being affected by known security vulnerabilities (which > may also > > >>>>>> break functionality sooner or later). There is a concept of > > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . > > >>>>>> > > >>>>>> Regarding updating to 20.04, it is likely more time consuming and > may > > >>>>>> have more breaking changes, and you may not need all the newest > and > > >>>>>> shiniest software versions there, and you may wish to only update > to ubuntu > > >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu > 20.04 being > > >>>>>> unusable or unstable, but I'm quite out of the loop. > > >>>>>> > > >>>>>> Good luck! > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>>> Thanks, > > >>>>>>> Uri. > > >>>>>>> ???? > > >>>>>>> uri at speedy.net > > >>>>>>> _______________________________________________ > > >>>>>>> Linux-il mailing list > > >>>>>>> Linux-il at cs.huji.ac.il > > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >>>>>>> > > >>>>>> > > >>>>>> > > >>>>>> -- > > >>>>>> Shlomi Fish https://www.shlomifish.org/ > > >>>>>> > > >>>>>> Buddha has the Chuck Norris nature. > > >>>>>> > > >>>>>> Please reply to list if it's a mailing list post - > > >>>>>> http://shlom.in/reply . > > >>>>>> > > >>>>> _______________________________________________ > > >>>>> Linux-il mailing list > > >>>>> Linux-il at cs.huji.ac.il > > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >>>>> > > >>>> _______________________________________________ > > >> Linux-il mailing list > > >> Linux-il at cs.huji.ac.il > > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > >> > > > > > > _______________________________________________ > > Linux-il mailing list > > Linux-il at cs.huji.ac.il > > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > > > -- > Efraim Flashner ????? ????? > GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 > Confidentiality cannot be guaranteed on emails sent or received unencrypted > -------------- next part -------------- An HTML attachment was scrubbed... URL: From govershay at gmail.com Thu Jun 11 09:48:49 2020 From: govershay at gmail.com (Shay Gover) Date: Thu, 11 Jun 2020 09:48:49 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: <20200611063805.GE963@E5400> Message-ID: What do u have in apache logs? ?On Thu, Jun 11, 2020 at 9:47 AM ??????? wrote:? > # systemctl status apache2.service > ? apache2.service - The Apache HTTP Server > Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor > preset: enabled) > Drop-In: /lib/systemd/system/apache2.service.d > ??apache2-systemd.conf > Active: failed (Result: timeout) since Thu 2020-06-11 08:44:35 CEST; > 2min 1s ago > Process: 577 ExecStart=/usr/sbin/apachectl start (code=killed, > signal=TERM) > > Jun 11 08:43:03 www.speedypedia.info systemd[1]: Starting The Apache HTTP > Server... > Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: Start > operation timed out. Terminating. > Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: Failed > with result 'timeout'. > Jun 11 08:44:35 www.speedypedia.info systemd[1]: Failed to start The > Apache HTTP Server. > ???? > uri at speedy.net > > > On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner > wrote: > >> Not sure why apache is only starting some time after you reboot. What >> does the output of 'systemctl status apache2.service' look like? >> >> On Thu, Jun 11, 2020 at 07:31:31AM +0300, ???? wrote: >> > Hi, >> > >> > I estimate it's about 15 to 20 minutes after reboot that I can start >> apache >> > successfully. Otherwise, I can't start apache. >> > >> > ???? >> > uri at speedy.net >> > >> > >> > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: >> > >> > > Please run: >> > > apachectl start >> > > from the command line, and copy the response to this list. >> > > If there is no error, please copy the relevant lines from the >> error.log of >> > > apache2. >> > > >> > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: >> > > >> > >> Hi, >> > >> >> > >> Running the command "sudo apachectl configtest" returns "Syntax OK". >> > >> >> > >> Running "sudo systemctl restart apache2" doesn't respond. But a few >> > >> minutes ago it worked and the website worked. I rebooted again and >> now >> > >> again it's not working. The problem is that apache doesn't restart >> after >> > >> rebooting. >> > >> >> > >> ???? >> > >> uri at speedy.net >> > >> >> > >> >> > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? >> > >> >> > >>> Hi, >> > >>> >> > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I >> ran a >> > >>> few times the following commands (from root): >> > >>> >> > >>> sudo apt autoremove >> > >>> sudo apt-get update >> > >>> sudo apt-get upgrade >> > >>> sudo apt update >> > >>> sudo apt upgrade >> > >>> >> > >>> I have 4 servers and I upgraded all of them and 3 of them are >> working >> > >>> properly, however one server apache is not working, I can't restart >> apache >> > >>> (with "sudo systemctl restart apache2" - it's not responding) and >> the >> > >>> website is not working. How can I fix it now? >> > >>> >> > >>> The server didn't respond after reboot once (after 2 reboots) and I >> had >> > >>> to shut it down and restart it again. >> > >>> >> > >>> Thanks, >> > >>> Uri >> > >>> ???? >> > >>> uri at speedy.net >> > >>> >> > >>> >> > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey < >> michabailey at gmail.com> >> > >>> wrote: >> > >>> >> > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. >> > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In >> fact, >> > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need >> to go out >> > >>>> of your way to get it) until 20.04.1 is out in a few months. >> > >>>> >> > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >> > >>>> understanding is that point releases aren?t new versions of Ubuntu >> per se. >> > >>>> At point releases, new isos are spun with up-to-date packages, but >> it?s >> > >>>> still the same version. Assuming you make a habit of installing >> updates >> > >>>> regularly (which you obviously should be), you will effectively >> > >>>> automatically be on 18.04.4. >> > >>>> >> > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >> > >>>> >> > >>>>> Hi, >> > >>>>> >> > >>>>> Actually I have a staging server which I can upgrade first to >> 18.04.4 >> > >>>>> to see if it works, or if something breaks. But I didn't find it >> on Google >> > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without >> upgrading >> > >>>>> it to 20.04? >> > >>>>> >> > >>>>> ???? >> > >>>>> uri at speedy.net >> > >>>>> >> > >>>>> >> > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish >> wrote: >> > >>>>> >> > >>>>>> Hi Uri! >> > >>>>>> >> > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? >> wrote:? >> > >>>>>> >> > >>>>>>> Hi, >> > >>>>>>> >> > >>>>>>> I'm sorry for posting twice in the same day to the same mailing >> > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a >> few >> > >>>>>>> production servers (one of them I upgraded a few months ago >> from 14.04). >> > >>>>>>> How important it is to upgrade the OS version, or can I keep it >> like this? >> > >>>>>>> I'm afraid that things will break up if I upgrade. And if I >> upgrade, should >> > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has >> been recently >> > >>>>>>> released, it might have bugs which will be fixed later, and I >> prefer not to >> > >>>>>>> use the first version of 20.04 but to wait about one year >> before I use it. >> > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade >> at least to >> > >>>>>>> 18.04.4? >> > >>>>>>> >> > >>>>>>> >> > >>>>>> I've answered the general question here: >> > >>>>>> >> > >>>>>> >> > >>>>>> >> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >> > >>>>>> >> > >>>>>> Quoting it: >> > >>>>>> >> > >>>>>> Will a change I would like to do break some functionality? >> > >>>>>> >> > >>>>>> As the aphorism >> > >>>>>> < >> https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 >> > >> > >>>>>> goes: The difference between theory and practice is that in >> theory, >> > >>>>>> there is no difference between theory and practice, while in >> practice, >> > >>>>>> there is.. There is usually a risk, however small, that a change >> > >>>>>> will break some functionality. With good tooling (such as >> > >>>>>> https://en.wikipedia.org/wiki/Version_control , >> > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and >> > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it >> should be >> > >>>>>> relatively easy to revert a change which introduced regressions, >> and you >> > >>>>>> should do adequate testing. >> > >>>>>> >> > >>>>>> A change may have to be avoided due to being estimated as too >> time or >> > >>>>>> money consuming, or as having too little gain. However, >> promising changes >> > >>>>>> should be attempted because: >> > >>>>>> >> > >>>>>> 1. "No guts - no glory." >> > >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? >> > >>>>>> < >> https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html >> > >> > >>>>>> 3. If you never change anything, your project won't progress. >> > >>>>>> >> > >>>>>> ---------- >> > >>>>>> While you may break some functionality by updating to 18.04.04 , >> you >> > >>>>>> also risk being affected by known security vulnerabilities >> (which may also >> > >>>>>> break functionality sooner or later). There is a concept of >> > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . >> > >>>>>> >> > >>>>>> Regarding updating to 20.04, it is likely more time consuming >> and may >> > >>>>>> have more breaking changes, and you may not need all the newest >> and >> > >>>>>> shiniest software versions there, and you may wish to only >> update to ubuntu >> > >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu >> 20.04 being >> > >>>>>> unusable or unstable, but I'm quite out of the loop. >> > >>>>>> >> > >>>>>> Good luck! >> > >>>>>> >> > >>>>>> >> > >>>>>> >> > >>>>>>> Thanks, >> > >>>>>>> Uri. >> > >>>>>>> ???? >> > >>>>>>> uri at speedy.net >> > >>>>>>> _______________________________________________ >> > >>>>>>> Linux-il mailing list >> > >>>>>>> Linux-il at cs.huji.ac.il >> > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >> > >>>>>>> >> > >>>>>> >> > >>>>>> >> > >>>>>> -- >> > >>>>>> Shlomi Fish https://www.shlomifish.org/ >> > >>>>>> >> > >>>>>> Buddha has the Chuck Norris nature. >> > >>>>>> >> > >>>>>> Please reply to list if it's a mailing list post - >> > >>>>>> http://shlom.in/reply . >> > >>>>>> >> > >>>>> _______________________________________________ >> > >>>>> Linux-il mailing list >> > >>>>> Linux-il at cs.huji.ac.il >> > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >> > >>>>> >> > >>>> _______________________________________________ >> > >> Linux-il mailing list >> > >> Linux-il at cs.huji.ac.il >> > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >> > >> >> > > >> >> > _______________________________________________ >> > Linux-il mailing list >> > Linux-il at cs.huji.ac.il >> > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >> >> >> -- >> Efraim Flashner ????? ????? >> GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 >> Confidentiality cannot be guaranteed on emails sent or received >> unencrypted >> > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 09:51:13 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 09:51:13 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: <20200611063805.GE963@E5400> Message-ID: # cat /var/log/apache2/error.log [Thu Jun 11 06:25:05.426924 2020] [mpm_prefork:notice] [pid 1154] AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming normal operations [Thu Jun 11 06:25:05.427080 2020] [core:notice] [pid 1154] AH00094: Command line: '/usr/sbin/apache2' [Thu Jun 11 06:27:29.459759 2020] [mpm_prefork:notice] [pid 1154] AH00169: caught SIGTERM, shutting down [Thu Jun 11 06:27:34.334311 2020] [mpm_prefork:notice] [pid 1250] AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming normal operations [Thu Jun 11 06:27:34.334390 2020] [core:notice] [pid 1250] AH00094: Command line: '/usr/sbin/apache2' [Thu Jun 11 08:42:54.263194 2020] [mpm_prefork:notice] [pid 1250] AH00169: caught SIGTERM, shutting down access logs - when apache worked, nothing unusual. (I think caught SIGTERM, shutting down is due to reboot) ???? uri at speedy.net On Thu, Jun 11, 2020 at 9:49 AM Shay Gover wrote: > What do u have in apache logs? > > ?On Thu, Jun 11, 2020 at 9:47 AM ??????? wrote:? > >> # systemctl status apache2.service >> ? apache2.service - The Apache HTTP Server >> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor >> preset: enabled) >> Drop-In: /lib/systemd/system/apache2.service.d >> ??apache2-systemd.conf >> Active: failed (Result: timeout) since Thu 2020-06-11 08:44:35 CEST; >> 2min 1s ago >> Process: 577 ExecStart=/usr/sbin/apachectl start (code=killed, >> signal=TERM) >> >> Jun 11 08:43:03 www.speedypedia.info systemd[1]: Starting The Apache >> HTTP Server... >> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: Start >> operation timed out. Terminating. >> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: Failed >> with result 'timeout'. >> Jun 11 08:44:35 www.speedypedia.info systemd[1]: Failed to start The >> Apache HTTP Server. >> ???? >> uri at speedy.net >> >> >> On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner >> wrote: >> >>> Not sure why apache is only starting some time after you reboot. What >>> does the output of 'systemctl status apache2.service' look like? >>> >>> On Thu, Jun 11, 2020 at 07:31:31AM +0300, ???? wrote: >>> > Hi, >>> > >>> > I estimate it's about 15 to 20 minutes after reboot that I can start >>> apache >>> > successfully. Otherwise, I can't start apache. >>> > >>> > ???? >>> > uri at speedy.net >>> > >>> > >>> > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: >>> > >>> > > Please run: >>> > > apachectl start >>> > > from the command line, and copy the response to this list. >>> > > If there is no error, please copy the relevant lines from the >>> error.log of >>> > > apache2. >>> > > >>> > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: >>> > > >>> > >> Hi, >>> > >> >>> > >> Running the command "sudo apachectl configtest" returns "Syntax OK". >>> > >> >>> > >> Running "sudo systemctl restart apache2" doesn't respond. But a few >>> > >> minutes ago it worked and the website worked. I rebooted again and >>> now >>> > >> again it's not working. The problem is that apache doesn't restart >>> after >>> > >> rebooting. >>> > >> >>> > >> ???? >>> > >> uri at speedy.net >>> > >> >>> > >> >>> > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? >>> > >> >>> > >>> Hi, >>> > >>> >>> > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I >>> ran a >>> > >>> few times the following commands (from root): >>> > >>> >>> > >>> sudo apt autoremove >>> > >>> sudo apt-get update >>> > >>> sudo apt-get upgrade >>> > >>> sudo apt update >>> > >>> sudo apt upgrade >>> > >>> >>> > >>> I have 4 servers and I upgraded all of them and 3 of them are >>> working >>> > >>> properly, however one server apache is not working, I can't >>> restart apache >>> > >>> (with "sudo systemctl restart apache2" - it's not responding) and >>> the >>> > >>> website is not working. How can I fix it now? >>> > >>> >>> > >>> The server didn't respond after reboot once (after 2 reboots) and >>> I had >>> > >>> to shut it down and restart it again. >>> > >>> >>> > >>> Thanks, >>> > >>> Uri >>> > >>> ???? >>> > >>> uri at speedy.net >>> > >>> >>> > >>> >>> > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey < >>> michabailey at gmail.com> >>> > >>> wrote: >>> > >>> >>> > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. >>> > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In >>> fact, >>> > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need >>> to go out >>> > >>>> of your way to get it) until 20.04.1 is out in a few months. >>> > >>>> >>> > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >>> > >>>> understanding is that point releases aren?t new versions of >>> Ubuntu per se. >>> > >>>> At point releases, new isos are spun with up-to-date packages, >>> but it?s >>> > >>>> still the same version. Assuming you make a habit of installing >>> updates >>> > >>>> regularly (which you obviously should be), you will effectively >>> > >>>> automatically be on 18.04.4. >>> > >>>> >>> > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >>> > >>>> >>> > >>>>> Hi, >>> > >>>>> >>> > >>>>> Actually I have a staging server which I can upgrade first to >>> 18.04.4 >>> > >>>>> to see if it works, or if something breaks. But I didn't find it >>> on Google >>> > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) >>> without upgrading >>> > >>>>> it to 20.04? >>> > >>>>> >>> > >>>>> ???? >>> > >>>>> uri at speedy.net >>> > >>>>> >>> > >>>>> >>> > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish >>> wrote: >>> > >>>>> >>> > >>>>>> Hi Uri! >>> > >>>>>> >>> > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? >>> wrote:? >>> > >>>>>> >>> > >>>>>>> Hi, >>> > >>>>>>> >>> > >>>>>>> I'm sorry for posting twice in the same day to the same mailing >>> > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for >>> a few >>> > >>>>>>> production servers (one of them I upgraded a few months ago >>> from 14.04). >>> > >>>>>>> How important it is to upgrade the OS version, or can I keep >>> it like this? >>> > >>>>>>> I'm afraid that things will break up if I upgrade. And if I >>> upgrade, should >>> > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has >>> been recently >>> > >>>>>>> released, it might have bugs which will be fixed later, and I >>> prefer not to >>> > >>>>>>> use the first version of 20.04 but to wait about one year >>> before I use it. >>> > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I >>> upgrade at least to >>> > >>>>>>> 18.04.4? >>> > >>>>>>> >>> > >>>>>>> >>> > >>>>>> I've answered the general question here: >>> > >>>>>> >>> > >>>>>> >>> > >>>>>> >>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>> > >>>>>> >>> > >>>>>> Quoting it: >>> > >>>>>> >>> > >>>>>> Will a change I would like to do break some functionality? >>> > >>>>>> >>> > >>>>>> As the aphorism >>> > >>>>>> < >>> https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 >>> > >>> > >>>>>> goes: The difference between theory and practice is that in >>> theory, >>> > >>>>>> there is no difference between theory and practice, while in >>> practice, >>> > >>>>>> there is.. There is usually a risk, however small, that a change >>> > >>>>>> will break some functionality. With good tooling (such as >>> > >>>>>> https://en.wikipedia.org/wiki/Version_control , >>> > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and >>> > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it >>> should be >>> > >>>>>> relatively easy to revert a change which introduced >>> regressions, and you >>> > >>>>>> should do adequate testing. >>> > >>>>>> >>> > >>>>>> A change may have to be avoided due to being estimated as too >>> time or >>> > >>>>>> money consuming, or as having too little gain. However, >>> promising changes >>> > >>>>>> should be attempted because: >>> > >>>>>> >>> > >>>>>> 1. "No guts - no glory." >>> > >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? >>> > >>>>>> < >>> https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html >>> > >>> > >>>>>> 3. If you never change anything, your project won't progress. >>> > >>>>>> >>> > >>>>>> ---------- >>> > >>>>>> While you may break some functionality by updating to 18.04.04 >>> , you >>> > >>>>>> also risk being affected by known security vulnerabilities >>> (which may also >>> > >>>>>> break functionality sooner or later). There is a concept of >>> > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . >>> > >>>>>> >>> > >>>>>> Regarding updating to 20.04, it is likely more time consuming >>> and may >>> > >>>>>> have more breaking changes, and you may not need all the newest >>> and >>> > >>>>>> shiniest software versions there, and you may wish to only >>> update to ubuntu >>> > >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu >>> 20.04 being >>> > >>>>>> unusable or unstable, but I'm quite out of the loop. >>> > >>>>>> >>> > >>>>>> Good luck! >>> > >>>>>> >>> > >>>>>> >>> > >>>>>> >>> > >>>>>>> Thanks, >>> > >>>>>>> Uri. >>> > >>>>>>> ???? >>> > >>>>>>> uri at speedy.net >>> > >>>>>>> _______________________________________________ >>> > >>>>>>> Linux-il mailing list >>> > >>>>>>> Linux-il at cs.huji.ac.il >>> > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>> > >>>>>>> >>> > >>>>>> >>> > >>>>>> >>> > >>>>>> -- >>> > >>>>>> Shlomi Fish https://www.shlomifish.org/ >>> > >>>>>> >>> > >>>>>> Buddha has the Chuck Norris nature. >>> > >>>>>> >>> > >>>>>> Please reply to list if it's a mailing list post - >>> > >>>>>> http://shlom.in/reply . >>> > >>>>>> >>> > >>>>> _______________________________________________ >>> > >>>>> Linux-il mailing list >>> > >>>>> Linux-il at cs.huji.ac.il >>> > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>> > >>>>> >>> > >>>> _______________________________________________ >>> > >> Linux-il mailing list >>> > >> Linux-il at cs.huji.ac.il >>> > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>> > >> >>> > > >>> >>> > _______________________________________________ >>> > Linux-il mailing list >>> > Linux-il at cs.huji.ac.il >>> > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>> >>> >>> -- >>> Efraim Flashner ????? ????? >>> GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 >>> Confidentiality cannot be guaranteed on emails sent or received >>> unencrypted >>> >> _______________________________________________ >> Linux-il mailing list >> Linux-il at cs.huji.ac.il >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From govershay at gmail.com Thu Jun 11 09:56:01 2020 From: govershay at gmail.com (Shay Gover) Date: Thu, 11 Jun 2020 09:56:01 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: <20200611063805.GE963@E5400> Message-ID: Anything related in journalctl? ?On Thu, Jun 11, 2020 at 9:52 AM ??????? wrote:? > # cat /var/log/apache2/error.log > [Thu Jun 11 06:25:05.426924 2020] [mpm_prefork:notice] [pid 1154] AH00163: > Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming normal > operations > [Thu Jun 11 06:25:05.427080 2020] [core:notice] [pid 1154] AH00094: > Command line: '/usr/sbin/apache2' > [Thu Jun 11 06:27:29.459759 2020] [mpm_prefork:notice] [pid 1154] AH00169: > caught SIGTERM, shutting down > [Thu Jun 11 06:27:34.334311 2020] [mpm_prefork:notice] [pid 1250] AH00163: > Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming normal > operations > [Thu Jun 11 06:27:34.334390 2020] [core:notice] [pid 1250] AH00094: > Command line: '/usr/sbin/apache2' > [Thu Jun 11 08:42:54.263194 2020] [mpm_prefork:notice] [pid 1250] AH00169: > caught SIGTERM, shutting down > > access logs - when apache worked, nothing unusual. > > (I think caught SIGTERM, shutting down is due to reboot) > > ???? > uri at speedy.net > > > On Thu, Jun 11, 2020 at 9:49 AM Shay Gover wrote: > >> What do u have in apache logs? >> >> ?On Thu, Jun 11, 2020 at 9:47 AM ??????? wrote:? >> >>> # systemctl status apache2.service >>> ? apache2.service - The Apache HTTP Server >>> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor >>> preset: enabled) >>> Drop-In: /lib/systemd/system/apache2.service.d >>> ??apache2-systemd.conf >>> Active: failed (Result: timeout) since Thu 2020-06-11 08:44:35 CEST; >>> 2min 1s ago >>> Process: 577 ExecStart=/usr/sbin/apachectl start (code=killed, >>> signal=TERM) >>> >>> Jun 11 08:43:03 www.speedypedia.info systemd[1]: Starting The Apache >>> HTTP Server... >>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: Start >>> operation timed out. Terminating. >>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: >>> Failed with result 'timeout'. >>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: Failed to start The >>> Apache HTTP Server. >>> ???? >>> uri at speedy.net >>> >>> >>> On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner >>> wrote: >>> >>>> Not sure why apache is only starting some time after you reboot. What >>>> does the output of 'systemctl status apache2.service' look like? >>>> >>>> On Thu, Jun 11, 2020 at 07:31:31AM +0300, ???? wrote: >>>> > Hi, >>>> > >>>> > I estimate it's about 15 to 20 minutes after reboot that I can start >>>> apache >>>> > successfully. Otherwise, I can't start apache. >>>> > >>>> > ???? >>>> > uri at speedy.net >>>> > >>>> > >>>> > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: >>>> > >>>> > > Please run: >>>> > > apachectl start >>>> > > from the command line, and copy the response to this list. >>>> > > If there is no error, please copy the relevant lines from the >>>> error.log of >>>> > > apache2. >>>> > > >>>> > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: >>>> > > >>>> > >> Hi, >>>> > >> >>>> > >> Running the command "sudo apachectl configtest" returns "Syntax >>>> OK". >>>> > >> >>>> > >> Running "sudo systemctl restart apache2" doesn't respond. But a few >>>> > >> minutes ago it worked and the website worked. I rebooted again and >>>> now >>>> > >> again it's not working. The problem is that apache doesn't restart >>>> after >>>> > >> rebooting. >>>> > >> >>>> > >> ???? >>>> > >> uri at speedy.net >>>> > >> >>>> > >> >>>> > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? >>>> > >> >>>> > >>> Hi, >>>> > >>> >>>> > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I >>>> ran a >>>> > >>> few times the following commands (from root): >>>> > >>> >>>> > >>> sudo apt autoremove >>>> > >>> sudo apt-get update >>>> > >>> sudo apt-get upgrade >>>> > >>> sudo apt update >>>> > >>> sudo apt upgrade >>>> > >>> >>>> > >>> I have 4 servers and I upgraded all of them and 3 of them are >>>> working >>>> > >>> properly, however one server apache is not working, I can't >>>> restart apache >>>> > >>> (with "sudo systemctl restart apache2" - it's not responding) and >>>> the >>>> > >>> website is not working. How can I fix it now? >>>> > >>> >>>> > >>> The server didn't respond after reboot once (after 2 reboots) and >>>> I had >>>> > >>> to shut it down and restart it again. >>>> > >>> >>>> > >>> Thanks, >>>> > >>> Uri >>>> > >>> ???? >>>> > >>> uri at speedy.net >>>> > >>> >>>> > >>> >>>> > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey < >>>> michabailey at gmail.com> >>>> > >>> wrote: >>>> > >>> >>>> > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to >>>> rush. >>>> > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In >>>> fact, >>>> > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you >>>> need to go out >>>> > >>>> of your way to get it) until 20.04.1 is out in a few months. >>>> > >>>> >>>> > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >>>> > >>>> understanding is that point releases aren?t new versions of >>>> Ubuntu per se. >>>> > >>>> At point releases, new isos are spun with up-to-date packages, >>>> but it?s >>>> > >>>> still the same version. Assuming you make a habit of installing >>>> updates >>>> > >>>> regularly (which you obviously should be), you will effectively >>>> > >>>> automatically be on 18.04.4. >>>> > >>>> >>>> > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >>>> > >>>> >>>> > >>>>> Hi, >>>> > >>>>> >>>> > >>>>> Actually I have a staging server which I can upgrade first to >>>> 18.04.4 >>>> > >>>>> to see if it works, or if something breaks. But I didn't find >>>> it on Google >>>> > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) >>>> without upgrading >>>> > >>>>> it to 20.04? >>>> > >>>>> >>>> > >>>>> ???? >>>> > >>>>> uri at speedy.net >>>> > >>>>> >>>> > >>>>> >>>> > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish >>>> wrote: >>>> > >>>>> >>>> > >>>>>> Hi Uri! >>>> > >>>>>> >>>> > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? >>>> wrote:? >>>> > >>>>>> >>>> > >>>>>>> Hi, >>>> > >>>>>>> >>>> > >>>>>>> I'm sorry for posting twice in the same day to the same >>>> mailing >>>> > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for >>>> a few >>>> > >>>>>>> production servers (one of them I upgraded a few months ago >>>> from 14.04). >>>> > >>>>>>> How important it is to upgrade the OS version, or can I keep >>>> it like this? >>>> > >>>>>>> I'm afraid that things will break up if I upgrade. And if I >>>> upgrade, should >>>> > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has >>>> been recently >>>> > >>>>>>> released, it might have bugs which will be fixed later, and I >>>> prefer not to >>>> > >>>>>>> use the first version of 20.04 but to wait about one year >>>> before I use it. >>>> > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I >>>> upgrade at least to >>>> > >>>>>>> 18.04.4? >>>> > >>>>>>> >>>> > >>>>>>> >>>> > >>>>>> I've answered the general question here: >>>> > >>>>>> >>>> > >>>>>> >>>> > >>>>>> >>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>>> > >>>>>> >>>> > >>>>>> Quoting it: >>>> > >>>>>> >>>> > >>>>>> Will a change I would like to do break some functionality? >>>> > >>>>>> >>>> > >>>>>> As the aphorism >>>> > >>>>>> < >>>> https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 >>>> > >>>> > >>>>>> goes: The difference between theory and practice is that in >>>> theory, >>>> > >>>>>> there is no difference between theory and practice, while in >>>> practice, >>>> > >>>>>> there is.. There is usually a risk, however small, that a >>>> change >>>> > >>>>>> will break some functionality. With good tooling (such as >>>> > >>>>>> https://en.wikipedia.org/wiki/Version_control , >>>> > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and >>>> > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it >>>> should be >>>> > >>>>>> relatively easy to revert a change which introduced >>>> regressions, and you >>>> > >>>>>> should do adequate testing. >>>> > >>>>>> >>>> > >>>>>> A change may have to be avoided due to being estimated as too >>>> time or >>>> > >>>>>> money consuming, or as having too little gain. However, >>>> promising changes >>>> > >>>>>> should be attempted because: >>>> > >>>>>> >>>> > >>>>>> 1. "No guts - no glory." >>>> > >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? >>>> > >>>>>> < >>>> https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html >>>> > >>>> > >>>>>> 3. If you never change anything, your project won't >>>> progress. >>>> > >>>>>> >>>> > >>>>>> ---------- >>>> > >>>>>> While you may break some functionality by updating to 18.04.04 >>>> , you >>>> > >>>>>> also risk being affected by known security vulnerabilities >>>> (which may also >>>> > >>>>>> break functionality sooner or later). There is a concept of >>>> > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . >>>> > >>>>>> >>>> > >>>>>> Regarding updating to 20.04, it is likely more time consuming >>>> and may >>>> > >>>>>> have more breaking changes, and you may not need all the >>>> newest and >>>> > >>>>>> shiniest software versions there, and you may wish to only >>>> update to ubuntu >>>> > >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu >>>> 20.04 being >>>> > >>>>>> unusable or unstable, but I'm quite out of the loop. >>>> > >>>>>> >>>> > >>>>>> Good luck! >>>> > >>>>>> >>>> > >>>>>> >>>> > >>>>>> >>>> > >>>>>>> Thanks, >>>> > >>>>>>> Uri. >>>> > >>>>>>> ???? >>>> > >>>>>>> uri at speedy.net >>>> > >>>>>>> _______________________________________________ >>>> > >>>>>>> Linux-il mailing list >>>> > >>>>>>> Linux-il at cs.huji.ac.il >>>> > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>> > >>>>>>> >>>> > >>>>>> >>>> > >>>>>> >>>> > >>>>>> -- >>>> > >>>>>> Shlomi Fish https://www.shlomifish.org/ >>>> > >>>>>> >>>> > >>>>>> Buddha has the Chuck Norris nature. >>>> > >>>>>> >>>> > >>>>>> Please reply to list if it's a mailing list post - >>>> > >>>>>> http://shlom.in/reply . >>>> > >>>>>> >>>> > >>>>> _______________________________________________ >>>> > >>>>> Linux-il mailing list >>>> > >>>>> Linux-il at cs.huji.ac.il >>>> > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>> > >>>>> >>>> > >>>> _______________________________________________ >>>> > >> Linux-il mailing list >>>> > >> Linux-il at cs.huji.ac.il >>>> > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>> > >> >>>> > > >>>> >>>> > _______________________________________________ >>>> > Linux-il mailing list >>>> > Linux-il at cs.huji.ac.il >>>> > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>> >>>> >>>> -- >>>> Efraim Flashner ????? ????? >>>> GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 >>>> Confidentiality cannot be guaranteed on emails sent or received >>>> unencrypted >>>> >>> _______________________________________________ >>> Linux-il mailing list >>> Linux-il at cs.huji.ac.il >>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 09:56:49 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 09:56:49 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: <20200611063805.GE963@E5400> Message-ID: Now I get this error on https://en.speedypedia.info/ for the first time: Sorry! This site is experiencing technical difficulties. Try waiting a few minutes and reloading. (Cannot access the database) ------------------------------ You can try searching via Google in the meantime. Note that their indexes of our content may be out of date. Speedypedia WWW ???? uri at speedy.net On Thu, Jun 11, 2020 at 9:56 AM Shay Gover wrote: > Anything related in journalctl? > > ?On Thu, Jun 11, 2020 at 9:52 AM ??????? wrote:? > >> # cat /var/log/apache2/error.log >> [Thu Jun 11 06:25:05.426924 2020] [mpm_prefork:notice] [pid 1154] >> AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming >> normal operations >> [Thu Jun 11 06:25:05.427080 2020] [core:notice] [pid 1154] AH00094: >> Command line: '/usr/sbin/apache2' >> [Thu Jun 11 06:27:29.459759 2020] [mpm_prefork:notice] [pid 1154] >> AH00169: caught SIGTERM, shutting down >> [Thu Jun 11 06:27:34.334311 2020] [mpm_prefork:notice] [pid 1250] >> AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming >> normal operations >> [Thu Jun 11 06:27:34.334390 2020] [core:notice] [pid 1250] AH00094: >> Command line: '/usr/sbin/apache2' >> [Thu Jun 11 08:42:54.263194 2020] [mpm_prefork:notice] [pid 1250] >> AH00169: caught SIGTERM, shutting down >> >> access logs - when apache worked, nothing unusual. >> >> (I think caught SIGTERM, shutting down is due to reboot) >> >> ???? >> uri at speedy.net >> >> >> On Thu, Jun 11, 2020 at 9:49 AM Shay Gover wrote: >> >>> What do u have in apache logs? >>> >>> ?On Thu, Jun 11, 2020 at 9:47 AM ??????? wrote:? >>> >>>> # systemctl status apache2.service >>>> ? apache2.service - The Apache HTTP Server >>>> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor >>>> preset: enabled) >>>> Drop-In: /lib/systemd/system/apache2.service.d >>>> ??apache2-systemd.conf >>>> Active: failed (Result: timeout) since Thu 2020-06-11 08:44:35 CEST; >>>> 2min 1s ago >>>> Process: 577 ExecStart=/usr/sbin/apachectl start (code=killed, >>>> signal=TERM) >>>> >>>> Jun 11 08:43:03 www.speedypedia.info systemd[1]: Starting The Apache >>>> HTTP Server... >>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: >>>> Start operation timed out. Terminating. >>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: >>>> Failed with result 'timeout'. >>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: Failed to start The >>>> Apache HTTP Server. >>>> ???? >>>> uri at speedy.net >>>> >>>> >>>> On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner >>>> wrote: >>>> >>>>> Not sure why apache is only starting some time after you reboot. What >>>>> does the output of 'systemctl status apache2.service' look like? >>>>> >>>>> On Thu, Jun 11, 2020 at 07:31:31AM +0300, ???? wrote: >>>>> > Hi, >>>>> > >>>>> > I estimate it's about 15 to 20 minutes after reboot that I can start >>>>> apache >>>>> > successfully. Otherwise, I can't start apache. >>>>> > >>>>> > ???? >>>>> > uri at speedy.net >>>>> > >>>>> > >>>>> > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: >>>>> > >>>>> > > Please run: >>>>> > > apachectl start >>>>> > > from the command line, and copy the response to this list. >>>>> > > If there is no error, please copy the relevant lines from the >>>>> error.log of >>>>> > > apache2. >>>>> > > >>>>> > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: >>>>> > > >>>>> > >> Hi, >>>>> > >> >>>>> > >> Running the command "sudo apachectl configtest" returns "Syntax >>>>> OK". >>>>> > >> >>>>> > >> Running "sudo systemctl restart apache2" doesn't respond. But a >>>>> few >>>>> > >> minutes ago it worked and the website worked. I rebooted again >>>>> and now >>>>> > >> again it's not working. The problem is that apache doesn't >>>>> restart after >>>>> > >> rebooting. >>>>> > >> >>>>> > >> ???? >>>>> > >> uri at speedy.net >>>>> > >> >>>>> > >> >>>>> > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? >>>>> > >> >>>>> > >>> Hi, >>>>> > >>> >>>>> > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and >>>>> I ran a >>>>> > >>> few times the following commands (from root): >>>>> > >>> >>>>> > >>> sudo apt autoremove >>>>> > >>> sudo apt-get update >>>>> > >>> sudo apt-get upgrade >>>>> > >>> sudo apt update >>>>> > >>> sudo apt upgrade >>>>> > >>> >>>>> > >>> I have 4 servers and I upgraded all of them and 3 of them are >>>>> working >>>>> > >>> properly, however one server apache is not working, I can't >>>>> restart apache >>>>> > >>> (with "sudo systemctl restart apache2" - it's not responding) >>>>> and the >>>>> > >>> website is not working. How can I fix it now? >>>>> > >>> >>>>> > >>> The server didn't respond after reboot once (after 2 reboots) >>>>> and I had >>>>> > >>> to shut it down and restart it again. >>>>> > >>> >>>>> > >>> Thanks, >>>>> > >>> Uri >>>>> > >>> ???? >>>>> > >>> uri at speedy.net >>>>> > >>> >>>>> > >>> >>>>> > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey < >>>>> michabailey at gmail.com> >>>>> > >>> wrote: >>>>> > >>> >>>>> > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to >>>>> rush. >>>>> > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. >>>>> In fact, >>>>> > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you >>>>> need to go out >>>>> > >>>> of your way to get it) until 20.04.1 is out in a few months. >>>>> > >>>> >>>>> > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >>>>> > >>>> understanding is that point releases aren?t new versions of >>>>> Ubuntu per se. >>>>> > >>>> At point releases, new isos are spun with up-to-date packages, >>>>> but it?s >>>>> > >>>> still the same version. Assuming you make a habit of installing >>>>> updates >>>>> > >>>> regularly (which you obviously should be), you will effectively >>>>> > >>>> automatically be on 18.04.4. >>>>> > >>>> >>>>> > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >>>>> > >>>> >>>>> > >>>>> Hi, >>>>> > >>>>> >>>>> > >>>>> Actually I have a staging server which I can upgrade first to >>>>> 18.04.4 >>>>> > >>>>> to see if it works, or if something breaks. But I didn't find >>>>> it on Google >>>>> > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) >>>>> without upgrading >>>>> > >>>>> it to 20.04? >>>>> > >>>>> >>>>> > >>>>> ???? >>>>> > >>>>> uri at speedy.net >>>>> > >>>>> >>>>> > >>>>> >>>>> > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish >>>>> wrote: >>>>> > >>>>> >>>>> > >>>>>> Hi Uri! >>>>> > >>>>>> >>>>> > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? >>>>> wrote:? >>>>> > >>>>>> >>>>> > >>>>>>> Hi, >>>>> > >>>>>>> >>>>> > >>>>>>> I'm sorry for posting twice in the same day to the same >>>>> mailing >>>>> > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS >>>>> for a few >>>>> > >>>>>>> production servers (one of them I upgraded a few months ago >>>>> from 14.04). >>>>> > >>>>>>> How important it is to upgrade the OS version, or can I keep >>>>> it like this? >>>>> > >>>>>>> I'm afraid that things will break up if I upgrade. And if I >>>>> upgrade, should >>>>> > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 >>>>> has been recently >>>>> > >>>>>>> released, it might have bugs which will be fixed later, and >>>>> I prefer not to >>>>> > >>>>>>> use the first version of 20.04 but to wait about one year >>>>> before I use it. >>>>> > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I >>>>> upgrade at least to >>>>> > >>>>>>> 18.04.4? >>>>> > >>>>>>> >>>>> > >>>>>>> >>>>> > >>>>>> I've answered the general question here: >>>>> > >>>>>> >>>>> > >>>>>> >>>>> > >>>>>> >>>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>>>> > >>>>>> >>>>> > >>>>>> Quoting it: >>>>> > >>>>>> >>>>> > >>>>>> Will a change I would like to do break some functionality? >>>>> > >>>>>> >>>>> > >>>>>> As the aphorism >>>>> > >>>>>> < >>>>> https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 >>>>> > >>>>> > >>>>>> goes: The difference between theory and practice is that in >>>>> theory, >>>>> > >>>>>> there is no difference between theory and practice, while in >>>>> practice, >>>>> > >>>>>> there is.. There is usually a risk, however small, that a >>>>> change >>>>> > >>>>>> will break some functionality. With good tooling (such as >>>>> > >>>>>> https://en.wikipedia.org/wiki/Version_control , >>>>> > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and >>>>> > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it >>>>> should be >>>>> > >>>>>> relatively easy to revert a change which introduced >>>>> regressions, and you >>>>> > >>>>>> should do adequate testing. >>>>> > >>>>>> >>>>> > >>>>>> A change may have to be avoided due to being estimated as too >>>>> time or >>>>> > >>>>>> money consuming, or as having too little gain. However, >>>>> promising changes >>>>> > >>>>>> should be attempted because: >>>>> > >>>>>> >>>>> > >>>>>> 1. "No guts - no glory." >>>>> > >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? >>>>> > >>>>>> < >>>>> https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html >>>>> > >>>>> > >>>>>> 3. If you never change anything, your project won't >>>>> progress. >>>>> > >>>>>> >>>>> > >>>>>> ---------- >>>>> > >>>>>> While you may break some functionality by updating to >>>>> 18.04.04 , you >>>>> > >>>>>> also risk being affected by known security vulnerabilities >>>>> (which may also >>>>> > >>>>>> break functionality sooner or later). There is a concept of >>>>> > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . >>>>> > >>>>>> >>>>> > >>>>>> Regarding updating to 20.04, it is likely more time consuming >>>>> and may >>>>> > >>>>>> have more breaking changes, and you may not need all the >>>>> newest and >>>>> > >>>>>> shiniest software versions there, and you may wish to only >>>>> update to ubuntu >>>>> > >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu >>>>> 20.04 being >>>>> > >>>>>> unusable or unstable, but I'm quite out of the loop. >>>>> > >>>>>> >>>>> > >>>>>> Good luck! >>>>> > >>>>>> >>>>> > >>>>>> >>>>> > >>>>>> >>>>> > >>>>>>> Thanks, >>>>> > >>>>>>> Uri. >>>>> > >>>>>>> ???? >>>>> > >>>>>>> uri at speedy.net >>>>> > >>>>>>> _______________________________________________ >>>>> > >>>>>>> Linux-il mailing list >>>>> > >>>>>>> Linux-il at cs.huji.ac.il >>>>> > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> > >>>>>>> >>>>> > >>>>>> >>>>> > >>>>>> >>>>> > >>>>>> -- >>>>> > >>>>>> Shlomi Fish https://www.shlomifish.org/ >>>>> > >>>>>> >>>>> > >>>>>> Buddha has the Chuck Norris nature. >>>>> > >>>>>> >>>>> > >>>>>> Please reply to list if it's a mailing list post - >>>>> > >>>>>> http://shlom.in/reply . >>>>> > >>>>>> >>>>> > >>>>> _______________________________________________ >>>>> > >>>>> Linux-il mailing list >>>>> > >>>>> Linux-il at cs.huji.ac.il >>>>> > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> > >>>>> >>>>> > >>>> _______________________________________________ >>>>> > >> Linux-il mailing list >>>>> > >> Linux-il at cs.huji.ac.il >>>>> > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> > >> >>>>> > > >>>>> >>>>> > _______________________________________________ >>>>> > Linux-il mailing list >>>>> > Linux-il at cs.huji.ac.il >>>>> > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> >>>>> >>>>> -- >>>>> Efraim Flashner ????? ????? >>>>> GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 >>>>> Confidentiality cannot be guaranteed on emails sent or received >>>>> unencrypted >>>>> >>>> _______________________________________________ >>>> Linux-il mailing list >>>> Linux-il at cs.huji.ac.il >>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 09:57:37 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 09:57:37 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: <20200611063805.GE963@E5400> Message-ID: How do I use journalctl? ???? uri at speedy.net On Thu, Jun 11, 2020 at 9:56 AM Shay Gover wrote: > Anything related in journalctl? > > ?On Thu, Jun 11, 2020 at 9:52 AM ??????? wrote:? > >> # cat /var/log/apache2/error.log >> [Thu Jun 11 06:25:05.426924 2020] [mpm_prefork:notice] [pid 1154] >> AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming >> normal operations >> [Thu Jun 11 06:25:05.427080 2020] [core:notice] [pid 1154] AH00094: >> Command line: '/usr/sbin/apache2' >> [Thu Jun 11 06:27:29.459759 2020] [mpm_prefork:notice] [pid 1154] >> AH00169: caught SIGTERM, shutting down >> [Thu Jun 11 06:27:34.334311 2020] [mpm_prefork:notice] [pid 1250] >> AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming >> normal operations >> [Thu Jun 11 06:27:34.334390 2020] [core:notice] [pid 1250] AH00094: >> Command line: '/usr/sbin/apache2' >> [Thu Jun 11 08:42:54.263194 2020] [mpm_prefork:notice] [pid 1250] >> AH00169: caught SIGTERM, shutting down >> >> access logs - when apache worked, nothing unusual. >> >> (I think caught SIGTERM, shutting down is due to reboot) >> >> ???? >> uri at speedy.net >> >> >> On Thu, Jun 11, 2020 at 9:49 AM Shay Gover wrote: >> >>> What do u have in apache logs? >>> >>> ?On Thu, Jun 11, 2020 at 9:47 AM ??????? wrote:? >>> >>>> # systemctl status apache2.service >>>> ? apache2.service - The Apache HTTP Server >>>> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor >>>> preset: enabled) >>>> Drop-In: /lib/systemd/system/apache2.service.d >>>> ??apache2-systemd.conf >>>> Active: failed (Result: timeout) since Thu 2020-06-11 08:44:35 CEST; >>>> 2min 1s ago >>>> Process: 577 ExecStart=/usr/sbin/apachectl start (code=killed, >>>> signal=TERM) >>>> >>>> Jun 11 08:43:03 www.speedypedia.info systemd[1]: Starting The Apache >>>> HTTP Server... >>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: >>>> Start operation timed out. Terminating. >>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: >>>> Failed with result 'timeout'. >>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: Failed to start The >>>> Apache HTTP Server. >>>> ???? >>>> uri at speedy.net >>>> >>>> >>>> On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner >>>> wrote: >>>> >>>>> Not sure why apache is only starting some time after you reboot. What >>>>> does the output of 'systemctl status apache2.service' look like? >>>>> >>>>> On Thu, Jun 11, 2020 at 07:31:31AM +0300, ???? wrote: >>>>> > Hi, >>>>> > >>>>> > I estimate it's about 15 to 20 minutes after reboot that I can start >>>>> apache >>>>> > successfully. Otherwise, I can't start apache. >>>>> > >>>>> > ???? >>>>> > uri at speedy.net >>>>> > >>>>> > >>>>> > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: >>>>> > >>>>> > > Please run: >>>>> > > apachectl start >>>>> > > from the command line, and copy the response to this list. >>>>> > > If there is no error, please copy the relevant lines from the >>>>> error.log of >>>>> > > apache2. >>>>> > > >>>>> > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: >>>>> > > >>>>> > >> Hi, >>>>> > >> >>>>> > >> Running the command "sudo apachectl configtest" returns "Syntax >>>>> OK". >>>>> > >> >>>>> > >> Running "sudo systemctl restart apache2" doesn't respond. But a >>>>> few >>>>> > >> minutes ago it worked and the website worked. I rebooted again >>>>> and now >>>>> > >> again it's not working. The problem is that apache doesn't >>>>> restart after >>>>> > >> rebooting. >>>>> > >> >>>>> > >> ???? >>>>> > >> uri at speedy.net >>>>> > >> >>>>> > >> >>>>> > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? >>>>> > >> >>>>> > >>> Hi, >>>>> > >>> >>>>> > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and >>>>> I ran a >>>>> > >>> few times the following commands (from root): >>>>> > >>> >>>>> > >>> sudo apt autoremove >>>>> > >>> sudo apt-get update >>>>> > >>> sudo apt-get upgrade >>>>> > >>> sudo apt update >>>>> > >>> sudo apt upgrade >>>>> > >>> >>>>> > >>> I have 4 servers and I upgraded all of them and 3 of them are >>>>> working >>>>> > >>> properly, however one server apache is not working, I can't >>>>> restart apache >>>>> > >>> (with "sudo systemctl restart apache2" - it's not responding) >>>>> and the >>>>> > >>> website is not working. How can I fix it now? >>>>> > >>> >>>>> > >>> The server didn't respond after reboot once (after 2 reboots) >>>>> and I had >>>>> > >>> to shut it down and restart it again. >>>>> > >>> >>>>> > >>> Thanks, >>>>> > >>> Uri >>>>> > >>> ???? >>>>> > >>> uri at speedy.net >>>>> > >>> >>>>> > >>> >>>>> > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey < >>>>> michabailey at gmail.com> >>>>> > >>> wrote: >>>>> > >>> >>>>> > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to >>>>> rush. >>>>> > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. >>>>> In fact, >>>>> > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you >>>>> need to go out >>>>> > >>>> of your way to get it) until 20.04.1 is out in a few months. >>>>> > >>>> >>>>> > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >>>>> > >>>> understanding is that point releases aren?t new versions of >>>>> Ubuntu per se. >>>>> > >>>> At point releases, new isos are spun with up-to-date packages, >>>>> but it?s >>>>> > >>>> still the same version. Assuming you make a habit of installing >>>>> updates >>>>> > >>>> regularly (which you obviously should be), you will effectively >>>>> > >>>> automatically be on 18.04.4. >>>>> > >>>> >>>>> > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >>>>> > >>>> >>>>> > >>>>> Hi, >>>>> > >>>>> >>>>> > >>>>> Actually I have a staging server which I can upgrade first to >>>>> 18.04.4 >>>>> > >>>>> to see if it works, or if something breaks. But I didn't find >>>>> it on Google >>>>> > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) >>>>> without upgrading >>>>> > >>>>> it to 20.04? >>>>> > >>>>> >>>>> > >>>>> ???? >>>>> > >>>>> uri at speedy.net >>>>> > >>>>> >>>>> > >>>>> >>>>> > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish >>>>> wrote: >>>>> > >>>>> >>>>> > >>>>>> Hi Uri! >>>>> > >>>>>> >>>>> > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? >>>>> wrote:? >>>>> > >>>>>> >>>>> > >>>>>>> Hi, >>>>> > >>>>>>> >>>>> > >>>>>>> I'm sorry for posting twice in the same day to the same >>>>> mailing >>>>> > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS >>>>> for a few >>>>> > >>>>>>> production servers (one of them I upgraded a few months ago >>>>> from 14.04). >>>>> > >>>>>>> How important it is to upgrade the OS version, or can I keep >>>>> it like this? >>>>> > >>>>>>> I'm afraid that things will break up if I upgrade. And if I >>>>> upgrade, should >>>>> > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 >>>>> has been recently >>>>> > >>>>>>> released, it might have bugs which will be fixed later, and >>>>> I prefer not to >>>>> > >>>>>>> use the first version of 20.04 but to wait about one year >>>>> before I use it. >>>>> > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I >>>>> upgrade at least to >>>>> > >>>>>>> 18.04.4? >>>>> > >>>>>>> >>>>> > >>>>>>> >>>>> > >>>>>> I've answered the general question here: >>>>> > >>>>>> >>>>> > >>>>>> >>>>> > >>>>>> >>>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>>>> > >>>>>> >>>>> > >>>>>> Quoting it: >>>>> > >>>>>> >>>>> > >>>>>> Will a change I would like to do break some functionality? >>>>> > >>>>>> >>>>> > >>>>>> As the aphorism >>>>> > >>>>>> < >>>>> https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 >>>>> > >>>>> > >>>>>> goes: The difference between theory and practice is that in >>>>> theory, >>>>> > >>>>>> there is no difference between theory and practice, while in >>>>> practice, >>>>> > >>>>>> there is.. There is usually a risk, however small, that a >>>>> change >>>>> > >>>>>> will break some functionality. With good tooling (such as >>>>> > >>>>>> https://en.wikipedia.org/wiki/Version_control , >>>>> > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and >>>>> > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it >>>>> should be >>>>> > >>>>>> relatively easy to revert a change which introduced >>>>> regressions, and you >>>>> > >>>>>> should do adequate testing. >>>>> > >>>>>> >>>>> > >>>>>> A change may have to be avoided due to being estimated as too >>>>> time or >>>>> > >>>>>> money consuming, or as having too little gain. However, >>>>> promising changes >>>>> > >>>>>> should be attempted because: >>>>> > >>>>>> >>>>> > >>>>>> 1. "No guts - no glory." >>>>> > >>>>>> 2. What does "if it ain't broke, don't fix it" really mean? >>>>> > >>>>>> < >>>>> https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html >>>>> > >>>>> > >>>>>> 3. If you never change anything, your project won't >>>>> progress. >>>>> > >>>>>> >>>>> > >>>>>> ---------- >>>>> > >>>>>> While you may break some functionality by updating to >>>>> 18.04.04 , you >>>>> > >>>>>> also risk being affected by known security vulnerabilities >>>>> (which may also >>>>> > >>>>>> break functionality sooner or later). There is a concept of >>>>> > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . >>>>> > >>>>>> >>>>> > >>>>>> Regarding updating to 20.04, it is likely more time consuming >>>>> and may >>>>> > >>>>>> have more breaking changes, and you may not need all the >>>>> newest and >>>>> > >>>>>> shiniest software versions there, and you may wish to only >>>>> update to ubuntu >>>>> > >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu >>>>> 20.04 being >>>>> > >>>>>> unusable or unstable, but I'm quite out of the loop. >>>>> > >>>>>> >>>>> > >>>>>> Good luck! >>>>> > >>>>>> >>>>> > >>>>>> >>>>> > >>>>>> >>>>> > >>>>>>> Thanks, >>>>> > >>>>>>> Uri. >>>>> > >>>>>>> ???? >>>>> > >>>>>>> uri at speedy.net >>>>> > >>>>>>> _______________________________________________ >>>>> > >>>>>>> Linux-il mailing list >>>>> > >>>>>>> Linux-il at cs.huji.ac.il >>>>> > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> > >>>>>>> >>>>> > >>>>>> >>>>> > >>>>>> >>>>> > >>>>>> -- >>>>> > >>>>>> Shlomi Fish https://www.shlomifish.org/ >>>>> > >>>>>> >>>>> > >>>>>> Buddha has the Chuck Norris nature. >>>>> > >>>>>> >>>>> > >>>>>> Please reply to list if it's a mailing list post - >>>>> > >>>>>> http://shlom.in/reply . >>>>> > >>>>>> >>>>> > >>>>> _______________________________________________ >>>>> > >>>>> Linux-il mailing list >>>>> > >>>>> Linux-il at cs.huji.ac.il >>>>> > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> > >>>>> >>>>> > >>>> _______________________________________________ >>>>> > >> Linux-il mailing list >>>>> > >> Linux-il at cs.huji.ac.il >>>>> > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> > >> >>>>> > > >>>>> >>>>> > _______________________________________________ >>>>> > Linux-il mailing list >>>>> > Linux-il at cs.huji.ac.il >>>>> > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> >>>>> >>>>> -- >>>>> Efraim Flashner ????? ????? >>>>> GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 >>>>> Confidentiality cannot be guaranteed on emails sent or received >>>>> unencrypted >>>>> >>>> _______________________________________________ >>>> Linux-il mailing list >>>> Linux-il at cs.huji.ac.il >>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From govershay at gmail.com Thu Jun 11 10:01:03 2020 From: govershay at gmail.com (Shay Gover) Date: Thu, 11 Jun 2020 10:01:03 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: <20200611063805.GE963@E5400> Message-ID: journalctl -e Send what's relevant around the time u start apache ?On Thu, Jun 11, 2020 at 9:59 AM ??????? wrote:? > How do I use journalctl? > ???? > uri at speedy.net > > > On Thu, Jun 11, 2020 at 9:56 AM Shay Gover wrote: > >> Anything related in journalctl? >> >> ?On Thu, Jun 11, 2020 at 9:52 AM ??????? wrote:? >> >>> # cat /var/log/apache2/error.log >>> [Thu Jun 11 06:25:05.426924 2020] [mpm_prefork:notice] [pid 1154] >>> AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming >>> normal operations >>> [Thu Jun 11 06:25:05.427080 2020] [core:notice] [pid 1154] AH00094: >>> Command line: '/usr/sbin/apache2' >>> [Thu Jun 11 06:27:29.459759 2020] [mpm_prefork:notice] [pid 1154] >>> AH00169: caught SIGTERM, shutting down >>> [Thu Jun 11 06:27:34.334311 2020] [mpm_prefork:notice] [pid 1250] >>> AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming >>> normal operations >>> [Thu Jun 11 06:27:34.334390 2020] [core:notice] [pid 1250] AH00094: >>> Command line: '/usr/sbin/apache2' >>> [Thu Jun 11 08:42:54.263194 2020] [mpm_prefork:notice] [pid 1250] >>> AH00169: caught SIGTERM, shutting down >>> >>> access logs - when apache worked, nothing unusual. >>> >>> (I think caught SIGTERM, shutting down is due to reboot) >>> >>> ???? >>> uri at speedy.net >>> >>> >>> On Thu, Jun 11, 2020 at 9:49 AM Shay Gover wrote: >>> >>>> What do u have in apache logs? >>>> >>>> ?On Thu, Jun 11, 2020 at 9:47 AM ??????? wrote:? >>>> >>>>> # systemctl status apache2.service >>>>> ? apache2.service - The Apache HTTP Server >>>>> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; >>>>> vendor preset: enabled) >>>>> Drop-In: /lib/systemd/system/apache2.service.d >>>>> ??apache2-systemd.conf >>>>> Active: failed (Result: timeout) since Thu 2020-06-11 08:44:35 >>>>> CEST; 2min 1s ago >>>>> Process: 577 ExecStart=/usr/sbin/apachectl start (code=killed, >>>>> signal=TERM) >>>>> >>>>> Jun 11 08:43:03 www.speedypedia.info systemd[1]: Starting The Apache >>>>> HTTP Server... >>>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: >>>>> Start operation timed out. Terminating. >>>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: >>>>> Failed with result 'timeout'. >>>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: Failed to start The >>>>> Apache HTTP Server. >>>>> ???? >>>>> uri at speedy.net >>>>> >>>>> >>>>> On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner >>>>> wrote: >>>>> >>>>>> Not sure why apache is only starting some time after you reboot. What >>>>>> does the output of 'systemctl status apache2.service' look like? >>>>>> >>>>>> On Thu, Jun 11, 2020 at 07:31:31AM +0300, ???? wrote: >>>>>> > Hi, >>>>>> > >>>>>> > I estimate it's about 15 to 20 minutes after reboot that I can >>>>>> start apache >>>>>> > successfully. Otherwise, I can't start apache. >>>>>> > >>>>>> > ???? >>>>>> > uri at speedy.net >>>>>> > >>>>>> > >>>>>> > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: >>>>>> > >>>>>> > > Please run: >>>>>> > > apachectl start >>>>>> > > from the command line, and copy the response to this list. >>>>>> > > If there is no error, please copy the relevant lines from the >>>>>> error.log of >>>>>> > > apache2. >>>>>> > > >>>>>> > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: >>>>>> > > >>>>>> > >> Hi, >>>>>> > >> >>>>>> > >> Running the command "sudo apachectl configtest" returns "Syntax >>>>>> OK". >>>>>> > >> >>>>>> > >> Running "sudo systemctl restart apache2" doesn't respond. But a >>>>>> few >>>>>> > >> minutes ago it worked and the website worked. I rebooted again >>>>>> and now >>>>>> > >> again it's not working. The problem is that apache doesn't >>>>>> restart after >>>>>> > >> rebooting. >>>>>> > >> >>>>>> > >> ???? >>>>>> > >> uri at speedy.net >>>>>> > >> >>>>>> > >> >>>>>> > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? >>>>>> wrote:? >>>>>> > >> >>>>>> > >>> Hi, >>>>>> > >>> >>>>>> > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and >>>>>> I ran a >>>>>> > >>> few times the following commands (from root): >>>>>> > >>> >>>>>> > >>> sudo apt autoremove >>>>>> > >>> sudo apt-get update >>>>>> > >>> sudo apt-get upgrade >>>>>> > >>> sudo apt update >>>>>> > >>> sudo apt upgrade >>>>>> > >>> >>>>>> > >>> I have 4 servers and I upgraded all of them and 3 of them are >>>>>> working >>>>>> > >>> properly, however one server apache is not working, I can't >>>>>> restart apache >>>>>> > >>> (with "sudo systemctl restart apache2" - it's not responding) >>>>>> and the >>>>>> > >>> website is not working. How can I fix it now? >>>>>> > >>> >>>>>> > >>> The server didn't respond after reboot once (after 2 reboots) >>>>>> and I had >>>>>> > >>> to shut it down and restart it again. >>>>>> > >>> >>>>>> > >>> Thanks, >>>>>> > >>> Uri >>>>>> > >>> ???? >>>>>> > >>> uri at speedy.net >>>>>> > >>> >>>>>> > >>> >>>>>> > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey < >>>>>> michabailey at gmail.com> >>>>>> > >>> wrote: >>>>>> > >>> >>>>>> > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to >>>>>> rush. >>>>>> > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. >>>>>> In fact, >>>>>> > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you >>>>>> need to go out >>>>>> > >>>> of your way to get it) until 20.04.1 is out in a few months. >>>>>> > >>>> >>>>>> > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >>>>>> > >>>> understanding is that point releases aren?t new versions of >>>>>> Ubuntu per se. >>>>>> > >>>> At point releases, new isos are spun with up-to-date packages, >>>>>> but it?s >>>>>> > >>>> still the same version. Assuming you make a habit of >>>>>> installing updates >>>>>> > >>>> regularly (which you obviously should be), you will effectively >>>>>> > >>>> automatically be on 18.04.4. >>>>>> > >>>> >>>>>> > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >>>>>> > >>>> >>>>>> > >>>>> Hi, >>>>>> > >>>>> >>>>>> > >>>>> Actually I have a staging server which I can upgrade first to >>>>>> 18.04.4 >>>>>> > >>>>> to see if it works, or if something breaks. But I didn't find >>>>>> it on Google >>>>>> > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) >>>>>> without upgrading >>>>>> > >>>>> it to 20.04? >>>>>> > >>>>> >>>>>> > >>>>> ???? >>>>>> > >>>>> uri at speedy.net >>>>>> > >>>>> >>>>>> > >>>>> >>>>>> > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish < >>>>>> shlomif at gmail.com> wrote: >>>>>> > >>>>> >>>>>> > >>>>>> Hi Uri! >>>>>> > >>>>>> >>>>>> > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? >>>>>> wrote:? >>>>>> > >>>>>> >>>>>> > >>>>>>> Hi, >>>>>> > >>>>>>> >>>>>> > >>>>>>> I'm sorry for posting twice in the same day to the same >>>>>> mailing >>>>>> > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS >>>>>> for a few >>>>>> > >>>>>>> production servers (one of them I upgraded a few months ago >>>>>> from 14.04). >>>>>> > >>>>>>> How important it is to upgrade the OS version, or can I >>>>>> keep it like this? >>>>>> > >>>>>>> I'm afraid that things will break up if I upgrade. And if I >>>>>> upgrade, should >>>>>> > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 >>>>>> has been recently >>>>>> > >>>>>>> released, it might have bugs which will be fixed later, and >>>>>> I prefer not to >>>>>> > >>>>>>> use the first version of 20.04 but to wait about one year >>>>>> before I use it. >>>>>> > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I >>>>>> upgrade at least to >>>>>> > >>>>>>> 18.04.4? >>>>>> > >>>>>>> >>>>>> > >>>>>>> >>>>>> > >>>>>> I've answered the general question here: >>>>>> > >>>>>> >>>>>> > >>>>>> >>>>>> > >>>>>> >>>>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>>>>> > >>>>>> >>>>>> > >>>>>> Quoting it: >>>>>> > >>>>>> >>>>>> > >>>>>> Will a change I would like to do break some functionality? >>>>>> > >>>>>> >>>>>> > >>>>>> As the aphorism >>>>>> > >>>>>> < >>>>>> https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 >>>>>> > >>>>>> > >>>>>> goes: The difference between theory and practice is that in >>>>>> theory, >>>>>> > >>>>>> there is no difference between theory and practice, while in >>>>>> practice, >>>>>> > >>>>>> there is.. There is usually a risk, however small, that a >>>>>> change >>>>>> > >>>>>> will break some functionality. With good tooling (such as >>>>>> > >>>>>> https://en.wikipedia.org/wiki/Version_control , >>>>>> > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and >>>>>> > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it >>>>>> should be >>>>>> > >>>>>> relatively easy to revert a change which introduced >>>>>> regressions, and you >>>>>> > >>>>>> should do adequate testing. >>>>>> > >>>>>> >>>>>> > >>>>>> A change may have to be avoided due to being estimated as >>>>>> too time or >>>>>> > >>>>>> money consuming, or as having too little gain. However, >>>>>> promising changes >>>>>> > >>>>>> should be attempted because: >>>>>> > >>>>>> >>>>>> > >>>>>> 1. "No guts - no glory." >>>>>> > >>>>>> 2. What does "if it ain't broke, don't fix it" really >>>>>> mean? >>>>>> > >>>>>> < >>>>>> https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html >>>>>> > >>>>>> > >>>>>> 3. If you never change anything, your project won't >>>>>> progress. >>>>>> > >>>>>> >>>>>> > >>>>>> ---------- >>>>>> > >>>>>> While you may break some functionality by updating to >>>>>> 18.04.04 , you >>>>>> > >>>>>> also risk being affected by known security vulnerabilities >>>>>> (which may also >>>>>> > >>>>>> break functionality sooner or later). There is a concept of >>>>>> > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . >>>>>> > >>>>>> >>>>>> > >>>>>> Regarding updating to 20.04, it is likely more time >>>>>> consuming and may >>>>>> > >>>>>> have more breaking changes, and you may not need all the >>>>>> newest and >>>>>> > >>>>>> shiniest software versions there, and you may wish to only >>>>>> update to ubuntu >>>>>> > >>>>>> 22.04/etc. I didn't hear of too many horror stories of >>>>>> ubuntu 20.04 being >>>>>> > >>>>>> unusable or unstable, but I'm quite out of the loop. >>>>>> > >>>>>> >>>>>> > >>>>>> Good luck! >>>>>> > >>>>>> >>>>>> > >>>>>> >>>>>> > >>>>>> >>>>>> > >>>>>>> Thanks, >>>>>> > >>>>>>> Uri. >>>>>> > >>>>>>> ???? >>>>>> > >>>>>>> uri at speedy.net >>>>>> > >>>>>>> _______________________________________________ >>>>>> > >>>>>>> Linux-il mailing list >>>>>> > >>>>>>> Linux-il at cs.huji.ac.il >>>>>> > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>> > >>>>>>> >>>>>> > >>>>>> >>>>>> > >>>>>> >>>>>> > >>>>>> -- >>>>>> > >>>>>> Shlomi Fish https://www.shlomifish.org/ >>>>>> > >>>>>> >>>>>> > >>>>>> Buddha has the Chuck Norris nature. >>>>>> > >>>>>> >>>>>> > >>>>>> Please reply to list if it's a mailing list post - >>>>>> > >>>>>> http://shlom.in/reply . >>>>>> > >>>>>> >>>>>> > >>>>> _______________________________________________ >>>>>> > >>>>> Linux-il mailing list >>>>>> > >>>>> Linux-il at cs.huji.ac.il >>>>>> > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>> > >>>>> >>>>>> > >>>> _______________________________________________ >>>>>> > >> Linux-il mailing list >>>>>> > >> Linux-il at cs.huji.ac.il >>>>>> > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>> > >> >>>>>> > > >>>>>> >>>>>> > _______________________________________________ >>>>>> > Linux-il mailing list >>>>>> > Linux-il at cs.huji.ac.il >>>>>> > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>> >>>>>> >>>>>> -- >>>>>> Efraim Flashner ????? ????? >>>>>> GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 >>>>>> Confidentiality cannot be guaranteed on emails sent or received >>>>>> unencrypted >>>>>> >>>>> _______________________________________________ >>>>> Linux-il mailing list >>>>> Linux-il at cs.huji.ac.il >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>> >>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 10:33:48 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 10:33:48 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: <20200611063805.GE963@E5400> Message-ID: Hi, It's a big file and I prefer to send it off-list. If you want to receive it, please let me know (off-list). Uri. ???? uri at speedy.net On Thu, Jun 11, 2020 at 10:01 AM Shay Gover wrote: > journalctl -e > Send what's relevant around the time u start apache > > ?On Thu, Jun 11, 2020 at 9:59 AM ??????? wrote:? > >> How do I use journalctl? >> ???? >> uri at speedy.net >> >> >> On Thu, Jun 11, 2020 at 9:56 AM Shay Gover wrote: >> >>> Anything related in journalctl? >>> >>> ?On Thu, Jun 11, 2020 at 9:52 AM ??????? wrote:? >>> >>>> # cat /var/log/apache2/error.log >>>> [Thu Jun 11 06:25:05.426924 2020] [mpm_prefork:notice] [pid 1154] >>>> AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming >>>> normal operations >>>> [Thu Jun 11 06:25:05.427080 2020] [core:notice] [pid 1154] AH00094: >>>> Command line: '/usr/sbin/apache2' >>>> [Thu Jun 11 06:27:29.459759 2020] [mpm_prefork:notice] [pid 1154] >>>> AH00169: caught SIGTERM, shutting down >>>> [Thu Jun 11 06:27:34.334311 2020] [mpm_prefork:notice] [pid 1250] >>>> AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming >>>> normal operations >>>> [Thu Jun 11 06:27:34.334390 2020] [core:notice] [pid 1250] AH00094: >>>> Command line: '/usr/sbin/apache2' >>>> [Thu Jun 11 08:42:54.263194 2020] [mpm_prefork:notice] [pid 1250] >>>> AH00169: caught SIGTERM, shutting down >>>> >>>> access logs - when apache worked, nothing unusual. >>>> >>>> (I think caught SIGTERM, shutting down is due to reboot) >>>> >>>> ???? >>>> uri at speedy.net >>>> >>>> >>>> On Thu, Jun 11, 2020 at 9:49 AM Shay Gover wrote: >>>> >>>>> What do u have in apache logs? >>>>> >>>>> ?On Thu, Jun 11, 2020 at 9:47 AM ??????? wrote:? >>>>> >>>>>> # systemctl status apache2.service >>>>>> ? apache2.service - The Apache HTTP Server >>>>>> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; >>>>>> vendor preset: enabled) >>>>>> Drop-In: /lib/systemd/system/apache2.service.d >>>>>> ??apache2-systemd.conf >>>>>> Active: failed (Result: timeout) since Thu 2020-06-11 08:44:35 >>>>>> CEST; 2min 1s ago >>>>>> Process: 577 ExecStart=/usr/sbin/apachectl start (code=killed, >>>>>> signal=TERM) >>>>>> >>>>>> Jun 11 08:43:03 www.speedypedia.info systemd[1]: Starting The Apache >>>>>> HTTP Server... >>>>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: >>>>>> Start operation timed out. Terminating. >>>>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: >>>>>> Failed with result 'timeout'. >>>>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: Failed to start The >>>>>> Apache HTTP Server. >>>>>> ???? >>>>>> uri at speedy.net >>>>>> >>>>>> >>>>>> On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner < >>>>>> efraim at flashner.co.il> wrote: >>>>>> >>>>>>> Not sure why apache is only starting some time after you reboot. What >>>>>>> does the output of 'systemctl status apache2.service' look like? >>>>>>> >>>>>>> On Thu, Jun 11, 2020 at 07:31:31AM +0300, ???? wrote: >>>>>>> > Hi, >>>>>>> > >>>>>>> > I estimate it's about 15 to 20 minutes after reboot that I can >>>>>>> start apache >>>>>>> > successfully. Otherwise, I can't start apache. >>>>>>> > >>>>>>> > ???? >>>>>>> > uri at speedy.net >>>>>>> > >>>>>>> > >>>>>>> > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: >>>>>>> > >>>>>>> > > Please run: >>>>>>> > > apachectl start >>>>>>> > > from the command line, and copy the response to this list. >>>>>>> > > If there is no error, please copy the relevant lines from the >>>>>>> error.log of >>>>>>> > > apache2. >>>>>>> > > >>>>>>> > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: >>>>>>> > > >>>>>>> > >> Hi, >>>>>>> > >> >>>>>>> > >> Running the command "sudo apachectl configtest" returns "Syntax >>>>>>> OK". >>>>>>> > >> >>>>>>> > >> Running "sudo systemctl restart apache2" doesn't respond. But a >>>>>>> few >>>>>>> > >> minutes ago it worked and the website worked. I rebooted again >>>>>>> and now >>>>>>> > >> again it's not working. The problem is that apache doesn't >>>>>>> restart after >>>>>>> > >> rebooting. >>>>>>> > >> >>>>>>> > >> ???? >>>>>>> > >> uri at speedy.net >>>>>>> > >> >>>>>>> > >> >>>>>>> > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? >>>>>>> wrote:? >>>>>>> > >> >>>>>>> > >>> Hi, >>>>>>> > >>> >>>>>>> > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 >>>>>>> and I ran a >>>>>>> > >>> few times the following commands (from root): >>>>>>> > >>> >>>>>>> > >>> sudo apt autoremove >>>>>>> > >>> sudo apt-get update >>>>>>> > >>> sudo apt-get upgrade >>>>>>> > >>> sudo apt update >>>>>>> > >>> sudo apt upgrade >>>>>>> > >>> >>>>>>> > >>> I have 4 servers and I upgraded all of them and 3 of them are >>>>>>> working >>>>>>> > >>> properly, however one server apache is not working, I can't >>>>>>> restart apache >>>>>>> > >>> (with "sudo systemctl restart apache2" - it's not responding) >>>>>>> and the >>>>>>> > >>> website is not working. How can I fix it now? >>>>>>> > >>> >>>>>>> > >>> The server didn't respond after reboot once (after 2 reboots) >>>>>>> and I had >>>>>>> > >>> to shut it down and restart it again. >>>>>>> > >>> >>>>>>> > >>> Thanks, >>>>>>> > >>> Uri >>>>>>> > >>> ???? >>>>>>> > >>> uri at speedy.net >>>>>>> > >>> >>>>>>> > >>> >>>>>>> > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey < >>>>>>> michabailey at gmail.com> >>>>>>> > >>> wrote: >>>>>>> > >>> >>>>>>> > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to >>>>>>> rush. >>>>>>> > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. >>>>>>> In fact, >>>>>>> > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you >>>>>>> need to go out >>>>>>> > >>>> of your way to get it) until 20.04.1 is out in a few months. >>>>>>> > >>>> >>>>>>> > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >>>>>>> > >>>> understanding is that point releases aren?t new versions of >>>>>>> Ubuntu per se. >>>>>>> > >>>> At point releases, new isos are spun with up-to-date >>>>>>> packages, but it?s >>>>>>> > >>>> still the same version. Assuming you make a habit of >>>>>>> installing updates >>>>>>> > >>>> regularly (which you obviously should be), you will >>>>>>> effectively >>>>>>> > >>>> automatically be on 18.04.4. >>>>>>> > >>>> >>>>>>> > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >>>>>>> > >>>> >>>>>>> > >>>>> Hi, >>>>>>> > >>>>> >>>>>>> > >>>>> Actually I have a staging server which I can upgrade first >>>>>>> to 18.04.4 >>>>>>> > >>>>> to see if it works, or if something breaks. But I didn't >>>>>>> find it on Google >>>>>>> > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) >>>>>>> without upgrading >>>>>>> > >>>>> it to 20.04? >>>>>>> > >>>>> >>>>>>> > >>>>> ???? >>>>>>> > >>>>> uri at speedy.net >>>>>>> > >>>>> >>>>>>> > >>>>> >>>>>>> > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish < >>>>>>> shlomif at gmail.com> wrote: >>>>>>> > >>>>> >>>>>>> > >>>>>> Hi Uri! >>>>>>> > >>>>>> >>>>>>> > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? >>>>>>> wrote:? >>>>>>> > >>>>>> >>>>>>> > >>>>>>> Hi, >>>>>>> > >>>>>>> >>>>>>> > >>>>>>> I'm sorry for posting twice in the same day to the same >>>>>>> mailing >>>>>>> > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS >>>>>>> for a few >>>>>>> > >>>>>>> production servers (one of them I upgraded a few months >>>>>>> ago from 14.04). >>>>>>> > >>>>>>> How important it is to upgrade the OS version, or can I >>>>>>> keep it like this? >>>>>>> > >>>>>>> I'm afraid that things will break up if I upgrade. And if >>>>>>> I upgrade, should >>>>>>> > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 >>>>>>> has been recently >>>>>>> > >>>>>>> released, it might have bugs which will be fixed later, >>>>>>> and I prefer not to >>>>>>> > >>>>>>> use the first version of 20.04 but to wait about one year >>>>>>> before I use it. >>>>>>> > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I >>>>>>> upgrade at least to >>>>>>> > >>>>>>> 18.04.4? >>>>>>> > >>>>>>> >>>>>>> > >>>>>>> >>>>>>> > >>>>>> I've answered the general question here: >>>>>>> > >>>>>> >>>>>>> > >>>>>> >>>>>>> > >>>>>> >>>>>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>>>>>> > >>>>>> >>>>>>> > >>>>>> Quoting it: >>>>>>> > >>>>>> >>>>>>> > >>>>>> Will a change I would like to do break some functionality? >>>>>>> > >>>>>> >>>>>>> > >>>>>> As the aphorism >>>>>>> > >>>>>> < >>>>>>> https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 >>>>>>> > >>>>>>> > >>>>>> goes: The difference between theory and practice is that in >>>>>>> theory, >>>>>>> > >>>>>> there is no difference between theory and practice, while >>>>>>> in practice, >>>>>>> > >>>>>> there is.. There is usually a risk, however small, that a >>>>>>> change >>>>>>> > >>>>>> will break some functionality. With good tooling (such as >>>>>>> > >>>>>> https://en.wikipedia.org/wiki/Version_control , >>>>>>> > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and >>>>>>> > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it >>>>>>> should be >>>>>>> > >>>>>> relatively easy to revert a change which introduced >>>>>>> regressions, and you >>>>>>> > >>>>>> should do adequate testing. >>>>>>> > >>>>>> >>>>>>> > >>>>>> A change may have to be avoided due to being estimated as >>>>>>> too time or >>>>>>> > >>>>>> money consuming, or as having too little gain. However, >>>>>>> promising changes >>>>>>> > >>>>>> should be attempted because: >>>>>>> > >>>>>> >>>>>>> > >>>>>> 1. "No guts - no glory." >>>>>>> > >>>>>> 2. What does "if it ain't broke, don't fix it" really >>>>>>> mean? >>>>>>> > >>>>>> < >>>>>>> https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html >>>>>>> > >>>>>>> > >>>>>> 3. If you never change anything, your project won't >>>>>>> progress. >>>>>>> > >>>>>> >>>>>>> > >>>>>> ---------- >>>>>>> > >>>>>> While you may break some functionality by updating to >>>>>>> 18.04.04 , you >>>>>>> > >>>>>> also risk being affected by known security vulnerabilities >>>>>>> (which may also >>>>>>> > >>>>>> break functionality sooner or later). There is a concept of >>>>>>> > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . >>>>>>> > >>>>>> >>>>>>> > >>>>>> Regarding updating to 20.04, it is likely more time >>>>>>> consuming and may >>>>>>> > >>>>>> have more breaking changes, and you may not need all the >>>>>>> newest and >>>>>>> > >>>>>> shiniest software versions there, and you may wish to only >>>>>>> update to ubuntu >>>>>>> > >>>>>> 22.04/etc. I didn't hear of too many horror stories of >>>>>>> ubuntu 20.04 being >>>>>>> > >>>>>> unusable or unstable, but I'm quite out of the loop. >>>>>>> > >>>>>> >>>>>>> > >>>>>> Good luck! >>>>>>> > >>>>>> >>>>>>> > >>>>>> >>>>>>> > >>>>>> >>>>>>> > >>>>>>> Thanks, >>>>>>> > >>>>>>> Uri. >>>>>>> > >>>>>>> ???? >>>>>>> > >>>>>>> uri at speedy.net >>>>>>> > >>>>>>> _______________________________________________ >>>>>>> > >>>>>>> Linux-il mailing list >>>>>>> > >>>>>>> Linux-il at cs.huji.ac.il >>>>>>> > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>>> > >>>>>>> >>>>>>> > >>>>>> >>>>>>> > >>>>>> >>>>>>> > >>>>>> -- >>>>>>> > >>>>>> Shlomi Fish https://www.shlomifish.org/ >>>>>>> > >>>>>> >>>>>>> > >>>>>> Buddha has the Chuck Norris nature. >>>>>>> > >>>>>> >>>>>>> > >>>>>> Please reply to list if it's a mailing list post - >>>>>>> > >>>>>> http://shlom.in/reply . >>>>>>> > >>>>>> >>>>>>> > >>>>> _______________________________________________ >>>>>>> > >>>>> Linux-il mailing list >>>>>>> > >>>>> Linux-il at cs.huji.ac.il >>>>>>> > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>>> > >>>>> >>>>>>> > >>>> _______________________________________________ >>>>>>> > >> Linux-il mailing list >>>>>>> > >> Linux-il at cs.huji.ac.il >>>>>>> > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>>> > >> >>>>>>> > > >>>>>>> >>>>>>> > _______________________________________________ >>>>>>> > Linux-il mailing list >>>>>>> > Linux-il at cs.huji.ac.il >>>>>>> > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Efraim Flashner ????? ????? >>>>>>> GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 >>>>>>> Confidentiality cannot be guaranteed on emails sent or received >>>>>>> unencrypted >>>>>>> >>>>>> _______________________________________________ >>>>>> Linux-il mailing list >>>>>> Linux-il at cs.huji.ac.il >>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>> >>>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Thu Jun 11 10:44:18 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 10:44:18 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: <20200611063805.GE963@E5400> Message-ID: Hi, I'm sending this on-list. The relevant lines for apache are: Jun 11 08:44:35 www.speedypedia.info systemd[1]: Failed to start The Apache HTTP Server. Jun 11 08:44:35 www.speedypedia.info systemd[1]: Starting Disk Cache Cleaning Daemon for Apache HTTP Server... Jun 11 08:44:35 www.speedypedia.info systemd[1]: Started Disk Cache Cleaning Daemon for Apache HTTP Server. Jun 11 08:55:40 www.speedypedia.info systemd[1]: Starting The Apache HTTP Server... Jun 11 08:55:40 www.speedypedia.info systemd[1]: Started The Apache HTTP Server. And for mysql: Jun 11 08:53:05 www.speedypedia.info systemd[1]: mysql.service: Start operation timed out. Terminating. Jun 11 09:00:46 www.speedypedia.info systemd[1]: mysql.service: Failed with result 'timeout'. Jun 11 09:00:46 www.speedypedia.info systemd[1]: Failed to start MySQL Community Server. Jun 11 09:00:47 www.speedypedia.info systemd[1]: mysql.service: Service hold-off time over, scheduling restart. Jun 11 09:00:47 www.speedypedia.info systemd[1]: mysql.service: Scheduled restart job, restart counter is at 1. Jun 11 09:00:47 www.speedypedia.info systemd[1]: Stopped MySQL Community Server. Jun 11 09:00:47 www.speedypedia.info systemd[1]: Starting MySQL Community Server... Jun 11 09:00:47 www.speedypedia.info systemd[1]: Started MySQL Community Server. ???? uri at speedy.net On Thu, Jun 11, 2020 at 10:01 AM Shay Gover wrote: > journalctl -e > Send what's relevant around the time u start apache > > ?On Thu, Jun 11, 2020 at 9:59 AM ??????? wrote:? > >> How do I use journalctl? >> ???? >> uri at speedy.net >> >> >> On Thu, Jun 11, 2020 at 9:56 AM Shay Gover wrote: >> >>> Anything related in journalctl? >>> >>> ?On Thu, Jun 11, 2020 at 9:52 AM ??????? wrote:? >>> >>>> # cat /var/log/apache2/error.log >>>> [Thu Jun 11 06:25:05.426924 2020] [mpm_prefork:notice] [pid 1154] >>>> AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming >>>> normal operations >>>> [Thu Jun 11 06:25:05.427080 2020] [core:notice] [pid 1154] AH00094: >>>> Command line: '/usr/sbin/apache2' >>>> [Thu Jun 11 06:27:29.459759 2020] [mpm_prefork:notice] [pid 1154] >>>> AH00169: caught SIGTERM, shutting down >>>> [Thu Jun 11 06:27:34.334311 2020] [mpm_prefork:notice] [pid 1250] >>>> AH00163: Apache/2.4.29 (Ubuntu) OpenSSL/1.1.1g configured -- resuming >>>> normal operations >>>> [Thu Jun 11 06:27:34.334390 2020] [core:notice] [pid 1250] AH00094: >>>> Command line: '/usr/sbin/apache2' >>>> [Thu Jun 11 08:42:54.263194 2020] [mpm_prefork:notice] [pid 1250] >>>> AH00169: caught SIGTERM, shutting down >>>> >>>> access logs - when apache worked, nothing unusual. >>>> >>>> (I think caught SIGTERM, shutting down is due to reboot) >>>> >>>> ???? >>>> uri at speedy.net >>>> >>>> >>>> On Thu, Jun 11, 2020 at 9:49 AM Shay Gover wrote: >>>> >>>>> What do u have in apache logs? >>>>> >>>>> ?On Thu, Jun 11, 2020 at 9:47 AM ??????? wrote:? >>>>> >>>>>> # systemctl status apache2.service >>>>>> ? apache2.service - The Apache HTTP Server >>>>>> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; >>>>>> vendor preset: enabled) >>>>>> Drop-In: /lib/systemd/system/apache2.service.d >>>>>> ??apache2-systemd.conf >>>>>> Active: failed (Result: timeout) since Thu 2020-06-11 08:44:35 >>>>>> CEST; 2min 1s ago >>>>>> Process: 577 ExecStart=/usr/sbin/apachectl start (code=killed, >>>>>> signal=TERM) >>>>>> >>>>>> Jun 11 08:43:03 www.speedypedia.info systemd[1]: Starting The Apache >>>>>> HTTP Server... >>>>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: >>>>>> Start operation timed out. Terminating. >>>>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: apache2.service: >>>>>> Failed with result 'timeout'. >>>>>> Jun 11 08:44:35 www.speedypedia.info systemd[1]: Failed to start The >>>>>> Apache HTTP Server. >>>>>> ???? >>>>>> uri at speedy.net >>>>>> >>>>>> >>>>>> On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner < >>>>>> efraim at flashner.co.il> wrote: >>>>>> >>>>>>> Not sure why apache is only starting some time after you reboot. What >>>>>>> does the output of 'systemctl status apache2.service' look like? >>>>>>> >>>>>>> On Thu, Jun 11, 2020 at 07:31:31AM +0300, ???? wrote: >>>>>>> > Hi, >>>>>>> > >>>>>>> > I estimate it's about 15 to 20 minutes after reboot that I can >>>>>>> start apache >>>>>>> > successfully. Otherwise, I can't start apache. >>>>>>> > >>>>>>> > ???? >>>>>>> > uri at speedy.net >>>>>>> > >>>>>>> > >>>>>>> > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: >>>>>>> > >>>>>>> > > Please run: >>>>>>> > > apachectl start >>>>>>> > > from the command line, and copy the response to this list. >>>>>>> > > If there is no error, please copy the relevant lines from the >>>>>>> error.log of >>>>>>> > > apache2. >>>>>>> > > >>>>>>> > > On Thu, Jun 11, 2020, 7:12 AM ???? wrote: >>>>>>> > > >>>>>>> > >> Hi, >>>>>>> > >> >>>>>>> > >> Running the command "sudo apachectl configtest" returns "Syntax >>>>>>> OK". >>>>>>> > >> >>>>>>> > >> Running "sudo systemctl restart apache2" doesn't respond. But a >>>>>>> few >>>>>>> > >> minutes ago it worked and the website worked. I rebooted again >>>>>>> and now >>>>>>> > >> again it's not working. The problem is that apache doesn't >>>>>>> restart after >>>>>>> > >> rebooting. >>>>>>> > >> >>>>>>> > >> ???? >>>>>>> > >> uri at speedy.net >>>>>>> > >> >>>>>>> > >> >>>>>>> > >> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? >>>>>>> wrote:? >>>>>>> > >> >>>>>>> > >>> Hi, >>>>>>> > >>> >>>>>>> > >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 >>>>>>> and I ran a >>>>>>> > >>> few times the following commands (from root): >>>>>>> > >>> >>>>>>> > >>> sudo apt autoremove >>>>>>> > >>> sudo apt-get update >>>>>>> > >>> sudo apt-get upgrade >>>>>>> > >>> sudo apt update >>>>>>> > >>> sudo apt upgrade >>>>>>> > >>> >>>>>>> > >>> I have 4 servers and I upgraded all of them and 3 of them are >>>>>>> working >>>>>>> > >>> properly, however one server apache is not working, I can't >>>>>>> restart apache >>>>>>> > >>> (with "sudo systemctl restart apache2" - it's not responding) >>>>>>> and the >>>>>>> > >>> website is not working. How can I fix it now? >>>>>>> > >>> >>>>>>> > >>> The server didn't respond after reboot once (after 2 reboots) >>>>>>> and I had >>>>>>> > >>> to shut it down and restart it again. >>>>>>> > >>> >>>>>>> > >>> Thanks, >>>>>>> > >>> Uri >>>>>>> > >>> ???? >>>>>>> > >>> uri at speedy.net >>>>>>> > >>> >>>>>>> > >>> >>>>>>> > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey < >>>>>>> michabailey at gmail.com> >>>>>>> > >>> wrote: >>>>>>> > >>> >>>>>>> > >>>> Regarding the upgrade to Focal (20.04): There?s no reason to >>>>>>> rush. >>>>>>> > >>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. >>>>>>> In fact, >>>>>>> > >>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you >>>>>>> need to go out >>>>>>> > >>>> of your way to get it) until 20.04.1 is out in a few months. >>>>>>> > >>>> >>>>>>> > >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >>>>>>> > >>>> understanding is that point releases aren?t new versions of >>>>>>> Ubuntu per se. >>>>>>> > >>>> At point releases, new isos are spun with up-to-date >>>>>>> packages, but it?s >>>>>>> > >>>> still the same version. Assuming you make a habit of >>>>>>> installing updates >>>>>>> > >>>> regularly (which you obviously should be), you will >>>>>>> effectively >>>>>>> > >>>> automatically be on 18.04.4. >>>>>>> > >>>> >>>>>>> > >>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >>>>>>> > >>>> >>>>>>> > >>>>> Hi, >>>>>>> > >>>>> >>>>>>> > >>>>> Actually I have a staging server which I can upgrade first >>>>>>> to 18.04.4 >>>>>>> > >>>>> to see if it works, or if something breaks. But I didn't >>>>>>> find it on Google >>>>>>> > >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) >>>>>>> without upgrading >>>>>>> > >>>>> it to 20.04? >>>>>>> > >>>>> >>>>>>> > >>>>> ???? >>>>>>> > >>>>> uri at speedy.net >>>>>>> > >>>>> >>>>>>> > >>>>> >>>>>>> > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish < >>>>>>> shlomif at gmail.com> wrote: >>>>>>> > >>>>> >>>>>>> > >>>>>> Hi Uri! >>>>>>> > >>>>>> >>>>>>> > >>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? >>>>>>> wrote:? >>>>>>> > >>>>>> >>>>>>> > >>>>>>> Hi, >>>>>>> > >>>>>>> >>>>>>> > >>>>>>> I'm sorry for posting twice in the same day to the same >>>>>>> mailing >>>>>>> > >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS >>>>>>> for a few >>>>>>> > >>>>>>> production servers (one of them I upgraded a few months >>>>>>> ago from 14.04). >>>>>>> > >>>>>>> How important it is to upgrade the OS version, or can I >>>>>>> keep it like this? >>>>>>> > >>>>>>> I'm afraid that things will break up if I upgrade. And if >>>>>>> I upgrade, should >>>>>>> > >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 >>>>>>> has been recently >>>>>>> > >>>>>>> released, it might have bugs which will be fixed later, >>>>>>> and I prefer not to >>>>>>> > >>>>>>> use the first version of 20.04 but to wait about one year >>>>>>> before I use it. >>>>>>> > >>>>>>> Is there a risk with keeping using 18.04.3? Or should I >>>>>>> upgrade at least to >>>>>>> > >>>>>>> 18.04.4? >>>>>>> > >>>>>>> >>>>>>> > >>>>>>> >>>>>>> > >>>>>> I've answered the general question here: >>>>>>> > >>>>>> >>>>>>> > >>>>>> >>>>>>> > >>>>>> >>>>>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>>>>>> > >>>>>> >>>>>>> > >>>>>> Quoting it: >>>>>>> > >>>>>> >>>>>>> > >>>>>> Will a change I would like to do break some functionality? >>>>>>> > >>>>>> >>>>>>> > >>>>>> As the aphorism >>>>>>> > >>>>>> < >>>>>>> https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988 >>>>>>> > >>>>>>> > >>>>>> goes: The difference between theory and practice is that in >>>>>>> theory, >>>>>>> > >>>>>> there is no difference between theory and practice, while >>>>>>> in practice, >>>>>>> > >>>>>> there is.. There is usually a risk, however small, that a >>>>>>> change >>>>>>> > >>>>>> will break some functionality. With good tooling (such as >>>>>>> > >>>>>> https://en.wikipedia.org/wiki/Version_control , >>>>>>> > >>>>>> https://en.wikipedia.org/wiki/Virtual_machine and >>>>>>> > >>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it >>>>>>> should be >>>>>>> > >>>>>> relatively easy to revert a change which introduced >>>>>>> regressions, and you >>>>>>> > >>>>>> should do adequate testing. >>>>>>> > >>>>>> >>>>>>> > >>>>>> A change may have to be avoided due to being estimated as >>>>>>> too time or >>>>>>> > >>>>>> money consuming, or as having too little gain. However, >>>>>>> promising changes >>>>>>> > >>>>>> should be attempted because: >>>>>>> > >>>>>> >>>>>>> > >>>>>> 1. "No guts - no glory." >>>>>>> > >>>>>> 2. What does "if it ain't broke, don't fix it" really >>>>>>> mean? >>>>>>> > >>>>>> < >>>>>>> https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html >>>>>>> > >>>>>>> > >>>>>> 3. If you never change anything, your project won't >>>>>>> progress. >>>>>>> > >>>>>> >>>>>>> > >>>>>> ---------- >>>>>>> > >>>>>> While you may break some functionality by updating to >>>>>>> 18.04.04 , you >>>>>>> > >>>>>> also risk being affected by known security vulnerabilities >>>>>>> (which may also >>>>>>> > >>>>>> break functionality sooner or later). There is a concept of >>>>>>> > >>>>>> https://en.wikipedia.org/wiki/Technical_debt . >>>>>>> > >>>>>> >>>>>>> > >>>>>> Regarding updating to 20.04, it is likely more time >>>>>>> consuming and may >>>>>>> > >>>>>> have more breaking changes, and you may not need all the >>>>>>> newest and >>>>>>> > >>>>>> shiniest software versions there, and you may wish to only >>>>>>> update to ubuntu >>>>>>> > >>>>>> 22.04/etc. I didn't hear of too many horror stories of >>>>>>> ubuntu 20.04 being >>>>>>> > >>>>>> unusable or unstable, but I'm quite out of the loop. >>>>>>> > >>>>>> >>>>>>> > >>>>>> Good luck! >>>>>>> > >>>>>> >>>>>>> > >>>>>> >>>>>>> > >>>>>> >>>>>>> > >>>>>>> Thanks, >>>>>>> > >>>>>>> Uri. >>>>>>> > >>>>>>> ???? >>>>>>> > >>>>>>> uri at speedy.net >>>>>>> > >>>>>>> _______________________________________________ >>>>>>> > >>>>>>> Linux-il mailing list >>>>>>> > >>>>>>> Linux-il at cs.huji.ac.il >>>>>>> > >>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>>> > >>>>>>> >>>>>>> > >>>>>> >>>>>>> > >>>>>> >>>>>>> > >>>>>> -- >>>>>>> > >>>>>> Shlomi Fish https://www.shlomifish.org/ >>>>>>> > >>>>>> >>>>>>> > >>>>>> Buddha has the Chuck Norris nature. >>>>>>> > >>>>>> >>>>>>> > >>>>>> Please reply to list if it's a mailing list post - >>>>>>> > >>>>>> http://shlom.in/reply . >>>>>>> > >>>>>> >>>>>>> > >>>>> _______________________________________________ >>>>>>> > >>>>> Linux-il mailing list >>>>>>> > >>>>> Linux-il at cs.huji.ac.il >>>>>>> > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>>> > >>>>> >>>>>>> > >>>> _______________________________________________ >>>>>>> > >> Linux-il mailing list >>>>>>> > >> Linux-il at cs.huji.ac.il >>>>>>> > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>>> > >> >>>>>>> > > >>>>>>> >>>>>>> > _______________________________________________ >>>>>>> > Linux-il mailing list >>>>>>> > Linux-il at cs.huji.ac.il >>>>>>> > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Efraim Flashner ????? ????? >>>>>>> GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 >>>>>>> Confidentiality cannot be guaranteed on emails sent or received >>>>>>> unencrypted >>>>>>> >>>>>> _______________________________________________ >>>>>> Linux-il mailing list >>>>>> Linux-il at cs.huji.ac.il >>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>> >>>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From slitt at troubleshooters.com Thu Jun 11 12:45:47 2020 From: slitt at troubleshooters.com (Steve Litt) Date: Thu, 11 Jun 2020 05:45:47 -0400 Subject: Ubuntu - apache is not working In-Reply-To: References: Message-ID: <20200611054547.2f2dddeb@mydesk.domain.cxm> On Thu, 11 Jun 2020 07:27:50 +0300 ???? wrote: > Website is working now. But if I reboot the server again, I expect it > to stop working. After you've rebooted and it's stopped working: View the unit file for apache2. Verify the user and group, and su to that user. Verify any stated current directory, and cd to that directory. Now view the command to run, and perform that command on the command line. View any output, error messages, etc. If it appears to run, test that it's running right by viewing a website farmed out by Apache. If Apache starts OK, at the command line, right after reboot, but doesn't come up at reboot, that points an accusing finger at the systemd unit file. One thing I'd do is prepend: sleep 60; in front of the command in the unit file. If that "solves" the problem, something happens during later reboot that enables it to start. Also, look at the logs created when systemd tries (or doesn't try) to start Apache. HTH, SteveT Steve Litt May 2020 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques From uri at speedy.net Thu Jun 11 16:52:59 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 16:52:59 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: Message-ID: Hi, I have errors when running *sudo apt update*: # sudo apt update Hit:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease Err:4 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic InRelease 403 Forbidden [IP: 91.189.95.83 80] Hit:5 http://mirrors.digitalocean.com/ubuntu bionic InRelease Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease Hit:7 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease Reading package lists... Done E: Failed to fetch http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease 403 Forbidden [IP: 91.189.95.83 80] E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic InRelease' is no longer signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Do you know how to fix this issue? It is worth mentioning that this server used to be Ubuntu 14.04, and now it's 18.04.4. I did upgrade its OS. All the other servers of mine, where I didn't have problems, are originally 18.04. I can, in theory, deploy a new server from scratch, but if I can fix the current server in less effort, I prefer. Even if I deploy a new server, I think I will prefer 18.04 than 20.04, since I'm sure this website runs on 18.04, and I still didn't check 20.04. Currently the website is working, but it takes about 15-20 minutes after reboot that I can start apache and mysql. Otherwise it doesn't work. I want to fix first the *sudo apt update* issue to see if this is the cause to the problem. ???? uri at speedy.net ?On Thu, Jun 11, 2020 at 8:05 AM ??????? wrote:? > I ran the commands again and found out there are errors: > > root at www:~# sudo apt autoremove > Reading package lists... Done > Building dependency tree > Reading state information... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > root at www:~# sudo apt-get update > Hit:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease > Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 > kB] > Err:3 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic > InRelease > 403 Forbidden [IP: 91.189.95.83 80] > Hit:4 http://archive.ubuntu.com/ubuntu bionic InRelease > Hit:5 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease > Hit:6 http://mirrors.digitalocean.com/ubuntu bionic InRelease > Hit:7 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease > Reading package lists... Done > E: Failed to fetch > http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease > 403 Forbidden [IP: 91.189.95.83 80] > E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu > bionic InRelease' is no longer signed. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > root at www:~# sudo apt-get upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > root at www:~# sudo apt update > Hit:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease > Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease > Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease > Err:4 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic > InRelease > 403 Forbidden [IP: 91.189.95.83 80] > Hit:5 http://mirrors.digitalocean.com/ubuntu bionic InRelease > Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease > Hit:7 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease > Reading package lists... Done > E: Failed to fetch > http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease > 403 Forbidden [IP: 91.189.95.83 80] > E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu > bionic InRelease' is no longer signed. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > root at www:~# sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > ???? > uri at speedy.net > > > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor wrote: > >> Please run: >> apachectl start >> from the command line, and copy the response to this list. >> If there is no error, please copy the relevant lines from the error.log >> of apache2. >> >> On Thu, Jun 11, 2020, 7:12 AM ???? wrote: >> >>> Hi, >>> >>> Running the command "sudo apachectl configtest" returns "Syntax OK". >>> >>> Running "sudo systemctl restart apache2" doesn't respond. But a few >>> minutes ago it worked and the website worked. I rebooted again and now >>> again it's not working. The problem is that apache doesn't restart after >>> rebooting. >>> >>> ???? >>> uri at speedy.net >>> >>> >>> ?On Thu, Jun 11, 2020 at 6:29 AM ??????? wrote:? >>> >>>> Hi, >>>> >>>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I ran a >>>> few times the following commands (from root): >>>> >>>> sudo apt autoremove >>>> sudo apt-get update >>>> sudo apt-get upgrade >>>> sudo apt update >>>> sudo apt upgrade >>>> >>>> I have 4 servers and I upgraded all of them and 3 of them are working >>>> properly, however one server apache is not working, I can't restart apache >>>> (with "sudo systemctl restart apache2" - it's not responding) and the >>>> website is not working. How can I fix it now? >>>> >>>> The server didn't respond after reboot once (after 2 reboots) and I had >>>> to shut it down and restart it again. >>>> >>>> Thanks, >>>> Uri >>>> ???? >>>> uri at speedy.net >>>> >>>> >>>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey >>>> wrote: >>>> >>>>> Regarding the upgrade to Focal (20.04): There?s no reason to rush. >>>>> Bionic (18.04) is supported, if I?m not mistaken, until 2023. In fact, >>>>> Bionic (LTS) users aren?t even offered the upgrade (i.e. you need to go out >>>>> of your way to get it) until 20.04.1 is out in a few months. >>>>> >>>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my >>>>> understanding is that point releases aren?t new versions of Ubuntu per se. >>>>> At point releases, new isos are spun with up-to-date packages, but it?s >>>>> still the same version. Assuming you make a habit of installing updates >>>>> regularly (which you obviously should be), you will effectively >>>>> automatically be on 18.04.4. >>>>> >>>>> On Wed, Jun 10, 2020 at 6:44 PM ???? wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Actually I have a staging server which I can upgrade first to 18.04.4 >>>>>> to see if it works, or if something breaks. But I didn't find it on Google >>>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without upgrading >>>>>> it to 20.04? >>>>>> >>>>>> ???? >>>>>> uri at speedy.net >>>>>> >>>>>> >>>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish >>>>>> wrote: >>>>>> >>>>>>> Hi Uri! >>>>>>> >>>>>>> ?On Wed, Jun 10, 2020 at 5:30 PM ??????? wrote:? >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I'm sorry for posting twice in the same day to the same mailing >>>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a few >>>>>>>> production servers (one of them I upgraded a few months ago from 14.04). >>>>>>>> How important it is to upgrade the OS version, or can I keep it like this? >>>>>>>> I'm afraid that things will break up if I upgrade. And if I upgrade, should >>>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently >>>>>>>> released, it might have bugs which will be fixed later, and I prefer not to >>>>>>>> use the first version of 20.04 but to wait about one year before I use it. >>>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade at least to >>>>>>>> 18.04.4? >>>>>>>> >>>>>>>> >>>>>>> I've answered the general question here: >>>>>>> >>>>>>> >>>>>>> https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#will-a-change-i-would-like-to-do-break-some-functionality >>>>>>> >>>>>>> Quoting it: >>>>>>> >>>>>>> Will a change I would like to do break some functionality? >>>>>>> >>>>>>> As the aphorism >>>>>>> >>>>>>> goes: The difference between theory and practice is that in theory, >>>>>>> there is no difference between theory and practice, while in practice, >>>>>>> there is.. There is usually a risk, however small, that a change >>>>>>> will break some functionality. With good tooling (such as >>>>>>> https://en.wikipedia.org/wiki/Version_control , >>>>>>> https://en.wikipedia.org/wiki/Virtual_machine and >>>>>>> https://en.wikipedia.org/wiki/OS-level_virtualisation ) it should >>>>>>> be relatively easy to revert a change which introduced regressions, and you >>>>>>> should do adequate testing. >>>>>>> >>>>>>> A change may have to be avoided due to being estimated as too time >>>>>>> or money consuming, or as having too little gain. However, promising >>>>>>> changes should be attempted because: >>>>>>> >>>>>>> 1. "No guts - no glory." >>>>>>> 2. What does "if it ain't broke, don't fix it" really mean? >>>>>>> >>>>>>> 3. If you never change anything, your project won't progress. >>>>>>> >>>>>>> ---------- >>>>>>> While you may break some functionality by updating to 18.04.04 , you >>>>>>> also risk being affected by known security vulnerabilities (which may also >>>>>>> break functionality sooner or later). There is a concept of >>>>>>> https://en.wikipedia.org/wiki/Technical_debt . >>>>>>> >>>>>>> Regarding updating to 20.04, it is likely more time consuming and >>>>>>> may have more breaking changes, and you may not need all the newest and >>>>>>> shiniest software versions there, and you may wish to only update to ubuntu >>>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being >>>>>>> unusable or unstable, but I'm quite out of the loop. >>>>>>> >>>>>>> Good luck! >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Thanks, >>>>>>>> Uri. >>>>>>>> ???? >>>>>>>> uri at speedy.net >>>>>>>> _______________________________________________ >>>>>>>> Linux-il mailing list >>>>>>>> Linux-il at cs.huji.ac.il >>>>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Shlomi Fish https://www.shlomifish.org/ >>>>>>> >>>>>>> Buddha has the Chuck Norris nature. >>>>>>> >>>>>>> Please reply to list if it's a mailing list post - >>>>>>> http://shlom.in/reply . >>>>>>> >>>>>> _______________________________________________ >>>>>> Linux-il mailing list >>>>>> Linux-il at cs.huji.ac.il >>>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>>>> >>>>> _______________________________________________ >>> Linux-il mailing list >>> Linux-il at cs.huji.ac.il >>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From geoff at QuiteLikely.com Thu Jun 11 17:32:51 2020 From: geoff at QuiteLikely.com (Geoff Shang) Date: Thu, 11 Jun 2020 17:32:51 +0300 (IDT) Subject: Ubuntu - apache is not working In-Reply-To: References: Message-ID: On Thu, 11 Jun 2020, ???? wrote: > Err:4 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic InRelease > 403 Forbidden [IP: 91.189.95.83 80] > E: Failed to fetch > http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease > 403 Forbidden [IP: 91.189.95.83 80] > E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu > bionic InRelease' is no longer signed. > N: Updating from such a repository can't be done securely, and is therefore > disabled by default. > N: See apt-secure(8) manpage for repository creation and user configuration > details. > > Do you know how to fix this issue? Firstly, this is just failing to get an updated list of packages from this repository. The existing version, if there is one, will still be installed, so it shouldn't actually be breaking anything. Having said that, a quick search says that Ubuntu 18.04 ships with Python 3.6.8, so there should be no need to get it from an external repository which appears not to function correctly anymore anyway. The entry for this repository is either in /etc/apt/sources.list or in a file in /etc/apt/sources.list.d. Remove the line or lines which reference it from the file it appears in. If it's in a file in /etc/apt/sources.list.d and there are no other repositories listed, you can delete the file. This will stop the complaints. Note: I've not used Ubuntu in awhile. This is assuming that they are still doing what Debian does. Cheers, Geoff. From uri at speedy.net Thu Jun 11 17:52:56 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Thu, 11 Jun 2020 17:52:56 +0300 Subject: Ubuntu - apache is not working In-Reply-To: References: Message-ID: Hi Geoff, Thanks for your feedback. I was not aware of these settings. I compared my servers' /etc/apt directories now with Beyond Compare, and copied files from the other server to this server and another server where there were differences, and then I ran the following commands again: sudo apt update sudo apt upgrade sudo apt dist-upgrade sudo apt autoremove sudo apt autoclean I checked again now, after rebooting the servers, and this server's apache still doesn't work after rebooting, as you expected. But at least I don't get this apt error messages any more. I'm still looking for the reason why this server's apache and mysql don't restart after a reboot. ???? uri at speedy.net On Thu, Jun 11, 2020 at 5:33 PM Geoff Shang wrote: > On Thu, 11 Jun 2020, ???? wrote: > > > Err:4 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic > InRelease > > 403 Forbidden [IP: 91.189.95.83 80] > > E: Failed to fetch > > > http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease > > 403 Forbidden [IP: 91.189.95.83 80] > > E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu > > bionic InRelease' is no longer signed. > > N: Updating from such a repository can't be done securely, and is > therefore > > disabled by default. > > N: See apt-secure(8) manpage for repository creation and user > configuration > > details. > > > > Do you know how to fix this issue? > > Firstly, this is just failing to get an updated list of packages from this > repository. The existing version, if there is one, will still be > installed, so it shouldn't actually be breaking anything. > > Having said that, a quick search says that Ubuntu 18.04 ships with Python > 3.6.8, so there should be no need to get it from an external repository > which appears not to function correctly anymore anyway. > > The entry for this repository is either in /etc/apt/sources.list or in a > file in /etc/apt/sources.list.d. > > Remove the line or lines which reference it from the file it appears in. > If it's in a file in /etc/apt/sources.list.d and there are no other > repositories listed, you can delete the file. > > This will stop the complaints. > > Note: I've not used Ubuntu in awhile. This is assuming that they are > still doing what Debian does. > > Cheers, > Geoff. > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Fri Jun 12 09:23:49 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Fri, 12 Jun 2020 09:23:49 +0300 Subject: Upgrade Ubuntu Linux kernel Message-ID: Hi, I want to upgrade my Ubuntu Linux kernel from 3.13.0-52-generic to 4.15.0-106-generic. How do I do it? I searched on Google and found a few websites, but it doesn't work - I get error messages: https://linuxhint.com/upgrade-kernel-ubuntu-1804/ # sudo apt-get install ukuu Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package ukuu http://ubuntuhandbook.org/index.php/2018/01/install-linux-kernel-4-15-in-ubuntu-linux-mint/ root at www:/tmp# wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500_4.15.0-041500.201801282230_all.deb URL transformed to HTTPS due to an HSTS policy --2020-06-12 08:19:53-- https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500_4.15.0-041500.201801282230_all.deb Resolving kernel.ubuntu.com (kernel.ubuntu.com)... 91.189.94.216 Connecting to kernel.ubuntu.com (kernel.ubuntu.com)|91.189.94.216|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2020-06-12 08:19:53 ERROR 404: Not Found. Thanks, Uri. ???? uri at speedy.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Fri Jun 12 10:27:49 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Fri, 12 Jun 2020 10:27:49 +0300 Subject: Upgrade Ubuntu Linux kernel In-Reply-To: References: Message-ID: Hi, I followed the steps on this website: http://www.yourownlinux.com/2018/12/how-to-install-linux-kernel-4-15-0.html # cd /tmp # wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500_4.15.0-041500.201802011154_all.deb # wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64.deb # wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-image-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64.deb # sudo dpkg -i linux-headers-4.15.0*.deb linux-image-4.15.0*.deb # sudo reboot And then: # uname -r 3.13.0-52-generic And the kernel version is still 3.13.0. How do I upgrade to 4.15.0? ???? uri at speedy.net ?On Fri, Jun 12, 2020 at 9:23 AM ??????? wrote:? > Hi, > > I want to upgrade my Ubuntu Linux kernel from 3.13.0-52-generic > to 4.15.0-106-generic. How do I do it? I searched on Google and found a few > websites, but it doesn't work - I get error messages: > > https://linuxhint.com/upgrade-kernel-ubuntu-1804/ > > # sudo apt-get install ukuu > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Unable to locate package ukuu > > > http://ubuntuhandbook.org/index.php/2018/01/install-linux-kernel-4-15-in-ubuntu-linux-mint/ > > root at www:/tmp# wget > http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500_4.15.0-041500.201801282230_all.deb > URL transformed to HTTPS due to an HSTS policy > --2020-06-12 08:19:53-- > https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500_4.15.0-041500.201801282230_all.deb > Resolving kernel.ubuntu.com (kernel.ubuntu.com)... 91.189.94.216 > Connecting to kernel.ubuntu.com (kernel.ubuntu.com)|91.189.94.216|:443... > connected. > HTTP request sent, awaiting response... 404 Not Found > 2020-06-12 08:19:53 ERROR 404: Not Found. > > Thanks, > Uri. > > ???? > uri at speedy.net > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Fri Jun 12 11:04:19 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Fri, 12 Jun 2020 11:04:19 +0300 Subject: Upgrade Ubuntu Linux kernel In-Reply-To: References: Message-ID: Hi, It's a cloud server located in Amsterdam, and I can connect only with SSH. ???? uri at speedy.net ?On Fri, Jun 12, 2020 at 10:27 AM ??????? wrote:? > Hi, > > I followed the steps on this website: > > http://www.yourownlinux.com/2018/12/how-to-install-linux-kernel-4-15-0.html > > > # cd /tmp > > # wget > http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500_4.15.0-041500.201802011154_all.deb > > # wget > http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64.deb > > # wget > http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-image-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64.deb > > # sudo dpkg -i linux-headers-4.15.0*.deb linux-image-4.15.0*.deb > > # sudo reboot > > And then: > > # uname -r > 3.13.0-52-generic > > And the kernel version is still 3.13.0. > > How do I upgrade to 4.15.0? > > ???? > uri at speedy.net > > > ?On Fri, Jun 12, 2020 at 9:23 AM ??????? wrote:? > >> Hi, >> >> I want to upgrade my Ubuntu Linux kernel from 3.13.0-52-generic >> to 4.15.0-106-generic. How do I do it? I searched on Google and found a few >> websites, but it doesn't work - I get error messages: >> >> https://linuxhint.com/upgrade-kernel-ubuntu-1804/ >> >> # sudo apt-get install ukuu >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> E: Unable to locate package ukuu >> >> >> http://ubuntuhandbook.org/index.php/2018/01/install-linux-kernel-4-15-in-ubuntu-linux-mint/ >> >> root at www:/tmp# wget >> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500_4.15.0-041500.201801282230_all.deb >> URL transformed to HTTPS due to an HSTS policy >> --2020-06-12 08:19:53-- >> https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500_4.15.0-041500.201801282230_all.deb >> Resolving kernel.ubuntu.com (kernel.ubuntu.com)... 91.189.94.216 >> Connecting to kernel.ubuntu.com (kernel.ubuntu.com)|91.189.94.216|:443... >> connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2020-06-12 08:19:53 ERROR 404: Not Found. >> >> Thanks, >> Uri. >> >> ???? >> uri at speedy.net >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gabor at szabgab.com Sat Jun 13 14:31:04 2020 From: gabor at szabgab.com (Gabor Szabo) Date: Sat, 13 Jun 2020 14:31:04 +0300 Subject: Connecting multiple external screens to Ubuntu Linux Message-ID: Hi, I have a Thinkpad ( https://www.lenovo.com/il/en/laptops/thinkpad/13-series/ThinkPad-13-Windows-2nd-Gen/p/22TP2TX133E ). It has a single HDMI slot but when I run xrandr I get: Screen 0: minimum 320 x 200, current 1920 x 2160, maximum 16384 x 16384 eDP-1 connected 1920x1080+0+1080 (normal left inverted right x axis y axis) 294mm x 165mm ..... HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 287mm .... DP-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) (The .... are just lots of lines of possible configuration). Based on this (and on my lack of understanding) I could connect another monitor to DP-1 and one to HDMI-2, but I don't know where can I plug them in physically? If I understand correctly an HDMI-splitter might work, but the screens connected to that would show the same image. (Mirror configuration.) I would like to have different content on each screen. Any idea? In a more generic question: what do I need in my computer so I can have more than 2 displays showing different(!) content? Do I need a separate graphics card for each display? regards Gabor -------------- next part -------------- An HTML attachment was scrubbed... URL: From geoffreymendelson at gmail.com Sat Jun 13 14:43:50 2020 From: geoffreymendelson at gmail.com (Geoffrey Mendelson) Date: Sat, 13 Jun 2020 14:43:50 +0300 Subject: Connecting multiple external screens to Ubuntu Linux In-Reply-To: References: Message-ID: I answered a similar question by finding this: https://forums.lenovo.com/t5/ThinkPad-X-Series-Laptops/X380-USB-C-Dock-2-external-monitors/td-p/4309124 I hope it at least points you in the right direction. Geoff -- Geoffrey S. Mendelson, N3OWJ/4X1GM/KBUH7245/KBUW5379 Jerusalem, Israel On Jun 13, 2020, 2:31 PM +0300, Gabor Szabo , wrote: > Hi, > > I have a Thinkpad ( https://www.lenovo.com/il/en/laptops/thinkpad/13-series/ThinkPad-13-Windows-2nd-Gen/p/22TP2TX133E ). It has a single HDMI slot but when I run xrandr I get: > > Screen 0: minimum 320 x 200, current 1920 x 2160, maximum 16384 x 16384 > eDP-1 connected 1920x1080+0+1080 (normal left inverted right x axis y axis) 294mm x 165mm > ..... > HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 287mm > .... > DP-1 disconnected (normal left inverted right x axis y axis) > HDMI-2 disconnected (normal left inverted right x axis y axis) > > (The .... are just lots of lines of possible configuration). > > Based on this (and on my lack of understanding) I could connect another monitor to DP-1 > and one to HDMI-2, but I don't know where can I plug them in physically? > > If I understand correctly an HDMI-splitter might work, but the screens connected to that would show the same image. (Mirror configuration.) I would like to have different content on each screen. > > Any idea? > > In a more generic question: what do I need in my computer so I can have more than 2 displays showing different(!) content? Do I need a separate graphics card for each display? > > regards > ??? Gabor > > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il -------------- next part -------------- An HTML attachment was scrubbed... URL: From govershay at gmail.com Sat Jun 13 14:44:41 2020 From: govershay at gmail.com (Shay Gover) Date: Sat, 13 Jun 2020 14:44:41 +0300 Subject: Connecting multiple external screens to Ubuntu Linux In-Reply-To: References: Message-ID: Docking station probably. On Sat, Jun 13, 2020 at 2:31 PM Gabor Szabo wrote: > Hi, > > I have a Thinkpad ( > https://www.lenovo.com/il/en/laptops/thinkpad/13-series/ThinkPad-13-Windows-2nd-Gen/p/22TP2TX133E > ). It has a single HDMI slot but when I run xrandr I get: > > Screen 0: minimum 320 x 200, current 1920 x 2160, maximum 16384 x 16384 > eDP-1 connected 1920x1080+0+1080 (normal left inverted right x axis y > axis) 294mm x 165mm > ..... > HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis > y axis) 510mm x 287mm > .... > DP-1 disconnected (normal left inverted right x axis y axis) > HDMI-2 disconnected (normal left inverted right x axis y axis) > > (The .... are just lots of lines of possible configuration). > > Based on this (and on my lack of understanding) I could connect another > monitor to DP-1 > and one to HDMI-2, but I don't know where can I plug them in physically? > > If I understand correctly an HDMI-splitter might work, but the screens > connected to that would show the same image. (Mirror configuration.) I > would like to have different content on each screen. > > Any idea? > > In a more generic question: what do I need in my computer so I can have > more than 2 displays showing different(!) content? Do I need a separate > graphics card for each display? > > regards > Gabor > > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > -------------- next part -------------- An HTML attachment was scrubbed... URL: From w1 at zak.co.il Sat Jun 13 14:45:22 2020 From: w1 at zak.co.il (Omer Zak) Date: Sat, 13 Jun 2020 14:45:22 +0300 Subject: Connecting multiple external screens to Ubuntu Linux In-Reply-To: References: Message-ID: <84699bb5cfe4132329479aa6ab01f28a627d66a6.camel@zak.co.il> Hello Gabor, I use a Lenovo Ideapad Y700 to which are connected two displays in addition to its native display. You may find the following blog article to be of some use: https://tddpirate.zak.co.il/2019/10/13/displaylink-y700-debianbuster/ (Get DisplayLink to work on Lenovo Y700 after upgrade to Debian Buster) Regards, --- Omer Zak On Sat, 2020-06-13 at 14:31 +0300, Gabor Szabo wrote: > Hi, > > I have a Thinkpad ( > https://www.lenovo.com/il/en/laptops/thinkpad/13-series/ThinkPad-13-Windows-2nd-Gen/p/22TP2TX133E > ). It has a single HDMI slot but when I run xrandr I get: > > Screen 0: minimum 320 x 200, current 1920 x 2160, maximum 16384 x > 16384 > eDP-1 connected 1920x1080+0+1080 (normal left inverted right x axis y > axis) 294mm x 165mm > ..... > HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x > axis y axis) 510mm x 287mm > .... > DP-1 disconnected (normal left inverted right x axis y axis) > HDMI-2 disconnected (normal left inverted right x axis y axis) > > (The .... are just lots of lines of possible configuration). > > Based on this (and on my lack of understanding) I could connect > another monitor to DP-1 > and one to HDMI-2, but I don't know where can I plug them in > physically? > > If I understand correctly an HDMI-splitter might work, but the > screens connected to that would show the same image. (Mirror > configuration.) I would like to have different content on each > screen. > > Any idea? > > In a more generic question: what do I need in my computer so I can > have more than 2 displays showing different(!) content? Do I need a > separate graphics card for each display? -- We will only have peace with the Arabs when they love their children more than they hate us. Golda Meir (Israeli Prime Minister between 1969-1974) My own blog is at https://tddpirate.zak.co.il/ My opinions, as expressed in this E-mail message, are mine alone. They do not represent the official policy of any organization with which I may be affiliated in any way. WARNING TO SPAMMERS: at https://www.zak.co.il/spamwarning.html From uri at speedy.net Sun Jun 14 13:33:49 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Sun, 14 Jun 2020 13:33:49 +0300 Subject: Letsencrypt certbot auto-renew not working Message-ID: Hi, I have 4 servers with Letsencrypt HTTPS certificates which should renew with certbot. They were created with user `ubuntu` with the flags --dns-route53, --dns-digitalocean and --dns-digitalocean-credentials respectively. When I installed certbot, a file /etc/cron.d/certbot was created: SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin 0 */12 * * * root test -x /usr/bin/certbot -a \! -d /run/systemd/system && perl -e 'sleep int(rand(43200))' && certbot -q renew But, I think it runs from root, and the credentials for these flags expect user ubuntu. And I checked, they are not automatically renewed (except one certificate which was created without these flags). How do I configure these certificates to renew automatically? To renew them manually, I can run `sudo certbot renew` from user ubuntu, and then type the password. ???? uri at speedy.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From rabin at rabin.io Sun Jun 14 20:43:47 2020 From: rabin at rabin.io (Rabin Yasharzadehe) Date: Sun, 14 Jun 2020 20:43:47 +0300 Subject: Letsencrypt certbot auto-renew not working In-Reply-To: References: Message-ID: You can move it to the ubuntu user crontab (crontab -e) just remember to remove the "root" from the line. Regards, Rabin ?On Sun, 14 Jun 2020 at 13:36, ??????? wrote:? > Hi, > > I have 4 servers with Letsencrypt HTTPS certificates which should renew > with certbot. They were created with user `ubuntu` with the > flags --dns-route53, --dns-digitalocean and --dns-digitalocean-credentials > respectively. When I installed certbot, a file /etc/cron.d/certbot was > created: > > SHELL=/bin/sh > PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin > > 0 */12 * * * root test -x /usr/bin/certbot -a \! -d /run/systemd/system && > perl -e 'sleep int(rand(43200))' && certbot -q renew > > But, I think it runs from root, and the credentials for these flags expect > user ubuntu. And I checked, they are not automatically renewed (except one > certificate which was created without these flags). How do I configure > these certificates to renew automatically? > > To renew them manually, I can run `sudo certbot renew` from user ubuntu, > and then type the password. > > > ???? > uri at speedy.net > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gabor at szabgab.com Mon Jun 15 09:17:59 2020 From: gabor at szabgab.com (Gabor Szabo) Date: Mon, 15 Jun 2020 09:17:59 +0300 Subject: Connecting multiple external screens to Ubuntu Linux In-Reply-To: References: Message-ID: Thanks for all the replies so far. So if I understand correctly I might buy a docking station similar to this one: Lenovo Powered USB-C Travel Hub - Docking station - USB-C - VGA, HDMI - Worldwide - for ThinkPad L14 Gen 1, P14s Gen 1, https://www.newegg.com/global/il-en/p/0XP-006B-001E1?item=0XP-006B-001E1 that connects to the USB-C of my computer and provides an HDMI and VGA slots so I can connect two screens, one via each slot. Will I be able to also connect a 3rd external screen to my regular HDMI slot in the computer? Will I be able to have 4 different screens? As I understand this computer has a single graphics card. So how can it drive more than one screen? What is the limit? If I buy a desktop computer can a single graphics card drive more than one screen there? Any pointers to some explanations how this graphics card to screens mapping works? Gabor -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Tue Jun 16 16:06:43 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Tue, 16 Jun 2020 16:06:43 +0300 Subject: certbot version conflict Message-ID: Hi, I installed certbot with pip3 on an Ubuntu 18.04 server: # pip3 freeze|grep -i certbot certbot==1.5.0 certbot-apache==1.5.0 certbot-dns-digitalocean==1.5.0 But when running `certbot renew` with crontab, I receive the following error message: 2020-06-16 14:42:01,556:DEBUG:certbot.log:Exiting abnormally: Traceback (most recent call last): File "/usr/bin/certbot", line 11, in load_entry_point('certbot==0.31.0', 'console_scripts', 'certbot')() File "/usr/lib/python3/dist-packages/certbot/main.py", line 1335, in main plugins = plugins_disco.PluginsRegistry.find_all() File "/usr/lib/python3/dist-packages/certbot/plugins/disco.py", line 206, in find_all plugin_ep = PluginEntryPoint(entry_point) File "/usr/lib/python3/dist-packages/certbot/plugins/disco.py", line 52, in __init__ self.plugin_cls = entry_point.load() File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", line 2461, in load self.require(*args, **kwargs) File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", line 2484, in require items = working_set.resolve(reqs, env, installer, extras=self.extras) File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", line 792, in resolve raise VersionConflict(dist, req).with_context(dependent_req) pkg_resources.VersionConflict: (certbot 0.31.0 (/usr/lib/python3/dist-packages), Requirement.parse('certbot>=1.1.0')) 2020-06-16 14:42:01,556:ERROR:certbot.log:An unexpected error occurred: I ran `ls -l /usr/lib/python3/dist-packages|grep certbot` and received the following output: drwxr-xr-x 6 root root 4096 Jun 16 05:36 certbot drwxr-xr-x 2 root root 4096 Jun 16 05:36 certbot-0.31.0.egg-info drwxr-xr-x 5 root root 4096 Jun 16 05:36 certbot_apache drwxr-xr-x 2 root root 4096 Jun 16 05:36 certbot_apache-0.31.0.egg-info drwxr-xr-x 3 root root 4096 Jun 16 05:47 certbot_dns_digitalocean drwxr-xr-x 2 root root 4096 Jun 16 05:47 certbot_dns_digitalocean-0.23.0.egg-info What did I do wrong and how do I fix it? ????, ???? uri at speedy.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Tue Jun 16 18:41:45 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Tue, 16 Jun 2020 18:41:45 +0300 Subject: certbot version conflict In-Reply-To: References: Message-ID: Hi, I removed these directories and reinstalled with pip3. I hope it works now. ???? uri at speedy.net ?On Tue, Jun 16, 2020 at 4:06 PM ??????? wrote:? > Hi, > > I installed certbot with pip3 on an Ubuntu 18.04 server: > > # pip3 freeze|grep -i certbot > certbot==1.5.0 > certbot-apache==1.5.0 > certbot-dns-digitalocean==1.5.0 > > But when running `certbot renew` with crontab, I receive the following > error message: > > 2020-06-16 14:42:01,556:DEBUG:certbot.log:Exiting abnormally: > Traceback (most recent call last): > File "/usr/bin/certbot", line 11, in > load_entry_point('certbot==0.31.0', 'console_scripts', 'certbot')() > File "/usr/lib/python3/dist-packages/certbot/main.py", line 1335, in main > plugins = plugins_disco.PluginsRegistry.find_all() > File "/usr/lib/python3/dist-packages/certbot/plugins/disco.py", line > 206, in find_all > plugin_ep = PluginEntryPoint(entry_point) > File "/usr/lib/python3/dist-packages/certbot/plugins/disco.py", line 52, > in __init__ > self.plugin_cls = entry_point.load() > File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", > line 2461, in load > self.require(*args, **kwargs) > File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", > line 2484, in require > items = working_set.resolve(reqs, env, installer, extras=self.extras) > File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", > line 792, in resolve > raise VersionConflict(dist, req).with_context(dependent_req) > pkg_resources.VersionConflict: (certbot 0.31.0 > (/usr/lib/python3/dist-packages), Requirement.parse('certbot>=1.1.0')) > 2020-06-16 14:42:01,556:ERROR:certbot.log:An unexpected error occurred: > > I ran `ls -l /usr/lib/python3/dist-packages|grep certbot` and received the > following output: > drwxr-xr-x 6 root root 4096 Jun 16 05:36 certbot > drwxr-xr-x 2 root root 4096 Jun 16 05:36 certbot-0.31.0.egg-info > drwxr-xr-x 5 root root 4096 Jun 16 05:36 certbot_apache > drwxr-xr-x 2 root root 4096 Jun 16 05:36 certbot_apache-0.31.0.egg-info > drwxr-xr-x 3 root root 4096 Jun 16 05:47 certbot_dns_digitalocean > drwxr-xr-x 2 root root 4096 Jun 16 05:47 > certbot_dns_digitalocean-0.23.0.egg-info > > What did I do wrong and how do I fix it? > > ????, > ???? > uri at speedy.net > -------------- next part -------------- An HTML attachment was scrubbed... URL: From geoff at QuiteLikely.com Tue Jun 16 22:32:14 2020 From: geoff at QuiteLikely.com (Geoff Shang) Date: Tue, 16 Jun 2020 20:32:14 +0100 (BST) Subject: certbot version conflict In-Reply-To: References: Message-ID: On Tue, 16 Jun 2020, ???? wrote: > raise VersionConflict(dist, req).with_context(dependent_req) > pkg_resources.VersionConflict: (certbot 0.31.0 > (/usr/lib/python3/dist-packages), Requirement.parse('certbot>=1.1.0')) My guess is that you installed Certbot both from the Python Package repository and also from an Ubuntu package repository. You should install a Python package one way or the other, not both. Otherwise you will get problems like this. If you run: dpkg -s python3-certbot or similar (try 'dpkg --get-selections |grep certbot' if you can't find the package). I would recommend removing the Ubuntu package if you are working with a package installed via pip. BTW: randomly deleting directories is generally not a good idea, particularly if you have installed from a package. All packages provide a method to remove it, even programs compiled from source will usually have the ability to "make uninstall". Geoff. From uri at speedy.net Wed Jun 17 05:03:42 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Wed, 17 Jun 2020 05:03:42 +0300 Subject: certbot version conflict In-Reply-To: References: Message-ID: Thank you, I removed them with dpkg. ???? uri at speedy.net On Tue, Jun 16, 2020 at 10:33 PM Geoff Shang wrote: > On Tue, 16 Jun 2020, ???? wrote: > > > raise VersionConflict(dist, req).with_context(dependent_req) > > pkg_resources.VersionConflict: (certbot 0.31.0 > > (/usr/lib/python3/dist-packages), Requirement.parse('certbot>=1.1.0')) > > My guess is that you installed Certbot both from the Python Package > repository and also from an Ubuntu package repository. > > You should install a Python package one way or the other, not both. > Otherwise you will get problems like this. > > If you run: > > dpkg -s python3-certbot > > or similar (try 'dpkg --get-selections |grep certbot' if you can't find > the package). > > I would recommend removing the Ubuntu package if you are working with a > package installed via pip. > > BTW: randomly deleting directories is generally not a good idea, > particularly if you have installed from a package. All packages provide a > method to remove it, even programs compiled from source will usually have > the ability to "make uninstall". > > Geoff. > _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Sun Jun 21 07:37:59 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Sun, 21 Jun 2020 07:37:59 +0300 Subject: Error running shared postrotate script for mysql Message-ID: Hi, I installed a new Ubuntu 18.04 server with mysql, and I receive the following error by email daily: *Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )/etc/cron.daily/logrotate:error: error running shared postrotate script for '/var/log/mysql.log /var/log/mysql/*log 'run-parts: /etc/cron.daily/logrotate exited with return code 1* How can I fix this error? ????, ???? uri at speedy.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From uri at speedy.net Sun Jun 21 08:14:47 2020 From: uri at speedy.net (=?UTF-8?B?15DXldeo15k=?=) Date: Sun, 21 Jun 2020 08:14:47 +0300 Subject: Error running shared postrotate script for mysql In-Reply-To: References: Message-ID: Hi, I think I found the problem according to https://serverfault.com/questions/325171/debian-mysql-error-running-shared-postrotate-script-for-var-log-mysql-log : My password for user debian-sys-maint was not correct. I updated the password with: update user set authentication_string=password("") where user="debian-sys-maint"; ???? uri at speedy.net ?On Sun, Jun 21, 2020 at 7:37 AM ??????? wrote:? > Hi, > > I installed a new Ubuntu 18.04 server with mysql, and I receive the > following error by email daily: > > > > > > > *Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report > /etc/cron.daily )/etc/cron.daily/logrotate:error: error running shared > postrotate script for '/var/log/mysql.log /var/log/mysql/*log 'run-parts: > /etc/cron.daily/logrotate exited with return code 1* > How can I fix this error? > ????, > ???? > uri at speedy.net > -------------- next part -------------- An HTML attachment was scrubbed... URL: