Go-Agent always missing after restart

518 views
Skip to first unread message

Rafael Pólit

unread,
Apr 14, 2016, 3:16:09 PM4/14/16
to go-cd
Good afternoon friends,

I am having issues with my GoCD.  My go-server goes up as expected, but the go-agent is always missing after a restart.  I have tried with:

$ sudo update-rc.d go-agent defaults

But it is already registered.  I read somewhere that you can assign it a 'Delayed start', but cannot find any info on how to do that, or is there any other obvious step that I forgot?.

Thanks for the feedback!

Best regards,
Rafa. 

Jyoti Singh

unread,
Apr 15, 2016, 8:16:32 AM4/15/16
to go...@googlegroups.com
Did you check the agent logs to see why is it missing? 
An agent can run independent of a server, and it would successfully connect to the server whenever the server comes back online. Not sure if I understand the need for a delayed start.

--
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+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Cheers,
Jyoti

Rafael Pólit

unread,
Apr 19, 2016, 5:53:35 PM4/19/16
to go...@googlegroups.com
Thanks for the answer and sorry for the late reply.  Had not restarted the server in a while, this is still an issue.

Just to be clear, it is missing because the Ubuntu service is not automatically starting upon system restart.  It never starts unless I run explicitly:

/etc/init.d/go-agent start

How can I make it run upon system restart? Thanks.

--
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/obicx6hYCKA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to go-cd+un...@googlegroups.com.

Jyoti Singh

unread,
Apr 21, 2016, 4:04:24 AM4/21/16
to go...@googlegroups.com
That should happen automatically for run levels -> 2 3 4 5 unless it has been explicitly disabled by someone. 
Check current runlevel and chkconfig/update-rc.d, that might give you a hint on why the service is not being started automatically. 


Reply all
Reply to author
Forward
0 new messages