Starting apache2 server failed ?

[Feathers McGraw]

OK so after running that command to stop tntnet, can you start Apache successfully?

[kdeuser]

Still not working :

reel@BM2LTSR66RBex:/media/hd/home/reel$ sudo service apache2 start
sudo: unable to resolve host BM2LTSR66RBex
[sudo] password for reel: 
Starting web server: apache2(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Action 'start' failed.
The Apache error log may have more information.
 failed!
The apache2 instance did not start within 20 seconds. Please read the log files to discover problems ... (warning).
reel@BM2LTSR66RBex:/media/hd/home/reel$

On kernel 3.15.10-031510-generic , my mediacenter boots fine - tv side plus pc .

Loading kernel 3.19.2 is fast but the tv side has no tv picture but the pc side is ok.

[Feathers McGraw]

please run the two commands in order:

sudo service tntnet stop
sudo service apache2 start

i guess you've probably rebooted since you stopped tntnet last (these services are often autostarted on boot)

also, could you run this, which will show us any time tntnet showed up in your APT history. I still think it was probably pulled in by some other package.

cat /var/log/apt/history.log | grep -C 5 tntnet
for log in /var/log/apt/history.log.* ; do echo $log && zcat $log | grep -C 5 tntnet

Sam

[kdeuser]

Hi there Feathers McGraw,

The problem which was causing Reelbox not to output via hdmi seems to have been addressed by the developers of BM2LTS at vdr-portal.

The solution was to download and install a file named (hdshm.ko) and place in :

/lib/modules/3.16.0-33-generic/kernel/drivers/video

Followed by :

sudo depmod -a
sudo init 6

Everything seems to be working now.

BTW , i entered those commands from the post #18 :

reel@BM2LTSR66RBin:/media/hd/home/reel$ sudo service tntnet stop
[sudo] password for reel: 
Stopping web server: tntnet.
reel@BM2LTSR66RBin:/media/hd/home/reel$ sudo service apache2 start
Starting web server: apache2AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.5.1. Set the 'ServerName' directive globally to suppress this message
.
reel@BM2LTSR66RBin:/media/hd/home/reel$

No error messages there , only that `could not determine....` message.

I will now place `ServerName foo.com` command in `apache2.conf` and see whether that message goes away.

Update : Entered those 2 commands from post #18 -

sudo service tntnet stop
sudo service apache2 start

The Resulting output :

reel@BM2LTSR66RBin:/media/hd/home/reel$ sudo nano /etc/apache2/apache2.conf
[sudo] password for reel: 
reel@BM2LTSR66RBin:/media/hd/home/reel$ sudo service tntnet stop
Stopping web server: tntnet.
reel@BM2LTSR66RBin:/media/hd/home/reel$ sudo service apache2 start
Starting web server: apache2.
reel@BM2LTSR66RBin:/media/hd/home/reel

Indeed, back to normal, no warnings or errors.

Many thanks for all your help on this Feathers McGraw.

[Feathers McGraw]

You're welcome

[SteveRiley]

Until reboot. Then who knows which service will start first -- that Tntnet thing or Apache.

It would be good to understand why you have Tntnet -- maybe it's a candidate for removal. Feathers's post #18 had a second set of commands. What's the output of those?