Apache wont start after dist-upgrade

Briefly describe your issue below:
Apache wont start after dist-upgrade.

sudo service apache2 start

output :

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

systemctl status apache2.service

output:

apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2019-02-02 15:20:55 IST; 2min 20s ago
Process: 16658 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)

sudo journalctl | tail

output:

Feb 02 15:20:55 parrot apachectl[16658]: no listening sockets available, shutting down
Feb 02 15:20:55 parrot apachectl[16658]: AH00015: Unable to open logs
Feb 02 15:20:55 parrot apachectl[16658]: Action 'start' failed.
Feb 02 15:20:55 parrot apachectl[16658]: The Apache error log may have more information.
Feb 02 15:20:55 parrot systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
Feb 02 15:20:55 parrot systemd[1]: apache2.service: Failed with result 'exit-code'.
Feb 02 15:20:55 parrot systemd[1]: Failed to start The Apache HTTP Server.
Feb 02 15:20:55 parrot sudo[16629]: pam_unix(sudo:session): session closed for user root
Feb 02 15:23:59 parrot sudo[16675]:  johndoe : TTY=pts/0 ; PWD=/etc/apache2 ; USER=root ; COMMAND=/bin/journalctl
Feb 02 15:23:59 parrot sudo[16675]: pam_unix(sudo:session): session opened for user root by (uid=0)

apache2ctl configtest

output:

Syntax OK

What version of Parrot are you running? (Release 4.5 64-bit, Kernel Linux 4.19.0-parrot1-13t-amd64 x86_64)

What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)

Configured to multiboot with other systems? (yes / no)

If there are any similar issues or solutions, link to them below:

If there are any error messages or relevant logs, post them below:

no listening sockets available, shutting down

By the look of that, you already have a service running on port 80. Either kill off the other program or change the port you want to use.

its getting used by gsad

tcp 0 0 127.0.0.1:80 0.0.0.0:* LISTEN 845/gsad

whatis gsad

o/p:

gsad (8) - Greenbone Security Assistant for the Open Vulnerabilit...

is it necessary service?

i terminated it then fired the command, apache started but getting “Forbidden
You don’t have permission to access / on this server.” when accessing localhost.

so i changed the default directory from /usr/share/www to home/www with index.html still same error

Greenbone is openVAS. So it doesnt have to be running.

A 403 means your server is running but you need to change you configuration to access your service. There will be a config in /etc/apache2/sites-available/ listening on port 80, change that config.

tried it, wont work. can it be possible bcos of parot new upgrade, i think they moved from apache to nginx,in previous versions there was only option for apache in applications > parrot > system service > http.
now it shows nginx.
nginx is working without any errors.
one more thing is parrot-upgrade same as dist-upgrade?

Use whatever works.

Yes, the commands parrot-upgrade and dist-upgrade are the same.

I think you set openvas start with your system. Port 80 http has been used so Apache can’t bind that port. That is simple.