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
Bot log warnings: "Couldn't flush user prefs: java.util.prefs.BackingStoreException" #3738
Comments
Hmm this shouldn't happen for 2 Reasons:
|
Changing type to 'bug', considering this a logging bug which would need a code change to fix one way or another. |
The TripleA team regrets this issue was not solved sooner. To keep focus on latest issues and the most pressing tasks, this issue has been automatically marked as stale because it has not had recent activity. If the issue may be closed, please do so. If there are remaining items, we encourage for those items to be resubmitted as new, independent, concise tasks. The strategy is divide and conquer. Thank you for your contributions. |
I reviewed the chat logs of all the bots; at the present date, the bug occurs ONLY in the 900 number bots, which are labeled Frankfurt bots. It occurs in all the 90x bots, and none of the bots from other numbers. @RoiEXLab |
Based on the explanation of the error at this site: It appears the problem is that whatever server the Frankfurt bots are running on does not have its java setup correctly; it lacks a user_home directory. I don't know whether we have any direct control over whatever that bot is running on in order to fix that; or if we can contact the people who run it to get them to fix it. The simplest fix by far would involve that computer having its directory set, if we can arrange for that. Since the server bot shouldn't be saving any preferences of its own, it must be about general java preferences. Seeing as people have been using the offending bots for games, it appears that whatever the problem is, it does not substantially worsen gameplay; so we could just catch and ignore the exception. Any fix we implement would require the bot to be redeployed so it gets the update. I don't know how our progress is on the plan to replace the bots with that alternate system; once that's completed it would render this problem moot. edit: I cannot tell which parts of the engine code get used by a bot, and which it cannot access at all. So I cannot use that to exclude any possibilities. |
@zlefin Thank you for digging into this issue. It should be resolved now. Basically on "Frankfurt" the "bot user" did not have a home directory, making it impossible for it to store preferences somewhere. So I created the home directory for it and added the directories for preferences manually (I believe it would have automatically created the directories on restart, but I didn't want to restart the bot if there isn't a good reason for it.) As soon as I created the prefs directory and gave it the correct permissions the error messages instantly stopped. A couple of questions remain though:
Thoughts @DanVanAtta ? |
The following warning appears in the logs very frequently:
If this is harmless then it should be removed otherwise we should look into the problem.
The text was updated successfully, but these errors were encountered: