Hi again,The main one that is still shows up repeatedly looks like this:
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!)
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!ChrisOn Sun, May 12, 2013 at 12:38 PM, Chris Calef <..hidden..> 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 <..hidden..> wrote:
Yes, sir! Thanks for sticking with me!Chris
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?
On Sun, May 12, 2013 at 2:11 AM, Erik Huelsmann <..hidden..> wrote:
On Sun, May 12, 2013 at 12:02 AM, Chris Calef <..hidden..> 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