bl-welcome shows lamp stack installed, localhost shows as dead

schwim · 2019-12-03 14:33:04

Hi there guys,

lamp stack installed through bl-welcome.

schwim@schwim-vm-bl8:~$ sudo /etc/init.d/apache2 start
[ ok ] Starting apache2 (via systemctl): apache2.service.
schwim@schwim-vm-bl8:~$ sudo systemctl status apache2
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enab
Active: active (running) since Tue 2019-12-03 09:50:23 EST; 15min ago
Process: 453 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
Main PID: 593 (apache2)
Tasks: 9 (limit: 4915)
CGroup: /system.slice/apache2.service
├─ 593 /usr/sbin/apache2 -k start
├─ 613 /usr/sbin/apache2 -k start
├─ 614 /usr/sbin/apache2 -k start
├─ 615 /usr/sbin/apache2 -k start
├─ 616 /usr/sbin/apache2 -k start
├─ 617 /usr/sbin/apache2 -k start
├─2056 /usr/sbin/apache2 -k start
├─2095 /usr/sbin/apache2 -k start
└─2096 /usr/sbin/apache2 -k start
Dec 03 09:50:21 schwim-vm-bl8 systemd[1]: Starting The Apache HTTP Server...
Dec 03 09:50:23 schwim-vm-bl8 systemd[1]: Started The Apache HTTP Server.
lines 1-19/19 (END)

http://localhost:

127.0.0.1

Not sure what's going on, previous installs, the stack was always running but now I can't seem to access it. Any help would be greatly appreciated.

Thanks for your time!

Last edited by schwim (2019-12-03 15:06:51)

rbh · 2019-12-03 18:46:32

Have you tried to purge apache2 and reinstall?

Do you have any other installation to compare configs with?

Do you have resorces to install another (physical or virtual), just for test...

brontosaurusrex · 2019-12-03 18:59:59

This should give you an idea on what port server might be listening

 sudo netstat -anp | grep lighttpd
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1165/lighttpd       
tcp6       0      0 :::80                   :::*                    LISTEN      1165/lighttpd       
unix  3      [ ]         STREAM     CONNECTED     25504    1165/lighttpd

Replace lighttpd with apache.

edit: Btw, that error page is generated by squid proxy in case you didn't notice.

Last edited by brontosaurusrex (2019-12-03 19:02:21)

schwim · 2019-12-03 20:07:23

Hi there Mr. Rex.

schwim@schwim-vm-bl8:~$ sudo netstat -anp | grep apache
tcp6 0 0 :::80 :::* LISTEN 605/apache2

Which I'm not sure what to do with. I didn't intentionally modify the lamp install from bl-welcome but apparently something I've done has mucked it up. Any thoughts on how I would repair it?

bigbenaugust · 2019-12-03 20:13:03

Why is that error coming from Squid proxy? I'd start there.

schwim · 2019-12-03 20:16:37

I have no idea why it's installed. Would I just purge it if it's not being used to restore the connection to apache?

sudo apt-get purge squid

bigbenaugust · 2019-12-03 20:25:52

If Squid and apache were fighting for the same port, apache never would have started.
Your browser is going through Squid and is unable connect to localhost.
It does look like apache is only listening on ipv6 based on your netstat output, though...

Don't uninstall squid just yet, it might not be conflicting.

schwim · 2019-12-03 20:31:52

Not sure what to do next then.

bigbenaugust · 2019-12-03 20:56:39

That's a connection refused, though, and not an HTTP 404 sort of a thing. Do you have a firewall set up on the machine (ufw/iptables/etc.)?

schwim · 2019-12-03 21:20:50

I do not. This is a VM that is basically a vanilla install of BL Stretch with the stack being installed via the welcome script.

ohnonot · 2019-12-04 06:48:53

show us

sudo netstat -anp | grep ':80'

linux_user · 2019-12-06 04:33:21

One of the problems I've faced with lamp stack and Helium is that apparmor isn't installed/activated by default in Helium. So even if lamp is installed, you need to install/activate apparmor for lamp to work.

earlybird · 2019-12-06 10:47:01

linux_user wrote:

One of the problems I've faced with lamp stack and Helium is that apparmor isn't installed/activated by default in Helium. So even if lamp is installed, you need to install/activate apparmor for lamp to work.

This doesn't sound right. AppArmor is if anything more restrictive, not more permissive than no AppArmor.

linux_user · 2019-12-06 15:18:13

earlybird wrote:

linux_user wrote:
One of the problems I've faced with lamp stack and Helium is that apparmor isn't installed/activated by default in Helium. So even if lamp is installed, you need to install/activate apparmor for lamp to work.
This doesn't sound right. AppArmor is if anything more restrictive, not more permissive than no AppArmor.

What I am saying is that LAMP never worked out of the box for me. I had to manually install/activate AppArmor to run LAMP.
Debian 10 has it activated default though

#1 2019-12-03 14:33:04

bl-welcome shows lamp stack installed, localhost shows as dead

#2 2019-12-03 18:46:32

Re: bl-welcome shows lamp stack installed, localhost shows as dead

#3 2019-12-03 18:59:59

Re: bl-welcome shows lamp stack installed, localhost shows as dead

#4 2019-12-03 20:07:23

Re: bl-welcome shows lamp stack installed, localhost shows as dead

#5 2019-12-03 20:13:03

Re: bl-welcome shows lamp stack installed, localhost shows as dead

#6 2019-12-03 20:16:37

Re: bl-welcome shows lamp stack installed, localhost shows as dead

#7 2019-12-03 20:25:52

Re: bl-welcome shows lamp stack installed, localhost shows as dead

#8 2019-12-03 20:31:52

Re: bl-welcome shows lamp stack installed, localhost shows as dead

#9 2019-12-03 20:56:39

Re: bl-welcome shows lamp stack installed, localhost shows as dead

#10 2019-12-03 21:20:50

Re: bl-welcome shows lamp stack installed, localhost shows as dead

#11 2019-12-04 06:48:53

Re: bl-welcome shows lamp stack installed, localhost shows as dead

#12 2019-12-06 04:33:21

Re: bl-welcome shows lamp stack installed, localhost shows as dead

#13 2019-12-06 10:47:01

Re: bl-welcome shows lamp stack installed, localhost shows as dead

#14 2019-12-06 15:18:13

Re: bl-welcome shows lamp stack installed, localhost shows as dead

Board footer