forum.bitel.ru :: Просмотр темы - Циклические разрывы сессии

##### FROM access.log line:412996 ############

Packet type: Access-Request
Identifier: 144
Authenticator: {11 48 6F FD 76 3D E7 5E 6A 1C CF 0C 9B C4 52 63}
Attributes:
NAS-Identifier=BRAS-CCR-1036-FL-50.7
User-Name=v11255
CHAP-Password={01 87 D9 BF F6 F6 2E 1C 3B 3C F0 FF FD 0A 98 11 0D}
NAS-IP-Address=176.67.50.7
NAS-Port=16050920
Service-Type=2
Framed-Protocol=1
NAS-Port-Id=pppoe-vlan-148
CHAP-Challenge=:'m�y�]XN�y�
NAS-Port-Type=15
Called-Station-Id=smartkom_pppoe
Calling-Station-Id=E4:8D:8C:31:87:80

radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS:
Packet type: Access-Request
Identifier: 144
Authenticator: {11 48 6F FD 76 3D E7 5E 6A 1C CF 0C 9B C4 52 63}
Attributes:
NAS-Identifier=BRAS-CCR-1036-FL-50.7
User-Name=v11255
CHAP-Password={01 87 D9 BF F6 F6 2E 1C 3B 3C F0 FF FD 0A 98 11 0D}
NAS-IP-Address=176.67.50.7
NAS-Port=16050920
Service-Type=2
Framed-Protocol=1
NAS-Port-Id=pppoe-vlan-148
CHAP-Challenge=:'m�y�]XN�y�
NAS-Port-Type=15
Called-Station-Id=smartkom_pppoe
Calling-Station-Id=E4:8D:8C:31:87:80

radius 11-10/16:55:32 DEBUG [rdsLstnr-p-9-t-3] RadiusProcessor - Create new radius session.
radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetNas - Search by username=v11255
radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusProcessor - [username=v11255] Authenticated as inetServId:1407
radius 11-10/16:55:32 DEBUG [rdsLstnr-p-9-t-3] InetNas - agentRemoteId=null
radius 11-10/16:55:32 DEBUG [rdsLstnr-p-9-t-3] InetRadiusProcessor - Identifier from request: null
radius 11-10/16:55:32 DEBUG [rdsLstnr-p-9-t-3] InetRadiusProcessor - MAC-address from request:
radius 11-10/16:55:32 DEBUG [rdsLstnr-p-9-t-3] InetAccountingPeriodList - Create:
AccountingPeriod: 1367: 10.11.2016 00:00:00.0 - 30.11.2016 23:59:59.999
radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetApplication - TariffOptionMap: {}
radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetApplication - inetServ[id=1407] balance ok: ru.bitel.bgbilling.kernel.contract.balance.server.ConvergenceBalanceRuntime$1@6fa18af2
radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetApplication - OptionSet: [20]
radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusProcessor - Write new waiting connection to DB
radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusProcessor - New connection id=43049
radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusProcessor - Return code=0
radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusProcessor - RESPONSE_BEFORE_POSTPROCESS:
Packet type: Access-Accept
Identifier: 144
Authenticator: {}
Attributes:
Acct-Interim-Interval=60
Service-Type=2
Framed-Protocol=1
Framed-IP-Address=176.67.51.226
Session-Timeout=604800
Mikrotik-Rate-Limit=20M

Process time auth: 3

radius 11-10/16:55:32 DEBUG [rdsLstnr-p-9-t-3] ProcessorRequest - Sending to /176.67.50.7:47209
radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusListenerWorker - RESPONSE:
Packet type: Access-Accept
Identifier: 144
Authenticator: {32 CD 1B F4 CA C6 C7 BC 7E C6 39 E6 7C F3 16 28}
Attributes:
Acct-Interim-Interval=60
Service-Type=2
Framed-Protocol=1
Framed-IP-Address=176.67.51.226
Session-Timeout=604800
Mikrotik-Rate-Limit=20M

Process time auth: 3

mq 11-10/16:55:32 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 4336; scid: -1; userId: 0; type: 1; deviceId: 7; connectionId: 43049; timestamp: 1478775332256
mq 11-10/16:55:32 INFO [event-proc-p-2-t-1] InetConnectionManager - Add connection: InetConnection [id=43049-0, iface=7:16050920, sessId=8184e5fe, start=10.11.2016 16:55:32, uname=v11255, addr=176.67.51.226]
mq 11-10/16:55:32 INFO [event-proc-p-2-t-1] InetConnectionMap - interfaceId not set
connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorSet - Connecting to device
connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorSet - Skip device:8 with disabled ServiceActivator
connection 11-10/16:55:32 DEBUG [sa-p-14-t-30] AcknowledgeConsumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountingEvent] moduleId: 23; pluginId: no; cid: 4336; scid: -1; userId: 0; type: 1; deviceId: 7; connectionId: 43049; timestamp: 1478775332256
connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorDeviceWorker - Do task deviceId: 7; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountingEvent] moduleId: 23; pluginId: no; cid: 4336; scid: -1; userId: 0; type: 1; deviceId: 7; connectionId: 43049; timestamp: 1478775332256
connection 11-10/16:55:32 INFO [sa-p-14-t-30] InetApplication - TariffOptionMap: {}
connection 11-10/16:55:32 INFO [sa-p-14-t-30] InetApplication - OptionSet: [20]
connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=4; inetServId: 1407; call: true; oldState: 1; newState: 1; oldOptionSet: 20; newOptionSet: 20
connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorDeviceWorker - Processing deviceId:7; command ServiceActivatorEvent type=4; inetServId: 1407; call: true; oldState: 1; newState: 1; oldOptionSet: 20; newOptionSet: 20
connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorSet - Invoking onAccountingStart
connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorDeviceWorker - Process event type[4] result=true
mq 11-10/16:55:32 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 2729; scid: -1; userId: 0; type: 3; deviceId: 7; connectionId: 42630; timestamp: 1478775332345
mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 13602; scid: -1; userId: 0; type: 3; deviceId: 9; connectionId: 42971; timestamp: 1478775332958
mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 13610; scid: -1; userId: 0; type: 3; deviceId: 9; connectionId: 37819; timestamp: 1478775333238
mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 11789; scid: -1; userId: 0; type: 3; deviceId: 7; connectionId: 22188; timestamp: 1478775333397
mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 6748; scid: -1; userId: 0; type: 3; deviceId: 7; connectionId: 34298; timestamp: 1478775333398
mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 8056; scid: -1; userId: 0; type: 3; deviceId: 7; connectionId: 41551; timestamp: 1478775333398
mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 17568; scid: -1; userId: 0; type: 3; deviceId: 9; connectionId: 42403; timestamp: 1478775333714
mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 4215; scid: -1; userId: 0; type: 3; deviceId: 9; connectionId: 42431; timestamp: 1478775333714
radius 11-10/16:55:33 INFO [rdsLstnr-p-9-t-2] RadiusListenerWorker - REQUEST:
Packet type: Access-Request
Identifier: 150
Authenticator: {E5 8F 31 32 BF A9 CA BB A0 40 A0 A2 EE 61 89 BD}
Attributes:
NAS-Identifier=BRAS-CCR-1036-FL-50.7
User-Name=k12425
CHAP-Password={01 60 6D D6 B7 DB 2B 0E 27 27 4D 26 74 27 7E 6E FD}
NAS-IP-Address=176.67.50.7
NAS-Port=16050921
Service-Type=2
Framed-Protocol=1
NAS-Port-Id=pppoe-vlan-598
CHAP-Challenge=@ �5c�r��y��
NAS-Port-Type=15
Called-Station-Id=smartkom_pppoe
Calling-Station-Id=18:A6:F7:5B:8D:29

radius 11-10/16:55:33 INFO [rdsLstnr-p-9-t-2] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS:
Packet type: Access-Request
Identifier: 150
Authenticator: {E5 8F 31 32 BF A9 CA BB A0 40 A0 A2 EE 61 89 BD}
Attributes:
NAS-Identifier=BRAS-CCR-1036-FL-50.7
User-Name=k12425
CHAP-Password={01 60 6D D6 B7 DB 2B 0E 27 27 4D 26 74 27 7E 6E FD}
NAS-IP-Address=176.67.50.7
NAS-Port=16050921
Service-Type=2
Framed-Protocol=1
NAS-Port-Id=pppoe-vlan-598
CHAP-Challenge=@ �5c�r��y��
NAS-Port-Type=15
Called-Station-Id=smartkom_pppoe
Calling-Station-Id=18:A6:F7:5B:8D:29

radius 11-10/16:55:33 DEBUG [rdsLstnr-p-9-t-2] RadiusProcessor - Create new radius session.
radius 11-10/16:55:33 INFO [rdsLstnr-p-9-t-2] InetNas - Search by username=k12425
radius 11-10/16:55:33 INFO [rdsLstnr-p-9-t-2] InetRadiusProcessor - [username=k12425 ] InetServ not found.

##################################

####### FROM accounting.log #######

777833 Packet type: Accounting-Request
777834 Identifier: 145
777835 Authenticator: {29 F5 3B 8A 2F BC EF 2F 59 1B 55 FC 2C A1 A3 95}
777836 Attributes:
777837 NAS-Identifier=BRAS-CCR-1036-FL-50.7
777838 User-Name=v11255
777839 NAS-IP-Address=176.67.50.7
777840 NAS-Port=16050920
777841 Service-Type=2
777842 Framed-Protocol=1
777843 Framed-IP-Address=176.67.51.226
777844 Acct-Status-Type=1
777845 Acct-Delay-Time=0
777846 Acct-Session-Id=8184e5fe
777847 Acct-Authentic=1
777848 NAS-Port-Id=pppoe-vlan-148
777849 Event-Timestamp=1478775332
777850 NAS-Port-Type=15
777851 Called-Station-Id=smartkom_pppoe
777852 Calling-Station-Id=E4:8D:8C:31:87:80
777853
777854 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS:
777855 Packet type: Accounting-Request
777856 Identifier: 145
777857 Authenticator: {29 F5 3B 8A 2F BC EF 2F 59 1B 55 FC 2C A1 A3 95}
777858 Attributes:
777859 NAS-Identifier=BRAS-CCR-1036-FL-50.7
777860 User-Name=v11255
777861 NAS-IP-Address=176.67.50.7
777862 NAS-Port=16050920
777863 Service-Type=2
777864 Framed-Protocol=1
777865 Framed-IP-Address=176.67.51.226
777866 Acct-Status-Type=1
777867 Acct-Delay-Time=0
777868 Acct-Session-Id=8184e5fe
777869 Acct-Authentic=1
777870 NAS-Port-Id=pppoe-vlan-148
777871 Event-Timestamp=1478775332
777872 NAS-Port-Type=15
777873 Called-Station-Id=smartkom_pppoe
777874 Calling-Station-Id=E4:8D:8C:31:87:80
777875

777876 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] InetNas - Search by username=v11255
777877 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] InetRadiusProcessor - Creating NasConnection from radius accounting packet
777878 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] InetRadiusProcessor - Connection exist in DB
777879 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] InetNas - agentRemoteId=null
777880 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] InetAccountingPeriodList - Create:
777881 AccountingPeriod: 1367: 10.11.2016 00:00:00.0 - 30.11.2016 23:59:59.999
777882 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] Accounting - Update connection in DB
777883 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] Accounting - Write new session to DB
777884 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] Accounting - New session's id=48932
777885 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] Accounting - Created new AccountingSession.
777886 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] Accounting - Register v11255 on 7:-1
777887 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] connection - 43049:48932 Register ip: 176.67.51.226
777888 mq 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] EventProcessor - Publish: Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountingEvent] moduleId: 23; pluginId: no; cid: 4336; scid: -1; userId: 0; type: 1; dev
777888 iceId: 7; connectionId: 43049; timestamp: 1478775332256
777889 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] Accounting - InetConnection [id=43049-0, iface=7:16050920, sessId=8184e5fe, start=10.11.2016 16:55:32, uname=v11255, addr=176.67.51.226]
777890 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] ProcessorRequest - Sending to /176.67.50.7:46011
777891 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] RadiusListenerWorker - RESPONSE:
777892 Packet type: Accounting-Response
777893 Identifier: 145
777894 Authenticator: {ED 98 A7 66 FC 5F 43 BE 3F D3 32 25 EC C2 49 45}
777895 Attributes:
777896
777897 Process time start: 5
777898

803931 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] SessionTarifficationManager - InetOptionSet: [22]
803932 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 36905:44250 Option set from tariff: [22]
803933 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 36905:44250 Option set full: [22]
803934 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 43049:48932 Before calc inetOptions: 20
803935 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] SessionTarifficationManager - Calculate for 10.11.2016 16:55:40
803936 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] SessionTarifficationManager - TariffOptionMap: {}
803937 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 43049:48932 TariffRequest:
803938 PARAMS: mid: 23; cid: 4336
803939 ServiceCost [serviceId: -1; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 8; cost: null]
803940 ServiceCost [serviceId: -4; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 16070; cost: null]
803941 ServiceCost [serviceId: -5; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 973742; cost: null]
803942 ServiceCost [serviceId: -6; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 84444072; cost: null]
803943 ServiceCost [serviceId: -7; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 430816662; cost: null]
803944 ServiceCost [serviceId: -8; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 258306; cost: null]
803945 ServiceCost [serviceId: -9; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 5454275; cost: null]
803946 HIST:
803947 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 43049:48932 Executed TariffRequest:
803948 PARAMS: mid: 23; cid: 4336
803949 ServiceCost [serviceId: 65; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 8; cost: 0.0] УСЛУГА ВРЕМЯ
803950 ServiceCost [serviceId: 66; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 258306; cost: 0.0] УСЛУГА ВХОДЯЩИЙ
803951 ServiceCost [serviceId: 67; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 5454275; cost: 0.0] УСЛУГА ПРОЧИЙ
803952 ServiceCost [serviceId: 67; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 84444072; cost: 0.0]
803953 ServiceCost [serviceId: 67; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 430816662; cost: 0.0]
803954 ServiceCost [serviceId: 67; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 16070; cost: 0.0]
803955 ServiceCost [serviceId: 67; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 973742; cost: 0.0]
803956 HIST:
803957 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] SessionTarifficationManager - InetOptionSet: [20]
803958 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 43049:48932 Option set from tariff: [20]
803959 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 43049:48932 Option set full: [20]
803960 mq 11-10/16:55:40 INFO [accwrkr-1-p-34-t-1] connection - 43049:48932 inetServ[id=1407] not active.
803961 mq 11-10/16:55:40 INFO [accwrkr-1-p-34-t-1] connection - 43049:48932 Found error 10
803962 mq 11-10/16:55:40 INFO [accwrkr-1-p-34-t-1] connection - 43049:48932 Sending event to stop session...
803963 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] EventProcessor - Publish: Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaStateModifyEvent] moduleId: 23; pluginId: no; cid: 4336; scid: -1; userId: 0; deviceId:
803963 7; inetServId: 1407; connectionId: 43049; state: 0; accessCode: 10; timestamp: 1478775340999
803964 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 20522:44112 Before calc inetOptions: 19
803965 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] SessionTarifficationManager - Calculate for 10.11.2016 16:55:40
803966 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] SessionTarifficationManager - TariffOptionMap: {}
803967 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 20522:44112 TariffRequest:

Автор:	arj57 [ 11 ноя 2016, 13:36 ]
Заголовок сообщения:	Циклические разрывы сессии
Добрый день! Переводим клиентов с модуля PPPoE на Inet. При работе с модулем PPPoE у клиента проблем нет. (В субдоговоре клиента присутствуют как модуль PPPoE, так и модуль Inet). У некоторых клиентов через несколько минут после перевода на Inet и подключения наблюдаются циклические разрывы сессии (Pod-пакеты от биллинга). При этом в договоре состояние сервиса в модуле Inet - "Недостаточно средств". Затем сессия поднимается и вновь рвется. Тип инициации сессии - по сигналу (RADIUS start\stop) Привязка типов трафика - Netflow. Режим супер- и субдоговоров - кредит. Лимит на двух субдоговорах (-99999999.99), остаток на супердоговоре (-153000.00). В конфигурации BGBilling указан параметр: balance.convergence.subLimitMode=1 Если в этой ситуации повторно заполнить лимит на субдоговоре значением (-99999999.99), разрывы сессии прекращаются, но могут появиться опять через несколько дней. Такой же эффект, если указать лимит на супердоговоре (-99999999.99). Обычно здесь лимит = 0. Выборка из логов all.log InetAccess, InetAccounting (User-Name=v11255): Код: ##### FROM access.log line:412996 ############ Packet type: Access-Request Identifier: 144 Authenticator: {11 48 6F FD 76 3D E7 5E 6A 1C CF 0C 9B C4 52 63} Attributes: NAS-Identifier=BRAS-CCR-1036-FL-50.7 User-Name=v11255 CHAP-Password={01 87 D9 BF F6 F6 2E 1C 3B 3C F0 FF FD 0A 98 11 0D} NAS-IP-Address=176.67.50.7 NAS-Port=16050920 Service-Type=2 Framed-Protocol=1 NAS-Port-Id=pppoe-vlan-148 CHAP-Challenge=:'m�y�]XN�y� NAS-Port-Type=15 Called-Station-Id=smartkom_pppoe Calling-Station-Id=E4:8D:8C:31:87:80 radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS: Packet type: Access-Request Identifier: 144 Authenticator: {11 48 6F FD 76 3D E7 5E 6A 1C CF 0C 9B C4 52 63} Attributes: NAS-Identifier=BRAS-CCR-1036-FL-50.7 User-Name=v11255 CHAP-Password={01 87 D9 BF F6 F6 2E 1C 3B 3C F0 FF FD 0A 98 11 0D} NAS-IP-Address=176.67.50.7 NAS-Port=16050920 Service-Type=2 Framed-Protocol=1 NAS-Port-Id=pppoe-vlan-148 CHAP-Challenge=:'m�y�]XN�y� NAS-Port-Type=15 Called-Station-Id=smartkom_pppoe Calling-Station-Id=E4:8D:8C:31:87:80 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-9-t-3] RadiusProcessor - Create new radius session. radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetNas - Search by username=v11255 radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusProcessor - [username=v11255] Authenticated as inetServId:1407 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-9-t-3] InetNas - agentRemoteId=null radius 11-10/16:55:32 DEBUG [rdsLstnr-p-9-t-3] InetRadiusProcessor - Identifier from request: null radius 11-10/16:55:32 DEBUG [rdsLstnr-p-9-t-3] InetRadiusProcessor - MAC-address from request: radius 11-10/16:55:32 DEBUG [rdsLstnr-p-9-t-3] InetAccountingPeriodList - Create: AccountingPeriod: 1367: 10.11.2016 00:00:00.0 - 30.11.2016 23:59:59.999 radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetApplication - TariffOptionMap: {} radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetApplication - inetServ[id=1407] balance ok: ru.bitel.bgbilling.kernel.contract.balance.server.ConvergenceBalanceRuntime$1@6fa18af2 radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetApplication - OptionSet: [20] radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusProcessor - Write new waiting connection to DB radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusProcessor - New connection id=43049 radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusProcessor - Return code=0 radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusProcessor - RESPONSE_BEFORE_POSTPROCESS: Packet type: Access-Accept Identifier: 144 Authenticator: {} Attributes: Acct-Interim-Interval=60 Service-Type=2 Framed-Protocol=1 Framed-IP-Address=176.67.51.226 Session-Timeout=604800 Mikrotik-Rate-Limit=20M Process time auth: 3 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-9-t-3] ProcessorRequest - Sending to /176.67.50.7:47209 radius 11-10/16:55:32 INFO [rdsLstnr-p-9-t-3] InetRadiusListenerWorker - RESPONSE: Packet type: Access-Accept Identifier: 144 Authenticator: {32 CD 1B F4 CA C6 C7 BC 7E C6 39 E6 7C F3 16 28} Attributes: Acct-Interim-Interval=60 Service-Type=2 Framed-Protocol=1 Framed-IP-Address=176.67.51.226 Session-Timeout=604800 Mikrotik-Rate-Limit=20M Process time auth: 3 mq 11-10/16:55:32 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 4336; scid: -1; userId: 0; type: 1; deviceId: 7; connectionId: 43049; timestamp: 1478775332256 mq 11-10/16:55:32 INFO [event-proc-p-2-t-1] InetConnectionManager - Add connection: InetConnection [id=43049-0, iface=7:16050920, sessId=8184e5fe, start=10.11.2016 16:55:32, uname=v11255, addr=176.67.51.226] mq 11-10/16:55:32 INFO [event-proc-p-2-t-1] InetConnectionMap - interfaceId not set connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorSet - Connecting to device connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorSet - Skip device:8 with disabled ServiceActivator connection 11-10/16:55:32 DEBUG [sa-p-14-t-30] AcknowledgeConsumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountingEvent] moduleId: 23; pluginId: no; cid: 4336; scid: -1; userId: 0; type: 1; deviceId: 7; connectionId: 43049; timestamp: 1478775332256 connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorDeviceWorker - Do task deviceId: 7; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountingEvent] moduleId: 23; pluginId: no; cid: 4336; scid: -1; userId: 0; type: 1; deviceId: 7; connectionId: 43049; timestamp: 1478775332256 connection 11-10/16:55:32 INFO [sa-p-14-t-30] InetApplication - TariffOptionMap: {} connection 11-10/16:55:32 INFO [sa-p-14-t-30] InetApplication - OptionSet: [20] connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=4; inetServId: 1407; call: true; oldState: 1; newState: 1; oldOptionSet: 20; newOptionSet: 20 connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorDeviceWorker - Processing deviceId:7; command ServiceActivatorEvent type=4; inetServId: 1407; call: true; oldState: 1; newState: 1; oldOptionSet: 20; newOptionSet: 20 connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorSet - Invoking onAccountingStart connection 11-10/16:55:32 INFO [sa-p-14-t-30] ServiceActivatorDeviceWorker - Process event type[4] result=true mq 11-10/16:55:32 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 2729; scid: -1; userId: 0; type: 3; deviceId: 7; connectionId: 42630; timestamp: 1478775332345 mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 13602; scid: -1; userId: 0; type: 3; deviceId: 9; connectionId: 42971; timestamp: 1478775332958 mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 13610; scid: -1; userId: 0; type: 3; deviceId: 9; connectionId: 37819; timestamp: 1478775333238 mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 11789; scid: -1; userId: 0; type: 3; deviceId: 7; connectionId: 22188; timestamp: 1478775333397 mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 6748; scid: -1; userId: 0; type: 3; deviceId: 7; connectionId: 34298; timestamp: 1478775333398 mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 8056; scid: -1; userId: 0; type: 3; deviceId: 7; connectionId: 41551; timestamp: 1478775333398 mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 17568; scid: -1; userId: 0; type: 3; deviceId: 9; connectionId: 42403; timestamp: 1478775333714 mq 11-10/16:55:33 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] moduleId: 23; pluginId: no; cid: 4215; scid: -1; userId: 0; type: 3; deviceId: 9; connectionId: 42431; timestamp: 1478775333714 radius 11-10/16:55:33 INFO [rdsLstnr-p-9-t-2] RadiusListenerWorker - REQUEST: Packet type: Access-Request Identifier: 150 Authenticator: {E5 8F 31 32 BF A9 CA BB A0 40 A0 A2 EE 61 89 BD} Attributes: NAS-Identifier=BRAS-CCR-1036-FL-50.7 User-Name=k12425 CHAP-Password={01 60 6D D6 B7 DB 2B 0E 27 27 4D 26 74 27 7E 6E FD} NAS-IP-Address=176.67.50.7 NAS-Port=16050921 Service-Type=2 Framed-Protocol=1 NAS-Port-Id=pppoe-vlan-598 CHAP-Challenge=@ �5c�r��y�� NAS-Port-Type=15 Called-Station-Id=smartkom_pppoe Calling-Station-Id=18:A6:F7:5B:8D:29 radius 11-10/16:55:33 INFO [rdsLstnr-p-9-t-2] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS: Packet type: Access-Request Identifier: 150 Authenticator: {E5 8F 31 32 BF A9 CA BB A0 40 A0 A2 EE 61 89 BD} Attributes: NAS-Identifier=BRAS-CCR-1036-FL-50.7 User-Name=k12425 CHAP-Password={01 60 6D D6 B7 DB 2B 0E 27 27 4D 26 74 27 7E 6E FD} NAS-IP-Address=176.67.50.7 NAS-Port=16050921 Service-Type=2 Framed-Protocol=1 NAS-Port-Id=pppoe-vlan-598 CHAP-Challenge=@ �5c�r��y�� NAS-Port-Type=15 Called-Station-Id=smartkom_pppoe Calling-Station-Id=18:A6:F7:5B:8D:29 radius 11-10/16:55:33 DEBUG [rdsLstnr-p-9-t-2] RadiusProcessor - Create new radius session. radius 11-10/16:55:33 INFO [rdsLstnr-p-9-t-2] InetNas - Search by username=k12425 radius 11-10/16:55:33 INFO [rdsLstnr-p-9-t-2] InetRadiusProcessor - [username=k12425 ] InetServ not found. ################################## ####### FROM accounting.log ####### 777833 Packet type: Accounting-Request 777834 Identifier: 145 777835 Authenticator: {29 F5 3B 8A 2F BC EF 2F 59 1B 55 FC 2C A1 A3 95} 777836 Attributes: 777837 NAS-Identifier=BRAS-CCR-1036-FL-50.7 777838 User-Name=v11255 777839 NAS-IP-Address=176.67.50.7 777840 NAS-Port=16050920 777841 Service-Type=2 777842 Framed-Protocol=1 777843 Framed-IP-Address=176.67.51.226 777844 Acct-Status-Type=1 777845 Acct-Delay-Time=0 777846 Acct-Session-Id=8184e5fe 777847 Acct-Authentic=1 777848 NAS-Port-Id=pppoe-vlan-148 777849 Event-Timestamp=1478775332 777850 NAS-Port-Type=15 777851 Called-Station-Id=smartkom_pppoe 777852 Calling-Station-Id=E4:8D:8C:31:87:80 777853 777854 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS: 777855 Packet type: Accounting-Request 777856 Identifier: 145 777857 Authenticator: {29 F5 3B 8A 2F BC EF 2F 59 1B 55 FC 2C A1 A3 95} 777858 Attributes: 777859 NAS-Identifier=BRAS-CCR-1036-FL-50.7 777860 User-Name=v11255 777861 NAS-IP-Address=176.67.50.7 777862 NAS-Port=16050920 777863 Service-Type=2 777864 Framed-Protocol=1 777865 Framed-IP-Address=176.67.51.226 777866 Acct-Status-Type=1 777867 Acct-Delay-Time=0 777868 Acct-Session-Id=8184e5fe 777869 Acct-Authentic=1 777870 NAS-Port-Id=pppoe-vlan-148 777871 Event-Timestamp=1478775332 777872 NAS-Port-Type=15 777873 Called-Station-Id=smartkom_pppoe 777874 Calling-Station-Id=E4:8D:8C:31:87:80 777875 777876 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] InetNas - Search by username=v11255 777877 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] InetRadiusProcessor - Creating NasConnection from radius accounting packet 777878 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] InetRadiusProcessor - Connection exist in DB 777879 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] InetNas - agentRemoteId=null 777880 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] InetAccountingPeriodList - Create: 777881 AccountingPeriod: 1367: 10.11.2016 00:00:00.0 - 30.11.2016 23:59:59.999 777882 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] Accounting - Update connection in DB 777883 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] Accounting - Write new session to DB 777884 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] Accounting - New session's id=48932 777885 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] Accounting - Created new AccountingSession. 777886 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] Accounting - Register v11255 on 7:-1 777887 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] connection - 43049:48932 Register ip: 176.67.51.226 777888 mq 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] EventProcessor - Publish: Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountingEvent] moduleId: 23; pluginId: no; cid: 4336; scid: -1; userId: 0; type: 1; dev 777888 iceId: 7; connectionId: 43049; timestamp: 1478775332256 777889 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] Accounting - InetConnection [id=43049-0, iface=7:16050920, sessId=8184e5fe, start=10.11.2016 16:55:32, uname=v11255, addr=176.67.51.226] 777890 radius 11-10/16:55:32 DEBUG [rdsLstnr-p-8-t-2] ProcessorRequest - Sending to /176.67.50.7:46011 777891 radius 11-10/16:55:32 INFO [rdsLstnr-p-8-t-2] RadiusListenerWorker - RESPONSE: 777892 Packet type: Accounting-Response 777893 Identifier: 145 777894 Authenticator: {ED 98 A7 66 FC 5F 43 BE 3F D3 32 25 EC C2 49 45} 777895 Attributes: 777896 777897 Process time start: 5 777898 803931 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] SessionTarifficationManager - InetOptionSet: [22] 803932 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 36905:44250 Option set from tariff: [22] 803933 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 36905:44250 Option set full: [22] 803934 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 43049:48932 Before calc inetOptions: 20 803935 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] SessionTarifficationManager - Calculate for 10.11.2016 16:55:40 803936 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] SessionTarifficationManager - TariffOptionMap: {} 803937 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 43049:48932 TariffRequest: 803938 PARAMS: mid: 23; cid: 4336 803939 ServiceCost [serviceId: -1; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 8; cost: null] 803940 ServiceCost [serviceId: -4; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 16070; cost: null] 803941 ServiceCost [serviceId: -5; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 973742; cost: null] 803942 ServiceCost [serviceId: -6; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 84444072; cost: null] 803943 ServiceCost [serviceId: -7; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 430816662; cost: null] 803944 ServiceCost [serviceId: -8; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 258306; cost: null] 803945 ServiceCost [serviceId: -9; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 5454275; cost: null] 803946 HIST: 803947 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 43049:48932 Executed TariffRequest: 803948 PARAMS: mid: 23; cid: 4336 803949 ServiceCost [serviceId: 65; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 8; cost: 0.0] УСЛУГА ВРЕМЯ 803950 ServiceCost [serviceId: 66; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 258306; cost: 0.0] УСЛУГА ВХОДЯЩИЙ 803951 ServiceCost [serviceId: 67; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 5454275; cost: 0.0] УСЛУГА ПРОЧИЙ 803952 ServiceCost [serviceId: 67; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 84444072; cost: 0.0] 803953 ServiceCost [serviceId: 67; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 430816662; cost: 0.0] 803954 ServiceCost [serviceId: 67; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 16070; cost: 0.0] 803955 ServiceCost [serviceId: 67; date1: ; date2: ; serviceStart: ; serviceEnd: ; accountingPeriodDays: 0; amount: 973742; cost: 0.0] 803956 HIST: 803957 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] SessionTarifficationManager - InetOptionSet: [20] 803958 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 43049:48932 Option set from tariff: [20] 803959 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 43049:48932 Option set full: [20] 803960 mq 11-10/16:55:40 INFO [accwrkr-1-p-34-t-1] connection - 43049:48932 inetServ[id=1407] not active. 803961 mq 11-10/16:55:40 INFO [accwrkr-1-p-34-t-1] connection - 43049:48932 Found error 10 803962 mq 11-10/16:55:40 INFO [accwrkr-1-p-34-t-1] connection - 43049:48932 Sending event to stop session... 803963 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] EventProcessor - Publish: Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaStateModifyEvent] moduleId: 23; pluginId: no; cid: 4336; scid: -1; userId: 0; deviceId: 803963 7; inetServId: 1407; connectionId: 43049; state: 0; accessCode: 10; timestamp: 1478775340999 803964 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 20522:44112 Before calc inetOptions: 19 803965 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] SessionTarifficationManager - Calculate for 10.11.2016 16:55:40 803966 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] SessionTarifficationManager - TariffOptionMap: {} 803967 mq 11-10/16:55:40 DEBUG [accwrkr-1-p-34-t-1] connection - 20522:44112 TariffRequest: В логах после выполнения тарифного запроса в логах появляется запись: Код: inetServ[id=1407] not active Сессия после этого рвется. Подскажите, в какую сторону копать? Информация о версии: Код: Сервер: вер. 7.0.1094 / 24.08.2016 14:51:39 os: Linux; java: Java HotSpot(TM) 64-Bit Server VM, v.1.8.0_102 bill: вер. 7.0.92 / 23.08.2016 18:37:34 card: вер. 7.0.40 / 22.08.2016 16:40:03 dialup: вер. 7.0.318 / 08.04.2016 17:52:02 drweb: вер. 7.0.73 / 08.04.2016 17:52:33 email: вер. 7.0.180 / 25.05.2016 13:53:19 inet: вер. 7.0.669 / 24.08.2016 14:51:52 ipn: вер. 7.0.257 / 24.08.2016 14:51:47 mps: вер. 7.0.196 / 29.07.2016 13:42:35 npay: вер. 7.0.198 / 19.07.2016 18:37:21 phone: вер. 7.0.274 / 18.08.2016 19:43:42 rentsoft: вер. 7.0.65 / 10.06.2016 17:00:01 reports: вер. 7.0.213 / 18.08.2016 19:43:50 rscm: вер. 7.0.180 / 10.06.2016 17:00:08 ru.bitel.bgbilling.plugins.cladr: вер. 7.0.123 / 08.04.2016 17:52:32 trayinfo: вер. 7.0.175 / 10.06.2016 17:00:23 voiceip: вер. 7.0.189 / 08.04.2016 17:52:10 Окружение: Сервер: os: Linux amd64, 3.10.0-327.22.2.el7.x86_64 java: Java HotSpot(TM) 64-Bit Server VM, v.1.8.0_102 jre home: /opt/java/jdk1.8.0_102/jre default tz: 11.11.2016 13:22 OMST +0600 (Asia/Omsk) db time: master: 11.11.2016 13:22 OMST db charset: connection: utf8(utf8_unicode_ci), database: utf8(utf8_unicode_ci) locale: ru_RU uptime: Started: 09.10.2016 04:08:34 Uptime: 33 d 09:13:54

Автор:	Amir [ 11 ноя 2016, 17:09 ]
Заголовок сообщения:	Re: Циклические разрывы сессии
В конфигурации ядра биллинга укажите balance.convergence.subLimitMode=1

Автор:	arj57 [ 11 ноя 2016, 17:57 ]
Заголовок сообщения:	Re: Циклические разрывы сессии
Это происходит при установленном параметре balance.convergence.subLimitMode=1 у некоторых клиентов. У клиентов, где наблюдается это явление, на одном супердоговоре несколько субдоговоров (с лимитом -99999999.99), может, с этим связано? Недели за 3-4 перед этим перевели часть клиентов, у которых на супердоговоре было по одному субдоговору, там такого нет.

Автор:	Amir [ 11 ноя 2016, 19:55 ]
Заголовок сообщения:	Re: Циклические разрывы сессии
Т.е. он у вас изначально установлен был?

Автор:	arj57 [ 14 ноя 2016, 09:05 ]
Заголовок сообщения:	Re: Циклические разрывы сессии
Да, этот параметр был установлен. Я это написал в исходном сообщении, но не выделил, извините. Если эта ошибка проявляется однократно в процессе перевода клиента с PPPoE на Inet, это, конечно, несущественно. Проблема в том, что такая ошибка у нескольких переведенных клиентов появлялась повторно, через несколько дней.

forum.bitel.ru http://forum.bitel.ru/

Циклические разрывы сессии http://forum.bitel.ru/viewtopic.php?f=44&t=12084	Страница 1 из 1

Автор:	Amir [ 14 ноя 2016, 17:12 ]
Заголовок сообщения:	Re: Циклические разрывы сессии
Ошибка происходила, если на обоих (суб и супер) договорах лимит был -99999999.99 (т.е. не 0)? В balance.convergence.subLimitMode в конфигурации ядра нет опечатки или лишнего пробела? После добавления balance.convergence.subLimitMode требуется перезапуск всех приложений. Без balance.convergence.subLimitMode=1 была проблема в том, что ядро использует для зависимого субдоговора при вычислении "недостаточно средств" его собственный лимит, а Inet использовал лимит супердоговора (вместе с его балансом). Получался конфликт, если на одном из договоров лимит 0. С balance.convergence.subLimitMode=1 Inet должен использовать лимит зависимого субдоговора, как и ядро.

Автор:	arj57 [ 15 ноя 2016, 10:10 ]
Заголовок сообщения:	Re: Циклические разрывы сессии
1. Ошибка происходила, если на супердоговоре лимит был 0, а на субдоговоре(ах) лимит(ы) были -99999999. 2. Параметр balance.convergence.subLimitMode=1 перепроверил, без ошибок. Столкнувшись с проблемой ошибки баланса и прочитав https://forum.bitel.ru/viewtopic.php?f=22&t=10605, мы установили этот параметр в конфигурации биллинга и перезагрузили InetAccess и InetAccounting. Массовая проблема ушла, но остались единичные случаи. Попробуем перезагрузить ВСЕ приложения биллинга и понаблюдаем.

Автор:	Amir [ 15 ноя 2016, 18:20 ]
Заголовок сообщения:	Re: Циклические разрывы сессии
Если сервер действительно не перезагружали после изменения параметра, то возможно в этом дело.

Автор:	arj57 [ 02 дек 2016, 12:17 ]
Заголовок сообщения:	Re: Циклические разрывы сессии
После перезагрузки сервера обнаружили, что, версии модулей и ядра биллинга оказались несогласованы (непонятно, как это произошло, обнаружили по датам создания файлов). Привели все файлы в соответствие из бэкапа. Работает нормально 10 дней. Спасибо.

Страница 1 из 1	Часовой пояс: UTC + 5 часов [ Летнее время ]
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/