Snap 520 probelm with edr interface

stokie · 03-18-2009, 05:37 AM

Hi Guys,

First time posting noob here so please be gentle

Stumbled across your forum and there seem to be some experts here!!

I've got 2 Snap 520's that are giving me grief!

To cut a long story short, the 2 devices were setup to replicate to each other and worked ok. Unfortunately one of them died and this happened just as overland took over the product. Eventually I had a replacement 520 which had the wrong memory and had to be replaced then I finally got my POP code reissued so that I could re-license my edr department licenses.

As they had been down for such a long time I decided to update the replacement and the offsite device to the latest OS (5.1.041) and latest EDR (7.2).

This was fine on the replacement unit but when it happened on the original it seemd to go ok but now when I click on Snap EDR under extras, I get the message

Error 503 Service Unavailable (in red)
Sorry, Unable to process request.

Has anyone else had that problem? I logged the call with overland a week ago and I'm still no closer to resolving.

I've sent them the syswrapper and edrlogs but the only thing it is showing is that the original device is still referencing the old device. Regardless of this, both devices can see each other in the snap finder utility.

Any suggestions appreciated.

Thx in advance.

Pete

blue68f100 · 03-18-2009, 08:16 AM

We have see this error before with the AV. What you need to do is uninstall the EDR. The addon screen may not work. You have to connect to the server as admin and have root access. Then you need to find the directory as to where it is located at. It took us some time on the AV to locate it. Once you find it you will find an un installer. The un installer will remove the installed files returning it back to factory status. Originally they were telling us to do clean install to corect the problem. Which we thought was crap.

The 803 will happend with the JVM script when it does not a running process.

I don't have the link on the AV, but if you were to search for it you could use it as a guide as to where to be looking. Once youhave located as to which directory you can send the cmd from debug insead of using puddy to gain root access.

stokie · 03-18-2009, 09:39 AM

Thx for that

They have replied today with...

ls /hd/vol_mnt*/SnapEDR -d

This will give you the patch where EDR is actually installed. (e. .g /hd/vol_mnt9/SnapEDR). This path varies from server to server.

When you have the path, launch this command:

/hd/vol_mnt[installed volume]/SnapEDR/BINARIES/bin/SIG-snap-configure.sh -u

Sound familiar?

Pete

03-18-2009, 05:37 AM	#1
stokie Cooling Neophyte Join Date: Mar 2009 Location: staffs Posts: 2	Snap 520 probelm with edr interface Hi Guys, First time posting noob here so please be gentle Stumbled across your forum and there seem to be some experts here!! I've got 2 Snap 520's that are giving me grief! To cut a long story short, the 2 devices were setup to replicate to each other and worked ok. Unfortunately one of them died and this happened just as overland took over the product. Eventually I had a replacement 520 which had the wrong memory and had to be replaced then I finally got my POP code reissued so that I could re-license my edr department licenses. As they had been down for such a long time I decided to update the replacement and the offsite device to the latest OS (5.1.041) and latest EDR (7.2). This was fine on the replacement unit but when it happened on the original it seemd to go ok but now when I click on Snap EDR under extras, I get the message Error 503 Service Unavailable (in red) Sorry, Unable to process request. Has anyone else had that problem? I logged the call with overland a week ago and I'm still no closer to resolving. I've sent them the syswrapper and edrlogs but the only thing it is showing is that the original device is still referencing the old device. Regardless of this, both devices can see each other in the snap finder utility. Any suggestions appreciated. Thx in advance. Pete

03-18-2009, 08:16 AM	#2
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: Snap 520 probelm with edr interface We have see this error before with the AV. What you need to do is uninstall the EDR. The addon screen may not work. You have to connect to the server as admin and have root access. Then you need to find the directory as to where it is located at. It took us some time on the AV to locate it. Once you find it you will find an un installer. The un installer will remove the installed files returning it back to factory status. Originally they were telling us to do clean install to corect the problem. Which we thought was crap. The 803 will happend with the JVM script when it does not a running process. I don't have the link on the AV, but if you were to search for it you could use it as a guide as to where to be looking. Once youhave located as to which directory you can send the cmd from debug insead of using puddy to gain root access. __________________ 1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820

03-18-2009, 09:39 AM	#3
stokie Cooling Neophyte Join Date: Mar 2009 Location: staffs Posts: 2	Re: Snap 520 probelm with edr interface Thx for that They have replied today with... ls /hd/vol_mnt*/SnapEDR -d This will give you the patch where EDR is actually installed. (e. .g /hd/vol_mnt9/SnapEDR). This path varies from server to server. When you have the path, launch this command: /hd/vol_mnt[installed volume]/SnapEDR/BINARIES/bin/SIG-snap-configure.sh -u Sound familiar? Pete

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)