Hugi,

not sure I'm following this.

Which Application dispatchRequest am I supposed to monitor ? The application I wrote ? wotaskd ? WOMonitor ?

I don't use any /etc/WebObjects/Properties file. How is this supposed to be configured ? How do I have the system use it ?

Thanks,

On 10/29/21 10:32 AM, Hugi Thordarson wrote:

Hmm, ok… You might try logging request in your Application's dispatchRequest() to see if the requests are getting through? The admin requests (including "stop") will go through there, like any other request, so that way you'll at least see if they're getting through.

If your application is not receiving the admin requests, it's possible it's not listening to local requests. Local IPs can be added using the property "er.extensions.WOHostUtilities.localhostips". I've got a global Properties file on my system at /etc/WebObjects/Properties containing just: "er.extensions.WOHostUtilities.localhostips=(80.85.84.145)" (excluding quotes. And you'd of course substitute with your own server's IPs).

- hugi

On 29 Oct 2021, at 12:14, Valerio Luccio <webobjects-dev@wocommunity.org> wrote:

Hi Hugi,

as you suspected it didn't help. 

I doubt it's any system software blocking it explicitly since I don't see any messages in the log files.

On 10/27/21 3:44 PM, Hugi wrote:

Try running “setenforce 0”. It will (temporarily) disable selinux, making it easy enough to find out if that’s your problem. Having set up a few CentOS servers, I doubt it is though. Report back and we’ll get you up and running :)

On 27 Oct 2021, at 18:13, Valerio Luccio <webobjects-dev@wocommunity.org> wrote:


At the bottom of https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.wocommunity.org_display_documentation_Deploying-2Bon-2BLinux&d=DwIFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=7maqHYtwVmJLFrj8T6IkNUuylGvufsH41QC77LrCf5Y&s=a1rUeQVKdCPLmJheDsgkFECTpQfc_m52NguhujVfN7E&e=  there is a section on SELinux. It points to a blog post written in 2013 by Steven Klassen, unfortunately that blog post is no longer available, does anyone have the original ?  I've emailed Steven to see if he can send it to me.

I've tried to add 1085 as an allowed http port using semanage, but I'm not sure I'm taking the right steps.

On 10/27/21 1:22 PM, Valerio Luccio wrote:

I'm home and was able to test. It's not the firewall (I turned it off for a couple of minutes and tried, without success). I'm not sure what policies to look at. As far as I know wotaskd does not keep a log, correct ?

On 10/23/21 6:18 AM, Valerio Luccio wrote:

Hi Samuel,
that is a very good insight. I'm currently travelling, but when I'm back I'll play with policies/firewall and let you know what I found out.

Thanks,

On Fri, Oct 22, 2021 at 3:28 PM Samuel Pelletier <webobjects-dev@wocommunity.org> wrote:
Hi Valerio,

I experience the same problem on a Cent OS instance (I think this is a VMWare distribution) but it works on others...

There is a major difference between starting the instance and other function like stop and refuse new session. Start is done by wotaskd that launc the process, others are http call to the instance by wotaskd, to some direct actions (womp handler I think).

I suspect that the communication between wotaskd and instance is blocked by the firewall or system policy but I do not have a definitive proof of this.

Regards,

Samuel

Le 21 oct. 2021 à 13:29, Valerio Luccio <webobjects-dev@wocommunity.org> a écrit :

Thanks Lon,
I didn't see your answer until now because gmail (which I hate every day more) had hidden it.

I'll see what I can find in the logs, although "start" works fine, why would "stop" be different ?


On Tue, Oct 5, 2021 at 11:10 PM Lon Varscsak <webobjects-dev@wocommunity.org> wrote:
Look in your application log, do you see messages about not being able to communicate with monitor?  I found this problem happens if I don't have JavaXML as part of my project (or classpath defined to whatever the xml jars are).

-Lon

On Tue, Oct 5, 2021 at 1:43 PM Valerio Luccio <webobjects-dev@wocommunity.org> wrote:
I recently ported my WebObjects app from an old OS X server to a CentOS 8 server.

The WOMonitor on CentOS allows me to configure the app and start it, but it will not stop it (I end up doing with pkill from command line) and the Auto-Recover does not work. I also tried from command line using curl to communicate to WOMonitor, it does the info and start correctly, but it will not stop the app.

I've looked at the log file for the WOMonitor, but there was nothing useful.

Any ideas ?

Thanks in advance,

-- 
Valerio Luccio	   	
High Performance Computing	   	
New York University	   	New York, NY 10003

"In an open world, who needs windows or gates ?"


-- 
Valerio Luccio	   	
High Performance Computing	   	10 Astor Place, Room 415
New York University	   	New York, NY 10003

"In an open world, who needs windows or gates ?"

-- 
Valerio Luccio	   	
High Performance Computing	   	10 Astor Place, Room 415
New York University	   	New York, NY 10003

"In an open world, who needs windows or gates ?"

-- 
Valerio Luccio	   	
High Performance Computing	   	
New York University	   	New York, NY 10003

"In an open world, who needs windows or gates ?"

-- 
Valerio Luccio	   	
High Performance Computing	   	
New York University	   	New York, NY 10003

"In an open world, who needs windows or gates ?"

Valerio Luccio	   	
High Performance Computing	   	
New York University	   	New York, NY 10003

"In an open world, who needs windows or gates ?"

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <webobjects-dev@wocommunity.org>.
To unsubscribe, E-mail to: <webobjects-dev-off@wocommunity.org>
To switch to the DIGEST mode, E-mail to <webobjects-dev-digest@wocommunity.org>
To switch to the INDEX mode, E-mail to <webobjects-dev-index@wocommunity.org>
Send administrative queries to  <webobjects-dev-request@wocommunity.org>

--