Mailing List Archive: Interchange: users

"GDBM could not tie to access.gdbm"

Index | Next | Previous | View Threaded

emailgrant at gmail

Aug 18, 2009, 4:44 PM

Post #1 of 7 (1136 views)
Permalink

"GDBM could not tie to access.gdbm"

Has anyone seen errors like this in the global IC log:

Died in server spawn: GDBM could not tie to access.gdbm: Resource
temporarily unavailable at
/usr/local/interchange/lib/Vend/Table/GDBM.pm line 116.

It seems to happen once in a while when working in the admin. I'm not
sure what's causing this.

- Grant

_______________________________________________
interchange-users mailing list
interchange-users [at] icdevgroup
http://www.icdevgroup.org/mailman/listinfo/interchange-users

jon at endpoint

Aug 18, 2009, 4:52 PM

Post #2 of 7 (1060 views)
Permalink

Re: "GDBM could not tie to access.gdbm" [In reply to]

On Tue, 18 Aug 2009, Grant wrote:

> Has anyone seen errors like this in the global IC log:
>
> Died in server spawn: GDBM could not tie to access.gdbm: Resource
> temporarily unavailable at
> /usr/local/interchange/lib/Vend/Table/GDBM.pm line 116.
>
> It seems to happen once in a while when working in the admin. I'm not
> sure what's causing this.

I believe I've seen that when you try to log in at the same time another
process has the access table open and locked.

I found too much contention for that table when it's in DBM, so I
recommend you move it into your SQL database instead where this isn't a
problem.

Jon

--
Jon Jensen
End Point Corporation
http://www.endpoint.com/

_______________________________________________
interchange-users mailing list
interchange-users [at] icdevgroup
http://www.icdevgroup.org/mailman/listinfo/interchange-users

emailgrant at gmail

Aug 19, 2009, 12:35 AM

Post #3 of 7 (1059 views)
Permalink

Re: "GDBM could not tie to access.gdbm" [In reply to]

>> Has anyone seen errors like this in the global IC log:
>>
>> Died in server spawn: GDBM could not tie to access.gdbm: Resource
>> temporarily unavailable at
>> /usr/local/interchange/lib/Vend/Table/GDBM.pm line 116.
>>
>> It seems to happen once in a while when working in the admin. 狢'm not
>> sure what's causing this.
>
> I believe I've seen that when you try to log in at the same time another
> process has the access table open and locked.
>
> I found too much contention for that table when it's in DBM, so I
> recommend you move it into your SQL database instead where this isn't a
> problem.
>
> Jon

Thank you Jon.

- Grant

_______________________________________________
interchange-users mailing list
interchange-users [at] icdevgroup
http://www.icdevgroup.org/mailman/listinfo/interchange-users

racke at linuxia

Aug 20, 2009, 12:19 AM

Post #4 of 7 (1051 views)
Permalink

Re: "GDBM could not tie to access.gdbm" [In reply to]

Jon Jensen wrote:
> On Tue, 18 Aug 2009, Grant wrote:
>
>> Has anyone seen errors like this in the global IC log:
>>
>> Died in server spawn: GDBM could not tie to access.gdbm: Resource
>> temporarily unavailable at
>> /usr/local/interchange/lib/Vend/Table/GDBM.pm line 116.
>>
>> It seems to happen once in a while when working in the admin. I'm not
>> sure what's causing this.
>
> I believe I've seen that when you try to log in at the same time another
> process has the access table open and locked.
>
> I found too much contention for that table when it's in DBM, so I
> recommend you move it into your SQL database instead where this isn't a
> problem.

I agree. What about a patch for standard catalog?

Regards
Racke

--
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team

_______________________________________________
interchange-users mailing list
interchange-users [at] icdevgroup
http://www.icdevgroup.org/mailman/listinfo/interchange-users

emailgrant at gmail

Aug 20, 2009, 1:17 PM

Post #5 of 7 (1051 views)
Permalink

Re: "GDBM could not tie to access.gdbm" [In reply to]

>>> Has anyone seen errors like this in the global IC log:
>>>
>>> Died in server spawn: GDBM could not tie to access.gdbm: Resource
>>> temporarily unavailable at
>>> /usr/local/interchange/lib/Vend/Table/GDBM.pm line 116.
>>>
>>> It seems to happen once in a while when working in the admin. 狢'm not
>>> sure what's causing this.
>>
>> I believe I've seen that when you try to log in at the same time another
>> process has the access table open and locked.
>>
>> I found too much contention for that table when it's in DBM, so I
>> recommend you move it into your SQL database instead where this isn't a
>> problem.
>
> I agree. What about a patch for standard catalog?
>
> Regards
> � � � 袠acke

Sounds good to me. Please post here if such a patch is comitted.

- Grant

_______________________________________________
interchange-users mailing list
interchange-users [at] icdevgroup
http://www.icdevgroup.org/mailman/listinfo/interchange-users

jon at endpoint

Aug 21, 2009, 5:13 PM

Post #6 of 7 (1048 views)
Permalink

Re: "GDBM could not tie to access.gdbm" [In reply to]

On Thu, 20 Aug 2009, Stefan Hornburg wrote:

>> I found too much contention for that table when it's in DBM, so I
>> recommend you move it into your SQL database instead where this isn't a
>> problem.
>
> I agree. What about a patch for standard catalog?

On this topic, does anyone know why the MySQL definition for the access
table includes this additional parameter?

Database access IC_LOCKING 1

The access table is still a DBM table by default even when using MySQL as
it is for Postgres and SQLite definitions too, so I wonder why that's
there.

Jon

--
Jon Jensen
End Point Corporation
http://www.endpoint.com/

_______________________________________________
interchange-users mailing list
interchange-users [at] icdevgroup
http://www.icdevgroup.org/mailman/listinfo/interchange-users

gert at 3edge

Aug 23, 2009, 6:50 AM

Post #7 of 7 (1008 views)
Permalink

Re: "GDBM could not tie to access.gdbm" [In reply to]

> -----Original Message-----
> From: interchange-users-bounces [at] icdevgroup [mailto:interchange-
> users-bounces [at] icdevgroup] On Behalf Of Jon Jensen
> Sent: Saturday, August 22, 2009 3:13 AM
> To: interchange-users [at] icdevgroup
> Subject: Re: [ic] "GDBM could not tie to access.gdbm"
>
> On Thu, 20 Aug 2009, Stefan Hornburg wrote:
>
> >> I found too much contention for that table when it's in DBM, so I
> >> recommend you move it into your SQL database instead where this
> isn't a
> >> problem.
> >
> > I agree. What about a patch for standard catalog?
>
> On this topic, does anyone know why the MySQL definition for the access
> table includes this additional parameter?
>
> Database access IC_LOCKING 1
>
> The access table is still a DBM table by default even when using MySQL
> as
> it is for Postgres and SQLite definitions too, so I wonder why that's
> there.
>
> Jon

My assumption is that it was put there by someone who mainly uses MySQL as
their database of choice for Interchange.

According to Whatsnew 4.9:
* Add internal Interchange locking routines and support for GDBM. (Should
work on others as well but is not tested.)

To set internal locking, just put in the config:

Database access IC_LOCKING 1

On GDBM, employs the GDBM_NOLOCK parameter.

It should prevent the errors in access.gdbm when multiple admins are
logged in. It might also serve to make userdb in GDBM somewhat usable.

When you do not have this line and using GDBM for your access file and 2
people/processes are trying to use access.gdbm, the second process will have
a problem (2 admin users, one will get a 500 error screen for example). This
line will prevent this from happening and I suppose it should have been
added in the pgsql and sqlite versions as well ...

And if I am seeing the code correctly then in lib/Vend/Table/Common.pm the
sub's lock_table and unlock_table are depending on this variable being
set. If not set I suppose locking will depend on for example if MySQL itself
performs certain kinds of locking on the table during certain actions ...

CU,

Gert

_______________________________________________
interchange-users mailing list
interchange-users [at] icdevgroup
http://www.icdevgroup.org/mailman/listinfo/interchange-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads