Apache2 failed to start

[fausto99]

Yesterday I installed Apache and got the “it works” page using localhost in my browser. Today it wont start. Being new to Linux I don't have the first idea on where to start. I've tried removing and re-installing Apache using the Muon Package Manager but no joy.

Any suggestions on where to start?

[ActionParsnip]

What is the output of:

ps -ef | grep apache | grep -v apache
apt-cache policy apache2
lsb_release -a
uname -a

Thanks

[guiverc]

Question also appears to be asked here - https://discourse.lubuntu.me/t/new-i...-to-start/2727

[fausto99]

ricobasso@D620-02:~$ apt-cache policy apache2
apache2:                                                                     
  Installed: 2.4.46-4ubuntu1.1                                               
  Candidate: 2.4.46-4ubuntu1.1                                               
  Version table:                                                             
 *** 2.4.46-4ubuntu1.1 500                                                   
        500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages
        500 http://gb.archive.ubuntu.com/ubuntu hirsute-security/main amd64 Packages
        100 /var/lib/dpkg/status                                             
     2.4.46-4ubuntu1 500                                                     
        500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages  
ricobasso@D620-02:~$ lsb_release -a                      
No LSB modules are available.                                                
Distributor ID: Ubuntu                                                                                                       
Description:    Ubuntu 21.04                                                                                                 
Release:        21.04                                                                                                        
Codename:       hirsute
ricobasso@D620-02:~$ uname -a
Linux D620-02 5.11.0-34-generic #36-Ubuntu SMP Thu Aug 26 19:22:09 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
ricobasso@D620-02:~$ ^C
ricobasso@D620-02:~$

is this what you needed to see?

[fausto99]

yes . why are there two Lubuntu fora?

[grahammechanical]

yes . why are there two Lubuntu fora?

The Ubuntu forum has support and discussion sections not only for Ubuntu users but also for users of Linux distributions based on Ubuntu but with a different desktop environment. There is even a section for other operating systems. And there are several sections for specialist categories.

The developers of other distributions based on Ubuntu (we call them Ubuntu flavours) sometimes like to provide their own support channel. It all depends upon how many people are actually involved in helping to develop that distribution as to whether they have the resources to do this.

Your problem is not connected especially to the desktop environment that you are using. It is not a Lubuntu or a Ubuntu issue but an Apache2 issue. Which brings an end to my involvement in this problem.

Regards

[fausto99]

What was the purpose of asking me to run this code?

[deadflowr]

What code?
You mean the code in post #2?
I would think it's to see some very basic information about the system and the apache2 version installed.

That said if you use the systemctl command as posted in the lubuntu forum thread it might show something useful.
You can use the status option like

systemctl status apache2

[TheFu]

After running,

sudo systemctl status apache2

You can run

journalctl -xe

to see any failures.

Typically, failures to start are due to incorrect modification of a vhost file or some other apache settings in /etc/apache2/
or incorrect directory permissions where ever the files are stored. Incorrect file and directory permissions are an excellent way to have a system be hacked.

Running a web server isn't exactly something that someone new to Unix-like OSes should be doing. It is fine, provided the service isn't available outside the LAN. We all start learning somewhere, but skipping over basic Unix skills and running a web server is a mistake if the intent is to make a website for the internet.

[fausto99]

Running a web server isn't exactly something that someone new to Unix-like OSes should be doing. It is fine, provided the service isn't available outside the LAN. We all start learning somewhere, but skipping over basic Unix skills and running a web server is a mistake if the intent is to make a website for the internet.

that's not my intention at all. I have a trainer bike in my garage where I run an app called Fulgaz. It uses some sort of mp4 file which streams video to my Apple TV + TV and this controls the drag and tilt of the trainer bike according to the terrain in the video. It's very good but my internet connection is poor.

My garage is a fair way from my house and I can't have permanent cabling (mains or ethernet) to it. So, the plan is to d/l the mp4 files and stream them locally from a laptop as the Apple TV has very limited storage. I want to re-purpose an old not very powerful laptop, hence the idea to install a light version of Linux (lubuntu). I need Samba to get files on and off a Windows PC and I need Apache to stream to the Apple TV.

That's it. The laptop will only be on my LAN with very restricted sharing.