When installing Mingle 2.0 (Unix version) I get an error when it reaches the template stage of the install process. Trying to import the templates manually after the install I get the same error “The export file appears to be corrupt.” This happens regardless of whether I’m updating from 1.1 or doing a fresh install of 2.0.

Known issue? Other thoughts?

Thanks.

Hi -

This is not a known issue.

Does the application appear to otherwise be working?

Which installer are you using?

What is the exact size of each of the three template files? Can you open them using a standard ‘unzip’ program?

Thanks, David.

The application does appear to be working normally otherwise.

The installer is mingle_unix_2_0_8323.tar

Scrum template is 32k. Agile hybrid template is 44k. XP template is 36k.

The files do unzip happily into a bunch of YAML files which seem clean and uncorrupted.

Additional data points:

An OS X install works fine, including templates. Exporting either a template or a project from the OS X installation and attempting to import the .mingle file into the Unix installation results in the same error message “The export file appears to be corrupt.”

I had the same problem importing a project exported from Mingle 1.1 and importing templates. I am running on Ubuntu 7.10. Importing works OK when I run ”/opt/mingle/MingleServer start” from a root terminal. When I start Mingle2 normally from my /etc/init.d/mingled script importing gives the “export file corrupt” message, but everything else seems to work. The templates are owned by mingle:mingle.
My startup script is as follows:

!/bin/bash

1. description: JRuby Mingle #
2. modified from thoughtworks studios script in the forums #
   MINGLE_USER=mingle
   [ -z ”$MINGLE_USER” ] && MINGLE_USER=nobody
   RETVAL=0
   start(){ su – $MINGLE_USER -c ”/opt/mingle/MingleServer start”
   }
   stop(){ su – $MINGLE_USER -c ”/opt/mingle/MingleServer stop”
   }
   case ”$1” in start) start ;; stop) stop ;; restart) stop start ;; *) echo $”Usage: $0 {start|stop|restart}” RETVAL=1
   esac
   exit $RETVAL

When I change this to MINGLE_USER=root at the start, importing works ok.

Hope this helps.

Thanks very much, David.

Running mingle as root solves the problem.

Did you find running as a non-root user a problem in any other situations or only for importing templates?

Abie -

It should not be necessary to run Mingle as root. In fact, we do not encourage you to do that. So long as the mingle user has full privileges on the mingle install directory and its subdirectories, Mingle should be fine. Any chance you could forward mingle.log to our support team?

<http://studios.thoughtworks.com/mingle-project-intelligence/support-requests>