<div dir="ltr">How do I use journalctl?<br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div style="direction:rtl"><div style="direction:rtl">אורי</div><div style="direction:rtl"><a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a></div></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 11, 2020 at 9:56 AM Shay Gover <<a href="mailto:govershay@gmail.com">govershay@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:georgia,serif;font-size:large;color:rgb(32,18,77)">Anything related in journalctl?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 11, 2020 at 9:52 AM אורי <<a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"># cat /var/log/apache2/error.log<br>[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<br>[Thu Jun 11 06:25:05.427080 2020] [core:notice] [pid 1154] AH00094: Command line: '/usr/sbin/apache2'<br>[Thu Jun 11 06:27:29.459759 2020] [mpm_prefork:notice] [pid 1154] AH00169: caught SIGTERM, shutting down<br>[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<br>[Thu Jun 11 06:27:34.334390 2020] [core:notice] [pid 1250] AH00094: Command line: '/usr/sbin/apache2'<br>[Thu Jun 11 08:42:54.263194 2020] [mpm_prefork:notice] [pid 1250] AH00169: caught SIGTERM, shutting down<div><br></div><div>access logs - when apache worked, nothing unusual.<br></div><div><br></div><div>(I think caught SIGTERM, shutting down is due to reboot)</div><div><br><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div style="direction:rtl"><div style="direction:rtl">אורי</div><div style="direction:rtl"><a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 11, 2020 at 9:49 AM Shay Gover <<a href="mailto:govershay@gmail.com" target="_blank">govershay@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:georgia,serif;font-size:large;color:rgb(32,18,77)">What do u have in apache logs?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 11, 2020 at 9:47 AM אורי <<a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"># systemctl status apache2.service<br>● apache2.service - The Apache HTTP Server<br> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)<br> Drop-In: /lib/systemd/system/apache2.service.d<br> └─apache2-systemd.conf<br> Active: failed (Result: timeout) since Thu 2020-06-11 08:44:35 CEST; 2min 1s ago<br> Process: 577 ExecStart=/usr/sbin/apachectl start (code=killed, signal=TERM)<br><br>Jun 11 08:43:03 <a href="http://www.speedypedia.info" target="_blank">www.speedypedia.info</a> systemd[1]: Starting The Apache HTTP Server...<br>Jun 11 08:44:35 <a href="http://www.speedypedia.info" target="_blank">www.speedypedia.info</a> systemd[1]: apache2.service: Start operation timed out. Terminating.<br>Jun 11 08:44:35 <a href="http://www.speedypedia.info" target="_blank">www.speedypedia.info</a> systemd[1]: apache2.service: Failed with result 'timeout'.<br>Jun 11 08:44:35 <a href="http://www.speedypedia.info" target="_blank">www.speedypedia.info</a> systemd[1]: Failed to start The Apache HTTP Server.<br><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div style="direction:rtl"><div style="direction:rtl">אורי</div><div style="direction:rtl"><a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a></div></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 11, 2020 at 9:38 AM Efraim Flashner <<a href="mailto:efraim@flashner.co.il" target="_blank">efraim@flashner.co.il</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Not sure why apache is only starting some time after you reboot. What<br>
does the output of 'systemctl status apache2.service' look like?<br>
<br>
On Thu, Jun 11, 2020 at 07:31:31AM +0300, אורי wrote:<br>
> Hi,<br>
> <br>
> I estimate it's about 15 to 20 minutes after reboot that I can start apache<br>
> successfully. Otherwise, I can't start apache.<br>
> <br>
> אורי<br>
> <a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a><br>
> <br>
> <br>
> On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor <<a href="mailto:eli@netmask.it" target="_blank">eli@netmask.it</a>> wrote:<br>
> <br>
> > Please run:<br>
> > apachectl start<br>
> > from the command line, and copy the response to this list.<br>
> > If there is no error, please copy the relevant lines from the error.log of<br>
> > apache2.<br>
> ><br>
> > On Thu, Jun 11, 2020, 7:12 AM אורי <<a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a>> wrote:<br>
> ><br>
> >> Hi,<br>
> >><br>
> >> Running the command "sudo apachectl configtest" returns "Syntax OK".<br>
> >><br>
> >> Running "sudo systemctl restart apache2" doesn't respond. But a few<br>
> >> minutes ago it worked and the website worked. I rebooted again and now<br>
> >> again it's not working. The problem is that apache doesn't restart after<br>
> >> rebooting.<br>
> >><br>
> >> אורי<br>
> >> <a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a><br>
> >><br>
> >><br>
> >> On Thu, Jun 11, 2020 at 6:29 AM אורי <<a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a>> wrote:<br>
> >><br>
> >>> Hi,<br>
> >>><br>
> >>> Thanks for your suggestion, I decided to upgrade to 18.04.4 and I ran a<br>
> >>> few times the following commands (from root):<br>
> >>><br>
> >>> sudo apt autoremove<br>
> >>> sudo apt-get update<br>
> >>> sudo apt-get upgrade<br>
> >>> sudo apt update<br>
> >>> sudo apt upgrade<br>
> >>><br>
> >>> I have 4 servers and I upgraded all of them and 3 of them are working<br>
> >>> properly, however one server apache is not working, I can't restart apache<br>
> >>> (with "sudo systemctl restart apache2" - it's not responding) and the<br>
> >>> website is not working. How can I fix it now?<br>
> >>><br>
> >>> The server didn't respond after reboot once (after 2 reboots) and I had<br>
> >>> to shut it down and restart it again.<br>
> >>><br>
> >>> Thanks,<br>
> >>> Uri<br>
> >>> אורי<br>
> >>> <a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a><br>
> >>><br>
> >>><br>
> >>> On Wed, Jun 10, 2020 at 10:29 PM Micha Bailey <<a href="mailto:michabailey@gmail.com" target="_blank">michabailey@gmail.com</a>><br>
> >>> wrote:<br>
> >>><br>
> >>>> Regarding the upgrade to Focal (20.04): There’s no reason to rush.<br>
> >>>> Bionic (18.04) is supported, if I’m not mistaken, until 2023. In fact,<br>
> >>>> Bionic (LTS) users aren’t even offered the upgrade (i.e. you need to go out<br>
> >>>> of your way to get it) until 20.04.1 is out in a few months.<br>
> >>>><br>
> >>>> Regarding the upgrade to 18.04.4, I could be mistaken, but my<br>
> >>>> understanding is that point releases aren’t new versions of Ubuntu per se.<br>
> >>>> At point releases, new isos are spun with up-to-date packages, but it’s<br>
> >>>> still the same version. Assuming you make a habit of installing updates<br>
> >>>> regularly (which you obviously should be), you will effectively<br>
> >>>> automatically be on 18.04.4.<br>
> >>>><br>
> >>>> On Wed, Jun 10, 2020 at 6:44 PM אורי <<a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a>> wrote:<br>
> >>>><br>
> >>>>> Hi,<br>
> >>>>><br>
> >>>>> Actually I have a staging server which I can upgrade first to 18.04.4<br>
> >>>>> to see if it works, or if something breaks. But I didn't find it on Google<br>
> >>>>> - how do I upgrade an OS to Ubuntu 18.04.4 (from 18.04.*) without upgrading<br>
> >>>>> it to 20.04?<br>
> >>>>><br>
> >>>>> אורי<br>
> >>>>> <a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a><br>
> >>>>><br>
> >>>>><br>
> >>>>> On Wed, Jun 10, 2020 at 6:19 PM Shlomi Fish <<a href="mailto:shlomif@gmail.com" target="_blank">shlomif@gmail.com</a>> wrote:<br>
> >>>>><br>
> >>>>>> Hi Uri!<br>
> >>>>>><br>
> >>>>>> On Wed, Jun 10, 2020 at 5:30 PM אורי <<a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a>> wrote:<br>
> >>>>>><br>
> >>>>>>> Hi,<br>
> >>>>>>><br>
> >>>>>>> I'm sorry for posting twice in the same day to the same mailing<br>
> >>>>>>> list. But I have a question: I'm using Ubuntu 18.04.3 LTS for a few<br>
> >>>>>>> production servers (one of them I upgraded a few months ago from 14.04).<br>
> >>>>>>> How important it is to upgrade the OS version, or can I keep it like this?<br>
> >>>>>>> I'm afraid that things will break up if I upgrade. And if I upgrade, should<br>
> >>>>>>> I upgrade to Ubuntu 18.04.4 or 20.04? I think since 20.04 has been recently<br>
> >>>>>>> released, it might have bugs which will be fixed later, and I prefer not to<br>
> >>>>>>> use the first version of 20.04 but to wait about one year before I use it.<br>
> >>>>>>> Is there a risk with keeping using 18.04.3? Or should I upgrade at least to<br>
> >>>>>>> 18.04.4?<br>
> >>>>>>><br>
> >>>>>>><br>
> >>>>>> I've answered the general question here:<br>
> >>>>>><br>
> >>>>>><br>
> >>>>>> <a href="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" rel="noreferrer" target="_blank">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</a><br>
> >>>>>><br>
> >>>>>> Quoting it:<br>
> >>>>>><br>
> >>>>>> Will a change I would like to do break some functionality?<br>
> >>>>>><br>
> >>>>>> As the aphorism<br>
> >>>>>> <<a href="https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988" rel="noreferrer" target="_blank">https://github.com/shlomif/shlomif-email-signature/blob/master/shlomif-sig-quotes.txt#L1988</a>><br>
> >>>>>> goes: The difference between theory and practice is that in theory,<br>
> >>>>>> there is no difference between theory and practice, while in practice,<br>
> >>>>>> there is.. There is usually a risk, however small, that a change<br>
> >>>>>> will break some functionality. With good tooling (such as<br>
> >>>>>> <a href="https://en.wikipedia.org/wiki/Version_control" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Version_control</a> ,<br>
> >>>>>> <a href="https://en.wikipedia.org/wiki/Virtual_machine" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Virtual_machine</a> and<br>
> >>>>>> <a href="https://en.wikipedia.org/wiki/OS-level_virtualisation" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/OS-level_virtualisation</a> ) it should be<br>
> >>>>>> relatively easy to revert a change which introduced regressions, and you<br>
> >>>>>> should do adequate testing.<br>
> >>>>>><br>
> >>>>>> A change may have to be avoided due to being estimated as too time or<br>
> >>>>>> money consuming, or as having too little gain. However, promising changes<br>
> >>>>>> should be attempted because:<br>
> >>>>>><br>
> >>>>>> 1. "No guts - no glory."<br>
> >>>>>> 2. What does "if it ain't broke, don't fix it" really mean?<br>
> >>>>>> <<a href="https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html" rel="noreferrer" target="_blank">https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html</a>><br>
> >>>>>> 3. If you never change anything, your project won't progress.<br>
> >>>>>><br>
> >>>>>> ----------<br>
> >>>>>> While you may break some functionality by updating to 18.04.04 , you<br>
> >>>>>> also risk being affected by known security vulnerabilities (which may also<br>
> >>>>>> break functionality sooner or later). There is a concept of<br>
> >>>>>> <a href="https://en.wikipedia.org/wiki/Technical_debt" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Technical_debt</a> .<br>
> >>>>>><br>
> >>>>>> Regarding updating to 20.04, it is likely more time consuming and may<br>
> >>>>>> have more breaking changes, and you may not need all the newest and<br>
> >>>>>> shiniest software versions there, and you may wish to only update to ubuntu<br>
> >>>>>> 22.04/etc. I didn't hear of too many horror stories of ubuntu 20.04 being<br>
> >>>>>> unusable or unstable, but I'm quite out of the loop.<br>
> >>>>>><br>
> >>>>>> Good luck!<br>
> >>>>>><br>
> >>>>>><br>
> >>>>>><br>
> >>>>>>> Thanks,<br>
> >>>>>>> Uri.<br>
> >>>>>>> אורי<br>
> >>>>>>> <a href="mailto:uri@speedy.net" target="_blank">uri@speedy.net</a><br>
> >>>>>>> _______________________________________________<br>
> >>>>>>> Linux-il mailing list<br>
> >>>>>>> <a href="mailto:Linux-il@cs.huji.ac.il" target="_blank">Linux-il@cs.huji.ac.il</a><br>
> >>>>>>> <a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" rel="noreferrer" target="_blank">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a><br>
> >>>>>>><br>
> >>>>>><br>
> >>>>>><br>
> >>>>>> --<br>
> >>>>>> Shlomi Fish <a href="https://www.shlomifish.org/" rel="noreferrer" target="_blank">https://www.shlomifish.org/</a><br>
> >>>>>><br>
> >>>>>> Buddha has the Chuck Norris nature.<br>
> >>>>>><br>
> >>>>>> Please reply to list if it's a mailing list post -<br>
> >>>>>> <a href="http://shlom.in/reply" rel="noreferrer" target="_blank">http://shlom.in/reply</a> .<br>
> >>>>>><br>
> >>>>> _______________________________________________<br>
> >>>>> Linux-il mailing list<br>
> >>>>> <a href="mailto:Linux-il@cs.huji.ac.il" target="_blank">Linux-il@cs.huji.ac.il</a><br>
> >>>>> <a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" rel="noreferrer" target="_blank">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a><br>
> >>>>><br>
> >>>> _______________________________________________<br>
> >> Linux-il mailing list<br>
> >> <a href="mailto:Linux-il@cs.huji.ac.il" target="_blank">Linux-il@cs.huji.ac.il</a><br>
> >> <a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" rel="noreferrer" target="_blank">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a><br>
> >><br>
> ><br>
<br>
> _______________________________________________<br>
> Linux-il mailing list<br>
> <a href="mailto:Linux-il@cs.huji.ac.il" target="_blank">Linux-il@cs.huji.ac.il</a><br>
> <a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" rel="noreferrer" target="_blank">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a><br>
<br>
<br>
-- <br>
Efraim Flashner <<a href="mailto:efraim@flashner.co.il" target="_blank">efraim@flashner.co.il</a>> אפרים פלשנר<br>
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351<br>
Confidentiality cannot be guaranteed on emails sent or received unencrypted<br>
</blockquote></div>
_______________________________________________<br>
Linux-il mailing list<br>
<a href="mailto:Linux-il@cs.huji.ac.il" target="_blank">Linux-il@cs.huji.ac.il</a><br>
<a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" rel="noreferrer" target="_blank">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a><br>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>