Jump to content

purestg2

Alexey Osipov

By Alexey Osipov
in Stargazer modules

 Share

Recommended Posts

Alexey Osipov Точу Зубы

Alexey Osipov

Posted
  • Author
Posted

Это какой-то баг или так надо?

 

Dec 16 20:23:40 stg pppd[4830]: purestg2: stargazer socket has just been closed. Terminating connection.

Это вы видимо старгейзер остановили. Это фича: когда старгейзер останавливается (или падает) все подключения разрываются.

  • Replies 396
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Alexey Osipov
Alexey Osipov

Релиз 2.4: https://github.com/lion-simba/purestg2/releases/tag/2.4   PS. Проект переехал на github.

Alexey Osipov
Alexey Osipov

Плагин авторизации для Stargazer, который работает напрямую с pppd Общая информация Страница проекта (NEW!): http://lion-simba.github.io/purestg2 Последняя версия (NEW!): 2.4 (04.04.2015) Исходный

Alexey Osipov
Alexey Osipov

потому что:   Если поставить пакет stargazer-dev из моего репозитория, то должно собраться.   Либо можно руками все .h файлы из дистрибутива старгейзера скинуть в одну папку и при сборке purestg2

trinux Оборотень

trinux

Posted
Posted

Биллинг не останавливался. Да и происходит это не со всеми пользователями.

trinux Оборотень

trinux

Posted
Posted

2013-12-16 20:23:39 -- purestg2: No pings from PPPD for user "ruslan2" for 120 seconds, terminating connection...

 

 

может просто выключился :)

trinux Оборотень

trinux

Posted
Posted

Очень странно, но происходит сие довольно часто.

 

purestg2: No pings from PPPD for user.........

Alexey Osipov Точу Зубы

Alexey Osipov

Posted
  • Author
Posted

2013-12-16 20:23:39 -- purestg2: No pings from PPPD for user "ruslan2" for 120 seconds, terminating connection...

 

 

может просто выключился :)

Убедитесь, что у вас 'pppdtimeout' в конфиге старгейзера больше, чем 'keepalivetimeout' в конфиге pppd.

yKpon Оборотень

yKpon

Posted
Posted (edited)

Алексей, привет, баг снова повторился

Dec 18 04:39:55 skyprox pppoe-server[24865]: Session 40 created for client 54:e6:fc:9b:54:43 (10.67.15.40) on eth_local2 using Service-Name ''
Dec 18 04:39:55 skyprox pppd[24865]: Plugin /usr/lib/pppd/2.4.5/rp-pppoe.so loaded.
Dec 18 04:39:55 skyprox pppd[24865]: Plugin rp-pppoe.so loaded.
Dec 18 04:39:55 skyprox pppd[24865]: Plugin purestg2.so loaded.
Dec 18 04:39:55 skyprox pppd[24865]: Stargazer (purestg2 2.4) auth plugin initialized.
Dec 18 04:39:55 skyprox pppd[24865]: purestg2: Chap check is allowed.
Dec 18 04:39:55 skyprox pppd[24865]: pppd 2.4.5 started by root, uid 0
Dec 18 04:39:55 skyprox pppd[24865]: purestg2: Connected to stargazer via /var/run/purestg2.sock.
Dec 18 04:39:55 skyprox pppd[24865]: purestg2: ifunit set to 102.
Dec 18 04:39:55 skyprox pppd[24865]: Connected to 54:e6:fc:9b:54:43 via interface eth_local2
Dec 18 04:39:55 skyprox pppd[24865]: Couldn't allocate PPP unit 102 as it is already in use
Dec 18 04:39:55 skyprox pppd[24865]: Using interface ppp0
Dec 18 04:39:55 skyprox pppd[24865]: Connect: ppp0 <--> eth_local2
Dec 18 04:39:55 skyprox pppd[24865]: purestg2: Chap check is allowed.
Dec 18 04:39:55 skyprox pppd[24865]: purestg2: Chap check is allowed.
Dec 18 04:39:55 skyprox pppd[24865]: purestg2: CHAP started.
Dec 18 04:39:55 skyprox pppd[24865]: purestg2: Got passwd for user brat.
Dec 18 04:39:55 skyprox pppd[24865]: peer from calling number 54:E6:FC:9B:54:43 authorized
Dec 18 04:39:55 skyprox pppd[24865]: purestg2: IP choose started.
Dec 18 04:39:55 skyprox pppd[24865]: purestg2: Allowed address.
Dec 18 04:39:55 skyprox pppd[24865]: purestg2: Good address.
Dec 18 04:39:55 skyprox pppd[24865]: local  IP address 10.0.0.252
Dec 18 04:39:55 skyprox pppd[24865]: remote IP address 10.168.1.21
Dec 18 04:39:55 skyprox pppd[24865]: purestg2: User brat connected.
Dec 18 04:39:58 skyprox pppd[17033]: Connection terminated.
Dec 18 04:39:58 skyprox pppd[17033]: Modem hangup
Dec 18 04:39:58 skyprox pppd[17033]: Exit.
Dec 18 04:39:58 skyprox pppoe-server[18080]: Session 3 closed for client 54:e6:fc:9b:54:43 (10.67.15.3) on eth_local2
Edited by yKpon
Alexey Osipov Точу Зубы

Alexey Osipov

Posted
  • Author
Posted

Они одинаковы :)

Ну вот потому и отваливается. Можно вообще убрать обе опции, там по умолчанию нормальные значения стоят: keepalive 60 секунд, а timeout в 5 минут. Итого, если за 5 минут не получили от pppd ни одной весточки, считаем что pppd пропал без вести и отключаем пользователя.

Alexey Osipov Точу Зубы

Alexey Osipov

Posted
  • Author
Posted

yKpon, будь добр более подробную нарезку логов. В частности, интересует момент, когда ifunit 102 был в прошлый раз выдан. А также момент, когда тот старый 102-й pppd написал в логе "purestg2: Disconnected from stargazer" (ну и окрестности).

yKpon Оборотень

yKpon

Posted
Posted (edited)

&nbsp;

yKpon, будь добр более подробную нарезку логов. В частности, интересует момент, когда ifunit 102 был в прошлый раз выдан. А также момент, когда тот старый 102-й pppd написал в логе "purestg2: Disconnected from stargazer" (ну и окрестности).

вот полностью история pid-а

Dec 17 17:25:32 skyprox pppoe-server[17033]: Session 3 created for client 54:e6:fc:9b:54:43 (10.67.15.3) on eth_local2 using Service-Name ''
Dec 17 17:25:32 skyprox pppd[17033]: Plugin /usr/lib/pppd/2.4.5/rp-pppoe.so loaded.
Dec 17 17:25:32 skyprox pppd[17033]: Plugin rp-pppoe.so loaded.
Dec 17 17:25:32 skyprox pppd[17033]: Plugin purestg2.so loaded.
Dec 17 17:25:32 skyprox pppd[17033]: Stargazer (purestg2 2.4) auth plugin initialized.
Dec 17 17:25:32 skyprox pppd[17033]: purestg2: Chap check is allowed.
Dec 17 17:25:32 skyprox pppd[17033]: pppd 2.4.5 started by root, uid 0
Dec 17 17:25:32 skyprox pppd[17033]: purestg2: Connected to stargazer via /var/run/purestg2.sock.
Dec 17 17:25:32 skyprox pppd[17033]: purestg2: ifunit set to 102.
Dec 17 17:25:32 skyprox pppd[17033]: Connected to 54:e6:fc:9b:54:43 via interface eth_local2
Dec 17 17:25:32 skyprox pppd[17033]: Using interface ppp102
Dec 17 17:25:32 skyprox pppd[17033]: Connect: ppp102 <--> eth_local2
Dec 17 17:25:32 skyprox pppd[17033]: purestg2: Chap check is allowed.
Dec 17 17:25:32 skyprox pppd[17033]: purestg2: Chap check is allowed.
Dec 17 17:25:32 skyprox pppd[17033]: purestg2: CHAP started.
Dec 17 17:25:32 skyprox pppd[17033]: purestg2: Got passwd for user brat.
Dec 17 17:25:32 skyprox pppd[17033]: peer from calling number 54:E6:FC:9B:54:43 authorized
Dec 17 17:25:32 skyprox pppd[17033]: purestg2: IP choose started.
Dec 17 17:25:33 skyprox pppd[17033]: purestg2: Allowed address.
Dec 17 17:25:33 skyprox pppd[17033]: purestg2: Good address.
Dec 17 17:25:33 skyprox pppd[17033]: local  IP address 10.0.0.252
Dec 17 17:25:33 skyprox pppd[17033]: remote IP address 10.168.1.21
Dec 17 17:25:33 skyprox pppd[17033]: purestg2: User brat connected.
Dec 18 04:39:52 skyprox pppd[17033]: purestg2: stargazer socket has just been closed. Terminating connection.
Dec 18 04:39:52 skyprox pppd[17033]: purestg2: No ping from stargazer, exiting.
Dec 18 04:39:52 skyprox pppd[17033]: Terminating on signal 15
Dec 18 04:39:52 skyprox pppd[17033]: purestg2: Can't disconnect user brat
Dec 18 04:39:52 skyprox pppd[17033]: Connect time 674.4 minutes.
Dec 18 04:39:52 skyprox pppd[17033]: Sent 3904794042 bytes, received 2464469473 bytes.
Dec 18 04:39:52 skyprox pppd[17033]: Terminating on signal 15
Dec 18 04:39:54 skyprox pppd[17033]: Terminating on signal 15
Dec 18 04:39:58 skyprox pppd[17033]: Connection terminated.
Dec 18 04:39:58 skyprox pppd[17033]: Modem hangup
Dec 18 04:39:58 skyprox pppd[17033]: Exit.
Edited by yKpon
yKpon Оборотень

yKpon

Posted
Posted (edited)

вот так был выдан в прошлый раз

Dec 17 11:58:48 skyprox pppd[30868]: Plugin purestg2.so loaded.
Dec 17 11:58:48 skyprox pppd[30868]: Stargazer (purestg2 2.4) auth plugin initialized.
Dec 17 11:58:48 skyprox pptp[30868]: Plugin pptp.so loaded.
Dec 17 11:58:48 skyprox pptp[30868]: PPTP plugin version 0.8.5 compiled for pppd-2.4.5, linux-2.6.
Dec 17 11:58:48 skyprox pptp[30868]: purestg2: Pap check is allowed.
Dec 17 11:58:48 skyprox pptp[30868]: pppd 2.4.5 started by root, uid 0
Dec 17 11:58:48 skyprox pptp[30868]: purestg2: Connected to stargazer via /var/run/purestg2.sock.
Dec 17 11:58:48 skyprox pptp[30868]: purestg2: ifunit set to 102.
Dec 17 11:58:48 skyprox pptp[30868]: Using interface ppp102
Dec 17 11:58:48 skyprox pptp[30868]: Connect: ppp102 <--> pptp (172.24.1.21)
Dec 17 11:58:48 skyprox pptp[30868]: purestg2: Chap check is allowed.
Dec 17 11:58:48 skyprox pptp[30868]: purestg2: Pap check is allowed.
Dec 17 11:58:48 skyprox pptp[30868]: purestg2: Chap check is allowed.
Dec 17 11:58:50 skyprox pptp[30868]: purestg2: CHAP started.
Dec 17 11:58:50 skyprox pptp[30868]: purestg2: Got passwd for user qwest.
Dec 17 11:58:50 skyprox pptp[30868]: purestg2: IP choose started.
Dec 17 11:58:50 skyprox pptp[30868]: purestg2: Allowed address.
Dec 17 11:58:50 skyprox pptp[30868]: purestg2: Good address.
Dec 17 11:58:51 skyprox pptp[30868]: Cannot determine ethernet address for proxy ARP
Dec 17 11:58:51 skyprox pptp[30868]: local  IP address 10.0.0.254
Dec 17 11:58:51 skyprox pptp[30868]: remote IP address 10.168.3.1
Dec 17 11:58:51 skyprox pptp[30868]: purestg2: User qwest connected.
Dec 17 16:55:24 skyprox pptp[30868]: LCP terminated by peer (^?M-2E^W^@<M-Mt^@^@^@^@)
Dec 17 16:55:24 skyprox pptp[30868]: purestg2: User qwest disconnected.
Dec 17 16:55:24 skyprox pptp[30868]: purestg2: Disconnected from stargazer.
Dec 17 16:55:24 skyprox pptp[30868]: Connect time 296.6 minutes.
Dec 17 16:55:24 skyprox pptp[30868]: Sent 309106615 bytes, received 20222278 bytes.
Dec 17 16:55:24 skyprox pptpd[30867]: CTRL: Reaping child PPP[30868]
Dec 17 16:55:24 skyprox pptp[30868]: Terminating on signal 15
Dec 17 16:55:27 skyprox pptp[30868]: Connection terminated.
Dec 17 16:55:27 skyprox pptp[30868]: Modem hangup
Dec 17 16:55:27 skyprox pptp[30868]: Exit.
кстати предыдущий раз был авторизован через pptpd Edited by yKpon
trinux Оборотень

trinux

Posted
Posted

Скажите пожалуйста, что это значит??

 

2013-12-18 22:22:41 -- purestg2: Accepted new client connection (socket=11)
2013-12-18 22:22:44 -- purestg2: User parubets (socket=11) is connected.
2013-12-18 22:23:36 -- purestg2: User zhdan (socket=9) is disconnected.
2013-12-18 22:28:40 -- purestg2: Accepted new client connection (socket=9)
2013-12-18 22:28:43 -- purestg2: Terminating previous session (oldsocket=11) for user "parubets"
2013-12-18 22:28:43 -- purestg2: User parubets (socket=9) is connected.
2013-12-18 23:13:37 -- purestg2: Accepted new client connection (socket=11)
2013-12-18 23:13:40 -- purestg2: Terminating previous session (oldsocket=9) for user "parubets"
2013-12-18 23:13:40 -- purestg2: User parubets (socket=11) is connected.
2013-12-18 23:16:48 -- purestg2: Accepted new client connection (socket=9)
2013-12-18 23:16:51 -- purestg2: Terminating previous session (oldsocket=11) for user "parubets"
2013-12-18 23:16:51 -- purestg2: User parubets (socket=9) is connected.
2013-12-18 23:17:54 -- purestg2: Accepted new client connection (socket=11)
2013-12-18 23:17:58 -- purestg2: Terminating previous session (oldsocket=9) for user "parubets"
2013-12-18 23:17:58 -- purestg2: User parubets (socket=11) is connected.
2013-12-18 23:18:27 -- purestg2: Accepted new client connection (socket=9)
2013-12-18 23:18:30 -- purestg2: Terminating previous session (oldsocket=11) for user "parubets"
2013-12-18 23:18:30 -- purestg2: User parubets (socket=9) is connected.
Alexey Osipov Точу Зубы

Alexey Osipov

Posted
  • Author
Posted

Это значит, что пользователь "parubets" пытается подключиться дважды, то есть установить одновременно два подключения под одним логином. В этом случае поведение purestg2 определяется опцией 'kickprevious'. Если она установлена, то при попытке повторного подключения предыдущее будет разрываться, а новое устанавливаться (это как у вас сейчас). Если она не установлена, то при наличии одного подключения второе будет запрещаться.

trinux Оборотень

trinux

Posted
Posted

Это значит, что пользователь "parubets" пытается подключиться дважды, то есть установить одновременно два подключения под одним логином. В этом случае поведение purestg2 определяется опцией 'kickprevious'. Если она установлена, то при попытке повторного подключения предыдущее будет разрываться, а новое устанавливаться (это как у вас сейчас). Если она не установлена, то при наличии одного подключения второе будет запрещаться.

Спасибо. И вообще за модуль тоже спасибо :)

  • 2 weeks later...
yKpon Оборотень

yKpon

Posted
Posted (edited)

какая-то не понятная фигня произошла сегодня, у всех абонентов ошибка 619, авторизация PPPoE, в логах миллионами сыпалось

сначала

Dec 28 15:48:57 skyprox kernel: [3973540.454397] nf_conntrack: table full, dropping packet.
Dec 28 15:48:57 skyprox kernel: [3973540.454438] nf_conntrack: table full, dropping packet.
Dec 28 15:48:57 skyprox kernel: [3973540.455457] nf_conntrack: table full, dropping packet.
Dec 28 15:48:57 skyprox kernel: [3973540.455473] nf_conntrack: table full, dropping packet.
Dec 28 15:48:57 skyprox kernel: [3973540.455478] nf_conntrack: table full, dropping packet.
Dec 28 15:48:57 skyprox kernel: [3973540.455494] nf_conntrack: table full, dropping packet.
Dec 28 15:48:57 skyprox kernel: [3973540.519900] nf_conntrack: table full, dropping packet.
Dec 28 15:48:57 skyprox kernel: [3973540.526004] nf_conntrack: table full, dropping packet.
Dec 28 15:49:02 skyprox kernel: [3973545.549297] __ratelimit: 403 callbacks suppressed
Dec 28 15:49:02 skyprox kernel: [3973545.549300] nf_conntrack: table full, dropping packet.
Dec 28 15:49:02 skyprox kernel: [3973545.555684] nf_conntrack: table full, dropping packet.
Dec 28 15:49:02 skyprox kernel: [3973545.557798] nf_conntrack: table full, dropping packet.
Dec 28 15:49:02 skyprox kernel: [3973545.561340] nf_conntrack: table full, dropping packet.
Dec 28 15:49:02 skyprox kernel: [3973545.564035] nf_conntrack: table full, dropping packet.
Dec 28 15:49:02 skyprox kernel: [3973545.564040] nf_conntrack: table full, dropping packet.
Dec 28 15:49:02 skyprox kernel: [3973545.578946] nf_conntrack: table full, dropping packet.
Dec 28 15:49:02 skyprox kernel: [3973545.578960] nf_conntrack: table full, dropping packet.
Dec 28 15:49:02 skyprox kernel: [3973545.584130] nf_conntrack: table full, dropping packet.
Dec 28 15:49:02 skyprox kernel: [3973545.584247] nf_conntrack: table full, dropping packet.
Dec 28 15:49:08 skyprox kernel: [3973550.658189] __ratelimit: 306 callbacks suppressed
Dec 28 15:49:08 skyprox kernel: [3973550.658192] nf_conntrack: table full, dropping packet.
Dec 28 15:49:08 skyprox kernel: [3973550.674095] nf_conntrack: table full, dropping packet.
Dec 28 15:49:08 skyprox kernel: [3973550.674301] nf_conntrack: table full, dropping packet.
Dec 28 15:49:08 skyprox kernel: [3973550.704670] nf_conntrack: table full, dropping packet.
Dec 28 15:49:08 skyprox kernel: [3973550.718084] nf_conntrack: table full, dropping packet.
Dec 28 15:49:08 skyprox kernel: [3973550.719320] nf_conntrack: table full, dropping packet.
Dec 28 15:49:08 skyprox kernel: [3973550.728333] nf_conntrack: table full, dropping packet.
Dec 28 15:49:08 skyprox kernel: [3973550.730922] nf_conntrack: table full, dropping packet.
Dec 28 15:49:08 skyprox kernel: [3973550.884239] nf_conntrack: table full, dropping packet.
Dec 28 15:49:08 skyprox kernel: [3973550.884499] nf_conntrack: table full, dropping packet.
Dec 28 15:49:13 skyprox kernel: [3973555.794354] __ratelimit: 295 callbacks suppressed
Dec 28 15:49:13 skyprox kernel: [3973555.794356] nf_conntrack: table full, dropping packet.
Dec 28 15:49:13 skyprox kernel: [3973555.894352] nf_conntrack: table full, dropping packet.
Dec 28 15:49:13 skyprox kernel: [3973555.901862] nf_conntrack: table full, dropping packet.
Dec 28 15:49:13 skyprox kernel: [3973555.905583] nf_conntrack: table full, dropping packet.
Dec 28 15:49:13 skyprox kernel: [3973555.911336] nf_conntrack: table full, dropping packet.
Dec 28 15:49:13 skyprox kernel: [3973555.912776] nf_conntrack: table full, dropping packet.
Dec 28 15:49:13 skyprox kernel: [3973555.942792] nf_conntrack: table full, dropping packet.
Dec 28 15:49:13 skyprox kernel: [3973555.983516] nf_conntrack: table full, dropping packet.
Dec 28 15:49:13 skyprox kernel: [3973556.045180] nf_conntrack: table full, dropping packet.
Dec 28 15:49:13 skyprox kernel: [3973556.049006] nf_conntrack: table full, dropping packet.
Dec 28 15:49:18 skyprox kernel: [3973561.018377] __ratelimit: 436 callbacks suppressed
Dec 28 15:49:18 skyprox kernel: [3973561.018381] nf_conntrack: table full, dropping packet.
 
потом
 
Dec 28 15:51:27 skyprox pppd[27720]: Plugin /usr/lib/pppd/2.4.5/rp-pppoe.so loaded.
Dec 28 15:51:27 skyprox pppd[27720]: Plugin rp-pppoe.so loaded.
Dec 28 15:51:27 skyprox pppd[27720]: Plugin purestg2.so loaded.
Dec 28 15:51:27 skyprox pppd[27720]: Stargazer (purestg2 2.4) auth plugin initialized.
Dec 28 15:51:27 skyprox pppd[27720]: purestg2: Chap check is allowed.
Dec 28 15:51:27 skyprox pppd[27720]: pppd 2.4.5 started by root, uid 0
Dec 28 15:51:27 skyprox pppd[27720]: purestg2: Can't connect to stargazer's socket /var/run/purestg2.sock. Exiting.
Dec 28 15:51:27 skyprox pppd[27720]: Exit.
Dec 28 15:51:27 skyprox pppoe-server[18080]: Session 20 closed for client 54:e6:fc:9b:54:43 (10.67.15.20) on eth_local2
Dec 28 15:51:27 skyprox pppoe-server[18080]: Sent PADT
Dec 28 15:51:27 skyprox pppd[22306]: Exit.
Dec 28 15:51:27 skyprox pppoe-server[13630]: Session 39 closed for client 00:0c:42:8f:3e:30 (10.67.15.39) on vlan51
Dec 28 15:51:27 skyprox pppoe-server[13630]: Sent PADT
Dec 28 15:51:27 skyprox pppoe-server[27728]: Session 10 created for client 00:e0:52:af:a1:92 (10.67.15.10) on eth_local2 using Service-Name ''
Dec 28 15:51:27 skyprox pppd[27728]: Plugin /usr/lib/pppd/2.4.5/rp-pppoe.so loaded.
Dec 28 15:51:27 skyprox pppd[27728]: Plugin rp-pppoe.so loaded.
Dec 28 15:51:27 skyprox pppd[27728]: Plugin purestg2.so loaded.
Dec 28 15:51:27 skyprox pppd[27728]: Stargazer (purestg2 2.4) auth plugin initialized.
Dec 28 15:51:27 skyprox pppd[27728]: purestg2: Chap check is allowed.
Dec 28 15:51:27 skyprox pppd[27728]: pppd 2.4.5 started by root, uid 0
Dec 28 15:51:27 skyprox pppd[27728]: purestg2: Can't connect to stargazer's socket /var/run/purestg2.sock. Exiting.
Dec 28 15:51:27 skyprox pppd[27728]: Exit.
Dec 28 15:51:27 skyprox pppoe-server[18080]: Session 10 closed for client 00:e0:52:af:a1:92 (10.67.15.10) on eth_local2
Dec 28 15:51:27 skyprox pppoe-server[18080]: Sent PADT
Dec 28 15:51:27 skyprox pppoe-server[18080]: Sent PADT
Dec 28 15:51:27 skyprox pppoe-server[27757]: Session 34 created for client dc:9f:db:32:6c:fc (10.67.15.34) on vlan51 using Service-Name ''
Dec 28 15:51:27 skyprox pppd[27757]: Plugin /usr/lib/pppd/2.4.5/rp-pppoe.so loaded.
Dec 28 15:51:27 skyprox pppd[27757]: Plugin rp-pppoe.so loaded.
Dec 28 15:51:27 skyprox pppd[27757]: Plugin purestg2.so loaded.
Dec 28 15:51:27 skyprox pppd[27757]: Stargazer (purestg2 2.4) auth plugin initialized.
Dec 28 15:51:27 skyprox pppd[27757]: purestg2: Chap check is allowed.
Dec 28 15:51:27 skyprox pppd[27757]: pppd 2.4.5 started by root, uid 0
Dec 28 15:51:27 skyprox pppd[27757]: purestg2: Can't connect to stargazer's socket /var/run/purestg2.sock. Exiting.
Dec 28 15:51:27 skyprox pppd[27757]: Exit.
Dec 28 15:51:27 skyprox pppoe-server[13630]: Session 34 closed for client dc:9f:db:32:6c:fc (10.67.15.34) on vlan51
Dec 28 15:51:27 skyprox pppoe-server[13630]: Sent PADT
Dec 28 15:51:27 skyprox dhcpd: DHCPINFORM from 192.168.5.131 via vlan52
Dec 28 15:51:27 skyprox dhcpd: DHCPACK to 192.168.5.131 (44:87:fc:42:26:20) via vlan52
Dec 28 15:51:27 skyprox pppd[12488]: Exit.
Dec 28 15:51:27 skyprox pppoe-server[13630]: Session 37 closed for client dc:9f:db:32:6c:fc (10.67.15.37) on vlan51
Dec 28 15:51:27 skyprox pppoe-server[13630]: Sent PADT
Dec 28 15:51:28 skyprox pppoe-server[27766]: Session 19 created for client d4:ca:6d:6d:db:d4 (10.67.15.19) on vlan51 using Service-Name ''
Dec 28 15:51:28 skyprox pppd[27766]: Plugin /usr/lib/pppd/2.4.5/rp-pppoe.so loaded.
 
рестарт биллинга спас, но позже один из пользователей не мог авторизоваться

 

Dec 28 19:18:20 skyprox pppoe-server[10884]: Session 20 created for client dc:0e:a1:e2:3e:dc (10.67.15.20) on vlan53 using Service-Name ''
Dec 28 19:18:20 skyprox pppd[10884]: Plugin /usr/lib/pppd/2.4.5/rp-pppoe.so loaded.
Dec 28 19:18:20 skyprox pppd[10884]: Plugin rp-pppoe.so loaded.
Dec 28 19:18:20 skyprox pppd[10884]: Plugin purestg2.so loaded.
Dec 28 19:18:20 skyprox pppd[10884]: Stargazer (purestg2 2.4) auth plugin initialized.
Dec 28 19:18:20 skyprox pppd[10884]: purestg2: Chap check is allowed.
Dec 28 19:18:20 skyprox pppd[10884]: pppd 2.4.5 started by root, uid 0
Dec 28 19:18:20 skyprox pppd[10884]: purestg2: Connected to stargazer via /var/run/purestg2.sock.
Dec 28 19:18:20 skyprox pppd[10884]: purestg2: ifunit set to 120.
Dec 28 19:18:20 skyprox pppd[10884]: Connected to dc:0e:a1:e2:3e:dc via interface vlan53
Dec 28 19:18:20 skyprox pppd[10884]: Using interface ppp120
Dec 28 19:18:20 skyprox pppd[10884]: Connect: ppp120 <--> vlan53
Dec 28 19:18:20 skyprox pppd[10884]: purestg2: Chap check is allowed.
Dec 28 19:18:20 skyprox pppd[10884]: purestg2: Chap check is allowed.
Dec 28 19:18:23 skyprox pppd[10884]: purestg2: CHAP started.
Dec 28 19:18:23 skyprox pppd[10884]: purestg2: Got passwd for user molot6.
Dec 28 19:18:23 skyprox pppd[10884]: peer from calling number DC:0E:A1:E2:3E:DC authorized
Dec 28 19:18:23 skyprox pppd[10884]: purestg2: IP choose started.
Dec 28 19:18:24 skyprox pppd[10884]: purestg2: Allowed address.
Dec 28 19:18:24 skyprox pppd[10884]: purestg2: Good address.
Dec 28 19:18:24 skyprox pppd[10884]: local  IP address 10.0.0.247
Dec 28 19:18:24 skyprox pppd[10884]: remote IP address 10.168.5.149
Dec 28 19:18:24 skyprox pppd[10884]: purestg2: Can't connect user molot6.
Dec 28 19:18:24 skyprox pppd[10884]: Exit.
 
спустя многих попыток получилось
 
место на жёстком диске есть
 
что это? новогодний переполох? всех с наступающим! =)
Edited by yKpon
KaYot Бог

KaYot

Posted
Posted

Вам же ясно сказали, conntrack table переполнен. Из-за этого прут потери пакетов и разваливается вся сетевая система.

Увеличьте размер таблицы.

yKpon Оборотень

yKpon

Posted
Posted (edited)

пол часа назад рухнуло опять

KaYot, спасибо, увеличил до 1548576, тестирую

 

вообще нормальная реакция stg была на переполнение?

Edited by yKpon
madf Дьявол

madf

Posted
Posted

Каким боком переполнение таблицы contrack имеет отношение к биллингу?

  • 4 weeks later...
yKpon Оборотень

yKpon

Posted
Posted (edited)

жалоба абонента, не может подключиться, ошибка 619, вижу пользователь статус онлайн, на самом деле нет, делаю рестарт биллинга и такое произошло с другой учёткой, сам пробую подключиться, и да действительно ошибка 619

 

syslog

 

Jan 21 09:51:36 skyprox pppd[25446]: Plugin /usr/lib/pppd/2.4.5/rp-pppoe.so loaded.

Jan 21 09:51:36 skyprox pppd[25446]: Plugin rp-pppoe.so loaded.

Jan 21 09:51:36 skyprox pppd[25446]: Plugin purestg2.so loaded.

Jan 21 09:51:36 skyprox pppd[25446]: Stargazer (purestg2 2.4) auth plugin initialized.

Jan 21 09:51:36 skyprox pppd[25446]: purestg2: Chap check is allowed.

Jan 21 09:51:36 skyprox pppd[25446]: pppd 2.4.5 started by root, uid 0

Jan 21 09:51:36 skyprox pppd[25446]: purestg2: Connected to stargazer via /var/run/purestg2.sock.

Jan 21 09:51:36 skyprox pppd[25446]: purestg2: ifunit set to 136.

Jan 21 09:51:36 skyprox pppd[25446]: Connected to ec:a8:6b:f5:7a:86 via interface red

Jan 21 09:51:36 skyprox pppd[25446]: Using interface ppp136

Jan 21 09:51:36 skyprox pppd[25446]: Connect: ppp136 red

Jan 21 09:51:36 skyprox pppd[25446]: purestg2: Chap check is allowed.

Jan 21 09:51:36 skyprox pppd[25446]: purestg2: Chap check is allowed.

Jan 21 09:51:36 skyprox pppd[25446]: purestg2: CHAP started.

Jan 21 09:51:36 skyprox pppd[25446]: purestg2: Got passwd for user razor.

Jan 21 09:51:36 skyprox pppd[25446]: peer from calling number EC:A8:6B:F5:7A:86 authorized

Jan 21 09:51:36 skyprox pppd[25446]: purestg2: IP choose started.

Jan 21 09:51:36 skyprox pppd[25446]: purestg2: Allowed address.

Jan 21 09:51:36 skyprox pppd[25446]: purestg2: Good address.

Jan 21 09:51:36 skyprox pppd[25446]: local IP address 10.0.0.249

Jan 21 09:51:36 skyprox pppd[25446]: remote IP address 10.168.2.5

Jan 21 09:51:36 skyprox pppd[25446]: purestg2: Can't connect user razor.

Jan 21 09:51:36 skyprox pppd[25446]: Exit.

 

stargazer.log

 

2014-01-21 09:48:11 -- purestg2: Accepted new client connection (socket=46)

2014-01-21 09:48:11 -- purestg2: BUG: can't find previous user socket for user "razor"

Edited by yKpon
Alexey Osipov Точу Зубы

Alexey Osipov

Posted
  • Author
Posted (edited)

2014-01-21 09:48:11 -- purestg2: BUG: can't find previous user socket for user "razor"

Да, фигня какая-то случилась. Сообщения с префиксом BUG по задумке если всё работает правильно не должны никогда выводиться. Буду посмотреть.

 

Можно ещё логи предыдущего подключения пользователя razor?

Edited by Alexey Osipov
yKpon Оборотень

yKpon

Posted
Posted (edited)
началось всё с пользователя medison
 
2014-01-21 08:25:11 -- purestg2: Terminating previous session (oldsocket=37) for user "medison"
2014-01-21 08:25:11 -- purestg2: User medison (socket=37) is connected.
2014-01-21 08:25:11 -- purestg2: ERROR: Can't send reply: Bad file descriptor
2014-01-21 08:25:11 -- purestg2: ERROR: can't handle client connection for socket 37
2014-01-21 08:25:32 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:25:38 -- purestg2: Accepted new client connection (socket=44)
2014-01-21 08:25:41 -- purestg2: User molot6 (socket=44) is connected.
2014-01-21 08:25:47 -- purestg2: Terminating previous session (oldsocket=37) for user "medison"
2014-01-21 08:25:47 -- purestg2: User medison (socket=37) is connected.
2014-01-21 08:25:47 -- purestg2: ERROR: Can't send reply: Bad file descriptor
2014-01-21 08:25:47 -- purestg2: ERROR: can't handle client connection for socket 37
2014-01-21 08:25:57 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:26:00 -- purestg2: Terminating previous session (oldsocket=37) for user "medison"
2014-01-21 08:26:00 -- purestg2: User medison (socket=37) is connected.
2014-01-21 08:26:00 -- purestg2: ERROR: Can't send reply: Bad file descriptor
2014-01-21 08:26:00 -- purestg2: ERROR: can't handle client connection for socket 37
2014-01-21 08:26:14 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:26:26 -- purestg2: Terminating previous session (oldsocket=37) for user "medison"
2014-01-21 08:26:26 -- purestg2: User medison (socket=37) is connected.
2014-01-21 08:26:26 -- purestg2: ERROR: Can't send reply: Bad file descriptor
2014-01-21 08:26:26 -- purestg2: ERROR: can't handle client connection for socket 37
2014-01-21 08:26:39 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:26:48 -- purestg2: Terminating previous session (oldsocket=37) for user "medison"
2014-01-21 08:26:48 -- purestg2: User medison (socket=37) is connected.
2014-01-21 08:26:48 -- purestg2: ERROR: Can't send reply: Bad file descriptor
2014-01-21 08:26:48 -- purestg2: ERROR: can't handle client connection for socket 37
2014-01-21 08:27:11 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:27:17 -- purestg2: Terminating previous session (oldsocket=37) for user "medison"
2014-01-21 08:27:17 -- purestg2: User medison (socket=37) is connected.
2014-01-21 08:27:17 -- purestg2: ERROR: Can't send reply: Bad file descriptor
2014-01-21 08:27:17 -- purestg2: ERROR: can't handle client connection for socket 37
2014-01-21 08:27:33 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:27:33 -- purestg2: User pilorama (socket=37) is connected.
2014-01-21 08:27:47 -- purestg2: Accepted new client connection (socket=48)
2014-01-21 08:27:50 -- purestg2: Terminating previous session (oldsocket=37) for user "medison"
2014-01-21 08:27:50 -- purestg2: User medison (socket=48) is connected.
2014-01-21 08:27:59 -- purestg2: Terminating previous session (oldsocket=48) for user "medison"
2014-01-21 08:27:59 -- purestg2: User medison (socket=48) is connected.
2014-01-21 08:27:59 -- purestg2: ERROR: Can't send reply: Bad file descriptor
2014-01-21 08:27:59 -- purestg2: ERROR: can't handle client connection for socket 48
2014-01-21 08:28:13 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:28:13 -- purestg2: Terminating previous session (oldsocket=37) for user "pilorama"
2014-01-21 08:28:13 -- purestg2: User pilorama (socket=37) is connected.
2014-01-21 08:28:13 -- purestg2: ERROR: Can't send reply: Bad file descriptor
2014-01-21 08:28:13 -- purestg2: ERROR: can't handle client connection for socket 37
2014-01-21 08:28:13 -- purestg2: ERROR: can't handle client connection for socket 37
2014-01-21 08:28:15 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:28:27 -- purestg2: Terminating previous session (oldsocket=48) for user "medison"
2014-01-21 08:28:27 -- purestg2: Can't find connection for socket 48
2014-01-21 08:28:27 -- purestg2: BUG: delConnection for socket 48 failed: -1
2014-01-21 08:28:27 -- purestg2: BUG: Can't find unit for socket 48
2014-01-21 08:28:27 -- purestg2: User medison (socket=37) is connected.
2014-01-21 08:28:44 -- purestg2: Accepted new client connection (socket=48)
2014-01-21 08:28:44 -- purestg2: Terminating previous session (oldsocket=37) for user "pilorama"
2014-01-21 08:28:44 -- purestg2: User pilorama (socket=48) is connected.
2014-01-21 08:29:46 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:29:49 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:30:04 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:30:13 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:30:36 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:30:48 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:31:01 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:31:07 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:31:21 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:31:27 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:31:43 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:31:46 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:32:06 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:32:09 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:32:34 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:32:46 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:33:11 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:33:20 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:33:41 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:33:53 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:34:13 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:34:24 -- purestg2: User molot25 (socket=43) is disconnected.
2014-01-21 08:34:28 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:34:48 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:35:00 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:35:03 -- purestg2: Accepted new client connection (socket=37)
2014-01-21 08:35:03 -- purestg2: User tarasss (socket=37) is connected.
2014-01-21 08:35:30 -- purestg2: Accepted new client connection (socket=43)
2014-01-21 08:35:39 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:35:50 -- purestg2: Accepted new client connection (socket=43)
2014-01-21 08:35:53 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:36:13 -- purestg2: Accepted new client connection (socket=43)
2014-01-21 08:36:25 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:36:44 -- purestg2: Accepted new client connection (socket=43)
2014-01-21 08:36:50 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:37:06 -- purestg2: Accepted new client connection (socket=43)
2014-01-21 08:37:24 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:37:43 -- purestg2: Accepted new client connection (socket=43)
2014-01-21 08:37:46 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:37:56 -- purestg2: Accepted new client connection (socket=43)
2014-01-21 08:38:02 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:38:21 -- purestg2: Accepted new client connection (socket=43)
2014-01-21 08:38:27 -- purestg2: BUG: can't find previous user socket for user "medison"
2014-01-21 08:38:43 -- purestg2: Accepted new client connection (socket=43)

 

с трудом получилось пустить всех пользователей, убивал все pppd, убивал все pppoe-server, рестартил биллинг и запускал pppoe сервера

абонентская база растёт, боюсь баг снова всплывёт

Edited by yKpon
Alexey Osipov Точу Зубы

Alexey Osipov

Posted
  • Author
Posted

Памятка для себя: сначала обрабатывать POLLIN сокеты (кроме listening), затем POLLHUP, и только затем POLLIN listening сокет.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...