X-CGP-ClamAV-Result: CLEAN X-VirusScanner: Niversoft's CGPClamav Helper v1.22.2a (ClamAV engine v0.102.2) From: "Valerio Luccio" Received: from [148.163.150.240] (HELO mx0b-00256a01.pphosted.com) by post.selbstdenker.com (CommuniGate Pro SMTP 6.3.7) with ESMTPS id 26699151 for webobjects-dev@wocommunity.org; Wed, 27 Oct 2021 19:22:47 +0200 Received-SPF: softfail receiver=post.selbstdenker.com; client-ip=148.163.150.240; envelope-from=valerio.luccio@nyu.edu Received: from pps.filterd (m0142701.ppops.net [127.0.0.1]) by mx0b-00256a01.pphosted.com (8.16.1.2/8.16.1.2) with SMTP id 19RGoo8g001663 for ; Wed, 27 Oct 2021 13:22:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nyu.edu; h=content-type : message-id : date : mime-version : subject : to : references : from : in-reply-to; s=20180315; bh=AsoT1RZCJyviwEEom9CRX+SfLgULVDqNUJCzFg/Egt8=; b=DB3FLelYE3SPSoL7tZMMQSgrJpDgdPrSihCqptvCcBEuTJSqmOMBmIFWMDUbrF6jKBGR Ch5ZlQGB3eT/8cvfRyB3UTQFMBsuFWX6yjTnf72eVfdCPYgtX7D5p5WT1/osi+Y3O4cC ebAC2B5EwKUkK4zPFFTfv3YJq5Zk/n3u8G21ZE11cnFzb4i7GNr3i4/+8MFeiXsnGecl VpY3g+9SGhj03oVCAA+3b1IlXvv44u40xiMn1eWhVLm4Lapvq5GDzZPRLG6K4SiPnswo 0sJ3JLRJzvK0Nlnf1sITU/Hti4StFjz2NfY9eDPzZQr7CMuNgQGjAO+mEntzApEF4Xth Nw== Received: from mail-qv1-f71.google.com (mail-qv1-f71.google.com [209.85.219.71]) by mx0b-00256a01.pphosted.com with ESMTP id 3by177u4wm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Wed, 27 Oct 2021 13:22:25 -0400 Received: by mail-qv1-f71.google.com with SMTP id bu1-20020ad455e1000000b0038529a6d278so2756632qvb.10 for ; Wed, 27 Oct 2021 10:22:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to; bh=AsoT1RZCJyviwEEom9CRX+SfLgULVDqNUJCzFg/Egt8=; b=wrv/Sqv1SqFGNZ7cWhcPLxR8fjfls5c1HQ3YJzhfaw08AQgwoNIvcltDDEhfZ0FTR3 gjw9UnfvH0y/afc34uCuCPvk+3mc2+kAgRtIfvr60AVN1FcHVrLXk07GAdurDC7ohPZx qT6xb7uVUI612hLHN/bvi09vdF68kAwL/l3Kor5KCQNWS6gQgsbyLaxlyqaM+9vTE3v5 YEgop8Fi/1KVciUJUbiAebhYcfqtTq65NHW89yflEIfTqiON/fq3mqEO9m0Y84COlqc7 o3ms3U8ugtcfQGzoXjMXkMpNFNqdEZgT8q2l26/+xqreiMm3lvjhCGzFtVelPTDABr7X 5m8Q== X-Gm-Message-State: AOAM533847Fu0WwIxGHtjifzh8IejVv5kzq8AuikKkxKLb3cxrrbKOyZ CBYBlKrAW1Is3/Nc8ZHk/7KIYtTiqwSUsrjy6H4sVl6aZPCS19ptoSo7DMgkSIDcAupVCsN8Xmd qxaIMKstZPCRKSWm+9eoLBEjs1Q== X-Received: by 2002:a05:6214:20a5:: with SMTP id 5mr25812232qvd.66.1635355343660; Wed, 27 Oct 2021 10:22:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxz4peYlPMQ/noIx2ncalT6bKiPMhcbsRj7w42DnFz1d6fm3PrUSRExMVO7q2RHCM3IcSbmeQ== X-Received: by 2002:a05:6214:20a5:: with SMTP id 5mr25812201qvd.66.1635355343212; Wed, 27 Oct 2021 10:22:23 -0700 (PDT) Received: from [192.168.1.93] (4133da4e.cst.lightpath.net. [65.51.218.78]) by smtp.gmail.com with ESMTPSA id n20sm385118qkk.63.2021.10.27.10.22.21 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 27 Oct 2021 10:22:22 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------j0wsY4KF9G4EpAnwTyqdkG06" Message-ID: Date: Wed, 27 Oct 2021 13:22:21 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Subject: Re: [WO-DEV] Re: WOMonitor on CentOS Content-Language: en-CA To: WebObjects & WOnder Development References: In-Reply-To: X-Proofpoint-GUID: schbo9banGHgwKp2OXkD2GYezbueY6LT X-Proofpoint-ORIG-GUID: schbo9banGHgwKp2OXkD2GYezbueY6LT X-Orig-IP: 209.85.219.71 X-Proofpoint-Spam-Details: rule=outbound_bp_notspam policy=outbound_bp score=0 suspectscore=0 bulkscore=0 mlxlogscore=999 phishscore=0 malwarescore=0 impostorscore=0 mlxscore=0 priorityscore=1501 adultscore=0 lowpriorityscore=0 clxscore=1015 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2110150000 definitions=main-2110270098 This is a multi-part message in MIME format. --------------j0wsY4KF9G4EpAnwTyqdkG06 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 > 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 >> 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 >> 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 >> 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 ?" --------------j0wsY4KF9G4EpAnwTyqdkG06 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

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