Enviroment:
Server Almalinux 8.7
java: java-11-openjdk-11.0.17.0.8-2.el8_6.x86_64
Micro integrator installed (4.1.0) Micro Integrator Dashboard installed (4.1.0)
The micro-integrator connects to the Dashboard, but when I try to login, the dashboard says "No running micro integrator instances found. Pls start a server a login":
The MI runs after the dashboard. The dashboard registers de MI as per below log line, but when I try to login it says that no MI is running....
New node dev_node_2 in group : mi_dev is registered. Inserting heartbeat information ERROR {LoginDelegate} - No running micro integrator instances found. Please start a server and login.
I verified the default "-DenableManagementApi=true" system parameter value in micro-integrator.sh.
What else can I do?
The MI node might not be registering its hostname properly. Along with the dashboard url, please try configuring MI's hostname and port as well.
[dashboard_config]
dashboard_url = "https://{hostname/ip}:{port}/dashboard/api/"
management_hostname = "<HOST_NAME>"
management_port = <PORT>
Related
Enviroment:
1 Linux Serves
Micro integrator installed (4.1.0)
Micro Integrator Dashboard installed (4.1.0)
The micro-integrator connects to the Dashboard, but when I try to login, the dashboard says "No running micro integrator instances found. Pls start a server a login":
any help?
Thanks!
Daniel
I reviewed both deployment.toml files, and everything seems to be ok.
You need to configure the mi with the dashboard. This config needs to be added at each mi node.
[dashboard_config]
dashboard_url = "https://{hostname/ip}:{port}/dashboard/api/"
heartbeat_interval = 5
group_id = "mi_dev"
node_id = "dev_node_2"
More information can be found in here[1].
[1] - https://apim.docs.wso2.com/en/latest/observe/mi-observe/working-with-monitoring-dashboard/#step-2-configure-the-mi-servers
Make sure you start the MI dashboard first and after the dashboard is up and running start the MI server. Please verify the configs you have added with the configurations mentioned here[1].
[1] https://apim.docs.wso2.com/en/latest/observe/mi-observe/working-with-monitoring-dashboard/
I'm unable to start the WSO2am 3.0.0 . I have to replicate WSO2am from an environment. But when I do so, the service doesn't start , it keeps printing warning messages saying it cannot fetch certain things from the remote endpoint. This is a single node setup, with nginx as reverse proxy, and running on Amazon VM(Amazon linux 2) and RDS(MySql).
Attached are the screenshots of the logs printing the warnings.screenshot1 screenshot2
my scenario is about two servers one running wso2 api manager and one running wso2 analytics and I want to show statics of api manager on analytics server .how to configure this servers? (analytics dashboard conf , analytics worker conf , api manager conf) thanx
WARN {org.wso2.msf4j.internal.MSF4JHttpConnectorListener} - Unmapped exception
feign.RetryableException: No subject alternative names matching IP address 192.168.115.132
found executing GET https://192.168.115.132:9443/api/am/admin/v1/custom-urls/carbon.super
This is due to the hostname verification. The recommended option is to use proper certs with hostnames. Otherwise, you can disable hostname verification by adding the following.
hostnameVerificationEnabled: false
https://github.com/wso2/docker-apim/blob/3.2.x/docker-compose/apim-with-analytics/conf/apim-analytics-dashboard/conf/dashboard/deployment.yaml#L25
I can't launch wso2 micro-integrator 7.0.1. I launch files micro-integrator.sh or launcher_micro-integrator.sh or command wso2mi, after that i have strings in logs (look below), after that nothing, MI isn't loaded later. What is wrong? My Java_Home is correct. User who launches MI has all permissions on MI directory.
INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - Pass-through HTTP Listener started on 0.0.0.0:8290
INFO {org.apache.axis2.transport.mail.MailTransportListener} - MAILTO listener started
INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - Pass-through HTTPS Listener started on 0.0.0.0:8253
INFO {org.wso2.micro.integrator.initializer.StartupFinalizer} - WSO2 Micro Integrator started in 4 seconds
According to the below log, your Micro integrator has started successfully.
INFO {org.wso2.micro.integrator.initializer.StartupFinalizer} - WSO2 Micro Integrator started in 4 seconds
Micro integrator is starting in a very little time compared to the WSO2 Enterprise integrator and does not have the Mgt console capability of WSO2 Enterprise Integrator. However, you can access MI monitoring dashboard by referring to this doc.
Please check this quick start guide for more details on WSO2 Micro integrator.
I'm running WSO 5 components cluster (KeyManager, Gateway, Publisher, Store, Traffic Manager), each component has his own server and they are all exist in the same LAN.
Finally i got to a point where every component is running with no errors and i get this message below,
[2018-02-23 23:42:12,475] INFO - StartupFinalizerServiceComponent Server
: WSO2 API Manager-2.1.0
[2018-02-23 23:42:12,476] INFO - StartupFinalizerServiceComponent WSO2
Carbon started in 54 sec
[2018-02-23 23:42:12,720] INFO - CarbonUIServiceComponent Mgt Console URL
: https://172.31.25.234:9443/carbon/
[2018-02-23 23:42:12,720] INFO - CarbonUIServiceComponent API Publisher
DefaultContext : https://172.31.25.234:9443/publisher
[2018-02-23 23:42:12,720] INFO - CarbonUIServiceComponent API Store Default
Context : https://172.31.25.234:9443/store
wget -O- https://localhost:9443/publisher --no-check-certificate - give me the page and i can see its running locally, however , i cant reach the url from its external IP
Firewall disabled on CentOS. (firewall--cmd not exist)
I've tried also to use reverse proxy to my LAN publisher address:9443 but still no luck.
Appreciate your assistance.
Found the issue, although there is no firewall not sure why publisher ui management was not accessible from internet through port 9443
Finally i changed the port to 8080 on repository/conf/tomcat/catalina-server.xml and it worked.