Coder Social home page Coder Social logo

Comments (3)

piersc avatar piersc commented on August 13, 2024

It appears when running apply some errors are actually sent to stderr. It seems these are coming from https://github.com/rackerlabs/auter/blob/master/auter#L163

 local HISTORY_BEFORE=$(${PACKAGE_MANAGER} history list)

Here's an example of what this might show:

# auter --apply
INFO: Running with: /usr/bin/auter --apply
INFO: Running in an interactive shell, disabling all random sleeps
INFO: Applying updates
Warning: RPMDB altered outside of yum.
** Found 10 pre-existing rpmdb problem(s), 'yum check' output follows:
avahi-autoipd-0.6.31-15.el7_2.1.x86_64 is a duplicate with avahi-autoipd-0.6.31-15.el7.x86_64
avahi-libs-0.6.31-15.el7_2.1.x86_64 is a duplicate with avahi-libs-0.6.31-15.el7.x86_64
ca-certificates-2015.2.6-70.1.el7_2.noarch is a duplicate with ca-certificates-2015.2.4-71.el7.noarch
coreutils-8.22-15.el7_2.1.x86_64 is a duplicate with coreutils-8.22-15.el7.x86_64
cyrus-sasl-lib-2.1.26-20.el7_2.x86_64 is a duplicate with cyrus-sasl-lib-2.1.26-19.2.el7.x86_64
cyrus-sasl-plain-2.1.26-20.el7_2.x86_64 is a duplicate with cyrus-sasl-plain-2.1.26-19.2.el7.x86_64
1:grub2-tools-2.02-0.34.el7.centos.x86_64 is a duplicate with 1:grub2-tools-2.02-0.29.el7.centos.x86_64
python-pyudev-0.15-7.el7_2.1.noarch is a duplicate with python-pyudev-0.15-7.el7.noarch
selinux-policy-3.13.1-60.el7_2.3.noarch is a duplicate with selinux-policy-3.13.1-60.el7.noarch
selinux-policy-targeted-3.13.1-60.el7_2.3.noarch is a duplicate with selinux-policy-targeted-3.13.1-60.el7.noarch
INFO: Updates complete (yum Transaction ID : 57). You may need to reboot for some updates to take effect

from auter.

piersc avatar piersc commented on August 13, 2024

To summarise this:

  1. During prep, stderr is not captured to file, but is printed to screen
  2. During apply, errors from the yum history command will do the same
  3. During apply, no errors are either captured or printed to screen, the output of yum is dropped

Point 3 makes debugging what went wrong impossible without rerunning yum manually. 1 and 2 means the error output won't be in the place you expect it to be.

from auter.

reaperzn avatar reaperzn commented on August 13, 2024

fixed in #36

from auter.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.