Your browser was unable to load all of the resources. They may
have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.
Hi,
I am running a script (ksh) on UNIX using quickbuild. The build log displays the information pasted below:
2008-12-17 10:55:38,346 [Thread-3353] INFO - process not attached to terminal
2008-12-17 10:55:38,346 [Thread-3353] INFO - Usage: who [-rbtpludAasHTqRm] [am i] [utmp_like_file]
2008-12-17 10:55:38,346 [Thread-3353] INFO -
2008-12-17 10:55:38,346 [Thread-3353] INFO - r run level
2008-12-17 10:55:38,347 [Thread-3353] INFO - b boot time
2008-12-17 10:55:38,347 [Thread-3353] INFO - t time changes
2008-12-17 10:55:38,347 [Thread-3353] INFO - p processes other than getty or users
2008-12-17 10:55:38,347 [Thread-3353] INFO - l login processes
2008-12-17 10:55:38,347 [Thread-3353] INFO - u useful information
2008-12-17 10:55:38,347 [Thread-3353] INFO - d dead processes
2008-12-17 10:55:38,347 [Thread-3353] INFO - A accounting information
2008-12-17 10:55:38,347 [Thread-3353] INFO - a all (rbtpludA options)
2008-12-17 10:55:38,347 [Thread-3353] INFO - s short form of who (no time since last output or pid)
2008-12-17 10:55:38,347 [Thread-3353] INFO - H print header
2008-12-17 10:55:38,347 [Thread-3353] INFO - T status of tty (+ writable, - not writable, x exclusive open, ? hung)
2008-12-17 10:55:38,348 [Thread-3353] INFO - q quick who
2008-12-17 10:55:38,348 [Thread-3353] INFO - R print host name
I dont get this on the screen while running the script manually on UNIX. Is this something quickbuild is trying , or something that i need to check in my script.
Please note the script executes successfully and also generated necessary logs which doesnt contain this message. This message only appears in QB build log.
Thank you,
-
replies
12
-
views
4493
-
stars
0
-
How do you define the command builder calling the script? It should be defined something like below:
/bin/ksh /path/to/your/script
Regards
Robin
Build Command : /usr/bin/ksh ./execute_CGSDpackage.ksh
Directory to run command in : ${var["CM_SCRIPTS"]}/PsfReader
This is how i execute the script. Please let me know if you need anymore information.
Thank you for looking into this
I also get usage messages like that when I run unix commands. Please note my QB is on Windows and we use putty's plink utility to run remote commands. The usage message pops out when plink is run through QB, but does not happen when we use it directly. Everything executes successfully on the unix side, as you mentioned happens to you as well.
I have noticed when there is a problem on the unix side, I get the unix error in the build log and no usage message. So to me, I've taken the usage message printing to be a sign that all is well <!-- s:D --><img src="{SMILIES_PATH}/icon_biggrin.gif" alt=":D" title="Very Happy" /><!-- s:D -->
It is odd, I tried to run some ksh script on Linux at my side through QB over plink. What is your UNIX system?
Regards
Robin
The machine I am using is a UNIX system, and my admin told me its running on running on N4000 class system (not sure if its useful). The QB installation is on the same UNIX machine. Also my script kicks of a script written by unix admins (owned by root). But like i said when i kickoff my script on the box itself i dont see those warnings or messages.
Thank you,
I was a little confused. You mentioned that the command was issued through plink by a QB server installed on Windows. And now you told me that a QB server installed on N4000 also takes part in...
Hi,
Sorry for the confusion , one of the forum memebers - kyky17 replied to the same thread and is facing the same issue but kyky17 has QB installed on Windows and is using plink to execute unix commands and I have my QB installed on N4000 UNIX system and am executing the commads on unix.
Thank you,
Sorry I did not noticed that there are two members involved in the thread. Since we do not have N4000 system here, it is way difficult for us trying to reproduce the problem here. If it is convenient for you, can you please test below:
1. Does the usage message got printed if you got QuickBuild executing other commands such as "ls"? To do this, you may create a separate configuration with a single builder executing command "/usr/bin/ksh ls", and configure the master step to be a build step running that builder.
2. Do you have QB installed on other UNIX system, such as Solaris, Linux, and can you observe such behavior there?
Regards
Robin
Hi,
I did try step 1. I created a test builder which ran "ls" command and it worked fine. But i could not run "/usr/bin/ksh ls", as it kept giving me a syntax error "ls: syntax error at line 1 : `(' unexpected". I also ran a ksh script which was able to run ls -lart and the output came out fine.
It will take me a day or two to try out step 2, as i need to install QB on the solaris machine. Will try have it done as soon as i can.
Thank you for looking into this.
For the test builder defined to execute "/usr/bin/ksh ls", please run the build again with "verbose" logging level, and the build log will contain the actual command executed by QuickBuild.
Hi , Sorry for the late reply.
This is the output from verbose mode.
2008-12-31 10:28:03,062 [Thread-4349] INFO - Condition satisfied, running step "TestPsf".
2008-12-31 10:28:03,063 [Thread-4349] DEBUG - Resolving step OGNL expressions...
2008-12-31 10:28:03,063 [Thread-4349] DEBUG - Resolving builder OGNL expressions...
2008-12-31 10:28:03,066 [Thread-4349] DEBUG - Creating temp file for builder logging...
2008-12-31 10:28:03,070 [Thread-4349] DEBUG - Executing '/usr/bin/ksh' with arguments:
'ls'
The ' characters around the executable and arguments are
not part of the command.
2008-12-31 10:28:03,073 [Thread-4349] DEBUG - Starting stream handler...
2008-12-31 10:28:03,074 [Thread-4349] DEBUG - Waiting for process "java.lang.UNIXProcess@14768c6"to finish...
2008-12-31 10:28:03,089 [Thread-4350] WARN - ls: syntax error at line 1 : `(' unexpected
2008-12-31 10:28:03,091 [Thread-4349] DEBUG - Process finished.
2008-12-31 10:28:03,091 [Thread-4349] DEBUG - Stopping stream handler...
2008-12-31 10:28:03,091 [Thread-4349] DEBUG - Stream handler stopped.
2008-12-31 10:28:03,094 [Thread-4349] ERROR - Step "TestPsf" is failed: Build success condition not satisfied.
2008-12-31 10:28:03,095 [Thread-4349] ERROR - Step "default" is failed: Composite step "default" failed due to unsatisfication of step success condition.
2008-12-31 10:28:03,096 [Thread-4349] INFO - Finished triggering step "default". Saving build status based on triggering result...
2008-12-31 10:28:03,096 [Thread-4349] INFO - Build failed: 2008-12-31 build3
2008-12-31 10:28:03,096 [Thread-4349] INFO - Finishing build...
Like i said if i use /usr/bin/ksh ls , build fails but if i use only ls it works fine.
Thank you,
Sorry the commad "/usr/bin/ksh ls" does not work since "ls" is not a ksh script. Please wrap the ls command in a test.ksh script for example:
#!/usr/bin/ksh
ls
And then write the command to be executed in QuickBuild like below:
/usr/bin/ksh /path/to/test.ksh
After this please run the build in verbose logging mode again to see what happens.
Also what is the result on a solaris machine?
Regards
Robin
