Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Починить периодически возникающую ошибку на nginx-2 #32

Closed
RedRatInTheHat opened this issue Apr 6, 2024 · 0 comments

Comments

@RedRatInTheHat
Copy link
Owner

null_resource.ansible (local-exec): fatal: [nginx-2]: FAILED! => changed=false
null_resource.ansible (local-exec):   cache_update_time: 1712390430
null_resource.ansible (local-exec):   cache_updated: false
null_resource.ansible (local-exec):   msg: |-
null_resource.ansible (local-exec):     '/usr/bin/apt-get -y -o "Dpkg::Options::=--force-confdef" -o "Dpkg::Options::=--force-confold"       install 'filebeat=8.10.3'' failed: E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3318 (unattended-upgr)
null_resource.ansible (local-exec):     E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
null_resource.ansible (local-exec):   rc: 100
null_resource.ansible (local-exec):   stderr: |-
null_resource.ansible (local-exec):     E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3318 (unattended-upgr)
null_resource.ansible (local-exec):     E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
null_resource.ansible (local-exec):   stderr_lines: <omitted>
null_resource.ansible (local-exec):   stdout: ''
null_resource.ansible (local-exec):   stdout_lines: <omitted>

Решение можно стащить отсюда

RedRatInTheHat added a commit that referenced this issue Apr 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant