Unexpected and frequently Apache server shutdowns on Ubuntu 18.04 server

I’m having difficult times trying out to figure which are the problems Apache2 is having for it to die “randomly”. I get noticed with some insults lol and have to restart it manually

Ubuntu 18.04.5 LTS (GNU/Linux 4.15.0-141-generic x86_64)
Server version: Apache/2.4.29 (Ubuntu)
Server built: 2020-08-12T21:33:25

Memory total used free shared buff/cache available
Mem: 2041 132 540 2 1369 1731
Swap: 1048 1 1047

Default Apache config:

   <VirtualHost *:80>
    ServerName SERVER_IP:80
    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html
    <Directory /var/www/html>
            Options Indexes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            allow from all
            Require all granted
        </Directory>
        ErrorLog ${APACHE_LOG_DIR}/error.log
        CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

mpm_prefork.conf

<IfModule mpm_prefork_module>
StartServers        5
MinSpareServers     5
MaxSpareServers     10
MaxRequestWorkers   900
MaxConnectionsPerChild  0

The apache error.log file (last 4 days)

(Mon May 24 04:14:44.411885 2021) (:error) (pid 7932) (client PROXYPASS_IP:52274) script '/var/www/html/index.php' not found or unable to stat
(Mon May 24 04:34:28.497231 2021) (:error) (pid 7932) (client PROXYPASS_IP:57038) script '/var/www/html/index.php' not found or unable to stat
(Mon May 24 05:40:15.417989 2021) (:error) (pid 7931) (client PROXYPASS_IP:47890) script '/var/www/html/compliancepolicies.inc.php' not found or unable to stat
(Mon May 24 05:59:27.146680 2021) (:error) (pid 7932) (client PROXYPASS_IP:51980) script '/var/www/html/compliancepolicies.inc.php' not found or unable to stat
(Mon May 24 07:23:38.786537 2021) (:error) (pid 7933) (client PROXYPASS_IP:42934) script '/var/www/html/index.php' not found or unable to stat
(Mon May 24 07:23:40.291081 2021) (:error) (pid 7929) (client PROXYPASS_IP:42936) script '/var/www/html/index.php' not found or unable to stat
(Mon May 24 08:02:24.889646 2021) (:error) (pid 7930) (client PROXYPASS_IP:54024) script '/var/www/html/index.php' not found or unable to stat
(Mon May 24 08:02:26.436263 2021) (:error) (pid 8486) (client PROXYPASS_IP:54028) script '/var/www/html/index.php' not found or unable to stat
(Mon May 24 12:48:00.390667 2021) (:error) (pid 8486) (client PROXYPASS_IP:41238) script '/var/www/html/zabbix.php' not found or unable to stat
(Mon May 24 13:04:15.559852 2021) (:error) (pid 7933) (client PROXYPASS_IP:53794) script '/var/www/html/zabbix.php' not found or unable to stat
(Tue May 25 02:41:24.347577 2021) (:error) (pid 7929) (client PROXYPASS_IP:52622) script '/var/www/html/wp-config.php' not found or unable to stat
(Tue May 25 02:41:27.066550 2021) (:error) (pid 8486) (client PROXYPASS_IP:52632) script '/var/www/html/wp-config-sample.php' not found or unable to stat
(Tue May 25 04:26:30.536685 2021) (:error) (pid 7930) (client PROXYPASS_IP:42512) script '/var/www/html/wp-login.php' not found or unable to stat
(Tue May 25 04:26:32.413864 2021) (:error) (pid 8486) (client PROXYPASS_IP:42522) script '/var/www/html/wp-login.php' not found or unable to stat
(Tue May 25 05:47:46.793367 2021) (:error) (pid 7929) (client PROXYPASS_IP:54138) script '/var/www/html/index.php' not found or unable to stat
(Tue May 25 06:04:29.557875 2021) (:error) (pid 7932) (client PROXYPASS_IP:56360) script '/var/www/html/index.php' not found or unable to stat
(Tue May 25 07:50:38.303574 2021) (:error) (pid 7931) (client PROXYPASS_IP:48612) script '/var/www/html/wp-config.php' not found or unable to stat
(Tue May 25 07:50:41.045859 2021) (:error) (pid 7933) (client PROXYPASS_IP:48620) script '/var/www/html/wp-config-sample.php' not found or unable to stat
(Tue May 25 09:09:20.992386 2021) (:error) (pid 7929) (client PROXYPASS_IP:35758) script '/var/www/html/search.php' not found or unable to stat
(Tue May 25 09:17:50.675332 2021) (:error) (pid 8486) (client PROXYPASS_IP:39500) script '/var/www/html/lfm.php' not found or unable to stat
(Tue May 25 09:25:46.620318 2021) (:error) (pid 7931) (client PROXYPASS_IP:42236) script '/var/www/html/search.php' not found or unable to stat
(Tue May 25 09:33:42.456898 2021) (:error) (pid 7932) (client PROXYPASS_IP:44744) script '/var/www/html/lfm.php' not found or unable to stat
(Tue May 25 09:42:43.906866 2021) (:error) (pid 7929) (client PROXYPASS_IP:47104) script '/var/www/html/admin.php' not found or unable to stat
(Tue May 25 09:42:46.670982 2021) (:error) (pid 8486) (client PROXYPASS_IP:47114) script '/var/www/html/user.php' not found or unable to stat
(Tue May 25 10:37:47.776532 2021) (:error) (pid 7930) (client PROXYPASS_IP:43198) script '/var/www/html/admin.php' not found or unable to stat
(Tue May 25 10:37:50.676811 2021) (:error) (pid 7931) (client PROXYPASS_IP:43216) script '/var/www/html/user.php' not found or unable to stat
(Tue May 25 11:33:54.751108 2021) (:error) (pid 7931) (client PROXYPASS_IP:48124) script '/var/www/html/wp-login.php' not found or unable to stat
(Tue May 25 11:47:39.089285 2021) (:error) (pid 7929) (client PROXYPASS_IP:55144) script '/var/www/html/wp-login.php' not found or unable to stat
(Tue May 25 11:52:15.245326 2021) (:error) (pid 7929) (client PROXYPASS_IP:57810) script '/var/www/html/wp-login.php' not found or unable to stat
(Tue May 25 12:05:51.302652 2021) (:error) (pid 8486) (client PROXYPASS_IP:51014) script '/var/www/html/wp-login.php' not found or unable to stat
(Tue May 25 13:27:59.278228 2021) (:error) (pid 8486) (client PROXYPASS_IP:44234) script '/var/www/html/email_passthrough.php' not found or unable to stat
(Tue May 25 13:41:58.115424 2021) (:error) (pid 7932) (client PROXYPASS_IP:50026) script '/var/www/html/email_passthrough.php' not found or unable to stat
(Tue May 25 15:41:46.967467 2021) (:error) (pid 7932) (client PROXYPASS_IP:48632) script '/var/www/html/index.php' not found or unable to stat
(Tue May 25 15:56:29.117296 2021) (:error) (pid 8486) (client PROXYPASS_IP:55530) script '/var/www/html/index.php' not found or unable to stat
(Tue May 25 21:24:04.682693 2021) (:error) (pid 7930) (client PROXYPASS_IP:48692) script '/var/www/html/login_up.php' not found or unable to stat
(Tue May 25 21:38:45.465703 2021) (:error) (pid 7931) (client PROXYPASS_IP:60814) script '/var/www/html/login_up.php' not found or unable to stat
(Wed May 26 01:38:24.515955 2021) (:error) (pid 7933) (client PROXYPASS_IP:39402) script '/var/www/html/index.php' not found or unable to stat
(Wed May 26 01:57:16.951116 2021) (:error) (pid 7930) (client PROXYPASS_IP:45162) script '/var/www/html/index.php' not found or unable to stat
(Wed May 26 04:38:19.462977 2021) (:error) (pid 7931) (client PROXYPASS_IP:46570) script '/var/www/html/snippets.inc.php' not found or unable to stat
(Wed May 26 04:57:06.747394 2021) (:error) (pid 7932) (client PROXYPASS_IP:48582) script '/var/www/html/snippets.inc.php' not found or unable to stat
(Wed May 26 06:42:23.204774 2021) (:error) (pid 7931) (client PROXYPASS_IP:38488) script '/var/www/html/php.php' not found or unable to stat
(Wed May 26 06:42:24.631918 2021) (:error) (pid 7932) (client PROXYPASS_IP:38492) script '/var/www/html/phpinfo.php' not found or unable to stat
(Wed May 26 06:42:25.995827 2021) (:error) (pid 7933) (client PROXYPASS_IP:38496) script '/var/www/html/info.php' not found or unable to stat
(Wed May 26 06:42:27.355651 2021) (:error) (pid 7929) (client PROXYPASS_IP:38498) script '/var/www/html/infophp.php' not found or unable to stat
(Wed May 26 06:42:28.749061 2021) (:error) (pid 7930) (client PROXYPASS_IP:38502) script '/var/www/html/php_info.php' not found or unable to stat
(Wed May 26 06:42:30.105537 2021) (:error) (pid 8486) (client PROXYPASS_IP:38504) script '/var/www/html/test.php' not found or unable to stat
(Wed May 26 06:42:31.466479 2021) (:error) (pid 7931) (client PROXYPASS_IP:38512) script '/var/www/html/i.php' not found or unable to stat
(Wed May 26 06:42:32.843191 2021) (:error) (pid 7932) (client PROXYPASS_IP:38518) script '/var/www/html/asdf.php' not found or unable to stat
(Wed May 26 06:42:34.203376 2021) (:error) (pid 7933) (client PROXYPASS_IP:38566) script '/var/www/html/pinfo.php' not found or unable to stat
(Wed May 26 06:42:35.582707 2021) (:error) (pid 7929) (client PROXYPASS_IP:38574) script '/var/www/html/phpversion.php' not found or unable to stat
(Wed May 26 06:42:36.931655 2021) (:error) (pid 7930) (client PROXYPASS_IP:38578) script '/var/www/html/time.php' not found or unable to stat
(Wed May 26 06:42:38.387809 2021) (:error) (pid 8486) (client PROXYPASS_IP:38584) script '/var/www/html/index.php' not found or unable to stat
(Wed May 26 06:42:39.743931 2021) (:error) (pid 7931) (client PROXYPASS_IP:38586) script '/var/www/html/temp.php' not found or unable to stat
(Wed May 26 06:42:41.143446 2021) (:error) (pid 7932) (client PROXYPASS_IP:38594) script '/var/www/html/old_phpinfo.php' not found or unable to stat
(Wed May 26 06:42:42.485594 2021) (:error) (pid 7933) (client PROXYPASS_IP:38598) script '/var/www/html/infos.php' not found or unable to stat
(Wed May 26 06:42:43.832260 2021) (:error) (pid 7929) (client PROXYPASS_IP:38600) script '/var/www/html/linusadmin-phpinfo.php' not found or unable to stat
(Wed May 26 06:42:45.203621 2021) (:error) (pid 7930) (client PROXYPASS_IP:38606) script '/var/www/html/php-info.php' not found or unable to stat
(Wed May 26 07:33:26.421135 2021) (:error) (pid 8486) (client PROXYPASS_IP:55784) script '/var/www/html/index.php' not found or unable to stat
(Wed May 26 07:52:46.969891 2021) (:error) (pid 7932) (client PROXYPASS_IP:40388) script '/var/www/html/index.php' not found or unable to stat
(Wed May 26 12:06:27.502320 2021) (:error) (pid 7929) (client PROXYPASS_IP:37278) script '/var/www/html/php.php' not found or unable to stat
(Wed May 26 12:06:28.873814 2021) (:error) (pid 7930) (client PROXYPASS_IP:37334) script '/var/www/html/phpinfo.php' not found or unable to stat
(Wed May 26 12:06:30.206625 2021) (:error) (pid 9596) (client PROXYPASS_IP:37408) script '/var/www/html/info.php' not found or unable to stat
(Wed May 26 12:06:31.590073 2021) (:error) (pid 8486) (client PROXYPASS_IP:37448) script '/var/www/html/infophp.php' not found or unable to stat
(Wed May 26 12:06:32.932107 2021) (:error) (pid 7931) (client PROXYPASS_IP:37490) script '/var/www/html/php_info.php' not found or unable to stat
(Wed May 26 12:06:34.306775 2021) (:error) (pid 7932) (client PROXYPASS_IP:37516) script '/var/www/html/test.php' not found or unable to stat
(Wed May 26 12:06:35.701149 2021) (:error) (pid 9594) (client PROXYPASS_IP:37632) script '/var/www/html/i.php' not found or unable to stat
(Wed May 26 12:06:37.068345 2021) (:error) (pid 7933) (client PROXYPASS_IP:37710) script '/var/www/html/asdf.php' not found or unable to stat
(Wed May 26 12:06:38.426905 2021) (:error) (pid 7929) (client PROXYPASS_IP:37810) script '/var/www/html/pinfo.php' not found or unable to stat
(Wed May 26 12:06:39.855108 2021) (:error) (pid 7930) (client PROXYPASS_IP:37902) script '/var/www/html/phpversion.php' not found or unable to stat
(Wed May 26 12:06:41.295390 2021) (:error) (pid 9596) (client PROXYPASS_IP:38004) script '/var/www/html/time.php' not found or unable to stat
(Wed May 26 12:06:42.634024 2021) (:error) (pid 8486) (client PROXYPASS_IP:38108) script '/var/www/html/index.php' not found or unable to stat
(Wed May 26 12:06:44.767269 2021) (:error) (pid 7931) (client PROXYPASS_IP:38222) script '/var/www/html/temp.php' not found or unable to stat
(Wed May 26 12:06:46.129798 2021) (:error) (pid 7932) (client PROXYPASS_IP:38346) script '/var/www/html/old_phpinfo.php' not found or unable to stat
(Wed May 26 12:06:47.486713 2021) (:error) (pid 9594) (client PROXYPASS_IP:38442) script '/var/www/html/infos.php' not found or unable to stat
(Wed May 26 12:06:48.917990 2021) (:error) (pid 7933) (client PROXYPASS_IP:38534) script '/var/www/html/linusadmin-phpinfo.php' not found or unable to stat
(Wed May 26 12:06:50.382427 2021) (:error) (pid 7929) (client PROXYPASS_IP:38598) script '/var/www/html/php-info.php' not found or unable to stat
(Wed May 26 20:32:46.990524 2021) (:error) (pid 9596) (client PROXYPASS_IP:33452) script '/var/www/html/getcfg.php' not found or unable to stat
(Wed May 26 20:52:09.915084 2021) (:error) (pid 7932) (client PROXYPASS_IP:50880) script '/var/www/html/getcfg.php' not found or unable to stat
(Fri May 28 17:11:34.033543 2021) (core:warn) (pid 7924) AH00045: child process 7929 still did not exit, sending a SIGTERM
(Fri May 28 17:11:34.033689 2021) (core:warn) (pid 7924) AH00045: child process 7930 still did not exit, sending a SIGTERM
(Fri May 28 17:11:34.033703 2021) (core:warn) (pid 7924) AH00045: child process 7931 still did not exit, sending a SIGTERM
(Fri May 28 17:11:34.033716 2021) (core:warn) (pid 7924) AH00045: child process 7932 still did not exit, sending a SIGTERM
(Fri May 28 17:11:34.033728 2021) (core:warn) (pid 7924) AH00045: child process 7933 still did not exit, sending a SIGTERM
(Fri May 28 17:11:34.033740 2021) (core:warn) (pid 7924) AH00045: child process 8486 still did not exit, sending a SIGTERM
(Fri May 28 17:11:36.035954 2021) (core:warn) (pid 7924) AH00045: child process 7929 still did not exit, sending a SIGTERM
(Fri May 28 17:11:36.035995 2021) (core:warn) (pid 7924) AH00045: child process 7930 still did not exit, sending a SIGTERM
(Fri May 28 17:11:36.036001 2021) (core:warn) (pid 7924) AH00045: child process 7931 still did not exit, sending a SIGTERM
(Fri May 28 17:11:36.036008 2021) (core:warn) (pid 7924) AH00045: child process 7932 still did not exit, sending a SIGTERM
(Fri May 28 17:11:36.036014 2021) (core:warn) (pid 7924) AH00045: child process 7933 still did not exit, sending a SIGTERM
(Fri May 28 17:11:36.036021 2021) (core:warn) (pid 7924) AH00045: child process 8486 still did not exit, sending a SIGTERM
(Fri May 28 17:11:38.038163 2021) (core:warn) (pid 7924) AH00045: child process 7929 still did not exit, sending a SIGTERM
(Fri May 28 17:11:38.038217 2021) (core:warn) (pid 7924) AH00045: child process 7930 still did not exit, sending a SIGTERM
(Fri May 28 17:11:38.038229 2021) (core:warn) (pid 7924) AH00045: child process 7931 still did not exit, sending a SIGTERM
(Fri May 28 17:11:38.038241 2021) (core:warn) (pid 7924) AH00045: child process 7932 still did not exit, sending a SIGTERM
(Fri May 28 17:11:38.038252 2021) (core:warn) (pid 7924) AH00045: child process 7933 still did not exit, sending a SIGTERM
(Fri May 28 17:11:38.038264 2021) (core:warn) (pid 7924) AH00045: child process 8486 still did not exit, sending a SIGTERM
(Fri May 28 17:11:40.040476 2021) (core:error) (pid 7924) AH00046: child process 7929 still did not exit, sending a SIGKILL
(Fri May 28 17:11:40.044186 2021) (core:error) (pid 7924) AH00046: child process 7930 still did not exit, sending a SIGKILL
(Fri May 28 17:11:40.046559 2021) (core:error) (pid 7924) AH00046: child process 7931 still did not exit, sending a SIGKILL
(Fri May 28 17:11:40.048150 2021) (core:error) (pid 7924) AH00046: child process 7932 still did not exit, sending a SIGKILL
(Fri May 28 17:11:40.050355 2021) (core:error) (pid 7924) AH00046: child process 7933 still did not exit, sending a SIGKILL
(Fri May 28 17:11:40.052198 2021) (core:error) (pid 7924) AH00046: child process 8486 still did not exit, sending a SIGKILL
(Fri May 28 17:11:41.055832 2021) (mpm_prefork:notice) (pid 7924) AH00169: caught SIGTERM, shutting down
(Fri May 28 17:11:41.230953 2021) (mpm_prefork:notice) (pid 819) AH00163: Apache/2.4.29 (Ubuntu) configured -- resuming normal operations
(Fri May 28 17:11:41.230989 2021) (core:notice) (pid 819) AH00094: Command line: '/usr/sbin/apache2'
(Fri May 28 17:18:43.024640 2021) (mpm_prefork:notice) (pid 819) AH00169: caught SIGTERM, shutting down

There’s a nginx server which acts as a proxypass (I guess) that throws 502 bad gateway when Internet client tries to use the webservice while Apache is dead

Any clues? Thanks a lot

Ubuntu Server 18.04 and 20.04 fail on 2010 PC

At the moment I am trying to install Ubuntu Server on a PC made in 2010 (this is not the first time I have made a server on old hardware), however when I attempt to install Ubuntu Server 18.04 the installer will report “Unable to install Ubuntu Server 18.04, please try again…” or something of the like. Trying the ‘mini.iso’ version of the Ubuntu Server 18.04 the installer freezes after pressing install. Trying Ubuntu Server 20.04 the installer makes it further but eventually does the same as the first instance, however the only difference between 18.04 and 20.04 is that before 20.04’s installer launches it reports three times ‘blk_update_request: I/O error, dev fd0, sector 0’, it then continues as normal. Does this have anything to do with the failed attemps? Some extra info, I have two identical 500GB harddrives and a similar 250GB harddrive, I’m attempting to run the two 500GB hdds in a RAID0 config and then have the 250GB drive for Ubuntu Server itself to install on. Thanks…

18.04 – How to get source version of containerd 1.3.3 via apt?

Package containerd in version 1.3.3 seems to be the most recent one for Ubuntu Bionic architecture amd64:

$ apt show containerd      
Package: containerd
Version: 1.3.3-0ubuntu1~18.04.4
Priority: optional
...

Unfortunately the sources are not available.

$ apt-get source containerd      
Reading package lists... Done
E: Unable to find a source package for containerd


$ cat /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu/ bionic main restricted
deb-src http://archive.ubuntu.com/ubuntu/ bionic main restricted
deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted
deb-src http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted

It seems like the sources are only available for the most recent version. Which is 1.4.4. But this version is not available for amd64.

Is there a way of getting the sources for the recent containerd version 1.3.3 via apt ?

Nginx won’t start after upgrade from 16.04 to 18.04

I have just upgraded from 16.04 to 18.04 and nginx is not starting. One of the lines from journalctl -xe is:

nginx.service: Failed at step EXEC spawning /usr/sbin/nginx: No such file or directory

…and yes /usr/sbin/nginx doesn’t exist there.

This question seems the most relevant for my issue. However given that I’m going from 16.04 to 18.04 and the problem and resolution described therein are old and were temporary I’m wondering if this is some other problem.

All help gratefully received.

Of course if the solution is as described therein then I will carry that out but I’m reluctant to do so in case I cause more harm.

windows subsystem for linux – How to upgrade ubuntu 18.04 to 20.04 in WSL when “wsl –export” fails

I’m trying to follow the directions to upgrade my WSL 1 Ubunutu (18.04) release to WSL 2 Ubuntu-20.04 and the first step gives me an error message I don’t know how to work around.

wsl --set-version ubuntu 
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
Exporting the distribution failed.
bsdtar: Couldn't read link data: I/O error
bsdtar: Error exit delayed from previous errors.

I have also tried doing it the “normal” Ubuntu way and get different “errors”:

$ lsb_release -a

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.5 LTS
Release:    18.04
Codename:   bionic
cfclark@p53:
~
$ sudo apt update

Hit:1 http://ppa.launchpad.net/git-core/ppa/ubuntu bionic InRelease
Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:5 http://security.ubuntu.com/ubuntu bionic-security InRelease
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.
cfclark@p53:
~
$ sudo apt upgrade

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  libdumbnet1
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
cfclark@p53:
~
$ sudo do-release-upgrade

Checking for a new Ubuntu release
Get:1 Upgrade tool signature (1554 B)                                                                                                                                                                       
Get:2 Upgrade tool (1340 kB)                                                                                                                                                                                
Fetched 1342 kB in 0s (0 B/s)                                                                                                                                                                               
authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg' 
extracting 'focal.tar.gz'
(4l>7(r(?1;3;4;6l87(4l=)0(1;66rlspci: Cannot find any working access method.

Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://archive.ubuntu.com/ubuntu bionic InRelease
Hit http://ppa.launchpad.net/git-core/ppa/ubuntu bionic InRelease
Hit http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit http://security.ubuntu.com/ubuntu bionic-security InRelease
Fetched 0 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done

Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
=== Command detached from window (Sun May 23 13:26:05 2021) ===
=== Command terminated with exit status 1 (Sun May 23 13:26:15 2021) ===

active directory – Joining AD through haproxy Ubuntu 18.04

For starters I have several Ubuntu servers successfully joined to the domain for the servers that sit in the same subnet as the DCs. However, I’m working to join a few Ubuntu machines through haproxy but running into an odd error that has me stuck at the moment. Worrying about auth flapping I disabled one of the DCs through haproxy for now.

haproxy config:

frontend DC_389
    bind 0.0.0.0:389
    mode tcp
    option tcplog
    default_backend DC_Backend_389

backend DC_Backend_389
    mode tcp
    server dc1 X.X.X.21:389
    #server dc2 X.X.X.22:389

frontend DC_636
    bind 0.0.0.0:636
    mode tcp
    option tcplog
    default_backend DC_Backend_636

backend DC_Backend_636
    mode tcp
    server dc1 X.X.X.21:636
    #server dc2 X.X.X.22:636

frontend DC_88
        bind 0.0.0.0:88
        mode tcp
        option tcplog
        default_backend DC_Backend_88

backend DC_Backend_88
        mode tcp
        server dc1 X.X.X.21:88
        #server dc2 X.X.X.22:88

frontend DC_464
        bind 0.0.0.0:464
        mode tcp
        option tcplog
        default_backend DC_Backend_464

backend DC_Backend_464
        mode tcp
        server dc1 X.X.X.21:464
        #server dc2 X.X.X.22:464

All in all connectivity all seems good.

On the server I’m connecting from I’m authing with the same creds as I have successfully done so inside the network. Also, I’ve added the int.domain.com IP in /etc/hosts to point to the proxy’s IP address (Y.Y.Y.20 int.domain.com)

realm join -U linux_ad_admin --computer-ou="OU=LinuxServers,OU=Servers,OU=IT_Systems" int.domain.com --verbose

Log:

 * Resolving: _ldap._tcp.int.domain.com
 * Resolving: int.domain.com
 * Performing LDAP DSE lookup on: Y.Y.Y.20
 * Successfully discovered: int.domain.com
Password for linux_ad_admin: 
 * Required files: /usr/sbin/oddjobd, /usr/libexec/oddjob/mkhomedir, /usr/sbin/sssd, /usr/sbin/adcli
 * LANG=C /usr/sbin/adcli join --verbose --domain int.domain.com --domain-realm INT.DOMAIN.COM --domain-controller Y.Y.Y.20 --computer-ou OU=LinuxServers,OU=Servers,OU=IT_Systems,dc=int,dc=domain,dc=com --login-type user --login-user linux_ad_admin --stdin-password
 * Using domain name: int.domain.com
 * Calculated computer account name from fqdn: DMZHOSTTEST1
 * Using domain realm: int.domain.com
 * Sending NetLogon ping to domain controller: Y.Y.Y.20
 * Wrote out krb5.conf snippet to /var/cache/realmd/adcli-krb5-llM0zh/krb5.d/adcli-krb5-conf-qOXHOs
 * Authenticated as user: linux_ad_admin@INT.DOMAIN.COM
 * Using GSS-SPNEGO for SASL bind
 ! Couldn't authenticate to active directory: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (Server not found in Kerberos database)
adcli: couldn't connect to int.domain.com domain: Couldn't authenticate to active directory: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (Server not found in Kerberos database)
 ! Insufficient permissions to join the domain
realm: Couldn't join realm: Insufficient permissions to join the domain

Any idea what I’m missing here? This same command/account joins the servers to the AD no problem while in the same subnet. But going through the proxy is suddenly giving me the insufficient permissions error. Are additional open ports needed to go through haproxy?

Elementary OS, 18.04 – Nvidia driver is not working. Nouveau turned off, X server empty

I am struggling to install a Nvidia driver for almost two weeks and slowly giving up. I reinstalled the newly Elementary OS probably 5 times already and still cannot find a way how to install the driver.

I went through many guides on the forum and internet but none of them worked.
Now I stuck on the low resolution 640×480 and any driver I installed not working. I have Nvidia GTX 980 graphic card, and last few days tried to install driver 465, 460, 450, 390. Result was: even the “nvidia-smi” showing that driver is installed, the X server is empty and low resolution is still cutting my eyes.

The secure boot in IOS is turned off, nouveau workaround applied in the config file.

These are added in: /etc/modprobe.d/blacklist.conf
(according: https://newbedev.com/how-to-disable-nouveau-kernel-driver)

blacklist nouveau
blacklist lbm-nouveau
options nouveau modeset=0
alias nouveau off
alias lbm-nouveau off

I tried also these links: none of them worked though 🙁
Nvidia drivers reset after update and now monitor is “unknown” and stuck in 640×480
Nvidia driver problems on 20.04
https://github.com/lutris/docs/blob/master/InstallingDrivers.md
Completely removing old Nvidia drivers
https://forums.linuxmint.com/viewtopic.php?f=59&t=339381&sid=47bef6e9d81174f29e405858bcc98d28&start=20
https://forums.linuxmint.com/viewtopic.php?p=1895521#p1895521
Unable to get nvidia running on ubuntu 18.04.2
https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-18-04-bionic-beaver-linux

Is there normal way to install a current nvidia driver ? or am I forced to use a nouveau or old 390 version ? (I had old one running when I installed it manually few days ago, but I realized when kernel update will come I had to re-intall it again, so tried to work again on auto updating driver, via additional driver center).

I will be really grateful if anyone can shade a light and help me.
The OS reinstall is not a problem at this time, so I am willing to try any guide, just to have a latest driver working, even after reboot. With proper resolution of course.

Many thanks.

(if any output needed please tell me, I will provide it)

hyper v – Ubuntu fails to start by default after upgrade 18.04 to 20.04

I tried to upgrade an Ubuntu 18.04 to 20.04 today. The system is a server type installation running as a virtual machine on Hyper-V, primarily running letsencrypt and nginx.

Actually I tried twice, both upgrades left me with a system that doesn´t boot by default. The first iteration was I tried to accept maintainer version for the boot/grub menu, and as that didn´t restart properly, I tried another time, this time keeping my own version. Both upgrades left me with a system that was not booting.

With the second upgrade, I experimented a little more. When the system restarts, I am stuck with it doesn´t boot. When I then power off and power on again, I get a boot menu with the options Ubuntu, Advanced options for Ubuntu, and UEFI Firmware Settings. With Advanced I get Ubuntu with various kernel options, with Linux 5.4.0-73-generic w/o recovery mode, and Linux 4.15.0-143-generic w/o recovery mode. The variants with 4.15.0-143 actually work, whereas 5.4.0-73 doesn´t work.

I do have some VMs that run 20.04 with kernel 5.4.0-something, thus I assume it is an issue caused by the upgrade or previous installation.

Any idea what to look for?

Thanks, Joachim

18.04 – How to delete an aptly published snapshot

Using Ubuntu 18.04 and aptly version 1.4.0.

I am attempting to create a focal mirror using aptly, as follows:

aptly mirror create --architectures="amd64" -filter-with-deps -filter="Installed-Size (<=500000)" focal http://uk.archive.ubuntu.com/ubuntu focal main restricted universe multiverse
aptly mirror update focal
aptly snapshot create focal-latest from mirror focal
aptly publish snapshot --skip-signing focal-latest filesystem:export:export

This seemed to work OK — but I made a small mistake and want to delete the published snapshot and redo it.

How does one do this please? The command line help shows this:

Usage: aptly publish drop <distribution> ((<endpoint>:prefix)

I presume <distribution> is what aptly publish snapshot refers to as <name> but I have been unsuccessful divining the correct format to use. I have tried dozens of combinations, but here are a few, and the results:

$ aptly publish drop focal-latest
ERROR: unable to remove: published repo with storage:prefix/distribution ./focal-latest not found
$ aptly publish drop focal-latest filesystem:export:export
ERROR: unable to remove: published repo with storage:prefix/distribution filesystem:export:export/focal-latest not found
$ aptly publish drop focal-latest filesystem:export
ERROR: unable to remove: published repo with storage:prefix/distribution filesystem:export/focal-latest not found