Greetings, hackers,

I've been spending a lot of time debugging client-side installations lately, and finally got around to providing a diagnostic utility for it. This is now integrated into sensorshell. The basic idea is that if you call:

java -jar sensorshell.jar -verify

Then sensorshell, instead of doing what it normally does, enters a special 'verification' mode where it checks:
- that the sensor.properties file exists
- that a host and userkey value can be obtained from the file
- that the server host can be contacted.
- that the userkey is valid (i.e. can be used to login to the host)
- that Soap services appear to be available.


It tries to print out enough stuff along the way so that if something doesn't work, you've got half a chance of fixing it.

If this works, but your sensor doesn't, then you know it's something specific to your sensor.

Here's a sample run where everything works correctly (I've changed my user key, of course):

--------------------------------------------------------------------

C:\cvs\hackyBuild>java -jar build\war\download\sensorshell.jar -verify
SensorShell Client-side Verification.
Info:    All command line args except -debug ignored.
Info:    No logging of this output is performed.
Info:    Version: 6.3.1102 (November 2 2004 15:59:29)

******** Verifying sensor.properties installation and settings.
Success: Found sensor.properties: C:\Documents and Settings\johnson\.hackystat\sensor.properties
Info: Hackystat host is: http://hackystat.ics.hawaii.edu/
Info: Your user key: 'aasdfasasdfY'
Info: Hackystat context root: hackystat
Success: sensor.properties file found and host/key values obtained.


******** Verifying server home page availability.
Info: Retrieving home page from: http://hackystat.ics.hawaii.edu/hackystat/controller
Rhino classes (js.jar) not found - Javascript disabled
Success: Retrieved server home page from: http://hackystat.ics.hawaii.edu/hackystat/controller


******** Verifying your hackystat user key.
Info:    Attempting to login with key: aasdfasasdfY
Success: Logged in with key: aasdfasasdfY

******** Verifying Soap service.
Info: Checking Soap service from: http://hackystat.ics.hawaii.edu/hackystat/servlet/rpcrouter
Success: Contacted Soap service successfully.


Client-side verification appears to have succeeded.

C:\cvs\hackyBuild>

-------------------------------------------------------------

If any of these sections fail, then a failure message is printed and execution terminates.

If you can think of other things to include, please let me know. After I'm convinced that this is working in the daily build, I'll add information about it to the installation documentation.

Cheers,
Philip



Reply via email to