NetXMS Support Forum

Ok, that's good to know. We're in something of a rough state at the moment with our install due to this issue (things don't move around properly, zone GUIDs are duplicated because we deleted one and added one and the original didn't delete properly, can't remove old cruft) and think we might be better served starting over fresh. Is there an easy way to re-initialize the database and start over from scratch that doesn't involve deleting the DB? Another team manages our databases and if we can do this ourselves it'd be easier.

Hey that's great news. Do you happen to have a time-frame for when we can expect to see that released?

Alright, that sounds good to me! Thanks for all so far.

I can certainly try! What dev studio do I need for that? Eclipse? I've only worked in Visual Studio and some Borland stuff ages ago.

That worked quite well, thank you. This is what we're seeing:
D:\NetXMS\log>find "delet" netxmsd.log
.... (snipped)
2020.02.20 20:00:27.827 *D* [obj.sync           ] Unable to delete object with id 81066 because it is being referenced 2 time(s)
2020.02.20 20:00:27.827 *D* [obj.sync           ] Object 23 [81067] marked for deletion
2020.02.20 20:00:27.827 *D* [obj.sync           ] Unable to delete object with id 81067 because it is being referenced 2 time(s)
2020.02.20 20:00:27.827 *D* [obj.sync           ] Object 24 [81068] marked for deletion
2020.02.20 20:00:27.827 *D* [obj.sync           ] Unable to delete object with id 81068 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object 25 [81069] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81069 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object 26 [81070] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81070 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object 27 [81071] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81071 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object 28 [81072] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81072 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object DEFAULT_VLAN [81073] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81073 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object VLAN4 [81074] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81074 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object VLAN7 [81075] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81075 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object VLAN8 [81076] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81076 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object VLAN9 [81077] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81077 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object VLAN10 [81078] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81078 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object VLAN41 [81079] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81079 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object VLAN55 [81080] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81080 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object VLAN85 [81081] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81081 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object VLAN92 [81082] marked for deletion
2020.02.20 20:00:27.828 *D* [obj.sync           ] Unable to delete object with id 81082 because it is being referenced 2 time(s)
2020.02.20 20:00:27.828 *D* [obj.sync           ] Object VLAN93 [81083] marked for deletion
.... (snipped)

There are 1566 matching lines generated over the course of maybe 30 seconds, so I think it's safe to say you're onto something here. I'm not sure what to do about it, though.

We keep logging set at 0 generally, so I turned on debug 6 and deleted a set of objects that are known to return. I let the debug run for a few seconds after that as well, and don't find any references to what you mentioned in the log. We generate a lot of logging very quickly, so that few seconds of debug 6 made a 4MB log, making it challenging to leave it running for a while. Would that be occurring randomly, or right at the time of delete?

Hello,
We are seeing an issue where when we delete nodes, subnets, and/or zones from NetXMS, they return after the NetXMS core service is restarted. We are running version 3.1p3, though I can't say exactly when the issue started. I've run the nxdbmgr check -f command it it resolved some issues, but the issue still occurs. What can I check? Thanks!

I know this is old, but today we just solved this one. It turns out that the LdapUserMappingName configuration field is case sensitive - I had samAccountName populated there, but in AD the attribute is written as sAMAccountName. When I put this in instead, the sync worked. Many thanks to Tatjana for her help in this!

Hello all,
I am trying to setup LDAP sync with MS Active Directory but users and groups are not being added.

My configuration:
Name   Value
LdapConnectionString   ldaps://####.net
LdapGroupClass   group
LdapGroupMappingName   samAccountName
LdapGroupUniqueId   objectGUID
LdapMappingDescription   description
LdapMappingFullName   name
LdapPageSize   1000
LdapSearchBase   DC=####,DC=NET
LdapSearchFilter   (objectClass=*)
LdapSyncInterval   0
LdapSyncUser   CN=####,OU=Admin,DC=####,DC=net
LdapSyncUserPassword   ####
LdapUserClass   user
LdapUserDeleteAction   Disable user
LdapUserMappingName   samAccountName
LdapUserUniqueId   objectGUID

Log shows:

2019.09.16 20:45:55.478 *D* LDAPConnection::fillLists(): member: CN=TimSim01,OU=PRJ_Employees,OU=Users,OU=PRJ,OU=GIT,OU=KGR,DC=####,DC=net
2019.09.16 20:45:56.244 *D* LDAPConnection::fillLists(): member: CN=TimSim01,OU=PRJ_Employees,OU=Users,OU=PRJ,OU=GIT,OU=KGR,DC=####,DC=net
2019.09.16 20:45:58.371 *D* LDAPConnection::fillLists(): member: CN=TimSim01,OU=PRJ_Employees,OU=Users,OU=PRJ,OU=GIT,OU=KGR,DC=####,DC=net
2019.09.16 20:45:58.386 *D* LDAPConnection::fillLists(): member: CN=TimSim01,OU=PRJ_Employees,OU=Users,OU=PRJ,OU=GIT,OU=KGR,DC=####,DC=net
2019.09.16 20:45:59.246 *D* LDAPConnection::fillLists(): Found dn: CN=TimSim01,OU=PRJ_Employees,OU=Users,OU=PRJ,OU=GIT,OU=KGR,DC=####,DC=net
2019.09.16 20:45:59.246 *D* LDAPConnection::fillLists(): Unknown object is not added: dn: CN=TimSim01,OU=PRJ_Employees,OU=Users,OU=PRJ,OU=GIT,OU=KGR,DC=####,DC=net, login name: (null), full name: TimSim01, description: TimothySimmons undefined
2019.09.16 20:45:59.277 *D* LDAPConnection::fillLists(): member: CN=TimSim01,OU=PRJ_Employees,OU=Users,OU=PRJ,OU=GIT,OU=KGR,DC=####,DC=net
2019.09.16 20:45:59.277 *D* LDAPConnection::fillLists(): member: CN=TimSim01,OU=PRJ_Employees,OU=Users,OU=PRJ,OU=GIT,OU=KGR,DC=####,DC=net
2019.09.16 20:45:59.386 *D* LDAPConnection::fillLists(): member: CN=TimSim01,OU=PRJ_Employees,OU=Users,OU=PRJ,OU=GIT,OU=KGR,DC=####,DC=net
2019.09.16 20:45:59.386 *D* LDAPConnection::fillLists(): member: CN=TimSim01,OU=PRJ_Employees,OU=Users,OU=PRJ,OU=GIT,OU=KGR,DC=####,DC=net
2019.09.16 20:46:00.121 *D* LDAPConnection::fillLists(): member: CN=TimSim01,OU=PRJ_Employees,OU=Users,OU=PRJ,OU=GIT,OU=KGR,DC=####,DC=net
2019.09.16 20:46:00.761 *D* LDAPConnection::fillLists(): member: CN=TimSim01,OU=PRJ_Employees,OU=Users,OU=PRJ,OU=GIT,OU=KGR,DC=####,DC=net

It almost looks like the values aren't being assigned to the right fields (off by 1?) and as such, no new users or groups are getting added.
It's also not turning up any users with '-'s in their name in the log, and all of the users we would want end in -admtx. I'm not sure if that's a real problem or not through because I can't get the user database to populate. Thanks for any help you can give!

Hello all,
I have the web management console installed on a windows server. I have setup IIS ARR to do reverse proxy w/ SSL offload to this console, but I want to restrict the web console itself to only listen to traffic from the reverse proxy server (localhost/127.0.0.1). How is it possible to do this? I tried to modify jetty.xml to set the jetty.host parameter but was unsuccessful.

Greetings all,
I am evaluating NetXMS for use in our environment and I have a question about how to best represent stacked switches in the rack function. Since they only show up as one node, it's challenging for us. It's not uncommon for us to have switch stacks spread out across multiple racks as well - usually in the same room, but sometimes not. What is the best way to represent this? We use Juniper (EX), Aruba (2930f, 3810m), and Cisco (moving to Cat 9series) mostly - but we could inherit all sorts of things.