I guess you have read the OES admin guide.

novell-ifolder-mono is a part of the OES product which in turn is mono 2.4.2.3

On openSUSE 11.1, 11.2 suggested and tested mono version for ifolder server to run is mono 2.4.2.3 .

However it should run on mono 2.6 also which is available in openSUSE 11.3.

Hi,

I too found this confusing and ultimately used the mono that Ravi mentioned is included with OpenSuse 11.3.  I'm curious as to you successes though.  Would you post back.  I was never able to move forward under OpenSuse 11.2 and mono 2.4.2.3.

James

Well I simply downloaded the admin guide from here, which I guess is the OES admin guide its very Novll branded.

http://kablink.org/ifolder/documentation

The problem I am have been facing ever since my installation has ramped up to about 200+users is that mono process get stuck in wait state. I have done extensive research and I know this to be the problem. I have also applied all the proper settings for threading and concurrent coneections etc. Then I read this in the novell iFOlder 3.8 README under section 2.2 iFolder server:

http://www.novell.com/documentation/ifolder3/ifolder38_readme/data/ifolder38_readme.html#buxexmd

Support for mono 2.4 runtime environment

Mono build and runtime environment for iFolder is upgraded to mono 2.4. As part of OES, now iFolder bundles its own mono 2.4 runtime (novell-ifolder-mono) and iFolder will explicitly use this environment for running iFolder. This change in mono runtime addresses several issues related to thread synchronization and daily crashes. With novell-ifolder-mono, iFolder will not use system installed mono (SLES) and updates to latest mono runtime package will be available from regular OES 2 channel.

This is exactly what is going on with my installation and it makes sense that the way Novell solved this for OES is to tweak the mono package to handle these stuck threads. But it also begs the question what about me?? I tried to get novell-ifolder-mono-2.4 to install on OpenSuse 11.2 but that was a loosing battle the paths and scripts are totally different and Im not sure what version of mod_mono.so to use...

James thanks for chiming in your information is vry useful, how big is your ifolder installation? Maybe the mono thread synchronization problems are solved in mono 2.6 and that is an option.

I appreciate every crumb of your help, as I have been workin on this for sometime.

thanks

-s

So I want tothank

There were issues iwth mod_mono and server using more of CPU in 3.7 of which some were fixed in 3.8 . Please file a bug and describe the setup

Hi,

My instalation is just for home use ... very light about 4 people and I'm having a bit of trouble.  See thread 132.

James

The reason why there is novell-ifolder-mono on OES boxes is totally different thing. Yes moving to 2.4 solved the thread related issues and crashes for us on OES, but that is nothing to do with packaging novell-ifolder-mono explicitly or using a separate installed at a different path.

novell-ifolder-mono on OES is nothing but mono-2.4.2.3 on any open source platform. During that migration(mono 1.2.2 to 2.4) cycle we had raised couple of issues and mono team fixed them. All these fixes done for iFolder were released in mono 2.4.2.3, and we have verified with mono 2.4.2.3+ versions of mono on opensuse platforms and not encountered any threading related issue.

With above context, if your mono, mod-mono and xsp package version are appropriate(compatible, all are from one release version and >= 2.4.2.3), then ideally iFolder should work fine for you.

Please attach the simias & apache logs, so that we can verify the verify the issues you are referring are really to do with threading related issues or not. If the issues are to do with something else probably we can address them separately.