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
Intermittently users are disappearing [CORE6155] #6404
Comments
Modified by: Mark Kendall (markk_touchcut.com)description: We have development and client production databases with users SYSDBA, THREAD and REPORT. We have a running service that on machine restart creates the THREAD and REPORT users if they are missing. We are about to add user recreation into our front end app as our clients are still not able to connect at times and don't always have the ability to restart their server. Unfortunately I do not have much to report to help with tracking this down. My manager thinks it happens more predominantly to him after his laptop (development PC with fb server) goes to sleep We are probably seeing this about once a month. => We have development and client production databases with users SYSDBA, THREAD and REPORT. We have a running service that on machine restart creates the THREAD and REPORT users if they are missing. We are about to add user recreation into our front end app as our clients are still not able to connect at times and don't always have the ability to restart their server. Unfortunately I do not have much to report to help with tracking this down. My manager thinks it happens more predominantly to him after his laptop (development PC with fb server) goes to sleep We are probably seeing this about once a month - so probably about a 1 in 100 or so chance of it occurring to a particular server in a month |
Commented by: Sean Leyne (seanleyne) Mark, 1- This seems like a support issues which really should be directed to the Support mailing list |
Commented by: Sean Leyne (seanleyne) More details on how to reproduce this issue are required. If you can provide those details, this ticket will be re-opened. |
Modified by: Sean Leyne (seanleyne)status: Open [ 1 ] => Resolved [ 5 ] resolution: Cannot Reproduce [ 5 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Commented by: Mark Kendall (markk_touchcut.com) I have my doubts about it being a support issue, it's never happened before moving to FB3, our app has no ability to drop database users and it's happened here and at a number of client sites. If I find anything else l'lI add notes but I suspect we won't notice it much any more with the work around I've put into the client app to hide it. |
Commented by: Sean Leyne (seanleyne) Mark, Understand. Given the number of locations that FB v3 is installed at, however, I am 99.999% certain that a ticket would have been already been created if this was issue not related to a specific configuration or deployment. |
Commented by: Mark Kendall (markk_touchcut.com) I've just had this happen on my own dev machine which has client application, application server/service and Firebird server on it I did a PC reboot yesterday afternoon (via windows restart). Can connect using windows 64bit odbc admin using user sysdba Nothing in the firebird log for today or yesterday Table SEC$USERS shows the user REPORT |
Modified by: Mark Kendall (markk_touchcut.com)Attachment: showing database.png [ 13399 ] Attachment: security view and sec$users.PNG [ 13400 ] |
Submitted by: Mark Kendall (markk_touchcut.com)
Attachments:
showing database.png
security view and sec$users.PNG
We have development and client production databases with users SYSDBA, THREAD and REPORT.
Every now and again when the front end app connects using the THREAD or REPORT user it fails to connect to the database.
If we re-create the user(s) it then works.
We have a running service that on machine restart creates the THREAD and REPORT users if they are missing. We are about to add user recreation into our front end app as our clients are still not able to connect at times and don't always have the ability to restart their server.
Unfortunately I do not have much to report to help with tracking this down.
My manager thinks it happens more predominantly to him after his laptop (development PC with fb server) goes to sleep
We are probably seeing this about once a month - so probably about a 1 in 100 or so chance of it occurring to a particular server in a month
The text was updated successfully, but these errors were encountered: