|
At the bottom of
https://wiki.wocommunity.org/display/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 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,
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
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 ?
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
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 ?"
|