Segmentation Fault With V5.2

[peterlaursen]

Not reproduceable here. Testing includes Fedora3, Fedora5, RHEL4 and SuSE10.

I just tried passwords like '123()abc' and similar.

We will need a complete test case or temporary access to your server.

Create a ticket if you have some details you do not want to reveal here.

[Amir]

peterlaursen wrote on Dec 6 2006, 11:31 AM:

Not reproduceable here. Testing includes Fedora3, Fedora5, RHEL4 and SuSE10.

I just tried passwords like '123()abc' and similar.

We will need a complete test case or temporary access to your server.

Create a ticket if you have some details you do not want to reveal here.

Unfortunatley the database servers are behind a firewall so I cant give you access. I'd be happy to run any testcase or anyting else you want me to run against the servers. I have root access to the server so can run any commands against the server.

FWIW one server (src) is 4.0.20 and the other is 5.X (destination).

[Amir]

Thanks for the PM…

So is there anything else at all I can do to find out whats wrong?, how can I make a “ticket”?.. Can I run the agent in debug mode to see what its not happy about?

Tried to run the app under gdb, but it just sits there (and does nothing) ?

Code:

[amir@khan x7]$ gdb ./sja
GNU gdb Red Hat Linux (6.5-13.fc6rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type “show copying” to see the conditions.
There is absolutely no warranty for GDB. Type “show warranty” for details.
This GDB was configured as “i386-redhat-linux-gnu”…(no debugging symbols found)
Using host libthread_db library “/lib/libthread_db.so.1”.

(gdb) run syncstage-newsql0.xml
Starting program: /home/amir/tmp/x7/sja syncstage-newsql0.xml
(no debugging symbols found)
SQLyog Job Agent Version 5.2
Copyright (c) Webyog Softworks Pvt. Ltd.. All Rights Reserved.

Sync started at Wed Dec 6 13:05:09 2006

Program received signal SIGTSTP, Stopped (user).
0x08079acb in connect ()
(gdb) quit
The program is running. Exit anyway? (y or n) y
[amir@khan x7]$ date
Wed Dec 6 13:05:48 GMT 2006
[amir@khan x7]$

[peterlaursen]

OK .. reproduced now.

I can copy the text from your 'Code box' here and change the details and get the segmentation fault on Fedora3 and SuSE10. If I build a similar jobfile with the wizard on Windows and copy that file to Linux I do not.

Password does not matter. It is reproducable with any password.

We will have to look detailed into this tomorrow.

[Amir]

peterlaursen wrote on Dec 6 2006, 03:33 PM:

OK .. reproduced now.

I can copy the text from your 'Code box' here and change the details and get the segmentation fault on Fedora3 and SuSE10. If I build a similar jobfile with the wizard on Windows and copy that file to Linux I do not.

Password does not matter. It is reproducable with any password.

We will have to look detailed into this tomorrow.

Thank you VERY much! 🙂

[peterlaursen]

First observations is that if you add tags for each connection it will work. However omitting a tag should be OK, so this must be considered a bug.

Enter the tags like:

Code:

localhost
root **** 3306 [default]
test2

localhost
root **** 3306 [default]
test3

[Amir]

Added element and its working fine now.

🙂

[peterlaursen]

It should now (version 5.21) also work on LINUX without the tag.

Can you confirm?

[Amir]

peterlaursen wrote on Dec 11 2006, 09:27 AM:

It should now (version 5.21) also work on LINUX without the tag.

Can you confirm?

Works 🙂

[Author]

Posts