Так, продолжаем разговор с резиновой уточкой, не много разжую написанное в предыдущих постах:
Имеются 3 типа сервисов :
Код:
1 real_ip
2 left_ip
3 vpn
И 6 типов устройств:
Код:
1 Access+Accounting_IPOE
2 netflow_source
3 ipoe_gates(real_ip)
4 ipoe_gates(left_ip)
5 Access+Accounting_PPTP
6 pptp_servers
В модуле inet вот такое дерево устройств:
Код:
-Access+Accounting_IPOE(192.168.120.212) id=1
--netflow_source: id=2,5,8
---ipoe_gates id=3,6,4,7,9,10
.........
-Access+Accounting_PPTP(192.168.120.210) id=11
--vpn (ПАПКА) id=12
---pptp_servers id=14,15,16,17
.......
на договорах в модуле inet заведено некоторое количество сервисов, причём сервисы с id от 1 до 1227 - только типов 1 и 2 ;
сервисы с id от 1228 и выше - только типа 3. На всех договорах сервисы - либо типа 1, либо 2, либо 3 ( нет сервисов разных типов на одном договоре )
сервисы типа 1 и 2 прикреплены к устройствам с id=3,6,4,7,9,10 ; сервисы типа 3 прикреплены к устройству с id=12
( т.к юзер может авторизоваться на любом из pptp-серверов )
на компе с ип 192.168.120.212 сервера BGInetAccounting и BGInetAccess работают без нареканий и в их логах видно, что вся обработка касается только
сервисов с id от 1 до 1227.
Вот конфиги этих серверов :
на 192.168.120.212 :
inet-access.xml:
Код:
<?xml version="1.0" encoding="UTF-8"?>
<application context="access">
<param name="app.name" value="BGInetAccess"/>
<param name="app.id" value="2"/>
<param name="db.driver" value="com.mysql.jdbc.Driver"/>
<param name="db.url" value="jdbc:mysql://192.168.120.211/bgbilling?useUnicode=true&characterEncoding=Cp1251&allowUrlInLocalInfile=true&zeroDateTimeBehavior=convertToNull&jdbcCompliantTruncation=false&queryTimeoutKillsConnection=true&connectTimeout=1000"/>
<param name="db.user" value="xxxxxxxxxxxxxx"/>
<param name="db.pswd" value="xxxxxxxxxxxxxxxxxxxxx"/>
<param name="db.validationTimeout" value="10"/>
<param name="mq.url" value="failover:(tcp://192.168.120.211:61616)"/>
<param name="mq.user" value="xxxxxxxxxxxxxxxxx"/>
<param name="mq.pswd" value="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"/>
<param name="moduleId" value="10"/>
<param name="rootDeviceId" value="1"/>
<param name="accounting.deviceTypeIds" value="1"/>
<param name="commonIdentifierName" value="rootDeviceId"/>
<param name="datalog.radius.dir" value="data/radius" />
<param name="datalog.radius.chunk.size" value="262144" />
<param name="datalog.radius.compression.type" value="1" />
<param name="datalog.dhcp.dir" value="data/dhcp" />
<param name="datalog.dhcp.chunk.size" value="131072" />
<param name="datalog.dhcp.compression.type" value="1" />
<bean name="access" class="ru.bitel.bgbilling.modules.inet.access.Access" />
</application>
inet-accounting.xml:
Код:
<?xml version="1.0" encoding="UTF-8"?>
<application context="accounting">
<param name="app.name" value="BGInetAccounting"/>
<param name="app.id" value="3"/>
<param name="db.driver" value="com.mysql.jdbc.Driver"/>
<param name="db.url" value="jdbc:mysql://192.168.120.211/bgbilling?useUnicode=true&characterEncoding=Cp1251&allowUrlInLocalInfile=true&zeroDateTimeBehavior=convertToNull&jdbcCompliantTruncation=false&queryTimeoutKillsConnection=true&connectTimeout=1000"/>
<param name="db.user" value="xxxxxxxxxxxxxxxx"/>
<param name="db.pswd" value="xxxxxxxxxxxxxxxxxxxxxxx"/>
<param name="db.validationTimeout" value="10"/>
<param name="mq.url" value="failover:(tcp://192.168.120.211:61616)"/>
<param name="mq.user" value="xxxxxxxxxxxxxxxx"/>
<param name="mq.pswd" value="xxxxxxxxxxxxxxxxxxxxxxxxx"/>
<param name="moduleId" value="10"/>
<param name="rootDeviceId" value="1"/>
<param name="commonIdentifierName" value="rootDeviceId"/>
<param name="datalog.radius.dir" value="data/radius" />
<param name="datalog.radius.chunk.size" value="524288" />
<param name="datalog.radius.compression.type" value="1" />
<param name="datalog.flow.dir" value="data/flow" />
<param name="datalog.flow.chunk.size" value="524288" />
<param name="datalog.flow.compression.type" value="1" />
<bean name="accounting" class="ru.bitel.bgbilling.modules.inet.accounting.Accounting"/>
<context name="collector">
<scheduledExecutorService name="hrlydtlggr" corePoolSize="1"/>
<bean name="flowDataLogger" class="ru.bitel.bgbilling.modules.inet.collector.IPHourlyDataLogger">
<param name="scheduledExecutor">hrlydtlggr</param>
</bean>
<bean name="flowListener" class="ru.bitel.bgbilling.modules.inet.collector.InetFlowListener">
<constructor factoryMethod="newInstance">
<param name="type" value="netflow"/>
<param name="host" value=""/>
<param name="port" value="2001"/>
<param name="recvBufferSize">4 * 1024 * 1024</param>
<param name="soRCVBUF">512 * 1024</param>
<param name="threadCount" value="10"/>
<param name="agentDeviceIds" value="2,5,8"/>
<param name="processAgentDeviceIds" value="2,5,8"/>
<param name="ipResourceFilter" value=""/>
<param name="dataLogger">flowDataLogger</param>
</constructor>
</bean>
<context name="detail">
<bean name="detailWorker" class="ru.bitel.bgbilling.modules.inet.accounting.detail.InetDetailWorker"/>
</context>
</context>
</application>
А вот на компе с ип 192.168.120.210 с сервера BGInetAccounting и BGInetAccess - пытаются обрабатывать абсолютно все сервисы с id от 1 и до бесконечности ( т.е. всех типов 1,2,3 )
Вот конфиги этих серверов ( на 192.168.120.210 ):
inet-access.xml:
Код:
<?xml version="1.0" encoding="UTF-8"?>
<application context="access">
<param name="app.name" value="BGInetAccessVPN"/>
<param name="app.id" value="4"/>
<param name="db.driver" value="com.mysql.jdbc.Driver"/>
<param name="db.url" value="jdbc:mysql://192.168.120.211/bgbilling?useUnicode=true&characterEncoding=Cp1251&allowUrlInLocalInfile=true&zeroDateTimeBehavior=convertToNull&jdbcCompliantTruncation=false&queryTimeoutKillsConnection=true&connectTimeout=1000"/>
<param name="db.user" value="xxxxxxxxxxxxx"/>
<param name="db.pswd" value="xxxxxxxxxxxxxxxxxxxxxx"/>
<param name="db.validationTimeout" value="10"/>
<param name="mq.url" value="failover:(tcp://192.168.120.211:61616)"/>
<param name="mq.user" value="xxxxxxxxxx"/>
<param name="mq.pswd" value="xxxxxxxxxxxxxxxxxxx"/>
<param name="moduleId" value="10"/>
<param name="rootDeviceId" value="11"/>
<param name="accounting.deviceTypeIds" value="5"/>
<param name="commonIdentifierName" value="rootDeviceId"/>
<param name="datalog.radius.dir" value="data/radius" />
<param name="datalog.radius.chunk.size" value="262144" />
<param name="datalog.radius.compression.type" value="0" />
<param name="datalog.dhcp.dir" value="data/dhcp" />
<param name="datalog.dhcp.chunk.size" value="131072" />
<param name="datalog.dhcp.compression.type" value="1" />
<bean name="access" class="ru.bitel.bgbilling.modules.inet.access.Access" />
<context name="radius">
<bean name="radiusProcessor" class="ru.bitel.bgbilling.modules.inet.radius.InetRadiusProcessor"/>
<scheduledExecutorService name="hrlydtlggr" corePoolSize="1" />
<bean name="radiusDataLogger" class="ru.bitel.bgbilling.modules.inet.radius.RadiusHourlyDataLogger">
<param name="scheduledExecutor">hrlydtlggr</param>
</bean>
<bean name="radiusListener" class="ru.bitel.bgbilling.modules.inet.radius.InetRadiusListener">
<constructor>
<param name="host" value=""/>
<param name="port" value="1814"/>
<param name="recvBufferSize">512 * 1024</param>
<param name="soRCVBUF"></param>
<param name="threadCount">10</param>
<param name="maxQueueSize">200</param>
<param name="processor">radiusProcessor</param>
<param name="mode">RadiusListener.Mode.authentication</param>
<param name="dataLogger">radiusDataLogger</param>
</constructor>
</bean>
</context>
</application>
inet-accounting.xml:
Код:
<?xml version="1.0" encoding="UTF-8"?>
<application context="accounting">
<param name="app.name" value="BGInetAccountingVPN"/>
<param name="app.id" value="5"/>
<param name="db.driver" value="com.mysql.jdbc.Driver"/>
<param name="db.url" value="jdbc:mysql://192.168.120.211/bgbilling?useUnicode=true&characterEncoding=Cp1251&allowUrlInLocalInfile=true&zeroDateTimeBehavior=convertToNull&jdbcCompliantTruncation=false&queryTimeoutKillsConnection=true&connectTimeout=1000"/>
<param name="db.user" value="xxxxxxxxxxxxxxx"/>
<param name="db.pswd" value="xxxxxxxxxxxxxxxxxxxxxxxx"/>
<param name="db.validationTimeout" value="10"/>
<param name="mq.url" value="failover:(tcp://192.168.120.211:61616)"/>
<param name="mq.user" value="xxxxxxxxxxxx"/>
<param name="mq.pswd" value="xxxxxxxxxxxxxxxxxxxxxxxxxx"/>
<param name="moduleId" value="10"/>
<param name="rootDeviceId" value="11"/>
<param name="commonIdentifierName" value="rootDeviceId"/>
<param name="datalog.radius.dir" value="data/radius" />
<param name="datalog.radius.chunk.size" value="524288" />
<param name="datalog.radius.compression.type" value="0" />
<param name="datalog.flow.dir" value="data/flow" />
<param name="datalog.flow.chunk.size" value="524288" />
<param name="datalog.flow.compression.type" value="1" />
<bean name="accounting" class="ru.bitel.bgbilling.modules.inet.accounting.Accounting"/>
<context name="radius">
<bean name="radiusProcessor" class="ru.bitel.bgbilling.modules.inet.radius.InetRadiusProcessor"/>
<scheduledExecutorService name="hrlydtlggr" corePoolSize="1"/>
<bean name="radiusDataLogger" class="ru.bitel.bgbilling.modules.inet.radius.RadiusHourlyDataLogger">
<param name="scheduledExecutor">hrlydtlggr</param>
</bean>
<bean name="radiusListener" class="ru.bitel.bgbilling.modules.inet.radius.InetRadiusListener">
<constructor>
<param name="host" value=""/>
<param name="port" value="1815"/>
<param name="recvBufferSize">1 * 1024 * 1024</param>
<param name="soRCVBUF">512 * 1024</param>
<param name="threadCount">10</param>
<param name="maxQueueSize">200</param>
<param name="processor">radiusProcessor</param>
<param name="mode">RadiusListener.Mode.accounting</param>
<param name="setup">setup</param>
<param name="dataLogger">radiusDataLogger</param>
</constructor>
</bean>
</context>
</application>
И так стартуем:
Вот например вырезка из all.log сервера BGInetAccess на компе 192.168.120.210:
В начале походу он парсит все коннекции из таблицы inet_connection_10 :
Код:
......
access 01-08/15:47:11 DEBUG [main] ResourceManager - Inject to protected ru.bitel.bgbilling.modules.inet.radius.RadiusHourlyDataLogger ru.bitel.bgbilling.modules.inet.dyn.device.radius.AbstractRadiusServiceActivator.dataLogger [files: 0]
access 01-08/15:47:11 INFO [main] Access - childrenDeviceIds=[17, 16, 19, 18, 21, 20, 23, 22, 11, 12, 14, 15]
access 01-08/15:47:11 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.modules.inet.access.InetConnectionManager@4b25ee49 to BG.Event.ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent WHERE moduleId=10
access 01-08/15:47:11 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.modules.inet.access.InetConnectionManager@4b25ee49 to BG.Event.ru.bitel.bgbilling.modules.inet.access.event.InetConnectionDeviceStateAndOptionsModifiedEvent WHERE moduleId=10
access 01-08/15:47:11 INFO [main] InetConnectionManager - Loading connections from database.
access 01-08/15:47:12 DEBUG [main] InetConnectionManager - Restore connection: InetConnection [id=58720-0, iface=6:0, sessId=null, start=07.01.2014 20:09:38, uname=null, addr=[IpAddress:null]]
access 01-08/15:47:12 DEBUG [main] InetConnectionManager - Restore connection: InetConnection [id=58400-0, iface=6:0, sessId=null, start=07.01.2014 11:30:21, uname=null, addr=[IpAddress:null]]
access 01-08/15:47:12 DEBUG [main] InetConnectionManager - Restore connection: InetConnection [id=54568-0, iface=3:13, sessId=null, start=01.01.2014 09:50:47, uname=null, addr=[IpAddress:null]]
access 01-08/15:47:12 DEBUG [main] InetConnectionManager - Restore connection: InetConnection [id=41864-0, iface=3:14, sessId=null, start=14.12.2013 07:16:20, uname=null, addr=[IpAddress:null]]
access 01-08/15:47:12 DEBUG [main] InetConnectionManager - Restore connection: InetConnection [id=58608-0, iface=3:4, sessId=null, start=07.01.2014 17:19:26, uname=null, addr=[IpAddress:null]]
access 01-08/15:47:12 DEBUG [main] InetConnectionManager - Restore connection: InetConnection [id=55600-0, iface=3:15, sessId=null, start=03.01.2014 03:30:05, uname=null, addr=[IpAddress:null]]
access 01-08/15:47:12 DEBUG [main] InetConnectionManager - Restore connection: InetConnection [id=58640-0, iface=3:14, sessId=null, start=07.01.2014 17:59:07, uname=null, addr=[IpAddress:null]]
access 01-08/15:47:12 DEBUG [main] InetConnectionManager - Restore connection: InetConnection [id=41888-0, iface=3:8, sessId=null, start=14.12.2013 07:20:25, uname=null, addr=[IpAddress:null]]
access 01-08/15:47:12 DEBUG [main] InetConnectionManager - Restore connection: InetConnection [id=54816-0, iface=6:0, sessId=null, start=01.01.2014 15:53:44, uname=null, addr=[IpAddress:null]]
access 01-08/15:47:12 DEBUG [main] InetConnectionManager - Restore connection: InetConnection [id=58856-0, iface=9:0, sessId=null, start=08.01.2014 04:48:48, uname=null, addr=[IpAddress:null]]
.........
iface=6:0 - это походу устройство с id=6 и портом 0 на нём ; или iface=3:14 это походу устройство с id=3 и портом 14 на нём.
короче виден перебор всех коннекций на устройствах с id 3,6,4,7,9,10 и нет ни одной строки , где восстанавливались коннекции с устройств с id =12 и выше
Это в принципе можно понять, так как BGInetAccess+BGInetAccounting на компе 192.168.120.210 мы запустили в первый раз, и коннекций на устройстве с id=12 ещё нет
Дальше:
Код:
................................
access 01-08/15:47:12 DEBUG [main] EventProcessor - Add InetServRuntimeMap@1472528887 to BG.Event.ru.bitel.bgbilling.modules.inet.api.server.event.InetServModifiedEvent WHERE moduleId=10
access 01-08/15:47:12 DEBUG [main] EventProcessor - Add InetServRuntimeMap@1472528887 to BG.Event.ru.bitel.bgbilling.modules.inet.access.event.InetServDeviceStateAndOptionsModifiedEvent WHERE moduleId=10
access 01-08/15:47:12 DEBUG [main] EventProcessor - Add InetServRuntimeMap@1472528887 to BG.Event.ru.bitel.bgbilling.kernel.event.events.ContractStatusModifiedEvent
access 01-08/15:47:12 DEBUG [main] EventProcessor - Add InetServRuntimeMap@1472528887 to BG.Event.ru.bitel.bgbilling.kernel.tariff.option.server.event.ContractTariffOptionChangedEvent
access 01-08/15:47:12 DEBUG [main] EventProcessor - Add InetServRuntimeMap@1472528887 to BG.Event.ru.bitel.bgbilling.kernel.tariff.server.event.ContractTariffChangedEvent
access 01-08/15:47:12 DEBUG [main] EventProcessor - Add InetServRuntimeMap@1472528887 to BG.Event.ru.bitel.bgbilling.modules.inet.api.server.event.InetAccountingPeriodModifiedEvent WHERE moduleId=10
access 01-08/15:47:12 DEBUG [main] EventProcessor - Add InetServRuntimeMap@1472528887 to BG.Event.ru.bitel.bgbilling.modules.inet.api.common.event.InetServRestrictionModifiedEvent WHERE moduleId=10
access 01-08/15:47:12 INFO [main] InetServRuntimeMap - Loading inetServs from database.
access 01-08/15:47:12 DEBUG [inetServ-load-p-10-t-2] EventProcessor - Add ru.bitel.bgbilling.kernel.contract.status.server.StatusCache$1@fd12614 to BG.Event.ru.bitel.bgbilling.kernel.event.events.system.ModuleConfigModifiedEvent
access 01-08/15:47:13 INFO [inetServ-load-p-10-t-1] InetServRuntimeMap - Loaded 0 inetServs.
access 01-08/15:47:13 INFO [inetServ-load-p-10-t-2] InetServRuntimeMap - Loaded 0 inetServs.
access 01-08/15:47:13 INFO [inetServ-load-p-10-t-3] InetServRuntimeMap - Loaded 0 inetServs.
access 01-08/15:47:13 INFO [inetServ-load-p-10-t-4] InetServRuntimeMap - Loaded 0 inetServs.
access 01-08/15:47:13 INFO [inetServ-load-p-10-t-3] InetServRuntimeMap - Loaded 0 inetServs.
access 01-08/15:47:13 INFO [inetServ-load-p-10-t-1] InetServRuntimeMap - Loaded 0 inetServs.
access 01-08/15:47:13 INFO [inetServ-load-p-10-t-4] InetServRuntimeMap - Loaded 0 inetServs.
access 01-08/15:47:13 INFO [inetServ-load-p-10-t-2] InetServRuntimeMap - Loaded 0 inetServs.
access 01-08/15:47:13 INFO [inetServ-load-p-10-t-3] InetServRuntimeMap - Loaded 0 inetServs.
access 01-08/15:47:13 INFO [inetServ-load-p-10-t-4] InetServRuntimeMap - Loaded 0 inetServs.
access 01-08/15:47:13 INFO [inetServ-load-p-10-t-2] InetServRuntimeMap - Loaded 0 inetServs.
access 01-08/15:47:14 DEBUG [inetServ-load-p-10-t-1] ContractTariffOptionList - Create:
access 01-08/15:47:14 DEBUG [inetServ-load-p-10-t-1] ProductPeriodRuntimeList - Create:
access 01-08/15:47:14 DEBUG [tree-cache-reload] EventProcessor - Add ru.bitel.bgbilling.kernel.tariff.tree.server.TariffTreeCache$1$1@67e6cf07 to BG.Event.ru.bitel.bgbilling.kernel.tariff.server.event.TariffTreeModifiedEvent
access 01-08/15:47:14 DEBUG [inetServ-load-p-10-t-1] InetAccountingPeriodList - Create:
access 01-08/15:47:14 INFO [inetServ-load-p-10-t-1] InetServRuntimeMap - Adding InetServRuntime: 1280
access 01-08/15:47:14 INFO [inetServ-load-p-10-t-1] InetServRuntimeMap - ContractId: 3648; status: 0; servId: 1280
104
Options [] TariffModuleTreeSet [30:21.05.2009-…; ]
Device state: 1; optionSet:
access 01-08/15:47:14 DEBUG [inetServ-load-p-10-t-1] ContractTariffOptionList - Create:
access 01-08/15:47:14 DEBUG [inetServ-load-p-10-t-1] ProductPeriodRuntimeList - Create:
access 01-08/15:47:14 DEBUG [inetServ-load-p-10-t-1] InetAccountingPeriodList - Create:
access 01-08/15:47:14 INFO [inetServ-load-p-10-t-1] InetServRuntimeMap - Adding InetServRuntime: 1792
access 01-08/15:47:14 INFO [inetServ-load-p-10-t-1] InetServRuntimeMap - ContractId: 4330; status: 0; servId: 1792
786
Options [] TariffModuleTreeSet [29:24.06.2009-…; ]
Device state: 1; optionSet:
access 01-08/15:47:14 DEBUG [inetServ-load-p-10-t-1] ContractTariffOptionList - Create:
access 01-08/15:47:14 DEBUG [inetServ-load-p-10-t-1] ProductPeriodRuntimeList - Create:
access 01-08/15:47:14 DEBUG [inetServ-load-p-10-t-1] InetAccountingPeriodList - Create:
access 01-08/15:47:14 INFO [inetServ-load-p-10-t-1] InetServRuntimeMap - Adding InetServRuntime: 2048
access 01-08/15:47:14 INFO [inetServ-load-p-10-t-1] InetServRuntimeMap - ContractId: 4703; status: 3; servId: 2048
.....................
access 01-08/15:48:01 INFO [inetServ-load-p-10-t-1] InetServRuntimeMap - Loaded 4797 inetServs.
access 01-08/15:48:01 INFO [main] InetServRuntimeMap - Load inetServs from database complete. Loaded 4797 inetServs.
access 01-08/15:48:02 DEBUG [main] EventProcessor - Add Thread[Thread-19,5,main] to BG.Event.ru.bitel.bgbilling.modules.inet.api.server.event.InetReloadEvent WHERE moduleId=10
access 01-08/15:48:02 INFO [main] Application - Started ru.bitel.bgbilling.modules.inet.access.Access@2cbc9673
access 01-08/15:48:02 INFO [main] AnnotatedMBean - Register MBean ru.bitel.bgbilling.modules.inet.runtime:type=InetServRuntimeMap
access 01-08/15:48:02 INFO [main] AnnotatedMBean - Register MBean ru.bitel.bgbilling.modules.inet.access:type=InetConnectionManager
radius 01-08/15:48:02 INFO [main] Application - Starting ru.bitel.bgbilling.modules.inet.radius.InetRadiusProcessor@65c2fee
..........
Начинают уже парситься сервисы с id > 1228 - очень хорошо, так и надо...
Дальше пошли грузиться NAS:
Код:
radius-processor 01-08/15:48:02 INFO [main] InetRadiusProcessor - Reloading NAS list
radius-processor 01-08/15:48:02 INFO [main] InetNasList - Loading NAS list...
radius-processor 01-08/15:48:02 DEBUG [main] Nas - activate services: [33]
radius-processor 01-08/15:48:02 INFO [main] AnnotatedMBean - Register MBean ru.bitel.oss.systems.inventory.resource.server.ip.dynamic:type=IpResourceReserveManager,name=26
radius-processor 01-08/15:48:02 INFO [main] NasList - LOADED NAS: Nas id: vpn_be; ip: 192.168.40.68
CONFIG:
accounting.deviceTypeIds=5
accounting.tariffication.checkPrice=0
accounting.worker.1.event.tracking.1.batchSize=500
accounting.worker.1.event.tracking.1.delay.millis=200
accounting.worker.1.serv.tracking.1.accountingPeriodActivate=1
accounting.worker.1.serv.tracking.1.batchSize=100
accounting.worker.1.serv.tracking.1.delay=20
accounting.worker.1.serv.tracking.1.servTypeIds=3
accounting.worker.1.tariffication.1.batchSize=1000
accounting.worker.1.tariffication.1.delay=10
accounting.worker.1.tariffication.1.minDeltaAmount=0
accounting.worker.1.thread.count=4
accounting.worker.1.tracking.1.batchSize=1000
accounting.worker.1.tracking.1.delay=10
accounting.worker.2.flushing.1.batchSize=500
accounting.worker.2.flushing.1.delay=20
accounting.worker.2.flushing.1.minDeltaAccount=0
accounting.worker.2.flushing.1.minDeltaAmount=0
accounting.worker.2.thread.count=1
accounting.worker.3.finishing.1.batchSize=500
accounting.worker.3.finishing.1.delay=20
accounting.worker.3.thread.count=1
add.mppe.enc.types.and.policy=0
app.id=4
app.name=BGInetAccessVPN
bgsecure.check=1
bgsecure.log=1
card.activate.serviceIds=33
card.moduleId=9
check.double.tariff=0
closed.date.enabled=0
commonIdentifierName=rootDeviceId
connection.auto.minDuration=600
connection.close.timeout=900
connection.close.timeout.forceClose=1
connection.start.fromAccept=0
connection.start.fromUpdate=1
connection.suspend.timeout=900
contract.balance.csv.xslt=contract_balance_print_csv.xsl
contract.balance.xslt=contract_balance_print.xsl
contract.csv.xslt=contract_balance_detail_print_csv.xsl
contract.status.active.codes=0
contract.status.deprected=
contract.status.list=0:Активен;1:В отключении;2:Отключен;3:Закрыт;4:Приостановлен;5:В подключении
contract.status.monitor.saldo.show.mode=1
contract.status.no.manual.set=1,5
contract.status.suspend.codes=3,4
contract.xslt=contract_balance_detail_print.xsl
contractcard.1=card_inet.xsl:Карта регистрации
credit.contract.active.status=0
credit.contract.open.by.payment.status=2,3
credit.contract.override.future.to.active.status=2
datalog.dhcp.chunk.size=131072
datalog.dhcp.compression.type=1
datalog.dhcp.dir=data/dhcp
datalog.radius.chunk.size=262144
datalog.radius.compression.type=0
datalog.radius.dir=data/radius
db.driver=com.mysql.jdbc.Driver
db.pswd=xxxxxxxxxxxxxxxxxxxxx
db.url=jdbc:mysql://192.168.120.211/bgbilling?useUnicode=true&characterEncoding=Cp1251&allowUrlInLocalInfile=true&zeroDateTimeBehavior=convertToNull&jdbcCompliantTruncation=false&queryTimeoutKillsConnection=true&connectTimeout=1000
db.user=xxxxxxxxxxxxxxxx
db.validationTimeout=10
deviceId=17
dynamic.src.dir=dyn
dynamic.src.encoding=UTF-8
header.name.remote.addr=X-Real-IP
independ.subcontract.status.change=0
loader.add.process=1
log.function.process=1
logon.counter.max=20
logon.lock.cache.expired=600
logon.lock.cache.size=100
logon.timeout.action=+
logon.timeout.lock=21600
logon.timeout.period=0
moduleId=10
mq.pswd=xxxxxxxxxxxxx
mq.url=failover:(tcp://192.168.120.211:61616)
mq.user=xxxxxxxxxxxx
multipart.max.post.size=1048576
nas.radius.connection.checkDuplicate=2
nas.radius.deviceTypeIds=6
nas.radius.inetOption.19.attributes=Mikrotik-Rate-Limit=10000k/256k
nas.radius.inetOption.20.attributes=Mikrotik-Rate-Limit=10000k/512k
nas.radius.inetOption.21.attributes=Mikrotik-Rate-Limit=10000k/1024k
nas.radius.inetOption.22.attributes=Mikrotik-Rate-Limit=10000k/2048k
nas.radius.inetOption.23.attributes=Mikrotik-Rate-Limit=10000k/100000k
nas.radius.inetOption.24.attributes=Mikrotik-Rate-Limit=10000k/8192k
nas.radius.inetOption.25.attributes=Mikrotik-Rate-Limit=10000k/128k
nas.radius.inetOption.26.attributes=Mikrotik-Rate-Limit=10000k/5000k
nas.radius.inetOption.27.attributes=Mikrotik-Rate-Limit=10000k/1k
nas.radius.inetOption.28.attributes=Mikrotik-Rate-Limit=10000k/3000k
nas.radius.inetOption.29.attributes=Mikrotik-Rate-Limit=10000k/6000k
nas.radius.inetOption.30.attributes=Mikrotik-Rate-Limit=10000k/12000k
nas.radius.inetOption.31.attributes=Mikrotik-Rate-Limit=10000k/60000k
nas.radius.inetOption.32.attributes=Mikrotik-Rate-Limit=10000k/80000k
nas.radius.inetOption.33.attributes=Mikrotik-Rate-Limit=10000k/10000k
nas.radius.inetOption.34.attributes=Mikrotik-Rate-Limit=10000k/20000k
nas.radius.inetOption.35.attributes=Mikrotik-Rate-Limit=10000k/30000k
nas.radius.inetOption.36.attributes=Mikrotik-Rate-Limit=10000k/40000k
nas.radius.inetOption.37.attributes=Mikrotik-Rate-Limit=10000k/50000k
nas.radius.port=1700
nas.radius.realm.default.ipCategories=26
nas.radius.servSearchMode=0
nas.radius.username.removeDomain=1
need.lic.alarm=1
password.chars=1234567890abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ!@#$%^&*()
password.length.auto=6
password.length.max=10
password.length.min=5
radius.connection.checkDuplicate=2
radius.deviceTypeIds=6
radius.inetOption.19.attributes=Mikrotik-Rate-Limit=10000k/256k
radius.inetOption.20.attributes=Mikrotik-Rate-Limit=10000k/512k
radius.inetOption.21.attributes=Mikrotik-Rate-Limit=10000k/1024k
radius.inetOption.22.attributes=Mikrotik-Rate-Limit=10000k/2048k
radius.inetOption.23.attributes=Mikrotik-Rate-Limit=10000k/100000k
radius.inetOption.24.attributes=Mikrotik-Rate-Limit=10000k/8192k
radius.inetOption.25.attributes=Mikrotik-Rate-Limit=10000k/128k
radius.inetOption.26.attributes=Mikrotik-Rate-Limit=10000k/5000k
radius.inetOption.27.attributes=Mikrotik-Rate-Limit=10000k/1k
radius.inetOption.28.attributes=Mikrotik-Rate-Limit=10000k/3000k
radius.inetOption.29.attributes=Mikrotik-Rate-Limit=10000k/6000k
radius.inetOption.30.attributes=Mikrotik-Rate-Limit=10000k/12000k
radius.inetOption.31.attributes=Mikrotik-Rate-Limit=10000k/60000k
radius.inetOption.32.attributes=Mikrotik-Rate-Limit=10000k/80000k
radius.inetOption.33.attributes=Mikrotik-Rate-Limit=10000k/10000k
radius.inetOption.34.attributes=Mikrotik-Rate-Limit=10000k/20000k
radius.inetOption.35.attributes=Mikrotik-Rate-Limit=10000k/30000k
radius.inetOption.36.attributes=Mikrotik-Rate-Limit=10000k/40000k
radius.inetOption.37.attributes=Mikrotik-Rate-Limit=10000k/50000k
radius.port=1700
radius.realm.default.ipCategories=26
radius.port=1700
radius.realm.default.ipCategories=26
radius.servSearchMode=0
radius.username.removeDomain=1
reject.limit.update=0
rootDeviceId=11
sa.connection.closeInsteadModify=1
scheduler.nonperiodic.thread.count=5
scheduler.periodic.thread.count=5
serv.disableOnTariffError=0
serv.password.length.auto=6
server.error.403=/error/error403.html
server.error.404=/error/error404.html
server.response.debug=0
session.close.timeout=120
session.split.onDeviceState=1
session.split.onTariffOption=1
session.suspend.timeout=60
.............
Насы загрузились, при этом некоторые директивы загрузились дважды (?)
Дальше видно, что activemq начинает рассылать одни и теже сообщения всем компам с работающими
access+accounting серверами (deviceId: 7; inetServId: 750 - явно что нашему access-serverу девайсы с ид=7 и сервисы с ид=750
д.б. абслолютно фиолетовы):
Код:
mq 01-08/15:48:02 DEBUG [event-proc-p-2-t-1] Consumer - Caught from BGInetAccess Event[ru.bitel.bgbilling.modules.inet.access.event.InetServDeviceStateAndOptionsModifiedEvent] moduleId: 10; pluginId: no; cid: g
lobal; scid: -1; userId: -1; deviceId: 7; inetServId: 750; state: 0; optionSet: ; timestamp: 1389181672992
mq 01-08/15:48:02 INFO [event-proc-p-2-t-1] InetServRuntimeMap - Caught event: Event[ru.bitel.bgbilling.modules.inet.access.event.InetServDeviceStateAndOptionsModifiedEvent] moduleId: 10; pluginId: no; cid: gl
obal; scid: -1; userId: -1; deviceId: 7; inetServId: 750; state: 0; optionSet: ; timestamp: 1389181672992
mq 01-08/15:48:03 INFO [event-proc-p-2-t-1] InetServRuntimeMap - Caught event: Event[ru.bitel.bgbilling.modules.inet.access.event.InetServDeviceStateAndOptionsModifiedEvent] moduleId: 10; pluginId: no; cid: gl
obal; scid: -1; userId: -1; deviceId: 6; inetServId: 512; state: 0; optionSet: ; timestamp: 1389181673718
mq 01-08/15:48:03 DEBUG [event-proc-p-2-t-1] Consumer - Caught from BGInetAccess Event[ru.bitel.bgbilling.modules.inet.access.event.InetServDeviceStateAndOptionsModifiedEvent] moduleId: 10; pluginId: no; cid: g
lobal; scid: -1; userId: -1; deviceId: 6; inetServId: 509; state: 0; optionSet: ; timestamp: 1389181673727
mq 01-08/15:48:03 INFO [event-proc-p-2-t-1] InetServRuntimeMap - Caught event: Event[ru.bitel.bgbilling.modules.inet.access.event.InetServDeviceStateAndOptionsModifiedEvent] moduleId: 10; pluginId: no; cid: gl
obal; scid: -1; userId: -1; deviceId: 6; inetServId: 509; state: 0; optionSet: ; timestamp: 1389181673727
Наконец то по netstat -napu открылся порт 1814 . Прошло n-ое кол-во секунд...
Код:
..............
radius 01-08/15:48:04 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.modules.inet.radius.InetRadiusProcessor$1@512566c9 to BG.Event.ru.bitel.bgbilling.modules.inet.api.server.event.InetReloadEvent WHERE m
oduleId=10
radius 01-08/15:48:04 INFO [main] Application - Started ru.bitel.bgbilling.modules.inet.radius.InetRadiusProcessor@65c2fee
radius 01-08/15:48:04 INFO [main] Application - Starting ru.bitel.bgbilling.modules.inet.radius.InetRadiusListener@14b5d05b [queue_size: 0; threads_active: 0; largest: 0; core: 10; pool_size: 0; recv_socket_bu
f_size: 114 688; recv_buf_size: 524 288]
radius 01-08/15:48:04 INFO [main] DatagramChannelListener - Open socket [0.0.0.0/0.0.0.0:1814]
radius 01-08/15:48:04 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.modules.inet.radius.InetRadiusListener socket init ok.
radius 01-08/15:48:04 INFO [main] Application - Started ru.bitel.bgbilling.modules.inet.radius.InetRadiusListener@14b5d05b [queue_size: 0; threads_active: 0; largest: 0; core: 10; pool_size: 0; recv_socket_buf
_size: 114 688; recv_buf_size: 524 288]
..........
connection 01-08/15:48:04 INFO [sa-p-11-t-4] ServiceActivatorSet - Connecting to device
connection 01-08/15:48:04 DEBUG [sa-p-11-t-4] AcknowledgeConsumer - Caught BGBillingServer:Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaServInitEvent] moduleId: 10; pluginId: no; cid: global; sci
d: -1; userId: 8; deviceId: 12; inetServId: 5621; timestamp: 1389169157708
connection 01-08/15:48:04 INFO [sa-p-11-t-4] ServiceActivatorDeviceWorker - Do task deviceId: 12; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaServInitEvent] moduleId: 10; pluginId: no; cid: glo
bal; scid: -1; userId: 8; deviceId: 12; inetServId: 5621; timestamp: 1389169157708
connection 01-08/15:48:04 INFO [sa-p-11-t-4] ServiceActivatorDeviceWorker - Do InetSaServInitEvent task
connection 01-08/15:48:04 INFO [sa-p-11-t-4] ServiceActivatorDeviceWorker - Do task deviceId: 12; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaServModifyEvent] moduleId: 10; pluginId: no; cid: 1
0728; scid: -1; userId: -1; oldInetServ: 5728; newInetServ: null; newInetServState: -1; newInetServOptionList: ; timestamp: 1389181684939
connection 01-08/15:48:04 WARN [sa-p-11-t-4] InetApplication - Accounting period not found for inetServ:5621
connection 01-08/15:48:04 INFO [sa-p-11-t-4] InetApplication - OptionSet: []
connection 01-08/15:48:04 INFO [sa-p-11-t-4] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=3; inetServId: 5622; call: true; oldState: 0; newState: -1; oldOptionSet: ; newOptio
nSet:
connection 01-08/15:48:04 INFO [sa-p-11-t-4] ServiceActivatorDeviceWorker - Processing deviceId:12; command ServiceActivatorEvent type=3; inetServId: 5622; call: true; oldState: 0; newState: -1; oldOptionSet: ; newOptionSet:
.................
Начали работать....
И сразу начался ад !:Код:
access 01-08/16:11:20 DEBUG [access-p-6-t-1] SessionCountManager - Run SessionCountManager...
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:177 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:374 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:239 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:333 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:1106 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:305 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:558 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:21 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:14 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:60 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:1077 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:242 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:608 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:1213 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:1105 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:553 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:1164 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:436 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:422 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:361 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:159 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:231 is null
access 01-08/16:11:20 WARN [access-p-6-t-1] SessionCountManager - inetServRuntime:66 is null
....................
Ну зачем accessy лезть в сервисы с ид ниже 1228 ???.
Я бы смирился, но all.log от этих записей за 5 мин распух до 96 мегов, и продолжал пухнуть дальше, с космической скоростью!!!
Ещё раз один и тот же вопрос: поможет ли здесь access.group=1 и куда эту дерективу втыкать ?