Bugzilla – Full Text Bug Listing
| Summary: | [server] user.json parse error causes failure for all to login using Persona or OpenID | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Ken Walker <ken_walker> |
| Component: | Server | Assignee: | Anthony Hunter <ahunter.eclipse> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ahunter.eclipse, john.arthorne, libingw |
| Version: | 4.0 | ||
| Target Milestone: | 5.0 M1 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
I could login today but it seems my index is gone. Neither global nor file name search worked. Talked to John, he redeployed the server and my search is back now. Thanks. It is possible bug 422251 was the culprit here (which I have fixed already). Yes, I think your change to continue regardless of a single failed user is the fix. |
On orion.eclipse.org we're using the new server format. For some unexplained reason, Libing's user.jaon could not be parsed. 2013-11-20 16:41:59.001 [qtp1921086081-35] ERROR org.eclipse.orion.server.config - Meta File Error, cannot read JSON file /opt/mnt/serverworkspace/li/liwang/user.json: Expected a ',' or '}' at character 73730 The line was "operations///task/id/wHrXl8NsABIQAdONTKp72A": "{\"expires\":1360364609915,"Name\":\"Pushing remote: /gitapi/branch/master/file/R/OrionClient/\"}", Note the lack of escape \ in the "Name causing the failure. Not even sure how that happened. Adding in a \ and saving the file fixed it. However, when it could not be parsed, I could not login using Persona or OpenID. Likely due to the iterative loop discovering who I should be but it failed due to this parse error and stopped vs. carrying on.