Anything related in journalctl? On Thu, Jun 11, 2020 at 9:52 AM אורי <u...@speedy.net> 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) > > אורי > u...@speedy.net > > > On Thu, Jun 11, 2020 at 9:49 AM Shay Gover <govers...@gmail.com> wrote: > >> What do u have in apache logs? >> >> On Thu, Jun 11, 2020 at 9:47 AM אורי <u...@speedy.net> 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. >>> אורי >>> u...@speedy.net >>> >>> >>> On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner <efr...@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. >>>> > >>>> > אורי >>>> > u...@speedy.net >>>> > >>>> > >>>> > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor <e...@netmask.it> 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 אורי <u...@speedy.net> 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. >>>> > >> >>>> > >> אורי >>>> > >> u...@speedy.net >>>> > >> >>>> > >> >>>> > >> On Thu, Jun 11, 2020 at 6:29 AM אורי <u...@speedy.net> 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 >>>> > >>> אורי >>>> > >>> u...@speedy.net >>>> > >>> >>>> > >>> >>>> > >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey < >>>> michabai...@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 אורי <u...@speedy.net> 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? >>>> > >>>>> >>>> > >>>>> אורי >>>> > >>>>> u...@speedy.net >>>> > >>>>> >>>> > >>>>> >>>> > >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish <shlo...@gmail.com> >>>> wrote: >>>> > >>>>> >>>> > >>>>>> Hi Uri! >>>> > >>>>>> >>>> > >>>>>> On Wed, Jun 10, 2020 at 5:30 PM אורי <u...@speedy.net> >>>> 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. >>>> > >>>>>>> אורי >>>> > >>>>>>> u...@speedy.net >>>> > >>>>>>> _______________________________________________ >>>> > >>>>>>> Linux-il mailing list >>>> > >>>>>>> Linux-il@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@cs.huji.ac.il >>>> > >>>>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>> > >>>>> >>>> > >>>> _______________________________________________ >>>> > >> Linux-il mailing list >>>> > >> Linux-il@cs.huji.ac.il >>>> > >> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>> > >> >>>> > > >>>> >>>> > _______________________________________________ >>>> > Linux-il mailing list >>>> > Linux-il@cs.huji.ac.il >>>> > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>>> >>>> >>>> -- >>>> Efraim Flashner <efr...@flashner.co.il> אפרים פלשנר >>>> 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@cs.huji.ac.il >>> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il >>> >>
_______________________________________________ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
