forum.bitel.ru http://forum.bitel.ru/ |
|
Не создается таблица log_session http://forum.bitel.ru/viewtopic.php?f=5&t=11963 |
Страница 1 из 1 |
Автор: | kleem-head [ 29 сен 2016, 14:21 ] |
Заголовок сообщения: | Не создается таблица log_session |
Доброго времени суток. Разворачиваем тестовый стенд для тестирования перехода с DialUp на Inet. Взяли дамп месячной давности и после запуска RadiusDialUp автоматически не создалась таблица log_session за текущий месяц. При этом сессия устанавливается, но в логах соответственно ничего нет. В каком месте руки кривые? Информация о версии: Клиент: вер. 6.2.835 / 10.08.2016 16:56:20 os: Linux; java: Java HotSpot(TM) 64-Bit Server VM, v.1.8.0_101 Сервер: вер. 6.2.1108 / 24.08.2016 15:03:09 os: Linux; java: Java HotSpot(TM) 64-Bit Server VM, v.1.8.0_77 assist: вер. 6.2.87 / 13.07.2016 17:32:04 bill: вер. 6.2.87 / 10.06.2016 13:28:18 card: вер. 6.2.39 / 26.05.2016 14:50:45 dialup: вер. 6.2.315 / 01.03.2016 00:17:59 email: вер. 6.2.176 / 01.03.2016 00:18:32 inet: вер. 6.2.684 / 24.08.2016 15:03:21 ipn: вер. 6.2.259 / 06.07.2016 19:29:33 mps: вер. 6.2.214 / 14.07.2016 16:43:28 npay: вер. 6.2.196 / 20.07.2016 09:56:08 paymaster: вер. 6.2.55 / 14.07.2016 14:11:47 phone: вер. 6.2.280 / 22.08.2016 15:50:39 reports: вер. 6.2.211 / 22.08.2016 15:50:48 rscm: вер. 6.2.177 / 10.06.2016 13:40:20 ru.bitel.bgbilling.plugins.crm: вер. 6.2.194 / 11.07.2016 17:42:15 ru.bitel.bgbilling.plugins.dispatch: вер. 6.2.85 / 11.07.2016 17:32:00 ru.bitel.bgbilling.plugins.documents: вер. 6.2.171 / 11.07.2016 17:46:28 ru.bitel.bgbilling.plugins.helpdesk: вер. 6.2.181 / 14.06.2016 14:50:40 trayinfo: вер. 6.2.170 / 02.02.2016 17:42:09 voiceip: вер. 6.2.190 / 03.03.2016 18:32:27 wm: вер. 6.2.188 / 29.07.2016 16:09:59 Окружение: Клиент: os: Linux amd64, 4.7.0-0.bpo.1-amd64 java: Java HotSpot(TM) 64-Bit Server VM, v.1.8.0_101 jre home: /usr/lib/jvm/java-8-oracle/jre default tz: 29.09.2016 11:20 MSK +0300 (Europe/Moscow) user tz: 29.09.2016 11:20 MSK +0300 (Europe/Moscow) locale: ru_RU Сервер: os: Linux amd64, 4.5.0-0.bpo.2-amd64 java: Java HotSpot(TM) 64-Bit Server VM, v.1.8.0_77 jre home: /usr/lib/jvm/java-8-oracle/jre default tz: 29.09.2016 11:18 MSK +0300 (Europe/Moscow) db time: master: 29.09.2016 11:18 MSK, trash@trash_1: 29.09.2016 11:18 MSK db charset: connection: utf8(utf8_unicode_ci), database: utf8(utf8_unicode_ci) locale: ru_RU uptime: Started: 29.09.2016 08:04:47 Uptime: 0 d 03:13:28 |
Автор: | stark [ 29 сен 2016, 15:53 ] |
Заголовок сообщения: | Re: Не создается таблица log_session |
A accouning, в частности start пакет в Raius-сервер приходит ? Что вообще есть в логах ? |
Автор: | kleem-head [ 29 сен 2016, 17:52 ] |
Заголовок сообщения: | Re: Не создается таблица log_session |
radius.log 09-29/09:40:50 INFO [main] DefaultServerSetup - Binding javax.jms.ConnectionFactory[org.apache.activemq.ActiveMQConnectionFactory@4abdb505] to java:comp/env/mq/connectionFactory 09-29/09:40:50 INFO [main] DefaultServerSetup - Init DB connection pools 09-29/09:40:50 INFO [main] DefaultServerSetup - Binding JDBC pool "master" to java:comp/env/jdbc/master 09-29/09:40:50 INFO [main] AnnotatedMBean - Register MBean ru.bitel.bgbilling.server.util:type=DatabaseConnectionPool,name=master 09-29/09:40:51 INFO [main] DefaultServerSetup - Init trash pools... 09-29/09:40:51 INFO [main] DefaultServerSetup - Init trash pool trash_1 09-29/09:40:51 INFO [main] DefaultServerSetup - Binding JDBC pool "trash.trash_1." to java:comp/env/jdbc/trash.trash_1. 09-29/09:40:51 INFO [main] AnnotatedMBean - Register MBean ru.bitel.bgbilling.server.util:type=DatabaseConnectionPool,name=trash.trash_1. 09-29/09:40:51 INFO [main] DefaultServerSetup - Init trash pools... 09-29/09:40:51 INFO [main] DefaultServerSetup - Init trash pool trash_1 09-29/09:40:51 INFO [main] DefaultServerSetup - Binding JDBC pool "trash.trash_1." to java:comp/env/jdbc/trash.trash_1. 09-29/09:40:53 INFO [main] Radius - Starting radius auth_port:1812 acct_port:1813 admin_port:1955 09-29/09:40:53 INFO [main] Radius - Init processor class: ru.bitel.bgbilling.modules.dialup.radius.DialUpRadiusProcessor mid: 1 09-29/09:40:53 INFO [main] radius - Eap not enabled (keystore file not loaded). 09-29/09:40:54 INFO [main] Radius - Starting authentication listener... 09-29/09:40:54 INFO [main] Setup - Load config for mid=1 09-29/09:40:54 INFO [main] DatagramChannelListener - Open socket [0.0.0.0/0.0.0.0:1812] 09-29/09:40:54 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.RadiusListener socket init ok. 09-29/09:40:54 INFO [main] Radius - Starting accounting listener... 09-29/09:40:54 INFO [main] DatagramChannelListener - Open socket [0.0.0.0/0.0.0.0:1813] 09-29/09:40:54 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.RadiusListener socket init ok. 09-29/09:40:54 INFO [Thread-21] AdminPortListener - Starting AdminPortListener on 1955 09-29/09:41:31 INFO [rdsLstnr-p-6-t-1] update - REQUEST: Packet type: Accounting-Request Identifier: 36 Authenticator: {98 8E FA C8 21 0C A5 A9 AB B5 A8 38 5E 09 FF 83} Attributes: NAS-Identifier=test-pppoe User-Name=test NAS-IP-Address=192.168.150.31 NAS-Port=0 Service-Type=2 Framed-Protocol=1 Acct-Status-Type=3 Framed-IP-Address=188.124.127.89 Acct-Input-Octets=44865 Acct-Output-Octets=46639 Acct-Session-Id=90e578daa478f02f Acct-Authentic=1 Acct-Session-Time=2104 Acct-Input-Packets=708 Acct-Output-Packets=512 Acct-Input-Gigawords=0 Acct-Output-Gigawords=0 NAS-Port-Id=ppp0 NAS-Port-Type=5 Called-Station-Id=74:d4:35:49:9d:4c Calling-Station-Id=00:0c:76:15:f7:4f 09-29/09:41:31 WARN [rdsLstnr-p-6-t-1] DialUpNas - Not found connection for update packet: Packet type: Accounting-Request Identifier: 36 Authenticator: {98 8E FA C8 21 0C A5 A9 AB B5 A8 38 5E 09 FF 83} Attributes: NAS-Identifier=test-pppoe User-Name=test NAS-IP-Address=192.168.150.31 NAS-Port=0 Service-Type=2 Framed-Protocol=1 Acct-Status-Type=3 Framed-IP-Address=188.124.127.89 Acct-Input-Octets=44865 Acct-Output-Octets=46639 Acct-Session-Id=90e578daa478f02f Acct-Authentic=1 Acct-Session-Time=2104 Acct-Input-Packets=708 Acct-Output-Packets=512 Acct-Input-Gigawords=0 Acct-Output-Gigawords=0 NAS-Port-Id=ppp0 NAS-Port-Type=5 Called-Station-Id=74:d4:35:49:9d:4c Calling-Station-Id=00:0c:76:15:f7:4f 09-29/09:41:31 INFO [rdsLstnr-p-6-t-1] update - RESPONSE: Packet type: Accounting-Response Identifier: 36 Authenticator: {AF 59 A0 EA F3 76 7C 30 05 DC 90 C5 95 9A 8E 88} Attributes: Process time update: 8 09-29/09:42:31 INFO [rdsLstnr-p-6-t-2] update - REQUEST: Packet type: Accounting-Request Identifier: 37 Authenticator: {29 4E 20 DE E9 B3 1F 56 28 F4 15 DC 22 62 A2 39} Attributes: NAS-Identifier=test-pppoe User-Name=test NAS-IP-Address=192.168.150.31 NAS-Port=0 Service-Type=2 Framed-Protocol=1 Acct-Status-Type=3 Framed-IP-Address=188.124.127.89 Acct-Input-Octets=45423 Acct-Output-Octets=46639 Acct-Session-Id=90e578daa478f02f Acct-Authentic=1 Acct-Session-Time=2164 Acct-Input-Packets=717 Acct-Output-Packets=512 Acct-Input-Gigawords=0 Acct-Output-Gigawords=0 NAS-Port-Id=ppp0 NAS-Port-Type=5 Called-Station-Id=74:d4:35:49:9d:4c Calling-Station-Id=00:0c:76:15:f7:4f 09-29/09:42:31 WARN [rdsLstnr-p-6-t-2] DialUpNas - Not found connection for update packet: Packet type: Accounting-Request Identifier: 37 Authenticator: {29 4E 20 DE E9 B3 1F 56 28 F4 15 DC 22 62 A2 39} Attributes: NAS-Identifier=test-pppoe User-Name=test NAS-IP-Address=192.168.150.31 NAS-Port=0 Service-Type=2 Framed-Protocol=1 Acct-Status-Type=3 Framed-IP-Address=188.124.127.89 Acct-Input-Octets=45423 Acct-Output-Octets=46639 Acct-Session-Id=90e578daa478f02f Acct-Authentic=1 Acct-Session-Time=2164 Acct-Input-Packets=717 Acct-Output-Packets=512 Acct-Input-Gigawords=0 Acct-Output-Gigawords=0 NAS-Port-Id=ppp0 NAS-Port-Type=5 Called-Station-Id=74:d4:35:49:9d:4c Calling-Station-Id=00:0c:76:15:f7:4f |
Автор: | stark [ 29 сен 2016, 18:47 ] |
Заголовок сообщения: | Re: Не создается таблица log_session |
kleem-head писал(а): radius.log Acct-Status-Type=2 Это update-пакет. А где start ? А вот и ошибка: kleem-head писал(а): 09-29/09:41:31 WARN [rdsLstnr-p-6-t-1] DialUpNas - Not found connection for update packet: Ему пришел update, он ничего не нашел и ничего не создал. |
Автор: | kleem-head [ 30 сен 2016, 13:19 ] |
Заголовок сообщения: | Re: Не создается таблица log_session |
Start пакетов добился 09-30/10:11:27 INFO [rdsLstnr-p-5-t-1] RadiusListenerWorker - REQUEST: Packet type: Access-Request Identifier: 1 Authenticator: {40 FE 26 46 FE 71 B0 3F CA 3D 1B 24 0D 0E 3E 93} Attributes: NAS-Identifier=test-pppoe User-Name=test NAS-IP-Address=192.168.150.31 NAS-Port=-1 Service-Type=2 NAS-Port-Id= Framed-Protocol=1 NAS-Port-Type=5 Called-Station-Id=74:d4:35:49:9d:4c Calling-Station-Id=00:0c:76:15:f7:4f MS-CHAP2-Response={01 00 BC 03 98 72 05 C5 25 00 50 F5 A0 7B 14 EC E7 AD 00 00 00 00 00 00 00 00 4B 0D 12 D1 75 E2 76 BB 96 79 4E 66 D2 DB B0 F7 BC A8 F3 17 8A B5 FA 54} MS-CHAP-Challenge={A5 01 FA B0 87 E7 BF 77 71 E8 84 1D 46 F2 93 5D} 09-30/10:11:28 INFO [rdsLstnr-p-5-t-1] RadiusListenerWorker - RESPONSE: Packet type: Access-Accept Identifier: 1 Authenticator: {E6 8A 41 C3 09 03 0C 32 AA CD F0 D5 5D 16 D1 BF} Attributes: Acct-Interim-Interval=60 Service-Type=2 Framed-Protocol=1 Framed-IP-Address=188.124.127.48 mpd-filter=1#1=match dst 10.5.0.6 mpd-filter=2#1=match src 10.5.0.6 mpd-limit=in#1=flt1 shape 256000 48000 pass mpd-limit=in#2=all rate-limit 102400000 19200000 38400000 pass mpd-limit=out#1=flt2 shape 256000 48000 pass mpd-limit=out#2=all rate-limit 102400000 19200000 38400000 pass MS-MPPE-Send-Key={D9 BE 8D 2C C3 0E EB 65 2F F7 D4 6F 86 E7 CA 88 C1 07 B2 F3 A6 FD BB 2A 33 92 88 6B 95 DB 21 65 46 26} MS-MPPE-Recv-Key={91 83 15 A0 33 D6 C4 2D 40 7F B6 70 3A C5 9E D9 76 0F 16 F8 91 03 4D DF DC 3B 8C BA 7D 6C 09 A7 FC 99} MS-MPPE-Encryption-Policy={00 00 00 01} MS-MPPE-Encryption-Types={00 00 00 04} MS-CHAP2-Success={3F 53 3D 35 37 35 38 37 35 36 43 37 44 41 35 33 36 43 43 45 34 41 45 35 31 41 30 44 43 45 37 33 33 39 31 37 35 46 30 39 36 41 42} cisco-avpair=lcp:interface-config#1=service-policy input 100M cisco-avpair=lcp:interface-config#1=service-policy output 100M Process time auth: 777 09-30/10:11:28 INFO [rdsLstnr-p-6-t-1] RadiusListenerWorker - REQUEST: Packet type: Accounting-Request Identifier: 1 Authenticator: {5A F3 6D 33 BE 20 16 0F 8E A4 22 34 32 31 AA 2A} Attributes: NAS-Identifier=test-pppoe User-Name=test NAS-IP-Address=192.168.150.31 NAS-Port=0 Service-Type=2 Framed-Protocol=1 Acct-Status-Type=1 Framed-IP-Address=188.124.127.48 Acct-Input-Octets=0 Acct-Output-Octets=0 Acct-Session-Id=90e578daa4791f1c Acct-Authentic=1 Acct-Session-Time=0 Acct-Input-Packets=0 Acct-Output-Packets=0 Acct-Input-Gigawords=0 Acct-Output-Gigawords=0 NAS-Port-Id=ppp0 NAS-Port-Type=5 Called-Station-Id=74:d4:35:49:9d:4c Calling-Station-Id=00:0c:76:15:f7:4f 09-30/10:11:28 INFO [rdsLstnr-p-6-t-1] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 1 Authenticator: {FD D0 19 EE 15 0A CF E5 A2 EA FF 4B 4B 80 80 6B} Attributes: Process time start: 3 09-30/10:12:28 INFO [rdsLstnr-p-6-t-2] update - REQUEST: Packet type: Accounting-Request Identifier: 2 Authenticator: {08 E2 43 43 1C 8E 8E 38 12 E2 F5 CB C6 B1 DD 21} Attributes: NAS-Identifier=test-pppoe User-Name=test NAS-IP-Address=192.168.150.31 NAS-Port=0 Service-Type=2 Framed-Protocol=1 Acct-Status-Type=3 Framed-IP-Address=188.124.127.48 Acct-Input-Octets=7177 Acct-Output-Octets=2677 Acct-Session-Id=90e578daa4791f1c Acct-Authentic=1 Acct-Session-Time=63 Acct-Input-Packets=114 Acct-Output-Packets=32 Acct-Input-Gigawords=0 Acct-Output-Gigawords=0 NAS-Port-Id=ppp0 NAS-Port-Type=5 Called-Station-Id=74:d4:35:49:9d:4c Calling-Station-Id=00:0c:76:15:f7:4f 09-30/10:12:28 WARN [rdsLstnr-p-6-t-2] DialUpNas - Not found connection for update packet: Packet type: Accounting-Request Identifier: 2 Authenticator: {08 E2 43 43 1C 8E 8E 38 12 E2 F5 CB C6 B1 DD 21} Attributes: NAS-Identifier=test-pppoe User-Name=test NAS-IP-Address=192.168.150.31 NAS-Port=0 Service-Type=2 Framed-Protocol=1 Acct-Status-Type=3 Framed-IP-Address=188.124.127.48 Acct-Input-Octets=7177 Acct-Output-Octets=2677 Acct-Session-Id=90e578daa4791f1c Acct-Authentic=1 Acct-Session-Time=63 Acct-Input-Packets=114 Acct-Output-Packets=32 Acct-Input-Gigawords=0 Acct-Output-Gigawords=0 NAS-Port-Id=ppp0 NAS-Port-Type=5 Called-Station-Id=74:d4:35:49:9d:4c Calling-Station-Id=00:0c:76:15:f7:4f 09-30/10:12:28 INFO [rdsLstnr-p-6-t-2] update - RESPONSE: Packet type: Accounting-Response Identifier: 2 Authenticator: {9B 2E B0 8D D3 59 F0 D9 53 9C A8 CE FC AE D7 87} Attributes: Process time update: 3 Но результат тот же. Таблица не создалась. accel-ppp.conf [modules] log_file #log_syslog #log_tcp #log_pgsql #pptp #l2tp pppoe #ipoe auth_mschap_v2 auth_mschap_v1 auth_chap_md5 auth_pap radius ippool sigchld pppd_compat #shaper #chap-secrets #net-snmp #logwtmp #connlimit #ipv6_nd #ipv6_dhcp #ipv6pool [core] log-error=/var/log/accel-ppp/core.log thread-count=2 [common] #single-session=replace #sid-case=upper #sid-source=seq [ppp] verbose=1 min-mtu=1280 mtu=1492 mru=1492 #ccp=0 #check-ip=0 #mppe=require ipv4=require ipv6=deny ipv6-intf-id=0:0:0:1 ipv6-peer-intf-id=0:0:0:2 ipv6-accept-peer-intf-id=1 lcp-echo-interval=20 #lcp-echo-failure=3 lcp-echo-timeout=120 #unit-cache=1000 [auth] #any-login=0 #noauth=0 [pppoe] verbose=1 #ac-name=xxx #service-name=yyy #pado-delay=0 pado-delay=0 #ifname-in-sid=called-sid #tr101=1 #padi-limit=0 #ip-pool=pppoe #interface=eth1,padi-limit=1400 interface=eth0.10 [radius] #sid_in_auth=1 dictionary=/usr/share/accel-ppp/radius/dictionary nas-identifier=test-pppoe nas-ip-address=192.168.150.31 gw-ip-address=10.10.10.2 server=192.168.150.32,sota,auth-port=1812,acct-port=1813,req-limit=0,fail-time=0 dae-server=192.168.150.31:3799,secpas verbose=1 #timeout=3 #max-try=3 #acct-timeout=120 acct-timeout=0 #acct-delay-time=0 #acct-on=0 [client-ip-range] 10.0.0.0/8 [dns] dns1=8.8.8.8 dns2=8.8.8.4 [ip-pool] gw-ip-address=10.10.10.2 #vendor=Cisco #attr=Cisco-AVPair attr=Framed-Pool 192.168.150.210-215 192.168.1.1-255,name=pool1 192.168.2.1-255,name=pool2 192.168.3.1-255,name=pool3 192.168.4.0/24 [log] log-file=/var/log/accel-ppp/accel-ppp.log log-emerg=/var/log/accel-ppp/emerg.log log-fail-file=/var/log/accel-ppp/auth-fail.log #log-debug=/dev/stdout #syslog=accel-pppd,daemon #log-tcp=127.0.0.1:3000 copy=1 #color=1 #per-user-dir=per_user #per-session-dir=per_session #per-session=1 level=5 [log-pgsql] conninfo=user=log log-table=log [pppd-compat] #ip-pre-up=/etc/ppp/ip-pre-up ip-up=/etc/ppp/accel-ppp/ip-up ip-down=/etc/ppp/accel-ppp/ip-down ip-change=/etc/ppp/accel-ppp/ip-change radattr-prefix=/var/run/radattr verbose=1 [chap-secrets] gw-ip-address=192.168.100.1 #chap-secrets=/etc/ppp/chap-secrets #encrypted=0 #username-hash=md5 [shaper] vendor=Cisco attr=Cisco-AVPair #attr=Filter-Id #down-burst-factor=0.1 #up-burst-factor=1.0 #latency=50 #mpu=0 #mtu=0 #r2q=10 #quantum=1500 #cburst=1534 #ifb=ifb0 up-limiter=police down-limiter=tbf #leaf-qdisc=sfq perturb 10 #rate-multiplier=1 verbose=1 [cli] telnet=127.0.0.1:2000 tcp=127.0.0.1:2001 #password=123 [snmp] master=0 agent-name=accel-ppp [connlimit] limit=10/min burst=3 timeout=60 [ipv6-pool] fc00:0:1::/48,64 delegate=fc00:1::/36,48 [ipv6-dns] #fc00:1::1 #fc00:1::2 #fc00:1::3 #dnssl=suffix1.local.net #dnssl=suffix2.local.net. [ipv6-dhcp] verbose=1 pref-lifetime=604800 valid-lifetime=2592000 route-via-gw=1 |
Страница 1 из 1 | Часовой пояс: UTC + 5 часов [ Летнее время ] |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |