Как продиагностировать UTM?

Настройка сетевых служб, маршрутизации, фаерволлов. Проблемы с сетевым оборудованием.
Правила форума
Убедительная просьба юзать теги [code] при оформлении листингов.
Сообщения не оформленные должным образом имеют все шансы быть незамеченными.
Аватара пользователя
paran0id
мл. сержант
Сообщения: 128
Зарегистрирован: 2011-11-22 14:03:08
Откуда: мск

Как продиагностировать UTM?

Непрочитанное сообщение paran0id » 2012-06-27 16:03:34

Есть криво перенесенная с одного компа на другой система биллинга UTM5.

utm_core работает, клиент к нему подключается, старую статистику видит, новая, по всей видимости, не собирается.

в /netup/utm5/db/ новые файлы вида iptraffic_raw_1338931652.utm не появляются.

В main.log за сегодня следующее:

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

[root@GATE2 /netup/utm5/log]# cat main.log | grep "Jun 27"
 Notice: Jun 27 15:37:08 ModMap: Log file reopened
 Notice: Jun 27 15:37:08 NFBuffer: Worker thread terminated...
 Info  : Jun 27 15:37:08 BusClassif: Periodic clean thread stopped.
 Notice: Jun 27 15:37:09 ModMap: Cleaning modules, <12> modules registered.
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'busmod' trying to erase...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'busmod' erased...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'config' trying to erase...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'config' erased...
 Notice: Jun 27 15:37:09 UTM5 Config: Pid file found: /var/run/utm5_core.pid; Overwriting
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'dba' trying to erase...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'dba' erased...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'dba:ctx' trying to erase...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'dba:ctx' erased...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'dba:giga' trying to erase...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'dba:giga' erased...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'dba:radius' trying to erase...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'dba:radius' erased...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'logger' trying to erase...
 Notice: Jun 27 15:37:09 ModMap: Skipping 'logger' module...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'nfbuffer' trying to erase...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'nfbuffer' erased...
 Notice: Jun 27 15:37:09 ModMap: Skipping 'nfbuffer'  module...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'radius' trying to erase...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'radius' erased...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'radius' erased...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'nfbuffer' trying to erase...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'nfbuffer' erased...
 Notice: Jun 27 15:37:09 ModMap: Skipping 'nfbuffer'  module...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'rehash' trying to erase...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'rehash' erased...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'rpc@0.0.0.0' trying to erase...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'rpc@0.0.0.0' erased...
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'stream-manager' trying to erase...
 Info  : Jun 27 15:37:09 StreamConnection: Connection from 127.0.0.1:29242 closed
 Notice: Jun 27 15:37:09 ModMap: Sub-Module 'stream-manager' erased...
 Info  : Jun 27 15:37:09 Core: System is down
 Info  : Jun 27 15:37:17 UTM5 Logger: New ` Info  : ' stream: /netup/utm5/log/main.log
 Info  : Jun 27 15:37:17 UTM5 Logger: New `*CRIT  : ' stream: /netup/utm5/log/main.log
 Info  : Jun 27 15:37:17 DBA:Ctx: Creating 8 user DB connections
 Info  : Jun 27 15:37:17 DBA:Ctx: Creating 4 system DB connections
 Notice: Jun 27 15:37:17 ModMap: Sub-Module 'dba:ctx' inserted...
 Info  : Jun 27 15:37:17 UTM5 Core: New traffic classification mechanism enabled
 Notice: Jun 27 15:37:17 UTM5 DBA: Summary sys users fetched: 3
 Notice: Jun 27 15:37:17 UTM5 DBA: Summary sys users fetched: 3
 Notice: Jun 27 15:37:17 UTM5 DBA: Summary discount periods fetched:2
 Notice: Jun 27 15:37:17 UTM5 DBA: Summary users fetched: 256
 Info  : Jun 27 15:37:17 UTM5 DBA: parsed 1.000000 notification border
 Info  : Jun 27 15:37:17 UTM5 DBA: block_recalc_abon = 0
 Info  : Jun 27 15:37:17 UTM5 DBA: block_recalc_prepaid = 0
 Info  : Jun 27 15:37:17 UTM5 DBA: default_vat_rate = 0.000000
 Info  : Jun 27 15:37:17 UTM5 DBA: fw_rule_offset = 5000
 Info  : Jun 27 15:37:17 UTM5 DBA: login_prefix_separator = :
 Info  : Jun 27 15:37:17 UTM5 DBA: null_prepaid_traffic_if_tarif_change = 0
 Info  : Jun 27 15:37:17 UTM5 DBA: www_prefix </var/www/>
 Info  : Jun 27 15:37:17 UTM5 DBA: hosting_ip <127.0.0.1>
 Info  : Jun 27 15:37:17 UTM5 DBA: hosting_uid_number <10001>
 Info  : Jun 27 15:37:17 UTM5 DBA: hosting_gid_number <10001>
 Info  : Jun 27 15:37:17 UTM5 DBA: mail_server_ip <127.0.0.1>
 Info  : Jun 27 15:37:17 UTM5 DBA: force_prepaid_change <0>
 Info  : Jun 27 15:37:17 UTM5 DBA: email_exec_register <>
 Info  : Jun 27 15:37:17 UTM5 DBA: email_exec_unregister <>
 Info  : Jun 27 15:37:17 UTM5 DBA: tel_attrs_write <0>
 Info  : Jun 27 15:37:17 UTM5 DBA: dialup_attrs_write <0>
 Info  : Jun 27 15:37:17 UTM5 DBA: access_attrs_write <0>
 Info  : Jun 27 15:37:17 UTM5 DBA: access_log_write <0>
 Notice: Jun 27 15:37:17 ModMap: Sub-Module 'dba' inserted...
 Notice: Jun 27 15:37:17 ModMap: Sub-Module 'dba:giga' inserted...
 Info  : Jun 27 15:37:17 BusClassif: Created...
 Info  : Jun 27 15:37:17 BusLogic: Worker thread started.
 Info  : Jun 27 15:37:17 BusClassif: Periodic cleanup thread started.
 Info  : Jun 27 15:37:17 BusClassif: NF5 processor thread started
 Notice: Jun 27 15:37:17 ModMap: Sub-Module 'nfbuffer' inserted...
 Info  : Jun 27 15:37:17 BusPeriodic: BusPeriodic thread started.
 Notice: Jun 27 15:37:17 ModMap: Sub-Module 'busmod' inserted...
 Notice: Jun 27 15:37:17 ModMap: Sub-Module 'rpc@0.0.0.0' inserted...
 Info  : Jun 27 15:37:17 RPCServer@0.0.0.0: [URFA: 2.3]: Ready to accept connections on 0.0.0.0:11758
 Notice: Jun 27 15:37:17 ModMap: Sub-Module 'stream-manager' inserted...
 Info  : Jun 27 15:37:17 StreamManager: Registering message handlers..
 Info  : Jun 27 15:37:17 StreamManager: ID <0x3000> handler <0x28cf8a20>
 Info  : Jun 27 15:37:17 StreamManager: ID <0x3001> handler <0x28cf8a20>
 Info  : Jun 27 15:37:17 SecureSocketImpl: Listening on 0.0.0.0:11777
 Info  : Jun 27 15:37:17 RPCFMan: Loading RPC Functions from /netup/utm5/lib/utm5_core/liburfa-utils.so
 Info  : Jun 27 15:37:17 RPCFMan: Loading RPC Functions from /netup/utm5/lib/utm5_core/liburfa-std.so
 Info  : Jun 27 15:37:17 RPCFMan: Loading RPC Functions from /netup/utm5/lib/utm5_core/liburfa-reports.so
 Info  : Jun 27 15:37:17 RPCFMan: Loading RPC Functions from /netup/utm5/lib/utm5_core/liburfa-card.so
 Info  : Jun 27 15:37:18 RPCFMan: Loading RPC Functions from /netup/utm5/lib/utm5_core/liburfa-graph.so
 Info  : Jun 27 15:37:18 RPCFMan: Loading RPC Functions from /netup/utm5/lib/utm5_radius/liburfa-radius.so
 Notice: Jun 27 15:37:18 ModMap: Sub-Module 'dba:radius' inserted...
 Notice: Jun 27 15:37:18 Radius: Plugin registered.
 Notice: Jun 27 15:37:18 ModMap: Sub-Module 'radius' inserted...
 Info  : Jun 27 15:37:18 StreamManager: Registering message handlers..
 Info  : Jun 27 15:37:18 StreamManager: ID <0x1000> handler <0x28f50a5c>
 Info  : Jun 27 15:37:18 StreamManager: ID <0x1001> handler <0x28f50a5c>
 Info  : Jun 27 15:37:18 StreamManager: ID <0x1002> handler <0x28f50a5c>
 Info  : Jun 27 15:37:18 StreamManager: ID <0x1003> handler <0x28f50a5c>
 Info  : Jun 27 15:37:18 StreamManager: ID <0x1004> handler <0x28f50a5c>
 Info  : Jun 27 15:37:18 StreamManager: ID <0x1005> handler <0x28f50a5c>
 Info  : Jun 27 15:37:18 StreamManager: ID <0x1006> handler <0x28f50a5c>
 Info  : Jun 27 15:37:18 StreamManager: ID <0x1007> handler <0x28f50a5c>
 Info  : Jun 27 15:37:18 StreamManager: ID <0x1008> handler <0x28f50a5c>
 Info  : Jun 27 15:37:18 StreamManager: ID <0x1009> handler <0x28f50a5c>
 Info  : Jun 27 15:37:18 StreamManager: ID <0x100a> handler <0x28f50a5c>
 Info  : Jun 27 15:37:18 NFBuffer: Socket attached to 94.159.64.50:9996
 Info  : Jun 27 15:37:19 StreamConnection: Connection thread started. Peer 127.0.0.1:36235
 Info  : Jun 27 15:37:19 StreamConnection: Authorized user <radius> from <127.0.0.1>
Вопрос: как локализовать проблему?
Хватит, хватит, $%@^ая рогатая тварь, остановись!

Хостинговая компания 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/

Аватара пользователя
tynix
сержант
Сообщения: 246
Зарегистрирован: 2008-08-06 8:25:42
Откуда: Красноярск

Re: Как продиагностировать UTM?

Непрочитанное сообщение tynix » 2012-07-10 14:17:43

Повысить log_level в utm5.cfg.
Конфиг выложи.
Проверь, идет ли статистика на utm.
Don' t panic !
cd /usr/ports && make srach
make: don't know how to make srach. Stop