On Tue, 8 Oct 2013 17:48:18 +0100 Dean Arnold <dean.arn...@arm.com> wrote:
> Hi Neil, *Please* keep the list in the loop. I am not the sole point of contact for this issue. > The reason the scheduler log wasn't present is because my scheduler > is crashing when I try to run it. Unfortunately the upstart commands > didn't seem to want to output the failure to me. It's a daemon, stdout and stderr are closed for all daemons - this isn't confined to upstart. That is why I advised running the command manually.... > When I attempted to launch the scheduler manually I was able to > detect from the command line output that the initial problem was due > to the postgres database not accepting TCP/IP connections on port > 5432. If you had an older version of postgresql ever installed at the same time as a new version, postgresql will change that to 5433, then 5434 and so on for each one. This is standard postgresql behaviour and nothing to do with LAVA. > WARNING:root:This instance will not use sentry as SENTRY_DSN is not > configured execvp: No such file or directory > 2013-10-08 16:26:48,742 [ERROR] > [lava_scheduler_daemon.job.SchedulerMonitorPP] scheduler monitor for > pdswlava-vetc2-04 crashed: [Failure instance: Traceback (failure with > no frames): <class 'twisted.internet.error.ProcessTerminated'>: A > process has ended with a probable error condition: process ended with > exit code 1. ] 2013-10-08 16:26:48,864 [ERROR] [sentry.errors] No > servers configured, and sentry not installed. Cannot send message No > servers configured, and sentry not installed. Cannot send message Looks like a django error - your database connection is still not correct. > Is this something you have seen before? No. I just googled SENTRY_DSN. > Did you need to install any > extra packages outside of what the lava-deployment-tool provides when > running the setupworker/installworker commands? No - however, if you have a postgresql server installed on the worker, it is not required. > Could I have missed > a configuration step somewhere? The initial use of setup instead of setupworker could have messed up the database configuration on the worker. It just looks like the worker cannot find the database. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
_______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
