Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Problem adding node from web

Has anyone else had an issue similar to this when adding nodes from the web?
I added a new server from the web console, selected the various resources, and set some custom properties on it.
We then took it down to make some changes.
The built-in alert from Orion that adds an event to the log fired, but my other advanced alert did not. This alert is using a custom property.
I couldn't figure out why the advanced alert didn't for this system since it works on all the others.

I then deleted the system and re-added it from the Orion console, selected resources, custom properties, etc..
I then took it down again and this time the alert fired as it was supposed to.

I'm wondering if it is related to adding the node from the web in general, or if it had to do with setting custom properties from the web. Some of the custom properties are True/False check boxes and I'm curious as to whether it had to with entering the text 'True' into one these. If so, I want to make sure we follow specific procedures when adding nodes.

Thanks.

Find more posts tagged with

Accepted answers

All comments

Ohmus

For those of you that are interested, I found out what the problem is. If you are using any True/False custom properties, these are set to 'NULL' in the Nodes table when the device is added from the Web. When added via the Orion Console (System Manager), these are set to false ('0' in the table) unless selected.

Due to the fact that my advanced alert was relying on a custom property that is True/False, the NULL entry in the database did not show the property as 'False', thus the alert did not fire.

You can verify this by checking any custom properties you have that are True/False in the Nodes table in your database. All values 'should' be '0' or '1'. If the node was added from the web, these values will be 'NULL'.

jdedmundson

Whe we add node from the web console and then go back to manage the node the web console errors out, Could this be caused by the 'NULL'?

mark_wiggans

This issue will addressed in 9.1-

The workaround is to open the custom property editor and editing a single one which should set them all to the proper default.

jdedmundson

When is 9.1 going to be released?

Ohmus

This issue will addressed in 9.1-
The workaround is to open the custom property editor and editing a single one which should set them all to the proper default.

That does work. However, we have a large number of custom properties and I have found several systems that were added from the web, so it's kind of a pain. I just wish my SQL skills were a little stronger so I could update it from the backend.

How come when I opened a ticket, support didn't know what the problem was?

mark_wiggans

This issue will addressed in 9.1-
The workaround is to open the custom property editor and editing a single one which should set them all to the proper default.

How come when I opened a ticket, support didn't know what the problem was?

Not sure really, I just found out about 10 minutes ago myself.

Ohmus

The 9.1 upgrade did in fact fix the issue with the NULL entries in the Custom Properties. Plus the new VMWare views are sweet.

Keep up the great work SolarWinds!