Как заставить mpd5 переподключаться?

Проблемы установки, настройки и работы Правильной Операционной Системы

Модератор: terminus

Правила форума
Убедительная просьба юзать теги [cоde] при оформлении листингов.
Сообщения не оформленные должным образом имеют все шансы быть незамеченными.
penkov-mm
проходил мимо
Сообщения: 2
Зарегистрирован: 2009-04-24 14:25:59

Как заставить mpd5 переподключаться?

Непрочитанное сообщение penkov-mm » 2009-04-24 14:35:22

На FreeBSD 7.1 Release установлена из портов и сконфигурирована программа mpd 5.3. Конфигурация:

Код: Выделить всё

startup: 
    set user root air-admin
    set console self 127.0.0.1 5005
    set console open
    set web self 127.0.0.1 5006
    set web open
default:
    load pppoe_client
pppoe_client: 
    create bundle static B1
    set iface route default
    set iface enable nat
    set ipcp ranges 0.0.0.0/0 0.0.0.0/0
    create link static L1 pppoe
    set link action bundle B1
    set auth authname penkov-mm
    set auth password ********
    set link max-redial 0
    set link keep-alive 10 60
    set link mtu 1492
    set link mru 1492
    set pppoe iface sk0
    set pppoe service "Trinity"
    open
и лог:

Код: Выделить всё

Apr 19 13:01:50 penkov-mm mpd: Multi-link PPP daemon for FreeBSD
Apr 19 13:01:50 penkov-mm mpd:  
Apr 19 13:01:50 penkov-mm mpd: process 637 started, version 5.3 (root@penkov-mm.homeip.net 22:13 17-Apr-2009)
Apr 19 13:01:51 penkov-mm mpd: CONSOLE: listening on 127.0.0.1 5005
Apr 19 13:01:51 penkov-mm mpd: web: listening on 127.0.0.1 5006
Apr 19 13:01:51 penkov-mm mpd: [B1] Bundle: Interface ng0 created
Apr 19 13:01:51 penkov-mm mpd: [L1] Link: OPEN event
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: Open event
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: state change Initial --> Starting
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: LayerStart
Apr 19 13:01:51 penkov-mm mpd: [L1] PPPoE: Connecting to 'Trinity'
Apr 19 13:01:51 penkov-mm mpd: PPPoE: rec'd ACNAME "mercury.azovline.net.ua"
Apr 19 13:01:51 penkov-mm mpd: [L1] PPPoE: connection successful
Apr 19 13:01:51 penkov-mm mpd: [L1] Link: UP event
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: Up event
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: state change Starting --> Req-Sent
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: SendConfigReq #1
Apr 19 13:01:51 penkov-mm mpd: [L1]   PROTOCOMP
Apr 19 13:01:51 penkov-mm mpd: [L1]   MRU 1492
Apr 19 13:01:51 penkov-mm mpd: [L1]   MAGICNUM d6baccee
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: rec'd Configure Request #1 (Req-Sent)
Apr 19 13:01:51 penkov-mm mpd: [L1]   MRU 1492
Apr 19 13:01:51 penkov-mm mpd: [L1]   MAGICNUM 4ab223aa
Apr 19 13:01:51 penkov-mm mpd: [L1]   AUTHPROTO CHAP MSOFTv2
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: SendConfigAck #1
Apr 19 13:01:51 penkov-mm mpd: [L1]   MRU 1492
Apr 19 13:01:51 penkov-mm mpd: [L1]   MAGICNUM 4ab223aa
Apr 19 13:01:51 penkov-mm mpd: [L1]   AUTHPROTO CHAP MSOFTv2
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: state change Req-Sent --> Ack-Sent
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: rec'd Configure Ack #1 (Ack-Sent)
Apr 19 13:01:51 penkov-mm mpd: [L1]   PROTOCOMP
Apr 19 13:01:51 penkov-mm mpd: [L1]   MRU 1492
Apr 19 13:01:51 penkov-mm mpd: [L1]   MAGICNUM d6baccee
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: state change Ack-Sent --> Opened
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: auth: peer wants CHAP, I want nothing
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: LayerUp
Apr 19 13:01:51 penkov-mm mpd: [L1] CHAP: rec'd CHALLENGE #1 len: 21
Apr 19 13:01:51 penkov-mm mpd: [L1]   Name: ""
Apr 19 13:01:51 penkov-mm mpd: [L1] CHAP: Using authname "penkov-mm"
Apr 19 13:01:51 penkov-mm mpd: [L1] CHAP: sending RESPONSE #1 len: 63
Apr 19 13:01:51 penkov-mm mpd: [L1] CHAP: rec'd SUCCESS #1 len: 46
Apr 19 13:01:51 penkov-mm mpd: [L1]   MESG: S=33D8E904CAC02445D9EE977F75B7C751475402ED
Apr 19 13:01:51 penkov-mm mpd: [L1] LCP: authorization successful
Apr 19 13:01:51 penkov-mm mpd: [L1] Link: Matched action 'bundle "B1" ""'
Apr 19 13:01:51 penkov-mm mpd: [L1] Link: Join bundle "B1"
Apr 19 13:01:51 penkov-mm mpd: [B1] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: Open event
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: state change Initial --> Starting
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: LayerStart
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: Up event
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: state change Starting --> Req-Sent
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: SendConfigReq #1
Apr 19 13:01:51 penkov-mm mpd: [B1]   IPADDR 0.0.0.0
Apr 19 13:01:51 penkov-mm mpd: [B1]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: rec'd Configure Request #1 (Req-Sent)
Apr 19 13:01:51 penkov-mm mpd: [B1]   IPADDR 193.46.210.5
Apr 19 13:01:51 penkov-mm mpd: [B1]     193.46.210.5 is OK
Apr 19 13:01:51 penkov-mm mpd: [B1]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: SendConfigAck #1
Apr 19 13:01:51 penkov-mm mpd: [B1]   IPADDR 193.46.210.5
Apr 19 13:01:51 penkov-mm mpd: [B1]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: state change Req-Sent --> Ack-Sent
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: rec'd Configure Nak #1 (Ack-Sent)
Apr 19 13:01:51 penkov-mm mpd: [B1]   IPADDR 217.67.64.50
Apr 19 13:01:51 penkov-mm mpd: [B1]     217.67.64.50 is OK
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: SendConfigReq #2
Apr 19 13:01:51 penkov-mm mpd: [B1]   IPADDR 217.67.64.50
Apr 19 13:01:51 penkov-mm mpd: [B1]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: rec'd Configure Ack #2 (Ack-Sent)
Apr 19 13:01:51 penkov-mm mpd: [B1]   IPADDR 217.67.64.50
Apr 19 13:01:51 penkov-mm mpd: [B1]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: state change Ack-Sent --> Opened
Apr 19 13:01:51 penkov-mm mpd: [B1] IPCP: LayerUp
Apr 19 13:01:51 penkov-mm mpd: [B1]   217.67.64.50 -> 193.46.210.5
Apr 19 13:01:51 penkov-mm mpd: [B1] IFACE: Up event
Apr 20 00:20:09 penkov-mm mpd: [B1] IPCP: rec'd IPCP: rec'd Terminate Request #2 (Opened)
Apr 20 00:20:09 penkov-mm mpd: [B1] IPCP: state change Opened --> Stopping
Apr 20 00:20:09 penkov-mm mpd: [B1] IPCP: SendTerminateAck #3
Apr 20 00:20:09 penkov-mm mpd: [B1] IPCP: LayerDown
Apr 20 00:20:09 penkov-mm mpd: [B1] IFACE: Down event
Apr 20 00:20:11 penkov-mm mpd: [B1] IPCP: rec'd Terminate Request #3 (Stopping)
Apr 20 00:20:11 penkov-mm mpd: [B1] IPCP: SendTerminateAck #4
Apr 20 00:20:11 penkov-mm mpd: [B1] IPCP: state change Stopping --> Stopped
Apr 20 00:20:11 penkov-mm mpd: [B1] IPCP: LayerFinish
Apr 20 00:20:11 penkov-mm mpd: [B1] Bundle: No NCPs left. Closing links...
Apr 20 00:20:11 penkov-mm mpd: [B1] Bundle: closing link "L1"...
Apr 20 00:20:11 penkov-mm mpd: [L1] Link: CLOSE event
Apr 20 00:20:11 penkov-mm mpd: [L1] LCP: Close event
Apr 20 00:20:11 penkov-mm mpd: [L1] LCP: state change Opened --> Closing
Apr 20 00:20:11 penkov-mm mpd: [L1] Link: Leave bundle "B1"
Apr 20 00:20:11 penkov-mm mpd: [B1] Bundle: Status update: up 0 links, total bandwidth 9600 bps
Apr 20 00:20:11 penkov-mm mpd: [B1] IPCP: Close event
Apr 20 00:20:11 penkov-mm mpd: [B1] IPCP: state change Stopped --> Closed
Apr 20 00:20:11 penkov-mm mpd: [B1] IPCP: Down event
Apr 20 00:20:11 penkov-mm mpd: [B1] IPCP: state change Closed --> Initial
Apr 20 00:20:11 penkov-mm mpd: [L1] LCP: SendTerminateReq #2
Apr 20 00:20:11 penkov-mm mpd: [L1] LCP: LayerDown
Apr 20 00:20:11 penkov-mm mpd: [L1] LCP: rec'd Terminate Request #2 (Closing)
Apr 20 00:20:11 penkov-mm mpd: [L1] LCP: SendTerminateAck #3
Apr 20 00:20:11 penkov-mm mpd: [L1] LCP: rec'd Terminate Ack #3 (Closing)
Apr 20 00:20:11 penkov-mm mpd: [L1] LCP: state change Closing --> Closed
Apr 20 00:20:11 penkov-mm mpd: [L1] LCP: LayerFinish
Apr 20 00:20:11 penkov-mm mpd: [L1] Link: DOWN event
Apr 20 00:20:11 penkov-mm mpd: [L1] LCP: Down event
Apr 20 00:20:11 penkov-mm mpd: [L1] LCP: state change Closed --> Initial
То есть после такого падения приходится на сервере давать команду "killall mpd5; mpd5 -b". Вопрос - как заставить mpd5 автоматически самостоятельно переподключаться после такого падения соединения, как в логе? option noretry из пятёрки исключена, погуглив, выяснил, что четвёртая версия работает как должна, но как заставить пятую?.. Документацию читал.

Хостинговая компания Host-Food.ru
Хостинг HostFood.ru
 

Услуги хостинговой компании Host-Food.ru

Хостинг HostFood.ru

Тарифы на хостинг в России, от 12 рублей: https://www.host-food.ru/tariffs/hosting/
Тарифы на виртуальные сервера (VPS/VDS/KVM) в РФ, от 189 руб.: https://www.host-food.ru/tariffs/virtualny-server-vps/
Выделенные сервера, Россия, Москва, от 2000 рублей (HP Proliant G5, Intel Xeon E5430 (2.66GHz, Quad-Core, 12Mb), 8Gb RAM, 2x300Gb SAS HDD, P400i, 512Mb, BBU):
https://www.host-food.ru/tariffs/vydelennyi-server-ds/
Недорогие домены в популярных зонах: https://www.host-food.ru/domains/

Аватара пользователя
schizoid
подполковник
Сообщения: 3228
Зарегистрирован: 2007-03-03 17:32:31
Откуда: Украина, Чернигов
Контактная информация:

Re: Как заставить mpd5 переподключаться?

Непрочитанное сообщение schizoid » 2009-04-24 14:39:52

в 4-м так

Код: Выделить всё

set bundle disable noretry
set link max-redial 0
ядерный взрыв...смертельно красиво...жаль, что не вечно...

penkov-mm
проходил мимо
Сообщения: 2
Зарегистрирован: 2009-04-24 14:25:59

Re: Как заставить mpd5 переподключаться?

Непрочитанное сообщение penkov-mm » 2009-04-24 15:13:04

В четвёртом знаю что так. А как в пятом?