relaxnow
commented
10 years ago Also my Terminal is set to wrap lines by default, so it was really hard to see that there was a second part to all the output at all.
Closed relaxnow closed 8 years ago
relaxnow
commented
10 years ago Also my Terminal is set to wrap lines by default, so it was really hard to see that there was a second part to all the output at all.
razvanphp
commented
9 years ago +1
The strange thing is that in my case, I have enough free space, so I don't understand why the error is there..
joaocc
commented
9 years ago I am also getting the same error with plenty of space left. In my case I am running a remote that is a hosted server, so it may be due to some lockdown.
However, all the files are extracted correctly. It's simply the annoyance and loosing the notion of "real" problems that make this a problem to me.
2015-07-27 02:40:07,068 p=26755 u=vagrant | changed: [hostedsite1] => {"changed": true, "check_results": {"cmd": "/bin/gtar -C \"/home/hostedsite1/__hsz/src.nodejs/nodejs-v0.12.7.tmp\" --diff -zf \"/home/hsz000manudemo1/__hsz/src.nodejs/node-v0.12.7.tar.gz\"", "err": "/bin/gtar: node-v0.12.7: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/idle_clients.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/http_simple.rb: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/fs-write-stream-throughput.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/http_server_lag.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/README.md: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/function_call: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/function_call/index.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/function_call/binding.gyp: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/function_call/binding.cc: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/function_call/.gitignore: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/function_call/Makefile: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/spawn-echo.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/startup.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/string-creation.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/next-tick-breadth.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/next-tick-depth.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/url.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/v8-bench.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/timers.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/child-process-read.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/misc/module-loader.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/common.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/fs: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmark/fs/readfile.js: Warning: Cannot stat: No such file or directory\n/bin/gtar: node-v0.12.7/benchmar
DenisGorbachev
commented
9 years ago +1 plenty of free space on a clean DigitalOcean droplet, Ubuntu 14.04
aussielunix
commented
9 years ago Seeing this issue too with ansible 1.9.3 on Ubuntu Trusty amd64
It is possible that this is not directly an Ansible issue but more an issue with /bin/tar
We are using the following task:
- name: Unpack Mule download
unarchive:
src="{{ mule_download_dir }}/{{ mule_package }}"
dest="{{ mule_installation_dir }}"
force=no
copy=false
owner={{ mule_os_user }}
group={{ mule_os_group }}
mode=0755
tags: unpackThis task results in the following /bin/tar command but fails.
/bin/tar -C "share/" --diff -zf mule-standalone-3.6.1.tar.gzfoo@bar:/tmp/mp$ /bin/tar -C "share/" --diff -zf mule-standalone-3.6.1.tar.gz
/bin/tar: mule-standalone-3.6.1/lib/boot/commons-cli-1.2.jar: Warning: Cannot stat: No such file or directory
/bin/tar: mule-standalone-3.6.1/lib/boot/disruptor-3.3.0.jar: Warning: Cannot stat: No such file or directory
/bin/tar: mule-standalone-3.6.1/lib/boot/slf4j-api-1.7.7.jar: Warning: Cannot stat: No such file or directory
/bin/tar: mule-standalone-3.6.1/lib/boot/log4j-api-2.1.jar: Warning: Cannot stat: No such file or directory
/bin/tar: mule-standalone-3.6.1/lib/boot/log4j-core-2.1.jar: Warning: Cannot stat: No such file or directory
/bin/tar: mule-standalone-3.6.1/lib/boot/log4j-slf4j-impl-2.1.jar: Warning: Cannot stat: No such file or directory
...
...
...Looking into this I was able to get it to work with the following:
/bin/tar -C "share/" --extract -zf mule-standalone-3.6.1.tar.gz
dagwieers
commented
8 years ago I have fixed the confusing check_results output issue in #3307 as part of commit 8a1b0071bc845018fec97c7bb7ba474c299c34d2.
If you are using the unarchive module, I welcome feedback and wider test reviews before this hits a new release. Testing the new unarchive is easy:
mkdir -p ./library/
wget -O ./library/unarchive.py https://raw.githubusercontent.com/dagwieers/ansible-modules-core/idempotent-unarchive/files/unarchive.pyBTW The reason you see those confusing Warning: Cannot stat: No such file or directory messages is because the unarchive module (unfortunately) uses gtar --diff to establish whether there is a change between what's in the archive and what is on disk. However, if there is nothing on disk (yet) the output will report that for each individual file with the above statement.
Very confusing if you don't know exactly what is going on. (Whether it means the extract fails, was successful, or there is an expected change that doesn't require extraction).
The patch I proposed will remove the check_result from the output. Personally, I would only show that information in debug-mode (or very verbose mode). But that's v2 specific AFAIK.
Issue Type:
Feature Idea
Ansible Version:
ansible 1.7.2
Environment:
Centos 6.5
Summary:
When the 'unarchive module' unpacks to a disk that is almost full it will display the "check_results" first, instead of the actual results for the unpacking "extract_results". With lots of output this may mean missing the original error.
Steps To Reproduce:
A disk that is almost full and contains a zip file to be unpacked:
Unpacking with latest Ansible 1.7.2:
Expected Results:
I expect to see the failing 'extract' first, the diff second.
Actual Results:
Instead I saw the diff first which gave confusing output.