search

glos / myglos

Repository for MyGLOS (GLOS Data Portal)
GNU General Public License v3.0
2 stars 2 forks source link

Missing *_20170608.nc files? #129

Closed tslawecki closed 7 years ago

tslawecki commented 7 years ago

As noted to dmac@glos.us, the Buoy Portal is showing many out-of-date stations. Checking, I saw that (e.g.) there is no 45023_20170608.nc file for today's observations, though the Data Portal shows 8 AM observations. I did do a quick check - there is still disk space on the thredds server and the NAS. @kknee , I'm thinking this is for @cheryldmorse to check into?

cheryldmorse commented 7 years ago

This was an issue with storage.glos.us not accepting incoming connections. A reboot solved the issue.

everhamme commented 7 years ago

Any idea if this might be a recurring issue? Do we have any checks in place to actively notify us of issues other than waiting for a user to notify?

From: cheryldmorse [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 12:39 PM To: glos/myglos myglos@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

This was an issue with storage.glos.us not accepting incoming connections. A reboot solved the issue.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307159489, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGlVKkF_6cY62xDoAC364QQQfK_0Jks5sCCO5gaJpZM4Nz-qe.

kknee commented 7 years ago

We can set up a daily report on the latest files and highlight those that are more than xx hours old. Probably a couple of days of effort to setup. Let me know if we should proceed.

From: Ed Verhamme [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 1:00 PM To: glos/myglos myglos@noreply.github.com Cc: Kelly Knee Kelly.Knee@rpsgroup.com; Mention mention@noreply.github.com Subject: [EXT] Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Any idea if this might be a recurring issue? Do we have any checks in place to actively notify us of issues other than waiting for a user to notify?

From: cheryldmorse [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 12:39 PM To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com> Cc: Subscribed subscribed@noreply.github.com<mailto:subscribed@noreply.github.com> Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

This was an issue with storage.glos.us not accepting incoming connections. A reboot solved the issue.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307159489, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGlVKkF_6cY62xDoAC364QQQfK_0Jks5sCCO5gaJpZM4Nz-qe.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307164825, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAMBBBP-61HHs51uSexG2REFVRyIn8wsks5sCCiTgaJpZM4Nz-qe.

This e-mail message and any attached file is the property of the sender and is sent in confidence to the addressee only.

Internet communications are not secure and RPS is not responsible for their abuse by third parties, any alteration or corruption in transmission or for any loss or damage caused by a virus or by any other means.

RPS Group Plc, company number: 208 7786 (England). Registered office: 20 Western Avenue Milton Park Abingdon Oxfordshire OX14 4SH.

RPS Group Plc web link: http://www.rpsgroup.comhttp://www.rpsgroup.com/

everhamme commented 7 years ago

Greg has a similar automated email report setup for the old gl buoys. I'm sure he could adapt with very little effort.

Greg can respond?

Ed Verhamme Project Engineer LimnoTech www.limno.com Ph: (734) 332-1200<tel:(734)%20332-1200> Direct/Cell: (734) 681-0577<tel:(734)%20681-0577> everhamme@limno.commailto:everhamme@limno.com

-------- Original message -------- From: Kelly Knee notifications@github.com Date: 6/9/17 6:51 AM (GMT-05:00) To: glos/myglos myglos@noreply.github.com Cc: Ed Verhamme everhamme@limno.com, Comment comment@noreply.github.com Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

We can set up a daily report on the latest files and highlight those that are more than xx hours old. Probably a couple of days of effort to setup. Let me know if we should proceed.

From: Ed Verhamme [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 1:00 PM To: glos/myglos myglos@noreply.github.com Cc: Kelly Knee Kelly.Knee@rpsgroup.com; Mention mention@noreply.github.com Subject: [EXT] Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Any idea if this might be a recurring issue? Do we have any checks in place to actively notify us of issues other than waiting for a user to notify?

From: cheryldmorse [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 12:39 PM To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com> Cc: Subscribed subscribed@noreply.github.com<mailto:subscribed@noreply.github.com> Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

This was an issue with storage.glos.us not accepting incoming connections. A reboot solved the issue.

- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307159489, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGlVKkF_6cY62xDoAC364QQQfK_0Jks5sCCO5gaJpZM4Nz-qe.

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307164825, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAMBBBP-61HHs51uSexG2REFVRyIn8wsks5sCCiTgaJpZM4Nz-qe.

This e-mail message and any attached file is the property of the sender and is sent in confidence to the addressee only.

Internet communications are not secure and RPS is not responsible for their abuse by third parties, any alteration or corruption in transmission or for any loss or damage caused by a virus or by any other means.

RPS Group Plc, company number: 208 7786 (England). Registered office: 20 Western Avenue Milton Park Abingdon Oxfordshire OX14 4SH.

RPS Group Plc web link: http://www.rpsgroup.comhttp://www.rpsgroup.com/

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307358698, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGngYMi2N1tTa2d3-9KcjDGT2jVaEks5sCSPHgaJpZM4Nz-qe.

tslawecki commented 7 years ago

I think that this is a different type of fault ... what we need is an alert that the ssh is not working.

From: Ed Verhamme notifications@github.com Sent: Friday, June 9, 2017 7:21 AM To: glos/myglos Cc: Tad Slawecki; Author Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Greg has a similar automated email report setup for the old gl buoys. I'm sure he could adapt with very little effort.

Greg can respond?

Ed Verhamme Project Engineer LimnoTech www.limno.com Ph: (734) 332-1200<tel:(734)%20332-1200> Direct/Cell: (734) 681-0577<tel:(734)%20681-0577> everhamme@limno.commailto:everhamme@limno.com

-------- Original message -------- From: Kelly Knee notifications@github.com Date: 6/9/17 6:51 AM (GMT-05:00) To: glos/myglos myglos@noreply.github.com Cc: Ed Verhamme everhamme@limno.com, Comment comment@noreply.github.com Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

We can set up a daily report on the latest files and highlight those that are more than xx hours old. Probably a couple of days of effort to setup. Let me know if we should proceed.

From: Ed Verhamme [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 1:00 PM To: glos/myglos myglos@noreply.github.com Cc: Kelly Knee Kelly.Knee@rpsgroup.com; Mention mention@noreply.github.com Subject: [EXT] Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Any idea if this might be a recurring issue? Do we have any checks in place to actively notify us of issues other than waiting for a user to notify?

From: cheryldmorse [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 12:39 PM To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com> Cc: Subscribed subscribed@noreply.github.com<mailto:subscribed@noreply.github.com> Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

This was an issue with storage.glos.us not accepting incoming connections. A reboot solved the issue.

- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307159489, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGlVKkF_6cY62xDoAC364QQQfK_0Jks5sCCO5gaJpZM4Nz-qe.

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307164825, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAMBBBP-61HHs51uSexG2REFVRyIn8wsks5sCCiTgaJpZM4Nz-qe.

This e-mail message and any attached file is the property of the sender and is sent in confidence to the addressee only.

Internet communications are not secure and RPS is not responsible for their abuse by third parties, any alteration or corruption in transmission or for any loss or damage caused by a virus or by any other means.

RPS Group Plc, company number: 208 7786 (England). Registered office: 20 Western Avenue Milton Park Abingdon Oxfordshire OX14 4SH.

RPS Group Plc web link: http://www.rpsgroup.comhttp://www.rpsgroup.com/

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307358698, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGngYMi2N1tTa2d3-9KcjDGT2jVaEks5sCSPHgaJpZM4Nz-qe.

- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307363746, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE-3PhrYkX7Q5oW1z97mgZzsCrKzE8AGks5sCSrAgaJpZM4Nz-qe.

everhamme commented 7 years ago

A check on the glbuoys.glos.us timestamps per buoy would catch a host of problems.

Ed Verhamme Project Engineer LimnoTech www.limno.com Ph: (734) 332-1200<tel:(734)%20332-1200> Direct/Cell: (734) 681-0577<tel:(734)%20681-0577> everhamme@limno.commailto:everhamme@limno.com

-------- Original message -------- From: Tad Slawecki notifications@github.com Date: 6/9/17 7:35 AM (GMT-05:00) To: glos/myglos myglos@noreply.github.com Cc: Ed Verhamme everhamme@limno.com, Comment comment@noreply.github.com Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

I think that this is a different type of fault ... what we need is an alert that the ssh is not working.

From: Ed Verhamme notifications@github.com Sent: Friday, June 9, 2017 7:21 AM To: glos/myglos Cc: Tad Slawecki; Author Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Greg has a similar automated email report setup for the old gl buoys. I'm sure he could adapt with very little effort.

Greg can respond?

Ed Verhamme Project Engineer LimnoTech www.limno.com Ph: (734) 332-1200<tel:(734)%20332-1200> Direct/Cell: (734) 681-0577<tel:(734)%20681-0577> everhamme@limno.commailto:everhamme@limno.com

-------- Original message -------- From: Kelly Knee notifications@github.com Date: 6/9/17 6:51 AM (GMT-05:00) To: glos/myglos myglos@noreply.github.com Cc: Ed Verhamme everhamme@limno.com, Comment comment@noreply.github.com Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

We can set up a daily report on the latest files and highlight those that are more than xx hours old. Probably a couple of days of effort to setup. Let me know if we should proceed.

From: Ed Verhamme [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 1:00 PM To: glos/myglos myglos@noreply.github.com Cc: Kelly Knee Kelly.Knee@rpsgroup.com; Mention mention@noreply.github.com Subject: [EXT] Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Any idea if this might be a recurring issue? Do we have any checks in place to actively notify us of issues other than waiting for a user to notify?

From: cheryldmorse [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 12:39 PM To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com> Cc: Subscribed subscribed@noreply.github.com<mailto:subscribed@noreply.github.com> Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

This was an issue with storage.glos.us not accepting incoming connections. A reboot solved the issue.

- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307159489, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGlVKkF_6cY62xDoAC364QQQfK_0Jks5sCCO5gaJpZM4Nz-qe.

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307164825, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAMBBBP-61HHs51uSexG2REFVRyIn8wsks5sCCiTgaJpZM4Nz-qe.

This e-mail message and any attached file is the property of the sender and is sent in confidence to the addressee only.

Internet communications are not secure and RPS is not responsible for their abuse by third parties, any alteration or corruption in transmission or for any loss or damage caused by a virus or by any other means.

RPS Group Plc, company number: 208 7786 (England). Registered office: 20 Western Avenue Milton Park Abingdon Oxfordshire OX14 4SH.

RPS Group Plc web link: http://www.rpsgroup.comhttp://www.rpsgroup.com/

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307358698, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGngYMi2N1tTa2d3-9KcjDGT2jVaEks5sCSPHgaJpZM4Nz-qe.

- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307363746, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE-3PhrYkX7Q5oW1z97mgZzsCrKzE8AGks5sCSrAgaJpZM4Nz-qe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307366027, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGqJHji3QNc3vZiM3uCz6WB0ckNyYks5sCS4AgaJpZM4Nz-qe.

kknee commented 7 years ago

Agree – first step is to be alerted that they are not current, then we can work out why.

From: Ed Verhamme [mailto:notifications@github.com] Sent: Friday, June 9, 2017 7:37 AM To: glos/myglos myglos@noreply.github.com Cc: Kelly Knee Kelly.Knee@rpsgroup.com; Mention mention@noreply.github.com Subject: [EXT] Re: [glos/myglos] Missing *_20170608.nc files? (#129)

A check on the glbuoys.glos.us timestamps per buoy would catch a host of problems.

Ed Verhamme Project Engineer LimnoTech www.limno.comhttp://www.limno.com Ph: (734) 332-1200<tel:(734)%20332-1200> Direct/Cell: (734) 681-0577<tel:(734)%20681-0577> everhamme@limno.commailto:everhamme@limno.com<mailto:everhamme@limno.com%3cmailto:everhamme@limno.com>

-------- Original message -------- From: Tad Slawecki notifications@github.com<mailto:notifications@github.com> Date: 6/9/17 7:35 AM (GMT-05:00) To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com> Cc: Ed Verhamme everhamme@limno.com<mailto:everhamme@limno.com>, Comment comment@noreply.github.com<mailto:comment@noreply.github.com> Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

I think that this is a different type of fault ... what we need is an alert that the ssh is not working.

From: Ed Verhamme notifications@github.com<mailto:notifications@github.com> Sent: Friday, June 9, 2017 7:21 AM To: glos/myglos Cc: Tad Slawecki; Author Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Greg has a similar automated email report setup for the old gl buoys. I'm sure he could adapt with very little effort.

Greg can respond?

Ed Verhamme Project Engineer LimnoTech www.limno.comhttp://www.limno.com Ph: (734) 332-1200<tel:(734)%20332-1200> Direct/Cell: (734) 681-0577<tel:(734)%20681-0577> everhamme@limno.commailto:everhamme@limno.com<mailto:everhamme@limno.com%3cmailto:everhamme@limno.com>

-------- Original message -------- From: Kelly Knee notifications@github.com<mailto:notifications@github.com> Date: 6/9/17 6:51 AM (GMT-05:00) To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com> Cc: Ed Verhamme everhamme@limno.com<mailto:everhamme@limno.com>, Comment comment@noreply.github.com<mailto:comment@noreply.github.com> Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

We can set up a daily report on the latest files and highlight those that are more than xx hours old. Probably a couple of days of effort to setup. Let me know if we should proceed.

From: Ed Verhamme [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 1:00 PM To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com> Cc: Kelly Knee Kelly.Knee@rpsgroup.com<mailto:Kelly.Knee@rpsgroup.com>; Mention mention@noreply.github.com<mailto:mention@noreply.github.com> Subject: [EXT] Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Any idea if this might be a recurring issue? Do we have any checks in place to actively notify us of issues other than waiting for a user to notify?

From: cheryldmorse [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 12:39 PM To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com<mailto:myglos@noreply.github.com%3cmailto:myglos@noreply.github.com>> Cc: Subscribed subscribed@noreply.github.com<mailto:subscribed@noreply.github.com<mailto:subscribed@noreply.github.com%3cmailto:subscribed@noreply.github.com>> Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

This was an issue with storage.glos.us not accepting incoming connections. A reboot solved the issue.

- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307159489, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGlVKkF_6cY62xDoAC364QQQfK_0Jks5sCCO5gaJpZM4Nz-qe.

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307164825, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAMBBBP-61HHs51uSexG2REFVRyIn8wsks5sCCiTgaJpZM4Nz-qe.

This e-mail message and any attached file is the property of the sender and is sent in confidence to the addressee only.

Internet communications are not secure and RPS is not responsible for their abuse by third parties, any alteration or corruption in transmission or for any loss or damage caused by a virus or by any other means.

RPS Group Plc, company number: 208 7786 (England). Registered office: 20 Western Avenue Milton Park Abingdon Oxfordshire OX14 4SH.

RPS Group Plc web link: http://www.rpsgroup.comhttp://www.rpsgroup.com/<http://www.rpsgroup.com%3chttp:/www.rpsgroup.com/>

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307358698, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGngYMi2N1tTa2d3-9KcjDGT2jVaEks5sCSPHgaJpZM4Nz-qe.

- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307363746, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE-3PhrYkX7Q5oW1z97mgZzsCrKzE8AGks5sCSrAgaJpZM4Nz-qe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307366027, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGqJHji3QNc3vZiM3uCz6WB0ckNyYks5sCS4AgaJpZM4Nz-qe.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307366314, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAMBBPq8lKYMxlgyGJUKmT_pmtFn_udRks5sCS5ygaJpZM4Nz-qe.

This e-mail message and any attached file is the property of the sender and is sent in confidence to the addressee only.

Internet communications are not secure and RPS is not responsible for their abuse by third parties, any alteration or corruption in transmission or for any loss or damage caused by a virus or by any other means.

RPS Group Plc, company number: 208 7786 (England). Registered office: 20 Western Avenue Milton Park Abingdon Oxfordshire OX14 4SH.

RPS Group Plc web link: http://www.rpsgroup.comhttp://www.rpsgroup.com/

tslawecki commented 7 years ago

Btw something's off again in case anyone is anle to check. -------- Original message -------- From: Kelly Knee notifications@github.com Date: 6/9/17 8:00 AM (GMT-05:00) To: glos/myglos myglos@noreply.github.com Cc: Tad Slawecki tslawecki@limno.com, Author author@noreply.github.com Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Agree – first step is to be alerted that they are not current, then we can work out why.

From: Ed Verhamme [mailto:notifications@github.com] Sent: Friday, June 9, 2017 7:37 AM To: glos/myglos myglos@noreply.github.com Cc: Kelly Knee Kelly.Knee@rpsgroup.com; Mention mention@noreply.github.com Subject: [EXT] Re: [glos/myglos] Missing *_20170608.nc files? (#129)

A check on the glbuoys.glos.us timestamps per buoy would catch a host of problems.

Ed Verhamme Project Engineer LimnoTech www.limno.comhttp://www.limno.com Ph: (734) 332-1200<tel:(734)%20332-1200> Direct/Cell: (734) 681-0577<tel:(734)%20681-0577> everhamme@limno.commailto:everhamme@limno.com<mailto:everhamme@limno.com%3cmailto:everhamme@limno.com>

-------- Original message -------- From: Tad Slawecki notifications@github.com<mailto:notifications@github.com> Date: 6/9/17 7:35 AM (GMT-05:00) To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com> Cc: Ed Verhamme everhamme@limno.com<mailto:everhamme@limno.com>, Comment comment@noreply.github.com<mailto:comment@noreply.github.com> Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

I think that this is a different type of fault ... what we need is an alert that the ssh is not working.

From: Ed Verhamme notifications@github.com<mailto:notifications@github.com> Sent: Friday, June 9, 2017 7:21 AM To: glos/myglos Cc: Tad Slawecki; Author Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Greg has a similar automated email report setup for the old gl buoys. I'm sure he could adapt with very little effort.

Greg can respond?

Ed Verhamme Project Engineer LimnoTech www.limno.comhttp://www.limno.com Ph: (734) 332-1200<tel:(734)%20332-1200> Direct/Cell: (734) 681-0577<tel:(734)%20681-0577> everhamme@limno.commailto:everhamme@limno.com<mailto:everhamme@limno.com%3cmailto:everhamme@limno.com>

-------- Original message -------- From: Kelly Knee notifications@github.com<mailto:notifications@github.com> Date: 6/9/17 6:51 AM (GMT-05:00) To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com> Cc: Ed Verhamme everhamme@limno.com<mailto:everhamme@limno.com>, Comment comment@noreply.github.com<mailto:comment@noreply.github.com> Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

We can set up a daily report on the latest files and highlight those that are more than xx hours old. Probably a couple of days of effort to setup. Let me know if we should proceed.

From: Ed Verhamme [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 1:00 PM To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com> Cc: Kelly Knee Kelly.Knee@rpsgroup.com<mailto:Kelly.Knee@rpsgroup.com>; Mention mention@noreply.github.com<mailto:mention@noreply.github.com> Subject: [EXT] Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Any idea if this might be a recurring issue? Do we have any checks in place to actively notify us of issues other than waiting for a user to notify?

From: cheryldmorse [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 12:39 PM To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com<mailto:myglos@noreply.github.com%3cmailto:myglos@noreply.github.com>> Cc: Subscribed subscribed@noreply.github.com<mailto:subscribed@noreply.github.com<mailto:subscribed@noreply.github.com%3cmailto:subscribed@noreply.github.com>> Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

This was an issue with storage.glos.us not accepting incoming connections. A reboot solved the issue.

- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307159489, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGlVKkF_6cY62xDoAC364QQQfK_0Jks5sCCO5gaJpZM4Nz-qe.

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307164825, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAMBBBP-61HHs51uSexG2REFVRyIn8wsks5sCCiTgaJpZM4Nz-qe.

This e-mail message and any attached file is the property of the sender and is sent in confidence to the addressee only.

Internet communications are not secure and RPS is not responsible for their abuse by third parties, any alteration or corruption in transmission or for any loss or damage caused by a virus or by any other means.

RPS Group Plc, company number: 208 7786 (England). Registered office: 20 Western Avenue Milton Park Abingdon Oxfordshire OX14 4SH.

RPS Group Plc web link: http://www.rpsgroup.comhttp://www.rpsgroup.com/<http://www.rpsgroup.com%3chttp:/www.rpsgroup.com/>

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307358698, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGngYMi2N1tTa2d3-9KcjDGT2jVaEks5sCSPHgaJpZM4Nz-qe.

- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307363746, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE-3PhrYkX7Q5oW1z97mgZzsCrKzE8AGks5sCSrAgaJpZM4Nz-qe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307366027, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGqJHji3QNc3vZiM3uCz6WB0ckNyYks5sCS4AgaJpZM4Nz-qe.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307366314, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAMBBPq8lKYMxlgyGJUKmT_pmtFn_udRks5sCS5ygaJpZM4Nz-qe.

This e-mail message and any attached file is the property of the sender and is sent in confidence to the addressee only.

Internet communications are not secure and RPS is not responsible for their abuse by third parties, any alteration or corruption in transmission or for any loss or damage caused by a virus or by any other means.

RPS Group Plc, company number: 208 7786 (England). Registered office: 20 Western Avenue Milton Park Abingdon Oxfordshire OX14 4SH.

RPS Group Plc web link: http://www.rpsgroup.comhttp://www.rpsgroup.com/

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307370333, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE-3PmFxIVPgKQ1-TlJCdxMAFiPuxSN5ks5sCTPVgaJpZM4Nz-qe.

everhamme commented 7 years ago

Many many stations aren't current as of now

Ed Verhamme Project Engineer LimnoTech www.limno.com Ph: (734) 332-1200<tel:(734)%20332-1200> Direct/Cell: (734) 681-0577<tel:(734)%20681-0577> everhamme@limno.commailto:everhamme@limno.com

-------- Original message -------- From: Tad Slawecki notifications@github.com Date: 6/10/17 8:32 PM (GMT-05:00) To: glos/myglos myglos@noreply.github.com Cc: Ed Verhamme everhamme@limno.com, Comment comment@noreply.github.com Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Btw something's off again in case anyone is anle to check. -------- Original message -------- From: Kelly Knee notifications@github.com Date: 6/9/17 8:00 AM (GMT-05:00) To: glos/myglos myglos@noreply.github.com Cc: Tad Slawecki tslawecki@limno.com, Author author@noreply.github.com Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Agree – first step is to be alerted that they are not current, then we can work out why.

From: Ed Verhamme [mailto:notifications@github.com] Sent: Friday, June 9, 2017 7:37 AM To: glos/myglos myglos@noreply.github.com Cc: Kelly Knee Kelly.Knee@rpsgroup.com; Mention mention@noreply.github.com Subject: [EXT] Re: [glos/myglos] Missing *_20170608.nc files? (#129)

A check on the glbuoys.glos.us timestamps per buoy would catch a host of problems.

Ed Verhamme Project Engineer LimnoTech www.limno.comhttp://www.limno.com Ph: (734) 332-1200<tel:(734)%20332-1200> Direct/Cell: (734) 681-0577<tel:(734)%20681-0577> everhamme@limno.commailto:everhamme@limno.com<mailto:everhamme@limno.com%3cmailto:everhamme@limno.com>

-------- Original message -------- From: Tad Slawecki notifications@github.com<mailto:notifications@github.com> Date: 6/9/17 7:35 AM (GMT-05:00) To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com> Cc: Ed Verhamme everhamme@limno.com<mailto:everhamme@limno.com>, Comment comment@noreply.github.com<mailto:comment@noreply.github.com> Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

I think that this is a different type of fault ... what we need is an alert that the ssh is not working.

From: Ed Verhamme notifications@github.com<mailto:notifications@github.com> Sent: Friday, June 9, 2017 7:21 AM To: glos/myglos Cc: Tad Slawecki; Author Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Greg has a similar automated email report setup for the old gl buoys. I'm sure he could adapt with very little effort.

Greg can respond?

Ed Verhamme Project Engineer LimnoTech www.limno.comhttp://www.limno.com Ph: (734) 332-1200<tel:(734)%20332-1200> Direct/Cell: (734) 681-0577<tel:(734)%20681-0577> everhamme@limno.commailto:everhamme@limno.com<mailto:everhamme@limno.com%3cmailto:everhamme@limno.com>

-------- Original message -------- From: Kelly Knee notifications@github.com<mailto:notifications@github.com> Date: 6/9/17 6:51 AM (GMT-05:00) To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com> Cc: Ed Verhamme everhamme@limno.com<mailto:everhamme@limno.com>, Comment comment@noreply.github.com<mailto:comment@noreply.github.com> Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

We can set up a daily report on the latest files and highlight those that are more than xx hours old. Probably a couple of days of effort to setup. Let me know if we should proceed.

From: Ed Verhamme [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 1:00 PM To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com> Cc: Kelly Knee Kelly.Knee@rpsgroup.com<mailto:Kelly.Knee@rpsgroup.com>; Mention mention@noreply.github.com<mailto:mention@noreply.github.com> Subject: [EXT] Re: [glos/myglos] Missing *_20170608.nc files? (#129)

Any idea if this might be a recurring issue? Do we have any checks in place to actively notify us of issues other than waiting for a user to notify?

From: cheryldmorse [mailto:notifications@github.com] Sent: Thursday, June 8, 2017 12:39 PM To: glos/myglos myglos@noreply.github.com<mailto:myglos@noreply.github.com<mailto:myglos@noreply.github.com%3cmailto:myglos@noreply.github.com>> Cc: Subscribed subscribed@noreply.github.com<mailto:subscribed@noreply.github.com<mailto:subscribed@noreply.github.com%3cmailto:subscribed@noreply.github.com>> Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

This was an issue with storage.glos.us not accepting incoming connections. A reboot solved the issue.

- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307159489, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGlVKkF_6cY62xDoAC364QQQfK_0Jks5sCCO5gaJpZM4Nz-qe.

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307164825, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAMBBBP-61HHs51uSexG2REFVRyIn8wsks5sCCiTgaJpZM4Nz-qe.

This e-mail message and any attached file is the property of the sender and is sent in confidence to the addressee only.

Internet communications are not secure and RPS is not responsible for their abuse by third parties, any alteration or corruption in transmission or for any loss or damage caused by a virus or by any other means.

RPS Group Plc, company number: 208 7786 (England). Registered office: 20 Western Avenue Milton Park Abingdon Oxfordshire OX14 4SH.

RPS Group Plc web link: http://www.rpsgroup.comhttp://www.rpsgroup.com/<http://www.rpsgroup.com%3chttp:/www.rpsgroup.com/>

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307358698, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGngYMi2N1tTa2d3-9KcjDGT2jVaEks5sCSPHgaJpZM4Nz-qe.

- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307363746, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE-3PhrYkX7Q5oW1z97mgZzsCrKzE8AGks5sCSrAgaJpZM4Nz-qe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307366027, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGqJHji3QNc3vZiM3uCz6WB0ckNyYks5sCS4AgaJpZM4Nz-qe.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307366314, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAMBBPq8lKYMxlgyGJUKmT_pmtFn_udRks5sCS5ygaJpZM4Nz-qe.

This e-mail message and any attached file is the property of the sender and is sent in confidence to the addressee only.

Internet communications are not secure and RPS is not responsible for their abuse by third parties, any alteration or corruption in transmission or for any loss or damage caused by a virus or by any other means.

RPS Group Plc, company number: 208 7786 (England). Registered office: 20 Western Avenue Milton Park Abingdon Oxfordshire OX14 4SH.

RPS Group Plc web link: http://www.rpsgroup.comhttp://www.rpsgroup.com/

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307370333, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE-3PmFxIVPgKQ1-TlJCdxMAFiPuxSN5ks5sCTPVgaJpZM4Nz-qe.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-307598214, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGigLSoCJnb-dMNcemCFTmDiYHV7oks5sCzV2gaJpZM4Nz-qe.

kknee commented 7 years ago

@everhamme aren't current where? Spot checked portal and TDS and am seeing 6/13/17 data in both places.

tslawecki commented 7 years ago

http://glbuoys.glos.us ...

From: Kelly Knee notifications@github.com Sent: Tuesday, June 13, 2017 8:09 AM To: glos/myglos Cc: Tad Slawecki; Author Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

@everhammehttps://github.com/everhamme aren't current where? Spot checked portal and TDS and am seeing 6/13/17 data in both places.

- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-308095643, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE-3PlJnmbGHceYWtVGq1Zfaev-Y9f1Nks5sDnvigaJpZM4Nz-qe.

tslawecki commented 7 years ago

Two examples:

45028 is > 6 hours old, but that's consistent with data.glos.us/status, which suggests UMnD is having some sort of problem, so maybe this is all right.

45001 is also outdated, but it's more problematic: I can't get to 45001 (NDBC) in portal.glos.us at all. NBDC link shows it as current, so two problems here:

From: Tad Slawecki Sent: Tuesday, June 13, 2017 8:15 AM To: glos/myglos; glos/myglos Cc: Author; Greg Cutrell Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

http://glbuoys.glos.us ...

From: Kelly Knee notifications@github.com Sent: Tuesday, June 13, 2017 8:09 AM To: glos/myglos Cc: Tad Slawecki; Author Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

@everhammehttps://github.com/everhamme aren't current where? Spot checked portal and TDS and am seeing 6/13/17 data in both places.

- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-308095643, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE-3PlJnmbGHceYWtVGq1Zfaev-Y9f1Nks5sDnvigaJpZM4Nz-qe.

kknee commented 7 years ago

taking 45176 as an example- same deal, data is more than 6 hours old but that is consistent in the portal and TDS.

For 45001 we may need to update the NDBC buoy collection layer

tslawecki commented 7 years ago

NDBC is an existing issue - I'm surprised it's still open ... https://github.com/glos/myglos/issues/125

Is this a Kathy or RPS issue?

From: Kelly Knee notifications@github.com Sent: Tuesday, June 13, 2017 8:27 AM To: glos/myglos Cc: Tad Slawecki; Author Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

taking 45176 as an example- same deal, data is more than 6 hours old but that is consistent in the portal and TDS.

For 45001 we may need to update the NDBC buoy collection layer

- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-308099706, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE-3Pve_fAxdDMrZ3RmqN5mnJpsYLQcCks5sDoAigaJpZM4Nz-qe.

kknee commented 7 years ago

This was an issue with the NDBC collection, which we updated and deployed to dev to keep an eye on: http://dev.oceansmap.com/myglos/#

I think we're probably good to push to production

everhamme commented 7 years ago

About 30 were red this morning on glbuoys.glos.us

Ed Verhamme Project Engineer LimnoTech www.limno.com Ph: (734) 332-1200<tel:(734)%20332-1200> Direct/Cell: (734) 681-0577<tel:(734)%20681-0577> everhamme@limno.commailto:everhamme@limno.com

-------- Original message -------- From: Kelly Knee notifications@github.com Date: 6/13/17 8:09 AM (GMT-05:00) To: glos/myglos myglos@noreply.github.com Cc: Ed Verhamme everhamme@limno.com, Mention mention@noreply.github.com Subject: Re: [glos/myglos] Missing *_20170608.nc files? (#129)

@everhammehttps://github.com/everhamme aren't current where? Spot checked portal and TDS and am seeing 6/13/17 data in both places.

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/129#issuecomment-308095643, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALbbGsK0TybqI6LS5UWW6Ist5aP7uqz6ks5sDnvigaJpZM4Nz-qe.

gcutrell commented 7 years ago

Strangely we are getting an error reading in some NDBC buoys but not others. Usually it is all or nothing. Not 100% sure why the error is occurring so I asked Reid if he knows what is going on.

I have also adopted a previous program where I scrap Limnotech's stations last update and check for a time difference greater than two hours and if this occurs an email is sent out. This program has been very useful for us to catch and fix station errors. The program also checks if the website is available to access. By checking LimnoTech's stations we would also pick up errors with thredds no updating correcting. I can also add a few NDBC stations to verify the script to retrieve NDBC data is working correctly.

Not sure if we want to check all the stations down the road and play the role of NDBC alerting buoy owners of an issue. 75% of the stations are on NDBC so that may be overkill.