I've done the most minimum viable change on a working project, simply changing the version of Rails to 6 from 5. A project that has been working fine for years now fails bitbucket builds with ** Execute db:create could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket How does one debug this? Works on developer machines, was working fine on pipelines until the gem change. Can confirm that postgresql is up and running. What documentation exists to debug the internals? Is it possible to log in to bitbucket's pipeline at some point? There's a doc on how to "test your pipeline locally" but it's not failing locally.

Hi Jack, Apologies for the late reply, I was out of office. As I mentioned in my previous reply, if the repo belongs to a workspace on a paid billing plan, you can create a ticket with the support team via https://support.atlassian.com/contact/#/ to request guidance about debugging. In "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. If the repo belongs to a workspace on the free plan, I would suggest upgrading to a paid billing plan so you can create a ticket. If we have an open support ticket, the engineer working on your case will be able to access the build logs. The ticket will be visible only to you and Atlassian staff, so you can share more details (like the commands you use to debug locally with Docker and their output) and they won't be publicly visible. The support I can provide here is limited without access to your yml file, and the build logs and without more details on your attempt to debug this locally with Docker. Kind regards, Theodora

It works for all branches except a new branch which uses Rails 6. I have confirmed it attempts to connect EXACTLY the same way. I'm stumped. I've tried to figure out what the heck is going on.

Hi Jack, I saw your comment and you mention trying this on your machine. My question concerned rerunning the last successful build in Pipelines (not locally), to confirm if it's still working or not (if not, perhaps something on our side may have caused the issue). If you open a Pipelines build on Bitbucket website, there is an option Rerun next to the build number. Could you try that for the last successful build and let me know if the rerun is also successful or not? If the repo belongs to a workspace on a paid billing plan, you can also create a ticket with the support team via https://support.atlassian.com/contact/#/ to request guidance about debugging. Kind regards, Theodora

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Simple Rails upgrade breaks Bitbucket pipeline

Jack Phantom

I've done the most minimum viable change on a working project, simply changing the version of Rails to 6 from 5.

A project that has been working fine for years now fails bitbucket builds with

** Execute db:create

could not connect to server: No such file or directory

Is the server running locally and accepting

connections on Unix domain socket 

How does one debug this? Works on developer machines, was working fine on pipelines until the gem change. Can confirm that postgresql is up and running. What documentation exists to debug the internals? Is it possible to log in to bitbucket's pipeline at some point? There's a doc on how to "test your pipeline locally" but it's not failing locally.

Accepted answers

All comments

Theodora Boudale

Hi Jack and welcome to the community.

The guide we have on debugging pipelines locally is for debugging pipelines locally with Docker, by using the same Docker image you use in Pipelines. Pipelines builds run in Docker containers, so running a build on your local machine does not simulate the environment where Pipelines builds run.

The following guide includes the steps you can take to debug the build locally with Docker:

https://support.atlassian.com/bitbucket-cloud/docs/debug-pipelines-locally-with-docker/

It is important to use the same Docker image and image tag you use in your bitbucket-pipelines.yml file, and also to do a git reset --hard in the clone to the commit of the build you are debugging.

If your build uses service containers, there is a section on the doc titled "Testing with build services" which includes more details on how to debug locally a build with services. It is important to use the same Docker image that you use in bitbucket-pipelines.yml for the service.

If the only change you made was the version of Rails, it is possible that it is not compatible with any other tools you may be using.

I would suggest as a first step debugging this locally with Docker and see if you get the same error or not.

Kind regards,
Theodora

Jack Phantom

That's all well and good, but the issue isn't with my code, it's with the interaction with a service.

I don't know how bitbucket sets this up, so I don't know if the replication is alright. In either way, I need to debug why it can't connect to the database on bitbucket.

Is there no way to get a console into the process as it is running on your machine and debug what's running where?

Theodora Boudale

Hi Jack,

It is not possible to interact with a Pipelines build while it is running. If you'd like to debug this in Pipelines, you can add any debugging commands in the bitbucket-pipelines.yml file and inspect the output after the build is finished. Any services defined for your build are additional Docker containers that share a network adapter with your build container:

https://support.atlassian.com/bitbucket-cloud/docs/databases-and-service-containers/

This is similar to the instructions we have for debugging locally a build that uses services:

https://support.atlassian.com/bitbucket-cloud/docs/debug-pipelines-locally-with-docker/#Testing-with-build-services

Kind regards,
Theodora

Jack Phantom

Unfortunately none of this is any help. "Just reproduce our services on your machine" doesn't contain any instructions as to how to do so.

There's any number of ways to get something started and working, so a simple "to get postgres working on your machine to test this, do

docker run -it flange bloop foo bar baz"

would be nice.

"Is the server running and accepting TCP/IP connections on port 5432?" is something that gets CONSTANTLY asked on Stack Overflow and here because I haven't found any docs apart from "just define a service like so" and people "just define a service like so" and it doesn't work.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud