Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Victor Kirhenshtein

#6361
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
#6362
General Support / Re: Linux compile error
October 08, 2010, 03:19:00 PM
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
#6363
I have fixed this bug. Fix will be included in next release.

Best regards,
Victor
#6364
General Support / Re: Parser Support Variable Filename
October 05, 2010, 09:53:41 PM
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
#6365
General Support / Re: Licensing
October 05, 2010, 04:59:38 PM
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
#6366
Poprobujte versiju 1.0.5 - tam sdelani izmenenija dlja predotvraschenija deadlock'a pri rabote s DCI, dolzno pomoch'.
#6367
General Support / Re: ICMP/Polling problems
October 05, 2010, 02:27:31 PM
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
#6368
General Support / Re: Licensing
October 05, 2010, 01:39:37 PM
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

#6369
Announcements / NetXMS 1.0.5 released
October 05, 2010, 01:37:28 PM
Hi all!

NetXMS version 1.0.5 is out. Changes since 1.0.4:

- New NXSL operators: += -= *= /= .= %= &= |= ^=
- New NXSL functions: index, rindex
- MIB compiler improved
- New MIBs added to default distribution:
   ASTERISK-MIB, DIGIUM-MIB, NetWare-Server-MIB, NETWORK-APPLIANCE-MIB
- Windows console: fixed problem with saving Object Browser and maps in
 desktop layout
- Fixed issues: #279, #303, #304, #305

Best regards,
Victor
#6370
Fixed in 1.0.5. Thanks for reporting!

Best regards,
Victor
#6371
Windows / Re: NetXMS 1.0.3 - missing dsp project
October 02, 2010, 12:34:39 AM
I have added missing files to dist in 1.0.5. Also, resources for most of the projects may not load until message files compiled to binary form - try to compile messages.mc first.

Best regards,
Victor
#6372
Добрый день!
А можно прислать скрипт disksp.sh? Попробую у себя погонять. И еще вопрос - агент под рутом запущен?
#6373
General Support / Re: problems creating database
October 01, 2010, 10:40:29 AM
Hi!

You are using installation wizard, right? What user you are using as DBA account? Does it have rights to create new database? If you not using Windows authentication, do you enable SQL Server authentication?

Best regards,
Victor
#6374
General Support / Re: SNMP Traps
September 28, 2010, 11:21:27 AM
Yes, you have to configure traps to events matching manually for each trap. Also, if you will go that way and create trap configuration for Juniper traps, it will be nice if you can export trap configuration and publish it here.

Best regards,
Victor
#6375
General Support / Re: Endit a .bat file so XMS can alert
September 28, 2010, 11:19:06 AM
Hi!

You have two options:

1. Create an action of type "execute command on management server", entering your command in "command" field like following:


c:\\Rcmd \\\\exchange1 osql -S exchange1 -U sa -P ourpassword -Q "insert into VGSMDB..loglog (destination, content) values ('Majors','Server %n is down')"


Note that all backslashes are doubled, because backslash is an escape character in action command definition, and you have to use \\ to get single backslash in command.

2. Modify you .bat file to accept server name as argument:


@echo off

c:\Rcmd \\exchange1 osql -S exchange1 -U sa -P ourpassword -Q "insert into VGSMDB..loglog (destination, content) values ('Majors','Server %1 is down')"

pause


and define action to call it, with "command" field set to


my_script.bat %n



In both cases, just add this new action to appropriate rule in event processing policy.

Hope this helps!

Best regards,
Victor