Re: [go-cd] Re: Garbage Collecition in GO

[Chris Tamlyn]

thanks.  Looks better on the support pages now.  Let's see what happens at 
 7am.

On Thursday, 31 August 2017 09:29:47 UTC+1, Ketan Padegaonkar wrote:
>
> On Thu, Aug 31, 2017 at 1:31 PM Chris Tamlyn <chris...@gmail.com 
> > wrote:
>
>> Since I raised this issue we've actually switched to a Linux server so 
>> the mechanism is slightly different.  When I view my support page I see:
>>
>>   "-Dgo.config.repo.gc.periodic\u003dY",
>>   "-Dgo.config.repo.gc.cron\u003d0 0 7 1/1 \\* \\?",
>>
>> Those are CLI args string escaped. You probably need to look at the 
> section under "System Properties" to see the unescaped values and see if 
> they are valid expressions understood by quartz (
> http://www.quartz-scheduler.org/api/2.2.1/org/quartz/CronExpression.html)
>
> I'm seeing this on the build server at build.gocd.org:
>
> $ curl -s -uUSER:PASS https://build.gocd.org/go/api/support | jq 
> '.["Runtime Information"]["System Properties"]["go.config.repo.gc.cron"]'
> *"0 0 7/12 1/1 * ?"*
>
> The file /etc/default/go-server contains:
>
> export GO_SERVER_SYSTEM_PROPERTIES="-Dgo.config.repo.gc.periodic=true 
> -Dgo.config.repo.gc.cron='0 0 7/12 1/1 * ?' -Dgo.config.repo.gc.expire=10"
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[go-cd] Re: Garbage Collecition in GO

[Chris Tamlyn]

Since I raised this issue we've actually switched to a Linux server so the 
mechanism is slightly different.  When I view my support page I see:

  "-Dgo.config.repo.gc.periodic\u003dY",
  "-Dgo.config.repo.gc.cron\u003d0 0 7 1/1 \\* \\?",


Which makes me think I've got an issue with escape characters, as yours looks 
like a real cron expression.


I followed the doc's with their comments on escaping special characters


(added to /etc/defaults/go-server):


GO_SERVER_SYSTEM_PROPERTIES="$GO_SERVER_SYSTEM_PROPERTIES 
-Dgo.config.repo.gc.periodic=Y -Dgo.config.repo.gc.cron='0 0 7 1/1 \* \?'" 


On Thursday, 19 May 2016 08:56:55 UTC+1, Chris Tamlyn wrote:
>
> We started to get an error in GO around Garabge collection which directs 
> us to this link:
>
> https://docs.go.cd/current/advanced_usage/config_repo.html
>
> Has anyone else implemented this in Go before?  I'm not sure that I'm 
> reading the documentation correctly on how to set it up for GO.  I've read 
> it as you need to add those properties to your 'wrapper-properties' file 
> (we run on Windows).  So I've added the following 3 settings:
>
> go.config.repo.gc.periodic=Y
> go.config.repo.gc.aggressive=Y
> go.config.repo.gc.cron=0 0 7 ? * SUN
>
> But I wasn't sure if this was the correct place of if they should be 
> Windows Environment variables.  Has anyone got any experience setting this 
> up and could help guide us?
>
> Many Thanks
>
> Chris
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-cd] Re: Garbage Collecition in GO

[Chris Tamlyn]

Once you set the config as above, do you see the settings in 
https://:8154/go/api/support?

I've followed your steps (I think) but just trying to verify if the 
settings are being read by the server.  I don't seem to see anything on the 
support page.

thanks

Chris

On Tuesday, 29 August 2017 20:43:26 UTC+1, keithl...@gmail.com wrote:
>
> Also an added quirkiness, with the below content, only the 
> go.config.repo.gc.cron  property is persisted but not the 
> go.config.repo.gc.periodic property.  I added a comment line at the very 
> top of the file and it works.
>
> On Tuesday, August 29, 2017 at 12:04:50 PM UTC-7, keithl...@gmail.com 
> wrote:
>>
>> Thank you Ketan and Aravind,
>>
>> With the #include directive in place, the final version that works is 
>> (note the double quotes) as below. 
>>
>> wrapper.java.additional.16=-Dgo.config.repo.gc.periodic=Y
>> wrapper.java.additional.17=-Dgo.config.repo.gc.cron="0 0 3 * * ?"
>>
>> So the confusion here is that, the sample showing cron with escape 
>> characters wrapped in single quotes and outer double quotes, when that did 
>> not work and the general eventlog error of (The Go Server service 
>> terminated with the following service-specific error: Incorrect function. 
>> was such that wrong function used), I went down the wrong path of the 
>> uncommenting #include. 
>>
>> Anyway, thanks for the quick reply and the help you gave me here.
>>
>> Appreciatively,
>> Keith
>>
>>
>>
>>
>>
>>
>> On Tuesday, August 29, 2017 at 9:45:21 AM UTC-7, Ketan Padegaonkar wrote:
>>>
>>> On Tue, Aug 29, 2017 at 10:07 PM Aravind SV  
>>> wrote:
>>>
 You shouldn't remove the "#" before the "#include". Though the rest of 
 the lines prefixed with a "#" are comments, in the case of the include 
 directive, it is: "#include", as you can see here: 
 https://wrapper.tanukisoftware.com/doc/english/props-cascading.html

>>>
>>> Gah! Perhaps we need to add a comment to that file to avoid someone 
>>> tripping on the same thing... 
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.