NetXMS Support Forum

Na samom dele eto stranno, poskol'ku v baze server hranit vse timestamp'i v UTC, i perevod v lokal'nuju time zonu proishodit na kliente. T.e. Oracle na etot pereschet vlijat' ne dolzen. A v Last Values vremja vsegda pravil'no otobrazaetsja?

Currently the only option is to recreate nodes. I'll try to add possibility to move node into cluster in 1.0.6 release.

Best regards,
Victor

Dobrij den'!

A konsol' restartili posle smeni nastroek? Poskol'ku pri smene time zoni uze otformatirovannie timestampi ne peredelivajutsja, tol'ko vo vnov' otkrivaemih oknah ili posle refresh'a uchitivaetsja novaja time zona, to mozet vozniknut' takaja situacija. A vot esli eto posle restarta, ili oba okna otkriti posle smeni time zoni, togda eto ochen' strannij bag...

Eto bag v GUI, ispravlju v sledujuschej versii. Mozno pereimenovat' zajdja v properties i vpisav novoe imja v pole "name".

Currently it's a mix. End of sequence flag was introduced later during protocol development, so some lists uses special message, and some uses this flag.

Best regards,
Victor

Hi!

Currently, the only way to lock node's DCI list is to issue CMD_GET_NODE_DCI_LIST, because when I was writing this, I was thinking only about GUI client, which usually need to display current DCI list immediately. Our current intention is to remove all exclusive locks for configuration and replace it with change notifications - this is already done for some parts of server configuration, like use management. Why receiving full DCI list is a problem? You can just ignore it if you don't need it. And for end of list - you don't have to wait a timeout to detect a list end - each NXCP message has a flags field, and in many list responses flag "END OF SEQUENCE" (0x0008) is used to indicate end of list. In case of DCI list, at the end you will get empty message with this flag set.

Best regards,
Victor

Hi!

All %number macros are event-dependent. %5 will be DCI ID for threshold violation events. However, for threshold rearm events DCI ID will be %3 (I know that it's confusing, but unfortunately this cannot be changed without breaking backward compatibility). There should not be any difference on how DCI was created - directly on the node or via template.
Could you please provide more details about your configuration (DCI thresholds configuration, event policy rule)?

Best regards,
Victor

Character escaping bug fixed as well. I agree that we should switch to nvarchar from varchar in MS SQL, and we definitely will do that, but it's a major change, which will require careful examination of many SQL statements within existing code.

Best regards,
Victor

Hi!

Problem is with "--with-mysql=/usr/bin/mysql" configure option. You supposed to specify MySQL installation directory here, not a path to MySQL client binary. In most cases, you may just specify --with-mysql without any parameters. So, try to run configure as follows:

./configure --with-server --with-agent --with-client --with-mysql --enable-debug --with-nxhttpd  --prefix=/opt/netxms

Best regards,
Victor

I have fixed this bug. Fix will be included in next release.

Best regards,
Victor

Hi!

It's not possible to take most recent file in directory for log parsing. The only workaround I see is to update <file> section in parser's XML with some external script on server start. I have created feature request (https://www.netxms.org/bugtrack/view.php?id=306) to improve this in the future.

Best regards,
Victor

Subagent is a shared library loaded by nxagentd, so it's nxagentd linked to subagent. The only dependence for any subagent is libnetxms, which is LGPL. From the GPL FAQ (http://www.gnu.org/licenses/gpl-faq.html#GPLAndPlugins) it looks like a borderline case - core agent calls subagents periodically via few entry points. Also, if I understand license correctly, it doesn't matter until you use your proprietary modules in your organization and not selling them.

Best regards,
Victor

Poprobujte versiju 1.0.5 - tam sdelani izmenenija dlja predotvraschenija deadlock'a pri rabote s DCI, dolzno pomoch'.

Hi!

Didn't you miss some alarms? It can happen in this situation that node down alarm didn't get terminated automatically, and you have to terminate it manually. If this is not the case, than it's definitely a strange bug.

Best regards,
Victor

Version 1.0.5 just released, where I have changed licensing for most libraries to LGPL. Current licensing scheme is as follows:

NetXMS components:

libnetxms       LGPL
libnxcl         LGPL
libnxdb         LGPL
libnxlp         LGPL
libnxmap        LGPL
libnxmb         GPL
libnxsl         LGPL
libnxsnmp       LGPL
libnxsrv        LGPL
nxagentd        GPL
nxalarm         GPL
nxav            GPL
nxcon           GPL
nxcptest        GPL
nxevent         GPL
nxflowd         GPL
nxhttpd         GPL
nxlexer         GPL
nxlptest        GPL
nxmibc          GPL
nxnotify        GPL
nxpush          GPL
nxscript        GPL
nxsms           GPL
nxsnmpget       GPL
nxsnmpset       GPL
nxsnmpwalk      GPL
nxuilib         GPL

all subagents   GPL
all DB drivers  GPL
all SMS drivers GPL


Third party components bundled with NetXMS:

freetype        BSD-like
libexpat        BSD-like
libgd           BSD-like
libipfix        LGPL
libjpeg         BSD-like
libpng          BSD-like
scilexer        BSD-like
sqlite          BSD-like
zlib            BSD-like

Best regards,
Victor