cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1402
Views
0
Helpful
2
Replies

Errors on VSMS

ahmed_ellboudy
Level 1
Level 1

Dear All,

I have a system running 6.3 for all servers VSOM/VSMS and VSVM , the running IP cameras are Cisco 4300 .

till now I used only two VSMS to add the IP cameras on it ,the system running since the first of December 2010,and we adding cameras every day,

today we faced a problems on the two servers which reflects on the feeds of the cameras on the VSVM clients, the first server have a problem with Mideaout service as it is down and the attached files shows its problem ,the issue reflects on the feeds did not displayed on the VSVM client and gives us Endpoint error :<camera name >unreachable,I get the error on the image (VSMS error ) so I removed the VSMS package and install it again but the problem still exists and gives me on the same page under Mideaout ports ---> Http port :    , gives me error the port must be take value from [1,65365 ],also find attached the error I get on the ssh session regarding the Mideaout service ( error mediaout.txt).

The problem on the 2nd VSMS is the new added cameras today gives  Endpoint error:<camera name > unreachable ,the attached file show some errors of the new cameras from SYS log of the VSMS (10.30.30.29 logs.txt).

Also please find the error I get on the VSOM (VSOM.jpg) .

any idea to know the cause of these problems and how I solve it?

Thanks,

Ahmed Ellboudy

2 Replies 2

Scott Olsen
Level 6
Level 6

There certainly seems to be more than one issue going on here for sure.  Regarding the errors:

- "There are no valid partitions"; Have you experienced some form of disk subsystem failure on that server?  It seems to indicate the RAID sets / Repository volumes are not mounted / detected.  This is what I would consider a critical system problem.

- "Starting mediaout... done.
/usr/BWhttpd/bin/init_mediaout: line 85: [: 80: unary operator expected"; Someone (or something) has modified or changed this init script.  Basically it appears to be complaining of a scripting syntax error.  Honestly, I would considering taking your most recent (good!) backup and reinstalling the VSM suite on this server.

- "VSOM screenshot" ; From what I can see in your VSOM screenshot, It appears as though you have partial or NO access/communication with a majority of your VSMS servers.  Given what little I can gather from your description, this is either a substantial network issue (loss of connectivity), or your VSOM server is experiencing some significant issues when attempting to communicate with them.

I would recommend you open a TAC case.  Some of these issues seem quite significant.

Scott.

Scott Olsen Solutions Specialist Bulletproof Solutions Inc. Web: www.bulletproofsi.com

Hi Scoot,

This to inform you that the problem was in the Mideaout file on the VSMS and the problem solved after get this file from the backup created on the server and but it in the location of the damaged file .

Thanks,

Ahmed Ellboudy