[OPEN-ILS-DEV] Re: Build errors on Debian
Bill Erickson
billserickson at gmail.com
Fri Mar 31 08:45:48 EST 2006
I was running the autogen.sh directly. It would execute fine, up unto
> the org_tree_js.pl.
Heh.. I finally went back and read your previous email.. sorry 'bout that.
The config looks fine.. the next thing I would recommend is to check for
startup errors either in osrfsys.log or in the 'unix' logs (usually found in
/openil/var/log/*_unix.log). It's also important for the
open-ils.storageapp to be configured to run in your
openils.xml config file (the section near the bottom with the host
configs). If none of this helps, could you also send your
openils.xmlconfig along?
A lot has changed since Alpha, indeed...
-bill
===bootstrap.conf===
> # ----------------------------------------------------------
> # bootstrap config file
> # ----------------------------------------------------------
> [bootstrap]
>
> # location of the opensrf.xml config file
> settings_config = /openils/conf/openils.xml
>
> # log files directory
> log_dir = /openils/var/log
>
> ## Log file is either a file name or syslog:<facility>
> logfile = osrfysys.log
> #logfile = syslog:local0
>
> # defines the syslog facility for the activity log
> actlog = activity.log
> #actlog = syslog:local1
>
> # log level
> #debug = WARN
> #debug = INFO
> debug = DEBUG
> #debug = INTERNAL
>
> # the jabber login of the router (changing this will likely cause
> problems)
> router_name = router
>
> # all jabber domains we want our app to connect to
> list:domains = evergreen.mcmorrisfamily.net
>
> # jabber login
> username = juser
>
> # jabber password
> passwd = jpass
>
> # if port is non-numeric (e.g. /tmp/mysock.sock) then we will attempt to
> # connect to the specified string as a unix socket file
> # This works with Chop Chop jabber only (opensrf custom jabber server)
> port = 5222
>
> # --------------------------------------
>
> # log file names
> [logs]
> debug = debug.log
> error = error.log
> transport = transport.log
> message = message.log
> method = method.log
> trace = trace.log
> opac = opac.log
>
>
> ======================
>
> It looks to me like $app isn't getting properly defined in
> Application.pm. I guess nobody had those issues there?
>
> --Don
>
> On 3/31/06, Bill Erickson <billserickson at gmail.com> wrote:
> > Don
> >
> > It's not immediately obvious what's causing this particular problem. I
> > usually run 'autogen.sh' directly (instead of org_tree_js.pl), which
> then
> > runs the org-tree builder and updates the fieldmapper javascript. I
> would
> > suggest running autogen.sh from within your bin directory and seeing if
> that
> > helps. (Of course, that doesn't change the fact that what you're doing
> > should work..). If the errors continue, could you send your
> bootstrap.conf
> > file along as well?
> >
> > Let us know how it's going..
> >
> >
> > On 3/31/06, Don McMorris <don.mcmorris at gmail.com> wrote:
> > > I found some clues to my issue...:
> > >
> > > ==Application.PM==
> > > 105 $log->debug( " * Looking up $method_name inside $app",
> > DEBUG);
> > > 106
> > > 107 my $method_proto =
> > $session->last_message_api_level;
> > > 108 $log->debug( " * Method API Level [$method_proto]",
> DEBUG);
> > > 109
> > > 110 my $coderef = $app->method_lookup( $method_name,
> > > $method_proto, 1, 1 );
> > > ============
> > >
> > > ==osrfysys.log==
> > > [2006-3-31 6:48:34] org_tree_js.pl [DEBG:29809:::] In
> > Application::handler()
> > > [2006-3-31 6:48:34] org_tree_js.pl [DEBG:29809:::] We got a REQUEST:
> > >
> > open-ils.storage.direct.actor.org_unit.retrieve.all.atomic
> > > [2006-3-31 6:48:34] org_tree_js.pl [DEBG:29809:::] * Looking up
> > >
> > open-ils.storage.direct.actor.org_unit.retrieve.all.atomic
> > inside
> > > [2006-3-31 6:48:34] org_tree_js.pl [DEBG:29809:::] * Method API Level
> [1]
> > > ============
> > >
> > > Again, the issue
> > > =============
> > > evergreen:/openils/bin# perl org_tree_js.pl
> /openils/conf/bootstrap.conf
> > > Use of uninitialized value in concatenation (.) or string at
> > > /etc/perl/OpenSRF/Application.pm line 105.
> > > Can't call method "method_lookup" on an undefined value at
> > > /etc/perl/OpenSRF/Application.pm line 110.
> > > evergreen:/openils/bin#
> > > =============
> > >
> > > It appears to me that $app isn't defined for whatever reason (notice
> > > the log entry
> > "open-ils.storage.direct.actor.org_unit.retrieve.all.atomic
> > > inside"... immediately following that entry should be the value of
> > > $app, which apparently is nothing.
> > >
> > > Comments?
> > >
> > >
> > >
> > > On 3/30/06, Don McMorris <don.mcmorris at gmail.com> wrote:
> > > > I ran make install again (putty had a little hickup, so I was forced
> > > > to close it). It seems I'm getting a lot of "already exist" errors
> > > > (which was expected). No "real" errors. Seems I'm set for now.
> > > >
> > > > I'll keep you posted on my progress. Let me know if there's
> anything I
> > can do.
> > > >
> > > > --Don
> > > >
> > > > On 3/30/06, Mike Rylander <mrylander at gmail.com> wrote:
> > > > > On 3/30/06, Don McMorris < don.mcmorris at gmail.com> wrote:
> > > > > > Another DUH moment. Apparently, since the documentation was
> > created,
> > > > > > there have been some dependencies added. Now, I'm executing
> > > > > > make_install, and I'm getting some errors...
> > > > > >
> > > > > > psql:005.schema.actors.sql:1: ERROR: schema "actor" does not
> exist
> > > > > > psql:005.schema.actors.sql:65: ERROR: schema "config" does not
> > exist
> > > > > > psql: 006.schema.permissions.sql:1: ERROR: schema "permission"
> does
> > not exist
> > > > > > psql:006.schema.permissions.sql:121: ERROR: schema "actor" does
> not
> > exist
> > > > > > psql:010.schema.biblio.sql :1: ERROR: schema "biblio" does not
> > exist
> > > > > > psql:011.schema.authority.sql:1: ERROR: schema "authority" does
> not
> > exist
> > > > > > psql:040.schema.asset.sql:1: ERROR: schema "asset" does not
> exist
> > > > >
> > > > > Actually, that's fine. There unconditional DROP SCHEMA commands
> at
> > > > > the top of each of those files which will fail on an empty
> database,
> > > > > which is ok.
> > > > > >
> > > > > > A lot has been snipped out. If you need more, let me know.
> > > > > >
> > > > >
> > > > > I would be interested in seeing the any errors from psql other
> than
> > > > > 'ERROR: schema "..." does not exist', however, since we haven't
> > > > > really done a full, ground up database install in some time.
> > > > >
> > > > >
> > > > > > Did I skip a step somewhere?
> > > > >
> > > > > I don't think so. :)
> > > > >
> > > > > >
> > > > > > --Don
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Mike Rylander
> > > > > mrylander at gmail.com
> > > > > GPLS -- PINES Development
> > > > > Database Developer
> > > > > http://open-ils.org
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Bill Erickson
> > PINES Systems Developer
> > Georgia Public Library Service
> > billserickson at gmail.com
> > http://open-ils.org
>
--
Bill Erickson
PINES Systems Developer
Georgia Public Library Service
billserickson at gmail.com
http://open-ils.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20060331/f9b6be39/attachment-0001.html
More information about the Open-ils-dev
mailing list