![]() The error indicates that the host cannot be reached. Symptoms: When you attempt to log into the Cloud UI or when you attempt to connect to an Elasticsearch or Kibana endpoint URL, the connection eventually times out with an error. Log into the Cloud UI administration console to confirm that the issue is resolved.Ĭloud UI, Elasticsearch, and Kibana endpoint URLs inaccessible on AWS edit Alternatively, you can perform the step from localhost. If you prefer, you can use the HTTPS protocol on port 12443, but it currently supports only a self-signed certificate. In the current release, there is no direct way to change the Java heap size in the UI, so you need to increase the heap size as follows:ĭocker stop frc-admin-consoles-admin-console & docker rm -f frc-admin-consoles-admin-console As a workaround, you can manually increase the heap size. This issue is expected to be fixed in a future release. ![]() Resolution: The administration console that supports the Cloud UI might be running out of Java heap space, causing login failures. Symptoms: When you attempt to log into the Cloud UI, the login process appears to hang and then fails. To avoid this issue on future allocators you create, generate a roles token that has the right permissions for this to work, in this case the permission to assign the allocator role the token generated during the installation on the first host will not suffice. Verify that the allocator is now being used when creating new Elasticsearch clusters or moving nodes off other allocators. To resolve this issue, you might need to refresh the roles for the allocator.įollow the steps for assigning roles to hosts, but do not change any of the assigned roles. Resolution: The issue is caused by a token specified with the -roles-token 'TOKEN' parameter that does not have sufficient privileges to assign the role correctly. Symptoms: You installed Elastic Cloud Enterprise on a new host and assigned it the allocator role from the command line with the -roles "allocator" parameter during installation, but new clusters are not being created on the allocator. After the allocator is vacated, you should investigate the cause of the failure separately, which could be due to a host machine failure, and replace any lost capacity. Vacate options for a selected allocator can help fine tune the removal of nodes. You cannot repair an allocator in the Cloud UI, so you should first move all nodes to a new allocator. Allocator failures editĪllocator failures result in alerts in the Cloud UI. To learn more, check the the configuration steps for Red Hat Enterprise Linux (RHEL) and CentOS. You must disable firewalld with sudo systemctl disable firewalld and reboot before installing or reinstalling ECE. The service is not compatible with Docker and interferes with the installation of ECE. Resolution: The issue might be caused by the firewalld service. Symptom: On CentOS and RHEL the installation of Elastic Cloud Enterprise fails, possibly indicating an issue that affects communication between Docker containers on the host. Installation failures with firewalld enabled on CentOS and RHEL edit Otherwise, the host does not run any role. You must explicitly specify the roles with the parameter -roles, for example "coordinator,director,proxy". Resolution: Use the emergency token provided during the installation of the genesis ECE nodes. If all directors are lost, re-install ECE. If you lost more than half of the directors, contact the support. If you have 5 directors, 3 directors must be available. More than half of the director hosts are available. Symptom: You have no access to API and UI because all coordinators are lost. Emergency token not spinning up the coordinator role edit You can also refer to the list of product Limitations and known problems. ![]() Hi, I setup a conquer server using 5095 source at my friends house (non hamachi server) and I logged in from home and created my char but when i try to play it freezes at logging into game server.This set of common symptoms and resolutions can help you to diagnose unexpected behavior with Elastic Cloud Enterprise. I want to log in to metin2 server but it always kicks me off.i type the id and the password but it keeps me on "Connectiong to the server". I emailed the guy how to fix it but I haven't gotten a reply and like I said I'm kind of stupid with. I followed a video on youtube (also on this forum by reexco) that was fairly recent and had good links still, I got all the stuff done and got the game open, but when I try to log in, it goes to "Logging into game server." and then doesn't ever move. This is my first time trying to set up a private server and I thought I had done everything right. Conquer Online PServer 5165 Stuck on "Logging into Game Server."Īs the title states, tried everything.
0 Comments
Leave a Reply. |