What you can do when unable to log in to Hinemos Client
Have you ever experienced a situation where you have finally finished setting up your environment and the components of Hinemos by carefully following the instructions in the installation manual, but fail to log in to the client?
Although there are several reasons why you might be unsuccessful to login to Hinemos, e.g. the Manager is still loading, the internet connection is bad, etc, in this article, I will introduce you to 2 of the presumable reasons and their solution.
First, prepare an environment with Hinemos Manager ver.6.1 and Hinemos Web Client ver.6.1 installed.
[Confirm Installed Packages]
[Confirm Status of Hinemos Manager]
[Confirm Status of Hinemos We Client]
Cause1：Listening Address Setting
When logging in to Hinemos, the following error message may appear.
The cause might be because the listening IP address of Hinemos Manager is set to 0.0.0.0.0.
Due to the bug in OpenJDK 8, users cannot set 0.0.0.0.0 as the listening address when using java-1.8.0-openjdk-22.214.171.124 or earlier.
Therefore, users must upgrade their OpenJDK version or change the listening address.
This time, I will explain the latter solution.
In order to change the listening address, we will be using the script “hinemos_change_listen_address.sh” placed under “/opt/hinemos/sbin/mng/”.
①Stop Hinemos Manager and launch PostgreSQL
(root) # service hinemos_manager stop
(root) # service hinemos_pg start
(root) # /opt/hinemos/sbin/mng/hinemos_change_listen_address.sh IP Address or HostName
③Stop PostgreSQL and start Hinemos Manager
(root) # service hinemos_manager start
Try logging in again after finishing the 3 steps.
Cause2：Too many Clients connected to the Manager at the same time
There are a limitted number of simultaneous connections possible from Hinemos Client to Hinemos Manager. You cannot connect to Hinemos Manager when exceeding the limit.
In such a case, please try and increase the maximum number of connection.
Example: When increasing the number from 8 (default) to 16, modify the corresponding line as follows:
### JVM - Maximum number of access users
②Increase the number of Web Client’s heap memory
When the number of connection increases, the amount of Java heap memory used by Hinemos Client may not be enough.
Therefore, edit “/opt/hinemos_web/conf/hinemos_web.cfg” and increase the amount of Java heap memory of Hinemos Client.
Reference Value: When connecting using 10 to 20 browsers, select “medium”. When connecting using 20 or more browsers, select “large”
This time, we have increased the number to 16, so select “medium”.
### JVM - Performance Tuning
# for small systems
#JVM_HEAP_OPTS="-Xms256m -Xmx256m -XX:NewSize=40m -XX:MaxNewSize=40m -XX:MaxPermSize=128m -Xss256k"
# for medium systems
JVM_HEAP_OPTS="-Xms512m -Xmx512m -XX:NewSize=40m -XX:MaxNewSize=40m -XX:MaxPermSize=128m -Xss256k"
# for large systems
#JVM_HEAP_OPTS="-Xms1024m -Xmx1024m -XX:NewSize=40m -XX:MaxNewSize=40m -XX:MaxPermSize=128m -Xss256k"
③Restart Hinemos Web Client to apply changes
Let’s check if the maximum number of connection has actually changed.
Success! It works with more than 8 browsers.
That is it for today!
Thanks for reading!