RexOps / RexOps/Rex

Not getting output from dump_system_information

Open
#1,208 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Perl
Stars
737
Forks
214
PR merge metrics
No merged PRs in 30d

Description

I have a few debian machines. On two of them, the following task works fine:

desc "Get server info";
task "get_infos", group => 'myservers', sub {
  dump_system_information;
};

But on a third Debian machine, I get no output. Log file says this:

<snip>

[2018-10-14 12:53:30] DEBUG - Detecting shell...
[2018-10-14 12:53:30] DEBUG - Found shell in cache: bash
[2018-10-14 12:53:30] DEBUG - Shell/Bash: Got options:
[2018-10-14 12:53:30] DEBUG - $VAR1 = {
          'valid_retval' => [
                              0
                            ],
          'fail_ok' => 1
        };

[2018-10-14 12:53:30] DEBUG - SSH/executing: LC_ALL=C ; export LC_ALL; PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/pkg/bin:/usr/pkg/sbin; export PATH; which lsb_release  
[2018-10-14 12:53:30] DEBUG - Running postponed notifications.
[2018-10-14 12:53:30] DEBUG - Connections in queue: 1
[2018-10-14 12:53:30] DEBUG - Destroying all cached os information
[2018-10-14 12:53:30] DEBUG - Waiting for children to finish
[2018-10-14 12:53:30] DEBUG - Need to reinitialize connections.
[2018-10-14 12:53:30] DEBUG - Returning existing distribution class of type: Rex::TaskList::Base
[2018-10-14 12:53:30] INFO - All tasks successful on all hosts
[2018-10-14 12:53:30] DEBUG - Removing lockfile
[2018-10-14 12:53:30] DEBUG - Executing: LC_ALL=C /bin/sh -c '[ -L "Rexfile.lock" ]'
[2018-10-14 12:53:30] DEBUG - Returning existing distribution class of type: Rex::TaskList::Base

I am, however, able to get output from the machine with this simple task:

desc "Get server uptime";
task "uptime", group => 'myservers', sub {
  my $output = run "uptime";
  say $output;
};

Does anyone know why I might not be getting output from dump_system_information on this one machine.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing dump_system_information on the affected Debian machine and compare its debug output with the working hosts and the successful uptime task. Inspect the dump_system_information entry point and the lsb_release detection shown in the log; done means the task emits system information consistently on that host.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, perl
Domain
devops, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.