News:

We really need your input in this questionnaire

Main Menu
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

#6616
Try to replace netinfo.cpp with attached one.

Best regards,
Victor
#6617
General Support / Re: Not able to connect Database
January 07, 2010, 01:13:08 PM
Your database user netxms does not have access rights to database netxms. Try to grant required rights with the following MySQL query:


GRANT ALL ON netxms.* to netxms@localhost;


Best regards,
Victor
#6618
Hi!

You need Platform SDK, OpenSSL, and ZLib.  Others required only for some components:

DDK - for UPS subagent;
libgd - for nxhttpd;
DB library - for MSSQL database driver;
Scintilla - for management console;
Microsoft Speech SDK - for management console;
MySQL client - for MySQL database driver;
PostgreSQL client - for PostgreSQL database driver;
Oracle client - for Oracle database driver;

Packages not listed here are not needed for NetXMS build.

Best regards,
Victor
#6619
Probably something is wrong with headers you are using. Attached is my startup file for VC6, may be it will help. I use Platform SDK for Windows Server 2003, because many headers and libraries in VC6 distribution is outdated or missing.

Best regards,
Victor

#6620
Popravil node.cpp.
#6621
General Support / Re: SQlite failing
December 26, 2009, 04:06:53 PM
Could you please post complete error message from server's log?

Best regards,
Victor
#6622
Did you have libmysqlclient.so somewhere in the system? If yes, where?

Best regards,
Victor
#6623
Poprobujte zamenit' faili node.cpp i interface.cpp v src/server/core na prilozennie i peresobrat' server.
#6624
Please post your config.log

Best regards,
Victor
#6625
Polls / Smartphone client
December 26, 2009, 12:11:23 AM
For which smartphone platform you'd like NetXMS client to be developed? If you don't see any need for mobile client, please answer "I don't need smartphone client" so we know how important this feature is.

Best regards,
Victor
#6626
General / Re: problem with development
December 25, 2009, 12:18:18 PM
You have missed code for actual message reception. Instead of


// Initialize raw message receiving function
pMsgBuffer = (CSCP_BUFFER *)malloc(sizeof(CSCP_BUFFER));
RecvNXCPMessage(socketId, pRawMsg2, pMsgBuffer, RECEIVER_BUFFER_SIZE,0,0,0);

// Allocate space for raw message
pRawMsg2 = (CSCP_MESSAGE *)malloc(RECEIVER_BUFFER_SIZE);
pMsg2 = new CSCPMessage(pRawMsg2);


you should have something like


// Initialize raw message receiving function
pMsgBuffer = (CSCP_BUFFER *)malloc(sizeof(CSCP_BUFFER));
RecvNXCPMessage(0, NULL, pMsgBuffer, RECEIVER_BUFFER_SIZE,0,0,0);

CSCP_ENCRYPTION_CONTEXT *nullContext = NULL;
pRawMsg2 = (CSCP_MESSAGE *)malloc(RECEIVER_BUFFER_SIZE);
RecvNXCPMessage(socketId, pRawMsg2, pMsgBuffer, RECEIVER_BUFFER_SIZE,&nullContext,NULL,0);
pMsg2 = new CSCPMessage(pRawMsg2);


Best regards,
Victor
#6627
Hi!

Could you please post screenshots with your configuration - DCI configuration, Threshold configuration, event processing policy?

Best regards,
Victor
#6628
Eto trebuet izmenenij v LogWatch. Na etu temu est' issue v bugtracker'e (#271), nadejus' chto k sledujuschemu relizu mi eto sdelaem.
#6629
Parametri, peredavaemie v sobitii na vozvrat znachenija k norme (standartnoe sobitie - SYS_THRESHOLDS_REARMED), otlichajutsja ot parametrov dlja sobitija na otklonenie ot normi (standartnoe sobitie - SYS_THRESHOLD_REACHED). Dlja SYS_THRESHOLD_REARMED parametri takie:

1) Parameter name
2) Description
3) DCI ID
4) Instance

Znachenija tam ne peredajutsja. Eto ne ochen' udachnoe reshenie, pravil'nej bilo bi imet' odinakovij nabor parametrov i v tom i v drugom sluchae, no sejchas uze slozno menjat' chto-to iz-za uze suschestvujuschih konfiguracij. Horoshego reshenija ja poka ne pridumal.
#6630
Hello!

Did you look at this example: https://www.netxms.org/documentation/confexample/? It has a bit outdated screenshots, but you should got the idea. Example is for CPU usage monitoring, but you can easily adapt it for disk space, etc. with simple changes.

Best regards,
Victor