LinHES Forums :: View topic - mac osx intel frontend problems.. anyone successful?

MythFrontend.app/Contents/MacOS/MythFrontend -v all

sudo tcpdump host 10.0.0.5

DBHostName=192.168.1.106
DBPort=6543
DBUserName=mythtv
DBPassword=mythtv
DBName=mythconverg
DBType=QMYSQL3

# Set the following if you want to use something other than the
# machine's real hostname for identifying settings in the database.
# This is useful if your hostname changes often, as otherwise
# you'll need to reconfigure mythtv (or futz with the DB) every time.
# TWO HOSTS MUST NOT USE THE SAME VALUE
#
#LocalHostName=my-unique-identifier-goes-here

# If you want your frontend to be able to wake your MySQL server
# using WakeOnLan, have a look at the following settings:
#
# Set the time the frontend waits (in seconds) between reconnect tries.
# This should be the rough time your MySQL server needs for startup
#WOLsqlReconnectWaitTime=0
#
#

tcpdump: listening on en0, link-type EN10MB (Ethernet), capture size 96 bytes
16:52:15.259906 IP (tos 0x0, ttl 64, id 35623, offset 0, flags [DF], proto: TCP (6), length: 64, bad cksum 0 (->2b69)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: S, cksum 0x845a (incorrect (-> 0x671c), 471959475:471959475(0) win 65535 <mss 1460,nop,wscale 0,nop,nop,timestamp 910460410 0,sackOK,eol>
16:52:15.260163 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 60) 192.168.1.106.lds-distrib > 192.168.1.109.53787: S, cksum 0xaf26 (correct), 3517135507:3517135507(0) ack 471959476 win 5792 <mss 1460,sackOK,timestamp 246912852 910460410,nop,wscale 7>
16:52:15.260216 IP (tos 0x0, ttl 64, id 35624, offset 0, flags [DF], proto: TCP (6), length: 52, bad cksum 0 (->2b74)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: ., cksum 0x844e (incorrect (-> 0xf492), ack 1 win 65535 <nop,nop,timestamp 910460410 246912852>

16:54:09.944895 IP (tos 0x8, ttl 64, id 35681, offset 0, flags [DF], proto: TCP (6), length: 52, bad cksum 0 (->2b33)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: F, cksum 0x844e (incorrect (-> 0xf3ac), 1:1(0) ack 1 win 65535 <nop,nop,timestamp 910460639 246912852>
16:54:09.945244 IP (tos 0x0, ttl 64, id 44480, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.106.lds-distrib > 192.168.1.109.53787: F, cksum 0x3369 (correct), 1:1(0) ack 2 win 46 <nop,nop,timestamp 247027559 910460639>
16:54:10.146868 IP (tos 0x0, ttl 64, id 44481, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.106.lds-distrib > 192.168.1.109.53787: F, cksum 0x329f (correct), 1:1(0) ack 2 win 46 <nop,nop,timestamp 247027761 910460639>
16:54:10.146919 IP (tos 0x8, ttl 64, id 35682, offset 0, flags [DF], proto: TCP (6), length: 52, bad cksum 0 (->2b32)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: ., cksum 0x844e (incorrect (-> 0x32cc), ack 2 win 65535 <nop,nop,timestamp 910460640 247027761>

joebobs-computer:~ joebob$ /Applications/MythFrontend.app/Contents/MacOS/MythFrontend -v all
2007-08-06 16:52:15.232 Using runtime prefix = /Applications/MythFrontend.app/Contents/Resources
2007-08-06 16:52:15.241 New DB connection, total: 1
^C
joebobs-computer:~ joebob$

Last login: Mon Aug 6 16:34:15 on ttyp2
Welcome to Darwin!
joebobs-computer:~ joebob$ /Applications/MythFrontend.app/Contents/
Frameworks MacOS Resources
joebobs-computer:~ joebob$ /Applications/MythFrontend.app/Contents/MacOS/MythFrontend -v all
2007-08-06 16:44:50.116 Using runtime prefix = /Applications/MythFrontend.app/Contents/Resources
2007-08-06 16:44:50.125 New DB connection, total: 1
2007-08-06 16:44:50.144 Unable to connect to database!
2007-08-06 16:44:50.145 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.1.106' (61)

QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
2007-08-06 16:44:50.201 DB Error (KickDatabase):
Query was:
SELECT NULL;
No error type from QSqlError? Strange...
2007-08-06 16:44:50.255 Unable to connect to database!
2007-08-06 16:44:50.256 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.1.106' (61)

QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
2007-08-06 16:44:50.309 DB Error (KickDatabase):
Query was:
SELECT NULL;
No error type from QSqlError? Strange...
2007-08-06 16:44:50.361 Database not open while trying to load setting: GuiVidModeResolution
2007-08-06 16:44:50.364 Unable to connect to database!
2007-08-06 16:44:50.365 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.1.106' (61)

QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
2007-08-06 16:44:50.418 DB Error (KickDatabase):
Query was:
SELECT NULL;
No error type from QSqlError? Strange...
2007-08-06 16:44:50.469 Database not open while trying to load setting: GuiVidModeWidth
2007-08-06 16:44:50.472 Unable to connect to database!
2007-08-06 16:44:50.473 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.1.106' (61)

QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
2007-08-06 16:44:50.526 DB Error (KickDatabase):
Query was:
SELECT NULL;
No error type from QSqlError? Strange...
2007-08-06 16:44:50.577 Database not open while trying to load setting: GuiVidModeHeight
2007-08-06 16:44:50.620 Unable to connect to database!
2007-08-06 16:44:50.620 Driver error was [1/2003]:
QMYSQL3: Unable to connect
Database error was:
Can't connect to MySQL server on '192.168.1.106' (61)

16:52:15.259906 IP (tos 0x0, ttl 64, id 35623, offset 0, flags [DF], proto: TCP (6), length: 64, bad cksum 0 (->2b69)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: S, cksum 0x845a (incorrect (-> 0x671c), 471959475:471959475(0) win 65535 <mss 1460,nop,wscale 0,nop,nop,timestamp 910460410 0,sackOK,eol>
16:52:15.260163 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 60) 192.168.1.106.lds-distrib > 192.168.1.109.53787: S, cksum 0xaf26 (correct), 3517135507:3517135507(0) ack 471959476 win 5792 <mss 1460,sackOK,timestamp 246912852 910460410,nop,wscale 7>
16:52:15.260216 IP (tos 0x0, ttl 64, id 35624, offset 0, flags [DF], proto: TCP (6), length: 52, bad cksum 0 (->2b74)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: ., cksum 0x844e (incorrect (-> 0xf492), ack 1 win 65535 <nop,nop,timestamp 910460410 246912852>

Author:	jfkjfk2 [ Sun Aug 05, 2007 8:01 pm ]
Post subject:	mac osx intel frontend problems.. anyone successful?
I've dl a binary frontend for intel mac osx.. When I run it it I go through the setup pages, click finish and it disappears and stops responding.. (not responding in force quit dialog) Im pretty sure it's seeing the server because when I enter incorrect values for the server setup quits, and then brings me back to setup pages on the next launch... I've tried on Macbook pro 2gig duo core w 2gigs ram and mac pro 2.6 and 3 gigs ram x1900 video tx jfkjfk

Author:	mythingpersons [ Sun Aug 05, 2007 10:23 pm ]
Post subject:
Put me down as one for success. We have it running on a 20" imac, 1.83MHz intel core 2 duo etc. It has been a while since the installation but we did not have to go through any hoops to get the thing working.

Author:	nigelpearson [ Mon Aug 06, 2007 3:42 am ]
Post subject:	Re: mac osx intel frontend problems.. anyone successful?
jfkjfk2 wrote: go through the setup pages, click finish and it disappears and stops responding.. (not responding in force quit dialog) Hmmm. Are you saying that Control-Option-Escape doesn't bring up the "Force Quit Applications" window? Or that Quit from MythFrontend.app's menu bar does nothing? If the first, try Apple-Tab to go to a different application first. The second is to be expected if the client is busy doing something more important (like desperately trying to connect to the backend). Now, onto the the cause of the hang; First thing is to check for console output. Open /Applications/Console.app and look for any error messages from the Frontend. Next, is the Frontend in a busy loop? Open /Applications/Utilities/Activity Monitor.app and make sure that the CPU (or one of the cores) isn't stuck at 100% percent. Last, is your networking set up correctly? Can you ping the backend's IP address? Can you tcpdump any traffic being sent to/from the backend?

Author:	jfkjfk2 [ Mon Aug 06, 2007 1:50 pm ]
Post subject:	Re: mac osx intel frontend problems.. anyone successful?
nigelpearson wrote: Hmmm. Are you saying that Control-Option-Escape doesn't bring up the "Force Quit Applications" window? C-Opt_Esc will brng up the "Force Quit App" Window.. And it shows mythfrontend as not responding. Quote: Or that Quit from MythFrontend.app's menu bar does nothing? If the first, try Apple-Tab to go to a different application first. After the setup window disappears, I never seen anything else of MythFronted except it's still running.. (no windows no menue no nothing) I can apple tab away, and back.. but when I come back I don't see anything, exept I lose focus of the app I tabbed away from.. No menu or anything.. Quote: The second is to be expected if the client is busy doing something more important (like desperately trying to connect to the backend). Quote: Now, onto the the cause of the hang; First thing is to check for console output. Open /Applications/Console.app and look for any error messages from the Frontend . Console showed these two lines upon running... 2007-08-06 12:38:29.683 Using runtime prefix = /Applications/MythFrontend.app/Contents/Resources 2007-08-06 12:38:29.792 New DB connection, total: 1 Quote: Next, is the Frontend in a busy loop? Open /Applications/Utilities/Activity Monitor.app and make sure that the CPU (or one of the cores) isn't stuck at 100% percent. Looks like it's at 0%, but is show in red (Not responding) Quote: Last, is your networking set up correctly? Can you ping the backend's IP address? yes I can ping the backend... Quote: Can you tcpdump any traffic being sent to/from the backend? I don't know how to do this.. Now.. I just finished Dling the 20fixes version of the frontend, and it actually booted up... except now I'm getting a Protocol Version mismatch... 2007-08-06 12:51:08.981 Protocol version mismatch (frontend=31,backend=35) but at least it's getting somewhere... any ideas? My backend is patched for NA DN, but I don't think that should do anything?? my backend is version from svn 14135 tx.. jfkjfk

Author:	nigelpearson [ Mon Aug 06, 2007 5:15 pm ]
Post subject:	Re: mac osx intel frontend problems.. anyone successful?
jfkjfk2 wrote: Console showed these two lines upon running... 2007-08-06 12:38:29.683 Using runtime prefix = /Applications/MythFrontend.app/Contents/Resources 2007-08-06 12:38:29.792 New DB connection, total: 1 OK, so this version is stuck waiting to talk to the backend. This usually only happens when the wrong IP address was entered (e.g. trying to talk to 100.0.0.5 instead of 10.0.0.5). If it is not routable, the timeouts are huge. Leave it about 10 minutes, and come back to it? If that reveals nothing, try running the frontend with verbose output. In a Terminal window: Code: MythFrontend.app/Contents/MacOS/MythFrontend -v all Quote: Quote: Can you tcpdump any traffic being sent to/from the backend? I don't know how to do this.. In a Terminal window, do: Code: sudo tcpdump host 10.0.0.5 Quote: my backend is version from svn 14135 Should have no effect on the database interaction. Note that is on the trunk branch of the MythTV code, so a 0-20 fixes frontend will not be able to talk to it. But you probably already realise that.

LinHES Forums http://forums.linhes.org/

mac osx intel frontend problems.. anyone successful? http://forums.linhes.org/viewtopic.php?f=6&t=16050	Page 1 of 2

Author:	jfkjfk2 [ Mon Aug 06, 2007 5:54 pm ]
Post subject:
Here's my mysql.txt file on the frontend -------------------------------------------- Code: DBHostName=192.168.1.106 DBPort=6543 DBUserName=mythtv DBPassword=mythtv DBName=mythconverg DBType=QMYSQL3 # Set the following if you want to use something other than the # machine's real hostname for identifying settings in the database. # This is useful if your hostname changes often, as otherwise # you'll need to reconfigure mythtv (or futz with the DB) every time. # TWO HOSTS MUST NOT USE THE SAME VALUE # #LocalHostName=my-unique-identifier-goes-here # If you want your frontend to be able to wake your MySQL server # using WakeOnLan, have a look at the following settings: # # Set the time the frontend waits (in seconds) between reconnect tries. # This should be the rough time your MySQL server needs for startup #WOLsqlReconnectWaitTime=0 # # Here's the tcpdmump of sudo tcpdump -v host 192.168.1.106 192.168.1.106 is the backend server.. ===================================== Code: tcpdump: listening on en0, link-type EN10MB (Ethernet), capture size 96 bytes 16:52:15.259906 IP (tos 0x0, ttl 64, id 35623, offset 0, flags [DF], proto: TCP (6), length: 64, bad cksum 0 (->2b69)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: S, cksum 0x845a (incorrect (-> 0x671c), 471959475:471959475(0) win 65535 <mss 1460,nop,wscale 0,nop,nop,timestamp 910460410 0,sackOK,eol> 16:52:15.260163 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 60) 192.168.1.106.lds-distrib > 192.168.1.109.53787: S, cksum 0xaf26 (correct), 3517135507:3517135507(0) ack 471959476 win 5792 <mss 1460,sackOK,timestamp 246912852 910460410,nop,wscale 7> 16:52:15.260216 IP (tos 0x0, ttl 64, id 35624, offset 0, flags [DF], proto: TCP (6), length: 52, bad cksum 0 (->2b74)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: ., cksum 0x844e (incorrect (-> 0xf492), ack 1 win 65535 <nop,nop,timestamp 910460410 246912852> I let it sit and nothing else until I ctrl-c the backend ( I tried option-tabbing to the frontend but nothing happen) Hitting ctl-c get's this dump Code: 16:54:09.944895 IP (tos 0x8, ttl 64, id 35681, offset 0, flags [DF], proto: TCP (6), length: 52, bad cksum 0 (->2b33)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: F, cksum 0x844e (incorrect (-> 0xf3ac), 1:1(0) ack 1 win 65535 <nop,nop,timestamp 910460639 246912852> 16:54:09.945244 IP (tos 0x0, ttl 64, id 44480, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.106.lds-distrib > 192.168.1.109.53787: F, cksum 0x3369 (correct), 1:1(0) ack 2 win 46 <nop,nop,timestamp 247027559 910460639> 16:54:10.146868 IP (tos 0x0, ttl 64, id 44481, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.106.lds-distrib > 192.168.1.109.53787: F, cksum 0x329f (correct), 1:1(0) ack 2 win 46 <nop,nop,timestamp 247027761 910460639> 16:54:10.146919 IP (tos 0x8, ttl 64, id 35682, offset 0, flags [DF], proto: TCP (6), length: 52, bad cksum 0 (->2b32)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: ., cksum 0x844e (incorrect (-> 0x32cc), ack 2 win 65535 <nop,nop,timestamp 910460640 247027761> all I get from running the frontend is Code: joebobs-computer:~ joebob$ /Applications/MythFrontend.app/Contents/MacOS/MythFrontend -v all 2007-08-06 16:52:15.232 Using runtime prefix = /Applications/MythFrontend.app/Contents/Resources 2007-08-06 16:52:15.241 New DB connection, total: 1 ^C joebobs-computer:~ joebob$ Here's what happens when the backend is off, but the backend computer is running.. ============================= Code: Last login: Mon Aug 6 16:34:15 on ttyp2 Welcome to Darwin! joebobs-computer:~ joebob$ /Applications/MythFrontend.app/Contents/ Frameworks MacOS Resources joebobs-computer:~ joebob$ /Applications/MythFrontend.app/Contents/MacOS/MythFrontend -v all 2007-08-06 16:44:50.116 Using runtime prefix = /Applications/MythFrontend.app/Contents/Resources 2007-08-06 16:44:50.125 New DB connection, total: 1 2007-08-06 16:44:50.144 Unable to connect to database! 2007-08-06 16:44:50.145 Driver error was [1/2003]: QMYSQL3: Unable to connect Database error was: Can't connect to MySQL server on '192.168.1.106' (61) QSqlQuery::exec: database not open QSqlQuery::exec: database not open 2007-08-06 16:44:50.201 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... 2007-08-06 16:44:50.255 Unable to connect to database! 2007-08-06 16:44:50.256 Driver error was [1/2003]: QMYSQL3: Unable to connect Database error was: Can't connect to MySQL server on '192.168.1.106' (61) QSqlQuery::exec: database not open QSqlQuery::exec: database not open 2007-08-06 16:44:50.309 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... 2007-08-06 16:44:50.361 Database not open while trying to load setting: GuiVidModeResolution 2007-08-06 16:44:50.364 Unable to connect to database! 2007-08-06 16:44:50.365 Driver error was [1/2003]: QMYSQL3: Unable to connect Database error was: Can't connect to MySQL server on '192.168.1.106' (61) QSqlQuery::exec: database not open QSqlQuery::exec: database not open 2007-08-06 16:44:50.418 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... 2007-08-06 16:44:50.469 Database not open while trying to load setting: GuiVidModeWidth 2007-08-06 16:44:50.472 Unable to connect to database! 2007-08-06 16:44:50.473 Driver error was [1/2003]: QMYSQL3: Unable to connect Database error was: Can't connect to MySQL server on '192.168.1.106' (61) QSqlQuery::exec: database not open QSqlQuery::exec: database not open 2007-08-06 16:44:50.526 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... 2007-08-06 16:44:50.577 Database not open while trying to load setting: GuiVidModeHeight 2007-08-06 16:44:50.620 Unable to connect to database! 2007-08-06 16:44:50.620 Driver error was [1/2003]: QMYSQL3: Unable to connect Database error was: Can't connect to MySQL server on '192.168.1.106' (61) ============== the same stuff goes on for a while, but the frontend does eventually come up.. It just can see the backend.. I've got a frontend built from 14137, that's the closest I could find.. but should work... They're both protocol 35... Any ideas? Tx... jfkjfk

Author:	jfkjfk2 [ Mon Aug 06, 2007 6:24 pm ]
Post subject:
so I installed the 20.fixes version and the backend and frontend work fine.. It's just I want some features of the new SVN, so apparently 14135 has some issues.. Im going to dl the lastest svn and see if that works.. jfkjfk

Author:	jfkjfk [ Mon Aug 06, 2007 8:07 pm ]
Post subject:
Used cure 34150 and it's still a no go... When I connected with 20.fixes I wasn't able to play back any recordings.. it gave me an error saying the files didn't exist... Do I have to have a samba share with the frontend? Or is it probably just an incompatible db since I stepped back so far.. tx.. jfkjfk

Author:	jfkjfk [ Mon Aug 06, 2007 8:14 pm ]
Post subject:
Used cure 34150 and it's still a no go... When I connected with 20.fixes I wasn't able to play back any recordings.. it gave me an error saying the files didn't exist... Do I have to have a samba share with the frontend? Or is it probably just an incompatible db since I stepped back so far.. tx.. jfkjfk

Author:	nigelpearson [ Mon Aug 06, 2007 8:27 pm ]
Post subject:
Code: 16:52:15.259906 IP (tos 0x0, ttl 64, id 35623, offset 0, flags [DF], proto: TCP (6), length: 64, bad cksum 0 (->2b69)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: S, cksum 0x845a (incorrect (-> 0x671c), 471959475:471959475(0) win 65535 <mss 1460,nop,wscale 0,nop,nop,timestamp 910460410 0,sackOK,eol> 16:52:15.260163 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 60) 192.168.1.106.lds-distrib > 192.168.1.109.53787: S, cksum 0xaf26 (correct), 3517135507:3517135507(0) ack 471959476 win 5792 <mss 1460,sackOK,timestamp 246912852 910460410,nop,wscale 7> 16:52:15.260216 IP (tos 0x0, ttl 64, id 35624, offset 0, flags [DF], proto: TCP (6), length: 52, bad cksum 0 (->2b74)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: ., cksum 0x844e (incorrect (-> 0xf492), ack 1 win 65535 <nop,nop,timestamp 910460410 246912852> Hmmm. Bad checksum is a strange thing to see. I am doing some testing now to try and reproduce this. Quote: Here's what happens when the backend is off, but the backend computer is running.. ... QMYSQL3: Unable to connect Database error was: Can't connect to MySQL server on '192.168.1.106' (61) I assume you mean both backend off and Mysql shut down? I am at a loss. An older frontend binary works, but a newer one fails to connect at all. Very weird.

Author:	nigelpearson [ Mon Aug 06, 2007 8:29 pm ]
Post subject:
Code: 16:52:15.259906 IP (tos 0x0, ttl 64, id 35623, offset 0, flags [DF], proto: TCP (6), length: 64, bad cksum 0 (->2b69)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: S, cksum 0x845a (incorrect (-> 0x671c), 471959475:471959475(0) win 65535 <mss 1460,nop,wscale 0,nop,nop,timestamp 910460410 0,sackOK,eol> 16:52:15.260163 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 60) 192.168.1.106.lds-distrib > 192.168.1.109.53787: S, cksum 0xaf26 (correct), 3517135507:3517135507(0) ack 471959476 win 5792 <mss 1460,sackOK,timestamp 246912852 910460410,nop,wscale 7> 16:52:15.260216 IP (tos 0x0, ttl 64, id 35624, offset 0, flags [DF], proto: TCP (6), length: 52, bad cksum 0 (->2b74)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: ., cksum 0x844e (incorrect (-> 0xf492), ack 1 win 65535 <nop,nop,timestamp 910460410 246912852> Hmmm. Bad checksum is a strange thing to see. I am doing some testing now to try and reproduce this. Quote: Here's what happens when the backend is off, but the backend computer is running.. ... QMYSQL3: Unable to connect Database error was: Can't connect to MySQL server on '192.168.1.106' (61) I assume you mean both backend off and Mysql shut down? I am at a loss. An older frontend binary works, but a newer one fails to connect at all. Very weird.

Author:	nigelpearson [ Mon Aug 06, 2007 9:22 pm ]
Post subject:
Code: 16:52:15.259906 IP (tos 0x0, ttl 64, id 35623, offset 0, flags [DF], proto: TCP (6), length: 64, bad cksum 0 (->2b69)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: S, cksum 0x845a (incorrect (-> 0x671c), 471959475:471959475(0) win 65535 <mss 1460,nop,wscale 0,nop,nop,timestamp 910460410 0,sackOK,eol> 16:52:15.260163 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 60) 192.168.1.106.lds-distrib > 192.168.1.109.53787: S, cksum 0xaf26 (correct), 3517135507:3517135507(0) ack 471959476 win 5792 <mss 1460,sackOK,timestamp 246912852 910460410,nop,wscale 7> 16:52:15.260216 IP (tos 0x0, ttl 64, id 35624, offset 0, flags [DF], proto: TCP (6), length: 52, bad cksum 0 (->2b74)!) 192.168.1.109.53787 > 192.168.1.106.lds-distrib: ., cksum 0x844e (incorrect (-> 0xf492), ack 1 win 65535 <nop,nop,timestamp 910460410 246912852> Hmmm. Bad checksum is a strange thing to see. I am doing some testing now to try and reproduce this. Quote: Here's what happens when the backend is off, but the backend computer is running.. ... QMYSQL3: Unable to connect Database error was: Can't connect to MySQL server on '192.168.1.106' (61) I assume you mean both backend off and Mysql shut down? I am at a loss. An older frontend binary works, but a newer one fails to connect at all. Very weird.

Author:	jfkjfk [ Wed Aug 08, 2007 1:24 pm ]
Post subject:
Quote: I assume you mean both backend off and Mysql shut down? Just the backend service stopped... mysql service is up Quote: I am at a loss. An older frontend binary works, but a newer one fails to connect at all. Very weird. This also includes running an older matched version backend.. It was able to do live tv, but couldn't play recordings... Said file not found, but I was thinking that was a db incompatibility or some version issue.. I would love to hear anything you find.. I've literally spent hours going over my setup.. Assuming I have something messed up.. at this point I really want to believe it's a code problem.. but in the end I probably have a missing ; somewhere.. LOL! Keep me up to date with your thoughts, I'm curious and would like to learn even if we dont solve it.. tx.. jfkjfk

Author:	nigelpearson [ Wed Aug 08, 2007 5:59 pm ]
Post subject:
jfkjfk wrote: Quote: I assume you mean both backend off and Mysql shut down? Just the backend service stopped... mysql service is up That is very strange, because the errors from the frontend definitely say that the MySQL database isn't reachable. I am beginning to suspect a database socket issue. Could you maybe try an SQL client (e.g. CocoaMySQL) on the Mac to see if you can connect to the backend database in this situation? (i.e. with mythbackend stopped)

Page 1 of 2	All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/

Author:	jfkjfk [ Wed Aug 08, 2007 8:21 pm ]
Post subject:
I dled Navicat, and have no problem reaching the mysql server.. using mythtv mythtv as username and pw... I've also logged in via terminal mysql -u mythtv -p -h 192.168.1.106 so it's finding it..