Vagrant agents do not auto-start

adoptium / infrastructure

This repo contains all information about machine maintenance.

Apache License 2.0

86 stars 101 forks source link

Closed sxa closed 5 days ago

sxa commented 1 year ago

Please put the system name in the title of this issue.
Link to any log file showing the problem:
Please describe the issue: Spotted during last jenkins restart. At the moment the five jenkins agents for running the VPC jobs are started via the startjenkins.sh script via nohup but are not configured to automatically restart. These should be switched over to using services to ensure that they are all restarted when required.

I've restarted them manually for now.

sxa commented 1 year ago

Deferred to March pending resolution of instability in VPC job.

sxa commented 1 year ago

Tried with vagrant1 and vagrant2 using jenkins1 and jenkins2 services but neither are starting up properly at present.

sxa commented 1 week ago

@steelhead31 Have the jenkins agents on the replacement vagrant machine been set up to restart automatically?

steelhead31 commented 5 days ago

No, Its top of my to do list for today :)

steelhead31 commented 5 days ago

Services created for vagrant1 -> vagrant4 inclusive, set to run on restart.