I would recommend you to check OM logs to ensure there were no errors .. On Sat, Jul 6, 2019, 20:03 Xavier M <[email protected]> wrote:
> Hi! > > > As you can probably already presume, these command lines are quite magic > for me. No idea of how they work, neither what their utility is... But I > trust in the fact that most of you understand! > > > xavier@sd-118950:~$ ps -ef|grep java > root 1060 1 0 juil.05 ? 00:09:28 /usr/bin/java > -Djava.util.logging.config.file=/opt/open500/conf/logging.properties > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > -Djdk.tls.ephemeralDHKeySize=2048 > -Djava.protocol.handler.pkgs=org.apache.catalina.webresources > -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 > -Dignore.endorsed.dirs= -classpath > /opt/open500/bin/bootstrap.jar:/opt/open500/bin/tomcat-juli.jar > -Dcatalina.base=/opt/open500 -Dcatalina.home=/opt/open500 > -Djava.io.tmpdir=/opt/open500/temp org.apache.catalina.startup.Bootstrap -u > nobody -Dcatalina.base start > xavier 11265 11246 0 14:54 pts/0 00:00:00 grep --color=auto java > xavier@sd-118950:~$ netstat -an|grep 5443 > xavier@sd-118950:~$ > > Please note that the second command does not give any result (that's the > same with "sudo"). At the time being, I commented the "LISTEN" command in > ports.conf, since Maxim thought that they made no sense here. > > > Xavier > > > Le 06/07/2019 à 04:06, Maxim Solodovnik a écrit : > > Please check OM is running: `ps -ef|grep java` and necessary ports are > being LISTEN `netstat -an|grep 5443` > > The result of the last command should be something like > > tcp6 0 0 :::5443 :::* LISTEN > > > > On Fri, 5 Jul 2019 at 22:21, Xavier M <[email protected]> wrote: > >> Atomic steps sounds fine... Except if it is a nuclear bomb! >> >> In my case, I'd like as first step to understand why I can not connect >> anymore to "https://domain.eu:5443/openmeetings"; (while I could connect >> to "https://domain.eu <https://domain.eu:5443/openmeetings>") - domain.eu >> was a generic name in my explanation - since I followed the steps given >> yesterday. Nota Bene: it works again when I modify /etc/apache2/ports.conf >> to add "Listen 5443" and "Listen 8888", but I got the error >> SSL_ERROR_RX_RECORD_TOO_LONG. >> >> Assume that I go back to the previous problem, that is I can connect, but >> with a warning "self made certificate", or whatever the correct name... >> Then I have to understand what Aaron means by "Proxy through Apache, or >> configure your OM instance to be able to read where the keys are" and >> what are pros and cons. Aaron suggested me to "proxy", but actually I do >> not know how one does this. >> >> Thanks all of you for your help, >> Xavier >> >>
