Ah, I get it now... all those errors are references to menu_node entries
that don't exist. Pg-database.sql fills menu_node with the following
(clipped for brevity):
COPY menu_node (id, label, parent, "position") FROM stdin;
91 Search Groups 77 6
92 Search Pricegroups 77 8
6 Import Inventory 77 13
106 Search 98 1
etc...
But my lsmb_roles.sql refers to a number of nodes that do not exist in that
list. Specifically, here are the node ids that are missing, along with the
role names (christest02 is my db name). Does anyone know if these are
referring to menu nodes I should have, or else if perhaps the ids are
incorrect and the menu nodes do exist but have different ids?
28 'lsmb_christest02__ap_transaction_list'
29 'lsmb_christest02__ap_transaction_list'
17 'lsmb_christest02__pos_enter'
18 'lsmb_christest02__pos_enter'
18 'lsmb_christest02__list_all_open'
87 'lsmb_christest02__part_edit'
88 'lsmb_christest02__part_edit'
89 'lsmb_christest02__part_edit'
90 'lsmb_christest02__part_edit'
91 'lsmb_christest02__part_edit'
88 'lsmb_christest02__inventory_reports'
94 'lsmb_christest02__inventory_reports'
220 'lsmb_christest02__users_manage'
221 'lsmb_christest02__users_manage'
Thanks!
On Wed, May 15, 2013 at 12:02 PM, Chris Calef <[email protected]> wrote:
> Hi again,
>
> Sorry, got distracted away from keys for a day or two, but I just updated
> and tried my setup.pl again, and _almost_ all my errors went away with
> the recent changes to Reconciliation.sql. (Yay!)
>
> The main one that is still shows up repeatedly looks like this:
>
> psql:/tmp/ledgersmb/lsmb_roles.sql:635: ERROR: insert or update on
> table "menu_acl" violates foreign key constraint "menu_acl_node_id_fkey"
> DETAIL: Key (node_id)=(17) is not present in table "menu_node".
> psql:/tmp/ledgersmb/lsmb_roles.sql:637: ERROR: insert or update on
> table "menu_acl" violates foreign key constraint "menu_acl_node_id_fkey"
> DETAIL: Key (node_id)=(18) is not present in table "menu_node".
>
>
> Which seems a little weird, I'm no SQL expert but menu_node and menu_acl
> in my database both have the same foreign key definition for
> "menu_acl_node_id_fkey": "FOREIGN KEY (node_id) REFERENCES
> menu_node(id)". Unless it's trying to refer to the entire string
> "(node_id)=(17)" as a key(??)
>
>
>
> Also, my dblog concludes with this error, I don't know if it's related to
> the other one or an independent problem:
>
> psql:/tmp/ledgersmb/lsmb_roles.sql:1651: ERROR: syntax error at or near
> "END"
> LINE 10: END IF;
> ^
> psql:/tmp/ledgersmb/lsmb_roles.sql:1655: ERROR: function
> tg_enforce_perms_eclass() does not exist
> psql:/tmp/ledgersmb/lsmb_roles.sql:1659: ERROR: function
> tg_enforce_perms_eclass() does not exist
>
>
> Thanks for all your work!
>
> Chris
>
>
> On Sun, May 12, 2013 at 12:38 PM, Chris Calef <[email protected]>wrote:
>
>> Oh, whoops, I tried to attach all those files for you, but my message is
>> now in purgatory awaiting moderator approval, because it was bigger than
>> 40k. Here, I'll try just sending the one dblog file, it was most
>> interesting... also I chopped out a lot of repetitive SQL like CREATE
>> FUNCTION, GRANT, COMMENT just to get the file size down. All the errors
>> and warnings are untouched.
>>
>>
>>
>>
>> On Sun, May 12, 2013 at 11:23 AM, Chris Calef <[email protected]>wrote:
>>
>>> Yes, sir! Thanks for sticking with me!
>>>
>>> Turns out there are several errors in there. I'll attach all four log
>>> files, then go see if I can figure anything out on my own. In dblog, a
>>> number of transactions got cancelled, due to a large number of entities
>>> either already existing, or not existing. Do these make any sense to you?
>>>
>>> Chris
>>>
>>>
>>> On Sun, May 12, 2013 at 2:11 AM, Erik Huelsmann <[email protected]>wrote:
>>>
>>>>
>>>> On Sun, May 12, 2013 at 12:02 AM, Chris Calef <[email protected]>wrote:
>>>>
>>>>> Hm, well I got a different set of errors this time anyway. Attached
>>>>> is another version of fullpermissions.error.log.
>>>>>
>>>>> The first error claims that my database does not exist, but it did get
>>>>> created. Again I got as far as the create user screen before crashing.
>>>>> The database has all the tables, but the users table is still empty, no
>>>>> user got created.
>>>>>
>>>>>
>>>> When creating a database, setup.pl also creates a number of logs in
>>>> /tmp/ledgersmb/ (on unix); you can find more errors and issues there. So
>>>> far, I can only see from your logs that there may be interesting
>>>> information (such as errors) in those logs. Could you go through those and
>>>> search for transaction aborted errors?
>>>>
>>>> Thanks!
>>>>
>>>> Bye,
>>>>
>>>> Erik.
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Learn Graph Databases - Download FREE O'Reilly Book
>>>> "Graph Databases" is the definitive new guide to graph databases and
>>>> their applications. This 200-page book is written by three acclaimed
>>>> leaders in the field. The early access version is available now.
>>>> Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
>>>> _______________________________________________
>>>> Ledger-smb-devel mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
>>>>
>>>>
>>>
>>
>
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Ledger-smb-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
