I'm facing this error while try to config my Stratos - Partition Deployment it is always give me this error :
Error while getting available partitions. Cause : The service cannot be found for the endpoint reference (EPR) https://x.x.x.x:9443/services/AutoscalerService/
any suggested ideas ?!
Regards,
It looks like stratos manager cannot reach Autoscaler on the given endpoint. Is it possible for you to check whether you can telnet from the stratos manager host to Autoscaler IP, 9443?
If you could mention the stratos version and the deployment model (single jvm/distributed) you are using, we could provide a much better answer.
The cause is the wrong definition of the autoscaler endpoint in the /repository/conf/cartridge-config.properties file. Check if the specified IP address is reachable from the stratos manager, and check that /etc/hosts is updated with the specified domain name in the cartridge-config.properties.
Related
While creating destination to my hana system. I face the error 'Backend is not available in the list of defined system mappings in Cloud connector' in the connection test.
The connection in cloud connector is reachable. I read through blogs, the virtual and internal address doesn't mismatch. the url doesn't have any '_', but still I face the error. Any leads to this kind of issue?
Thanks
Issue is resolved by deleting the location id in the destination settings
When I use jconsole to access weblogic's mbean,I just can get some info about jvm like 'java.lang'.But what I want to get is about 'jdbc','jta','ejb','servlet'...
I wonder if I can get these indicators through service:jmx:rmi:///jndi/rmi://10.0.99.102:7997/jmxrmi with username and password.I think it's very likely that my configuration has errors, but I don't know where the problem is.
Then I tried another way.I enabled iiop, but I can't access it via iiop.
I met some errors like Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException.
Try to figure this error,I add wljarbulder.jar to my project,then another error comes out,'Unhandled exception in lookup,Caused by: javax.naming.NamingException Unhandled exception in lookup [Root exception is org.omg.CORBA.NO_PERMISSION...'.
All I need is to get the mbean information for weblogic, I am trying to monitor weblogic via jmx.
(I have collected weblogic's snmp oid, but it is not enough to complete my monitoring plan)
Thank you.
Actually,I figure out the problem.
It seems that the iiop default username and password must be set the same as weblogic Admin.
I don't understand why for this,but when I read one blog and try,then I get the data.
I'm not sure that I can get all the mbean data through this,but it connects successful at least and show a lot of data.
I should have used jconsole to find the value I want now.emmm,but I cannot connect by jconsole.But this is the next question.
First add these parameters to your WebLogic Server instance :
-Dcom.sun.management.jmxremote
-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
-Dcom.sun.management.jmxremote.port=6789
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
Second, launch jconsole :
jconsole.exe -J-Djmx.remote.protocol.provider.pkgs=weblogic.management.remote -J-Djava.class.path=%JAVA_HOME%\lib\jconsole.jar;%WL_HOME%\server\lib\weblogic.jar;%JAVA_HOME%\lib\tools.jar
and connect to port 6789
I'm unable to solve the below error since hours in Solr Admin. Please help me.
Unable to resolve canonical hostname for local host, possible DNS misconfiguration. Set the 'solr.dns.prevent.reverse.lookup' sysprop to true on startup to prevent future lookups if DNS can not be fixed.
The standard JVM accepts -D<param name>=<value> to set global configuration values available to the running application.
Depending on how you're starting Solr, you can edit solr.in.cmd in Windows or solr.in.sh in Linux or OS X.
Search for SOLR_OPTS and see how it uses -D... parameters to set new values. -Dsolr.dns.prevent.reverse.lookup=true is what you'd add as a setting like this.
Fixing DNS would be to make sure that localhost resolves locally at least.
The most direct way to fix this issue is to start Solr with the system property solr.dns.prevent.reverse.lookup=true in the command line.
For instance under Windows in a PowerShell console :
bin\solr.cmd start "-Dsolr.dns.prevent.reverse.lookup=true"
Hi I've been trying to try out the Fiware service.
I've setup an POI Instance in the Waterford Region.
I've followed the instructions and assigned a floating IP.
On the Instance page I have no IP address and an Status Error.
Under the security page -> Floating IP tab there is an IP address assigned. The Instance is blank. When I try and associate an IP to the instance i get a 400 error:
undefined. Cause: 400 Error
{"badRequest": {"message": "No nw_info cache associated with instance", "code": 400}}
Has anyone had the same problem?
Have you used the 'Allocate IP to project' menu under the Security Tab first ?
If you have a floating IP available it should be connected to the instance you've created using the Associate IP -Action under the Security/Floating IP's. Remember to also allocate and connect the keys and open relevant ports as described here: http://catalogue.fiware.org/enablers/poi-data-provider/creating-instances
There has been some resource (floating IPs) limitations in the FILAB cloud servers so this may be also the reason if you have followed all the above.
Currently, there seems to be some problems with the POI GE image in the Fiware Cloud. Currently a working choice is to start an Ubuntu 14.04 image and install the POI GE according to http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/POI_Data_Provider_-_Installation_and_Administration_Guide .
While I was trying to start ApacheDS 1.5.7 on windows platform, An Error 04450 occurs and the apacheds-rolling.log contains:
[21:07:27] ERROR [org.apache.directory.shared.ldap.entry.DefaultServerAttribute] - ERR_04450 The value {0} is incorrect, it hasnt been added
[21:07:27] ERROR [org.apache.directory.server.Service] - Cannot start the server : reuseAddress can't be set while the acceptor is bound.
How can i fix this problem? Anybody could help me? many thanks!
The warning log message is a bit misleading, actually this is not a serious issue, the server should be running despite of this warning, this has been fixed a while back in the latest trunk code (which will be released as 2.0 instead of 1.5.8).
According to this post, the dc=example,dc=org context entry is not created by default anymore but no one has updated the documentation to reflect this. I installed 1.5.7 and it looks to me like the partition was created fine, but I'm getting the same error as described above. I suggest installing an older version.
The 2nd error message suggests that the port is already in use. Is there a chance that you already had another ApacheDS process running, or that another program is using the ports?
This isn't a domain controller perchance, is it? If so, the default LDAP ports 389 & 636 are already in use for Active Directory, so you'll need to choose another. However, I believe the defaults for ApacheDS are 10389 (LDAP) and 10636 (LDAPS), in which case they would typically be open on a Windows box.
You can check for processes on the ports with the netstat -abn command, and look through the list for the process listening on port 10389 or whichever custom port you chose.