Closed JessyBarrette closed 4 months ago
how about data@hakai.org ?
what kind of emails are sent from erddap? or is it to advice users who to contact if they have questions?
ERDDAP sends a log summary and some key flag keys to trigger some actions on the server side.
It does suggest the user to contact the ERDDAP admin through this page at least I can see: https://catalogue.hakai.org/erddap/legal.html#contact
data@hakai.org is now however taken over by @Br-Johnson @timvdstap and I for hakai data wide specific issues. Though it could added in there certainly. But I guess this group would have to filter down what it gets back since the logs are very frequent
I think the log emails go to emailEverythingTo
, no?
https://coastwatch.pfeg.noaa.gov/erddap/download/setup.html#setup.xml
Oh yeah I guess your right, this is setup to point to @.***
Which i think is alright and I am getting those.
On Thu, Jan 11, 2024 at 5:08 PM Nate @.***> wrote:
I think the log emails go to emailEverythingTo, no?
https://coastwatch.pfeg.noaa.gov/erddap/download/setup.html#setup.xml
— Reply to this email directly, view it on GitHub https://github.com/HakaiInstitute/hakai-datasets/issues/171#issuecomment-1888046158, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHICYOMTLZSUKYWP4MPSFADYOBPE3AVCNFSM6AAAAABBXDUOWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBYGA2DMMJVHA . You are receiving this because you authored the thread.Message ID: @.***>
-- Jessy Barrette M.Sc. Marine Data and Instrumentation Specialist Hakai Institute https://www.hakai.org/ | CIOOS Pacific https://cioospacific.ca/ | CIOOS https://cioos.ca/ | @.*** | (C) (250) 208-7806
Then I'm not too sure what is sent to the adminEmail. Then if the logs aren't sent via that admin email. I'm ok pointing to data@hakai.org
We can always reassess later.
Here's an example of email received presently at info@cioospacific.ca
---------- Forwarded message ---------
From: <[notifications@hakai.org](mailto:notifications@hakai.org)>
Date: Thu, Jan 11, 2024 at 12:03 PM
Subject: df14a0d39f57 ERDDAP: ERROR in HakaiKetchikanBoLResearch constructor (inotify)
To: <[info@cioospacific.ca](mailto:info@cioospacific.ca)>
https://localhost:8443/erddap reports:
java.nio.file.NoSuchFileException: /datasets/HakaiKetchikanBoLResearch
at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
at java.base/sun.nio.fs.UnixException.asIOException(UnixException.java:115)
at java.base/sun.nio.fs.LinuxWatchService$Poller.implRegister(LinuxWatchService.java:246)
at java.base/sun.nio.fs.AbstractPoller.processRequests(AbstractPoller.java:266)
at java.base/sun.nio.fs.LinuxWatchService$Poller.run(LinuxWatchService.java:364)
at java.base/java.lang.Thread.run(Thread.java:833)
After talking to a few of the different people getting emails from data@hakai.org, we're thinking it would be best to use another address.
data@hakai.org is more an email to reach out about data questions related to Hakai.
how about creating erddap.admin@hakai.org
That sounds reasonable, who would be in the group?
@fostermh Is this a Google group you are creating or an email alias or a new Google user? Personally I've been creating Google Groups for project specific email collection and adding everyone involved so that the entire history of emails is preserved regardless of who is in the group and anyone added in the future can see previous.
I was thinking of a google group, yes. similar to support@hakai.org, eims.support@hakai.org, etc.
instead of erddap.admin@hakai.org we could consider erddap.support@hakai.org. It matters not to me. I'm happy to create, or someone else can.
Just to summarize the emails related to this erddap deployment:
emailFromAddress: notifications@hakai.org
emailEverythingTo: erddap-notifications@hakai.org
emailDailyReportsTo:
adminEmail: info@cioospacific.ca -> erddap.support@hakai.org
.
or -
erddap.support
seems good to me. I guess the only thing is since we're already using erddap-notifications@hakai.org
, perhaps it should be instead erddap-support
. Or we move erddap-notifications
to erddap.notifications
I don't really care though.
Who to add to the group. You can at least add me, not sure you wanna be included but all guess perhaps the 4 us.
PS We'll have to think about something similar for the cioospacific erddap.
I'll be included while we are doing the ongoing ERDDAP dev work and when that is over I will leave the group.
erddap support email group erddap.support@hakai.org erddap-support@hakai.org
erddap notifications email group erddap-notifications@hakai.org erddap.notifications@hakai.org
are all live
Perfect! Do both variant - or . are pointing to the same groups
Both Hakai ERDDAP were updated with the admin email erddap-support@hakai.org
Ah Java, even your logs are verbose nonsense
I don't think I received any erddap-support emails yet. lots of notitifcations one though haha
Woohooo! I haven't received any in the last 24 hours. Yippee!
Thanks guys! Jonathan
On Wed, Jan 24, 2024, 12:13 PM Jessy Barrette @.***> wrote:
I don't think I received any erddap-support emails yet. lots of notitifcations one though haha
— Reply to this email directly, view it on GitHub https://github.com/HakaiInstitute/hakai-datasets/issues/171#issuecomment-1908847180, or unsubscribe https://github.com/notifications/unsubscribe-auth/APA2V4DUM4ELBMNF7VTK3WDYQFTQHAVCNFSM6AAAAABBXDUOWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBYHA2DOMJYGA . You are receiving this because you were mentioned.Message ID: @.***>
All the erddap referencing info@cioospacific.ca
were taken down.
ERDDAP uses an admin email address to send to logs and potentially link users to.
Right now, that email address is wrongly pointing to
<adminEmail>info@cioospacific.ca</adminEmail>
Thanks to @jpkellogg for pointing that out. It would be a lot better to point towards an hakai specific email and perhaps ERDDAP specific.
@steviewanders @n-a-t-e @fostermh thoughts?