[rpbg]

@cmik,  here an update from me:

Thanks for your hint to check the following site:  https://community.atlassian.com/t5/Quest...q-p/433267
And, indeed after following the tips  to check any incorrect symbols in one of the configuration files.  I found and removed the incorrect symbols
in /etc/apache2/ports.conf.  However, amending/saving the configuration file and rerunning it   I have got new error, hence it failed again as follows:
------------------------------
-- Unit apache2.service has begun starting up.
Nov 15 14:06:55 osmc apachectl[4193]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive gl
Nov 15 14:06:55 osmc apachectl[4193]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Nov 15 14:06:55 osmc apachectl[4193]: no listening sockets available, shutting down
Nov 15 14:06:55 osmc apachectl[4193]: AH00015: Unable to open logs
Nov 15 14:06:55 osmc apachectl[4193]: Action 'start' failed.
Nov 15 14:06:55 osmc apachectl[4193]: The Apache error log may have more information.
Nov 15 14:06:55 osmc systemd[1]: apache2.service: Control process exited, code=exited status=1
Nov 15 14:06:55 osmc systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit apache2.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit apache2.service has failed.
--
-- The result is failed.
Nov 15 14:06:55 osmc systemd[1]: apache2.service: Unit entered failed state.
Nov 15 14:06:55 osmc systemd[1]: apache2.service: Failed with result 'exit-code'.
Nov 15 14:06:55 osmc sudo[4187]: pam_unix(sudoession): session closed for user root
------------------------------