Opened 14 years ago

Closed 14 years ago

#1806 closed defect (invalid)

mythbackend should provide full path name when it fails to find mysql.txt

Reported by: indulis@… Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: mythtv Version:
Severity: low Keywords:
Cc: Ticket locked: no


Was having problems getting mythbackend to start during boot sequence (from /etc/init.d via /etc/rc2.d script).

Troubleshooting was a nightmare, as the mythbackend message that complained that it couldn't find mysql.txt did not give the full path name. Where was it looking for mysql.txt? /usr/local? /etc? /usr/share/mythtv? It'd really help if the mythbackend log message gave the full directory and file name.

2006-05-13 11:11:14.644 Using runtime prefix = /usr/local
2006-05-13 11:11:14.722 Unable to read configuration file mysql.txt
2006-05-13 11:11:14.722 Trying to create a basic mysql.txt file
2006-05-13 11:11:14.723 Could not create //.mythtv

More details

Recompiled mythtv 0.19 from source (9926), mythbackend would start OK when run after boot completed, but would fail when run from inittab. The recompiler was done using the std file prefix /usr/local. I had previously been running debian (Ubuntu) packages and mythbackend started correctly.

The problem was resolved by setting HOME set in the startup script to point to mythtv user's home directory. Troubleshooting made difficult as mythtbackend log messages do not include full path name for the mysql.txt it is looking for.

Change History (1)

comment:1 Changed 14 years ago by Isaac Richards

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.