[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Perl upgrade



On Fri, Sep 3, 2010 at 10:13 PM, M Lubratt <..hidden..> wrote:
>
>
> On Sat, Sep 4, 2010 at 12:02 AM, M Lubratt <..hidden..> wrote:
>>
>>
>> On Fri, Sep 3, 2010 at 7:50 PM, Chris Travers <..hidden..>
>> wrote:
>>>
>>> On Fri, Sep 3, 2010 at 5:29 PM, M Lubratt <..hidden..> wrote:
>>> > Hello!
>>> >
>>> > I, unfortunately, ventured down the road of upgrading my perl
>>> > installation
>>> > on my FreeBSD 8.1 box from 5.8 to 5.12.  I followed the directions from
>>> > the
>>> > /usr/ports/UPDATING file and rebuilt everything that depends on perl.
>>> > After
>>> > doing so, I was getting errors related to Math::BigInt and the log on
>>> > screen
>>> > wouldn't even appear (from the error log file).  I installed BigInt
>>> > (with
>>> > the GMP library) and could get to the log on screen; however, the only
>>> > things that would appear in the menu system were submenus (with a few
>>> > exceptions).  If I looked under AP, for example, I would see "Reports"
>>> > and
>>> > "Vendors"; but wouldn't see any of the other screens such as "Add
>>> > Transaction."  When I look in /var/log/httpd-error.log, there aren't
>>> > any
>>> > errors.
>>> >
>>> > Frustrated, I downgraded back to 5.8 and rebuilt all dependencies
>>> > again.
>>> > However, the above problem still persists.
>>> >
>>> > I'm running LSMB 1.2.18 on FreeBSD 8.1, Apache 2.2.16 with PostgreSQL
>>> > 8.4.4.
>>> >
>>> > Does anyone have any insight?
>>>
>>> No direct insight.  However you mentioned a few things do work?  Can
>>> you describe what they are?
>>
>> Investigating further, it appears that my screen/workflow permissions for
>> my username in the admin interface were corrupted (I normally have
>> everything enabled).  I tried re-authorize them, but when I hit save, they
>> don't save.
>> I've been looking around and can't seem to find where these permissions
>> are stored.
>
>
> I found where this information is kept in the users_conf table under the acs
> column.  For some reason, it appears that the admin interface is unable to
> save changes to this table...
> I'm not sure if this helps more or not.
> Thanks for all your help!
> Mark

check your db server's logs.

In the mean time update the acs column to an empty string and see if
that gets you going and buys time to troubleshoot.

Best Wishes,
Chris Travers