Re: [Firebird-devel] second embedded connect hangs on armel, ia64, kfreebsd and s390

[Alex P. <pes...@ma...>]

 On 11/16/11 08:44, Dmitry Yemanov wrote:
> 16.11.2011 1:22, Damyan Ivanov wrote:
>
>>> Is there anything interesting in firebird.log?
>> There is no firebird.log file in the current directory. Perhaps
>> I missed an additional environment variable that needs to be set for
>> embedded (the system-wide firebird log directory is not writable by
>> the user).
> Setting FIREBIRD should be enough.
>

In standard install procedure empty, firebird group writable file
firebird.log is created. Does .deb package create that file too? Is
user, running that script, a member of group firebird?

>> Here it is. This is after (1) creating the database in the first
>> session and (2) attempting to attach to the freshly created database
>> in another session (same user, hanging).
>>
>> OWNER BLOCK  20872
>>          Owner id: 73448235728900, type: 1, pending:      0
>>          Process id:  17101 (Alive), thread id: 1073877248
>>          Flags: 0x10                           sgnl
>>          Requests (21):  forward:  21040, backward:  23440
>>          Blocks (1):     forward:  21040, backward:  21040
>>
>> OWNER BLOCK  23672
>>          Owner id: 73761768341505, type: 1, pending:  23840
>>          Process id:  17174 (Alive), thread id: 1073877248
>>          Flags: 0x24                 wait tout
>>          Requests (1):   forward:  23840, backward:  23840
>>          Blocks: *empty*
> The blocking process has been signaled (in the shared memory) but did 
> not see that fact. This is likely to mean that the IPC event hasn't been 
> delivered.

Starting with 2.5.1 all IPC-related errors, that can't be for some
reason delivered to user, are not ignored but logged. Therefore making
firebird.log work appears to be very good idea.