Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support (Russian)
  3. Ошибка SNMPTrapReceiver

Ошибка SNMPTrapReceiver

Scheduled Pinned Locked Moved Support (Russian)
3 Posts 1 Posters 12.7k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L
    L
    LMM
    wrote on last edited by
    #1

    Здравствуйте!

    Столкнулся с такой проблемой, где-то с ноября 2016 в логах сервера появилась следующая ошибка:

    [24-Nov-2016 18:56:54.375] [ERROR] Unable to bind socket to port 162 in function SNMPTrapReceiver: ??? ??? ??? ??? ??? ?? ??? ??? ??? ? ??? ??? ??? ??? ? ??? ??? ??? ??? ( ??? ??? ??/? ??? ??? ??? ??/? ??? ).
    

     
    К сожалению в предновогодней суете не было возможности рассмотреть данную проблему более детально... и все это вылилось в то, что новые устройства (пк/сервера и т.д.) не сканируются сервером NetXMS. Новодобавленный Datacollection не собирается и выдает ошибку...
    НО при этом, уже настроенные соборы данных - собираются нормально, DashBord (старые - не новые) - тоже работают. E-mail и sms рассылаются в случае срабатывания event-ov

    На сервере и в сети ничего не менялось/не добавлялось... полный лог на текущую дату - ниже:

    [31-Jan-2017 18:13:26.453] Log file opened
    [31-Jan-2017 18:13:26.890] [INFO ] Database driver "mysql.ddr" loaded and initialized successfully
    [31-Jan-2017 18:13:28.171] [INFO ] Stalled database lock removed
    [31-Jan-2017 18:13:37.328] [INFO ] Network device driver "AIRESPACE" loaded successfully
    [31-Jan-2017 18:13:37.343] [INFO ] Network device driver "AT" loaded successfully
    [31-Jan-2017 18:13:37.406] [INFO ] Network device driver "BAYSTACK" loaded successfully
    [31-Jan-2017 18:13:37.500] [INFO ] Network device driver "CATALYST-2900XL" loaded successfully
    [31-Jan-2017 18:13:37.531] [INFO ] Network device driver "CATALYST-GENERIC" loaded successfully
    [31-Jan-2017 18:13:37.578] [INFO ] Network device driver "CISCO-ESW" loaded successfully
    [31-Jan-2017 18:13:37.593] [INFO ] Network device driver "CISCO-SB" loaded successfully
    [31-Jan-2017 18:13:37.625] [INFO ] Network device driver "DELL-PWC" loaded successfully
    [31-Jan-2017 18:13:37.640] [INFO ] Network device driver "DLINK" loaded successfully
    [31-Jan-2017 18:13:37.671] [INFO ] Network device driver "ERS8000" loaded successfully
    [31-Jan-2017 18:13:37.687] [INFO ] Network device driver "H3C" loaded successfully
    [31-Jan-2017 18:13:37.718] [INFO ] Network device driver "HPSW" loaded successfully
    [31-Jan-2017 18:13:37.718] [INFO ] Network device driver "MIKROTIK" loaded successfully
    [31-Jan-2017 18:13:37.718] [INFO ] Network device driver "NETSCREEN" loaded successfully
    [31-Jan-2017 18:13:37.734] [INFO ] Network device driver "NTWS" loaded successfully
    [31-Jan-2017 18:13:37.765] [INFO ] Network device driver "PING3" loaded successfully
    [31-Jan-2017 18:13:37.765] [INFO ] Network device driver "PROCURVE" loaded successfully
    [31-Jan-2017 18:13:37.796] [INFO ] Network device driver "QTECH-OLT" loaded successfully
    [31-Jan-2017 18:13:37.812] [INFO ] Network device driver "SYMBOL-WS" loaded successfully
    [31-Jan-2017 18:13:37.859] [INFO ] Network device driver "TB" loaded successfully
    [31-Jan-2017 18:13:37.859] [INFO ] Network device driver "UBNT" loaded successfully
    [31-Jan-2017 18:13:59.968] [ERROR] Unable to bind socket to port 162 in function SNMPTrapReceiver: ??? ??? ??? ??? ??? ?? ??? ??? ??? ? ??? ??? ??? ??? ? ??? ??? ??? ??? ( ??? ??? ??/? ??? ??? ??? ??/? ??? ).
    [31-Jan-2017 18:13:59.968] [ERROR] Unable to bind socket to port 162 in function SNMPTrapReceiver: ??? ??? ??? ??? ??? ?? ??? ??? ??? ? ??? ??? ??? ??? ? ??? ??? ??? ??? ( ??? ??? ??/? ??? ??? ??? ??/? ??? ).
    [31-Jan-2017 18:13:59.968] [INFO ] Listening for syslog messages on UDP socket 0.0.0.0:514
    [31-Jan-2017 18:13:59.968] [INFO ] Listening for syslog messages on UDP socket [::]:514
    [31-Jan-2017 18:13:59.984] [INFO ] NetXMS Server started
    [31-Jan-2017 18:14:00.000] [INFO ] Listening for client connections on TCP socket 0.0.0.0:4701
    [31-Jan-2017 18:14:00.000] [INFO ] Listening for client connections on TCP socket [::]:4701
    [31-Jan-2017 18:14:00.000] [INFO ] Listening for mobile device connections on TCP socket 0.0.0.0:4747
    [31-Jan-2017 18:14:00.000] [INFO ] Listening for mobile device connections on TCP socket [::]:4747
    

    Поиск по форуму ничего похожего на мою проблему не дал.
    Есть у кого-нибудь идеи, куда копать?

    P.S. Сервер поднят на Hyper-v 2012 - никаких проблем до ноября замечено не было - все работало в штатном режиме... а тут...:(
    P.P.S.S. Так же попробовал обновить сервер с версии 2.0.3 до 2.0.8 (вроде как последняя стабильная) - никакого эффекта....

    1 Reply Last reply
    0
    • L
      L
      LMM
      wrote on last edited by
      #2

      Выключил службу "Ловушка SNMP", перезапустил NetXMS Core, в логе увидел:

      [01-Feb-2017 13:15:39.137] Log file opened
      [01-Feb-2017 13:15:39.137] [INFO ] Database driver "mysql.ddr" loaded and initialized successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "AIRESPACE" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "AT" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "BAYSTACK" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "CATALYST-2900XL" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "CATALYST-GENERIC" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "CISCO-ESW" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "CISCO-SB" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "DELL-PWC" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "DLINK" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "ERS8000" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "H3C" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "HPSW" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "MIKROTIK" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "NETSCREEN" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "NTWS" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "PING3" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "PROCURVE" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "QTECH-OLT" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "SYMBOL-WS" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "TB" loaded successfully
      [01-Feb-2017 13:15:44.372] [INFO ] Network device driver "UBNT" loaded successfully
      [01-Feb-2017 13:15:55.516] [INFO ] Listening for SNMP traps on UDP socket 0.0.0.0:162
      [01-Feb-2017 13:15:55.516] [INFO ] Listening for SNMP traps on UDP socket [::]:162
      [01-Feb-2017 13:15:55.516] [INFO ] Listening for syslog messages on UDP socket 0.0.0.0:514
      [01-Feb-2017 13:15:55.516] [INFO ] Listening for syslog messages on UDP socket [::]:514
      [01-Feb-2017 13:15:55.516] [INFO ] Listening for client connections on TCP socket 0.0.0.0:4701
      [01-Feb-2017 13:15:55.516] [INFO ] Listening for client connections on TCP socket [::]:4701
      [01-Feb-2017 13:15:55.516] [INFO ] Listening for mobile device connections on TCP socket 0.0.0.0:4747
      [01-Feb-2017 13:15:55.516] [INFO ] Listening for mobile device connections on TCP socket [::]:4747
      [01-Feb-2017 13:15:55.516] [INFO ] NetXMS Server started
      

      Для эксперимента грохнул подсеть, что бы он пересканировал её заново, но ничего... 😞

      1 Reply Last reply
      0
      • L
        L
        LMM
        wrote on last edited by
        #3

        Решилось.

        Вопрос можно закрывать.

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups