Start service and access
1、Server startup (enter the server/directory to start, remember to start the database service first)
(1) If it is a Linux platform, check if the files in the red box below have executable permissions. If not, assign executable permissions
(2) Linux deployed server, using commands sh start.sh to start the service (also use this command to restart), Use the command sh stop.sh to stop the service
(3) Windows deployed server, using start.bat to start the service,After startup, do not close the black window (especially do not left click on the black window, it will enter the selection mode, which will block the operation, right-click to release), stop the service and close it. You can also register the server as a Windows system service to enable startup and hide black windows
(4) The server startup process takes approximately 10 seconds to complete, Attention: When starting the server, the wgcloud daemon relese process will be guarded at the same time. Do not close the daemon process
The log file of the server running is in server/log/, and the following print information is seen in the log file indicating that the server has completed startup
......
2024-07-15 22:09:28.555 [main] INFO  org.apache.catalina.core.StandardEngine - Starting Servlet engine: [Apache Tomcat/9.0.82]
2024-07-15 22:09:28.903 [main] INFO  o.a.c.core.ContainerBase.[Tomcat].[localhost].[/] - Initializing Spring embedded WebApplicationContext
2024-07-15 22:09:28.904 [main] INFO  o.s.b.w.s.c.ServletWebServerApplicationContext - Root WebApplicationContext: initialization completed in 3215 ms
2024-07-15 22:09:29.528 [main] WARN  com.zaxxer.hikari.HikariConfig - HikariPool-1 - idleTimeout has been set but has no effect because the pool is operating as a fixed size pool.
2024-07-15 22:09:29.529 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
2024-07-15 22:09:29.543 [main] WARN  com.zaxxer.hikari.util.DriverDataSource - Registered driver with driverClassName=com.mysql.jdbc.Driver was not found, trying direct instantiation.
2024-07-15 22:09:29.895 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
2024-07-15 22:09:32.230 [main] INFO  com.wgcloud.util.IdGeneratorSnowflake - 当前机器的workerId: 0
2024-07-15 22:09:32.741 [main] INFO  o.s.b.a.web.servlet.WelcomePageHandlerMapping - Adding welcome page template: index
2024-07-15 22:09:33.596 [main] INFO  o.s.boot.web.embedded.tomcat.TomcatWebServer - Tomcat started on port(s): 9999 (http) with context path ''
2024-07-15 22:09:33.628 [main] INFO  com.wgcloud.WgcloudServiceApplication - Started WgcloudServiceApplication in 9.213 seconds (JVM running for 10.228)
2024-07-15 22:09:33.653 [main] INFO  com.wgcloud.common.ApplicationStartListener - NettyServer服务启动,端口:9998
2024-07-15 22:09:38.637 [taskScheduler-1] INFO  com.wgcloud.task.ScheduledTask - validateLicense------------2024-07-15 22:09:38
......
After startup is complete, the browser inputs http://192.168.1.1:9999 Login, change the information in the URL to your own server host IP and web port, default login account/password :admin/111111
Screenshot of the WGCLOUD monitoring system login page
Tip: wgcloud daemon release is the daemon process of the server, which starts simultaneously with the server. Do not shut it down or kill it
2、Agent startup (enter agent/directory to start)
(1) If it is a Linux platform, check if the files in the red box below have executable permissions. If not, assign executable permissions
(2) The agent deployed on Linux uses the command sh start.sh to start the service (also used for restarting), Use the command sh stop.sh to stop the service
(3) Windows deployment agent, run wgcloud-agent-release. exe as an administrator, After startup, do not close the black window. Stop the service and turn it off. You can also register the agent as a Windows system service, Implement boot up and hide black windows
(4) The log files of agent operation are located in agent/log/
If other hosts need to be monitored, check How to deploy agents separately on the monitoring host
3、Deployment completed
Previous Step    Return to installation directory