X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.22.2a (ClamAV engine v0.102.2) From: "Samuel Pelletier" Received: from fortimail.cybercat.ca ([216.13.210.77] verified) by post.selbstdenker.com (CommuniGate Pro SMTP 6.3.7) with ESMTPS id 26673624 for webobjects-dev@wocommunity.org; Fri, 22 Oct 2021 15:28:48 +0200 Received-SPF: none receiver=post.selbstdenker.com; client-ip=216.13.210.77; envelope-from=samuel@samkar.com Received: from smtpclient.apple (modemcable213.203-171.107.mc.videotron.ca [107.171.203.213]) (user=samuel%samkar.com mech=PLAIN bits=0) by fortimail.cybercat.ca with ESMTP id 19MDSPi3030739-19MDSPi4030739 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 22 Oct 2021 09:28:25 -0400 Content-Type: multipart/alternative; boundary="Apple-Mail=_73F43969-1456-457F-823C-9A4645AA522D" Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: [WO-DEV] WOMonitor on CentOS Date: Fri, 22 Oct 2021 09:28:25 -0400 References: To: WebObjects & WOnder Development In-Reply-To: Message-Id: <80CB61B4-CD01-406C-9A8F-5CD5070E1F3C@samkar.com> X-Mailer: Apple Mail (2.3654.120.0.1.13) X-FEAS-AUTH-USER: samuel%samkar.com --Apple-Mail=_73F43969-1456-457F-823C-9A4645AA522D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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 = a =C3=A9crit : >=20 > Thanks Lon, > I didn't see your answer until now because gmail (which I hate every = day 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 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). >=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 = CentOS 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 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. >=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 ?" --Apple-Mail=_73F43969-1456-457F-823C-9A4645AA522D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 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 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:
=20 =20 =20

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 ?"

= --Apple-Mail=_73F43969-1456-457F-823C-9A4645AA522D--