NWI Tech Support

You are currently browsing comments. If you would like to return to the full story, you can read the full entry here: “OpenGTS Install”.

1. tdurbin says:

   February 28, 2012 at 2:20 pm

   jeffreywt, I like your determination… good catch, by the way. Looks like we’ll have to address the 64-bit OS issue on the next go-round. Thank you for the feedback.
   Just as a side note. I did get a moment to peek in on the LiveCD and ran an update to version 2.4.0 via the following two commands:
   sudo sed -i 's|2.3.9|2.4.0|' /opt/opengtslive.sh
sudo sh /opt/opengtslive.sh
   The result produced some errors I didn’t get a chance to look over, but afterward I was able to login and verify version 2.4.0.
   I would also assume this will work as well for the install script… but I have not had a chance to test.
2. jeffreywt says:

   February 28, 2012 at 1:58 pm

   Looks like the issue was the x86_64 OS. I used CentOS 6.1 for i386/i686 and it was able to find the proper Java paths. Sorry to blow up the comments here with my issues but perhaps this will be helpful. Thanks again!
3. jeffreywt says:

   February 28, 2012 at 11:39 am

   Same errors in 6.1. I am in a KVM environment but I’m not sure how that would affect Java within my VM. I suppose I will try the LiveCD version until the script issues are addressed. Thanks!
4. jeffreywt says:

   February 28, 2012 at 10:17 am

   CentOS 6.2 x86_64 — I will try 6.1 and report back if it works. Thanks!
5. tdurbin says:

   February 28, 2012 at 10:15 am

   jeffreywt, what version of CentOS are you running?
   cat /etc/redhat-release
   I have only tested the script against 6.0 and 6.1…
6. jeffreywt says:

   February 28, 2012 at 9:31 am

   Thanks for the suggestions but no.

   tomcat6 was not listening on IPv4. I re-installed CentOS and did not include IPv6. This did not fix anything though, still a white page. I noticed this time there were errors during the install script.

   See this output: http://pastebin.com/ueCmER7p

   Thanks!
7. tdurbin says:

   February 28, 2012 at 8:10 am

   jeffreywt, the address should actually be typed in as such:
   http://localhost:8080/track/Track
   Let me know if this resolves your issue.
8. jeffreywt says:

   February 28, 2012 at 8:00 am

   I had no problems following the instructions here but when I connect to http://localhost:8080 it serves me a white page.

   Any ideas?
9. tdurbin says:

   January 23, 2012 at 11:14 am

   Andreas, thanks for the feedback. My pleasure, by the way… Have you tried compiling the OpenDMTP J2ME-Client? Unfortunately, I do not own a Windows mobile to test.
10. Andreas says:

    January 23, 2012 at 1:09 am

    Hey, thanks for this post. Great work!
    Do you know any app for windows mobile devices to connect to OpenGTS? I looked at OpenDMTP for this, but I only got confused…
11. tdurbin says:

    December 22, 2011 at 6:39 pm

    Duc,
    No problem, good to hear all went as planned.
    I’m not positive on this but I believe the add-ons listed under GeoTelematic’s site are related to the Enterprise package as I couldn’t find a ‘dcservers’ directory in the open source zip.
12. Duc says:

    December 22, 2011 at 1:42 pm

    tdurbun,
    I wanted to thank you for the script… I was able to install opengts without any issues and tested it with gps2opengts…

    But i do have question for you.
    Do you know if i can configure additional add-on modules with opengts myself or do i have to get GTS Enterprise?

    thanks for the script again.
13. tdurbin says:

    November 12, 2011 at 7:47 am

    Thank’s pjwelsh, I was looking at the script scratching my head… I now see you meant the post and added the .com.
    The script is very sloppy and to tell you truthfully, I’m not much of a programmer/scripter.
    If you have ideas or improvements, I would love to implement them and thank’s again for the feedback.
14. pjwelsh says:

    November 11, 2011 at 11:52 pm

    “wget http://www.nwitechsupport/download/66/”
    I think you missed the “.com”. I don’t get much without adding it
    I quick test script of the the export/mkdir/chown did not show there is an issue, but a “eval” at the beginning might help keep the variable in play in general.
15. tdurbin says:

    November 11, 2011 at 6:12 am

    pjwelsh,
    There’s an issue with wget? Thanks for the feedback, by the way.
    Run level 4 doesn’t necessarily need to be there, but I figured I’d tag it just in-case anyone decided to define it.
    I was having a problem with chown not respecting the $GTS_HOME variable and ran with it… sloppy, I know.
    I found some great info from your site that lead me to piecing together this script, so I owe you another thank you for the inspiration.
16. pjwelsh says:

    November 10, 2011 at 10:19 pm

    Errrrr… fix wget line
    Decent auto install script otherwise. Not sure about chkconfig and run level “4″ (unused), however. Could use your $GTS_HOME variable in a few more places.
    I do have to admit that I did not know about or had to use/create the /etc/init.d/opengts or the startServers.sh script it points too. My testing functioned without using them directly noted http://pjwelsh.blogspot.com/2011/10/centos-60-opengts-238-install-and-setup.html
17. tdurbin says:

    November 10, 2011 at 9:39 pm

    Alysson,
    Unfortunately there isn’t a best configuration… it all depends on your environment. Let’s start with your LAN, do you have a router/firewall, if so what is the model and make (for example: Linksys WRT54G, Asus RT-N16, etc…)? What IP do you see on the OpenGTS server? These two questions may hold your answer. Let me know and I’ll do the best I can for you.
18. Alysson says:

    November 10, 2011 at 7:56 pm

    Would explain to me the best configuration step in the ip and port opengts once created with this script?