Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Tunnelling Problem?

forums forums SQLyog Using SQLyog Tunnelling Problem?

  • This topic is empty.
Viewing 7 reply threads
  • Author
    Posts
    • #9258
      peterlaursen
      Participant

      With MySQL 5.0.13 I get this error when using HTTP-tunnelling.

      Tunnelling file as of SQLyog 4.2

      On another machine with MySQL 5.0.12 there is no problem.

      Apache 2.0.54 on both. Tested with SQLyog 4.1 and 4.2 beta2 and php 4.4 and 5.1,

      The problem is there even with the most simple setup. Such as

      URL = [url=”http://localhost/SQLyogTunnel.php”]http://localhost/SQLyogTunnel.php[/url]

      but same from the other machine and when backlooping from a dyndns adress.

      What is new with MySQL 5.0.13? a bug or a feature ?

      Or just me that forgot something ?

      Anyone out there that can reproduce ?

    • #19312
      peterlaursen
      Participant

      Additional info.

      It seems to be problems with MySQL 5.0.13 and php!

      On the machine that was running 5.0.12 before I upgraded to 5.0.13. This machine runs php 5.1 beta3. And SQLyog tunnelling works. This machine runs php 5.1 beta. However now php_mysqli extension does not work on this machine anymore. It did before

      The machine with the problem runs php 4.4.0.

      And this simple test-script

      http://deepeter.dyndns.dk/test.php

      Code:
      Connecting to database

      “;
      $link = mysql_connect(“localhost”,”*****”,”******”);

      $mysqlver = mysql_get_server_info($link);
      $phpeter = phpversion();
      $minapache = apache_get_version();

      echo “

      Connection OK –

      “;
      echo “

      –  MySQL version is   –  “;
      echo “$mysqlver
      “;
      echo ”  –  PHP version is “;
      echo “$phpeter
      “;
      echo ”  –  Apache version is “;
      echo “$minapache

      “;

      $database = “musik”;
      mysql_select_db($link,$database);
      echo “

      The database '”;
      echo $database;
      echo “' is selected

      “;

      $vis = “SELECT count(*), kunstner, albumtitel FROM mp3_filer WHERE kunstner = 'abaji' GROUP BY kunstner, albumtitel limit 1;”;
      echo “

      Query goes as: >>>>
      “;
      echo $vis;
      echo ” >>>>

      “;
      $resultat = mysql_query($link,$vis) or die (mysql_error($link));
      echo “

      Query succesfull

      “;

      $row = mysql_fetch_array($resultat, MYSQLI_NUM);
      echo “

      Query result (formatted):
      “;

      printf (“%s tracks in this album:  “%s” ….. by artist: %s “,$row[0],$row[2],$row[1]);
      echo “

      “;

      mysqli_close($link);
      ?>

      returns the same error. Did not before upgrade to MySQL 5.0.13.

    • #19313
      peterlaursen
      Participant

      Things seem a little complicated:

      computer METUSALEM allows for tunnelling (from itself, from DAISY and with a dyndns backloop) with both MySQL 5.0.12 and MySQL 5.0.13 and php 5.1 beta3.

      computer DAISY does not allows for tunnelling (neither from itself, from METUSALEM nor with a dyndns backloop) with MySQL 5.0.13 and php 4.4.0.

      The script above that used to work (in php_mysql and php_mysqli versions as well) does not work any more with neither MySQL 4.0.26. 4.1.13, 4.1.14, 5.0.12 or 5.0.13. However you can se that it is only php-mysql interface that is a problem. PHP-interpretation and query'ing Apache and php version works!

      That is all I can do here!

      Nobody else out there that could add some info to make the problem understandable?

    • #19314
      Ritesh
      Member
    • #19315
      peterlaursen
      Participant

      Now look at this slightly adjusted script:

      Code:
      Etablerer forbindelse til databasen

      “;
      mysql_connect(“*****”,”*****”,*****”);
      echo “

      Forbindelse til databasen etableret

      “;

      $phpeter = phpversion();
      $minapache = apache_get_version();

      echo “

      Connection OK –

      “;

      echo “

       –  PHP version is “;
      echo “$phpeter

      “;
      echo “

       –  Apache version is “;
      echo “$minapache

      “;

      $database = “musik”;
      mysql_select_db($link,$database);
      echo “

      The database '”;
      echo $database;
      echo “' is selected

      “;

      $vis = “SELECT count(*), kunstner, albumtitel FROM $database.mp3_filer WHERE kunstner = 'abaji' GROUP BY kunstner, albumtitel limit 1;”;
      echo “

      Query goes as: >>>>
      “;
      echo $vis;
      echo ” >>>>

      “;
      $resultat = mysql_query($vis) or die (mysql_error());
      echo “

      Query succesfull

      “;

      $row = mysql_fetch_array($resultat, MYSQL_NUM);
      echo “

      Query result (formatted):
      “;

      printf (“%s tracks in this album:  “%s” ….. by artist: %s “,$row[0],$row[2],$row[1]);
      echo “

      “;

      mysql_close($link);
      ?>

      Test it from my webhost: http://www.deepeter.dk/test3.php

      and my local http://deepeter.dyndns.dk/test3.php

      This script used to run on local in both php_mysql and php_mysqli (with mySQL 4.1 and 5.0) versions. Now it does not run on any recent MySQL! And note the PHP version is the same (4.4.0) at both hosts!

      PS: sorry that I forgot to change the language of text strings. Take it as a course in Danish!

    • #19316
      peterlaursen
      Participant

      Well, yes of course.

      On METUSALEM the database was originally created with MysQL 4.0

      On DAISY it is a fresh 5.0 install-

      So METUSALEM uses old-style hash and DAISY new-style.

      And PHP distributed binaries (all of them) seem to have the old-style hash compiled into them.

      A little bit more for the FAQ.

    • #19317
      peterlaursen
      Participant

      but @Ritesh

      SQLyog itself seems to be smart enough to be able to work with both hash-formats ? Does it simply try both ?

    • #19318
      peterlaursen
      Participant
Viewing 7 reply threads
  • You must be logged in to reply to this topic.