[ic] sdbm (and maybe locale)

[DB]

On 11/26/24 3:09 PM, Stefan Hornburg (Racke) wrote:
> On 26/11/2024 20:26, DB via interchange-users wrote:
>> On 11/26/24 12:07 PM, Stefan Hornburg (Racke) wrote:
>>> On 26/11/2024 18:02, DB via interchange-users wrote:
>>>> I'm moving my Interchange install to a new Alma Linux 9 machine and 
>>>> I have it mostly working. However I'm having some issue apparently 
>>>> caused by using sdbm. If I try to load the admin backend for 
>>>> example, in my main interchange error log I see
>>>>
>>>> Store /cgi-bin/Store/admin/login.html Died in server spawn: ichelp 
>>>> import into  failed: sdbm store returned -1, errno 22, key 
>>>> "kimport.main" at /usr/local/interchange/lib/Vend/Table/Common.pm 
>>>> line 516, <IN> line 2.
>>>>
>>>> Is this because I'm using sdbm for locale? And is there a way to 
>>>> switch form using sbdm?
>>>>
>>>> Thanks!
>>>>
>>>> DB
>>>
>>> I think you need to install GDBM.
>>>
>>> Regards
>>>    Racke
>>>
>>
>> Thanks! perl -MGDBM_File -e 'print $GDBM_File::VERSION' reports
>> 1.18
>> and I have also installed my OS's GDBM package, but I'm still getting 
>> the error.
>>
>> I had trouble getting IC installed using the AlmaLinux native perl but 
>> I did get things to work using plenv and an older perl version. The 
>> site's front end seems to work ok but I still get this 500 when I try 
>> to get into the back end.
>>
>> If there is some other way around this error I'm getting, I'd love to 
>> hear ideas.
>>
>> I'm not committed to Alma, so am open to suggestions from anyone on 
>> what to migrate to from my EOL Centos7 that may work better.
>>
>> DB
> 
> I got this problem a few times with a fresh installation, so it is 
> probably not a problem  of the distribution.
> 
> Regards
>     Racke
> 
>> _______________________________________________
>> interchange-users mailing list
>> interchange-users at interchangecommerce.org
>> https://www.interchangecommerce.org/mailman/listinfo/interchange-users
> 
> 

Thanks again for your reply. I did try removing *.sdbm from my products 
directory and restarting IC but that did not help. I have only seen this 
500 error occur when I try to access the admin pages, which makes me 
suspect some issue with the access.acs and access.gdbm files, so IC 
tries to fall back to using sdbm. Does that sound reasonable?

DB