NOTICEPOTENTIAL FOR DATA LOSS.
The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure, please contact Product Support Services prior to attempting the procedure below.
NOTICECOMPLEX PROCEDURE REQUIRED.
The resolution of this article has many complex steps that may result in unforeseen results if not performed correctly. If you are at all unfamiliar with the requirements, please contact Product Support Services for assistance.
Invalid NSD Device entries can cause NSM5200 Recording Pool malfunctions, including failure to record, video gapping, or other anomalies.
Pelco Video Management
- NSM5200 versions 02.03.01.0259 and below.
NSM Recording Pool Database has become corrupt due to several possible root causes, such as improper NSM Member removal, moving of NSM Members to other pools, network communication or defunct NSM Service states. See Lessons Learned Article LL#10446 for details.
Section 1: Verify existence of duplicate or invalid NSM Entries within the Pool Manager networkconfig database
note: For the best viewing experience, click here to visit this article directly.
note: There are two ways the issue may manifest, use both Methods below to check for the issue, then proceed to fix if either method reveals invalid/duplicate NSM entries.
Launch , log in and press Search.
note: The default login credentials are [Username: admin and Password: admin].
Method 1 - From the System Attributes tab, right-click the NSM5200 Pool Manager in question and select Open Web Interface, then login to the NSM WebUI, go into the NSM Pool tab and check for duplicate or invalid entries in the NSMs in pool: table, as seen here:
note: In this example, the NSM with the name kkcnsms2srvr is an invalid duplicate entry, which was verified by visiting the NSM Member WebUI at http://192.168.160.109 and verifying that the current Unit Name was kkcnsmsrvr2 (note the placement of the number 2 in this example). It is believed that a name change to the NSM Member during an abnormal system state (config db or other critical service was offline or non responsive) created this problem, though there are several possibilities as to the true root cause.
2a. Now that we know which name is invalid for this NSM, we can search for this in the devices xml data. To do this, modify the URL in your current internet browser connection to the NSM5200 by adding the port (:10000) and the path to the devices xml data (/devices) and press enter. Once loaded, utilize your browsers find function (control-f in most browsers) to search for the invalid entry (kkcnsm2srvr in this example), and then copy the value for the device id= into your clipboard (control-c) as shown below -
note: If you've identified an invalid/duplicate NSM using Method 1 above, skip Step 3 below, and proceed to Section 2: Remove invalid NSD Devices.
Method 2 - From Endura Utilities System Attributes tab, right-click the NSM5200 in question and select SSH Into -
note: The default Linux Administrative login credentials for Endura Linux devices is [Username: root and Password: pel2899100 ]
note: If you have never SSH'd into the unit before, you will likely receive the following warning prompt...
...simply click Yes to proceed.
note: If you receive the following error...
...visit http://www.putty.org/ to download Putty, then copy putty.exe into a directory contained in the Windows Environment Path Variable (i.e. c:\windows\system32).
3a. Issue the command nsterm and press enter, then enter the number corresponding to the nsm service entry for the nsm pool manager in question and press enter, and finally type n and press enter to check for invalid NSD Devices as shown below...
note: In this example, the UUID highlighted above was actually an NSM Member from another pool which had been incorrectly removed from this pool at some point in the past. If you are unsure of how to identify invalid entries, contact Pelco Technical Support at (800) 289-9100 for assistance.
Section 2: Remove invalid NSD Devices
!! WARNING !! - Incorrect utilization of steps within this section may result in loss of video!
If unsure, contact Pelco Technical Support at (800) 289-9100 for assistance.
To remove an NSD Device from the NSM5200 postgresql2 networkconfig database, follow these steps -
SSH into the NSM5200 Manager as shown in step 1a above.
Stop services -
service pald stop
service nsxd stop
Start the postgresql2 database server
service postgresql2 start
Connect to postgresql2 database by typing this command -
/usr/local/pgsql/bin/psql -U pelco -p 5490 -d networkconfig
Using the UUID you obtained in the Method 1 or Method 2 above, search for this entry in the database -
select * from device where id ilike '%uuid:3fec567f%';
note: The Universal Plug and Play Universally Unique Identifier (UUID aka UDN) used in this section is just an example, make sure to replace it with the UUID obtained from Method 1 or Method 2 above. Most cases it won't be required to type in "uuid:" unless it's displayed in step 2a.
Delete the Invalid NSD Listing, and verify this has been done successfully -
delete from device where id ilike '%uuid:3fec567f%';
select * from device where id ilike '%uuid:3fec567f%';
Exit the database by typing \q and pressing enter.
Reboot the NSM5200 Pool Manager by typing reboot and pressing enter.
- Wait at least 12 minutes for the NSM5200 to complete reboot and services start, and verify the duplicate/invalid NSM no longer exists using Method 1 or Method 2 above.