[uyuni]

That's it.

Thank you.

Emilio

[uyuni]

I don't have a real indication but this seems very probable to me.

[uyuni]

For such errors it would be nice to have a timeout for the SJA job (or maybe only for an SQL statement). Configuration of the timeout as a parameter for the commandline would be sufficient.

Now my whole system breaks because never a new sja is started from the scheduler until I kill the old sja.

Emilio

[uyuni]

peterlaursen wrote on Oct 9 2007, 10:33 AM:

An empty DUMP file is created when the program starts. The file is removed when it closes. If the program is 'killed' (not shutting down gracefully) the file will remain. Also it will remain as long as the job is running.

Please tell (for a start)

* Windows version

* remote or local servers? How do you connect (HTTP, SSH, direct)

* what kind of SJA job? data sync?

* how long does it normally take to complete the job?

* how can you be sure that job has completed?

Hello,

– OS: Server 2003

– connection to remote SSH server

– task: a maintenance task, an UPDATE on the remote server

– normal completion in 6 seconds

– I cannot check if the task has completed correctly because the database has changed since then.

Emilio

[uyuni]

This topic is still not solved (sqlyog 6.05).

When my connection over an SSH-tunnel is idle for 10 minutes I get the message “Error No 2006. MySQL server has gone away.”

I cannot reconnect with 'connect using the same details' from the 'file' menu because the local port is already used for SSH-forwarding.

It would be very nice if you could detect this error internally and close and reconnect the connection automatically!

Emilio

[uyuni]

This thread is already quite old but I have an interesting link to it:

http://http-tunnel.sourceforge.net/

One thing that is not working here is SSL.

[uyuni]

A stored procedure is not an option because the database is only Mysql 4.1

I've found where and how to change the PHP-script but it would be nice if it is really included.

Security is not such a big issue: The include-file can be outside of the webdirectory and you need to know the login of the database to start it this way.

[uyuni]

Is nobody interested in this feature?

It would allow me to do things I can't do now.

[uyuni]

It seeems OK now!

Thanx,

Emilio

[uyuni]

Any news?

[uyuni]

It cannot be the MySQL-bug because I use a MYISAM table.

---

I send you an SQL-export.

Do this:

– Run script

– run

select id,substr(text,1,196),substr(text,1,197) from utferror where id=10;

The result is NOT OK

– open “table data”, the result for the column 'text' is NOT OK

– change the value of column 'text', add Umlaut-characters (öäü). They are displayed correctly in the editor window. When you close the editor-window with “OK” then the value is wrong in the “table data”-tab!

---

SHOW VARIABLES LIKE '%character%';

character_set_client;utf8

character_set_connection;utf8

character_set_database;latin1

character_set_results;utf8

character_set_server;latin1

character_set_system;utf8

character_sets_dir;D:\Programme\MySQL\share\charsets/

[uyuni]

Serverversion is 4.1.16-nt.

The difference is there even when using SUBSTR twice, it depends on the substring-length, see screenshot.

The result is OK when using the commandline, see screenshot.

Emilio

[uyuni]

As long as the old window (with the timeout-connection) is not closed I cannot do Ctrl-N because this results in the error attached.

When I click Refresh Object Browser the error 2006-mysql server has gone away appears.

Emilio

[uyuni]

MySQL-Version: 4.1.16

Variables:

“character_set_client”;”latin1″

“character_set_connection”;”latin1″

“character_set_database”;”latin1″

“character_set_results”;”latin1″

“character_set_server”;”latin1″

“character_set_system”;”utf8″

“character_sets_dir”;”C:\Program Files\MySQL\share\charsets/”

Variables are the same for remote and local server (except last line).

I want to do “Copy table to different host” from a tunnel-host to my localhost. This works when the tunnel is SSH but not when the tunnel is http (servers are the same for SSH/http).

Unfortunately my license expired so I cannot update SQLYog anymore.

I just downloaded the trial of 5.29 and with that version it's OK.

Emilio

[uyuni]

Is OK now with RC1.

Emilio.

[Author]

Posts