every time I run mongod.exe from cmd I get the following message on my screen
I'm a beginner in this so I really don't know what it means
I haven't seen anything on the web describing this
You have three questions.
Cannot run mongo.exe - See mongo.exe not installed in Version 6.0.0
Excessive output when you run mongod.exe
Install MongoDB as service. Create a configuration file (a default file should be created at C:\Program Files\MongoDB\Server\6.0\bin\mongod.cfg while installation) and create the service with
mongod.exe --install "C:\Program Files\MongoDB\Server\6.0\bin\mongod.cfg"
Then your MongoDB starts automatically at boot time.
I haven't seen anything describing the log format - See Log Messages
I installed MongoDB and tried to run it on terminal. It just shows up 'mongo' is not recognized as an internal or external command, operable program or batch file.
I have set the path to bin folder inside Environment variables too. One thing I noticed is I might have a missing file inside bin folder and that is mongo. Because I have mongod and mongos file inside the bin folder. I tried to uninstall and reinstall the program and it was still not working.
I have no idea it's what that I'm missing. Please help out
Finally I have found the solution,
Mongo shell no longer ships with server binaries. We can download it from MongoDB Shell Download
Then we should extract the contents of the bin from the downloaded zip file to the bin file of the MongoDB folder and run mongosh instead of mongo on the terminal
I am new to clear case. Our organizations code is versioned using clear case and I have to edit some code. The codes are database .ddl file. so 2 .ddl files for a package.
I have checked out the pieces of code that I have to use. But I can not see them anywhere. I have checked the FTP client I am using, as well as my local.
Now I am confused about two parts:
After checking out do I copy the .ddl files from the current location to my clearcase home and then download them to pc and use them? That is what I am doing right now.
or is there any other way to generate the ddl files from PL/SQL developer?
I can see the package and package body but can not find the .ddl files.
here I am attaching the clearcase terminal commands and responses:
denoad32:ddl $ cleartool lsco -me
--04-03T03:02 Sayan.Sikdar checkout version "XXONT_OH_REL_SC_HOLD_PB.ddl" from /main/R12/8 (reserved)
--04-03T03:02 Sayan.Sikdar checkout version "XXONT_OH_REL_SC_HOLD_PS.ddl" from /main/R12/3 (reserved)
What I am doing right now is I have check the files out. Now that I have checked the files out I am copying it from their current location to my view home. Then I am downloading it and using it.
Basically, you have checked out the files with the command "cleartool co ". in order to be able to access the files, you need to be inside your Clearcase view. If you are in the same session as when you performed the check out, you should have access to the files you have checked out.
The usual workflow is :
checkout the file
modify and save the file
checkin the file
All these must be done inside a Clearcase view.
download them to pc and use them?
If your PC has a ClearCase Client, it can host a ClearCase view (snapshot or dynamic) and will download automatically checked out files.
is there any other way to generate the ddl files from PL/SQL developer
If there is, that would explain why you don't see those files: they can be generated.
pg_dump -U user_name -h host database -s -t table_or_view_names -f table_or_view_names.sql
I'm using a .bat file for installation purposes and I'm using ".\" very often when I need to access files (for example for an unzip) in order so get which directory I'm in.
It worked quite well until yesterday when suddenly I had 2 different behaviours:
Lauched from command console (with the console inside the directory): The file works as normal and knows where .\ is at.
Launched from windows explorer it also functions if it is not started with administrator rights
If launcehd from windows explorer with administrator rights the executing directory (thus the directory which is printed with cd if its the first command in the .bat file) suddenly is c:\windows\system32
This behaviour like I said started just a few days ago (2 days ago we saw it for the first time when we tried that .bat file), before that it worked from windows explorer exactly the same as from the command console.
So my question here is twofold:
Is there anything known as to the cuase of this changed behaviour?
How can I get a handle to the current directory that the .bat file is located in (because the .zip file will always be in the same directory as the .bat file itself), thus how can I solve this problem as I need to start the file with administrator privileges
I found that there is a similar issue in windows vista:
Windows batch file starting directory when 'run as admin' although what intrigues me there is why the problem did not appear for weeks and only appeared recently with windows 8
Use this as the line after #echo off:
cd /d "%~dp0"
It will change the working directory to be where the batch file is located.
I am trying to run this command in jenkins after a MSbuild
xcopy "C:\Program Files (x86)\Jenkins\workspace\trunk\Projects\results\results\obj\Debug\Package\PackageTmp" "Y:\Extraction_Zone\Jenkins\" /E
Y: is a mapped network drive. This runs fine in cmd.exe but when trying to run it in Jenkins, I am getting the error Invalid drive specification.
Here is the output from jenkins:
Time Elapsed 00:00:04.03
[trunk] $ cmd /c call C:\Windows\TEMP\hudson3389873107474371072.bat
C:\Program Files (x86)\Jenkins\workspace\trunk>xcopy "C:\Program Files (x86)\Jenkins\workspace\trunk\Projects\results\results\obj\Debug\Package\PackageTmp" "Y:\Extraction_Zone\Jenkins\" /E
Invalid drive specification
0 File(s) copied
C:\Program Files (x86)\Jenkins\workspace\trunk>exit 4
Build step 'Execute Windows batch command' marked build as failure
Finished: FAILURE
Any help would be appreciated.
I too had a similar issue once. Try granting the Jenkins service "Logon as This account" right under services.msc and make sure the account you type there is the same as the one you use for running cmd.exe.
These commands based on Java JAR files worked for me:
cmd
net use x: \\
xcopy "dist\" x:\ /Y
And that's it! I spent lot of time figure out this issue and nothing worked until I wrote CMD and NET USE!
Neither I didn't need to change permission on jenkins service nor use runas command.
But I must mention that everyone had read and write access to the network drive.
I had the same issue with my Windows Task running a batch file (I know it is not exactly same) where I tried to copy file to network location i.e. shared drive. I used the UNC path and mapped drive as well but the error was same. For me it was error number 4 - MS DOS error code.
The solution was to use net use command! Hope that it helps.
Easy fix for most things.
Make a batch command with what your trying to run, filename.bat with the command prompt text inside.
Make a normal windows shortcut for the batch command, edit the shortcuts advanced properties and check the "Run as admin" (tricky tricky).
Now run the filename.lnk shortcut from jenkins command line call, this will get you around all the jazz.
:)
The solution of adarshr (i.e., modifying the log on credentials of the service) has worked for me for a part of the problem: in my case, this allowed me to successfully check out a mercurial repository (using ssh protocol), which I could not do when using 'Local System account'.
However, I still have different behavior between running a command-line script or running the same script from a jenkins 'execute shell' script in the build section. In my case, I compile a Python extension. In Jenkins, I cannot import the extension (I don't see any error, but the execution simply stops, so I suspect it crashes).
If I uninstall the service and run the slave agent as a Java Web Start, I do get the same behavoir. It is a temporary fix for me, but it means that when I reboot the windows build machine, I have to manually re-start the Java Web Start application.
So -at least in my case- it is clear that this is a credential problem.
Credentials usage documentation: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI
I've solved my issue with the CIFS plugin.
Faced similar issue and found two ways to solve.
Type 1:
Tell Jenkins about mapped drive.
1.Goto -> Manage Jenkins -> Script Console (Groovy Script).
2.Run below command
def mapdrive = "net use Y: \\\\copy_nework_address"
mapdrive.execute();
println "net use".execute().getText()
Type:2
1.Goto -> cmd -> run "net use" to know network address
xcopy "C:\Program Files (x86)\Jenkins\workspace\trunk\Projects\results\results\obj\Debug\Package\PackageTmp" "Copy_Network_Address\Extraction_Zone\Jenkins\" /E
Conclusion:- I prefer 2nd types as after every restart i should run Groovy Script.