GoCD installation hung

[Ash]

Installtion of GOCD latest version on RHEL8 is not progressing with no database to upgrade. JDK17

2024-10-18 13:11:07,901 INFO  [WrapperJarAppMain] DatabaseMigrator:53 - WARNING: Shutting down your server at this point will lead to a database corruption. Please wait until the database upgrade completes.
2024-10-18 13:11:07,901 INFO  [WrapperJarAppMain] DatabaseMigrator:53 - ************************************************************************
2024-10-18 13:30:35,550 INFO  [WrapperJarAppMain] JettyServer:194 - Configuring Jetty using /etc/go/jetty.xml
2024-10-18 13:30:35,653 WARN  [WrapperJarAppMain] Server:366 - ErrorPageMapper not supported for Server level Error Handling
2024-10-18 13:30:35,770 WARN  [WrapperJarAppMain] AbstractHandler:88 - No Server set for ResourceHandler@22ca7374{STOPPED}
2024-10-18 13:30:42,674 WARN  [WrapperJarAppMain] ConnectionManager:117 - The file /etc/go/db.properties specified by `go.db.config` does not exist.
2024-10-18 13:30:43,151 INFO  [WrapperJarAppMain] DatabaseMigrator:44 - Upgrading database, this might take a while depending on the size of the database.
2024-10-18 13:30:43,153 INFO  [WrapperJarAppMain] DatabaseMigrator:53 - ************************************************************************
2024-10-18 13:30:43,153 INFO  [WrapperJarAppMain] DatabaseMigrator:53 - WARNING: Shutting down your server at this point will lead to a database corruption. Please wait until the database upgrade completes.
2024-10-18 13:30:43,153 INFO  [WrapperJarAppMain] DatabaseMigrator:53 - ************************************************************************

[Chad Wilson]

Hi Ash

What do you mean by "no database to upgrade"?

• Do you mean it is a fresh install? Or that you already upgraded the DB, so should have nothing to do now?
  
• Did you accidentally interrupt a previous upgrade/install part way through?
• if you are using the default H2DB on-disk database (not mysql/postgres) you can probably solve this by stopping gocd and removing the database so it starts with a fresh DB. Don't do this if I misinterpreted and you are trying to upgrade an existing database!
• Are you using some kind of network storage for GoCD's database/config, or just local disk?
  

If you are using postgres/mysql - will perhaps need more detail about your environment and what you did to get set up.

-Chad

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/55384ae2-207e-4869-88ef-82b59a473dadn%40googlegroups.com.

[Ash]

Fresh install of gocd on RHEl 8. Not an existing upgrade

I have tried with postgress and h2 as well. The logs are the same

tried with following config in /etc/go/db.properties but no luck. Disabled the firewall, no luck.

db.driver=org.postgresql.Driver
db.url=jdbc:postgresql://localhost:5432/gocd
db.user=gocd_database_user
db.password=gocd_database_password

I have confirmed that postgress i able to login using the above creds

[Chad Wilson]

Hmm, sorry to hear that.

Do the logs earlier than that you shared give you confidence it is trying to use the db type of your choice? (sorry, can't recall what it logs about the detected database type). Just so we know whether the instance we are debugging is H2 or Postgres.

At a time when it is "stuck", could you find the main java process and send a `kill -3` / SIGQUIT to it? This should cause it to dump all the thread state into STDOUT/STDERR and should appear in one of the logs. If you could share that it might help me figure out what is happening. Seems more like connectivity being stuck (or not timing out) since it should start logging each of the DB update commands as it applies them after that. However, that should not be a problem with H2.

-Chad

To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/41c64cba-1bb2-4d92-a6e7-af85a7b1c9b5n%40googlegroups.com.