[Expo-tech] Can someone re-start troggle on the server

[Philip Sargent (Gmail)]

Yes thanks all working now.
Have a look at http://expo.survex.com/pathsreport/

(make sure it is http:// otherwise the CSS fails)

But I still can't see why my install fails to serve any /expofiles/ but gets
intercepted by troggle with a 
"Page not found expofiles/" when it is exactly the same code as on the
server. Must be a PATHS 
problem but IU just can't see it.

Philip

-----Original Message-----
From: Wookey [mailto:wookey at wookware.org] 
Sent: 09 March 2020 17:44
To: Philip Sargent (Gmail)
Cc: expo-tech at lists.wookware.org
Subject: Re: [Expo-tech] Can someone re-start troggle on the server

On 2020-03-09 16:57 -0000, Philip Sargent (Gmail) wrote:
> I fixed a bug in the new report
> https://expo.survex.com/pathsreport/

> but troggle is still seeing the old code, even though git uploaded it 
> correctly.

It's currently giving
"NameError at /pathsreport/
global name 'EMAIL_HOST' is not defined"

Is that what you mean by 'seeing the old code'?

After an apache restart the message has changed to:
NameError at /pathsreport/

global name 'EMAIL_HOST_USER' is not defined (i.e the next item in the
list).

EMAIL_HOST_USER is still used, in: core/views_logbooks.py

> I presume that the views_ need to be reloaded ?

I think just restarting apache (with:)
apache2ctl graceful
will make it re-read the troggle code. BICBW.

Hmm. not necessarily, but an
apache2ctl stop
apache2ctl start

seems to have done the trick (unless someone else with more clue is
simultaneously fiddling)

> Can someone re-start troggle on the server or tell me how to do it ?
> (I'm using the SQLite option at home)

What are you trying to do? You seem to have removed two variables, one of
which which was indeed not actually used anywhere. (It presumably used to be
used for sending mail when we were inside the university and did not have a
local mail server config, because the machine was not allowed to send
email).

I tried removing EMAIL_HOST_USER from the pathreport pathdict, to see if
that was in fact the right thing to do, and after restarting apache that
seems to mean that the pathreport reports paths, which I guess is what it
was supposed to do.

Wookey
--
Principal hats:  Linaro, Debian, Wookware, ARM http://wookware.org/