forums › forums › SQLyog › Sync tools, Migration, Scheduled Backup and Notifications › Problems automating SJA in linux
- This topic is empty.
-
AuthorPosts
-
-
June 17, 2004 at 3:39 pm #8468darthwonkaMember
If I try and specify a log file in the call to sja, I recieve the following error:
Code:==================================================================
DB Mirroring started on Thu Jun 17 09:28:09 MDT 2004
==================================================================
SQLyog Job Agent Version 2.0
Copyright (c) Webyog. All Rights Reserved.Error opening session ERROR log file.
Could it be that it is setting the correct log file, but needs another argument to set the session file?
Does it make sense that both should be identified in the call? What about just specifying the directory for the logs and session files and having the xml file define the name of the log/session file to generate?
The current workaround is to not specify the logfile and to have the script 'cd' into the directory containing sja and where it can also write to the directory.
This workaround seems to pose coding problems when trying the same technique for adding a DB sync button in a webpage.
-
June 17, 2004 at 3:53 pm #15959darthwonkaMember
What is strange is that I just tried the generated command via command-line and it worked just fine.
Is this possibly an environment problem? Do I need to set something special in the script?
Code:user@localhost ~]$ /raid/httpd/html/iss_public/bin/sja -l/raid/httpd/html/iss_public/bin/sja.log /raid/httpd/html/iss_public/bin/public.xml -
June 17, 2004 at 3:59 pm #15960darthwonkaMember
After running the command from a command line — then re-trying the script.. the script started working.
Weird.
If anyone has an explanation, I would love to understand this.
-
June 22, 2004 at 7:36 pm #15961darthwonkaMember
humm.. I just noticed that the automated cron is no longer working… same error as before.
Anyone have any thoughts?
UPDATE: This is still an issue for us.. Is anyone around to look into it?
-
February 7, 2006 at 2:39 am #15962kenzyMember
Check the permissions on your script file… it should have execute permissions.
-
February 7, 2006 at 6:16 am #15963RiteshMember
Starting with v5.0, SJA takes two arguments. One for the log file and one for the session file. So now you can execute SJA like:
./sja -llogfile.log -ssessionlog.xml
-
February 7, 2006 at 10:06 am #15964peterlaursenParticipant
I think it takes three parameters … don't forget the jobfile! 😉
like:
sja jobfile.xml -llog.txt -ssession.xml
The -s and -l parameters for specifying the session file and the log file are optional. A complete file path can be specified. That is useful if you don’t have write privilege to the installation folder. If not specified default values logfile.txt and session.xml are used and files are placed in the directory from where SJA runs.
The order of the three parameters is unimportant.
-
-
AuthorPosts
- You must be logged in to reply to this topic.