Comments on: Running MythWeb on a separate machine from mythbackend http://www.happyassassin.net/2010/01/29/running-mythweb-on-a-separate-machine-from-mythbackend/ Fri, 30 Jul 2010 16:17:43 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: adamw http://www.happyassassin.net/2010/01/29/running-mythweb-on-a-separate-machine-from-mythbackend/comment-page-1/#comment-1127 adamw Fri, 29 Jan 2010 19:43:08 +0000 http://www.happyassassin.net/?p=907#comment-1127 Right. The only issue with that is that mythtv's own database access seems a bit finicky; mythbackend always seems to connect to 'mythtv'@'localhost' for me even if i tell it something different via mythtv-setup. Not quite sure what's going on there. So I thought it best to make sure access through that channel definitely works :) thanks for the pointer, though. Right. The only issue with that is that mythtv’s own database access seems a bit finicky; mythbackend always seems to connect to ‘mythtv’@'localhost’ for me even if i tell it something different via mythtv-setup. Not quite sure what’s going on there. So I thought it best to make sure access through that channel definitely works :) thanks for the pointer, though.

]]> By: <img src='http://www.happyassassin.net/wordpress/wp-content/plugins/rpx/images/openid.png'/> palintech http://www.happyassassin.net/2010/01/29/running-mythweb-on-a-separate-machine-from-mythbackend/comment-page-1/#comment-1126 palintech Fri, 29 Jan 2010 19:03:39 +0000 http://www.happyassassin.net/?p=907#comment-1126 Hi Adam, a bit of a hack for the mysql bind problem is to use the interface ip, and use it for the apps at localhost instead of 127.0.0.1 which does not support using a mysql socket. Es. bind-address=172.16.1.2 mysql will listen on 172.16.1.2 only, but on the 172.16.1.2 host you can point to 172.16.1.2 instead of 127.0.0.1 (you must adjust grants for users too). Note that you can login using localhost with mysql command line if you use sockets (mysql client does that by default): this way you don't lose root access on localhost. Hi Adam, a bit of a hack for the mysql bind problem is to use the interface ip, and use it for the apps at localhost instead of 127.0.0.1 which does not support using a mysql socket.

Es. bind-address=172.16.1.2

mysql will listen on 172.16.1.2 only, but on the 172.16.1.2 host you can point to 172.16.1.2 instead of 127.0.0.1 (you must adjust grants for users too).

Note that you can login using localhost with mysql command line if you use sockets (mysql client does that by default): this way you don’t lose root access on localhost.

]]>