ytti/oxidized · error · Oxidized::Output::Output::NoConfig

no output file config, edit #{Oxidized::Config.configfile}

Error message

no output file config, edit #{Oxidized::Config.configfile}

What it means

Error "no output file config, edit #{Oxidized::Config.configfile}" thrown in ytti/oxidized.

Source

Thrown at lib/oxidized/output/file.rb:19

module Oxidized
  module Output
    # ruby's File class must be accessed with ::File to avoid name conflicts
    class File < Output
      require 'fileutils'

      attr_reader :commitref

      def initialize
        super
        @cfg = Oxidized.config.output.file
      end

      def setup
        return unless @cfg.empty?

        Oxidized.asetus.user.output.file.directory = ::File.join(Config::ROOT, 'configs')
        Oxidized.asetus.save :user
        raise NoConfig, "no output file config, edit #{Oxidized::Config.configfile}"
      end

      # node: node name (String)
      # outputs: Oxidized::Models::Outputs
      # opts: dict of optional parameters:
      #  - group: node group
      #  - significant_changes:
      #      nil / not set / true  -> store as usual
      #      false                 -> do not store
      def store(node, outputs, opt = {})
        return false if opt[:significant_changes] == false

        file = ::File.expand_path @cfg.directory
        file = ::File.join ::File.dirname(file), opt[:group] if opt[:group]
        FileUtils.mkdir_p file
        file = ::File.join file, node
        ::File.write(file, outputs.to_cfg)
        @commitref = file

View on GitHub (pinned to 687ed4262d)

When it happens

Trigger: Thrown at lib/oxidized/output/file.rb:19 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of ytti/oxidized@687ed4262d (2026-08-23). Data as JSON: /api/errors/84db9b88a3f17f18. Report an issue: GitHub.