No, the symptom of that is that the app starts but Apache crashed when you try 
to access it.  

Under the .woa directory is the shell script that starts the app.  You can add 
debugging statements in there.  And edit SpawnOfWotaskd under the wostaskd.woa 
to not pipe the output to /dev/nul







On 2016-04-21, 3:08 PM, 
"[email protected] on behalf of Gino 
Pacitti" <[email protected] on behalf 
of [email protected]> wrote:

>I have tried both… and the app goes through the whole start up process and 
>even says Welcome..
>
>Could this be a WOAdaptor problem?
>
>
>
>
>
>> On 21 Apr 2016, at 23:03, Chuck Hill <[email protected]> wrote:
>> 
>> Are you logged in or su - as appserver when you start them from the command 
>> line?
>> 
>> 
>> 
>> 
>> On 2016-04-21, 3:00 PM, 
>> "[email protected] on behalf of 
>> Gino Pacitti" <[email protected] on 
>> behalf of [email protected]> wrote:
>> 
>>> yes both….
>>> 
>>> There is just no commencement of the app visibly happening…
>>> 
>>> Using top I can see the two java processes for WOMonitor and WOTaskd but 
>>> when I try and use monitor to start the app just nothing happens. There is 
>>> no java process beginning and ending… Its just like JavaMonitor is asked to 
>>> do something and the start button begins to change and it just hangs… Its 
>>> probably waiting for some response from something that is not returning...
>>> 
>>> And as I said I can start the bash script in the home directory and no 
>>> errors are reported.
>>> 
>>> 
>>> 
>>> 
>>>> On 21 Apr 2016, at 22:53, Chuck Hill <[email protected]> wrote:
>>>> 
>>>> Have you tried ps to see if it starts?  Or top as you try and start it?
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On 2016-04-21, 2:48 PM, "Gino Pacitti" <[email protected]> wrote:
>>>> 
>>>>> You reckon… Path is just /tmp<appname-1> and nothing is there?
>>>>> 
>>>>> Debugging enabled but there just seems to be no response with 
>>>>> starting/stopping the app…
>>>>> 
>>>>> The path to the log file is: /tmp and permissions are drwxrwxrwt and 
>>>>> owned by root root
>>>>> 
>>>>> It is like the app never gets touched or the bash script does not 
>>>>> commence starting the app…
>>>>> 
>>>>> Executable owned by appserver and the path is appserver/appserveradm
>>>>> 
>>>>> JavaMonitor and wotaskd are both appserver owned and USER variable in 
>>>>> startup script is appserver
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>> On 21 Apr 2016, at 22:36, Chuck Hill <[email protected]> wrote:
>>>>>> 
>>>>>> Bingo!  We have a winner!  Second guess is permissions on the path where 
>>>>>> it is writing log files.
>>>>>> 
>>>>>> Chuck
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On 2016-04-21, 2:27 PM, 
>>>>>> "[email protected] on behalf of 
>>>>>> Dev WO" <[email protected] on 
>>>>>> behalf of [email protected]> wrote:
>>>>>> 
>>>>>>> I think Chuck would say to check the WOHost parameter:)
>>>>>>> 
>>>>>>> Xavier
>>>>>>> 
>>>>>>>> On 21 Apr 2016, at 23:22, Gino Pacitti <[email protected]> wrote:
>>>>>>>> 
>>>>>>>> I have just set up a new deployment on a CentOS 6.7 box and downloaded 
>>>>>>>> java 6 as it has to support some older apps. I also set it up for 5.3 
>>>>>>>> javamonitor and wotaskd.
>>>>>>>> 
>>>>>>>> Now these run and I can see the JavaMonitor page and I can add apps 
>>>>>>>> but the apps do not start?
>>>>>>>> 
>>>>>>>> The script that starts wotaskd and javamonitor are both started by 
>>>>>>>> appserver user and the executable in the bundle is also owned by 
>>>>>>>> appserver. 
>>>>>>>> 
>>>>>>>> But it just does not start the apps. The on/off button just keeps 
>>>>>>>> moving from off -on - off.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> I can start the app with command line and it does not report any 
>>>>>>>> errors. Starting manually still does not allow me to point a browser 
>>>>>>>> at it though but I guess that’s the port assignment.
>>>>>>>> 
>>>>>>>> Any ideas?
>>>>>>>> 
>>>>>>>> Gino
>>>>>>>> _______________________________________________
>>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>>> Webobjects-dev mailing list      ([email protected])
>>>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/webobjects%40anazys.com
>>>>>>>> 
>>>>>>>> This email sent to [email protected]
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>> Webobjects-dev mailing list      ([email protected])
>>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com
>>>>>>> 
>>>>>>> This email sent to [email protected]
>>>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list      ([email protected])
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com
>>> 
>>> This email sent to [email protected]
>
>
> _______________________________________________
>Do not post admin requests to the list. They will be ignored.
>Webobjects-dev mailing list      ([email protected])
>Help/Unsubscribe/Update your Subscription:
>https://lists.apple.com/mailman/options/webobjects-dev/chill%40gevityinc.com
>
>This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to