X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.22.2a (ClamAV engine v0.102.2) From: "Hugi" Received: from mail-02.1984.is ([185.112.145.70] verified) by post.selbstdenker.com (CommuniGate Pro SMTP 6.3.7) with ESMTPS id 26699539 for webobjects-dev@wocommunity.org; Wed, 27 Oct 2021 21:45:31 +0200 Received-SPF: none receiver=post.selbstdenker.com; client-ip=185.112.145.70; envelope-from=hugi@karlmenn.is Received: from localhost by mail-02.1984.is with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mfor6-0002wv-Jp for webobjects-dev@wocommunity.org; Wed, 27 Oct 2021 19:45:00 +0000 Content-Type: multipart/alternative; boundary=Apple-Mail-120981E9-F1F9-4630-AA6B-59717CF09FD7 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Subject: Re: [WO-DEV] Re: WOMonitor on CentOS Date: Wed, 27 Oct 2021 19:44:59 +0000 Message-Id: <5126757B-3D6A-4944-AA69-E7FED42DE8AB@karlmenn.is> References: In-Reply-To: To: WebObjects & WOnder Development X-Mailer: iPhone Mail (19B74) --Apple-Mail-120981E9-F1F9-4630-AA6B-59717CF09FD7 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Try running =E2=80=9Csetenforce 0=E2=80=9D. It will (temporarily) disable se= linux, making it easy enough to find out if that=E2=80=99s your problem. Hav= ing set up a few CentOS servers, I doubt it is though. Report back and we=E2= =80=99ll get you up and running :) > On 27 Oct 2021, at 18:13, Valerio Luccio w= rote: >=20 > =EF=BB=BF > At the bottom of https://wiki.wocommunity.org/display/documentation/Deploy= ing+on+Linux 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 availa= ble, does anyone have the original ? I've emailed Steven to see if he can s= end it to me. >=20 > I've tried to add 1085 as an allowed http port using semanage, but I'm not= sure I'm taking the right steps. >=20 >> On 10/27/21 1:22 PM, Valerio Luccio wrote: >>=20 >> 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 ? >>=20 >>> On 10/23/21 6:18 AM, Valerio Luccio wrote: >>>=20 >>> 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. >>>=20 >>> Thanks, >>>=20 >>> On Fri, Oct 22, 2021 at 3:28 PM Samuel Pelletier wrote: >>>> Hi Valerio, >>>>=20 >>>> I experience the same problem on a Cent OS instance (I think this is a V= MWare distribution) but it works on others... >>>>=20 >>>> There is a major difference between starting the instance and other fun= ction like stop and refuse new session. Start is done by wotaskd that launc t= he process, others are http call to the instance by wotaskd, to some direct a= ctions (womp handler I think). >>>>=20 >>>> I suspect that the communication between wotaskd and instance is blocke= d by the firewall or system policy but I do not have a definitive proof of t= his. >>>>=20 >>>> Regards, >>>>=20 >>>> Samuel >>>>=20 >>>>> Le 21 oct. 2021 =C3=A0 13:29, Valerio Luccio a =C3=A9crit : >>>>>=20 >>>>> Thanks Lon, >>>>> I didn't see your answer until now because gmail (which I hate every d= ay more) had hidden it. >>>>>=20 >>>>> I'll see what I can find in the logs, although "start" works fine, why= would "stop" be different ? >>>>>=20 >>>>>=20 >>>>> On Tue, Oct 5, 2021 at 11:10 PM Lon Varscsak wrote: >>>>>> Look in your application log, do you see messages about not being abl= e 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 jar= s are). >>>>>>=20 >>>>>> -Lon >>>>>>=20 >>>>>> On Tue, Oct 5, 2021 at 1:43 PM Valerio Luccio wrote: >>>>>>> I recently ported my WebObjects app from an old OS X server to a Cen= tOS 8 server. >>>>>>>=20 >>>>>>> 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 t= he Auto-Recover does not work. I also tried from command line using curl to c= ommunicate to WOMonitor, it does the info and start correctly, but it will n= ot stop the app. >>>>>>>=20 >>>>>>> I've looked at the log file for the WOMonitor, but there was nothing= useful. >>>>>>>=20 >>>>>>> Any ideas ? >>>>>>>=20 >>>>>>> Thanks in advance, >>>>>>>=20 >>>>>>> --=20 >>>>>>> Valerio Luccio =09 >>>>>>> High Performance Computing =09 >>>>>>> New York University New York, NY 10003 >>>>>>>=20 >>>>>>> "In an open world, who needs windows or gates ?" >>>>>=20 >>>>>=20 >>>>> --=20 >>>>> Valerio Luccio =09 >>>>> High Performance Computing 10 Astor Place, Room 415 >>>>> New York University New York, NY 10003 >>>>>=20 >>>>> "In an open world, who needs windows or gates ?" >>>>=20 >>>=20 >>>=20 >>> --=20 >>> Valerio Luccio =09 >>> High Performance Computing 10 Astor Place, Room 415 >>> New York University New York, NY 10003 >>> "In an open world, who needs windows or gates ?" >>=20 >> --=20 >> Valerio Luccio =09 >> High Performance Computing =09 >> New York University New York, NY 10003 >> "In an open world, who needs windows or gates ?" >=20 > --=20 > Valerio Luccio =09 > High Performance Computing =09 > New York University New York, NY 10003 > "In an open world, who needs windows or gates ?" --Apple-Mail-120981E9-F1F9-4630-AA6B-59717CF09FD7 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Try running =E2=80=9Csetenforce 0=E2=80=9D.= It will (temporarily) disable selinux, making it easy enough to find out if= that=E2=80=99s your problem. Having set up a few CentOS servers, I doubt it= is though. Report back and we=E2=80=99ll get you up and running :)

=

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

=EF=BB=BF =20 =20 =20

At the bottom of https://wiki.wocommunity.org/dis= play/documentation/Deploying+on+Linux 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 t= o 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 =C3=A0 13:29, Valerio Luccio <= webobjects-dev@wocommunity.org> a =C3=A9crit :

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 thi= s 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@w= ocommunity.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 ?"
=20
= --Apple-Mail-120981E9-F1F9-4630-AA6B-59717CF09FD7--