jack huang 3 Posted September 2, 2019 Share Posted September 2, 2019 WARN 2019-09-02T182132,077 + 0800 [service-c4d6763a-193c-41e4-8972-15cf6ccae154-startup] nodemanager.service.AbstractServiceManagerUrlhttps// reportserver9501 / c4d6763a-193c-41e4-8972 -15cf6ccae154 / managementService / getServiceInformation404 WARN 2019-09-02T182137,131 + 0800 [service-c4d6763a-193c-41e4-8972-15cf6ccae154-startup] nodemanager.service.AbstractServiceManagerUrlhttps// reportserver9501 / c4d6763a-193c- 41e4-8972-15cf6ccae154 / managementService / getServiceInformation404 WARN 2019-09-02T182142,154 + 0800 [service-c4d6763a-193c-41e4-8972-15cf6ccae154-startup] nodemanager.service.AbstractServiceManagerUrlhttps// reportserver9501 / c4d6763a-193c- 41e4-8972-15cf6ccae154 / managementService / getServiceInformation404 WARN 2019-09-02T182147,177 + 0800 [service-c4d6763a-193c-41e4-8972-15cf6ccae154-startup] nodemanager.service.AbstractServiceManagerUrlhttps// reportserver9501 / c4d6763a-193c-41e4-8972 -15cf6ccae154 / managementService / getServiceInformation404 WARN 2019-09-02T182152,201 + 0800 [service-c4d6763a-193c-41e4-8972-15cf6ccae154-startup] nodemanager.service.AbstractServiceManagerUrlhttps// reportserver9501 / c4d6763a-193c- 41e4-8972-15cf6ccae154 / managementService / getServiceInformation404 WARN 2019-09-02T182157,233 + 0800 [service-c4d6763a-193c-41e4-8972-15cf6ccae154-startup] nodemanager.service.AbstractServiceManagerUrlhttps// reportserver9501 / c4d6763a-193c- 41e4-8972-15cf6ccae154 / managementService / getServiceInformation404 INFO 2019-09-02T182202,225 + 0800 [67ca361c-8617-443b-94b3-e5764dc5ded6] nodemanager.control.ServiceConfigCommandHandlerIDENTIFY_SERVICES [serverId = b0547da6-adc5-4553-8386-32df31213ecbserverName = biserver port = 9443siteID = 5c2c7b84-e1f4-4187-9799-85a2a48f0ebc]GUID67ca361c-8617-443b-94b3-e5764dc5ded6ServiceStatusObserver INFO 2019-09-02T182202,225 + 0800 [67ca361c-8617-443b-94b3-e5764dc5ded6] nodemanager.control.ServiceConfigCommandHandler4 INFO 2019-09-02T182202,225 + 0800 [67ca361c-8617-443b-94b3-e5764dc5ded6] nodemanager.control.ServiceConfigCommandHandler1827fe39-c893-47b4-ad2d-97bd235711c8 status RUNNING INFO 2019-09-02T182202,225 + 0800 [67ca361c-8617-443b-94b3-e5764dc5ded6] nodemanager.control.ServiceConfigCommandHandlerc4d6763a-193c-41e4-8972-15cf6ccae154 status STARTING INFO 2019-09-02T18 2202,225 + 0800 [67ca361c-8617-443b-94b3-e5764dc5ded6] nodemanager.control.ServiceConfigCommandHandler10.0.0 INFO 2019-09-02T182202,225 + 0800 [67ca361c-8617-443b- 94b3-e5764dc5ded6] nodemanager.control.ServiceConfigCommandHandlerWeb Player 10.0.0 WARN 2019-09-02T182202,256 + 0800 [service-c4d6763a-193c-41e4-8972-15cf6ccae154-startup] nodemanager.service.AbstractServiceManager https// reportserver9501 / c4d6763a-193c-41e4-8972-15cf6ccae154 / managementService / getServiceInformation404 INFO 2019-09-02T182207,667 + 0800 [service-c4d6763a-193c-41e4-8972-15cf6ccae154-startup] service.monitor.ServiceStatusCallablec4d6763a-193c-41e4-8972-15cf6ccae15445RUNNING INFO 2019-09-02T182207,667 + 0800 [service-c4d6763a-193c-41e4-8972-15cf6ccae154-startup] server.nodemanager.ServiceMonitorc4d6763a-193c-41e4-8972-15cf6ccae154RUNNING / INFO 2019-09-02T182207,667 + 0800 [service-c4d6763a-193c-41e4-8972-15cf6ccae154-startup] nodemanager.primus.ServiceNotifierc4d6763a-193c-41e4-8972-15cf6ccae154 INFO 2019-09-02T182207,667 + 0800 [service-c4d6763a-193c-41e4-8972-15cf6ccae154-startup] nodemanager.service.AbstractServiceManagerIDc4d6763a-193c-141e4-8972-15cf6ccae154 INFO 2019-09-02T182208,727 + 0800 [pool-4-thread-39] nodemanager.control.ServiceManipulator[c4d6763a-193c-41e4-8972-15cf6ccae154]STARTING INFO 2019-09-02T182208,727 + 0800 [pool-4-thread-39] nodemanager.control.ServiceConfigCommandHandlerNodeIDENTIFY_SERVICES [serverId = 1aec052f-755e-4e17-991a-61f2564c6428serverName = reportserverport = 9443siteID = 5c2c7b84-e1f4-4187-9799-85a2a48f0ebc]GUID868153ae-4fdd-4842-bdc5-a83e56de2810StartServiceCommandHandler INFO 2019-09-02T182208,727 + 0800 [pool-4-thread-39] nodemanager.control.ServiceConfigCommandHandler4 INFO 2019-09-02T182208,727 + 0800 [pool-4- thread-39] nodemanager.control.ServiceConfigCommandHandler1827fe39-c893-47b4-ad2d-97bd235711c8 status RUNNING INFO 2019-09-02T182208,727 + 0800 [pool-4-thread-39] nodemanager.control ServiceConfigCommandHandlerc4d6763a-193c-41e4-8972-15cf6ccae154 status RUNNING INFO 2019-09-02T182208,727 + 0800 [pool-4-thread-39] nodemanager.control.ServiceConfigCommandHandlerAutomation Services 10.0 0.0 INFO 2019-09-02T182208,727 + 0800 [pool-4-thread-39] nodemanager.control.ServiceConfigCommandHandlerWeb Player 10.0.0 INFO 2019-09-02T182208,727 + 0800 [pool- 4-thread-39] nodemanager.control.ServiceManipulator[c4d6763a-193c-41e4-8972-15cf6ccae154]STARTING Link to comment Share on other sites More sharing options...
Khushboo Rabadia Posted September 9, 2019 Share Posted September 9, 2019 You can open support case to investigate on this issue as actual cause is not evident from the stacktrace shared. Logs are in INFO mode, logs in debug mode can provide detailed information. Link to comment Share on other sites More sharing options...
Prashant Anand Posted September 10, 2019 Share Posted September 10, 2019 Please also check that the Web Player is up. You can also attach a screenshot of the error that you see while accessing the Web Player. If it is something that can be answered here, we can do that. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now