NetXMS Support Forum

Problem solved. Thank you very much.

M

NETXMS Team and Users Group,

I am using the following HTTP Service Check format listed below. My question is can NETXMS view the keepalive.html page inside the "/folder/"?

ServiceCheck.HTTP(xxx.xxx.xxx.xxx,80,/folder/keepalive.html,www.test.com,"^HTTP/1\.[01] 200.*")

I keep getting a number "3" response or "bad server's response".
----------------------------------------------------------------------------------------------------

Other HTTP Service Checks I have setup on this same server are using the format below and they are working just fine:

ServiceCheck.HTTP(xxx.xxx.xxx.xxx,80,/index.html,www.test.com,"^HTTP/1\.[01] 200.*")

I wonder if the extra "/folder/" makes a difference.

Thanks,

Mauricio

Victor,

Our NETXMS server is back up and running. I will continue to monitor the NETXMS server and I will update you on the status.

Thank you for all of your support. Hope all is well.

Mauricio

Victor,

I upgraded and checked the database and this is what I get. I still can't seem to start the service on the server. It still fails to start. I have removed and reinstalled NETXMS and it is still hanging up on starting the service.

Any idea?
----------------------------------------------------------------------------------------------------

C:\NetXMS\bin>nxdbmgr check
NetXMS Database Manager Version 0.2.29

Configuration file OK
Checking database:
* Checking node objects...                                            [PASSED]
* Checking interface objects...                                       [PASSED]
* Checking network service objects...                                 [PASSED]
* Checking cluster objects...                                         [PASSED]
* Checking template to node mapping...                                [PASSED]
* Checking object properties...                                       [PASSED]
* Checking event processing policy...                                 [PASSED]
* Checking collected data...                                          [PASSED]
Database doesn't contain any errors
Database check completed

C:\NetXMS\bin>nxdbmgr upgrade
NetXMS Database Manager Version 0.2.29

Configuration file OK
Upgrading database...
Your database format is up to date

C:\NetXMS\bin>

Thank you for this. It helped tremendously!

Mauricio

Hi Victor and Team,

I upgraded from upgraded my server from version 0.2.27 to version 0.2.29 and now I am having having problems. I tried starting the service manually and it won't start.

I checked the NETXMS using nxdbmgr check and I get the following:

C:\NetXMS\bin>nxdbmgr check
NetXMS Database Manager Version 0.2.29

Configuration file OK
Checking database:
Your database has format version 95, this tool is compiled for version 98.
Use "upgrade" command to upgrade your database first.
Database check aborted

C:\NetXMS\bin>nxdbmgr upgrade
NetXMS Database Manager Version 0.2.29

Configuration file OK
Upgrading database...
Upgrading from version 95 to 96
SQL query failed ([Microsoft][ODBC SQL Server Driver][SQL Server]The data types
text and varchar are incompatible in the equal to operator.):
UPDATE object_properties SET comments='' WHERE comments='#00'
Rolling back last stage due to upgrade errors...
Database upgrade failed

My question is where do I make this change or what is the best way to correct this problem.

Thank You

Mauricio

Hi Victor,


Help??? When the alert notifications are sent out by the NETXMS server to the my email I can't tell what system it is coming from. All alerts look the same. Is there a setting I am missing on the agent that would identify what system is causing the alert notification?

Example: If System A goes down won't the alert notification state that System A has gone down? At this point all I get is a notification stating that a system is down but it doesn't tell me which one. This is important as we have over 100 systems using NETXMS.

I know Victor is very busy....can anyone else help?

Thanks,

Mauricio

Hi Victor and Team,

Hoping you could help us on this one....

We have deployed the agents and they respond just fine when we poll the systems from the console but the information provided does not show the system IP.

Additionally, I have set up the default alarms in the event processing policy editor to send email notifiaction and I can't get the alarm notifications to identify where the notifications are coming from. I need the email alert notification to show an IP or hostname in order to determine what system has the problem. Is there a way to add a setting that would help us ID the system via IP address or hostname when their is an issue with that specific system.

At this time all I get is " NXMS Alert - Node Down" and no identifying information.

or "NXMS Alert - System Thread Hang" but again no identifying information.

Thanks a million!!!

Mauricio

Greetings Victor,

I recently added the latest patch to our NetXMS server. We went from release 02.22 to release 02.24. I then proceeded to add the nxagent-0.2.24-win32.npi to the Agent Package module and I started deploying it to systems on our network.  During this deployment I encountered a problem that causes me to lose complete connectivity to the agents.

Six of the agent upgrades installed correctly and 2 have hung during the deployment installation and lose communication with the NetXMS Server. They can't be polled anymore from the NetXMS console.

I tried uninstalling the agent 02.22 and reinstalling it but it was unsuccessful. I also tried to install 02.24 directly on the box and I get the same unsuccessful results.

If you try to reinstall anyone of the agents release 02.22 or release 02.24 it reports a message telling you the following:

"The application has failed to start because libnetxms.dll was not found. Re-installing the application may fix this problem. "

I am also getting an Error message that states:

" C:\NetXMS\bin\nxagentd.exe

An error occurred while trying to replace the existing file: Deleted
File failed; Code 5
Access is denied.
Click retry to try again, Ignore to skip this file(not recommended), or Abort to cancel installation."

One computer is running Windows Server 2000 SP4 and the other is running Windows Server 2003 SP2.

Any ideas what could be causing this problem?

Thank You,

Mauricio