Error unable to retrieve file contents

I am still having issues. I have set up a test repo to reproduce.

Adding this conversation because these people should know the code does not work in all scenarios.
#67435

###Setup
git clone git@github.com:provenvelocity/devops_test.git
git fetch —all
git checkout Collections_issue
python3 -m venv ~/.pv_devops/pv_devops_venv
source ~/.pv_devops/pv_devops_venv/bin/activate
pip install —upgrade pip
pip install -r requirements_withlock.txt

###to reproduce the Ansible Collections issue

branch: Collections_issue

####Run:

ansible-playbook ./molecule/default/converge.yml -i localhost

####Wrong Result:

└─▪ (pv_devops_venv) ansible-playbook ./molecule/default/converge.yml -i localhost
[WARNING]: Unable to parse /Users/H217689/kp/ansible/provenvelocity/devops_test/localhost as an inventory source
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'
ERROR! Unable to retrieve file contents
Could not find or access '/Users/H217689/kp/ansible/provenvelocity/devops_test/molecule/default/provenvelocity.devops_test.playbooks.main.yml' on the Ansible Controller.
If you are using a module and expect the file to exist on the remote, see the remote_src option

####Core Issue:
Ansible does not see the current collection as a collection. When using a collection to run a playbook you should not have to copy it to an anssible_collections folder to ensure ansible sees it that would mean you same code in two locations even though the working folder is the current folder and not the remote folder. This makes it overly complicated for the user to use collections.

In the roles_path var, you add «:roles» to is you should add the current folder to collections_path var if it has a galaxy.yml in it. This will fix the issue.

You can see how not doing this causes issues in other tools because the pattern of collections is unique and not how roles or playbooks are normally treated. Such as having to have it on a special path… This is fine for dependencies but not for the current collection repo your in.

###Further Issues and debugging:
«
####Also:

• Running it like this allows you to see (some times)(some times not) the types ansible views the files as. You can see that only some are playbooks and some are not even though they are.
• Also it thinks this is a file but it is not there. «molecule/provenvelocity.devops_test.main.yml»… These are all other issues but first I’m tackling the collections issue.
• Ansible lint uses ansible core for this so this is still an ansible issue BTW. ( I think :))

─▪ (pv_devops_venv) ansible-lint -vvv
DEBUG    Logging initialized to level 10
DEBUG    Options: Namespace(cache_dir='/Users/H217689/.cache/ansible-lint/5e737a', colored=True, configured=True, cwd=PosixPath('/Users/H217689/kp/ansible/provenvelocity/devops_test'), display_relative_path=True, exclude_paths=['/Users/H217689/kp/ansible/provenvelocity/devops_test/.cache', '/Users/H217689/kp/ansible/provenvelocity/devops_test/.github'], lintables=[], listrules=False, listtags=False, parseable=False, parseable_severity=False, quiet=False, rulesdirs=['/Users/H217689/.pv_devops/pv_devops_venv/lib/python3.9/site-packages/ansiblelint/rules'], skip_list=['204', 'yaml'], tags=[], verbosity=3, warn_list=['experimental', 'role-name'], kinds=[{'jinja2': '**/*.j2'}, {'jinja2': '**/*.j2.*'}, {'requirements': '**/meta/requirements.yml'}, {'galaxy': '**/galaxy.yml'}, {'reno': '**/releasenotes/*/*.{yaml,yml}'}, {'playbook': '**/playbooks/*.{yml,yaml}'}, {'playbook': '**/*playbook*.{yml,yaml}'}, {'role': '**/roles/*/'}, {'tasks': '**/tasks/**/*.{yaml,yml}'}, {'handlers': '**/handlers/*.{yaml,yml}'}, {'vars': '**/{host_vars,group_vars,vars,defaults}/**/*.{yaml,yml}'}, {'meta': '**/meta/main.{yaml,yml}'}, {'yaml': '.config/molecule/config.{yaml,yml}'}, {'requirements': '**/molecule/*/{collections,requirements}.{yaml,yml}'}, {'yaml': '**/molecule/*/{base,molecule}.{yaml,yml}'}, {'requirements': '**/requirements.yml'}, {'playbook': '**/molecule/*/*.{yaml,yml}'}, {'yaml': '**/{.ansible-lint,.yamllint}'}, {'yaml': '**/*.{yaml,yml}'}, {'yaml': '**/.*.{yaml,yml}'}], mock_modules=[], mock_roles=[], loop_var_prefix=None, var_naming_pattern='^[a-z_][a-z0-9_]*$', offline=False, project_dir='.', extra_vars=None, enable_list=[], skip_action_validation=True, rules={}, format='rich', progressive=False, rulesdir=[], use_default_rules=True, config_file='/Users/H217689/kp/ansible/provenvelocity/devops_test/.ansible-lint', version=False)
INFO     Running ansible-galaxy role install --roles-path /Users/H217689/.cache/ansible-lint/5e737a/roles -vr requirements.yml
INFO     Running ansible-galaxy collection install -p /Users/H217689/.cache/ansible-lint/5e737a/collections -vr requirements.yml
INFO     Added ANSIBLE_COLLECTIONS_PATH=/Users/H217689/.cache/ansible-lint/5e737a/collections
DEBUG    Loading rules from /Users/H217689/.pv_devops/pv_devops_venv/lib/python3.9/site-packages/ansiblelint/rules
INFO     Running ansible-galaxy role install --roles-path /Users/H217689/.cache/ansible-lint/5e737a/roles -vr requirements.yml
INFO     Running ansible-galaxy collection install -p /Users/H217689/.cache/ansible-lint/5e737a/collections -vr requirements.yml
INFO     Added ANSIBLE_COLLECTIONS_PATH=/Users/H217689/.cache/ansible-lint/5e737a/collections:/Users/H217689/.cache/ansible-lint/5e737a/collections
Loading custom .yamllint config file, this extends our internal yamllint config.
INFO     Discovered files to lint using: git ls-files -z
INFO     Executing syntax check on molecule/docker/verify.yml (0.83s)
INFO     Executing syntax check on molecule/default/verify.yml (0.84s)
INFO     Executing syntax check on molecule/docker/converge.yml (0.86s)
INFO     Executing syntax check on molecule/default/converge.yml (0.88s)
INFO     Executing syntax check on playbooks/main.yml (0.88s)
DEBUG    Examining tests/test.yml of type yaml
DEBUG    Examining tests/shared_tests.yml of type yaml
DEBUG    Examining molecule/default/converge.yml of type playbook
DEBUG    Examining molecule/docker/verify.yml of type playbook
DEBUG    Examining requirements.yml of type requirements
DEBUG    Examining .yamllint of type yaml
DEBUG    Examining .env.yml of type yaml
DEBUG    Examining molecule/docker/converge.yml of type playbook
DEBUG    Examining molecule/default/molecule.yml of type yaml
DEBUG    Examining playbooks/main.yml of type playbook
DEBUG    Examining molecule/default/verify.yml of type playbook
DEBUG    Examining main.yml of type yaml
DEBUG    Examining galaxy.yml of type galaxy
DEBUG    Examining molecule/docker/molecule.yml of type yaml
DEBUG    Examining .ansible-lint of type yaml
DEBUG    Examining molecule/provenvelocity.devops_test.main.yml of type playbook
DEBUG    Examining tests/shared_tests.yml of type playbook
WARNING  Listing 1 violation(s) that are fatal
load-failure: [Errno 2] No such file or directory: 'molecule/provenvelocity.devops_test.main.yml' (filenotfounderror)
molecule/provenvelocity.devops_test.main.yml:1

####Also:

If you notice in the example above it does not determine that main.yml in the root of the collection is a playbook so it marks it YAML type I then use the same file in the playbooks folder and then get the error below which is the same as the first error and explained below.

Ansible lint uses ansible core for this so this is still an ansible issue BTW. ( I think :))

└─▪ (pv_devops_venv) ansible-lint -vvv
DEBUG    Logging initialized to level 10
DEBUG    Options: Namespace(cache_dir='/Users/H217689/.cache/ansible-lint/5e737a', colored=True, configured=True, cwd=PosixPath('/Users/H217689/kp/ansible/provenvelocity/devops_test'), display_relative_path=True, exclude_paths=['/Users/H217689/kp/ansible/provenvelocity/devops_test/.cache', '/Users/H217689/kp/ansible/provenvelocity/devops_test/.github'], lintables=[], listrules=False, listtags=False, parseable=False, parseable_severity=False, quiet=False, rulesdirs=['/Users/H217689/.pv_devops/pv_devops_venv/lib/python3.9/site-packages/ansiblelint/rules'], skip_list=['204', 'yaml'], tags=[], verbosity=3, warn_list=['experimental', 'role-name'], kinds=[{'jinja2': '**/*.j2'}, {'jinja2': '**/*.j2.*'}, {'requirements': '**/meta/requirements.yml'}, {'galaxy': '**/galaxy.yml'}, {'reno': '**/releasenotes/*/*.{yaml,yml}'}, {'playbook': '**/playbooks/*.{yml,yaml}'}, {'playbook': '**/*playbook*.{yml,yaml}'}, {'role': '**/roles/*/'}, {'tasks': '**/tasks/**/*.{yaml,yml}'}, {'handlers': '**/handlers/*.{yaml,yml}'}, {'vars': '**/{host_vars,group_vars,vars,defaults}/**/*.{yaml,yml}'}, {'meta': '**/meta/main.{yaml,yml}'}, {'yaml': '.config/molecule/config.{yaml,yml}'}, {'requirements': '**/molecule/*/{collections,requirements}.{yaml,yml}'}, {'yaml': '**/molecule/*/{base,molecule}.{yaml,yml}'}, {'requirements': '**/requirements.yml'}, {'playbook': '**/molecule/*/*.{yaml,yml}'}, {'yaml': '**/{.ansible-lint,.yamllint}'}, {'yaml': '**/*.{yaml,yml}'}, {'yaml': '**/.*.{yaml,yml}'}], mock_modules=[], mock_roles=[], loop_var_prefix=None, var_naming_pattern='^[a-z_][a-z0-9_]*$', offline=False, project_dir='.', extra_vars=None, enable_list=[], skip_action_validation=True, rules={}, format='rich', progressive=False, rulesdir=[], use_default_rules=True, config_file='/Users/H217689/kp/ansible/provenvelocity/devops_test/.ansible-lint', version=False)
INFO     Running ansible-galaxy role install --roles-path /Users/H217689/.cache/ansible-lint/5e737a/roles -vr requirements.yml
INFO     Running ansible-galaxy collection install -p /Users/H217689/.cache/ansible-lint/5e737a/collections -vr requirements.yml
INFO     Added ANSIBLE_COLLECTIONS_PATH=/Users/H217689/.cache/ansible-lint/5e737a/collections
DEBUG    Loading rules from /Users/H217689/.pv_devops/pv_devops_venv/lib/python3.9/site-packages/ansiblelint/rules
INFO     Running ansible-galaxy role install --roles-path /Users/H217689/.cache/ansible-lint/5e737a/roles -vr requirements.yml
INFO     Running ansible-galaxy collection install -p /Users/H217689/.cache/ansible-lint/5e737a/collections -vr requirements.yml
INFO     Added ANSIBLE_COLLECTIONS_PATH=/Users/H217689/.cache/ansible-lint/5e737a/collections:/Users/H217689/.cache/ansible-lint/5e737a/collections
Loading custom .yamllint config file, this extends our internal yamllint config.
INFO     Discovered files to lint using: git ls-files -z
INFO     Executing syntax check on molecule/default/converge.yml (0.70s)
INFO     Executing syntax check on molecule/docker/verify.yml (0.82s)
INFO     Executing syntax check on molecule/default/verify.yml (0.83s)
INFO     Executing syntax check on playbooks/main.yml (0.86s)
INFO     Executing syntax check on molecule/docker/converge.yml (0.86s)
WARNING  Listing 1 violation(s) that are fatal
internal-error: Unexpected error code 1 from execution of: ansible-playbook --syntax-check molecule/default/converge.yml
molecule/default/converge.yml:1 [WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note that
the implicit localhost does not match 'all'
ERROR! Unable to retrieve file contents
Could not find or access '/Users/H217689/kp/ansible/provenvelocity/devops_test/molecule/default/provenvelocity.devops_test.playbooks.main.yml' on the Ansible Controller.
If you are using a module and expect the file to exist on the remote, see the remote_src option

####Expected Result:
Converge and install playbook.

####Issues:

• Ansible does not see the current collection as a collection unless it is in their collections folders. Currently, ansible lint does not place them there so this command fails. With role_paths you add «:role» to the paths you need to add the current folder if it has a galaxy.yml file in it. So you do not need to copy the current collection outside of the path it is in to see it in the collections struct.
• If you run this with ansible lint you will see that it sets the path of a collection and copies the collections there. This gets you past one issue but then you get another set of issues. Not all Types are respected and when it runs internally ansible-playbook command you get back to the core issue which is ansible does not see the current collection and in this example is not respecting the ANSIBLE_COLLECTION_PATH when run in a nested way as out of ansible-lint. (This may actually be an issue with ansible lint not passing the configure ENV to the command it runs to test the code. )
• This also happens in molecule because it runs the code from ansible-lint.

####Expected Result:
Converge and install playbook.

####Issues:

• Ansible does not see the current collection as a collection unless it is in their collections folders. Currently, ansible lint does not place them there so this command fails. With role_paths you add «:role» to the paths you need to add the current folder if it has a galaxy.yml file in it. So you do not need to copy the current collection outside of the path it is in to see it in the collections struct.
• If you run this with ansible lint you will see that it sets the path of a collection and copies the collections there. This gets you past one issue but then you get another set of issues. Not all Types are respected and when it runs internally ansible-playbook command you get back to the core issue which is ansible does not see the current collection and in this example is not respecting the ANSIBLE_COLLECTION_PATH when run in a nested way such as out of ansible -lint. (This may actually be an issue with ansible lint not passing the configure ENV to the command it runs to test the code. )
• This also happens in molecule because it runs the code from ansible-lint.

Unable to retrieve file contents about ansible-jupyter-kernel HOT 4 CLOSED

Thanks for submitting an issue. If possible please attach the contents of the notebook with the problem to this issue.

ohlisa55 commented on January 16, 2023

Thanks for replying this issue.

As you can see a picture, when I execute a debug module the first one was ok. After that I made error then trying debug module again that showed me different result from the first one.
What’s going on?

benthomasson commented on January 16, 2023

In cell 9 there is a syntax error that causes the underlying ansible playbook to halt. Try adding two spaces in front of the msg: argument to debug: . To restart the playbook context make and run a #play cell. I was thinking about fixing this restart problem anyway. So thanks for submitting this issue. I’ll work on that next.

ohlisa55 commented on January 16, 2023

In cell 9 there is a syntax error that causes the underlying ansible playbook to halt.

I deliberately made this error because I thought any cells can’t execute after error occured.
But as you can see this picture that works fine if add #play then add modules.
Thanks!!

• Play context dies after about two minutes.
• Multiple unexpected messages are returned from roles HOT 2
• Add #summary to end play context and print a summary of the tasks
• Add #python cell type HOT 1
• Ansible Kernel 0.8.0 did not work with Python3
• Python variable not accessible in a Ansible task HOT 1
• Getting the output of tasks on multiple hosts HOT 3
• In case of Python 3.6, register variable error occurs. HOT 1
• How to become? HOT 1
• Jupyterhub/lab ; Python 3.6 : using #vault_password throws type error HOT 3
• Compatibility with MacOSX and python 3.7 HOT 2
• Shared resources across notebooks.
• AttributeError: ‘AnsibleKernel’ object has no attribute ‘user_ns’ HOT 2
• Getting lots of extraneous output HOT 1
• Unable to ping: after installation ansible_kernel using pip3
• Release 0.9.1 (or 0.10.0) on pypi? HOT 1
• Excessive files in /tmp HOT 1
• copy link file BUG !
• Docker image tag lags behind PyPI releases, and contains deprecated dependencies

Recommend Projects

React

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

Vue.js

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

Typescript

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

TensorFlow

An Open Source Machine Learning Framework for Everyone

Django

The Web framework for perfectionists with deadlines.

Laravel

A PHP framework for web artisans

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

Recommend Topics

javascript

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

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.

Visualization

Some thing interesting about visualization, use data art

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

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

Microsoft

Open source projects and samples from Microsoft.

Источник

‘Unable to retrieve application files. Files corrupt in deployment’ error when you try to start the ClickOnce version of Report Builder from SQL Server 2012 Reporting Services

This article helps you resolve the Unable to retrieve application files. Files corrupt in deployment error that occurs when you try to start the ClickOnce version of SQL Server Report Builder.

Original product version: В SQL Server 2012
Original KB number: В 2781227

Symptoms

When you try to start the ClickOnce version of Microsoft SQL Server Report Builder for Microsoft SQL Server 2012 on a client computer, you may receive an error message that resembles the following:

Unable to retrieve application files. Files corrupt in deployment.

Additionally, when you click Details on the error message dialog box, you see detailed error information that resembles the following:

ERROR + Exception occurred loading manifest from file MSReportBuilder.exe: the manifest may not be valid or the file could not be opened. + Cannot load internal manifest from component file. ERROR DETAILS Following errors were detected during this operation. * [10/31/2012 9:25:34 AM] System.Deployment.Application.InvalidDeploymentException (ManifestLoad) — Exception occurred loading manifest from file MSReportBuilder.exe: the manifest may not be valid or the file could not be opened. — Source: System.Deployment — Stack trace: at System.Deployment.Application.Manifest.AssemblyManifest.ManifestLoadExceptionHelper(Exception exception, String filePath) at System.Deployment.Application.Manifest.AssemblyManifest.LoadFromInternalManifestFile(String filePath) at System.Deployment.Application.DownloadManager.ProcessDownloadedFile(Object sender, DownloadEventArgs e) at System.Deployment.Application.FileDownloader.DownloadModifiedEventHandler.Invoke(Object sender, DownloadEventArgs e) at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next) at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles() at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState) at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options) at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp) at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc) at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl) at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state) — Inner Exception — System.Deployment.Application.DeploymentException (InvalidManifest) — Cannot load internal manifest from component file.

Cause

This issue occurs because the Microsoft .NET Framework 4 or a later version of the .NET Framework is not installed on the client computer.

Resolution

To resolve this issue, install the .NET Framework 4. The following file is available for download from the Microsoft Download Center:

For more information about how to download Microsoft support files, see: How to obtain Microsoft support files from online services

Virus scan claim

Microsoft scanned this file for viruses, using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.

Restart requirement

You must restart your computer after you install this package, and then restart the Report Builder ClickOnce application.

Источник

Executing grunt refresh or grunt exec:all in production mode, leads to error «Unable to retrieve deployment version of static files from the file system.» #29570

Preconditions (*)

Steps to reproduce (*)

1. Make the folder pub your project root
2. Put magento in production mode. php bin/magento deploy:mode:set production
3. Create a theme.
4. Setup grunt.
5. Execute grunt exec:all

Expected result (*)

Actual result (*)

1. You will get Unable to retrieve deployment version of static files from the file system. and the command fails and the file pub/static/deployed_version.txt gets deleted.

This error is getting logged:

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0— Affects critical data or functionality and leaves users without workaround.
• Severity: S1— Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2— Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3— Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4— Affects aesthetics, professional look and feel, “quality” or “usability”.

The text was updated successfully, but these errors were encountered:

Источник

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

Unable to retrieve next block transmission command

[MERGED] Replication errors: Number of already processed blo

Post by bdoellefeld » Jun 10, 2013 3:00 pm this post

My case # is 00248715

Curious if anyone has seen his repetitive error before. I have been seeing more and more errors like this for the past few months and it seems to be increasing in frequency. They appear to be random failures but always the same reason. End of file Unable to retrieve next block transmission command. Number of already processed blocks: [0]. Job retry’s generally succeed.

I’ve been looking at the network side (WAN, 45Mb MPLS source / 30Mb MPLS target) for quite a while and although when replications are occurring there is some increase in latency the network is stable.

Curiously however is this right here: Number of already processed blocks: [0]. It’s always zero. If it was network and random, I would think this number would be different every time it happens. Also, with these and other failed jobs for other VMs, one vmdk will replicate but additional vmdk’s attached on these VMs will fail with this same error.

The last word I got from support was that I need to make sure «Antivirus is not locking the drive»(?) or other whole disk operations are not interfering.

All logs have been uploaded to support.

Re: [MERGED] Replication errors: Number of already processed

Post by foggy » Jun 10, 2013 3:26 pm this post

This is definitely a correct assumption.

Bill, please review this topic for some hints and continue working with support on this issue.

Re: Unable to retrieve next block transmission command

Post by zak2011 » Jun 11, 2013 6:52 am this post

My case #00203616

The error seems to be very intermittent. I was asked to run tshark and capture the packets so that support can investigate this further.

Re: Unable to retrieve next block transmission command

Post by bdoellefeld » Jun 12, 2013 7:48 pm this post

Re: Unable to retrieve next block transmission command

Post by eric.siedentopf » Jun 12, 2013 10:27 pm 1 person likes this post

I have the same issue after a upgrade to 6.5 last week.

Error: Client error: End of file Unable to retrieve next block transmission command. Number of already processed blocks: [0]. it was always [0].

I have never seen this error before with Veeam 5.02 running Backups for a few years and I also have Veeam 6.5 pulling Replication to my DR site without this error for at least 9 months.

All of the hardware is identical all I did was upgrade to Veeam 6.5. I am not using Proxies at this time it is all being ran from the Physical Veeam Server (Proxy, Repo).

I have had two different VMs fail with this error and succeeded on the retry and they are in separate jobs at separate times I have 3-7 VMs per job and no other VMs got this error.

VMware 4.1
NBD Mode (always has been)
Name Status Start time End time Size Read Transferred Duration
Friday VS-IMG1 Success 8:05:50 PM 8:07:56 PM 530.0 GB 717.0 MB 263.2 MB 0:02:06
Yesterday VS-IMG1 Error 8:06:13 PM 8:07:45 PM 530.0 GB 0.0 KB 0.0 KB 0:01:31
Retry VS-IMG1 Success 8:18:46 PM 8:20:31 PM 530.0 GB 1.2 GB 443.8 MB 0:01:44

Re: Unable to retrieve next block transmission command

Post by Vitaliy S. » Jun 16, 2013 7:37 pm this post

Re: Unable to retrieve next block transmission command

Post by zak2011 » Jun 17, 2013 2:17 pm 1 person likes this post

Okay..the latest and quite an interesting update I have now about this problem is the ‘Network Traffic Control’ feature triggers some false positives due to which these errors come up. Support has disabled this feature by adding registry keys ‘EnableTrafficControl’ to zero and also ‘VddkLogLevel’ to zero ( not to be done without supervision of support). According to the support experts, this functionality has been improved much better in v7. Hopefully this should help.

Re: Unable to retrieve next block transmission command

Post by eric.siedentopf » Jun 17, 2013 3:24 pm this post

Re: Unable to retrieve next block transmission command

Post by Vitaliy S. » Jun 17, 2013 3:50 pm this post

Re: Unable to retrieve next block transmission command

Post by eric.siedentopf » Jun 17, 2013 3:54 pm this post

Re: Unable to retrieve next block transmission command

Post by yizhar » Jun 17, 2013 11:16 pm this post

Just want to add that I’m experiencing same issue randomly.

I have seen it on 2 totally different systems, in Backup and also in Replication jobs.

Details about one instance of the problem:

Error message:
Error: Client error: End of file Unable to retrieve next block transmission command. Number of already processed blocks: [0].
After retry it works, but every several days one different VM might have this or similar problem (I don’t always have time to investigate further).

VBR server = physical Dell R610 (acting as the proxy and repository).
VBR version = 6.5.0.144
Production storage = HP 3PAR 7200 with 4 FC connections.
Production environment = 3 hosts, VMware esxi 5.1 update 1.
Backup job in SAN mode (using FC card on backup server), using reverse incremental.
Backup Repository = IBM DS3300 iscsi storage, mounted directly by VBR server.

I have also received report from another client of us, he had the same error but with replication job to remote site.
He has an HP P4300G2 (lefthand) ISCSI SAN on production site.
So I assume the problem is related to reading data from source storage.

Maybe the problem is related to SAN mode?

Re: Unable to retrieve next block transmission command

Post by yizhar » Jun 17, 2013 11:23 pm this post

Just to make it clear regarding my previous post:
I am experiencing the problem with no WAN connection involved, for example:
HP 3PAR storage — FC connection — FC HBA on physical backup server (proxy and repository) — NIC — iscsi switch — IBM DS3300 NTFS LUN as target.

My client also seen it with replication over WAN on totally different environment.

Re: Unable to retrieve next block transmission command

Post by foggy » Jun 18, 2013 10:09 am this post

[MERGED] : Last Hard Disk on a VM reads 0.0 KB at 0 KB/s [CB

Post by Virtualizer » Jun 27, 2013 9:45 am this post

I’m having a strange problem with my backup (Using Backup & Replicate 6.5.0.109)
Been looking at similar prompts floating around here but found different situation than mine.

The backup log is:
6/26/2013 9:20:58 PM :: Queued for processing at 6/26/2013 9:20:58 PM
6/26/2013 9:20:58 PM :: Required backup infrastructure resources have been assigned
6/26/2013 9:21:00 PM :: VM processing started at 6/26/2013 9:21:00 PM
6/26/2013 9:21:00 PM :: VM size: 1.8 TB (169.3 GB used)
6/26/2013 9:21:01 PM :: Using source proxy 10.200.120.118 [hotadd]
6/26/2013 9:21:13 PM :: Indexing guest file system
6/26/2013 9:22:56 PM :: Preparing guest for hot backup
6/26/2013 9:23:03 PM :: Creating snapshot
6/26/2013 9:23:11 PM :: Releasing guest
6/26/2013 9:23:28 PM :: Saving ‘[4Snap] mgt-fs-2008/mgt-fs-2008.vmx’
6/26/2013 9:23:32 PM :: Saving ‘[4Snap] mgt-fs-2008/mgt-fs-2008.vmxf’
6/26/2013 9:23:34 PM :: Saving ‘[4Snap] mgt-fs-2008/mgt-fs-2008.nvram’
6/26/2013 9:23:37 PM :: Hard Disk 1 (80.0 GB) 1.3 GB read at 24 MB/s [CBT]
6/26/2013 9:24:35 PM :: Hard Disk 2 (800.0 GB) 7.1 GB read at 106 MB/s [CBT]
6/26/2013 9:25:43 PM :: Hard Disk 3 (100.0 GB) 1.0 MB read at 106 KB/s [CBT]
6/26/2013 9:25:53 PM :: Hard Disk 4 (200.0 GB) 960.0 MB read at 68 MB/s [CBT]
6/26/2013 9:26:07 PM :: Hard Disk 5 (600.0 GB) 1.1 GB read at 61 MB/s [CBT]
6/26/2013 9:26:25 PM :: Hard Disk 6 (20.0 GB) 57.0 MB read at 6 MB/s [CBT]
6/26/2013 9:26:35 PM :: Hard Disk 7 (0.0 KB) 0.0 KB read at 0 KB/s [CBT]
6/26/2013 9:26:41 PM :: Removing VM snapshot
6/26/2013 9:33:07 PM :: Error: Client error: End of file Unable to retrieve next block transmission command. Number of already processed blocks: [0].
6/26/2013 9:33:07 PM :: Network traffic verification detected no corrupted blocks
6/26/2013 9:33:07 PM :: Busy: Source 79% > Proxy 28% > Network 10% > Target 6%
6/26/2013 9:33:07 PM :: Primary bottleneck: Source
6/26/2013 9:33:08 PM :: Processing finished with errors at 6/26/2013 9:33:07 PM

What the hell is wrong all of a sudden with Disk 7?

I’ve had more VMs backed up succesfuly right after this one and prioer to this one at the same night.

Can’t find anything wrong in there.

Usualy this backup always ends without any errors.

What can you advice me to check or do ?

Re: Unable to retrieve next block transmission command

Post by veremin » Jun 27, 2013 9:50 am this post

You have been merged to the existing discussion regarding similar issues. Typically you might get the aforesaid error due to unstable network connection. Additional information, as well as, other potential causes can be found above; so, please take a look.

[MERGED] Error: Client error: An existing connection

Post by wagnerj » Jul 08, 2013 1:08 pm this post

Hi,
I have searched the forums and have not found an answer. I also called support, and what they have asked me to do has not worked.

Here is the situation, I have two Veeam environments. I am backing up a clustered Hyper-V environment with 3 nodes. The nodes are connected to an IBM Storwize v7000 SAN. One Veeam server is the test environment which I still get perfect backups on every night (Old Gen 3 HP DL360). Keep in mind these are backing up to 4 external 1TB drives like a champ! The other environment is a high powered IBM server I just purchased just for Veeam with 20TB of Internal local storage on a RAID 5. I am able to take a full backup of my 4TB exchange environment on the new server, but reverse incremental fail with the following error:

Error: Client error: An existing connection was forcibly closed by the remote host
Unable to retrieve next block transmission command. Number of already processed blocks: [27987]

It fails each time at 25% on the second disk. Keep in mind it works perfectly on the old system. The backup is being performed over a LAN, on the same VLAN, connected to the same Cisco 3750 X. The port configs are the same as the test server. I did what Veeam support asked and throttle the connection by 60% and that did not work either. I also tried to re-seed the intital backup, I get the same results.
Can Anyone Help?
Jim

Источник

I am trying to include multiple tasks based on some values defined in one hostvar but some fatal errors are thrown even if I’m using the block-rescue block.
I have the variable profiles defined in host_vars/hostname.yml:

profiles: '["profile1","trap1"]'

and the role test_profiles in /etc/ansible/roles. Here, into the tasks directory I have the following .yml files: profile1.yml, profile2.yml, main.yml.

The content of main.yml file is:

- name: import profiles
   block:
     - include_tasks: "{{ item }}.yml"
       with_items: "{{ profiles|default([]) }}"
   rescue:
     - debug: msg='Error encountered while trying to include a .yml file corresponding to a defined profile from profiles variable. Profiles - "{{ profiles }}"'
   when: profiles is defined

Playbook’s content is:

 - name: Test profiles config
   hosts: myhost
   roles:
     - test_profiles

The output is something like this:

TASK [test_profiles : include_tasks] ***********************************************************************************************************************************************************************
included: /etc/ansible/roles/test_profiles/tasks/profile.yml for <my_host>
fatal: [<my_host>]: FAILED! => {"reason": "Unable to retrieve file contentsnCould not find or access '/etc/ansible/trap1.yml'"}

TASK [test_profiles : Ensure that profile directory exists into the D:profiles directory] ************************************************************************************************
ok: [<my_host>]

TASK [test_profiles : Update profile.properties file] ***************************************************************************************************************************************************
ok: [<my_host>]

TASK [test_profiles : debug] *******************************************************************************************************************************************************************************
ok: [<my_host>] => {
    "msg": "Error encountered while trying to include a .yml file corresponding to a defined profile from profiles variable. Profiles - "["profile1","trap1"]""
}
        to retry, use: --limit @/etc/ansible/playbook_test_profiles.retry

PLAY RECAP ********************************************************************************************************************************************************************************************************
<my_host>                 : ok=5    changed=0    unreachable=0    failed=1

From my point of view that fatal error should not appear. What am I doing wrong here and how can I get rid of this? I’ve also tried with a when conditional but without success.

I’m using Ansible 2.4.2.0 and the tasks are performed for some windows hosts.