Apache SSL: httpd (no pid file) not running

When I want to start apache there is httpd (no pid file) not running. More below.

• http worked for some years. I want ssl now.

• it is a ruby on rails application

• in /etc/apache2/ssl I put cacert.crt, ***.pem, intermedi**.crt, key.pem, req.pem, rootcert.crt

• I tested the following:

The <VirtualHost *:80> is in the file /etc/apache2/vhosts.d/default.conf and when I make a permanent redirect to <VirtualHost *:443>(which is in the same file below the <VirtualHost *:80> I get after I try service apache2 restart:

Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details.

journalctl -xe

Jan 21 13:00:01 myserver CRON[13699]: pam_unix(crond:session): session 
closed for user root
Jan 21 13:02:27 myserver liblogging-stdlog[1089]: -- MARK --
Jan 21 13:15:01 myserver cron[13735]: pam_unix(crond:session): session 
opened for user root by (uid=0)
Jan 21 13:15:01 myserver systemd[1]: Started Session 36832 of user root.
-- Subject: Unit session-36832.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-36832.scope has finished starting up.
--
-- The start-up result is done.
Jan 21 13:15:01 myserver dbus[1064]: [system] Activating service         name='org.opensuse.Snapper' (using servicehelper)
Jan 21 13:15:01 myserver dbus[1064]: [system] Successfully activated     service 'org.opensuse.Snapper'
Jan 21 13:15:03 myserver CRON[13735]: pam_unix(crond:session): session     closed for user root
Jan 21 13:22:21 myserver dbus[1064]: [system] Activating via systemd:     service name='org.freedesktop.hostname1' unit='dbus-    org.freedesktop.hostname1.service'
Jan 21 13:22:21 myserver systemd[1]: Starting Hostname Service...
-- Subject: Unit systemd-hostnamed.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-hostnamed.service has begun starting up.
Jan 21 13:22:21 myserver dbus[1064]: [system] Successfully activated     service 'org.freedesktop.hostname1'
Jan 21 13:22:21 myserver systemd[1]: Started Hostname Service.
-- Subject: Unit systemd-hostnamed.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-hostnamed.service has finished starting up.
--
-- The start-up result is done.
Jan 21 13:30:01 myserver cron[15546]: pam_unix(crond:session): session     opened for user root by (uid=0)
Jan 21 13:30:01 myserver systemd[1]: Started Session 36833 of user root.
-- Subject: Unit session-36833.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-36833.scope has finished starting up.
--
-- The start-up result is done.
Jan 21 13:30:01 myserver CRON[15546]: pam_unix(crond:session): session     closed for user root
Jan 21 13:31:48 myserver systemd[1]: Starting The Apache Webserver...
-- Subject: Unit apache2.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit apache2.service has begun starting up.
Jan 21 13:31:48 myserver start_apache2[15591]: [Mon Jan 21 13:31:48.530416     2019] [so:warn] [pid 15591] AH01574: module socache_shmcb_module is already     loaded, skipping
Jan 21 13:31:48 myserver systemd[1]: apache2.service: Main process exited,     code=exited, status=1/FAILURE
Jan 21 13:31:48 myserver start_apache2[15600]: [Mon Jan 21 13:31:48.671071     2019] [so:warn] [pid 15600] AH01574: module socache_shmcb_module is already     loaded, skipping
Jan 21 13:31:48 myserver start_apache2[15600]: httpd (no pid file) not     running
Jan 21 13:31:48 myserver systemd[1]: Failed to start The Apache Webserver.
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit apache2.service has failed.
--
-- The result is failed.
Jan 21 13:31:48 myserver systemd[1]: apache2.service: Unit entered failed     state.
Jan 21 13:31:48 myserver systemd[1]: apache2.service: Failed with result     'exit-code'.

When I take out the lines below and the <VirtualHost *:443> then it works again on http.

SSLEngine on
SSLCertificateFile /etc/apache2/ssl/***.pem
SSLCertificateKeyFile /etc/apache2/ssl/key.pem
SSLCertificateChainFile /etc/apache2/ssl/intermediatecacert.crt
SSLCACertificateFile /etc/apache2/ssl/cacert.crt

Any ideas?