SMS channel, Cannot get driver names

Started by hayarm, September 20, 2019, 11:59:15 AM

Previous topic - Next topic

hayarm

после обновления не работает отправка смс,  при попытке добавления канала выдает вот такая ошибка "Cannot get driver names" и служба netxmsd останавливается

если возможно дайте документацию или описание параметров по настройки notification channels
Спасибо

Victor Kirhenshtein

На какой ОС установлен сервер? Версия сервера 3.0.2287?  Если Windows, пришлите пожалуйста минидамп после падения если он есть.

hayarm

сервер windows 2012 R2, Netxms: Version 3.0.2284


2019.09.20 12:53:59.879 Log file opened (rotation policy 2, max size 16777216)
2019.09.20 12:53:59.882 *I* [db.driver          ] Database driver "mysql.ddr" loaded and initialized successfully
2019.09.20 12:53:59.902 *I* [                   ] Server ID 2D55C43E000019B5
2019.09.20 12:53:59.956 *I* [                   ] Stalled database lock removed
2019.09.20 12:54:00.021 *I* [                   ] Server certificate not set
2019.09.20 12:54:00.287 *I* [db.driver          ] Database driver "sqlite.ddr" loaded and initialized successfully
2019.09.20 12:54:02.212 *I* [db.driver          ] Database driver "sqlite.ddr" loaded and initialized successfully
2019.09.20 12:54:02.626 *I* [                   ] Network device driver AIRESPACE loaded successfully
2019.09.20 12:54:02.626 *I* [                   ] Network device driver AT loaded successfully
2019.09.20 12:54:02.626 *I* [                   ] Network device driver BAYSTACK loaded successfully
2019.09.20 12:54:02.626 *I* [                   ] Network device driver NTWS loaded successfully
2019.09.20 12:54:02.626 *I* [                   ] Network device driver ERS8000 loaded successfully
2019.09.20 12:54:02.626 *I* [                   ] Network device driver CATALYST-GENERIC loaded successfully
2019.09.20 12:54:02.626 *I* [                   ] Network device driver CATALYST-2900XL loaded successfully
2019.09.20 12:54:02.626 *I* [                   ] Network device driver CISCO-ESW loaded successfully
2019.09.20 12:54:02.626 *I* [                   ] Network device driver CISCO-NEXUS loaded successfully
2019.09.20 12:54:02.626 *I* [                   ] Network device driver CISCO-SB loaded successfully
2019.09.20 12:54:02.626 *I* [                   ] Network device driver CISCO-GENERIC loaded successfully
2019.09.20 12:54:02.626 *I* [                   ] Network device driver DELL-PWC loaded successfully
2019.09.20 12:54:02.627 *I* [                   ] Network device driver DLINK loaded successfully
2019.09.20 12:54:02.627 *I* [                   ] Network device driver EXTREME loaded successfully
2019.09.20 12:54:02.627 *I* [                   ] Network device driver H3C loaded successfully
2019.09.20 12:54:02.627 *I* [                   ] Network device driver HPSW loaded successfully
2019.09.20 12:54:02.627 *I* [                   ] Network device driver PROCURVE loaded successfully
2019.09.20 12:54:02.627 *I* [                   ] Network device driver OPTIX loaded successfully
2019.09.20 12:54:02.627 *I* [                   ] Network device driver IGNITENET loaded successfully
2019.09.20 12:54:02.627 *I* [                   ] Network device driver JUNIPER loaded successfully
2019.09.20 12:54:02.627 *I* [                   ] Network device driver NETSCREEN loaded successfully
2019.09.20 12:54:02.628 *I* [                   ] Network device driver MIKROTIK loaded successfully
2019.09.20 12:54:02.628 *I* [                   ] Network device driver NET-SNMP loaded successfully
2019.09.20 12:54:02.628 *I* [                   ] Network device driver NETONIX loaded successfully
2019.09.20 12:54:02.628 *I* [                   ] Network device driver PING3 loaded successfully
2019.09.20 12:54:02.628 *I* [                   ] Network device driver QTECH-OLT loaded successfully
2019.09.20 12:54:02.628 *I* [                   ] Network device driver RITTAL loaded successfully
2019.09.20 12:54:02.628 *I* [                   ] Network device driver SYMBOL-WS loaded successfully
2019.09.20 12:54:02.629 *I* [                   ] Network device driver TB loaded successfully
2019.09.20 12:54:02.629 *I* [                   ] Network device driver UBNT loaded successfully
2019.09.20 12:54:02.629 *I* [db.driver          ] Database driver "sqlite.ddr" loaded and initialized successfully
2019.09.20 12:54:08.947 *I* [                   ] NetXMS Server started
2019.09.20 12:54:08.947 *I* [                   ] SocketListener/AgentTunnels: listening on 0.0.0.0:4703
2019.09.20 12:54:08.948 *I* [                   ] SocketListener/Clients: listening on 0.0.0.0:4701
2019.09.20 12:54:08.948 *I* [                   ] SocketListener/AgentTunnels: listening on [0.0.0.0]:4703
2019.09.20 12:54:08.948 *I* [                   ] SocketListener/Clients: listening on [0.0.0.0]:4701
2019.09.20 12:54:08.948 *I* [                   ] SocketListener/MobileDevices: listening on 0.0.0.0:4747
2019.09.20 12:54:08.948 *I* [                   ] SocketListener/MobileDevices: listening on [0.0.0.0]:4747
2019.09.20 12:55:34.062 *E* [                   ] Call to GetIpNetTable() failed (???????? ??????? ?????????.)
2019.09.20 12:56:09.997 *E* [                   ] Call to GetIpNetTable() failed (???????? ??????? ?????????.)
2019.09.20 12:56:13.561 *E* [                   ] Call to GetIpNetTable() failed (???????? ??????? ?????????.)
2019.09.20 13:04:27.948 *D* [ncd.generic        ] Cannot open serial port <[root]>
    <Generic>
        <port>Com3</port>
    </Generic>
</[root]>

2019.09.20 13:24:52.193 *D* [ncd.generic        ] Cannot open serial port <[root]>
    <Generic></Generic>
</[root]>


Tatjana Dubrovica

У меня сервер падает после удалении канала. Я починила возможную проблему. Изменение войдёт в следующи патч релиз.

Ещё поправила конфигурацию generic канала, тоже войдёт в следующи патч релиз. Сейчас он ждёт portname=Com3 в конфигурации а не port=Com3. Так что сейчас можно поправить конфигурацию.