Re: Ubuntu - apache is not working

[אורי]

Hi Geoff,

Thanks for your feedback. I was not aware of these settings. I compared my
servers' /etc/apt directories now with Beyond Compare, and copied files
from the other server to this server and another server where there were
differences, and then I ran the following commands again:

sudo apt update
sudo apt upgrade
sudo apt dist-upgrade
sudo apt autoremove
sudo apt autoclean

I checked again now, after rebooting the servers, and this server's apache
still doesn't work after rebooting, as you expected. But at least I don't
get this apt error messages any more. I'm still looking for the reason why
this server's apache and mysql don't restart after a reboot.

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


On Thu, Jun 11, 2020 at 5:33 PM Geoff Shang  wrote:

> On Thu, 11 Jun 2020, אורי wrote:
>
> > Err:4 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic
> InRelease
> >  403  Forbidden [IP: 91.189.95.83 80]
> > E: Failed to fetch
> >
> http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease
> > 403  Forbidden [IP: 91.189.95.83 80]
> > E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu
> > bionic InRelease' is no longer signed.
> > N: Updating from such a repository can't be done securely, and is
> therefore
> > disabled by default.
> > N: See apt-secure(8) manpage for repository creation and user
> configuration
> > details.
> >
> > Do you know how to fix this issue?
>
> Firstly, this is just failing to get an updated list of packages from this
> repository.  The existing version, if there is one, will still be
> installed, so it shouldn't actually be breaking anything.
>
> Having said that, a quick search says that Ubuntu 18.04 ships with Python
> 3.6.8, so there should be no need to get it from an external repository
> which appears not to function correctly anymore anyway.
>
> The entry for this repository is either in /etc/apt/sources.list or in a
> file in /etc/apt/sources.list.d.
>
> Remove the line or lines which reference it from the file it appears in.
> If it's in a file in /etc/apt/sources.list.d and there are no other
> repositories listed, you can delete the file.
>
> This will stop the complaints.
>
> Note: I've not used Ubuntu in awhile.  This is assuming that they are
> still doing what Debian does.
>
> Cheers,
> Geoff.
> ___
> Linux-il mailing list
> Linux-il@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

[Geoff Shang]

On Thu, 11 Jun 2020, אורי wrote:


Err:4 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic InRelease
 403  Forbidden [IP: 91.189.95.83 80]
E: Failed to fetch
http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease
403  Forbidden [IP: 91.189.95.83 80]
E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu
bionic InRelease' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration
details.

Do you know how to fix this issue?


Firstly, this is just failing to get an updated list of packages from this 
repository.  The existing version, if there is one, will still be 
installed, so it shouldn't actually be breaking anything.


Having said that, a quick search says that Ubuntu 18.04 ships with Python 
3.6.8, so there should be no need to get it from an external repository 
which appears not to function correctly anymore anyway.


The entry for this repository is either in /etc/apt/sources.list or in a 
file in /etc/apt/sources.list.d.


Remove the line or lines which reference it from the file it appears in. 
If it's in a file in /etc/apt/sources.list.d and there are no other 
repositories listed, you can delete the file.


This will stop the complaints.

Note: I've not used Ubuntu in awhile.  This is assuming that they are 
still doing what Debian does.


Cheers,
Geoff.
___
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il

Re: Ubuntu - apache is not working

[אורי]

Hi,

I have errors when running *sudo apt update*:

# sudo apt update
Hit:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease
Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease
Err:4 http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu bionic InRelease
  403  Forbidden [IP: 91.189.95.83 80]
Hit:5 http://mirrors.digitalocean.com/ubuntu bionic InRelease
Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease
Hit:7 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease
Reading package lists... Done
E: Failed to fetch
http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu/dists/bionic/InRelease
 403  Forbidden [IP: 91.189.95.83 80]
E: The repository 'http://ppa.launchpad.net/jonathonf/python-3.6/ubuntu
bionic InRelease' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration
details.

Do you know how to fix this issue?

It is worth mentioning that this server used to be Ubuntu 14.04, and now
it's 18.04.4. I did upgrade its OS. All the other servers of mine, where I
didn't have problems, are originally 18.04.

I can, in theory, deploy a new server from scratch, but if I can fix the
current server in less effort, I prefer. Even if I deploy a new server, I
think I will prefer 18.04 than 20.04, since I'm sure this website runs on
18.04, and I still didn't check 20.04.

Currently the website is working, but it takes about 15-20 minutes after
reboot that I can start apache and mysql. Otherwise it doesn't work. I want
to fix first the *sudo apt update* issue to see if this is the cause to the
problem.


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


‪On Thu, Jun 11, 2020 at 8:05 AM ‫אורי‬‎  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" 

Re: Ubuntu - apache is not working

[Steve Litt]

On Thu, 11 Jun 2020 07:27:50 +0300
אורי  wrote:

> Website is working now. But if I reboot the server again, I expect it
> to stop working.

After you've rebooted and it's stopped working:

View the unit file for apache2. Verify the user and group, and su to
that user.  Verify any stated current directory, and cd to that
directory. Now view the command to run, and perform that command on the
command line. View any output, error messages, etc. If it appears to
run, test that it's running right by viewing a website farmed out by
Apache.

If Apache starts OK, at the command line, right after reboot, but
doesn't come up at reboot, that points an accusing finger at the
systemd unit file. One thing I'd do is prepend:

sleep 60; 

in front of the command in the unit file. If that "solves" the problem,
something happens during later reboot that enables it to start. Also,
look at the logs created when systemd tries (or doesn't try) to start
Apache.

HTH,

SteveT

Steve Litt 
May 2020 featured book: Troubleshooting Techniques
 of the Successful Technologist
http://www.troubleshooters.com/techniques

___
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

[אורי]

Hi,

I'm sending this on-list.

The relevant lines for apache are:

Jun 11 08:44:35 www.speedypedia.info systemd[1]: Failed to start The Apache
HTTP Server.
Jun 11 08:44:35 www.speedypedia.info systemd[1]: Starting Disk Cache
Cleaning Daemon for Apache HTTP Server...
Jun 11 08:44:35 www.speedypedia.info systemd[1]: Started Disk Cache
Cleaning Daemon for Apache HTTP Server.
Jun 11 08:55:40 www.speedypedia.info systemd[1]: Starting The Apache HTTP
Server...
Jun 11 08:55:40 www.speedypedia.info systemd[1]: Started The Apache HTTP
Server.

And for mysql:

Jun 11 08:53:05 www.speedypedia.info systemd[1]: mysql.service: Start
operation timed out. Terminating.
Jun 11 09:00:46 www.speedypedia.info systemd[1]: mysql.service: Failed with
result 'timeout'.
Jun 11 09:00:46 www.speedypedia.info systemd[1]: Failed to start MySQL
Community Server.
Jun 11 09:00:47 www.speedypedia.info systemd[1]: mysql.service: Service
hold-off time over, scheduling restart.
Jun 11 09:00:47 www.speedypedia.info systemd[1]: mysql.service: Scheduled
restart job, restart counter is at 1.
Jun 11 09:00:47 www.speedypedia.info systemd[1]: Stopped MySQL Community
Server.
Jun 11 09:00:47 www.speedypedia.info systemd[1]: Starting MySQL Community
Server...
Jun 11 09:00:47 www.speedypedia.info systemd[1]: Started MySQL Community
Server.

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


On Thu, Jun 11, 2020 at 10:01 AM Shay Gover  wrote:

> journalctl -e
> Send what's relevant around the time u start apache
>
> ‪On Thu, Jun 11, 2020 at 9:59 AM ‫אורי‬‎  wrote:‬
>
>> How do I use journalctl?
>> אורי
>> 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 <
>> efr...@flashner.co.il> wrote:
>>
>>> Not sure why apache is only starting some time after you reboot. What
>>> does the output of 'systemctl status apache2.service' look like?
>>>
>>> On Thu, Jun 11, 2020 at 07:31:31AM +0300, אורי wrote:
>>> > Hi,
>>> >
>>> > I estimate it's about 15 to 20 minutes after reboot that I can
>>> start apache
>>> > successfully. Otherwise, I can't start apache.
>>> >
>>> > אורי
>>> > u...@speedy.net
>>> >
>>> >
>>> > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor  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 

Re: Ubuntu - apache is not working

[אורי]

Hi,

It's a big file and I prefer to send it off-list. If you want to receive
it, please let me know (off-list).

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


On Thu, Jun 11, 2020 at 10:01 AM Shay Gover  wrote:

> journalctl -e
> Send what's relevant around the time u start apache
>
> ‪On Thu, Jun 11, 2020 at 9:59 AM ‫אורי‬‎  wrote:‬
>
>> How do I use journalctl?
>> אורי
>> 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 <
>> efr...@flashner.co.il> wrote:
>>
>>> Not sure why apache is only starting some time after you reboot. What
>>> does the output of 'systemctl status apache2.service' look like?
>>>
>>> On Thu, Jun 11, 2020 at 07:31:31AM +0300, אורי wrote:
>>> > Hi,
>>> >
>>> > I estimate it's about 15 to 20 minutes after reboot that I can
>>> start apache
>>> > successfully. Otherwise, I can't start apache.
>>> >
>>> > אורי
>>> > u...@speedy.net
>>> >
>>> >
>>> > On Thu, Jun 11, 2020 at 7:23 AM Eli Marmor  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 

Re: Ubuntu - apache is not working

[Shay Gover]

journalctl -e
Send what's relevant around the time u start apache

‪On Thu, Jun 11, 2020 at 9:59 AM ‫אורי‬‎  wrote:‬

> How do I use journalctl?
> אורי
> 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:
>> > 

Re: Ubuntu - apache is not working

[אורי]

Now I get this error on  https://en.speedypedia.info/ for the first time:

Sorry! This site is experiencing technical difficulties.

Try waiting a few minutes and reloading.

(Cannot access the database)
--
You can try searching via Google in the meantime.
Note that their indexes of our content may be out of date.

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

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

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

[אורי]

# 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]

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

[אורי]

# 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 

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

[אורי]

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 

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 

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 

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) 

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 

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
> >> 

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 

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 - 

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 

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 

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