I followed this tutorial:
http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.appadmin.doc/admin/r_invoking_the_wladm_program.html
I'm trying to enter a command in cmd and tried this:
wladm --url=http://IP:9080 --user=demo --passwordfile=PATH\wladm.config --secure=false show info
I'm getting this error:
Error accessing http://IP:9080/userAndConfigInfo?locale=en_US:
HTTP/1.1 404 Not Found
Now when I enter another command:
wladm --url=http://IP:9080 --user=demo --passwordfile=PATH\wladm.config --secure=false list adapters RuntimeName
I'm getting this error:
Error accessing http://sv591527.ph.sunlife:9080/management-apis/1.0/runtimes/Sun
lifeTestApp/adapters?pageSize=1000000000&locale=en_US: HTTP/1.1 404 Not Found
Anyone have an idea what I'm missing?
The URL should contain the context root of the MobileFirst web application for administration services, that is, should be something like http://IP:9080/wladmin or http://IP:9080/worklightadmin. For more details, please consult the wladm usage documentation http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.appadmin.doc/admin/r_invoking_the_wladm_program.html.
Related
While running jython py script with adminApp.install to install on Docker WAS, I'm getting the Error:
WASX7017E: Exception received while running file
"deployWebSphere_with_install_standAlone.py"; exception information:
com.ibm.websphere.management.filetransfer.client.TransferFailedException:
401 Unauthorized (for:
C:\Users\devopsjava\AppData\Local\Temp\app5674632847255103189.ear).
I tried give full control on this path,
I tried set custom property:com.ibm.websphere.management.filetransfer.serverBasicAuth=true
(https://www-01.ibm.com/support/docview.wss?uid=swg1PK71800)
My code:
options = ['-node ',node,'-cell ',cell,"-server ",server]
print AdminApp.install(packageFile, options)
I always get :
WASX7017E: Exception received while running file
"deployWebSphere_with_install_standAlone.py"; exception information:
com.ibm.websphere.management.filetransfer.client.TransferFailedException:
401 Unauthorized (for:
C:\Users\devopsjava\AppData\Local\Temp\app5674632847255103189.ear).
Maybe, I need to set some more property, or there is problem with security between docker domain and the outside world ?
I can access my site in the browser with the following path: my-dash.docker.localhost:8000. Also, as I found here in order to access the site via POSTMAN I had to add to my host file:
127.0.0.1 my-dash.docker.localhost
I updated my phpunit.xml:
<env name="SIMPLETEST_BASE_URL" value="http://my-dash.docker.localhost:8000"/>
When I run my test I get the following error:
1) Drupal\my_dashboard\Tests\Rest\MyDashboardResourceTest::testPost
GuzzleHttp\Exception\ConnectException: cURL error 7: Failed to connect to my-dash.docker.localhost port 8000: Connection refused (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)
/var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:186
/var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:150
I verified that if I add a know url, I don't get this error:
<env name="SIMPLETEST_BASE_URL" value="https://www.google.com/"/>
I found the answer here. Updated phpunit.xml:
<env name="SIMPLETEST_BASE_URL" value="http://nginx"/>
Also in my case, I was using Drupal and had trusted hosts set in my settings.php. I also had to add nginx as a trusted host.
I have installed alfresco & solr in different tomcat instances using below docs url. alfresco share was running file but when i run solr instance and see below error.
http://docs.alfresco.com/5.1/tasks/solr4-install-config.html
generated secure keys for Solr communication.
http://docs.alfresco.com/5.1/tasks/generate-keys-solr4.html
2016-07-18 13:25:30,037 ERROR [solr.tracker.AbstractTracker] [SolrTrackerSche
ler_Worker-14] Tracking failed
org.alfresco.error.AlfrescoRuntimeException: 06180034 api/solr/aclchangesets
turn status:403
at org.alfresco.solr.client.SOLRAPIClient.getAclChangeSets(SOLRAPIClie
.java:162)
at org.alfresco.solr.tracker.AclTracker.checkRepoAndIndexConsistency(A
Tracker.java:335)
at org.alfresco.solr.tracker.AclTracker.trackRepository(AclTracker.jav
313)
at org.alfresco.solr.tracker.AclTracker.doTrack(AclTracker.java:104)
at org.alfresco.solr.tracker.AbstractTracker.track(AbstractTracker.jav
185)
at org.alfresco.solr.tracker.TrackerJob.execute(TrackerJob.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool
ava:563)
2016-07-18 13:25:30,029 ERROR [solr.tracker.AbstractTracker] [SolrTrackerSche
ler_Worker-6] Tracking failed
org.alfresco.error.AlfrescoRuntimeException: 06180033 api/solr/aclchangesets
turn status:403
at org.alfresco.solr.client.SOLRAPIClient.getAclChangeSets(SOLRAPIClie
.java:162)
at org.alfresco.solr.tracker.AclTracker.checkRepoAndIndexConsistency(A
Tracker.java:335)
at org.alfresco.solr.tracker.AclTracker.trackRepository(AclTracker.jav
313)
at org.alfresco.solr.tracker.AclTracker.doTrack(AclTracker.java:104)
at org.alfresco.solr.tracker.AbstractTracker.track(AbstractTracker.jav
185)
at org.alfresco.solr.tracker.TrackerJob.execute(TrackerJob.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool
ava:563)
2016-07-18 13:25:30,056 ERROR [solr.tracker.AbstractTracker] [SolrTrackerSche
ler_Worker-11] Tracking failed
org.alfresco.error.AlfrescoRuntimeException: 06180036 GetModelsDiff return st
us is 403
at org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.
va:1157)
at org.alfresco.solr.tracker.ModelTracker.trackModelsImpl(ModelTracker
ava:249)
at org.alfresco.solr.tracker.ModelTracker.trackModels(ModelTracker.jav
207)
at org.alfresco.solr.tracker.ModelTracker.doTrack(ModelTracker.java:16
at org.alfresco.solr.tracker.AbstractTracker.track(AbstractTracker.jav
185)
at org.alfresco.solr.tracker.TrackerJob.execute(TrackerJob.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool
ava:563)
I had a similar problem which has been solved by changing
clientAuth="false"
to
clientAuth="want"
in Tomcat 7 server.xml
(credit goes to https://issues.alfresco.com/jira/browse/ACE-4551?focusedCommentId=424920&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-424920)
I install and user Crucible+FishEye on http://mydomen:8060
work several month - all works, integration with jira was worked.
I create http://crucible.mydomain (in other physic server) - with nginx proxy on localhost:8060, install Crucible+FishEye and restore from backup.
And now i get erro in jira tasks Source and Rewiev tab:
This list of reviews may be incomplete, as errors occurred retrieving data from the following repositories:
Request to http://mydomen:8060/ failed: Error in remote call to 'mydomen' (http://crucible1.mydomen) [AbstractRestCommand{path='rest-service/search-v1/reviews', params={maxReturn=50, term=XM-911}, methodType=GET}] : Received status code 404 (Not Found)
Request to http://crucible.mydomain/ failed: Error in remote call to 'Crucible+FishEye' (http://mydomen:8060) [AbstractRestCommand{path='rest-service/search-v1/reviews', params={maxReturn=50, term=XM-911}, methodType=GET}] : The host did not accept the connection within timeout of 10000 ms
Why it try connected on http://mydomen:8060 ??
In my Crucible > Administration > Global settings > Server > HTTP Bind=crucible.mydomain
I found solution: I need recreate Application links in http://jira.mydomen/plugins/servlet/applinks/listApplicationLinks
I get a 500 error when I try to run the site's backend in IE.
Apache error log.
Symfony error - PHP Fatal error: Class 'sfPropelRouteCollection' not found in
\\cache\\backend\\prod\\config\\config_routing.yml.php on line 5
I tried investigating config_routing.yml.php and it appears that it's calling a new sfPropelRouteCollection class, and cannot find it.
I found the file containing it in:
\lib\vendors\symfony\lib\plugins\sfPropelPlugin\lib\routing\sfPropelRouteCollection.class.php
I cleared the cache several times, that didn't help.
The frontend of the site is running normally