forked from pivotal-cf/docs-ops-guide
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathtroubleshooting-diego-windows.html.md.erb
140 lines (75 loc) · 4.87 KB
/
troubleshooting-diego-windows.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
---
title: Troubleshooting Diego for Windows
note: keep this page in sync with its equivalent in docs-running-cf/troubleshooting/
---
<strong><%= modified_date %></strong>
This topic describes how to troubleshoot a Windows cell in a Diego deployment.
##<a id='application-errors'></a>Resolve Application Errors
Ensure that your .NET app is ready for deployment. You usually see the following errors only after pushing an app.
#### Error
`NoCompatibleCell`: This error usually indicates that the RepService has not yet registered your Windows cell with the rest of your Pivotal Cloud Foundry (PCF) deployment. The RepService attempts to reconnect on an interval, and can sometimes resolve itself within a few minutes.
#### Resolution
Restart the RepService within your cell to trigger an immediate reconnection.
<hr>
#### Error
`Start Unsuccessful`: This error usually indicates that your app is misconfigured for your PCF Windows environment, but can also indicate your app does not contain the required DLL files and dependencies.
#### Resolution
Push your app from a directory containing either a `.exe` binary or a valid `Web.config` file for .NET apps. Alternatively, add the `-p` flag to your `cf push` command and specify the path to the directory that contains the `.exe` or `Web.config` file.
Ensure that your pushed app contains your app dependencies.
##<a id='find-errors-hakim'></a>Find Errors Using Hakim
Hakim is a diagnostic tool that reveals common configuration issues with Windows cells.
###<a id='install-hakim'></a>Install and Run Hakim
1. Navigate to the [Elastic Runtime product on Pivotal Network](https://network.pivotal.io/products/elastic-runtime).
1. Download the `hakim.exe` binary to your Windows cell from your `DiegoWindows` download.
1. In a shell window, navigate to the directory that contains the downloaded binary.
1. Execute the binary. Here is example hakim output:
<pre class='terminal'>
PS C:\Users\Administrator\Downloads> .\hakim.exe
2016/02/26 21:04:35 The following processes are not running: garden-windows.exe
2016/02/26 21:04:36 Failed to create container
Post http://api/containers: dial tcp 127.0.0.1:9241: ConnectEx tcp: No connection could be made because the target machine actively refused it.
</pre>
###<a id='resolve-errors'></a>Resolve Common Errors
Hakim only outputs to the console if it detects errors. Here are some common errors and resolutions:
####Error
`The following processes are not running`: This usually indicates a failed deployment.
#### Resolution
Re-provision your Windows components. If this does not fix this issue, contact support with the exact deployment steps followed and version of PCF deployed.
<hr>
#### Error
`Failed to resolve consul host`: This usually indicates interference with DNS resolution on your Windows cell.
#### Resolution
To resolve this error, set `localhost 127.0.0.1` as the primary DNS server for the active network adapter.
<hr>
#### Error
`Fair Share CPU Scheduling must be disabled`
#### Resolution
You must disable this setting for your Windows cell to function properly. Turn this off through the **Group Policy Management** console, and then restart your Windows cell.
<hr>
#### Error
`Windows firewall service is not enabled`: Diego for Windows enforces PCF security group settings for apps running on the cell through the Windows firewall. Apps can run without this, but security groups do not work correctly and apps have unrestricted network access.
#### Resolution
Enable the Windows firewall service.
<hr>
#### Error
`There was an error detecting ntp synchronization on your machine`: Clock skew with other PCF components can occur if NTP is not configured. Clock skew can result in odd errors. For example, clock skew can result in not receiving any application metrics for apps running on the affected machine.
#### Resolution
For your Windows cell, use the same NTP server as the rest of your PCF deployment.
<hr>
####Error
`Failed to create container`: This usually indicates an issue with the Windows containerization service.
#### Resolution
Contact support and provide the full output of this error.
##<a id='other'></a>Troubleshoot Other Issues
Look at the **Event Viewer** logs in Windows to troubleshoot other issues:
1. Navigate to **Windows Logs** > **Application**.
1. Review log messages from the services running in DiegoWindows.
1. To isolate the issue, clear the log, reproduce the issue, and review the latest messages.
1. Include the content of these messages in your support request if you need to contact support.
