Closed Kelvinrr closed 3 years ago
This issue has been up for a while and we haven't gotten any more posts about this, is this something that is still happening for folks? I've been running spiceinit over the web on Mac with dev builds and it hasn't happened for me, both on and off the DOI VPN.
If this is something you have run into recently please post on here with details about how to reproduce.
After restarting the server from #4384, it seems like this is cropping back up. Going to take some time to look into this.
I tried updating ISIS from 4.3 to 4.4, but the issue still remains. This is really a blocking issue, please provide some directions to skip it, thanks
@procton, you can download the spice kernels locally and skip using the SPICE server. See the installation instructions for information about installing the base area and whatever mission(s) you also require.
Yes, I am actually doing in this way, but it is an heavy download and the 'on demand' approach was very appreciated by the customer.
@procton :+1: We absolutely understand and are working to get the server back operating normally. Thank you for your patience and for using the work around in the meantime.
The problem seems solved, anyone can confirm the SPICE server is up and reliable ?
This was fixed by @acpaquette on issue #4356
Unfortunately my change did not fix this issue but the spiceserver should be working fine. We are currently using a 3.5.0 server and not the 4.2.0 server so this should not be an issue for users
I am currently using the 4.3 version and it seems fine
Yes, but the actual spiceserver that is currently deployed at the USGS is still using version 3.5.0 and the bad response still exists in 4.2.0 and greater versions. The server still works for the majority of ISIS releases that run spiceinit
with web=true
This issue has cropped again for me in the last day or so. I've been trying to process CTX images and I get
**ERROR** The server sent an unrecognized response.
after trying to run spiceinit web=yes
on the converted image cube.
I'm using the ISIS 3.5.1 build that is installed on Brown University's OSCAR computing cluster: https://docs.ccv.brown.edu/oscar/system-overview
Up until yesterday I'd been running spiceinit with the same specs and having no issues. Likewise, running spiceinit without web=yes works fine. The reason I need web=yes is to pull the kernels for the newest CTX images that aren't included in the local install.
Full print.prt file: print.prt.txt
I have been running into the same issue since yesterday when processing LRO NAC images with ISIS 5.0.1. Running spiceinit web=true
on my cube I get the same error **ERROR** The server sent an unrecognized response.
.
Here is my print.prt file: print.prt.txt
It seems the server just started returning empty responses regardless of the POST request sent, probably not an issue with a change in code and maybe something with the server itself.
Looking into it.
Alright, looks like the issue was server related, after changing some configs and a reset it should be back up.
@bboatwright @matthutt give it another shot and let me know if you still get the error.
No more error when I try again now. Thank you @Kelvinrr!
Works now for me as well, thanks!
Hi folks, the same issue has just happened to me with LRO NAC images using web=yes. ERROR The server sent an unrecognized response [3c73706963655f646174613e0a20203c61707.......
I have not seen a definite answer but is this a spice server issue which requires just some patience?
Also, does anyone know how large disk space is needed to download the whole LRO kernels? I only have about 10 GB space locally...
Many thanks!
@taoyu17, I have just tried it and spiceinit web=true
is working fine for me with NAC images. I hope that this gets resolved for you, though.
rsync --dry-run --stats
tells me the LRO kernels are 260GB (but it says the data for all missions is 793GB, and the ISIS docs say 520GB, so maybe 170GB is more accurate for LRO?). I have not performed this download myself (I am likewise subject to disc space restrictions) so this could be wildly wrong and I would like to know the answer too.
@matthutt Thanks a lot! Yeah spiceinit is now working again this morning so there was a server issue I believe. Thank you so much also for the command to calculate the downloadable size!
Hi, I've been having the same issue here. I am using ISIS=8.0.1, trying to process HiRISE images.
Whenever I try to run spiceinit on the converted cube image (web=yes, ckpredicted=yes), I recieve the error message:
ERROR The server sent an unrecognized response.
[Full print.prt attached]
Please let me know if there is something I am needing to do to correct this!
Hello, I am have the same issue as well when processing LRO NAC images. I am using ISIS version 7.0.0 and my command is:
spiceinit from= M110296979LE.cub web= true
the error I receive is:
**ERROR** The server sent an unrecognized response.
My print.prt is attached. print.prt.txt
Same here as of yesterday, also with NAC.
Spice server is down, try the newer URL: https://astrogeology.usgs.gov/apis/ale/v0.9.1/spiceserver/
IT is aware that the default server is down.
Thank you!
Heather
From: Kelvin Rodriguez @.> Sent: Thursday, December 21, 2023 3:13 PM To: DOI-USGS/ISIS3 @.> Cc: Lethcoe, Heather A (US 398N) @.>; Comment @.> Subject: [EXTERNAL] Re: [DOI-USGS/ISIS3] ISIS Spice Server returning incomplete responses on 4.2.0 (#4044)
Spice server is down, try the newer URL: https://astrogeology.usgs.gov/apis/ale/v0.9.1/spiceserver/https://urldefense.us/v3/__https:/astrogeology.usgs.gov/apis/ale/v0.9.1/spiceserver/__;!!PvBDto6Hs4WbVuu7!MqEsipOmBPdlft_-HEHtp3zFvv3Ddhn_QtGKZ023fRqB10CLMneZU88Rmxj1W8WOnJod9-shhCAOxVGyUmlmaZvxbjclUHISo5s$
IT is aware that the default server is down.
— Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https:/github.com/DOI-USGS/ISIS3/issues/4044*issuecomment-1867040097__;Iw!!PvBDto6Hs4WbVuu7!MqEsipOmBPdlft_-HEHtp3zFvv3Ddhn_QtGKZ023fRqB10CLMneZU88Rmxj1W8WOnJod9-shhCAOxVGyUmlmaZvxbjclfEeSK7Q$, or unsubscribehttps://urldefense.us/v3/__https:/github.com/notifications/unsubscribe-auth/BERAERRIXW2K5Z5Z3RF6KNLYKS7BLAVCNFSM4R6TJYIKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBWG4YDIMBQHE3Q__;!!PvBDto6Hs4WbVuu7!MqEsipOmBPdlft_-HEHtp3zFvv3Ddhn_QtGKZ023fRqB10CLMneZU88Rmxj1W8WOnJod9-shhCAOxVGyUmlmaZvxbjclUgcLYlM$. You are receiving this because you commented.Message ID: @.**@.>>
Default server should be back up now.
Hello,
I've been having trouble processing NAC images with spiceinit and web=yes, just as above comments. I've attached print.prt. print_prt.txt
appreciate any help I can get.
Hey @NatalieGallegos , we've had a lot of trouble with the spice server going down, and we've migrated the web service. The latest version of ISIS should default to the new server, but you can use the new server in older versions of ISIS by adding url=https://astrogeology.usgs.gov/apis/ale/v0.9.1/spiceserver/
to your spiceinit call.
@AustinSanders This works - thank you!
I apologize for opening this ticket again, but I am running into a similar issue and can't seem to find a way around it.
I've tried changing the url to the new server (as suggested in the documentation and in the above response from @AustinSanders ), but I receive ERROR An error occurred when talking to the server. The server encountered an unexpected error.
spiceinit from=/d0/marstherm/web_output/themis/MT_THEMIS_I80048017_11279/I80048017RDRa.cub url=https://astrogeology.usgs.gov/apis/ale/v0.9.1/spiceserver/ web=True
I am the Systems Manager for MARSTHERM (https://marstherm.psi.edu), which regularly uses ISIS functions for THEMIS processing. We are currently running IsisVersion 3.5.2.0.
I've included my print.prt file for reference.
Hey @mr-perry, it looks like the web service is up and running; do you mind linking to the data (.cub) you're using so that I can do some testing on my end?
ISIS 3.5.2.0 is considered a legacy version of ISIS, and it is no longer officially supported. Since this is not a supported version, I plan to perform testing on a later version of ISIS (v8.3.0).
ISIS version(s) affected: 4.x.x
Description
When using spiceinit with web=yes, the spice server sometimes gives a partial response.
How to reproduce
Run spiceinit with web=yes, it doesn't seem to matter what cube you use.
Note, the large block is the response from the server which is an XML string in HEX form .
Converting it back to ASCII:
The response is expected to be formatted more like:
Clearly, not all the data is getting across the wire, therefore triggering the unknown response error (which is a catchall parsing error).
This at least occurs when using ISIS 4.2.0 on the spice server.
Possible Solution
Currently, my hunch is this is a server issue as it started when the spice server's ISIS install switched to 4.2.0. Testing the Perl script might give some hints as to what is happening.
Additional context
The spice server is on the internal machine
isis-spice-d
and the Perl scripts are atisis-spice-d:/var/www/cgi-bin/isis/spiceinit.cgi
ISIS install is at
/work1/work2/isis3/isis
/work1/work2/isis3/isis4.2.0
contains a full ISIS4.2.0 install.