Date   

moderated Re: Event: Site maintenance, Thursday, 2 February 2017 #downtime #cal-invite

 

On Wed, Feb 1, 2017 at 11:31 AM, Brian Vogel <britechguy@...> wrote:
On Wed, Feb 1, 2017 at 11:24 am, Mark Fletcher wrote:
I can fairly confidently state that if I were to send a message unilaterally to all groups, I would have a mutiny on my hands.

Good heavens, people are fussy then, aren't they?!


I learned long ago that group owners are very possessive of their groups and members, and do not like anything happening with their groups that they don't know about or control. Note, this is not a criticism.

Mark


moderated Re: Event: Site maintenance, Thursday, 2 February 2017 #downtime #cal-invite

Brian Vogel <britechguy@...>
 

On Wed, Feb 1, 2017 at 11:24 am, Mark Fletcher wrote:
I can fairly confidently state that if I were to send a message unilaterally to all groups, I would have a mutiny on my hands.

Good heavens, people are fussy then, aren't they?!

There are several systems I use that routinely send me e-mail messages about planned outages, and that's the reason I suggested it.  They might come twice or three timed per year.  Unless I'm missing something those who interact via e-mail only will be left completely in the dark about this, which I don't think is good at all.

However, not my call. 
--
Brian

You can safely assume you've created God in your own image when it turns out that God hates all the same people you do.

    ~ Anne Lamott


moderated Re: Event: Site maintenance, Thursday, 2 February 2017 #downtime #cal-invite

 

On Wed, Feb 1, 2017 at 10:50 AM, J_Catlady <j.olivia.catlady@...> wrote:
At first I liked the idea, but a status banner works better for me. Plus I hate to think about what the spam filters would do if the messages were sent to all the groups....

I can fairly confidently state that if I were to send a message unilaterally to all groups, I would have a mutiny on my hands. 

I like the banner idea; I'll put one up this afternoon.

Thanks,
Mark 


moderated Re: Planned downtime next Thursday 2/2/17

 

On Wed, Feb 1, 2017 at 12:06 AM, Shal Farley <shals2nd@...> wrote:

"... growth continued unabated. We quickly had to begin the neverending cycle of hardware upgrades. The original ONElist box was a Pentium PC running Linux with 32 megs of memory. Laughable by today's standards."

So it's true: "plus ça change, plus c'est la même chose."


The more things change, the more I like to pick memes? I dunno, my French was never that good. But I do like a good cat meme (and they're all good). :-)

There are currently 10 machines in the Groups.io cluster. The main database machine that will be upgraded tomorrow night currently has 8GB memory and 96GB storage. I'll be bumping that to 24GB memory and 385GB storage. This afternoon I'll also be bringing a second web server online.

One of my goals over the next year is to transition some of the backend tech so that I won't have to ever take down the site completely. But I'm waiting on some database software to mature some more.

Mark


moderated Re: Event: Site maintenance, Thursday, 2 February 2017 #downtime #cal-invite

 

At first I liked the idea, but a status banner works better for me. Plus I hate to think about what the spam filters would do if the messages were sent to all the groups....
J


Sent from my iPhone

On Feb 1, 2017, at 10:28 AM, Shal Farley <shals2nd@gmail.com> wrote:

Mark,

Brian wrote:
Might this not be something that should show up in each and every
group in groups.io? It seems like it's something that every user
should be aware of. I have seen this notice, and the related post
about planned outage, only on beta.
I concur with Brian. I was thinking that perhaps this calendar entry would be better placed on updates@, as that reaches far more users. Or perhaps there should be a separate list for site status.

I would hope that a mechanism exists for "the Grand Poo-Bah of
Groups.io" [Mark right now and for the foreseeable future] to blast
a message out to each and every group in existence at a given point
in time.
I wouldn't want that posted as a message in my groups, as a group owner I'd find that intrusive. However a status banner on the web pages (all of them), just below the logo bar, might make sense.

For an event like this I don't think an email blast to _all_ users is warranted: the vast majority are unlikely to visit the site during the affected hours anyway. A notice on the site pages would be better targeted.

Shal
https://groups.io/g/Group_Help
https://groups.io/g/GroupManagersForum


--
J

Messages are the sole opinion of the author. Especially the fishy ones.

I wish I could shut up, but I can't, and I won't. - Desmond Tutu


moderated Re: Event: Site maintenance, Thursday, 2 February 2017 #downtime #cal-invite

Brian Vogel <britechguy@...>
 

On Wed, Feb 1, 2017 at 10:28 am, Shal Farley wrote:
I wouldn't want that posted as a message in my groups, as a group owner I'd find that intrusive.

I can't and won't argue with anyone's personal preferences, they are what they are.

That being said, there are users from all over the world who use Groups.io, and a number of them could very well be quite active during the scheduled maintenance time.  While the e-mail messages will be queued up, it could be very confusing to have stuff seemingly MIA for several hours without warning.  Intrusive is precisely what I'd be looking for as a user can read, or delete, an e-mail message at will or skip any entry on the web interface.  When it comes to scheduled outages I prefer overkill in notification to individual users rather than subtlety.
--
Brian

You can safely assume you've created God in your own image when it turns out that God hates all the same people you do.

    ~ Anne Lamott


moderated Re: Event: Site maintenance, Thursday, 2 February 2017 #downtime #cal-invite

 

Mark,

Brian wrote:
Might this not be something that should show up in each and every
group in groups.io? It seems like it's something that every user
should be aware of. I have seen this notice, and the related post
about planned outage, only on beta.
I concur with Brian. I was thinking that perhaps this calendar entry would be better placed on updates@, as that reaches far more users. Or perhaps there should be a separate list for site status.

I would hope that a mechanism exists for "the Grand Poo-Bah of
Groups.io" [Mark right now and for the foreseeable future] to blast
a message out to each and every group in existence at a given point
in time.
I wouldn't want that posted as a message in my groups, as a group owner I'd find that intrusive. However a status banner on the web pages (all of them), just below the logo bar, might make sense.

For an event like this I don't think an email blast to _all_ users is warranted: the vast majority are unlikely to visit the site during the affected hours anyway. A notice on the site pages would be better targeted.

Shal
https://groups.io/g/Group_Help
https://groups.io/g/GroupManagersForum


moderated Re: Event: Site maintenance, Thursday, 2 February 2017 #downtime #cal-invite

Brian Vogel <britechguy@...>
 

Might this not be something that should show up in each and every group in groups.io?  It seems like it's something that every user should be aware of.  I have seen this notice, and the related post about planned outage, only on beta.

I would hope that a mechanism exists for "the Grand Poo-Bah of Groups.io"  [Mark right now and for the foreseeable future] to blast a message out to each and every group in existence at a given point in time.
--
Brian

You can safely assume you've created God in your own image when it turns out that God hates all the same people you do.

    ~ Anne Lamott


moderated Event: Site maintenance, Thursday, 2 February 2017 #downtime #cal-invite

beta@groups.io Calendar <beta@...>
 

Site maintenance

When:
Thursday, 2 February 2017
9:00pm to 11:00pm
(GMT-08:00) America/Los Angeles

Description:

The site will be down to upgrade the main database machine. Emails sent during this time will be queued and delivered after the site is back up.


moderated Re: Planned downtime next Thursday 2/2/17

 

"... growth continued unabated. We quickly had to begin the neverending cycle of hardware upgrades. The original ONElist box was a Pentium PC running Linux with 32 megs of memory. Laughable by today's standards."

So it's true: "plus ça change, plus c'est la même chose."

Shal



moderated Re: Adding custom sign up fields #suggestion

 

Armando,

Can you add a feature in which you can customize your sign up
form to put on your website to have custom fields, for example, a
person is required to upload a profile picture to join the group?
There isn't a feature like that now, but there's an item like that on the wishlist:
https://trello.com/c/iSkDckWb/

There have also been some earlier discussions here about this. For example:
https://groups.io/g/beta/message/11126

Shal
https://groups.io/g/Group_Help
https://groups.io/g/GroupManagersForum


moderated Adding custom sign up fields #suggestion

Armando <armando.elevatorfan@...>
 

Hi. Can you add a feature in which you can customize your sign up form to put on your website to have custom fields, for example, a person is required to upload a profile picture to join the group?

Sent from my iPhone 6s


moderated Re: Outage report #outage

Bob Bellizzi
 

Sounds like self denial of service to me <g>

Bob Bellizzi


moderated Re: Outage report #outage

 

As an addendum, the extra large digest was caused by a bug. The group is not set to resize photos in email. We normally resize photos in digests to a max of 400x400 or what the group is set to resize photos to, whichever is smaller. Because of the bug, for groups that don't resize emailed photos, we were not resizing photos at all for digests. Hence, the extra large digests. This has been fixed.

Thanks, Mark


moderated Re: Outage report #outage

Sugar
 

As always Mark, God bless you and all you do to help us all enjoy groups io

Sugar

 

‘I have loved the stars too fondly to be fearful of the

night.

 

Sugar

 

From: beta@groups.io [mailto:beta@groups.io] On Behalf Of Mark Fletcher
Sent: Monday, January 30, 2017 4:36 PM
To: beta@groups.io
Subject: [beta] Outage report #outage

 

Hi All,

 

We had an incident starting at 4:04pm and lasting until 4:21pm. During that time the website was only sporadically available, and email was not delivered at all.

 

A post to a group triggered a digest to 271 of their members. The digest was 15MB in size each. Because each digest is unique, that meant 4GB of messages. The process that is responsible for sending email, called karl (after Karl the Mailman Malone), currently keeps all messages in memory. This immediately ate up much more than 4GB of memory, including overhead, causing the karl process to run out of memory. The main web machine became unresponsive and was rebooted. This sequence occurred several more times, until I was able to add some code to karl to skip reading those large digest messages when it started up. The machine is now stable.

 

To resolve this, I need to re-write parts of karl to not keep large messages in memory. Once I am able to do that, the large digest messages will be delivered.

 

Thanks,

Mark




moderated Outage report #outage

 

Hi All,

We had an incident starting at 4:04pm and lasting until 4:21pm. During that time the website was only sporadically available, and email was not delivered at all.

A post to a group triggered a digest to 271 of their members. The digest was 15MB in size each. Because each digest is unique, that meant 4GB of messages. The process that is responsible for sending email, called karl (after Karl the Mailman Malone), currently keeps all messages in memory. This immediately ate up much more than 4GB of memory, including overhead, causing the karl process to run out of memory. The main web machine became unresponsive and was rebooted. This sequence occurred several more times, until I was able to add some code to karl to skip reading those large digest messages when it started up. The machine is now stable.

To resolve this, I need to re-write parts of karl to not keep large messages in memory. Once I am able to do that, the large digest messages will be delivered.

Thanks,
Mark


moderated Re: New members not receiving notice

 

Yay! Thanks, Mark!!!
--
J

Messages are the sole opinion of the author. Especially the fishy ones.

I wish I could shut up, but I can't, and I won't. - Desmond Tutu


moderated Re: New members not receiving notice

 

On Fri, Jan 27, 2017 at 10:01 AM, J_Catlady <j.olivia.catlady@...> wrote:

This is great. Would it be possible to add tracking for the confirmation email, as well? That's the one that goes missing most of the time in our group.


We're now tracking confirmation email deliveries/bounces.

Thanks,
Mark 


moderated Adding Custom sign up form fields in embedded sign up forms #suggestion

Armando <armando.elevatorfan@...>
 

When I promote my mailing list, I only have the email address field so people can sign up with just there email address. I would like the option to put custom fields, for example, I would require a profile picture on their profile. The only way that I can approve my members is through google forms. I would like the option to approve them through groups.io, like for example, put there response in one email and I will decide if I will approve or reject a new member.

Sent from my iPhone 6s


moderated Re: +owner messages

 

On Mon, Jan 30, 2017 at 8:13 AM, J_Catlady <j.olivia.catlady@...> wrote:

This is great.

I'm wondering, do the confirmation emails have the same characteristic? Those have been more problematic for us than the "pending" messages.

No. The confirmation emails are created by us, and so don't have any headers that might cause issues.

Thanks,
Mark 

18341 - 18360 of 30985