Remote Frontend question

  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:7d2c8b281fecdf0167a34bc38fa4d704' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Howdy,</p>\n<p>I\'m in the process of adding a remote front end. Installed from the same DVD, so they\'re the same version of MythDora.</p>\n<p>I\'ve added the backend ip address in the mysql.txt, and gone in to the General sections on both machines and added the IP address of the backend. I can establish a connection with the back end, and I am getting electronic programming guide information (so I know they\'re talking).</p>\n<p>But, when I was configuring the Myth general on the front end, I specified the directory /video for the location where videos were to be stored. On the front end, when I go to \"Watch Recordings\", I can see the names of the recordings, but when I select any of them, I get the message \"could not find recording\". I went to a terminal and ran mythfrontend, and saw that the system was looking for the file in the /video directory... presumably on the local (front end) machine... but the videos are on the back end machine.</p>\n<p>Is the front end \'supposed to\' be pointed at the /video directory on the back end machine somehow?</p>\n<p>Thanks!</p>\n', created = 1369246943, expire = 1369333343, headers = '', serialized = 0 WHERE cid = '1:7d2c8b281fecdf0167a34bc38fa4d704' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:d0e1296fd5e438ca847ae02d33662b0a' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>You shouldn\'t ever have to touch a directory path on a frontend machine. Once you edit the mysql.txt file you should be good to go. Here is a post that said they couldn\'t get the frontend working until they used a unique identifier. I still have never heard of or used this but you may need to.<br />\n<a href=\"http://mythdora.com/?q=node/1261\">http://mythdora.com/?q=node/1261</a></p>\n<p>\"Please ignore the man behind the curtain\"<br />\nDennis</p>\n', created = 1369246943, expire = 1369333343, headers = '', serialized = 0 WHERE cid = '1:d0e1296fd5e438ca847ae02d33662b0a' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:7ee834acd95a5efc693cacccaa73a62b' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>\"Please ignore the man behind the curtain\"<br />\nDennis</p>\n', created = 1369246943, expire = 1369333343, headers = '', serialized = 0 WHERE cid = '1:7ee834acd95a5efc693cacccaa73a62b' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:ed21468ef34edab17b0e70ea795620c9' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Perfect!</p>\n<p>I went in to the Utilities/Setup, and then General, and set my frontend to a unique identifier. My recordings now play. :)</p>\n<p>Thanks a bunch!</p>\n', created = 1369246943, expire = 1369333343, headers = '', serialized = 0 WHERE cid = '1:ed21468ef34edab17b0e70ea795620c9' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:552430b660bad87617183a2819508961' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Ya, that will work...or change the host name to a unique name..<br />\nProbably both of the host names are the same...That was the problem I had...</p>\n<p>d00dtv...I should of updated that post....<br />\nBoth of my computers had the same host name..thats why the unique name works</p>\n<p>Sam Gann</p>\n', created = 1369246943, expire = 1369333343, headers = '', serialized = 0 WHERE cid = '1:552430b660bad87617183a2819508961' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:b095903a1dbb5f5750bced117dc1fd52' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>Ah then that explains it :-). Makes sense now.</p>\n<p>\"Please ignore the man behind the curtain\"<br />\nDennis</p>\n', created = 1369246943, expire = 1369333343, headers = '', serialized = 0 WHERE cid = '1:b095903a1dbb5f5750bced117dc1fd52' in /var/www/mythdora/html/includes/cache.inc on line 109.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: SELECT data, created, headers, expire, serialized FROM cache_filter WHERE cid = '1:7ee834acd95a5efc693cacccaa73a62b' in /var/www/mythdora/html/includes/cache.inc on line 26.
  • user warning: Table './drupal_gding/cache_filter' is marked as crashed and should be repaired query: UPDATE cache_filter SET data = '<p>\"Please ignore the man behind the curtain\"<br />\nDennis</p>\n', created = 1369246943, expire = 1369333343, headers = '', serialized = 0 WHERE cid = '1:7ee834acd95a5efc693cacccaa73a62b' in /var/www/mythdora/html/includes/cache.inc on line 109.

Howdy,

I'm in the process of adding a remote front end. Installed from the same DVD, so they're the same version of MythDora.

I've added the backend ip address in the mysql.txt, and gone in to the General sections on both machines and added the IP address of the backend. I can establish a connection with the back end, and I am getting electronic programming guide information (so I know they're talking).

But, when I was configuring the Myth general on the front end, I specified the directory /video for the location where videos were to be stored. On the front end, when I go to "Watch Recordings", I can see the names of the recordings, but when I select any of them, I get the message "could not find recording". I went to a terminal and ran mythfrontend, and saw that the system was looking for the file in the /video directory... presumably on the local (front end) machine... but the videos are on the back end machine.

Is the front end 'supposed to' be pointed at the /video directory on the back end machine somehow?

Thanks!

You shouldn't ever have to

You shouldn't ever have to touch a directory path on a frontend machine. Once you edit the mysql.txt file you should be good to go. Here is a post that said they couldn't get the frontend working until they used a unique identifier. I still have never heard of or used this but you may need to.
http://mythdora.com/?q=node/1261

"Please ignore the man behind the curtain"
Dennis

"Please ignore the man behind the curtain"
Dennis

Perfect!

Perfect!

I went in to the Utilities/Setup, and then General, and set my frontend to a unique identifier. My recordings now play. :)

Thanks a bunch!

Ya, that will work...or

Ya, that will work...or change the host name to a unique name..
Probably both of the host names are the same...That was the problem I had...

d00dtv...I should of updated that post....
Both of my computers had the same host name..thats why the unique name works

Sam Gann

Ah then that explains it

Ah then that explains it :-). Makes sense now.

"Please ignore the man behind the curtain"
Dennis

"Please ignore the man behind the curtain"
Dennis