Re: Reboot server, webapp can't launch!
Re: Reboot server, webapp can't launch!
- Subject: Re: Reboot server, webapp can't launch!
- From: Chuck Hill <email@hidden>
- Date: Tue, 8 Jun 2010 12:00:35 -0700
On Jun 8, 2010, at 11:42 AM, email@hidden wrote:
Hi,
When I reboot a 10.4.11 server, wotaskd and monitor? start, but
wotaskd can't start my webapp.
That is either permissions on the executable, permissions on the file
it is logging to, or a mismatched WOHost value.
The symptoms are it seems like it is trying to start, and womonitor
shows that it is trying. The app's log file showed it loaded once,
and then the log ends.
What was output in the log.
Of course, it does not start, and I have to restart wotaskd, then I
can start the app.
That sounds more like a a mismatched WOHost value. This needs to be
set to be the same for wotaskd and the apps. The host configuration
in JavaMonitor should also use this name.
Now I noticed the plist for womonitor did not have the key Disabled
set to <false/>, but womonitor always seemed to be running. ( I
fixed the womonitor plist.)
From what Mr. Google showed me, I may need to have a -WOHost
parameter. I have 2 ethernet ports; en0, which is not configured,
and en1, which is configured. Maybe it tries on en0?
Type "hostname" at the command line. Use that name (unless it ends
in .local in which case you have a different problem).
Also, the /System/Library/WebObjects/Adaptors/Apache/apache.conf
may need to be changed, as per the below info. If /System/Library/
WebObjects/Adaptors/Apache/apache.conf is set at the factory default
of "localhost" and one has 2 ip interfaces, how does it know which
ip address to use?
Better to use the host name that resolves into the primary IP
address. The most important thing is that they are the same.
There is also the option of setting a /Library/WebObjects/
Configuration/WOConfig.xml file with the application name, port,
host, etc. That may help.
I don't even remember that file! :-)
Chuck
Does anybody have any experience in this?
Thanks in advance.
Google showed me the following:
1/ Update the Adaptor configuration file located in :
/System/Library/WebObjects/Adaptors/Apache/apache.conf
by changing the WebObjectsConfig line from http://localhost:1085 to
http://1.2.3.4:1085 using the real IP of the computer
This problem was detected by logging the WOAdaptor comportement. To
start the log do :
sudo touch /tmp/logWebObjects
after that it's possible to look at the WebObjects.log in /tmp/
2/ In System/Library/LaunchDaemons/ on :
com.apple.womonitor.plist and com.apple.wotaskd.plist
I have added a new Parameter -WOHost=1.2.3.4 using the same IP than
in the apache.conf file
3/ when I created my host in JavaMonitor I've done it with the same
IP than above
4/ When I created an Application I've added the -WOHost=1.2.3.4 in
the "Additional Arguments" textarea for the "New Instance Defaults"
for the Application
--
email@hidden
_______________________________________________
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
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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