On 17/07/15 14:44, Ravindran, Madhusudhanan (M.) wrote:
On Wed, Jul 15, 2015 at 05:25:15PM +0100, Sam Thursfield wrote:
> There is a service called lorry-controller-readconf.service which
> runs once per minute to update the lorry-controller configuration.
> It seems like the API call made by that service is causing a crash
> in lorry-controller. The journal output you shared seems to be a
> backtrace for part of that crash, but it doesn't show the actual
> exception, so it's not really enough for me to be able to debug. Do
> you have the full backtrace including the exception message?
Sam, I have tried deleting the /home/lorry/confgit manually and
that fixed the problem for now.
I could not locate more log from the journalctl related to exception
is there any log file I can refer to?
You could look in /home/lorry/webapp.log. However, all the info should
be in the journal, I think... maybe it is just not logged.
> Also, could you tell me what ref of lorry-controller is in use?
> 'sha1' field in /baserock/lorry-controller-bins.meta will tell you.
The sha1 showed as "d7ca3f2f14ad28437f7332ca387a790fecb8b081"
OK. There have been some bugs fixed in lorry-controller since then, but
nothing I could see that might have fixed this issue. It's still good to
keep your Trove up to date, though ... see
Sam Thursfield, Codethink Ltd.
Office telephone: +44 161 236 5575