12-10-2019, 03:02 PM
Thanks! Seems running as apache was part of the issue although I had tried root so not sure overall. I did to remove the pid file as mentioned which does seem to start tactic now but, its odd that if I try to load from the browser it still looks like its down. Here is the output
[fedora@ip-172-31-24-227 init.d]$ sudo ./tactic_python3 start
TACTIC_INSTALL_DIR = /opt/tactic/tactic
TACTIC_SITE_DIR =
TACTIC_DATA_DIR = /opt/tactic/tactic_data
Starting Tactic: Success
[fedora@ip-172-31-24-227 init.d]$ ps -ef | grep python
root 495 1 0 14:42 ? 00:00:00 /usr/bin/python3 /usr/sbin/firewalld --nofork --nopid
root 3596 1 0 14:52 pts/0 00:00:00 su - tactic -m -c /usr/bin/python3 /opt/tactic/tactic/src/bin/monitor.py
tactic 3597 3596 0 14:52 ? 00:00:00 /usr/bin/python3 /opt/tactic/tactic/src/bin/monitor.py
root 4829 1 0 14:58 pts/0 00:00:00 su - tactic -m -c /usr/bin/python3 /opt/tactic/tactic/src/bin/monitor.py
tactic 4830 4829 4 14:58 ? 00:00:00 /usr/bin/python3 /opt/tactic/tactic/src/bin/monitor.py
fedora 4896 1016 0 14:59 pts/0 00:00:00 grep --color=auto python
[fedora@ip-172-31-24-227 init.d]$
If I start Tactic using startup.py it does actually load fine.
I did also try to reinstall Tactic using the rpm instead of the traditional install.py and it works but one thing i noticed is that it created a service file called tacitc.rpmnew?
I am going to spin up another instance and do a fresh install just to make sure I didn't screw anything up in all of this debugging. I will start with the rpm install this time.
it does seem to be going better starting with a fresh instance, it was likely my fault for using the install.py instead of the rpm installer. Thanks for all of the help! I know I will have more questions ;-)
[fedora@ip-172-31-24-227 init.d]$ sudo ./tactic_python3 start
TACTIC_INSTALL_DIR = /opt/tactic/tactic
TACTIC_SITE_DIR =
TACTIC_DATA_DIR = /opt/tactic/tactic_data
Starting Tactic: Success
[fedora@ip-172-31-24-227 init.d]$ ps -ef | grep python
root 495 1 0 14:42 ? 00:00:00 /usr/bin/python3 /usr/sbin/firewalld --nofork --nopid
root 3596 1 0 14:52 pts/0 00:00:00 su - tactic -m -c /usr/bin/python3 /opt/tactic/tactic/src/bin/monitor.py
tactic 3597 3596 0 14:52 ? 00:00:00 /usr/bin/python3 /opt/tactic/tactic/src/bin/monitor.py
root 4829 1 0 14:58 pts/0 00:00:00 su - tactic -m -c /usr/bin/python3 /opt/tactic/tactic/src/bin/monitor.py
tactic 4830 4829 4 14:58 ? 00:00:00 /usr/bin/python3 /opt/tactic/tactic/src/bin/monitor.py
fedora 4896 1016 0 14:59 pts/0 00:00:00 grep --color=auto python
[fedora@ip-172-31-24-227 init.d]$
If I start Tactic using startup.py it does actually load fine.
I did also try to reinstall Tactic using the rpm instead of the traditional install.py and it works but one thing i noticed is that it created a service file called tacitc.rpmnew?
I am going to spin up another instance and do a fresh install just to make sure I didn't screw anything up in all of this debugging. I will start with the rpm install this time.
it does seem to be going better starting with a fresh instance, it was likely my fault for using the install.py instead of the rpm installer. Thanks for all of the help! I know I will have more questions ;-)