RE: [go-cd] Issues with backups on Go 22.2 and PostgreSQL v12

2022-11-02 Thread chantryc
Sure! I’d be happy to drop it in and see if that works! I can double check on the folder creation that way as well. I haven’t entirely worked out building the package myself so if you have an installer I can run or just the files to replace and instructions on where they need to go I’m happy to

Re: [go-cd] Issues with backups on Go 22.2 and PostgreSQL v12

2022-11-02 Thread Chad Wilson
With a bit of quick pg_dump testing on Windows (via choco install postgresql12/choco install postgresql14) without actually integrating with GoCD) I can confirm the utility complains about the order of the positional (non-option) dbname arguments in ways that the same utility on MacOS does not. Onl

Re: [go-cd] Issues with backups on Go 22.2 and PostgreSQL v12

2022-11-02 Thread Chad Wilson
Technically speaking, the docs say the dbname without --dbname= should be the last argument after all connection options, which GoCD doesn't respect. Possibly pg_dump is more flexible on other OSes than Windows? If you move "gocd" to the end of the command line you will probably find it works. If

Re: [go-cd] Issues with backups on Go 22.2 and PostgreSQL v12

2022-11-02 Thread Funkycybermonk
It looks like the file version is 12.0.12.0. I'm using the version that shipped with the PostgreSQL 12 installer. I can downgrade to a lower PostgreSQL version if this is an issue with this release of pg_dump. The message I get when constructing the command line using as-is from the logs i

Re: [go-cd] Issues with backups on Go 22.2 and PostgreSQL v12

2022-11-02 Thread Ketan Padegaonkar
What version of pg_dump are you using? According to https://www.postgresql.org/docs/current/app-pgdump.html, the command line string looks OK. But we've not tested this on windows. - Ketan On Wed, Nov 2, 2022 at 4:31 AM Funkycybermonk wrote: > Hello! > > New upgrade going from GoCD 20.1 to 22

Re: [go-cd] Need help in resolving few issues with GoCD 20.4

2022-11-02 Thread Chad Wilson
The flyweight is just a temporary repository clone the GoCD server creates to keep track of changes on the remote repository and work out which pipelines need triggering due to changes. If you are getting "connection reset by peer" I suggest you investigate the network connectivity to that "peer"

Re: [go-cd] Need help in resolving few issues with GoCD 20.4

2022-11-02 Thread SATYA R
Hi Ashwanth, Thanks alot for the quick response. Here is what i found from the server.log *2022-11-02 08:43:20,092 WARN [131@MessageListener for MaterialUpdateListener] MaterialDatabaseUpdater:127 - [Material Update] Modification check failed for material: URL: gitit.l\tcom:flsndfydta/flydtadh

Re: [go-cd] Need help in resolving few issues with GoCD 20.4

2022-11-02 Thread 'Ashwanth Kumar' via go-cd
>From the attached screenshot the error seems like something to do with a network configuration. > kex_exchange_identification: read: Connection reset by peer First answer on SO also says the same. Also if you can check the go-server.log, it might have addit

[go-cd] Need help in resolving few issues with GoCD 20.4

2022-11-02 Thread SATYA R
Hi Everyone, Recently our GoCD 18.8 server got destroyed and we installed new version of GoCD 20.4 in new mac server and restored the backup of 18.8. We are able to get all the pipelines back and running. But we are facing few issues with the new server. 1. The pipelines Auto-trigger is not hap