[02:21] <lunaphyte> !help
[02:21] <Zinn> !help For a  complete list of my knowledge visit: http://www.baablogic.net/Zinn.cgi  Other available commands: !status, !about, !bug [bug_number].
[02:32] <lunaphyte> hi.  i've done a backend installation on one computer, and am doing a frontend installation on another.  i'm having trouble figuring out how to point the frontend at the backend.  the frontend installation process asks for a security pin, but no hostname.  this must be something silly i'm overlooking, but what?
[02:58] <tgm4883> lunaphyte, did you set a security PIN on the backend?
[02:59] <lunaphyte> yes, under mythtv backend setup -> general.
[03:00] <lunaphyte> i put this pin in the text field on the frontend and click test, and after a few moments it complains about not being able to connect to the database [iirc].
[03:00] <lunaphyte> but i'm wondering how it would know where to find the backend.
[03:01] <tgm4883> lunaphyte, did you run mythbuntu-control-centre on the backend and activate the mythtv service?
[03:01] <tgm4883> lunaphyte, it automatically detects backend machiens on the network
[03:03] <lunaphyte> oh, hmm. i thought mythbuntu control centre was only for frontend computers.
[03:03] <lunaphyte> i'm trying it just now, and the remote connectivity test is failing.
[03:05] <tgm4883> On the services tab did you enable the mythtv service?
[03:07] <lunaphyte> i see ssh, samba, nfs, and vnc [those are enabled aside from vnc], but no mythtv service - here is what is listening: http://pastebin.com/Crt50EtH
[03:07] <Zinn> [pastebin.com] apache2 1195 root 3u IPv4 8087 0t0 TCP *:80 (LISTEN) apache - Pastebin.com
[03:10] <tgm4883> that is from your mythtv master backend machine?
[03:10] <lunaphyte> yes
[03:13] <tgm4883> hmm
[03:15] <tgm4883> lunaphyte, sorry its' on the mysql tab
[03:17] <lunaphyte> oh, ok.  here's my mysql tab: http://oi43.tinypic.com/9ss7pt.jpg
[03:17] <Zinn> [oi43.tinypic.com] N/A
[03:18] <lunaphyte> that's where i did the test connection that didn't work
[03:18] <tgm4883> lunaphyte, ok, you didn't set the pin to 0000 did you?
[03:18] <lunaphyte> i didn't.  it's 5891
[03:19] <tgm4883> ok, and you hit apply after you turned on the mysql service?
[03:19] <lunaphyte> err, 5819, rather
[03:19] <tgm4883> in MCC
[03:20] <lunaphyte> http://oi44.tinypic.com/b8rec2.jpg
[03:21] <Zinn> [oi44.tinypic.com] N/A
[03:21] <lunaphyte> i believe so, yes.  i'll try disabling it and then re-enabling it.
[03:21] <tgm4883> ok
[03:23] <lunaphyte> after disabling it, i see in the output of lsof: mysqld    5773      mysql   10u  IPv4  27275      0t0  TCP 127.0.0.1:3306 (LISTEN)
[03:23] <lunaphyte> and after re-enabling it, i see: mysqld    5984      mysql   10u  IPv4  28121      0t0  TCP *:3306 (LISTEN)
[03:23] <tgm4883> lunaphyte, that looks better
[03:24] <lunaphyte> mysql was *:3306 in my earlier pastebin too though.
[03:24] <tgm4883> hmm, so it was
[03:25] <lunaphyte> the test connection still fails.
[03:25] <lunaphyte> maybe i'll try 0000
[03:25] <tgm4883> the backend is still running and listening for connections?
[03:28] <lunaphyte> i believe so, yes: http://pastebin.com/heaJsxbg
[03:28] <Zinn> [pastebin.com] # lsof -nPi | grep -iF myth mythbacke 6226 mythtv 7u IPv4 29137 0 - Pastebin.com
[03:28] <lunaphyte> let me see if i can connect from another host with telnet
[03:29] <lunaphyte> yes, i can connect to both ports from another computer
[03:29] <lunaphyte> open the socket, anyway.
[03:29] <tgm4883> hmm ok
[03:29] <tgm4883> what happens when you start mythfrontend
[03:29] <lunaphyte> on the backend?
[03:30] <tgm4883> if you have one on the backend, yes
[03:30] <tgm4883> if not, then on the other machine
[03:30] <lunaphyte> i have it only on the other computer at the moment.  one moment, i'll try.
[03:32] <lunaphyte> oh - that's what it was.  on the frontend, i was still in the installation phase.  it was asking for a pin, and when i supplied the pin and clicked test connection, it said "could not find database login credentials", and would not allow me to click continue.
[03:32] <lunaphyte> however, trying again just now, it still complained with the same error, but it allowed to me click continue anyway
[03:33] <tgm4883> ah ok
[03:34] <lunaphyte> what protocol/method is used to automatically detect backend computers?
[03:35] <tgm4883> IIRC it's AVAHI
[03:41] <lunaphyte> oh, mdns and zeroconf, etc?
[03:43] <tgm4883> yea
=== dduffey is now known as dduffey_afk
=== dduffey_afk is now known as dduffey
=== dduffey is now known as dduffey_test
[19:57] <sharkmonkey> How do I shutdown?
[20:03] <superm1> sharkmonkey: in mythtv?
[20:03] <superm1> hit esc from the frontend and pick shutdown
[20:03] <superm1> (or if on a remote, back or stop == esc)
[20:04] <sharkmonkey> From the window manager/desktop environment
[20:05] <sharkmonkey> Not seeing a shutdown option
[20:06] <sharkmonkey> Ok, found logout. And that brought up an option to shutdown
[20:24] <rhpot1991> sudo halt from a terminal works as well
[20:29] <sharkmonkey> rhpot1991: Not without a keyboard. :/
[20:30] <dekarl> ssh in and "sudo shutdown now"
[20:30] <dekarl> oh, I got a good one "push the power button" works well, too ;)
[20:33] <rhpot1991> ssh++
[20:33] <rhpot1991> theoretically you can use the onscreen keyboard if you really feel like doing that to yourself too
[20:39] <sharkmonkey> I did actually try the power button :). No reaction. I could hold it down, but that wouldn't be a clean shutdown. Might as well pull the cord at that point.
[20:41] <dekarl> sharkmonkey: oh, my diskless mythbuntu frontend cleanly shuts down as soon a I gently hit the button
[20:45] <dekarl> have you got a /etc/acpi/powerbtn.sh? or does the end of dmesg give any hint?
[20:54] <superm1> yeah it's supposed to react to the ACPI event of hitting the button, that's a bit weird
[20:55] <dekarl> seems like the shutdown is not executed if any power management daemon is found running
[20:56] <dekarl> so that these can take over (and offer stuff like "want to safe your work?")
[21:01] <superm1> well there isn't one seeded in 11.10
[21:01] <superm1> hmm
[21:01] <superm1> but if someone has like gnome-power-manager installed on their own accord, i suppose that would happen