05-30-2020, 11:07 AM
(05-28-2020, 01:52 PM)remkonoteboom Wrote: If TACTIC (or rather the underlying CherryPy module) exits immediately, that means it cannot bind to that port. CherryPy is pretty sensitive to the domain name that is passed through. It may be the "http://" part after -s
Try:
python3 startup_dev.py -p 80 -s <DOMAIN_NAME>
withouth the "http://" on the domain name.
Thank you, and good catch, to have noticed that I mistakenly included http:// in my command. I made that attempt early in the morning before going to work, and my brain was apparently not yet fully engaged. :/
However, I've retried several times this morning (Saturday, so no time constraints), following your original instructions (python startup_dev.py -p 80 -s <IP_OR_DOMAIN>).
I stopped apache, verified that no process is listening on port 80 (using lpn and also trying to connect to port 80 from a remote web browser). I verified that I'm using the correct hostname (that I've mapped to the correct IP address), and I've tried invoking:
python3 startup_dev.py -p 80 -s tactic.sootherapy.bid (correct hostname; NB no http:// in command line this time)
python3 startup_dev.py -p 80 -s sootherapy.bid (I am aware that sootherapy.bid maps to a different IP address than my host tactic.sootherapy.bid; I just tried this to see if TACTIC or CherryPy would continue running, rather than exiting immediately, but still no joy)
python3 startup_dev.py -p 80 -s 18.191.182.243
All of these commands exit immediately.
www-data@ip-172-31-24-182:/home/apache/tactic/src/bin$ python3 startup_dev.py -p 80 -s 18.191.182.243
Data Directory [/home/apache/tactic_data]
Asset Directory [/opt/tactic/assets]
Temp Directory [/opt/tactic/tactic_temp]
Config path [/home/apache/tactic_data/config/tactic-conf.xml]
Registering project ... admin
Registering project ... default
Initializing Workflow Engine
Starting Scheduler ....
Starting TACTIC v4.7.0.b02 ...
www-data@ip-172-31-24-182:/home/apache/tactic/src/bin$
You'll notice that the hostname as represented in /etc/hostname and present in the command prompt seems to indicate that the correct IP address for this server is 172.31.24.182, but that's actually incorrect (I verified this using ssh to try and login to that IP address; the correct IP address is indeed 18.191.182.243).
It's clear to me that this way of trying to get TACTIC to run bypasses apache config files (great idea for troubleshooting!), but it seems to still be processing some TACTIC config information (eg. /home/apache/tactic_data/config/tactic-conf.xml)? Perhaps I've unwittingly misconfigured TACTIC? I don't think I modified /home/apache/tactic_data/config/tactic-conf.xml at all, but I've been reviewing it just in case I did so and forgot, looking for filenames present in it that are not actually present at the paths given in that file).
I verified (using ls) that the directories (Data, Asset, Temp) and the Config path listed in the output from startup_dev.py are actually there. One thing I noticed:
This section of /home/apache/tactic_data/config/tactic-conf.xml:
<!-- external services -->
<services>
<mailserver></mailserver>
<python>python</python>
<python_path></python_path>
<render_submit_class></render_submit_class>
<render_dispatcher></render_dispatcher>
<system_class></system_class>
<process_count>3</process_count>
<thread_count>50</thread_count>
<process_time_alive></process_time_alive>
</services>
...lists "python" as an external service. On this server, "python" invokes Python 2.7.17 (default, Apr 15 2020, 17:20:14) whereas "python3" invokes Python 3.6.9 (default, Apr 18 2020, 01:56:04). Could this be a problem for TACTIC or CherryPy?
Thank you for all the patient assistance you've been offering. I'm very grateful. Unfortunately though, these steps aren't working for me. By chance, any other suggestions? Does CherryPy require that the host be accessible via just the domain name (which is not the case for this server at this moment)?
I'd happily give you access to this server via ssh if you think that would help you help me troubleshoot this problem?
Thanks again.
