I saw problems similiar to this in my environment. A few things to check: 1) make sure you have logging turned up to debug so you can make sure everything that can be logged is. You can change the level in /opt/traffic_ops/app/conf/production/log4perl.conf 2) make sure that all of the files under /opt/traffic_ops/app are owned by trafops:trafops. If there are files that are owned by root you could have issues that don't get logged. The latest postinstall should fix this, but I have run into the problem in the past. 3) make sure your certificates have the proper permissions or are owned by trafops as well.
Let me know if you have done all 3 of those things and are still having issues. Thanks, Dave On Mon, May 1, 2017 at 8:17 AM, X <[email protected]> wrote: > Dear Sir/Madam, > > We’ve been using ATC 1.7 on CentOS 6.5 and now we are trying to use 2.0 on > CentOS 7. > Unfortunately, during the installation of traffic_ops it always says > cannot connect and the status code of 500 is shown. `service traffic_ops > status` always is showing being offline whilst the service is started! > With the version 1.7 on CentOS 6.5 we have no problem, but this problem > occurs on CentOS 7 with the versions of 1.8 and 2.0 . Please let us know > what the reason is and how we can fix it. > > Yours Sincerely, > Vahedi >
