NetXMS Support Forum

Ispravil. Na kakoj platforme u vas server i kakoj versii? Esli Linux, to v faile src/server/core/node.cpp nado stroku


int snmpMethods = DBGetFieldLong(hResult, 0, 21);


zamenit' na


int snmpMethods = DBGetFieldLong(hResult, 0, 22);


(eto stroka 242 v trunke, v drugih versijah mozet bit' +/- neskol'ko strok)

i peresobrat' server. Esli Windows, to mne nado znat' versiju servera (1.0.11 ili 1.1.0), togda smogu vilozit' patch.

Takoj vopros - naskol'ko sloznim bil bi dlja vas perehod na versiju 1.1.x i Java Console? Tam karti sil'no peredelani. V versii 1.1.1 pojavitsja migracija kart, sdelannih v 1.0.x versijah, v novij format. V 1.0.x karti - odna iz samih neudachnih veschej na moj vzgljad, mnogovato s nimi problem...

Dobrij den'!

Ja poprobuju segodnja povtorit' u sebja.

Hi!

Please run agent with full debug (nxagentd -D 9), do configuration poll from console, and send me output of configuration poll and agent's log.

Best regards,
Victor

Did you install agent using agent installer on same machine where NetXMS server is running? Normally you shouldn't do that, because server installer installs agent as well.

Best regards,
Victor

Hi!

Is NetXMS agent running on NetXMS server machine? Is portcheck subagent loaded? (you can check this by right-clicking on NetXMS server node, and selecting Tools->Info->Agent->Subagents).

Best regards,
Victor

Poprobujte zamenit fail src/db/dbdrv/mysql/mysql.cpp na prilozennij i peresobrat'.

Pohoze nashel problemu, sejchas sdelaju patch.

Try to delete both subnets (this will not delete nodes unless the subnet is the only parent object for a node) and do configuration poll on nodes. Server should create one subnet object.

Best regards,
Victor

Hi!

NetXMS by itself is working on Windows 7 (I do most of development and testing on Windows 7), but mssql database driver uses very old and deprecated API called DB-library, which may be incompatible with modern Windows versions. It will be removed in 1.1.x branch. For connecting to MS SQL, it is now recommended to use ODBC.

Best regards,
Victor

Ja podumaju chto eto mozet bit'. U menja sejchas net vremeni, smogu vecherom vnimatel'no etim zanjatsja. Esli vremja terpit, to podozdite otveta do zavtra.

Poprobuhte prosto udalit' etu zapis:
Delete from interfaces where id=17;
Delete from object_properties where object_id=17;

A kakoj rezul'tat dadut sledujuschie SQL zaprosi, esli ih vipolnit' iz mysql klienta:

SELECT name,status,is_deleted,inherit_access_rights,last_modified,status_calc_alg,status_prop_alg,status_fixed_val,status_shift,status_translation,status_single_threshold,status_thresholds,comments,is_system,location_type,latitude,longitude,guid FROM object_properties WHERE object_id=17;

SELECT attr_name,attr_value FROM object_custom_attributes WHERE object_id=17;

Zapustite s debug level 9 - posmotrim kakie SQL zaprosi delajutsja i na chem vse obrivaetsja. Takze mozno poprobovat' zapustit' pod gdb.

By default, server check configuration of each node every hour - it's called "configuration poll". You can forcibly execute configuration poll by right-clicking node in console and then selecting Poll->Configuration. Or you can just wait one hour.

Best regards,
Victor