Troubleshooting Installation

Articles to help with common installation issues and questions

This is a public Discussion Area  publicRSS

Welcome Guest

Log in if you have an account.

Otherwise, register for an account.

For more details, please visit the How This Site Works page.

Forums

Troubleshooting Recent Posts

  • caljedi
    install on linux+apache4
    Post last edited February 7, 2008 by caljedi
    Hi, i installed Mingle on this location:/usr/local/apache/htdocs/mingleMade the necessary additions to the HTTPD.conf file to create a new subdomain (let’s call it mingle.test.com which has a Docroot = /usr/local/apache/htdocs/mingle) when i run ”./MingleServer start”, I get: nohup: appending output to `nohup.out' and when i run ”./MingleServer status”, I get:The daemon is running. Plus, when i run: “ps -ef | grep java”, i get:/usr/bin/java -server -Dinstall4j.jvmDir=/usr -Dexe4j.moduleName=/usr/local/apache/htdocs/mingle/MingleServer -Xmx1024m -XX:MaxPermSize=128m -classpath /usr/local/apache/htdocs/mingle/.install4j/i4jruntime.jar:/usr/local/apache/htdocs/mingle/vendor/java/activation-1.1.jar:/usr/local/apache/htdocs/mingle/vendor/java/ant.jar:/usr/local/apache/htdocs/mingle/vendor/java/ChartDirector.jar:/usr/local/apache/htdocs/mingle/vendor/java/chartdir_lic.jar:/usr/local/apache/htdocs/mingle/vendor/java/commons-pool-1.3.jar:/usr/local/apache/htdocs/mingle/vendor/java/core-renderer.jar:/usr/local/apache/htdocs/mingle/vendor/java/forms_rt.jar:/usr/local/apache/htdocs/mingle/vendor/java/ganymed-ssh2-build210.jar:/usr/local/apache/htdocs/mingle/vendor/java/goldspike.jar:/usr/local/apache/htdocs/mingle/vendor/java/itext-2.0.5.jar:/usr/local/apache/htdocs/mingle/vendor/java/jetty-6.1.5.jar:/usr/local/apache/htdocs/mingle/vendor/java/jetty-plus-6.1.5.jar:/usr/local/apache/htdocs/mingle/vendor/java/jetty-util-6.1.5.jar:/usr/local/apache/htdocs/mingle/vendor/java/jruby-complete.jar:/usr/local/apache/htdocs/mingle/vendor/java/minium.jar:/usr/local/apache/htdocs/mingle/vendor/java/mysql-connector-java-5.0.5.jar:/usr/local/apache/htdocs/mingle/vendor/java/postgresql-8.2-505.jdbc3.jar:/usr/local/apache/htdocs/mingle/vendor/java/servlet-api.jar:/usr/local/apache/htdocs/mingle/vendor/java/svnkit.jar:/usr/local/apache/htdocs/mingle/vendor/java/tagsoup-1.1.3.jar:/usr/local/apache/htdocs/mingle/lib/java/jdic.jar:/usr/local/apache/htdocs/mingle/lib/java/start.jar:/usr/local/apache/htdocs/mingle/lib/java/version.jar com.install4j.runtime.Launcher start com.thoughtworks.mingle.Server false false /usr/local/apache/htdocs/mingle/log/stderr.log /usr/local/apache/htdocs/mingle/log/stdout.log true true false true true 0 0 20 20 Arial 0,0,0 8 500 version 1_1 20 40 Arial 0,0,0 8 500 -1 Also, edited the mingle.properties file to set the port number to 80 and dataDir to ”/tmp/mingle” Now, my question is: how do i access the site, cause when I go to mingle.test.com, I just see a listing of all the files present in the folder. How do i start the Configuration wizard?

    Recent Comment (3 of 4)

  • Suzie Prince
    New troubleshooting documentation
    Post posted May 31, 2011 by Suzie Prince , tagged System Administration

    Hi all

    Just a quick note to say that with Mingle 3.3 we added more troubleshooting installation help to our documentation. You can check this out here.

    Thanks and let us know what you think.

    - Suzie

  • ThomasD
    Mingle/Jetty SSL/https Configuration Help...8
    Post posted June 9, 2009 by ThomasD

    I'll try to number the steps I've done so they are easier to refer to...

    1. Obtained a wildcard certificate from a CA and installed into IIS7 using a CSR I generated in IIS7.

    2. Used the Windows server certificate tool to export the public and private key which prompted me to generate a password for the pair.

    3. Used openssl to convert the public/private key to the x509 format.

    4. Used: 'keytool -keystore keystore -import -alias jetty -file my_cert.crt -trustcacerts' to import the certificate into Jetty (executed in C:\Program Files\Mingle\jre\bin).

    ! This also asked for a password and confirmation, so I entered the same info as step 2. This gave me a keystore file in the same folder, and gave me a message it was sucessfully entered into the store !

    5. Added the following lines in jetty.xml:

        <Call name="addConnector">
            <Arg>
              <New class="org.mortbay.jetty.security.SslSocketConnector">
                <Set name="Port">443</Set>
                <Set name="maxIdleTime">30000</Set>           
                <Set name="keystore"><SystemProperty name="jetty.home" default="." />/jre/bin/keystore</Set>
                <Set name="password">mypassword</Set>
                <Set name="keyPassword">mypassword</Set>
                <Set name="truststore"><SystemProperty name="jetty.home" default="." />/jre/bin/keystore</Set>
                <Set name="trustPassword">mypassword</Set>
              </New>
            </Arg>
        </Call>

    There are three password fields.... password, keyPassword, trustPassword, so I entered the same certificate password I used for step 2. and step 4. above in all three fields? What am I mising?

    6. Since we run Mingle on a specific IP (sub-domain/port 80), seperate than IIS, I also specify the specific IP in the jetty.xml file in an additional addConnector section:

    <Call name="addConnector">
          <Arg>
              <New class="org.mortbay.jetty.nio.SelectChannelConnector">
                <Set name="port"><SystemProperty name="mingle.port" default="80"/></Set>
                <Set name="maxIdleTime">30000</Set>
                <Set name="Acceptors">1</Set>
                <Set name="Host">***.***.***.***</Set>
                <Set name="statsOn">false</Set>
                <Set name="lowResourcesConnections">1000</Set>
                  <Set name="lowResourcesMaxIdleTime">500</Set>
                  <Set name="headerBufferSize">16384</Set>
              </New>
          </Arg>
        </Call>

    When I have both these addConnector calls in the jetty.xml, I get the following in the log file:

    [2009-06-09 07:15:25,399] [Thread-0] [org.mortbay.log] Started SelectChannelConnector@***.***.***.***:80
    [2009-06-09 07:15:25,436] [Thread-0] [org.mortbay.log] Started SslSocketConnector@0.0.0.0:443

    But... when I try either http and https with both these addConnector statements in the jetty.xml file, it just reels and reels, never connecting to Mingle. If I remove the SslSocketConnector connector, it works fine again.

    Really my end goal is a single SSL connection through:

    https://mingle.mydomain.com/

    My questions are:

    1.) Do I need both addConnector statements in jetty.xml?

    2.) Do I need to specify my Mingle Host (IP) twice in the jetty.xml file (also in the SslSocketConnector section)?

    3.) Do I need the confidentialPort Set in the SelectChannelConnector AddConnector section of jetty.xml? What do I set it to?

    4.) Do I need to change the mingle.properties file. i.e. - Dmingle.memcachedPort or Dmingle.memcachedHost. Currently this is '11311' and 'localhost' respectively.

    Any help is appreciated!

    Thanks,

    Thomas

    Recent Comment (3 of 8)

  • ndoran
    Moving Mingle license1
    Post posted May 5, 2010 by ndoran

    How do I move a mingle license from one machine to another?  This is Mingle 2.3 under Windows.

    Thanks.

    Recent Comment (1 of 1)

  • Bil Simser
    One subversion repository per project?2
    Post posted September 19, 2007 by Bil Simser
    I realize the subversion is read-only and local (which is fine) but I only have one subversion repository (c:\svnrepos) so with multiple projects in Mingle can I configure each project to look at a different path in subversion? There’s no physical path to the files (like c:\svnrepos\projects\project1) so all my projects are just looking at the entire repository. If I have to create one subversion repository per project that’s going to be a pain so I can wait until we get better support. If it’s only local can we at least get the svn:// feature. Even if it’s restricted to svn://localhost at least we can do something like svn://localhost/project1/trunk, svn://localhost/project2/trunk, etc. Thanks.

    Recent Comment (2 of 2)

  • Mansi Shah
    Starting Mingle on a port other than 8080
    Post last edited March 3, 2010 by Badri Janakiraman

    This is specific to Windows users.

    If you want to to start Mingle on a port other than 8080, you need to modify the mingle.properties file. Depending on the version of Mingle you are using, the location of your mingle.properties file will differ

    With Mingle 2.3.1 or earlier

    1. Open the <mingle install dir>/MingleServer.vmoptions file and check the path of the data dir (this is the value of the -Dmingle.dataDir property)
    2. Locate the mingle.properties file located in that directory

    With Mingle 3.0 or later

    1. Open the <mingle install dir>/MingleServer.vmoptions file and check the path of the config dir (this is the value of the -Dmingle.configDir property)
    2. Locate the mingle.properties file located in that directory

    Once you locate the mingle.properties file

    1. Stop the Mingle service
    2. Edit the value of the -Dmingle.port property in the mingle.properties file to be the new port you wish to run Mingle on
    3. Save the file
    4. Restart the Mingle service

Recent Comments

Recent Participants

  • Debbie_W
  • StJohn
  • Christopher Dalid
  • Lisa
  • Mark Richter
  • Steve Elkind
  • Ron
  • weswilliamz
  • jschwartz
  • Andy Yates
  • Suzie Prince
  • Arun Kumar
  • Ian Moes
  • plano2ktho
  • teresa gracias
  • Ladinar
  • Ethan Teng
  • John Downing
  • bitle
  • Scott Baldwin

Search this Forum

Keyword Search

Filter Posts with Tags