Difference between revisions of "Error: Error acquiring the state lock"

From wikieduonline
Jump to navigation Jump to search
(Created page with " == See also == * {{Terraform}}")
 
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
  
 +
Error: Error acquiring the state [[lock]]
 +
 +
│ Error message: resource temporarily unavailable
 +
│ Lock Info:
 +
│  ID:        660fed3f-cb8b-d3e4-7eec-7ea4f583435c
 +
│  Path:      terraform.tfstate
 +
│  Operation: OperationTypeApply
 +
│  Who:      root@XXXX
 +
│  Version:  1.0.4
 +
│  Created:  2021-09-08 10:32:49.0632977 +0000 UTC
 +
│  Info:
 +
 +
 +
│ Terraform acquires a state lock to protect the state from being written
 +
│ by multiple users at the same time. Please resolve the issue above and try
 +
│ again. For most commands, you can disable locking with the "[[-lock=false]]"
 +
│ flag, but this is not recommended.
  
 +
Acquiring state lock. This may take a few moments...
 +
 +
│ Error: Error acquiring the state lock
 +
 +
│ Error message: 2 errors occurred:
 +
│      * ResourceNotFoundException: Requested resource not found
 +
│      * ResourceNotFoundException: Requested resource not found
 +
 +
 +
 +
│ Terraform acquires a state lock to protect the state from being written
 +
│ by multiple users at the same time. Please resolve the issue above and try
 +
│ again. For most commands, you can disable locking with the "-lock=false"
 +
│ flag, but this is not recommended.
 +
 +
 +
[[terraform force-unlock]] your-version/learn-terraform-eks
 +
Do you really want to force-unlock?
 +
  Terraform will remove the lock on the remote state.
 +
  This will allow local Terraform commands to modify this state, even though it
 +
  may still be in use. Only 'yes' will be accepted to confirm.
 +
 +
  Enter a value: yes
 +
 +
Terraform state has been successfully unlocked!
 +
 +
The state has been unlocked, and Terraform commands should now be able to
 +
obtain a new lock on the remote state.
 +
 +
 +
[[terraform force-unlock]] 660fed3f-cb8b-d3e4-7eec-7ea4f583435c
 +
Local state cannot be unlocked by another process
 +
 +
 +
Solution:
 +
* Review [[filesystem permissions]] in case you work with more than 1 user
 +
 +
== Related commands ==
 +
* <code>[[terraform plan -lock=false]]</code>
 +
* <code>[[terraform force-unlock]]</code>
 +
* <code>[[terraform validate]]</code>
 +
* <code>[[terraform apply]]</code>
 +
* <code>[[terraform plan -refresh-only]]</code>
 +
* [[Error: Invalid multi-line string]]
 +
* [[Error: Missing newline after argument]]
 +
* [[Error: Invalid block definition]]
 +
* [[Error: Argument or block definition required]]
 +
* [[No changes. Infrastructure is up-to-date]]
  
 
== See also ==
 
== See also ==
* {{Terraform}}
+
* {{terraform plan}}
 +
* {{terraform apply}}
 +
 
 +
[[Category:Terraform]]

Latest revision as of 09:39, 12 February 2024

Error: Error acquiring the state lock
│
│ Error message: resource temporarily unavailable
│ Lock Info:
│   ID:        660fed3f-cb8b-d3e4-7eec-7ea4f583435c
│   Path:      terraform.tfstate
│   Operation: OperationTypeApply
│   Who:       root@XXXX
│   Version:   1.0.4
│   Created:   2021-09-08 10:32:49.0632977 +0000 UTC
│   Info:
│
│
│ Terraform acquires a state lock to protect the state from being written
│ by multiple users at the same time. Please resolve the issue above and try
│ again. For most commands, you can disable locking with the "-lock=false"
│ flag, but this is not recommended.
Acquiring state lock. This may take a few moments...
╷
│ Error: Error acquiring the state lock
│
│ Error message: 2 errors occurred:
│       * ResourceNotFoundException: Requested resource not found
│       * ResourceNotFoundException: Requested resource not found
│
│
│
│ Terraform acquires a state lock to protect the state from being written
│ by multiple users at the same time. Please resolve the issue above and try
│ again. For most commands, you can disable locking with the "-lock=false"
│ flag, but this is not recommended.
╵
terraform force-unlock your-version/learn-terraform-eks
Do you really want to force-unlock?
  Terraform will remove the lock on the remote state.
  This will allow local Terraform commands to modify this state, even though it
  may still be in use. Only 'yes' will be accepted to confirm.

  Enter a value: yes

Terraform state has been successfully unlocked!

The state has been unlocked, and Terraform commands should now be able to
obtain a new lock on the remote state.


terraform force-unlock 660fed3f-cb8b-d3e4-7eec-7ea4f583435c
Local state cannot be unlocked by another process


Solution:

Related commands[edit]

See also[edit]

Advertising: