To be able to download attached files from LastPass, you need to install the binary component for LastPass in your web browser.
- Navigate to https://lastpass.com/misc_download2.php
- Install the LastPass for Chrome (full version) plugin
Knowledge Base for IT Professionals, Teachers and Astronauts
To be able to download attached files from LastPass, you need to install the binary component for LastPass in your web browser.
The RightScale server templates publish server images to launch. It is advisable to create your own server image because the cloud providers can remove their published images anytime. If you generate your own image, you control the lifecycle of those.
$wc = New-Object System.Net.Webclient
$wc.DownloadFile("https://rightlink.rightscale.com/rll/10/rightlink.install.ps1",
"$pwd\rightlink.install.ps1")
Powershell -ExecutionPolicy Unrestricted -File rightlink.install.ps1
"provisioners": [
{
"type": "powershell",
"pause_before":"10s",
"scripts": [
"install-rightlink.ps1"
]
}
]
It can take 30 minutes for the new image to appear in the list.










Test the new MultiCloud image by TEMPORARILY using the HEAD revision of the Server Template and the MultiCloud image
To test the new image TEMPORARILY select the HEAD revision of the MultiCloud image to be used by the Server Template





In your CAT file set revision 0 to use the HEAD revision of the Server Template
Launch a new server using Self Service with the HEAD revision of the Server Template
When you have successfully tested the new MultiCloud Image create a new version of it.





To be able to use the new version of the Server Image switch to the other accounts and import the template




When the windows_task resource is called to “create” a Windows Scheduled Task that already exists, an error message is returned. In the past, the “modify” action was responsible for the modification of the scheduled tasks, since Chef 13 the “create” action would update the task if exists.
ArgumentError: …[…] (…:… line …) had an error: ArgumentError: windows_task[…] (… line …) had an error: ArgumentError: invalid date
C:/opscode/chef/embedded/lib/ruby/gems/2.4.0/gems/chef-13.6.4-universal-mingw32/lib/chef/provider/windows_task.rb:507:in `strptime’
C:/opscode/chef/embedded/lib/ruby/gems/2.4.0/gems/chef-13.6.4-universal-mingw32/lib/chef/provider/windows_task.rb:507:in `parse_day’
C:/opscode/chef/embedded/lib/ruby/gems/2.4.0/gems/chef-13.6.4-universal-mingw32/lib/chef/provider/windows_task.rb:239:in `convert_user_date_to_system_date’
C:/opscode/chef/embedded/lib/ruby/gems/2.4.0/gems/chef-13.6.4-universal-mingw32/lib/chef/provider/windows_task.rb:99:in `action_create’
It looks like Chef tries to get a date from the existing scheduled task, and cannot parse it successfully.
As we currently cannot update existing tasks, we need to put a guard into the windows_task resource to prevent the execution if the task exists.
startup_task_name = 'chef-client-at_startup'
windows_task "create #{startup_task_name}" do
task_name "#{startup_task_name}"
...
guard_interpreter :powershell_script
only_if "(Get-ScheduledTask | Where-Object {$_.TaskName -eq "#{startup_task_name}"}).TaskName.Length -eq 0"
end
When an application execution fails, it usually returns an error code to specify the cause of the problem.
| Application | Error code | Cause | Workaround | |
| Visual Studio | -2147205120 | The computer has a pending restart and must be rebooted before the execution. | Restart your computer, and then rerun the application. |
To determine which .NET framework is installed on the Windows computer check the values in the registry.
The HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full key contains two values you can check:
You can use InSpec, part of the Chef DK, to check the values:
describe registry_key('HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full') do
it { should have_property 'Release' }
it { should have_property_value('Release', :dword, 460805) } # For dword use the decimal value, no quotes
end
describe registry_key('HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full') do
it { should have_property 'Version' }
it { should have_property_value('Version', :string, '4.7.02053') }
end
| .NET version | Release key hexadecimal | Release key decimal | Version key | Install path |
| 4.6.1 | 6041F | 394271 | ||
| 4.6.2 | 60636 | 394806 | 4.6.01590 | |
| 4.7 | 70805 | 460805 | 4.7.02053 | C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ |
| 4.7.1 | 709FE | 461310 | 4.7.02558 | |
| 4.7.2 | 70bf6 | 461814 | 4.7.03062 | C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ |
| 4.8 | 80EB1 | 528049 |
For more information see
Chef uses the standard RFC 062 exit codes.
In your .kitchen.yml file, you can supply an array of exit codes in the “retry_on_exit_code” option to retry the operation in case the Chef script execution is interrupted. The usual values are
retry_on_exit_code: # An array of exit codes that can indicate that kitchen should retry the converge command. Defaults to an empty array. - 35 # Reboot is scheduled - 20 # The Windows system cannot find the device specified. - 1 # Generic failure
0: SUCCESS - Successful run - Any successful execution of a Chef utility should return this exit code 1: GENERIC_FAILURE - Failed execution - Generic error during Chef execution. 2: SIGINT_RECEIVED - SIGINT received - Received an interrupt signal 3: SIGTERM_RECEIVED - SIGTERM received - Received an terminate signal 35: REBOOT_SCHEDULED - Reboot Scheduled - Reboot has been scheduled in the run state 37: REBOOT_NEEDED - Reboot Needed - Reboot needs to be completed 41: REBOOT_FAILED - Reboot Failed - Initiated Reboot failed - due to permissions or any other reason 42: AUDIT_MODE_FAILURE - Audit Mode Failure - Audit mode failed, but chef converged successfully. 213: CLIENT_UPGRADED - Chef upgrade - Chef has exited during a client upgrade
20: ERROR_BAD_UNIT - The system cannot find the device specified.
The list of all Windows error codes is located at https://msdn.microsoft.com/en-us/library/windows/desktop/ms681381(v=vs.85).aspx
When your Chef recipe requests a reboot using the “reboot” Chef resource, the output window shows an error message:
Chef Client finished, …/… resources updated in … seconds
[…] WARN: Rebooting server at a recipe’s request. Details: {:delay_mins=>1, :reason=>”…”, :timestamp=>…, :requested_by=>”…”}Running handlers:
[…] ERROR: Running exception handlers
Running handlers complete
[…] ERROR: Exception handlers complete
Chef Client failed. … resources updated in … seconds
[…] FATAL: Stacktrace dumped to C:/Users/…/AppData/Local/Temp/kitchen/cache/chef-stacktrace.out
[…] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[…] FATAL: Chef::Exceptions::Reboot: Rebooting server at a recipe’s request. Details: {:delay_mins=>1, :reason=>”…”, :timestamp=>…, :requested_by=>”…”}
Chef also saves the error message in the stacktrace.out file at C:/Users/…/AppData/Local/Temp/kitchen/cache
As coderanger wrote it, replying to a StackOverflow post, it is not an error, it is a necessity to be able to stop the Chef cookbook execution when a reboot is requested. See https://stackoverflow.com/questions/39057254/why-does-chef-throw-fatal-error-on-restart-request
“Because we want to avoid running anything further in the Chef converge and the easiest way to do that is to raise an exception.”
“It’s a weird special case because Ruby doesn’t have any other non-local code execution flow construct that would work well in this case. You’ll just have to add a filter for it. Such are the realities of building software in an imperfect world :) – coderanger Aug 21 ’16 at 5:24″
When you make a change to the version restrictions in the metadata.rb file and execute berks install in your Chef cookbook directory, you may get the error message:
Unable to satisfy constraints on package … due to solution constraint (…). Solution constraints that may result in a constraint on …: [(…)], [(…) -> (…)]
Demand that cannot be met: (…)
Artifacts for which there are conflicting dependencies: … = … -> [(…), (… ~> …)]Unable to find a solution for demands:…
Execute
berks update
to
When you launch a Linux AWS EC2 instance with Terraform or create a Linux AWS image with Packer, one of the following errors are displayed:
amazon-ebs: Error waiting for SSH: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
aws_instance.default: 1 error(s) occurred:
* ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
In the Packer template the “ssh_username”, in the Terraform script the “user” attribute contains the username to connect to the instance. It is important to use the correct username for each operating system. For the list of correct usernames for each operating system, see Create a server image with Packer
Make sure you use the correct SSH key to connect to the instance. In the Terraform file, the “key_name” attribute of the “aws_instance resource” specifies the SSH key to launch the instance with, and the “private_key” attribute of the “connection” contains the key itself as a string.
To comment out a block of lines in the ASP.NET MVC Razor file, enclose them in @* and *@
@* Commented out instructions, including HTML and Extension methods *@