There is an open issue for that now: https://github.com/gocd/gocd/issues/2464
Thanks, Duda. On Wednesday, July 20, 2016 at 5:36:03 PM UTC-5, [email protected] wrote: > > Ok, I was able to solve the problem with Aravind's help > > I was getting the same stacktrace as you @Gerd. In the go-server, my new > agent was in 'Pending' state. I was able to then just enable that agent and > now it is working just fine. > > Cheers, > > Duda. > > On Wednesday, July 20, 2016 at 5:21:48 PM UTC-5, [email protected] > wrote: >> >> @Gerd: Did you solve your problem? I'm having the same issue... >> >> On Monday, July 18, 2016 at 2:41:20 AM UTC-5, Gerd Katzenbeisser wrote: >>> >>> Thanks for the quick reply. I only had a look at the config folder and >>> missed the file in the agents dir. >>> >>> 2016-07-18 9:07 GMT+02:00 Ketan Padegaonkar <[email protected]>: >>> >>>> You want to configure it using `go-agent-log4j.properties` in the >>>> directory where you installed the go agent. >>>> >>>> On Mon, Jul 18, 2016 at 12:33 PM Gerd Katzenbeisser < >>>> [email protected]> wrote: >>>> >>>>> Hi @all! >>>>> >>>>> The agents on one of our build cannot connect to the server anymore. >>>>> >>>>> 2016-07-18 08:49:36,113 [loopThread] INFO >>>>> go.agent.service.SslInfrastructureService:93 - [Agent Registration] >>>>> Starting to register agent >>>>> 2016-07-18 08:49:36,129 [loopThread] ERROR >>>>> go.agent.service.SslInfrastructureService:112 - [Agent Registration] >>>>> There >>>>> was a problem registering with the go server. >>>>> java.lang.StringIndexOutOfBoundsException: String index out of range: >>>>> -4 >>>>> at java.lang.String.charAt(Unknown Source) >>>>> at org.bouncycastle.util.encoders.Base64Encoder.decode(Unknown Source) >>>>> at org.bouncycastle.util.encoders.Base64.decode(Unknown Source) >>>>> at org.bouncycastle.util.io.pem.PemReader.loadObject(Unknown Source) >>>>> at org.bouncycastle.util.io.pem.PemReader.readPemObject(Unknown Source) >>>>> at >>>>> com.thoughtworks.go.security.Registration.fromJson(Registration.java:49) >>>>> >>>>> I want to enable the debug log level to get more infos about what is >>>>> going wrong. But I don't know how to do that. What I tried so far is: >>>>> >>>>> >>>>> - Change all lines mentioning log level INFO to DEBUG in >>>>> config/log4j.properties >>>>> - Uncomment the line mentioning Agent Debug in wrapper-agent.conf >>>>> set.JVM_DEBUG=-Xdebug >>>>> >>>>> -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=%JVM_DEBUG_PORT% >>>>> - Set all wrapper.*.loglevel to DEBUG in wrapper-agent.conf >>>>> >>>>> But I still only get Info level. How do I correctly enable the debug >>>>> log level? >>>>> >>>>> greets >>>>> Gerd >>>>> >>>>> -- >>>>> 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 [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "go-cd" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/go-cd/zLqeECge1t4/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
