11:08 a.m.
Hi,
Can you help figure the issue here
journalctl reports:
Jul 15 15:01:59 vtsc-trove gitano[4753]: 4753.150159: Client connected from unknown ip as
lorry () Executing command: git-upload-pack '/vtsc-trove/local-config/lorries'
Jul 15 15:01:59 vtsc-trove lighttpd[465]: 2015-07-15 15:01:59: (mod_fastcgi.c.2673)
FastCGI-stderr: File
"/usr/lib/python2.7/site-packages/lorrycontroller/readconf.py", line 47, in run
Jul 15 15:01:59 vtsc-trove lighttpd[465]: 2015-07-15 15:01:59: (mod_fastcgi.c.2673)
FastCGI-stderr: File
"/usr/lib/python2.7/site-packages/lorrycontroller/readconf.py", line 104, in
get_confgit
Jul 15 15:01:59 vtsc-trove lighttpd[465]: 2015-07-15 15:01:59: (mod_fastcgi.c.2673)
FastCGI-stderr: File
"/usr/lib/python2.7/site-packages/lorrycontroller/readconf.py", line 128, in
update_confgit
My issue is /home/lorry/confgit/lorry-controller.conf never gets updated and retains older
configuration,
where as /home/git/repos/vtsc-trove/local-config/lorries.git has updated commits with
configuration changes.
Regards,
Madhu
12:25 p.m.
Hi Madhu!
On 15/07/15 16:08, Ravindran, Madhusudhanan (M.) wrote:
Hi,
Can you help figure the issue here
journalctl reports:
Jul 15 15:01:59 vtsc-trove gitano[4753]: 4753.150159: Client connected from unknown ip as
lorry () Executing command: git-upload-pack '/vtsc-trove/local-config/lorries'
Jul 15 15:01:59 vtsc-trove lighttpd[465]: 2015-07-15 15:01:59: (mod_fastcgi.c.2673)
FastCGI-stderr: File
"/usr/lib/python2.7/site-packages/lorrycontroller/readconf.py", line 47, in run
Jul 15 15:01:59 vtsc-trove lighttpd[465]: 2015-07-15 15:01:59: (mod_fastcgi.c.2673)
FastCGI-stderr: File
"/usr/lib/python2.7/site-packages/lorrycontroller/readconf.py", line 104, in
get_confgit
Jul 15 15:01:59 vtsc-trove lighttpd[465]: 2015-07-15 15:01:59: (mod_fastcgi.c.2673)
FastCGI-stderr: File
"/usr/lib/python2.7/site-packages/lorrycontroller/readconf.py", line 128, in
update_confgit
My issue is /home/lorry/confgit/lorry-controller.conf never gets updated and retains
older configuration,
where as /home/git/repos/vtsc-trove/local-config/lorries.git has updated commits with
configuration changes.
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?
Also, could you tell me what ref of lorry-controller is in use? The
'sha1' field in /baserock/lorry-controller-bins.meta will tell you.
Thanks!
Sam
--
Sam Thursfield, Codethink Ltd.
Office telephone: +44 161 236 5575
9:44 a.m.
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?
Also, could you tell me what ref of lorry-controller is in use? The
'sha1' field in /baserock/lorry-controller-bins.meta will tell you.
The sha1 showed as "d7ca3f2f14ad28437f7332ca387a790fecb8b081"
Regards,
Madhu
11:49 a.m.
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.
Good!
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?
The
> '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
http://wiki.baserock.org/guides/upgrade-trove/
--
Sam Thursfield, Codethink Ltd.
Office telephone: +44 161 236 5575
2546
days inactive
2548
days old
3 comments
2 participants
participants (2)
-
Ravindran, Madhusudhanan (M.) -
Sam Thursfield