[peterlaursen]

one thing more:

there is a logging option:

Search the tunnelling file for

Code:

/* uncomment this line to create a debug log */
/*define ( “DEBUG”, 1 );/*

Uncomment the last line and lets see if it yields something.

The logfile 'yogtunnel.log' is created on the server in the folder of the tunnelling file.

Provided permissions allow for it.

[peterlaursen]

Did you try uploading the Tunnelling file again??

It could be corrupted!

[peterlaursen]

To summarize:

1) I get the same error if I stop Apache and try to connect with HTTP-tunnel.

2) If I start Apache without the php_mysql extension i DO NOT get this error but a HTTP error report.

3) If I start Apache wthout PHP at all, I also don't get this error but also a HTTP-error report

4) If I stop MySQL I simply get “Can't connect to MySQL Server etc.”. Further the experiments with the scripts show that Apache<>PHP<>php_mysql<>Mysql chain is functioning OK in general.

This must mean that the tunnelling script does not even succeed in creating the initial steps of connection to Apache.

But why?? Apache configuration changed? PHP-configuration changed? Could you ask at your ISP, if there has been any change in configurations? And don't forget to answer back if you find the reason for it!

[peterlaursen]

hmmm …

did they do something so that the SQLyog tunnelling script does not work ???

It is a problem with connection from the tunnelling script to Apache/PHP!

Is the tunnelling script and my script in same folder?

There could be some setting that restricted PHP to use or not to use scripts from certain folders ?!

[peterlaursen]

It is very likely that the php_mysql extension for some reason was not loaded with Apache last time it was started!

You could try the mysql_ping() function.

http://www.php.net/manual/en/function.mysql-ping.php

[peterlaursen]

And if I stop MySQL I get the MySQL client error returned!

[peterlaursen]

And I ABSOLUTELY am no coder! Stooped being so when TurboPascal went out!

[peterlaursen]

Try this.

Code:

connecting

“;
$connct = mysql_connect(“**host”,”**user”,”**pw”);
echo “

$connect

“;

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

echo “

 –  PHP version is “;
echo “$phpeter

“;
echo “

 –  Apache version is “;
echo “$minapache

“;

$database = “*db”;
mysql_select_db($database);
echo “

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

“;

$vis = “SELECT count(*) FROM $database.**mytable;”;
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 :
“;

printf (“%s rows in database:  %s $database”,$row[0],$row[2]);
mysql_close();
?>

It displays like attached

[peterlaursen]

No! The script is bad. Even is I stop MYSQL it displays 'Connection Succesful'.

Wait 5 minutes!

[peterlaursen]

Also check the settings of your Control Panel. For instance that the .php extension is enabled with the PHP-preprocessor!

[peterlaursen]

And the above script returns this (see attached) on my local system.

This is a php_mysql version of the script. I can copy in a php_mysqli -version of same. However SQLyog does not work with php_mysqli .

[peterlaursen]

I largely agree on your diagnosis that things may have changed at your ISP! The error message

Quote:

HTTP Error. The handle is in the wrong state for the requested operation

is very simple to reproduce with HTTP-tunnel. I have my own WAMP-stack. If I shut down Apache I get this error when trying to connect with HTTP-tunnel. So simply this error occurs if webserver/php -system cannot be contacted by the tunneling script. NB: I edited this!!

Sure that webserver is not down at the moment?

However can you connect with a script of your own like (where you substituete all that starts with ** with your own values):

Code:

connecting

“;
mysql_connect(“**host”,”**user”,”**pw”);
echo “

Connection OK

“;

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

echo “

 –  PHP version is “;
echo “$phpeter

“;
echo “

 –  Apache version is “;
echo “$minapache

“;

$database = “**database”;
mysql_select_db($database);
echo “

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

“;

mysql_close();
?>

All what works in mysql_connect(“**host”,”**user”,”**pw”); above should also work with SQLyog!

Maybe you can find something here that can help you:

http://www.webyog.com/faq/16_66_en.html

[peterlaursen]

Two small notes more:

1) There is one difference of MySQL 4.1 and 5.x

When SQLyog tries to insert literal string 'CURRENT_TIMESTAMP' MySQL 4.1 accepts that. With MySQL 5.0 (in most sql_modes) the string is substitued with '0000-00-00 00:00:00'.

2) It does not seem possible for the SQLyog ALTER TABLE GUI to generate the ' on update ….' right now. You must write SQL like

Code:

alter table `test`.`tbl` change `ts` `ts` timestamp  DEFAULT CURRENT_TIMESTAMP NOT NULL on update CURRENT_TIMESTAMP

to make 'on update ..' work with the test.tbl.ts -column.

[peterlaursen]

the answer is that you won't have to do so. With the more recent MySQL versions MySQL itself automatically creates the first timestamp column of a table as

Code:

NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

However you will have to wait a few days forSQLyog to fully support this, se http://www.webyog.com/forums/index.php?sho…view=getnewpost . 5.1 beta1should be out by the end of this week.

The problem is that SQLyog (like most grid-based editor) as of now simple reads CURRENT_TIMESTAMP as the literal string 'CURRENT_TIMESTAMP' and inserts this string, when you are saving from the grid. The workaround to avoid this is to work from the RESULT-pane: start issuing a SELCT column1, column2 etc (and omit the timestamp column). Now when inserting and updating data from result-pane the timestamp-column is not overwritten by SQLyog, and 'automatic rule' of the server takes effect.

There is a good article here: http://www.databasejournal.com/features/my…cle.php/3577131 . But the basic behaviour with timestamps in thsi respect is the same with 4.1 and 5.0. MySQL docs: http://dev.mysql.com/doc/refman/5.0/en/timestamp-4-1.html

[peterlaursen]

the name has changed. It is now named Migration Toolkit (from powertools menu). It is ONLY in Enterprise version.

related readings:

http://www.webyog.com/faq/category14.html

http://www.databasejournal.com/features/my…p/10897_3550146

[Author]

Posts