1 |
Background |
Background |
2 |
|
---------- |
3 |
|
|
4 |
What is the DGEE |
1. What is the DGEE |
5 |
The DotGNU Execution Environment is an application framework for managing the |
|
6 |
execution of Webservices (and in the future other web-applications) for the |
The DotGNU Execution Environment is an application framework for managing the |
7 |
DotGNU system. |
execution of Webservices (and in the future other web-applications) for the |
8 |
|
DotGNU system. |
9 |
What is Goldwater |
|
10 |
Goldwater is distributed message based middleware. It is highly scalable and |
|
11 |
allows applications written with it to be distributed across multiple machines. |
2. What is Goldwater |
12 |
It is used to tie the components of the DGEE together, performing request |
|
13 |
and reply queueing, load balancing, process sandboxing and resource management. |
Goldwater is distributed message based middleware. It is highly scalable and |
14 |
|
allows applications written with it to be distributed across multiple |
15 |
|
machines. It is used to tie the components of the DGEE together, performing |
16 |
|
request and reply queueing, load balancing, process sandboxing and resource |
17 |
|
management. |
18 |
|
|
19 |
|
|
20 |
Trouble at the top |
Trouble at the top |
21 |
Here we assume that the dgee was installed under /usr/local.... |
------------------ |
22 |
|
These points assume that the dgee was installed under /usr/local/ |
23 |
|
|
24 |
|
3. The DGEE fails to start, gives a message "Goldwater not started" |
25 |
|
|
26 |
|
There are two phases to starting the DGEE. First is to start and instance of |
27 |
|
the Goldwater middleware, Second is to boot the DGEE application within that |
28 |
|
Goldwater instance. |
29 |
|
These two steps may be performed in one go by running the dgeestart script. |
30 |
|
To start them seperately, use 'dgadmin start' and 'dgadmin boot'. |
31 |
|
|
32 |
|
|
33 |
|
4. Where do I find the logfiles? |
34 |
|
|
35 |
|
The logfiles will be found as: |
36 |
|
The DGEE log: /usr/local/var/log/dgee/dgee.log |
37 |
|
Any STDOUT : /usr/local/var/log/dgee/stdout |
38 |
|
Any STDERR : /usr/local/var/log/dgee/stderr |
39 |
|
|
40 |
|
|
41 |
|
5. Starting the DGEE/Goldwater complains about log file permissions. |
42 |
|
|
43 |
|
The user that the DGEE is configured to run as must have write permissions |
44 |
|
to the /usr/local/var/log/dgee directory. If permission is denied, then |
45 |
|
the Goldwater middleware will fail to start and complain loudly. |
46 |
|
|
47 |
|
|
48 |
|
6. Where is the master DGEE configuration file, and how do I change it? |
49 |
|
|
50 |
|
The master DGEE configuration file can be found at /usr/local/etc/dgeeconf.xml |
51 |
|
It defines where the logfiles are, where DGEE server processes are etc. If |
52 |
|
you change any of these resources, then you need to recompile the config file. |
53 |
|
Make sure GWCONFIG is set to point to the binary version of the config file: |
54 |
|
export GWCONFIG=/usr/local/etc/dgeeconf.bin |
55 |
|
|
56 |
The DGEE fails to start, gives a message "Goldwater not started" |
and compile it with gwmkcfg |
57 |
There are two phases to starting the DGEE. First is to start and instance of |
shell> gwmkcfg /usr/local/etc/dgeeconf.xml |
58 |
the Goldwater middleware, Second is to boot the DGEE application within that |
|
59 |
Goldwater instance. |
|
60 |
These two steps may be performed in one go by running the dgeestart script. |
7. I get an "Invalid user/group name" when starting the DGEE, why? |
61 |
|
|
62 |
Where do I find the logfiles |
The dgee is configured with the username and groupname of someone to run as. |
63 |
The logfiles will be found as: |
When run as root, the DGEE immediately becomes that user. |
64 |
The DGEE log: /usr/local/var/log/dgee/dgee.log |
Have a look at the dgeeconf.xml file (see above) and check the user and group |
65 |
Any STDOUT : /usr/local/var/log/dgee/stdout |
entries against your /etc/passwd and /etc/group files. |
66 |
Any STDERR : /usr/local/var/log/dgee/stderr |
The DGEE should be configured to run as the same user as Apache (if you're |
67 |
|
using apache) - if not, either reinstall the DGEE or edit the dgeeconf.xml |
68 |
The user that the DGEE is configured to run as must have write permissions |
manually and change the user and group entries to something valid. Don't |
69 |
to the /usr/local/var/log/dgee directory. If permission is denied, then |
forget to recompile the dgeeconf.xml file as described above. |
70 |
the Goldwater middleware will fail to start and complain loudly. |
|
71 |
|
|
72 |
Where is the master DGEE configuration file, and how do I change it? |
8. User/group running administrator does not match that in configuration. |
73 |
The master DGEE configuration file can be found at /usr/local/etc/dgeeconf.xml |
Error Initialising Administrator (Invalid user name) |
74 |
It defines where the logfiles are, where DGEE server processes are etc. If |
|
75 |
you change any of these resources, then you need to recompile the configuration. |
The user running the administrator is either not root or the user that the |
76 |
Make sure GWCONFIG is set to point to the binary version of the config file: |
DGEE was configured to run as. Please refer to the dgeeconf.xml file for |
77 |
export GWCONFIG=/usr/local/etc/dgeeconf.bin |
details as to who this is (see "I get an 'Invalid user/group name' when |
78 |
|
starting the DGEE, why?" ). |
79 |
and compile it with gwmkcfg |
|
80 |
shell> gwmkcfg /usr/local/etc/dgeeconf.xml |
|
81 |
|
9. How do I see what processes have started? |
82 |
|
|
83 |
I get an "Invalid user/group name" when starting the DGEE, why? |
The DGEE server processes will report their startup to the screen as they |
84 |
The dgee is configured with the username and groupname of someone to run as. |
boot. Such information is also written to the dgee logfile. |
85 |
When run as root, the DGEE immediately becomes that user. |
You can make a manual inspection at any time through the Goldwater |
86 |
Have a look at the dgeeconf.xml file (see above) and check the user and group |
administration tool. |
87 |
entries against your /etc/passwd and /etc/group files. |
Run dgadmin (this sets the environment properly and then invokes Goldwater). |
88 |
The DGEE should be configured to run as the same user as Apache (if you're |
and use the 'pl' command to list the Goldwater processes booted: |
|
using apache) - if not, either reinstall the DGEE or edit the dgeeconf.xml |
|
|
manually and change the user and group entries to something valid. Don't |
|
|
forget to recompile the dgeeconf.xml file as described above. |
|
|
|
|
|
How do I see what has started? |
|
|
The DGEE server processes will report their startup to the screen as they |
|
|
boot. Such information is also written to the dgee logfile. |
|
|
You can make a manual inspection at any time through the Goldwater |
|
|
administration tool. |
|
|
Run dgadmin (this sets up the environment properly and then invokes Goldwater). |
|
|
and use the 'pl' command to list the Goldwater processes booted: |
|
89 |
|
|
90 |
shell> dgadmin |
shell> dgadmin |
91 |
Welcome to the Goldwater Administrator (version 1.1.20) |
Welcome to the Goldwater Administrator (version 1.1.20) |
99 |
Server Class ID Domain/Node Pid Done FRst Status |
Server Class ID Domain/Node Pid Done FRst Status |
100 |
-------------- ------ ------ --------------- ----- ------- ---- --------------- |
-------------- ------ ------ --------------- ----- ------- ---- --------------- |
101 |
guardian 1 1 DotGnuLocal 29008 12 0 Ready |
guardian 1 1 DotGnuLocal 29008 12 0 Ready |
102 |
DGSvcMgr 100 100 DotGnuLocal 29011 1 0 Ready |
DGSvcMgr 100 100 DotGnuLocal 29011 3 0 Ready |
103 |
DGSvcMgr 100 101 DotGnuLocal 29012 0 0 Ready |
DGSvcMgr 100 101 DotGnuLocal 29012 0 0 Ready |
104 |
DGSvcMgr 100 102 DotGnuLocal 29013 0 0 Ready |
DGSvcMgr 100 102 DotGnuLocal 29013 0 0 Ready |
105 |
DGResMgr 200 200 DotGnuLocal 29014 1 0 Ready |
DGResMgr 200 200 DotGnuLocal 29014 1 0 Ready |
106 |
DGResMgr 200 201 DotGnuLocal 29015 0 0 Ready |
DGResMgr 200 201 DotGnuLocal 29015 0 0 Ready |
107 |
DGResMgr 200 202 DotGnuLocal 29016 0 0 Ready |
DGResMgr 200 202 DotGnuLocal 29016 0 0 Ready |
108 |
DGpnetVM 400 400 DotGnuLocal 29017 0 0 Ready |
DGpnetVM 400 400 DotGnuLocal 29017 0 0 Ready |
109 |
DGpnetVM 400 401 DotGnuLocal 29018 0 0 Ready |
DGpnetVM 400 401 DotGnuLocal 29018 1 0 Ready |
110 |
DGpnetVM 400 402 DotGnuLocal 29019 0 0 Ready |
DGpnetVM 400 402 DotGnuLocal 29019 1 0 Ready |
111 |
|
|
112 |
10 servers listed from a total of 10 booted. |
10 servers listed from a total of 10 booted. |
113 |
|
|
114 |
dotGNU DGEE> |
dotGNU DGEE> |
115 |
|
|
116 |
|
|
|
How do I see how many requests have been processed? |
|
|
The 'Done' column of the Goldwater "booted servers" list (above) indicates |
|
|
how may service requests each of the DGEE component processes have received. |
|
|
For instance, the requests 'Done' by the DGpnetVM processes indicates how many |
|
|
times portable.net webservices have been invoked. |
|
117 |
|
|
118 |
|
10. How do I see how many requests have been processed? |
119 |
|
|
120 |
|
The 'Done' column of the Goldwater "booted servers" list (above) indicates |
121 |
|
how may service requests each of the DGEE component processes have received. |
122 |
|
For instance, the requests 'Done' by the DGpnetVM processes indicates how many |
123 |
|
times portable.net webservices have been invoked. |
124 |
|
|
125 |
|
|
126 |
|
11. How do I stop DGEE components? |
127 |
|
|
128 |
|
Individual DGEE components (server processes) may be halted by using the |
129 |
|
administration tool dgadmin. |
130 |
|
The 'halt' command may be used to stop all processes, or individual processes |
131 |
|
by giving a Class or and ID value. |
132 |
|
For instance halt -c 100 will shutdown all of the DGSvcMgr processes, and |
133 |
|
halt -i100 will shutdown the process with ID 100 (the first DGSvcMgr process). |
134 |
|
|
135 |
|
|
136 |
|
12. How do I start DGEE components? |
137 |
|
|
138 |
How do I stop DGEE components? |
Starting DGEE components is very similar to stopping components except you |
139 |
|
use the boot command instead of halt. |
140 |
|
boot -c100 will boot all servers in Class 100, boot -i100 will boot the |
141 |
|
server who's ID is 100. |
142 |
|
Using boot without options will attempt to boot all server processes. |
143 |
|
|
144 |
|
|
145 |
How do I start DGEE components? |
13. How do I cycle DGEE components? |
|
How do I cycle DGEE components? |
|
|
How do I change the log level? |
|
|
How do I clean the IPC resources? |
|
146 |
|
|
147 |
|
If you want to 'bounce' the running dgee by shutting down all processes and |
148 |
|
then starting them up again, then using a halt followed by a boot will have |
149 |
|
the desired effect, except that there will be a window of 'downtime' whilst |
150 |
|
everything comes back up. |
151 |
|
To prevent this Goldwater provides a 'cycle' command which stops and starts |
152 |
|
individual servers one at a time. Again the -c class and -i ID options may |
153 |
|
be given if you want to target particular classes or instances of server. |
154 |
|
|
155 |
|
|
156 |
|
14. How do I change the log level? |
157 |
|
|
158 |
|
The log level may be changed on-the-fly with the set command. |
159 |
|
dgadmin accepts the following syntax for set: |
160 |
|
set <resource> <value> |
161 |
|
|
162 |
|
The DGEE and Goldwater itself writes log entries that are flaged with a |
163 |
|
log type. These flags are bit fields allowing you to select a number of |
164 |
|
different types to entry to be reported in the log. |
165 |
|
|
166 |
|
The following table gives the log types and corresponding OR'able values: |
167 |
|
|
168 |
|
Application Errors 1 |
169 |
|
Data 2 |
170 |
|
Control Flow 4 |
171 |
|
Debugging 8 |
172 |
|
Information 16 |
173 |
|
Audit Info 32 |
174 |
|
|
175 |
|
If you want to see Error, Data and Audit Information, then you would set the |
176 |
|
log level to 1 + 2 + 32 = 35 |
177 |
|
|
178 |
|
Thus: |
179 |
|
dotGNU DGEE> set loglevel 35 |
180 |
|
|
181 |
|
|
182 |
|
15. How do I clean the IPC resources? |
183 |
|
|
184 |
|
Sometimes IPC resources get into a mess and are not free'd properly. |
185 |
|
Goldwater supplies a tool 'gwcipc' to clear the IPC resources of the user |
186 |
|
that invokes it. *Be Careful running this as root* |
187 |
|
|
188 |
|
This command is usually used when you really must clear up the IPC resources. |
189 |
|
|
190 |
|
If you run gwcipc as root you can supply the username of the user who's IPC |
191 |
|
resources you want to clean: |
192 |
|
|
193 |
|
shell> gwcipc nobody |
194 |
|
|
195 |
|
will clear the ipc resources for the user nobody. |
196 |
|
|
197 |
|
* Note that Apache often runs as nobody and you will put Apache into an |
198 |
|
unstable state by doing this whilst it is running. You will need to stop |
199 |
|
and restart Apache if you run gwcipc as the Apache user. |
200 |
|
|
201 |
|
Apache and the DGEE usually run as the same user, so by clearing the IPC |
202 |
|
resources used by DGEE you often interfere with Apache as well. |
203 |
|
|
204 |
|
|
|
User/group running administrator does not match that in configuration. |
|
|
Error Initialising Administrator (Invalid user name) |
|
205 |
|
|