■ Failover Guide | ||
Phenomenon | Confirm | Action |
1.Unable to access the portal | 1.1 Check whether the tomcat process is running in the Linux server console Ps -ef|grep tomcat | Wait 5-10 minutes after restarting the terminated tomcat service. cd /rpa/bin/ ./tomcat-run.sh |
1.2 Check gateway, auth, tenant services ps -ef|grep gateway ps -ef|grep auth ps -ef|grep tenant | If the gateway service is shut down, restart it cd /rpa/apps/gateway ./run.sh If the auth service is stopped, restart it cd /rpa/apps/auth ./run.sh If the tenant service is shut down, restart it cd /rpa/apps/tenant ./run.sh | |
1.3 Check activemq service Ps -ef|grep activemq | If the activemq service is shut down, restart it cd /rpa/bin ./activemq-run.sh | |
1.4 Check the tomcat log /rpa/logs/admin/catalina.out | Identify the cause through the error log | |
2. If activemq restart is not possible | 2.1 Check whether the activemq process is running in the Linux server console ps -ef|grep activemq | If the activemq service is shut down, restart it cd /rpa/bin ./activemq-run.sh |
2.2 Check activemq log The path may be slightly different depending on the activemq version. /rpa/pkgs/apache-activemq-5.15.14/data/activemq.log | Usually WARN or INFO in the log is not the cause of the error Identify the cause through the error log | |
3. Bot PC does not connect to the server | 3.1 Verify that the process is connected in the Admin Portal About screen | Restart the terminated RPA service |
3.2 Check whether gateway and communication processes are running on Linux server console Check gateway and comm server processes ps -ef|grep gateway ps -ef|grep comm | If the gateway service is shut down, restart it cd /rpa/apps/gateway ./run.sh If the comm service is shut down, restart it cd /rpa/apps/comm ./run.sh | |
3.3 Check the gateway, comm error log /rpa/logs/gateway/error.log /rpa/logs/comm/error.log | Identify the cause through the error log | |
3.4 Check network and firewall changes and status | Network status check | |
4. In case DB connection is not possible | 4.1 Checking whether mariaDB process is running in Linux server console ps -ef|grep mysql | If mariaDB service is stopped, restart all RPA services and tomcat after shutting down. cd /rpa/bin ./mysql-start.sh |
4.2 If the process is alive, connect and check the status cd /rpa/pkgs/mariadb/bin ./mysql -u root -p enter password MariaDB [(none)]> select now(); Current time lookup | Check mariadb data through DB console | |
4.3 Check the error log /rpa/logs/mariadb/mariadb.err /rpa/logs/mariadb/mariadb-slow.log | Identify the cause through the error log | |
5. Slowness occurred while using the portal | 5.1 Verify that the process is connected in the Admin Portal About screen | Restart the terminated RPA service. |
5.2 Check the operation status of RPA service in Linux server console curl https://127.0.0.1:8777/version --insecure curl http://127.0.0.1:9091/auth/version curl https://127.0.0.1:9001/communication/version --insecure curl http://127.0.0.1:9096/asset/version curl http://127.0.0.1:9093/scheduler/version curl http://127.0.0.1:9094/workflow/version curl http://127.0.0.1:9096/interface/version curl http://127.0.0.1:9099/tenant/version | If there is an RPA service that does not respond or an error occurs, check the error log of that service. /rpa/logs/gateway/error.log /rpa/logs/auth/error.log /rpa/logs/comm/error.log /rpa/logs/core/server.log /rpa/logs/asset/error.log /rpa/logs/scheduler/error.log /rpa/logs/workflow/error.log /rpa/logs/interface/error.log /rpa/logs/tenant/error.log | |
5.3 Check CPU and MEM usage through top command | Check for Processes Using Excessive Resources | |
5.4 Check disk usage with df -k command | Check whether the disk is full and secure free space | |
6. The core service is abruptly terminated or OutOfMemory is displayed in the log | Increase jvm memory of 6.1 core service. cd /rpa/apps/core vi run.sh There is a memory setting option used to start the corresponding module. -Xmx to specify the maximum heap size -Xms to specify the initial Java heap size -Xss to set the Java thread stack size Increase the value to fix and restart | JVM memory may run out in situations where jobs including large amounts of resources are running at once, and the error is resolved by increasing it in run.sh |
7. When uploading a public resource, the upload is not possible because the capacity is full. | 7.1 Currently, the size of the project is limited to 50M when distributing the project to improve performance. It is recommended to maintain 50M as much as possible, and if necessary, it can be changed as follows. 1) How to modify project size (1) Quit designer (2) Change value in installation path / Designer.config /. <UserSetting category="Server" group="Internal" name="UploadFileSizeLimit" value="99137200" isReadOnly="false" valueType="number" /> | |
7.2 Increase jvm memory of core service. cd /rpa/apps/core vi run.sh There is a memory setting option used for starting the module. -Xmx to specify the maximum heap size -Xms to specify the initial Java heap size -Xss to set the Java thread stack size Increase the value to fix and restart | ||