Не запускается BGScheduler:
[root@ns3 ~]# systemctl status bgkernel_scheduler.service
● bgkernel_scheduler.service - BGScheduler
Loaded: loaded (/etc/systemd/system/bgkernel_scheduler.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Вс 2023-03-19 09:59:44 +07; 1 day 23h ago
Process: 3781 ExecStart=/opt/bgbilling/BGScheduler/bin/start.sh (code=exited, status=0/SUCCESS)
Main PID: 3812 (code=exited, status=255)
мар 19 09:59:41 ns3.sibtelecom42.ru systemd[1]: Starting BGScheduler...
мар 19 09:59:41 ns3.sibtelecom42.ru start.sh[3781]: Java version is 17.0 (17.0.6 2023-01-17)
мар 19 09:59:41 ns3.sibtelecom42.ru systemd[1]: Started BGScheduler.
мар 19 09:59:44 ns3.sibtelecom42.ru systemd[1]: bgkernel_scheduler.service: main process exited, code=exited, status=255/n/a
мар 19 09:59:44 ns3.sibtelecom42.ru systemd[1]: Unit bgkernel_scheduler.service entered failed state.
мар 19 09:59:44 ns3.sibtelecom42.ru systemd[1]: bgkernel_scheduler.service failed.
в логах BGScheduler.out:
[root@ns3 log]# cat BGScheduler.out
Starting CommandPortListener on port 9066
03-19/09:59:43.648 INFO [main] Localizer - Init locales
03-19/09:59:43.655 INFO [main] DefaultServerSetup - Init JNDI...
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See
http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
03-19/09:59:43.722 INFO [main] DefaultServerSetup - Binding javax.jms.ConnectionFactory[org.apache.activemq.ActiveMQConnectionFactory@1bb1fde8] to java:comp/env/mq/connectionFactory
03-19/09:59:43.740 INFO [main] DefaultServerSetup - Init DB connection pools...
03-19/09:59:43.766 INFO [main] DefaultServerSetup - Binding JDBC pool "master" to java:comp/env/jdbc/master
03-19/09:59:43.774 INFO [main] AnnotatedMBean - Register MBean ru.bitel.bgbilling.server.dbcp:type=DatabaseConnectionPool,name=master
03-19/09:59:44.017 INFO [main] DefaultServerSetup - Init trash pools...
03-19/09:59:44.476 INFO [main] AbstractConsumer - MQ createConsumer(Topic) [destination=BG.Event.ru.bitel.bgbilling.kernel.event.events.system.ModuleConfigModifiedEvent; query=null; noLocal=false
03-19/09:59:44.486 FATAL [main] Application - Fatal error, exit: Parameter app.id not defined in application XML!
03-19/09:59:44.486 FATAL [main] Application - Parameter app.id not defined in application XML!
ru.bitel.bgbilling.common.BGException: Parameter app.id not defined in application XML!
at ru.bitel.bgbilling.kernel.application.server.Application.<init>(Application.java:119) ~[kernel-server.jar:9.2301]
at ru.bitel.bgbilling.kernel.application.server.Application.main(Application.java:900) [kernel-server.jar:9.2301]
03-19/09:59:44.500 FATAL [main] Application - Shutdown with error
ru.bitel.bgbilling.common.BGException: Parameter app.id not defined in application XML!
at ru.bitel.bgbilling.kernel.application.server.Application.<init>(Application.java:119)
at ru.bitel.bgbilling.kernel.application.server.Application.main(Application.java:900)
03-19/09:59:44.502 INFO [Thread-3] EventProcessor - Shutdown EventProcessor...
BGScheduler.mq:
[root@ns3 log]# cat BGScheduler.mq
09:59:44,048 INFO [EventProcessor-init] EventProcessor - Init EventProcessor MQ connection factory...
версия биллинга:
BGBillingServer_9.2301-2302161959
BGScheduler_9.2301-2302010505
OS - Linux ns3 3.10.0-1160.88.1.el7.x86_64 #1 SMP Tue Mar 7 15:41:52 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
JDK - jdk-17.0.6+10
ActiveMQ - apache-activemq-5.16.6