Segmentation Fault – Sqlyog Job Agent Version 5.29

[jagtar]

Serious problem

I have a huge database on two different servers. I ran the SQLyog Job Agent Version 5.29 sync script to update the local database from remote database. My database tables are huge sizes (1G:cool:, I am storing the pdf file contents in BLOB field.

I tried to oneway sync with all the method but I am failed because of fallowing error.

`asbeaver_uploaded_files` 434 39 ./runme: line 3: 21768

Segmentation fault /home/mysync/lamba/sja -f

/home/mysync/lamba/testfile.xml

Please help me !!!!!!!!!!

---

My.cnf File contents

---

[mysqld]

datadir=/var/lib/mysql

socket=/var/lib/mysql/mysql.sock

set-variable=max_allowed_packet=999999999

set-variable=max_connections=500

[mysql.server]

user=mysql

basedir=/var/lib

[safe_mysqld]

err-log=/var/log/mysqld.log

pid-file=/var/run/mysqld/mysqld.pid

---

MySQL Error Log File

---

A mysqld process already exists at Sun Jan 28 22:06:11 PST 2007

070129 02:59:59 mysqld ended

070129 03:01:06 mysqld started

Cannot initialize InnoDB as 'innodb_data_file_path' is not set.

If you do not want to use transactional InnoDB tables, add a line skip-innodb to the [mysqld] section of init parameters in your my.cnf or my.ini. If you want to use InnoDB tables, add to the [mysqld] section, for example, innodb_data_file_path = ibdata1:10M:autoextend But to get good performance you should adjust for your hardware the InnoDB startup options listed in section 2 at http://www.innodb.com/ibman.html

/usr/libexec/mysqld: ready for connections

070129 3:14:35 /usr/libexec/mysqld: Normal shutdown

070129 3:14:35 /usr/libexec/mysqld: Shutdown Complete

070129 03:14:35 mysqld ended

070129 03:15:40 mysqld started

Cannot initialize InnoDB as 'innodb_data_file_path' is not set.

If you do not want to use transactional InnoDB tables, add a line skip-innodb to the [mysqld] section of init parameters in your my.cnf or my.ini. If you want to use InnoDB tables, add to the [mysqld] section, for example, innodb_data_file_path = ibdata1:10M:autoextend But to get good performance you should adjust for your hardware the InnoDB startup options listed in section 2 at http://www.innodb.com/ibman.html

/usr/libexec/mysqld: ready for connections A mysqld process already exists at Mon Jan 29 22:40:24 PST 2007

Status information:

Current dir: /var/lib/mysql/

Current locks:

lock: 839ebd4:

lock: 839cd34:

[peterlaursen]

I'll move your post to the SQLyog category, and after that study details …

Please distinguish the Monyog/SQLyog categories 😉

[peterlaursen]

I do not think this MySQL log is related to this problem!

Do you have any reason to think it is?

Are the timestaamps in the log showing the time when this problem occurred?

Obviously the OS tries to start more identical MySQL instances, but SJA does NOT start a server instaance – it only connects to a running instance!

'segmentation fault' in *nix is what we would call a 

'crash' is windows.  Crash is occuring on the client side and not the server side.

There is no information for analyzing the problem.  We will need more info – at least:

1) a structure only dump of the jobfile (or better: a dump of a small table) wioth a few rows of data) to reproduced with

2) the jobfile

3) detailed information about the OS where the client program (SJA) runs.  Linux-'dialect'? Version?

4) MySQL version(s)

do you have a chance do runs SJA on the other server (if more than one is involved) or from Windows (you may download SQLyog ENTERPRISE TRIAL) ?

I will have to ask you to do a little more research into this yourself.  We cannot guess u will have to find out and report!  And if there is an issue for us to solve, we need to detailed information so that we can reproduce!  Try to answer for instance:

1) Does it only happen with HUGE tables, or with small tables too?

2) Can the problem be located to a specific server?

3) Is it related to the PDF's or not?

[peterlaursen]

Also:

It would be nice to know if it is a problem specific to version 5.29?  Do you know?

[jagtar]

peterlaursen wrote on Apr 20 2007, 06:08 PM:

Also:

It would be nice to know if it is a problem specific to version 5.29? Do you know?

MYSQL Version is : 4.1.22-standard

OS : Redhat 9

JOB File

---

192.168.254.21

root

password 3306

[default]

documents_db

localhost

root

password 3306

[default]

documents_db

`asbeaver_uploaded_files`

---

SCRIPT ERROR

---

[root@clickdb lamba]# /home/mysync/lamba/runme

SQLyog Job Agent Version 5.29

Copyright © Webyog Softworks Pvt. Ltd.. All Rights Reserved.

Sync started at Sat Apr 21 01:02:51 2007

Table SrcRows TgtRows Inserted Updated Deleted

========================= ======= ======= ======== ======= =======

`asbeaver_uploaded_files` 462 39 /home/mysync/lamba/runme: line 3: 25509 Segmentation fault /home/mysync/lamba/sja -f /home/mysync/lamba/testfile.xml

[peterlaursen]

Please also give a SQL DUMP with table structure (or better a few rows of data).

To work with an issue like this we will need to start reproducing every detail in the debugging environment.  Anything else will be guesswork.

You can create a ticket if you want to keep that dump confidential.

You did not answer if SJA is running on the machine where MySQL runs!

[Author]

Posts