Error in MAD initialization There may be problems with the proxy certificate, bin directory, or the executable name of a MAD may not be in the correct location. Check that you have generated a valid proxy (for example with the grid-proxy-info command). Also, check that the directory $GW_LOCATION/bin is in your path, and the executable name of all the MADs is defined in gwd.conf.

Error Code	Definition	Possible Solutions
`Lock file exists`	Another GWD may be running.	Be sure that no other GWD is running, then remove the lock file and try again.
`Error in MAD initialization`	There may be problems with the proxy certificate, bin directory, or the executable name of a MAD may not be in the correct location.	Check that you have generated a valid proxy (for example with the grid-proxy-info command). Also, check that the directory `$GW_LOCATION/bin` is in your path, and the executable name of all the MADs is defined in `gwd.conf`.
`Could not connect to gwd`	GridWay may not be running or there may be something wrong with the connection.	Be sure that GWD is running; for example: pgrep -l gwd If it is running, check that you can connect to GWD; for example: telnet `cat $GW_LOCATION/var/gwd.port`

Could not connect to gwd

GridWay may not be running or there may be something wrong with the connection.

Be sure that GWD is running; for example:

pgrep -l gwd

If it is running, check that you can connect to GWD; for example:

telnet `cat $GW_LOCATION/var/gwd.port`

2. Debugging

For more detailed developer debugging information, see Debugging. For information about sys admin logging, see Debugging.

Prev
Debugging	Home