Segmentation Fault using SJA on Linux 9.0

This topic is empty.

Viewing 16 reply threads

Author

Posts
- December 12, 2004 at 11:38 am #8695
  
  garybarnes
  Member
  
  I have been using SJA on other servers quite happily, but when I tried it on a server running Linux 9 I get a Segemtation Fault error. Typing sja on it's own returns the help prompt as normal, and when I try a script which is known to work on another machine the sja log and session files are created, but are empty (and I get the error). Any clues?
- December 13, 2004 at 2:23 am #16679
  
  Ritesh
  Member
  
  I have forwarded the issue to my development team.
- December 15, 2004 at 3:25 pm #16680
  
  Cris_Boisvert
  Member
  
  I have had the same problem.. just installed Fedora Core 3 (did all the updates)
  
  and setup sqlyog to sync to a database.
  
  I used the same xml file that I have on another server that already works…
  
  Figureing It may be somthing with the connectvity to the sql server.
  
  I tried to do it locally and received the same results.
  
  below is what I have in the xml File
  
  and the error..
  
  (Note I had to remove the beginning “<" to make it post. job version=”4..0″>
  
  syncjob>
  
  abortonerror abort=”no” />
  
  fkcheck check=”no” />
  
  twowaysync twoway=”no” />
  
  source>
  
  host>localhost
  
  user>root
  
  pwd />
  
  port>3306
  
  database>test
  
  /source>
  
  target>
  
  host>localhost
  
  user>root
  
  pwd>
  
  port>3306
  
  database>test2
  
  /target>
  
  tables all=”yes” />
  
  /syncjob>
  
  /job>
  
  SQLyog Job Agent Version 4.0
  
  Copyright © Webyog Softworks Pvt. Ltd.. All Rights Reserved.
  
  Sync started at Wed Dec 15 09:55:19 2004
  
  Segmentation fault
- December 15, 2004 at 6:22 pm #16681
  
  Ritesh
  Member
  
  I think this issue is only related to Fedora Core :huh:
- December 17, 2004 at 8:59 pm #16682
  
  Cris_Boisvert
  Member
  
  I have it running fine on fedora core 2 and 1…
  
  just core 3 that is giving me problems..
- January 3, 2005 at 10:57 am #16683
  
  puzzlebox
  Member
  
  I've got the same problem, also on Fedora Core 3 – are there any workarounds available?
- January 4, 2005 at 9:47 am #16684
  
  Ritesh
  Member
  
  We are working on this issue. As of now there are no workarounds other then *not* using FC 3.
- February 26, 2005 at 12:13 am #16685
  
  dmakepeace
  Member
  
  Hi , has there been any fixes for this yet. I really need this to run on a Fedora Core 3 server. Thanks for any information.
- February 26, 2005 at 3:40 am #16686
  
  Ritesh
  Member
  
  We are actually working on the fix. You can expect a fix anywhere in the next week.
- March 15, 2005 at 8:50 pm #16687
  
  Cris_Boisvert
  Member
  
  it shows that their should be a fix in a couple weeks of feb 26th … I had not seen anything yet?
  
  Thanx
  
  Cris
- March 15, 2005 at 10:42 pm #16688
  
  Ritesh
  Member
  
  I know we have been little late on this issue but currently we are extremely busy with v4.1 so this fix might take some time.
- March 19, 2005 at 7:14 am #16689
  
  ks32
  Member
  
  SQLyog Job Agent Version 4.0 gives Segmentation fault on Redhat 9 linux installation. Although it did work with sja-samples but if you modify them a little bit then it will give Segmentation fault error.
- May 5, 2005 at 12:10 am #16690
  
  JasonPotter
  Member
  
  Hi There,
  
  It has now been a couple of months since this error was raised, is there a fix?
  
  Regards
  
  Jason
- May 5, 2005 at 2:14 am #16691
  
  Ritesh
  Member
  
  No.
  
  We are still working on the issue.
- May 31, 2005 at 7:48 am #16692
  
  Ritesh
  Member
  
  We have released a new version of SJA for Linux that fixes the above segmentation fault bug.
  
  You can download it from http://www.webyog.com/sqlyog/downsja.html
  
  Waiting for your comments.
- June 6, 2005 at 1:57 pm #16693
  
  Anonymous
  Guest
  
  i've the latest version of SJA Job Agent (4.0) but i have a segmentation fault when i start my sync….
  
  i think that the problem is Linux Red Hat 9…
- June 6, 2005 at 5:38 pm #16694
  
  Ritesh
  Member
  
  When did you download it?
  
  We had released a new build on 31st May that fixed the above bug.
Author

Posts