Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#7557 closed defect (invalid)

New Mythweb won't go past masterserverip error

Reported by: noah.swint@… Owned by: Rob Smith
Priority: minor Milestone: 0.22
Component: Plugin - MythWeb Version: 0.22
Severity: high Keywords:
Cc: Ticket locked: yes


I can't access mythweb any more due to the MasterserverIP error

select * from settings where value like 'MasterS%' order by value; +------------------+-------------+----------+ | value | data | hostname | +------------------+-------------+----------+ | MasterServerIP | | NULL | | MasterServerPort? | 6543 | NULL | +------------------+-------------+----------+

datetime: 2009-11-12 19:18:58 (EST) errornum: 256

error type: User Error

error string: MasterServerIP or MasterServerPort? not found! You mayneed to check your settings.php file or re-run mythtv-setup

filename: /var/www/html/mythweb/classes/MythBackend.php

error line: 45



file: /var/www/html/mythweb/classes/MythBackend.php line: 45


function: trigger_error

type: args: Array


[0] => MasterServerIP or MasterServerPort? not found! You mayneed to check your settings.php file or re-run mythtv-setup [1] => 256


file: /var/www/html/mythweb/includes/init.php line: 72

class: MythBackend?

function: find

args: Array ( ) file: /var/www/html/mythweb/mythweb.php line: 20 class:

function: require_once

type: args: Array


[0] => /var/www/html/mythweb/includes/init.php


Change History (4)

comment:1 Changed 11 years ago by Dibblah

Resolution: invalid
Status: newclosed

The configuration of Mythweb is done through configuration files, not the database. The version of Mythweb you are running is also not 0.22.

comment:2 Changed 11 years ago by anonymous

rpm -qa mythweb mythweb-0.22-220.fc11.i586

comment:3 Changed 11 years ago by Rik van Mierlo <rik@…>

I have the same problem, using Fedora 10, mythtv from atrpms, version 0.22-223

Somehow, the setting function does not work or is not called correctly from MythBackend?.php. Changing "setting" to "get_backend_setting" at least gets you into mythweb.

This is probably not the correct way to fix this (I'm not a programmer). If the configuration is done by file(?), than some file that was not required in 0.21 probably now is or should contain something that was previously not needed.

diff for MythBackend?.php:

<             $host = get_backend_setting('MasterServerIP');
<             $port = get_backend_setting('MasterServerPort');
>             $host = setting('MasterServerIP');
>             $port = setting('MasterServerPort');



comment:4 Changed 11 years ago by sphery

Ticket locked: set

Likely fixed by [22983] (which fixed #7755 ). Eventually we will likely backport that fix to 0.22-fixes. Until then, users can do so themselves. Further comments on the mailing lists, please.

Note: See TracTickets for help on using tickets.