Opened 2 years ago

Closed 2 years ago

Last modified 17 months ago

#13102 closed Bug Report - General (Abandoned)

mythweb 0.28 fails after reinstallation !!NoTrans: MasterServerIP or MasterServerPort not found!

Reported by: keepitsimpleengineer@… Owned by: Peter Bennett
Priority: minor Milestone: unknown
Component: MythTV - General Version: 0.28.0
Severity: medium Keywords: mythweb
Cc: Ticket locked: no

Description

Error message: Fatal Error / !NoTrans: MasterServerIP or MasterServerPort? not found! You may need to check your mythweb.conf file or re-run mythtv-setup!!

Note: /etc/apache2/sites-available/mythweb.conf point to /var/www/html/mythweb/data

# ls /var/www/html/mythweb
classes        data        includes  modules              mythweb.conf.lighttpd  mythweb.php  skins
configuration  Dockerfile  js        mythweb.conf.apache  mythweb.conf.nginx     mythweb.pl   tests

Backend server is KISE-055 / 192.168.0.55

before reinstall /etc/apache2/sites-available/mythweb.conf point to /var/www/mythweb/data

# ls /var/www/mythweb
classes        data        includes  modules              mythweb.conf.lighttpd  mythweb.php  skins
configuration  Dockerfile  js        mythweb.conf.apache  mythweb.conf.nginx     mythweb.pl   tests

Attachments (1)

backtrace.txt (5.3 KB) - added by keepitsimpleengineer@… 2 years ago.
backtrace

Download all attachments as: .zip

Change History (10)

Changed 2 years ago by keepitsimpleengineer@…

Attachment: backtrace.txt added

backtrace

comment:1 Changed 2 years ago by Peter Bennett

It looks like it cannot connect to your database. The database settings should be in the mythweb.conf file. Perhaps there have been lost or reverted to incorrect default values.

comment:2 Changed 2 years ago by keepitsimpleengineer@…

From mythweb.conf

       # This is unneeded due to the upnp setup via the backend
        #
        setenv db_server        "localhost"
        setenv db_name          "mythconverg"
        setenv db_login         "mythtv"
        setenv db_password      "correct password"

From 0.28 client successfully connected to database:

Hostname: 192.168.0.55

Port: 3306

Database name: mythconverg

User: mythtv

Password: correct password

Looks to be correct..?

comment:3 Changed 2 years ago by sphery

In MySQL/MariaDB, there's a difference between localhost and 192.168.0.55 hostnames when permissions are granted. You almost definitely need to fix your MySQL server permissions/grants. Please ask for help on the mythtv-users list and/or try using db_server "192.168.0.55".

comment:4 Changed 2 years ago by Peter Bennett

Owner: set to Peter Bennett
Status: newassigned

Let us know if this has solved the problem.

comment:5 Changed 2 years ago by Peter Bennett

Status: assignedinfoneeded

comment:6 Changed 2 years ago by Peter Bennett

Resolution: Abandoned
Status: infoneededclosed

comment:7 Changed 23 months ago by Stuart Auchterlonie

Milestone: needs_triageunknown

comment:8 Changed 23 months ago by james@…

This is not a database connection issue. I just reproduced this error on a botched upgrade and fixed it.

My problem was that my version of mythweb files in /usr/share/mythtv/bindings/php were not compatible with the current version of myth I was running.

I fixed the above error by editing the MythBackend?.php in the above folder and simply assigning my host and port variables.

But then further errors occured which pointed me to a version problem (error with MYTH_PROTO VERSION).

I then simply downloaded the proper version of mythtv tar file from the repo and replaced my bindings/php folder with that in the tar and it worked fine.

I hope this helps others that find this in a google search.

comment:9 Changed 17 months ago by Peter Bennett

Owner: changed from Peter Bennett to Peter Bennett
Note: See TracTickets for help on using tickets.