# Builds suddenly failing

**URL:** <https://travis-ci.community/t/builds-suddenly-failing/14580>\
**Category:** Deployment\
**Created:** [March 25, 2025, 2:43am UTC](https://travis-ci.community/t/builds-suddenly-failing/14580 "2025-03-25T02:43:04Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![HubertWagnerVE](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hubertwagnerve/32/5831_2.png) [@HubertWagnerVE](https://travis-ci.community/u/HubertWagnerVE)\
**Post date:** [March 25, 2025, 2:43am UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/1 "2025-03-25T02:43:04Z")

</div>

Hi,

Builds started to fail suddenly:

`Installing gem dependencies: nokogiri (~> 1.15), aws-sdk-cloudformation (~> 1.0) You have already activated logger 1.5.0, but your Gemfile requires logger 1.6.6. Since logger is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports logger as a default gem. (Gem::LoadError)`

---

<div class="post-metadata">

**Author:** ![etrangep](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/etrangep/32/9470_2.png) [@etrangep](https://travis-ci.community/u/etrangep)\
**Post date:** [March 25, 2025, 4:27am UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/3 "2025-03-25T04:27:47Z")

</div>

Getting the same issue on my builds

```auto
$ rvm use $(travis_internal_ruby) --fuzzy do ruby -S gem install dpl -v 2.0.5.1
Successfully installed mime-0.4.4
Successfully installed json_pure-2.8.1
Successfully installed excon-0.112.0
Successfully installed travis-packagecloud-ruby-1.1.0
Successfully installed regstry-1.0.15
Successfully installed travis-cl-1.2.4
Successfully installed dpl-2.0.5.1
7 gems installed
dpl.1

Install deployment dependencies
Installing deployment dependencies
Installing gem dependencies: nokogiri (~> 1.15), aws-sdk-elasticbeanstalk (~> 1), aws-sdk-s3 (~> 1), rubyzip (~> 2.3), pathspec (~> 1.1)
GemWrappers: Can not wrap not executable file: /home/travis/.rvm/gems/ruby-3.3.5/bin/racc.lock
GemWrappers: Can not wrap not executable file: /home/travis/.rvm/gems/ruby-3.3.5/bin/racc.lock
GemWrappers: Can not wrap not executable file: /home/travis/.rvm/gems/ruby-3.3.5/bin/racc.lock
GemWrappers: Can not wrap not executable file: /home/travis/.rvm/gems/ruby-3.3.5/bin/racc.lock

You have already activated logger 1.6.0, but your Gemfile requires logger 1.6.6. Since logger is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports logger as a default gem. (Gem::LoadError)
failed to deploy

```

The comment below (adding gem install nokogiri and gem install logger) fixes the issue for now. My config uses jammy and node\_js

---

<div class="post-metadata">

**Author:** ![HubertWagnerVE](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hubertwagnerve/32/5831_2.png) [@HubertWagnerVE](https://travis-ci.community/u/HubertWagnerVE)\
**Post date:** [March 25, 2025, 4:31am UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/4 "2025-03-25T04:31:16Z")

</div>

Adding the below works for me now:

```auto
before_install:
  - gem install nokogiri
  - gem install logger

```

---

<div class="post-metadata">

**Author:** ![nikhilo](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/nikhilo/32/9058_2.png) [@nikhilo](https://travis-ci.community/u/nikhilo)\
**Post date:** [March 25, 2025, 8:28am UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/7 "2025-03-25T08:28:02Z")

</div>

This worked for me. Thank you!

---

<div class="post-metadata">

**Author:** ![Montana](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/montana/32/9566_2.png) [@Montana](https://travis-ci.community/u/Montana)\
**Post date:** [March 25, 2025, 3:15pm UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/8 "2025-03-25T15:15:06Z")

</div>

Hey all,

When using dpl v2, it’s recommended you add `edge: true` in your `.travis.yml` file. We are currently working on a fix and will provide updates soon.

---

<div class="post-metadata">

**Author:** ![gabe](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/gabe/32/8881_2.png) [@gabe](https://travis-ci.community/u/gabe)\
**Post date:** [March 25, 2025, 8:46pm UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/9 "2025-03-25T20:46:21Z")

</div>

If it helps, I’m seeing this during the deploy step of a node\_js build on Focal

Does upgrading to a newer Linux distro fix this?

---

<div class="post-metadata">

**Author:** ![zzaacchh](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/zzaacchh/32/9471_2.png) [@zzaacchh](https://travis-ci.community/u/zzaacchh)\
**Post date:** [March 26, 2025, 2:36pm UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/10 "2025-03-26T14:36:50Z")

</div>

Our team is also having the same issue. Upgrading to jammy did not help. `edge: true` did.

---

<div class="post-metadata">

**Author:** ![HubertWagnerVE](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/hubertwagnerve/32/5831_2.png) [@HubertWagnerVE](https://travis-ci.community/u/HubertWagnerVE)\
**Post date:** [March 27, 2025, 1:29pm UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/11 "2025-03-27T13:29:29Z")

</div>

Now I’m getting:

```auto
You have already activated logger 1.6.6, but your Gemfile requires logger 1.7.0. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)

```

---

<div class="post-metadata">

**Author:** ![sambrady-chi](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/sambrady-chi/32/9473_2.png) [@sambrady-chi](https://travis-ci.community/u/sambrady-chi)\
**Post date:** [March 27, 2025, 2:50pm UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/12 "2025-03-27T14:50:15Z")

</div>

We are having the same issue. adding `edge: true` worked yesterday when the error message was

```auto
You have already activated logger 1.6.0, but your Gemfile requires logger 1.6.6. Since logger is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports logger as a default gem. (Gem::LoadError)

```

but today, the error message is

```auto
You have already activated logger 1.6.6, but your Gemfile requires logger 1.7.0. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)

```

EDIT:

removing `edge: true` made it work once, then error again. 😅

---

<div class="post-metadata">

**Author:** ![dennishendriksen](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/dennishendriksen/32/8292_2.png) [@dennishendriksen](https://travis-ci.community/u/dennishendriksen)\
**Post date:** [March 27, 2025, 3:48pm UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/13 "2025-03-27T15:48:34Z")

</div>

Running into the same issue with jammy and edge: true, have not found a workaround yet.

---

<div class="post-metadata">

**Author:** ![j.islas](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/j.islas/32/9474_2.png) [@j.islas](https://travis-ci.community/u/j.islas)\
**Post date:** [March 27, 2025, 3:50pm UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/14 "2025-03-27T15:50:57Z")

</div>

Gonna add my team to the list of stuck people. Tried upgrading the OS to Jammy, using `edge:true` and also force installing logger with `gem install logger -v 1.7.0` on before\_install step

According to what we researched, Logger was recently updated and current version of the dpl gem had removed the hard dependency on Logger

---

<div class="post-metadata">

**Author:** ![bogdan-niculescu-sch](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/bogdan-niculescu-sch/32/9475_2.png) [@bogdan-niculescu-sch](https://travis-ci.community/u/bogdan-niculescu-sch)\
**Post date:** [March 27, 2025, 3:57pm UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/15 "2025-03-27T15:57:51Z")

</div>

+1  
Same thing happening in my case also. Yesterday the build was working, using the `edge: true` workaround for the 1.6.0-1.6.6 bug. Today I’m getting the 1.6.6-1.7.0 bug.

Tried upgrading to `dist: jammy`, removing `edge: true`, force installing logger 1.7.0 with

```auto
before_deploy:
    - rvm use $(travis_internal_ruby) --fuzzy do ruby -S gem uninstall logger -v 1.6.6
    - rvm use $(travis_internal_ruby) --fuzzy do ruby -S gem install logger -v 1.7.0

```

and running the above commands as a script, and no luck so far

---

<div class="post-metadata">

**Author:** ![j.islas](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/j.islas/32/9474_2.png) [@j.islas](https://travis-ci.community/u/j.islas)\
**Post date:** [March 27, 2025, 5:41pm UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/16 "2025-03-27T17:41:46Z")

</div>

Haven’t confirmed it worked for all of our projects, but this helped:

```auto
before_install:
    - gem update --system

```

Already managed to deploy some projects

---

<div class="post-metadata">

**Author:** ![dennishendriksen](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/dennishendriksen/32/8292_2.png) [@dennishendriksen](https://travis-ci.community/u/dennishendriksen)\
**Post date:** [March 28, 2025, 6:16am UTC](https://travis-ci.community/t/builds-suddenly-failing/14580/17 "2025-03-28T06:16:18Z")

</div>

> [@sambrady-chi](#):
>
> `You have already activated logger 1.6.6, but your Gemfile requires logger 1.7.0`

Thanks for sharing, can confirm this works for our deploys (for now :-P).
