Web hosting providers (OT)

[אורי]

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.
אורי
u...@speedy.net
___
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il

Ubuntu

[אורי]

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.
אורי
u...@speedy.net
___
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il

Re: Ubuntu

[Geoffrey Mendelson]

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.
> אורי
> u...@speedy.net
> ___
> 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

Re: Ubuntu

[אורי]

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.

אורי
u...@speedy.net


On Wed, Jun 10, 2020 at 5:34 PM Geoffrey Mendelson <
geoffreymendel...@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.
> אורי
> u...@speedy.net
> ___
> 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

Re: Ubuntu

[Shlomi Fish]

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.
> אורי
> 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

Re: Ubuntu

[אורי]

Thank you, Shlomi. I like the difference between theory and practice.
אורי
u...@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.
>> אורי
>> 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

Re: Ubuntu

[אורי]

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  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.
>> אורי
>> 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

Re: Ubuntu

[Micha Bailey]

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?
>
> אורי
> u...@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.
>>> אורי
>>> 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

Re: Ubuntu

[אורי]

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  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?
>>
>> אורי
>> u...@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.
 אורי
 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 C

Ubuntu - apache is not working

[אורי]

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 ‫אורי‬‎  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 
> 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?
>>>
>>> אורי
>>> u...@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 v

Re: Ubuntu - apache is not working

[Eli Marmor]

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.
>
> אורי
> u...@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
>> אורי
>> u...@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?

 אורי
 u...@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 b

Re: Ubuntu - apache is not working

[אורי]

# apachectl start
Invoking 'systemctl start apache2'.
Use 'systemctl status apache2' for more info.
אורי
u...@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.
>>
>> אורי
>> u...@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
>>> אורי
>>> u...@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?
>
> אורי
> u...@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 do

Re: Ubuntu - apache is not working

[אורי]

Website is working now. But if I reboot the server again, I expect it to
stop working.
אורי
u...@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.
>>
>> אורי
>> u...@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
>>> אורי
>>> u...@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?
>
> אורי
> u...@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

Re: Ubuntu - apache is not working

[אורי]

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  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.
>>
>> אורי
>> u...@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
>>> אורי
>>> u...@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?
>
> אורי
> u...@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

Re: Ubuntu - apache is not working

[אורי]

I ran the commands again and found out there are errors:

root@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@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@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@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@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.

אורי
u...@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.
>>
>> אורי
>> u...@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
>>> אורי
>>> u...@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 upgrad

Re: Ubuntu

[Tzafrir Cohen]

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@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il

Re: Ubuntu

[אורי]

Hi,

I ran autoremove both before and after the upgrade.
אורי
u...@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@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

Re: Ubuntu - apache is not working

[Efraim Flashner]

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  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.
> >>
> >> אורי
> >> u...@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
> >>> אורי
> >>> u...@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?
> >
> > אורי
> > u...@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_contro

Re: Ubuntu - apache is not working

[Efraim Flashner]

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@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@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@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@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@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.
> 
> אורי
> u...@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.
> >>
> >> אורי
> >> u...@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
> >>> אורי
> >>> u...@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 pe

Re: Ubuntu - apache is not working

[אורי]

How do I remove it?
אורי
u...@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@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@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@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@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@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.
> >
> > אורי
> > u...@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.
> > >>
> > >> אורי
> > >> u...@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
> > >>> אורי
> > >>> u...@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) i

Re: Ubuntu - apache is not working

[אורי]

I think I need Python.
אורי
u...@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@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@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@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@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@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.
> >
> > אורי
> > u...@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.
> > >>
> > >> אורי
> > >> u...@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
> > >>> אורי
> > >>> u...@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

Re: Ubuntu - apache is not working

[אורי]

# 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.
אורי
u...@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.
> >
> > אורי
> > u...@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.
> > >>
> > >> אורי
> > >> u...@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
> > >>> אורי
> > >>> u...@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?
> > >
> > > אורי
> > > u...@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

Re: Ubuntu - apache is not working

[אורי]

Do you want me to run that again after reboot?
אורי
u...@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.
> >
> > אורי
> > u...@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.
> > >>
> > >> אורי
> > >> u...@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
> > >>> אורי
> > >>> u...@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?
> > >
> > > אורי
> > > u...@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 t

Re: Ubuntu - apache is not working

[אורי]

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...
אורי
u...@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.
> >
> > אורי
> > u...@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.
> > >>
> > >> אורי
> > >> u...@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
> > >>> אורי
> > >>> u...@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?
> > >
> > > אורי
> > > u...@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
> > >

Re: Ubuntu - apache is not working

[אורי]

# 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 
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  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.
> > >>
> > >> אורי
> > >> u...@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
> > >>> אורי
> > >>> u...@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?
> > >
> > > אורי
> > > u...@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 versio

Re: Ubuntu - apache is not working

[Shay Gover]

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.
> אורי
> u...@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.
>> >
>> > אורי
>> > u...@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.
>> > >>
>> > >> אורי
>> > >> u...@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
>> > >>> אורי
>> > >>> 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 אורי  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 
>> 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?
>> > >>> 

Re: Ubuntu - apache is not working

[אורי]

# 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  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.
>> אורי
>> u...@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.
>>> >
>>> > אורי
>>> > u...@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.
>>> > >>
>>> > >> אורי
>>> > >> u...@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
>>> > >>> אורי
>>> > >>> 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
>>> > >>>

Re: Ubuntu - apache is not working

[Shay Gover]

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)
>
> אורי
> u...@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.
>>> אורי
>>> u...@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.
 >
 > אורי
 > u...@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.
 > >>
 > >> אורי
 > >> u...@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
 > >>> אורי
 > >>> 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.
>>

Re: Ubuntu - apache is not working

[אורי]

How do I use journalctl?
אורי
u...@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)
>>
>> אורי
>> u...@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.
 אורי
 u...@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.
> >
> > אורי
> > u...@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.
> > >>
> > >> אורי
> > >> u...@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
> > >>> אורי
> > >>> 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
>>