I am new to Hudson and I have a question.
I'm trying to build some jobs on dumb slave and after that I need to shutdown that slave.(the machine). However, there is the following issue: I've tryed many ways,
using "shutdown /s /t 120", starting .bat file copyed at the slabe with this content, even starting .jar file to shutdown. And the result is the negative. When running "shutdown /s /t 120" I receive
"'shutdown' is not recognized as an internal or external command,
operable program or batch file.".
Does anybody solved such issue or have any suggestions?
Thanks :)
Try running cmd.exe /c shutdown /r /t 120
Related
I am running a Selenium C# project through Visual studio and suddenly encountered an error
Access to the path 'c:\users\documents\visual studio 2017\Project\SeleniumTestProject\SeleniumTestProject\bin\Debug\chromedriver.exe' is denied.
I removed the readonly attribute for the folder but still get this error. Can anyone please suggest me what could be wrong and solution for the same.
Just worked when I killed the chrome driver exe from command prompt
Launch command prompt and enter "taskkill /f /im chromedriver.exe"
Clean your solution
I solved it by shutting down the ChromeDriver correctly.
I used:
IWebDriver.Dispose() for quitting the ChromeDriver process
In your case, after your test completes, there should be a chromedriver.exe in your Task Manager which does not quit until you manually "End Process" it. However, if you use IWebDriver.Dispose(), it kills the process. And now, since the chromedriver.exe is no longer in use, the "Access denied" problem also goes away.
Hope this solves your problem.
Reference: https://stackoverflow.com/a/44126143/1785144
Deleted the chrome driver exe from command prompt
Launch command prompt and enter "taskkill /f /im chromedriver.exe" command.
Then rebuild the code again.
'c:\users\documents\visual studio 2017\Project\SeleniumTestProject\SeleniumTestProject\bin\Debug\chromedriver.exe'
First end the process of chromedriver.exe from Task Manger, then Delete the chromedriver.exe from your project bin file and check whether Selenium.WebDriver.ChromeDriver package installed or not, If it's not installed you should installSelenium.WebDriver.ChromeDriver package from "NuGet Package Manager"..and rebuild , otherwise rebuild the project directly...
End the chrome driver process from task manager.
My solution was to remove the Selenium.Chrome.WebDriver fixed version that I installed as part of my Nuget package and then cleaned my solution.
I am experiencing the same issue using visual studio 2017. I'm having to delete the chromdriver process via task manager, clean the solution and then build and start the test. I am also using a driver.Quit() method as my tear down
Hi I ended up downgrading my Chrome version from 58 to 57 whilst using the chromedriver nuget package 2.29 and it seems to be working ok now. haven't workedd out why yet though
Just you can cut chromeDriver.exe from debug folder and paste it to another place, then rebuild the project again
I tried the command taskkill /f /im chromedriver.exe on the command line and my test ran smoothly. But I needed a way to run this every time before a test run via Visual Studio. So I put it in Project > Properties > Build Events > Pre-build.
When I ran the test, I got an error:
The command taskkill /f /im chromedriver.exe exited with code 128.
The process chromedriver.exenot found.
So I used this instead: taskkill /f /fi "pid gt 0" /im chromedriver.exe. It works like a charm!
I installed scilab.6.0.0 and backdoor fromscilab website (which I could not find it from Application>Module maneger>atom>Technical). I moved the backdoor file my home and from scilab command line I installed it
-->atomsInstall('/home/user/BackDoor_0.2_5.5.bin.x86_64.linux.tar.gz')
Even though, it installed backdoor successfully, when I restart the scilab I got this error message with backdoor
Start Toolbox BackDoor
Load macros
atomsLoad: An error occurred while loading 'BackDoor-0.2':
lib: Old binary lib detected. Please recompile it for Scilab 6.
As I understand I need to update the library, but I don't know how?
Would sb tell me explicitly (because I am a newbie user of scilab) how can I get over the error?
at the and I try to connect octave and scilab and when I try to run a demo script at octave I get also this error
>> sci_sim_example
Scilab connection failed
FYI: I already installed sci_cosim package (after I downloaded the package, I write to octave prompt >>pkg install sci_cosim_0.1.3.tar.gz), and I load it before running the script.
How can I recompile the lib: Old binary lib detected
Thank you so much for your help in advance
Here's what worked for me.
Download Scilab 5.5.2 (link for Linux 64bit version)
Extract the .tar.gz file in your preferred system location to install it there. Generally, my preferred location to extract / install self-contained packages is inside /opt .
You can extract the .tar.gz file using your filebrowser's graphical facilities, or on the command line; if /opt is owned by root (which it usually is) you may need to change ownership after extraction. E.g. your installation might look something like this:
cd /opt
sudo wget http://www.scilab.org/download/5.5.2/scilab-5.5.2.bin.linux-x86_64.tar.gz
sudo tar -xvzf ./scilab-5.5.2.bin.linux-x86_64.tar.gz
sudo rm scilab-5.5.2.bin.linux-x86_64.tar.gz
sudo chown $USER ./scilab-5.5.2 -R
Launch scilab by typing
/opt/scilab-5.5.2/bin/scilab &
in your terminal.
Once scilab is launched, go to Applications->Module Manager ATOMS. In the new window that comes up, click on All modules -> BackDoor -> Install.
You should get a message saying "Installation done, please restart SciLab".
Exit Scilab, and launch it again from the terminal. If you see a message:
atomsLoad: An error occurred while loading 'BackDoor-0.2':
File "/opt/scilab-5.5.2/share/scilab/contrib/BackDoor/0.2/etc/backdoor.start" does not exist.
then type the following commands in your terminal to rename the affected files:
cd /opt/scilab-5.5.2/share/scilab/contrib/BackDoor/0.2/etc/
mv BackDoor.start backdoor.start
mv BackDoor.quit backdoor.quit
Restart SciLab again. Hopefully this time it will work and SciLab will inform you that BackDoor is listening for connections at a certain port.
PS. Also note that from the octave side of things, the -auto option is no longer accepted when you perform a pkg install. You will need to load the sockets and sci_cosim packages manually each time you want to use this.
SSIS package to decrypt files runs fine via command prompt and on other servers. Fails every time it is run inside of SSIS package.
Process was working perfect until today.
"C:\Program Files (x86)\WinSCP\winscp.exe" /console
/log=D:\XXX\XXXXX\SFTPDownload\WinSCP.log /command "option batch on"
"option confirm off" "open sftp://UserAccount:XXXXXXX#ServerName:22
-hostkey=""ssh-rsa 2048 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx""" " call ./decryptXX.ksh /app1/XX/XXXXXXXXX out txt decrypt_log.log signal
decrypt_end decrypt_error xxx_summary &" "exit"" at "", The process
exit code was "3" while the expected was "0".
Log is not created when I run it in SSIS, but is when command prompt and works as expected.
Exit code 3 usually indicates an error initializing WinSCP.
If you are using WinSCP 5.2.4 or older, you are likely a victim of bug that prevented WinSCP from being run more than approximately 32 thousand times on one Windows session (session 0 in case of SSIS).
See https://winscp.net/tracker/996 and
https://winscp.net/eng/docs/message_library_process_terminated_with_exit_code_3
Make sure you upgrade to the latest version of WinSCP. You also need to restart the server to recover the system.
I already googled a lot and found similar posts but I couldnt get my release plugin to work 100%.
The release plugin is running until tagging the release. Updating the poms in prepare works but tagging fails. The url is exactly the same:
[INFO] Checking in modified POMs...
[INFO] Executing: cmd.exe /X /C "svn --username user--password --no-auth-cache --non-interactive commit --file C:\Users\user\AppData\Local\Temp\maven-scm-527854298.commit --targets C:\Users\user\AppData\Local\Temp\maven-scm-1649111498782212601-targets"
[INFO] Working directory: C:\Hudson\jobs\project\workspace
[INFO] Tagging release with the label project-1.0...
[INFO] Executing: cmd.exe /X /C "svn --username user --password --no-auth-cache --non-interactive copy --file C:\Users\user\AppData\Local\Temp\maven-scm-185331125.commit --revision 10608 https://server:3691/svn/Repository/project https://server:3691/svn/Repository/project/tags/framework-1.0"
[INFO] Working directory: C:\Hudson\jobs\project\workspace
I really dont understand why the plugin is able to update the poms but not able to checkin the tag files.
I already tried to access the repository localy with cmd and accepted everything permanentely.
I am using Windows Server 2008 R2, SVN 1.5.7(due to old server) and Hudson 2.2.0 deployed on Tomcat 6.0. Can't enable default --trust-server-cert as svn doesnt support this in my version. Tomcat is running on exactly the same user I accepted the svn certificates on command line.
Can somebody let me know what I am doing wrong here?
Are you sure you have got permission to create files under the /tags directory in the repository? You should try executing the second tagging command in a Command Prompt window and see what happens. (If you've got any error messages, please paste them here).
I am starting a ruby command from a batch file using STAF.
STAF $TESTMACHINE process start command ruby "C:\MyProject\scripts\MasterScript.rb" WAIT SAMECONSOLE RETURNSTDERR RETURNSTDOUT WORKDIR "C:\MyProject\scripts"
This batch file is triggered by a Hudson job. But my observation is that the print/puts of the ruby files appear in the hudson console only after the completion of the execution of the ruby script [Hudson job]. This way I can not make out if something is going wrong in the script execution unless the job completes.
Also, I understand that if I remove RETURNSTDERR RETURNSTDOUT, the ruby script's output is displayed in the STAF console on the target machine. So STAF is the one which is sending back the ruby outputs to the hudson console.
Now can I use any option with STAF to get the ruby output spontaneously to the hudson console?
Thanks for reading this lengthy question :)
You can use SSH instead of STAF for such task.
It seems with STAF it's a little bit tricky and could be done with OUTPUT option.
If you have shared storage, for example NFS share called /nfs on hudson server and d:\nfs on Windows, the following hudson job should work:
STAF $TESTMACHINE process start command ruby "C:\MyProject\scripts\MasterScript.rb" WAIT SAMECONSOLE RETURNSTDERR RETURNSTDOUT WORKDIR "C:\MyProject\scripts" OUTPUT "d:\nfs\hudson.log" &
tail --pid=$! -f /nfs/hudson.log