On 4/1/19 7:51 PM, JonGeorg SageLibrary wrote:
> When I look at syslog it shows the fine generator runs at :05 and :40
> every hour. 
> 
> My understanding was that the lock file was only present when it was
> actively running. I tested that today at 16:40 and it was present for
> about 90 seconds or so before deleting itself.

Mine runs for nearly an hour, but yeah.

> 
> As far as attempting to run the command sudo
> /openils/bin/fine_generator.pl <http://fine_generator.pl> as root, I get
> the response bootstrap config required. However, that is the same
> response I had gotten after a restart of the server in the past when it
> was working properly. And when I tried to research that response, I
> couldn't find anything useful in the forums, and since it was working
> correctly as a cronjob I didn't pursue it.

/openils/bin/fine_generator.pl /openils/conf/opensrf_cor.xml

That command line should work as the opensrf user. You don't need, nor
want, to use sudo when running these commands as the opensrf user.

Have you checked the stop_fines field on the circulations that are not
calculating fines?



> 
> -Jon
> 
> On Mon, Apr 1, 2019 at 3:39 PM Jason Stephenson <ja...@sigio.com
> <mailto:ja...@sigio.com>> wrote:
> 
>     On 4/1/19 4:50 PM, JonGeorg SageLibrary wrote:
>     > No, there is no /tmp/generate_fines-LOCK file. 
>     >
>     > Yes, I get a PID when running sudo pgrep -af fine
> 
>     You should get more than a PID.  It should include the command line that
>     started the fine generator, unless your pgrep doesn't process one of the
>     options correctly.
> 
>     Also, if the fine generator is running, the lock file should exist.  If
>     it doesn't, then something is wrong.  However, I've never seen that
>     case, so I don't know what is wrong.
> 
>     What happens if you run the fine generator from the command line?
> 
>     Jason
> 

Reply via email to