No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NVR6128 stopped recording and was unable to access

Publication Date:  2014-05-28 Views:  102 Downloads:  0
Issue Description
eSpace NVR6128 suddenly stoped working properly. Recording of all cameras stoped. The IP which was configured for that specific NVR was also not pinging. GUI of Linux and ssh was also not working and not any process was running properly.
Alarm Information
None. As all the Hard Disks were normal and there was no alarm on the NVR as well.
Handling Process
It was seemed that there is some space issue, like might be the hard disks are full and no free space left. So tried to find out the Diskspace status specifically for "/path" to see that how much space it is using as mentioned below.

nvr6128:~ # df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdj1             197G  197G     0 100% /
udev                  3.9G  188K  3.9G   1% /dev
/dev/sdj6             197G  422M  187G   1% /DB_DATA
/dev/sdj5             493G   13G  455G   3% /home
/dev/sdj7             591G  297M  561G   1% /mrumnt/RecordIndexFile
/dev/sdj3             296G  1.2G  280G   1% /opt
nvr6128:~ #

So then it was cleared that "/path" is full that's why all processes are not working properly.

Then we came to know the actual issue, which was that the RAID was "Unmount" so the recording data occupied the "/path" which made that full and all processes stoped working properly. So the data from "/path" was deleted and RAID was re-assembled again. And finally the NVR6126 started working properly and recording started as well.

Root Cause
NVR6128 stopped pinging, so it was restarted just to reset the services that if some service is not working properly then it may reset after restart. It started pinging after it was being restarted but still it was neither accessing through the ssh nor through the GUI interface of the server. And recording issue was also still there. It was showing the following errors when we tried to access.

1: When I tried to access through the IVS client it was showing the following error before restart and after restart. 
 "login timeout due to network execption or server unstarted."

2: When I tried to access it directly through the Linux GUI then the follwoing error was coming before restart.
"Your session only lasted less than 10 seconds. If you have not logged out yourself, this could mean that there is some installation problem or that you may be out of dsskspace. Try to loggin in with one of the failsafe sessions to see if you can fix this problem. "

3: After restart it was showing main Linux GUI page but was opeing any of the application including YAST and was showing error that no diskspace is available.
Suggestions
None

END