[mythtv-users] Resolved: New installation errors

[Dick Steffens]

On 09/25/2017 03:16 PM, Bill Meek wrote:
> On 09/25/2017 04:10 PM, Dick Steffens wrote:
>> On 09/25/2017 02:04 PM, Bill Meek wrote:
>>> On 09/25/2017 03:58 PM, Dick Steffens wrote:
>>>>
>>>> rsteff at Enu-1:~$ nmap -p 80 192.168.0.106
>>>>
>>>> Starting Nmap 6.40 ( http://nmap.org ) at 2017-09-25 13:56 PDT
>>>> Nmap scan report for Jetway.lan (192.168.0.106)
>>>> Host is up (0.00017s latency).
>>>> PORT   STATE  SERVICE
>>>> 80/tcp closed http
>>>
>>> Web server not started if it happens from all boxes.
>>> Firewall preventing one box from connecting (sounds
>>> odd.) Maybe there are clues in: /var/log/apache2 .
>>>
>>
>> Apache not installed -- at least I assume it's not because there is 
>> no /var/log/apache2.
>>
>> I didn't install apache myself. I can easily do that, but what do I 
>> put where to get MythWeb working?
>
> Try: dpkg -l apache2 just to be sure it isn't
> there. Other Web servers can be used, but that's
> just the one Mythbuntu included years ago for my
> system.

Apache wasn't installed. I installed it.

> If you're starting mythweb from scratch, there should
> be a README and INSTALL file wherever mythweb was
> installed - such as: /var/www/mythweb .

There is no /var/www/mythweb. I did a search of the drive and did not 
find mythweb anywhere.

I Googled it and found https://github.com/MythTV/mythweb, and found the 
INSTALL file. I see that I need to also install php 5.3.x and Perl 
5.8.x. I can do that. And I see that I can download a tarball for 
mythweb from https://github.com/MythTV/mythweb/releases. I assume I 
should use v0.28.1 from Feb 1. I'll get that and put it in /var/www. 
Then I'll follow all the directions and see how that goes.

I did look at the new web tool, but I don't find a way to configure the 
display the way I need it (6 hours at a time). I'm happy with the old 
MythWeb for now. When more features are added to the new one, I'll give 
it a try.

Thanks to you, and others who responded, for all your help over the past 
few weeks.

My objective is to retire the old machine, which puts out a lot of heat. 
The "new" one is much smaller and cooler. At this point I don't have a 
cable card, and am just using Comcast's service. There are pluses and 
minuses to using their "DVR." It does not store videos locally, but in 
"the cloud." That's one of its disadvantages since when the cable is 
out, I can't watch already recorded stuff. The other is their web 
interface for scheduling. When I started with it last year it was okay. 
I was able to set it up for 6 hours at a time. But then they introduced 
a fancy Flash based interface. Number one, it won't work on Linux, so I 
have to use Google Chrome on my virtual Win 7 machine. That limits me to 
my desktop machine. It is not particularly configurable. It doesn't do 
Favorites, so I'm stuck with looking through 1785 channel numbers plus a 
slew of TVGO listings. Very unsatisfactory. Plus, I can only see two 
hours at a time. Also very unsatisfactory. Fortunately, I've been able 
to use the listings from MythWeb to see what I want to schedule. I still 
have to do the scheduling on the virtual machine, or, if I'm using my 
laptop in the living room, I can schedule a recording using Comcast's on 
screen tool. Not as good as MythWeb, but it works.

The plus for the service from Comcast ... pardon me xfinity ... is that 
it does the right thing with my TV. With MythTV, I always had to live 
with menu and task bars at the top and bottom of the screen, and the TV 
doesn't do underscan right. So, for now, I'll happily use MythWeb for 
scheduling, and Comcast for the DVR. This also has a higher WAF (Wife 
Acceptance Factor for those who haven't seen the acronymn).

If I ever decide I want to go back, I'll have to go through all this 
setup again, because even though my Jetway has a built in nVidia device, 
the horsepower on the box is too low (I tried this a few years ago when 
I first started using MythTV).

Again, thanks to all who have helped me get through this installation. 
I've learned quite a bit, and relearned some things I should have known.

-- 
Regards,

Dick Steffens