Is the nds.gwosc.org server down?

I am recieving the same error while fetching AUX channel data for O3a run through the gwpy’s Timeseries fetch function.

Error: no data received from nds.gwosc.org for [time segs]

I have tried different combinations of time segments, channels, internet providers and even laptops with no success.

1 Like

Thank you for letting us know. Indeed, the server was down, but it seems to be OK now.

1 Like

Thank you for the prompt update

1 Like

It seems to be a recurrent issue, I am once again getting the same error.
I am trying to fetch all aux channel data for O3a run channel by channel, I hope that is not causing this.

1 Like

Hello, thank you for posting this. Today I started having the same issue when trying to access data from the auxilary channells in the GW170814 Auxiliary Data Release. I have the same error

1 Like

Hi @Shan909 and @esocugalik ! Thank you for posting this. I will take a look at the NDS2 server. If you are trying to access a large amount of data, we recommend using OSDF instead. We have recently posted instructions for accessing these same data via OSDF. I would appreciate if you could try the new method, and send us any notes on if the instructions are easy to follow. OSDF is designed to work better for large data downloads than NDS2.

https://gwosc.org/osdf/

2 Likes

I restarted the NDS2 server and it seems to be working again. I am sorry for the problem.

2 Likes

Works now, thank you very much

1 Like

Thank you for looking into this. I had tried using the pelican pipeline before but it seemed a bit less documented compared to nds.
I will try again but in the meantime is there a limit to the segments/channels per week/month for the nds to not get overloaded? I can just limit my fetch code to certain segments at a time.
Thanks again

Hi, @jonah. I’m having a similar problem to this post when trying to execute the tutorials in gwosc / tutorials / Gwosc Aux Tutorials · GitLab, in particular, ‘data_access.ipynb’. Timeseries.fetch always returns “read_server_response: Wrong length read (0)”. The rest of the code works, returning channel availability. I have not tried the OSDF method yet.

Hi, I think the nds server keeps getting turned down quiet frequently. If you want to try the OSDF method, I have added a quick demo script here Review and sample for OSDF based data fetch
While OSDF does not work for aux channels as far as I know @jonah might be able to verify this but it works great for all other main strain data fetching.

1 Like

Hi @FabioNovaes . Thank you for flagging this. These repeated server failures are a problem. We need to create a monitor to reboot the server when needed, but we don’t have staff time for this at the moment. I am sorry for the inconvenience. I went ahead and rebooted the NDS server, and it should be working for now. I’d encourage you to try again.

Thank you very much, Jonah!

Thank you, I will take a look!

1 Like

Now it worked, thanks!

1 Like

Hi, I’m getting a timeout error when trying to access data from GW190521. I think it might be related to the server being down again, as I cannot access any page of the gwosc.org domain.

1 Like

Hi Serena, that’s correct, the system is offline, recovery work is being done at the moment and we’ll come back as soon as possible.

2 Likes

All systems should be up and running now.

2 Likes