Yes, that worked. I did have to copy the WebServerResources into the proper
directory under /Library/WebServer/Documents but all seems well now. So
basically I have two instances of JavaMonitor running. Any downside to that,
Or should I unload the one running on port 56789?
Thanks!
Jeff
> O
Another choice is to install JavaMonitor as a regular application, with a
single instance, always running. JavaMonitor has its own password protection,
but use Apache access permissions to further lock down access to it.
-- Patrick
On 29/11/2015 20:09, Tim Worman wrote:
>Jeff:
>
>Even
Jeff:
Even if it were not El Capitan, I would not open that port to outside traffic.
Instead, use ssh to tunnel that traffic to localhost, like:
ssh -L 8080:localhost:56789 @
Then you can connect your browser to: http://localhost:8080 to interact w
JavaMonitor on the remote host. You can also
One last annoyance with the El Capitan machine, I can’t seem to open port 56789
for accessing javamonitor remotely.
I tried the steps outlined at the link below, but according to Network Utility
port scan it’s still not open. Also, I have the firewall completely turned off
under Security & P
On Nov 27, 2015, at 10:55 AM, Jeff Schmitz wrote:
>
> Thinking maybe the apple installer failed because of no java I tried it again
> but it failed the same way.
The Apple installer attempts to install the WO runtime in /System/Library. El
Capitans SIP will not allow you to do that.
https://s
Thanks to help from Patrick Middleton I did get up and running on El Capitan.
Below is a fairly long synopsis of my journey, warts and all. Hopefully it can
help someone else out:
My notes on upgrading from Lion to El Capitan on a remote server:
The first issue I hit was I lost contact to my
Hello List,
I’m in the process of upgrading a server to El Capitan and apache is giving me
the below segmentation fault whenever I try to bring up a page on my
application:
[Tue Nov 24 23:19:32 2015] [notice] child pid 97433 exit signal
Segmentation fault (11)
I’ve seen a few things a