-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random error on service reset #194
Comments
I see this a after upgrading to a newer git hash and restarting my service. It seems like a temporary error that a logout / login or return to core room listing / re-entering room fixes. My only guess is it hasn't connected to mongo yet so user._id is still undefined. My only guess is it hasn't connected to mongo yet so user._id is still undefined. |
This problem persists even after connecting to mongo, all the way up to viewing the very front page of your instance. I suspect there's some reference getting updated on the viewing of that page (related to the population of the |
I had this my past 2 upgrades...the 2nd to latest upgrade I freaked out and reverted to older and older hashes until the error went away. Then I rolled forward 1 hash at a time and couldn't reproduce so went back to latest. The reason I became convinced it was a service restart/startup issue was the past upgrade I did was from before the #185 Merge to #187 revert of that merge...so no code actually changed, I just ran a I dropped this reminder to my self of the hashes and the error on my server:
I'll upload my /etc/init.d service and start.sh script if you think it has something to do with the way I restart. Edit: shell scripts here: https://gist.github.com/diginc/f54a5d7c6e7e66e28a40 |
The text was updated successfully, but these errors were encountered: