[User must see] Common Problem:Product does not Start and Access Properly

vividime-Club Show all floors Published on 2024-11-22 13:42:33 |Reading mode print Previous Topic Next Topic
What should be done if the product cannot start and access normally
reply

Using props report

Exciting comments1

vividime-Club Show all floors Published on 2024-11-22 13:44:01
Reference Documents:Click on me

1. Start-up problems
After the installation is complete, the startup of vividime BI fails.
The specific failures are listed below:
•Windows environment, go to tomcat/bin directory, double click startup.bat to start vividime, tomcat pop-up window flashback.
•Linux environment, go to tomcat/bin directory, execute sh startup.sh to start vividime, after startup can not find the process.
As shown in the above screenshot, the process cannot be found after startup, this kind of phenomenon belongs to the startup failure, the process did not start up, the causes and solutions of this kind of problem can be referred to the following three kinds:
1.1 Jdk version too low or Jdk path configuration error
The Jdk version used by vividime should be higher than Jdk9, Jdk11 is recommended, too low a Jdk version will lead to startup failure.
Check if the Jdk path is correct in tomcat/bin/setcalsspath.sh (Windows environment check setcalsspath.bat).
➢Note:
The Jdk11 version of Jre is the same as Jdk, the rest of the versions are not necessarily.
Reinstall Jdk and configure environment variables, for more details refer toJava JDK11 Download, Installation and Environment Variable Configuration JDK11 download, installation and environment variable configuration.
1.2 Port occupied
This type of cause can usually be seen in the tomcat/logs/catalina.out startup logs as a clear indication of an error.
Solution: Change the port number. Open the server.xml file under vividime\tomcat\conf with a text editor and modify the port number in the following red text.
1.3 jvm memory is too low
This type of cause can usually be seen in the tomcat/logs/catalina.out startup logs as a clear indication of an error.
Solution: Adjust the memory allocated to vividime jvm: Use a text editor to open vividime\tomcat\bin under the catlina.sh file (Windows environment to modify the catlina.bat), modify the following red text of the memory size, it is recommended to be half of the server's remaining available memory.
2. Visiting issues
There are two possible reasons and solutions for browsers using http://ip:port/bi/Viewer无法访问 after vividime tomcat starts:
2.1 Network not available
Using the computer where the browser is located, use the "ping server ip" command in the cmd window to test whether the network is smooth, if the network is not available, please contact your own network administrator.
The following figure shows a smooth network.
2.2 Port not available
Even if the network is up, if the port isn't open, you may not be able to access it.
Solution: Close the firewall of the vividime server or open the vividime tomcat access port

reply

Using props report

Advanced mode
You need to log in before you can reply to the post login | Free registration

© 2024 VIVIDATA PTE. LTD. All Rights Reserved. Privacy Statement