Unable to start the App Server from the command line - websphere-8

I cloned Websphere application machine and changed the hostname by the wsadmin.sh script.
DMGR and Node started successfully but when I start the server I got this error:
ADMU0111E: Program exiting with error: java.io.FileNotFoundException: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/CELL01/nodes/AppNode/servers/server01/server.xml (No such file or directory).
Note: I can start the server from the console only

The problem recovered after synced the node with master configuration and granted read/write permission for directive /opt/IBM/Webspere and its relative sub directives, Thanks all for your contributions and support.

Related

Error staging application: App staging failed in the buildpack compile phase in HWC Buildpack

I am trying to deploy my application built in ASP.Net 4.6.1. So I am using HWC Buildpack.
Below is my manifest.yml
---
applications:
- name: DRSN
random-route: true
memory: 128M
buildpack:
https://github.com/cloudfoundry/hwc-buildpack.git
env:
DOTNET_CLI_TELEMETRY_OPTOUT: 1
DOTNET_SKIP_FIRST_TIME_EXPERIENCE: true
The error that I am receiving is below.
Waiting for API to complete processing files...
Staging app and tracing logs...
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 creating container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 successfully created container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Downloading app package...
Downloading build artifacts cache...
Downloaded build artifacts cache (231B)
Downloaded app package (19.5M)
Failed to compile droplet: Failed to compile droplet: fork/exec /tmp/buildpackdownloads/6c6dca8d638ac0d145d6581f9eb9a96a/bin/compile: permission denied
Exit status 223
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 stopping instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Cell 0f7012eb-9e32-4fdf-ba92-85aee4639139 destroying container for instance 34107c3c-1acb-4aa5-b435-b06516abcfcb
Error staging application: App staging failed in the buildpack compile phase
Can anyone help me resolve this issue? Am I not correct in my manifest.yml? Or is it something else?
I believe that the problem is that you're telling the system to use the HWC buildpack, but at the same time you're not setting the Windows stack (at least based on what info I can see). That means it's going to default to the Linux stack, which I believe is why you're seeing the fork/exec /tmp/buildpackdownloads/... error.
Try adding stack: windows to your manifest.yml or -s windows to your cf push command (for future reference, when you need help always include the full cf push command you're running).
PS: you shouldn't use https://github.com/cloudfoundry/hwc-buildpack.git that is telling the system to grab the master branch in whatever state it's currently in. That's a.) not reproducible and b.) not guaranteed to be in a working state. You should either use the platform provided buildpack names (from cf buildpacks) or append #<branch_or_tag> to the end of the URL so it picks a specific branch. All CF Buildpacks have tags for each release. It's strongly recommended you use a tagged release.

Execution failed for task ':kotlin-source:compileKotlin'

I tried to run the cordapp-example from the command prompt. But when I input the "gradlew.bat deployNodes" command, I got the error as below.
Execution failed for task ':kotlin-source:compileKotlin'.
Could not resolve all dependencies for configuration ':kotlin-source:compileClasspath'.
Could not determine artifacts for org.jolokia:jolokia-war:1.3.7
Could not get resource 'https://jcenter.bintray.com/org/jolokia/jolokia-war/1.3.7/jolokia-war-1.3.7.war'.
Could not HEAD 'https://jcenter.bintray.com/org/jolokia/jolokia-war/1.3.7/jolokia-war-1.3.7.war'.
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target
I had done the "keytool -importcert" command to import the certificate of jolokia-war into java cacerts, but the error was still there.
Does anyone know how to solve the problem?
The error message indicates that the compilation failed because your machine was unable to download the resource at this location: https://jcenter.bintray.com/org/jolokia/jolokia-war/1.3.7/jolokia-war-1.3.7.war.
This URL works for me and I was able to download the resource. You are most likely behind a firewall or otherwise unable to download this resource. You need to make your machine able to access this resource to compile and deploy the node.

Could not authorize while connecting to the SonarQube server. Check your credentials and try again

I am trying to run SonarQube for my Xamarin Forms project, I am on the path where my .SLN file is there and executing the following command
Command:
$ mono /Users/akandasamy/Development/HIDProjects/sonar-scanner-msbuild-4.0.2.892/MSBuild.SonarQube.Runner.exe begin /k:"HIDReaderManagerApp" /d:sonar.host.url="http://localhost:9000" /d:sonar.login="My Login Token"
Error:
SonarQube Scanner for MSBuild 4.0.2
Default properties file was found at /Users/akandasamy/Development/HIDProjects/sonar-scanner-msbuild-4.0.2.892/SonarQube.Analysis.xml
Loading analysis properties from /Users/akandasamy/Development/HIDProjects/sonar-scanner-msbuild-4.0.2.892/SonarQube.Analysis.xml
Pre-processing started.
Preparing working directories...
17:29:10.391 Updating build integration targets...
17:29:10.414 Fetching analysis configuration settings...
17:29:10.517 Failed to request and parse 'http://localhost:9000/api/settings/values?component=HIDReaderManagerApp': The remote server returned an error: (401) .
17:29:10.517 Could not authorize while connecting to the SonarQube server. Check your credentials and try again.
17:29:10.518 Pre-processing failed. Exit code: 1
The api/settings/values API requires Browse permission when the component argument is used. Please, see if the user you are authenticating with has the aforementioned permission.
More details about security and permissions here:
https://docs.sonarqube.org/latest/instance-administration/security

glass fish 3.1.2 start failed in netbeans 7.2

I've installed Netbeans 7.2. with GlassFish Server 3.1.2 but when I run web application the default jsp page or any other jsp pages I got the error:
GlassFish Server 3.1.2 Start Failed
C:\Users****\Documents\NetBeansProjects\WebApplication3\nbproject\build-impl.xml:1022:
Deployment error: GlassFish Server 3.1.2 Start Failed See the server
log for details. BUILD FAILED (total time: 47 seconds)
build-impl.xml
< target depends="init,-init-cos,compile,
compile-jsps,-do-compile-single-jsp,-pre-dist,-do-tmp-dist-with-manifest,-do-tmp-dist-without-manifest,-pre-run-deploy,
-pre-nbmodule-run-deploy,-run-deploy-nb,-init-deploy-ant,-deploy-ant,-run-deploy-am,-post-nbmodule-run-deploy,-post-run-deploy,
-do-update-breakpoints" name="run-deploy"/>
< target if="netbeans.home" name="-run-deploy-nb">
< nbdeploy clientUrlPart="${client.urlPart}" debugmode="false"
forceRedeploy="${forceRedeploy}"/>
////////////////////////
glassFish Server 3.1.2
SEVERE: Shutting down v3 due to startup exception : No free port
within range:
8080=com.sun.enterprise.v3.services.impl.monitor.MonitorableSelectorHandler#788a7b
I've found the solution. My 8080 port was reserved by Oracle. So I edited the domain.xml file inside glassfish\domains\domain1\ config\domain.xml file.
I replaced the port 8080 with 9999 and replaced the file. After that I added the glassfish server to netbeans, and now it is working.
Thank You everyone.
The error message states it clearly:
No free port within range: 8080
Probably there is another instance of Glassfish (or any other server) running on your system. Try to find it out by calling http://localhost:8080 in your browser.
**Another option to solve this probs
**Enter the following on the command line:
netstat -ao
The active TCP addresses and ports will be listed — locate the line with local address “0.0.0.0:80″ and note the PID value.
Now right-click the task bar and select Start Task Manager. Navigate to the Processes tab and, if necessary, click View > Select Columns… to ensure “PID (Process Identifier)” is checked. You can now locate the PID you noted above. The description and properties should help you determine which application is using the port.
The Task Manager allows you to kill the process, but be a little wary about doing that — especially if it’s “NT Kernel & System”.**
i had the same problem.
i solved it by configuring the glassfish with jdk7 instead of jdk8.
i dont know why it wasnt working with jdk8 but now the glassfish is running.

Deployment error message in Jeveloper

I am deploying my BPEL project on Web-logic server through my JDeveloper 11g. its working fine. but when I selected my different environment for deployment(new one) then I got the following error.
Error is due to one of my BPEL prcess "TaskProcess1".
but the same setup when I deploy to my own server its deploying and running very fine.
code=500
[04:53:57 PM] Error deploying archive sca_RegistrationUpload_rev24.0.jar to partition "default" on server DAMS_Batch_Server1 [urasvr140.uradevt.gov.sg:8001, Cluster:DAMS_Batch_Cluster]
[04:53:57 PM] HTTP error code returned [500]
[04:53:57 PM] Error message from server:
#;There was an error deploying the composite on DAMS_Batch_Server1: Operation failed - Member(Id=1, Timestamp=2011-06-02 15:25:57.428, Address=172.16.10.45:8088, MachineId=46637, Location=site:uradevt.gov.sg,machine:urasvr140,process:3968, Role=WeblogicServer):Error occurred during deployment of component: TaskProcess1 to service engine: implementation.bpel, for composite: RegistrationUpload: ORABPEL-01005
#;
#;Failed to compile bpel generated classes.
#;failure to compile the generated BPEL classes for BPEL process "TaskProcess1" of composite "default/RegistrationUpload!24.0*soa_f19c6537-e518-4c05-940c-688c1ddb2593"
#;The class path setting is incorrect.
#;Ensure that the class path is set correctly. If this happens on the server side, verify that the custom classes or jars which this BPEL process is depending on are deployed correctly. Also verify that the run time is using the same release/version.
#;; . Please see the server diagnostic logs on DAMS_Batch_Server1 for details.
Please let me know if any suggestion you have.
Is there a dependant jar file that you are accessing from your bpel process?
Check the log files on the server for the soa_server. It will give you more information as to why it failed at the server

Resources