Issues with the Group Settings API?

[Brian Mcnamara]

Are there any issues with the Group Settings API endpoints?  I'm using GAM to iterate through a text file to change the archive settings for groups in a Google Apps domain and am receiving the following exception over most of the groups:

    'reason': server_response.reason, 'body': result_body}

gdata.service.RequestError: {'status': 503, 'body': '<?xml version="1.0" encoding="UTF-8"?>\n<errors xmlns="http://schemas.google.com/g/2005">\n <error>\n  <domain>GData</domain>\n  <code>backendError</code>\n  <internalReason>Backend Error</internalReason>\n </error>\n</errors>\n', 'reason': 'Service Unavailable'}

I am running the following command:

python gam.py update group ${group} settings is_archived true

Regards,

Brian

Brian McNamara, Certified Google Apps Deployment Specialist

LTech | bmcn...@ltech.com | 908-566-1728 | Google Voice 908-505-5155

[Jay Lee]

Thanks for reporting this here Brian, I've been seeing more reports of this on the GAM mailing list but have not had time to troubleshoot. Can you create a file named debug.gam and post the GAM debug output showing the raw GData HTTP calls also? (helps determine if it's a GAM issue or a GData / backend issue)

How reproducible is this? Does the error occur only on certain groups and is occurring 100% for those groups? If so, what does "gam info group <group email> settings" show? Any other Web UI settings different about the problem groups?

Jay

LTech | bmc...@lt...com | 908-566-1728 | Google Voice 908-505-5155

[Brian Mcnamara]

Hi Jay,

Thanks for the follow-up.  I've attached a sample run for 5 groups (basically using a bash for loop to call GAM).  I've stripped out the client name but all other output is unchanged.  I have not gone through multiple iterations but the output seems to be the same for the sample list; the production group list has over 1500 names.  The groups are being created with GADS.  I've put in a statement "Working on group" to separate the groups in the debug file.  

I manually set the Archive value for the first group to true but left it in the run.  Google is reporting a 400 - Bad Request error in the debug log.  

The second and third requests ran through fine and updated the setting in the group.

The fourth and fifth request generated a 503 - Service Unavailable error in the debug log.  

Please let me know if there is any additional information I can provide.

Regards,

Brian

Brian McNamara, Certified Google Apps Deployment Specialist

LTech | bmcn...@ltech.com | 908-566-1728 | Google Voice 908-505-5155

--
You received this message because you are subscribed to the Google Groups "Google Apps Domain Information and Management APIs" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-apps-mgmt-apis/-/_vYcWGvsQLMJ.
To post to this group, send email to google-app...@googlegroups.com.
To unsubscribe from this group, send email to google-apps-mgmt...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-apps-mgmt-apis?hl=en.

[Brian Mcnamara]

For any Googlers out there, I've opened up Ticket 02012649 with the raw debug output attached.

Regards,

Brian

To post to this group, send email to google-apps-mgmt-apis@googlegroups.com.
To unsubscribe from this group, send email to google-apps-mgmt-apis+unsub...@googlegroups.com.

[Jay Lee]

Just an FYI that I am experiencing the exact same error as Brian on a deployment (and I'm also the author of GAM).

We have however found a workaround for the issue. If you open the group's settings in a web browser, then API calls start succeeding for that group. So for example, if I'm getting the 503 Backend Error for myg...@example.com then I can open Chrome and go to:

https://groups.google.com/a/example.com/group/mygroup/manage_access

and from then on, GAM commands that update the group settings will succeed. However this is not scalable as opening a bunch of groups one right aftere the other in a browser will get you blocked by Google's automated process detection.

If any Googlers are looking into this, I've also filed ticket 02032230 with support on this issue.

Jay

[Stafford Marquardt]

Hi Jay and Brian,

Just wanted to let you know that we are indeed looking into this, and appreciate your patience in the meantime.  Thanks for figuring out this workaround and letting everyone know how to use it!

Cheers,

Stafford