Sorry Jeff,
I haven’t looked through the whole thread but have you tried this…
1) When this is happening can you login to a shell and maneuver to be inside the .woa directory.
2) From the command line, attempt to launch the application
3) This will often show you things that you would not be able to see otherwise.
Some possibilities:
A) The .sock file doesn’t have the correct permissions.
B) There are “too many files open” you’ll need to up your user limits otherwise you can’t talk to the DB, etc.
…. probably other issues but hopefully it will stick out like a sore thumb when you run from command line.
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|