I have installed and configured weblogic with chef but struggling to start weblogic server and nodemanager with chef "Service" resource.
I tried with bash resource to directly run the startweblogicerver.sh file, however the process is not exiting and when I tried putting & at end then chef run successfully but weblogic didn't started.
Related
I am trying to restart my node by running StartNode.bat in cmd. But it is giving me the following error,
ADMU0111E: Program exiting with error: java.io.FileNotFoundException: C:\Users{userid}\workspaces\was_profiles{profilename}\config\cells\localcell\nodes\localnode\servers\nodeagent\server.xml (The system cannot find the path specified.) When I checked the above path, server.xml is present in the path C:\Users{userid}\workspaces\was_profiles{profilename}\config\cells\localcell\nodes\localnode\servers\server1\server.xml. I am not sure how to restart my node. Also, I am restarting the node, since I get ORA error invalid username/password issue while trying to test my datasource connection in IBM websphere.
Most of the posts suggest me to restart websphere server and nodeagent as well. Eventually, when I start the nodeagent, I get the above error. I tried to use syncNode command, but could not find the deployment manager host name, port details for my application.
It looks like you have single server version installed, not network deployment. In that case you dont have node and deployment manager, but just single server.
You should use commands like:
startServer.bat server1 - to start the server
stopServer.bat server1 - to stop server
We are using Amazon AWS Ubuntu machine for our server.
Rails 4.2.7 and Ruby 2.3
I have installed redis with these instructions (Redis)
and installed sidekiq with Sidekiq
I started redis, then starting sidekiq with just bundle exec sidekiq it give me error as running the jobs
FATAL: password authentication failed for user "ubuntu"
Not sure why this error. Any suggestions ?
Closing this thread as it has been fixed.
Changed the permissions for Redis from root level to user level.
And running sidekiq in production mode.
I installed multiple instances of Tomcat in my Ubuntu machine. I was trying to start Tomcat (one of the instances from multiple Tomcat instances) from Jenkins. Jenkins is showing that Tomcat started. But Tomcat is still in shutdown state only.
In jenkins, When an build completes all the process Id's which are involved in the build are getting killed.
So mentioning BUILD_ID=dontKillMe ./home/tomcat/startup.sh in Execute shell script make it possible.
How do you "start a node agent" in Websphere ?
The error message is:
"Server cannot be started because the node agent for server x_server on node wasdev1Node01 is not active."
(I am on the dev server.)
Also, the app logon procedure errored because of "Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. ". While trying to start the JINDY I got the node server message.
When I try to start the application server:
"Server cannot be started because the node agent for server wasdev1 on node wasdev1Node01 is not active."
Starting the Node Agent from the console:
"The node agent on node wasdev1Node01 must be started to perform the restart operation. Node agents in stopped state can not be started from the console."
You would need to start the node agent from command line as below.
WAS_HOME/profiles/YOUR_PROFILE_NAME/bin/startNode.cmd (I do not have this command.)
You would have the startNode.sh or startNode.cmd command linked in your profile's bin directory if your profile was created from a Network Deployment installation and your node had been federated into a cell. If your profile is a standalone application profile that has not been federated, there should not be a startNode command available.
Looking at the error you are running ND not standalone/base version. You cannot start the nodeagent from the console (only stop and restart.
startNode.sh(.bat) from command line to start the nodeagent. Make sure nodeagent process/pid is not present. As for the applicatin servers defined under the node, they need Location Daemon Service running on the node to start.
Yes if the error appears only thing you need to start nodeagent from your appsrv profile/bin with command prompt only if you install on windows environment.
you should open as command prompt as administrator privileges and then go to profile path and run startNode.bat or .sh .
I am trying to get Jenkins to start a virtual machine on a Jenkins slave. The VM itself will then act as a Jenkins slave.
In order to do so I need to boot the VM and keep it running, even after the Jenkins job terminates. I have tried to create a freestyle project which runs a batch script on the slave and checks if the VM is running:
"C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe" -T ws start "D:\VM\MyVM.vmx"
"C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe" list
The second command shows me that the VM is actually up and running, but apparently it directly shuts down again since I can't see the node that corresponds to the VM as online.
The Jenkins Slave agent is installed as a Windows service on the VM's host and logs in as a domain user.
If I switch the first command to
"C:\Program Files (x86)\VMware\VMware Workstation\vmware.exe" -x "D:\VM\MyVM.vmx"
the VM powers on, the node gets connected to Jenkins. This is because somehow the batch script gets stuck after this command and does not terminate, so the VM remains powered on. However, if I log on the host with the same user the Jenkins service uses, I cannot see the VM running.
Ironically, I can in fact power OFF any virtual machine that I have started locally on the host from Jenkins by creating a project with the batch command
"C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe" -T ws stop "D:\VM\MyVM.vmx" soft
So, to summarize:
I want to create a Jenkins job that powers on a VM so I can use it as a slave agent. The VM has to remain powered on even after the job is done, I will shut it down with a different job as needed.
But only the shutdown job is working as intended.
try to start your VM with START command:
START "C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe" -T ws start "D:\VM\MyVM.vmx"
After playing around with VMs and Jenkins today I learned that vmrun works perfectly if the Jenkins slave does not run as a Windows service but is launched via the Java Webstart application.
Besides, one can prevent processes from getting killed by altering the BUILD_ID env. variable since Jenkins is using this variable to track the processes the build launched. So by changing the value of BUILD_ID before spawning processes they won't get killed after the Job finishes.