02-12-2014 02:49 PM
Tried installing Transport Gateway 3.5 under CentOS 6.x. I can start the process and I see a couple of items in the process list for it, but I don't see anything listening on port 80 when looking at the output from netstat and, of course, dont' see anything when trying to access the web gui.
Any ideas?
Solved! Go to Solution.
02-12-2014 03:37 PM
Make sure your hostname is in your hosts file. The HTTP daemon uses the hosts file to determine which IP Address to listen on.
02-12-2014 03:31 PM
There is an issue with the email functionality of Transport Gateway 3.5 (See CSCul96202) In addition, we have seen Windows 2008 issues installing the Transport Gateway version 3.5.
Some important points:
1. You need a complete reboot of the server for the Apache web server to come up at server boottime. It also needs to reboot if you make any configuration changes to the transport gateway URLs. The transport gateway uses the Apache web server for the HTTP(s) operations.
2. Make sure it fully installs successfully.
I would open a TAC case if you need further assistance moving forward or alternatively fallback to version 3.3 as a workaround. If you read the version 3.5 release notes, you can see if the version 3.3 bug fixes or version 3.5 new features would affect your operations.
02-12-2014 03:37 PM
Make sure your hostname is in your hosts file. The HTTP daemon uses the hosts file to determine which IP Address to listen on.
02-13-2014 07:00 AM
Verified I had the hostname and IP address in /etc/hosts and tried a reboot. Apache starts just fine, but I see nothing in the apache configuration or in /var/www/ that would direct any requests to the Transport Gateway software. Should the Transport Gateway be installing a vhost config or a directive in the apache configuration to direct requests for /TransportGateway to the gateway processes running in java?
Already tried installing previous versions of the Transport Gateway, but had just as much, if not more, trouble trying to get them running on Linux and Windows.
I'll submit a case to TAC to see what they find.
02-13-2014 01:41 PM
TG does not use apache. The HTTP listener is part of the TG java process.
[root@tspm-aus-tg4-rhel65 ~]# lsof -i
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 26546 root 79u IPv6 96108 0t0 TCP tspm-aus-tg4-rhel65.cisco.com:http (LISTEN)
java 26546 root 83u IPv6 96110 0t0 TCP tspm-aus-tg4-rhel65.cisco.com:https (LISTEN)
02-13-2014 02:32 PM
That's what I suspected.
Hmm. Curious. It doesn't seem to want to start a listener on the http or https ports. I see it listening on localhost:31000 and 32000, but I'm pretty certain those are used for something other than the web interface for the app.
wrapper 3286 root 7u IPv4 49309 0t0 TCP localhost:32000->localhost:31000 (ESTABLISHED)
java 3288 root 4u IPv4 49291 0t0 TCP localhost:32000 (LISTEN)
java 3288 root 68u IPv6 49308 0t0 TCP localhost:31000->localhost:32000 (ESTABLISHED)
Opened a case with TAC, but the rep is insisting that I neeed a GUI on the linux machine in order to troubleshoot, but I don't see how that would matter, so we'll see where that goes.
Not seeing much helpful in the log files. Seems pretty clean. No mention of missing components or unable to start services in either /var/log/messages or in the log files for the app.
I get a couple of processes: one wrapper process and the other is com.cisco.ca.csp.cso.conn.tg.service.TGServiceMain
I see in the jettyconfig.properties file that it has 80 and 443 conigured for http and https and the TGServiceMain process has the jars for jetty in the command line.
02-13-2014 03:04 PM
I also see the ports 31000 and 32000 on my working TG.
wrapper 26544 root 7u IPv4 96092 0t0 TCP localhost:32000->localhost:31000 (ESTABLISHED)
java 26546 root 4u IPv4 96073 0t0 TCP localhost:32000 (LISTEN)
java 26546 root 68u IPv6 96091 0t0 TCP localhost:31000->localhost:32000 (ESTABLISHED)
java 26546 root 77u IPv6 96106 0t0 TCP *:commplex-link (LISTEN)
java 26546 root 79u IPv6 96108 0t0 TCP tspm-aus-tg4-rhel65.cisco.com:http (LISTEN)
java 26546 root 83u IPv6 96110 0t0 TCP tspm-aus-tg4-rhel65.cisco.com:https (LISTEN)
The TG specific logs are in /opt/CSCOSchtg/tg/logs.
02-13-2014 03:10 PM
Looks like I'm missing some listeners or the TG just isn't fully starting for some reason.
Makes me wonder if there's still something not quite right with my /etc/hosts file or something and jetty isn't picking up the hostname, so it's refusing to start those additional listeners.
02-13-2014 03:21 PM
Bingo! There was something about the format of the /etc/hosts file that jetty (or some other component) just didn't like.
Blew it away and recreated and now the TG web interface starts.
Thanks for all your pointers!
02-13-2014 03:35 PM
Sorry about that. I meant Jetty, not Apache.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide