More info to the Log when engine opening database file fails

[TommiPrami]

If there is some other app, reserving the file, at least on Windows engine could try to check can the OS report the app holding the file.

Would help investigation very much, what actually happened.

Example code for getting info of the reserving app (on windows): https://devblogs.microsoft.com/oldnewthing/20120217-00/?p=8283

For security reasons most likely that information can only be in firebird log. Not the error sent to the client, maybe...

[TommiPrami]

For information we have server with 800 databases. When we have to update all databases, now we got "no permission for read-write access to database", I would guess it is more than less situation mentioned above.

If we would possibly have now info of the process reserving the file, it would be way easier to get to the root of the problem.

[hvlad]

It is not a task of database engine to query OS to find process that opens file in incompatible mode, IMHO.
More, there is no common way for this in different OS.

There is OS tools that allows what you want (and many more). On Windows - see SysInternals (ProcessExplorer or handle).

[TommiPrami]

Problem is, that when some random app reserves db-file for a split second, it is impossible to diagnose afterwards.

If this happens, let's say once a year, how to find out why.

If it happens when you are not monitoring the situation, when a problem arises, there is no sane way to find the culprit.

This server has been running without this error a couple of years, previous servers never encountered this.

It is a different case if the problem is reproducible

[aafemt]

That's why Firebird server should be run under a dedicated account and all databases to be located in a folder where only this account has access. This is an administration problem.

[TommiPrami]

Fair point, but still system etc can block file if it just chooses to do so.

…

-tee-

On Fri, Jan 10, 2025, 17:35 Dimitry Sibiryakov ***@***.***> wrote: That's why Firebird server should be run under a dedicated account and all databases to be located in a folder where only this account has access. This is an administration problem. — Reply to this email directly, view it on GitHub <#8378 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7E2H64I74EC7FPDHMZECT2J7SF3AVCNFSM6AAAAABUZIGLRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBSHE3TONZVGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[TommiPrami]

On other hand we have thousands of desktop installs, where we have no control what so ever, what user and it's possible installed applications do.

There this would be even more valuable.

User can be Admin, everything they install runs as admin, can be any virus scanner installed, with any settings. etc...

[TommiPrami]

I was also thinking that at least on windows Firebird could give extra info, easily, with quite minimal changes.

It is really hard to think that someone would get offended if such info would be in the log.

And repeat again that most likely it is impossible to investigate after the fact. Who is that lucky that problem is easily reproducible.