[ledgersmb-users] Re: Stuck upgrading 1.6.27 to anything beyond

[lsmbdev <..hidden..>]

Hi Louis,

What version were you intending to upgrade to?

For the "no such file or directory" error you can try manually creating the parent dir with

    mkdir "/tmp/deleted_transaction_files/"

That is not the ideal solution, but may allow the upgrade to proceed. 

(I'm not at a computer so can't try testing to confirm cause or if this will help)

Regards

David G

Sent from my Galaxy

-------- Original message --------

From: "Louis B. Moore" <..hidden..>

Date: 3/6/21 12:24 (GMT+08:00)

To: Erik Huelsmann <..hidden..>

Cc: ..hidden..

Subject: [ledgersmb-users] Re: Stuck upgrading 1.6.27 to anything beyond

Different error:

    Error!
    Can't create directory /tmp/deleted_transaction_files/hethcote: No such
    file or directory at
    /usr/local/ledgersmb/sql/changes/1.6/track-deleted-transactions.sql.checks.pl
    line 38.

    dbversion: , company: 1.6.31


Created directory:


    Error!
    Can't create directory /tmp/deleted_transaction_files/hethcote:
    Permission denied at
    /usr/local/ledgersmb/sql/changes/1.6/track-deleted-transactions.sql.checks.pl
    line 38.

    dbversion: , company: 1.6.31


Chowned directory:

success.




Thank you!











On Thu, 3 Jun 2021, Erik Huelsmann wrote:

> Hi Louis,
>
>
> On Wed, Jun 2, 2021 at 8:06 PM Louis <..hidden..> wrote:
>
>       Greetings,
>
>       I was beginning to move from the 1.6 line when I encountered an error. I
>       was able to isolate the error to the upgrade from 1.6.27 -> 1.6.28 which
>       dies with:
>
>       Error!
>
>       Error applying upgrade script ./sql/changes/1.6/track-deleted-transactions.sql: ERROR: update or delete
>           on table "transactions" violates foreign key constraint
>           "file_transaction_ref_key_fkey" on table "file_transaction"
>
>       DETAIL: Key (id)=(17812) is still referenced from table "file_transaction". at
>            /usr/local/ledgersmb/tools/../lib/LedgerSMB/Database/Change.pm line 227.
>
>       dbversion: , company: 1.6.28
>
>
>       This happened at postgresql 9.6 and also at 11.
>
>       Can anyone help me past this issue?
>
>
> Yes, I think I can: instead of upgrading to 1.6.28, could you try upgrading to 1.6.31 or 1.6.32? There is a fix in .31
> which should fix this exact problem:https://github.com/ledgersmb/LedgerSMB/commit/846886b3e36bd32db9fb99125bae17633323a749#diff-ead07c84baac57a9542f388a07a2a
> 5209456ce790b04251bc9bd7d179ea85cb1R6
>
>
> Let me know if that solves your problem!
>
>
> Regards,
>
> --
> Bye,
> Erik.
>
> http://efficito.com -- Hosted accounting and ERP.
> Robust and Flexible. No vendor lock-in.
>
>

_______________________________________________
users mailing list -- ..hidden..
To unsubscribe send an email to ..hidden..