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

Failed to execute operation: No such file or directory #4

Open
m0zgen opened this issue Aug 16, 2022 · 0 comments
Open

Failed to execute operation: No such file or directory #4

m0zgen opened this issue Aug 16, 2022 · 0 comments

Comments

@m0zgen
Copy link
Owner

m0zgen commented Aug 16, 2022

This error showing after execute disable_resolved_unit procedure.

Error:

[✓] Set user blockyusr permissions to /opt/blocky catalog
Created symlink from /etc/systemd/system/multi-user.target.wants/blocky.service to /etc/systemd/system/blocky.service.
Failed to execute operation: No such file or directory

Command procedure:

systemctl disable --now systemd-resolved.service
Failed to execute operation: No such file or directory

Solution:

  • Need to add checking unit systemd-resolved.service exist procedure.
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