Home » Forums » MythDora » Installation and Setup

MythWeather (Mythdora 2.32 LIVE)

Submitted by pindari on August 5, 2006 - 3:08pm

I have the MythDora 2.32 backend/frontend running and three frontend machines running (each was installed with MythDora 2.32 and selecting frontend only (rather than complete frontend and backend)). I can watch live TV, recordings or videos from any of the frontends and can set recordings so all the networking appears to be in order.

For some reason Mythweather isn't getting and/or displaying any data as I get no data on any of the weather pages and the screen shows "Not All Information Av..." along the bottom. As a control I booted one of the frontend machines with Mythdora 2.32 LIVE and the weather did work (as did the other functions once I set all the paths and network conditions). The backend/frontend machine does display the weather correctly.

Any ideas as to what I have missed in my configuration of the frontends that the Mythdora 2.32 LIVE version is doing correctly?

Tony.

‹ IR Blaster for Dish Network Receiver ?? snes9x: How to Fullscreen? Instruction help requested ›

fixed (but embarrassed)

Submitted by pindari on August 5, 2006 - 3:32pm.

There is nothing like posting a question to engage the brain -- in my haste to bring up all the frontend machines I failed to create /etc/resolve.conf so I had no DNS info, sigh! I obviously paid more attention doing the backend.

My configuration:

backend - Dell 4600 with 2.4GHz P4 (500GB disk, 1GB RAM, PVR250, PVR150MCE, generic ATI video since it is a dedicated backend with no need to display video)

multiple frontend - Dell GX240 Low profile with 1.6GHz P4 (20GB disk, 500M RAM, FX5200TV, no remote yet!)

Now I am working on the remote - perhaps the SnapStream FireFly since I would like an RF remote.

»

Quote:There is nothing like

Submitted by d00dtv on August 5, 2006 - 4:28pm.

Quote:

There is nothing like posting a question to engage the brain -- in my haste to bring up all the frontend machines I failed to create /etc/resolve.conf so I had no DNS info, sigh! I obviously paid more attention doing the backend.

This seems to be a system specific problem on the resolve.conf. I have never had this problem or been able to reproduce it. Not sure why it does this as it's supposed to enter this info for you when you give your ip address in setup. But glad it works now.

"Please ignore the man behind the curtain"
Dennis

—

"Please ignore the man behind the curtain"
Dennis

»