I will bee post on http://www.susethailand.com/suseforum/ as soon.

https://hostname.domain/admin

https://hostname.domain/ifolder

Thanks for the awesome howto!

I see now that you were looking in the “Mono:” repo, while I was looking in “Mono” (no colon).

Either way, maybe this will be a better place to get the 2.4.x line:

http://ftp.novell.com/pub/mono/archive/2.4.3/download/openSUSE_11.1/

As you can see, that’s the 2.4.3 version, but if you walk up the URL you’ll find the archive store of the previous versions….

Anyway, I believe I now have the correct locations of the correct Mono versions, etc., etc…. And, I just did a build to test it all.

Thanks again for the heads-up, and I hope it all works better for everyone.

yes, it seems a little messy there. I guess that it worked for me because I am using the x86_64 folder that still has mono 2.4 rpms:

http://download.opensuse.org/repositories/Mono:/2.4/openSUSE_11.1/x86_64/

The noarch and i586 folders have new stuff in them.

Do you know a way to tell them (repo admins) that the repos are mixed up?

Thank you for you great help !!!

Yep, it appears that the 2.4 stuff has recently dis-appeared (see the comment from Christian right above yours).

I’ll have to look in to it and report back. If anyone has a link to the 2.4 stuff (I should have saved it!)… or, if any of you have tried it with 2.6, let me know….

Thanks!

Whoa! Thank you for that. The 2.6 stuff wasn’t there when I originally did this, but I guess it is now.

Actually, after looking into it, it looks like all the 2.4 stuff is gone from both the URL I posted *and* the one you posted…? I’l have to look in to this… more to follow…

Happy New Year !!!

I tried it today on a fresh install of OpenSUSE 11.1 64 bit. The Mono repo in the instructions installs Mono 2.6 and later in the procedure I got and this error:

/usr/lib/apache2/mod_mono.so: wrong ELF Class ELFCLASS32 (when trying to config the admin server)

I went back and modified the repo to point to:

http://download.opensuse.org/repositories/Mono:/2.4/openSUSE_11.1/

And I installed Mono 2.4. With Mono 2.4, it works perfectly.

Thank you for the HowTo.

Regards,

Christian

Follow your steps to setup iFolder3.8,it works fine.
thanks your perfect post!!

I didn’t know that only opensuse 11.1 is compatible with iFolder 3.8. That explains a lot of things.

Well, I will stick to the 11.1 version for now.

Thank you very much for your help !!!

Thanks for the follow-up! Glad to hear you got that solved.

Yes, it’s true… Opensuse 11.1 is the only version of the OS on the server side that is currently supported at the time of this writing, at least according to the compatibility matrix provided by the iFolder 3.8 team.

It works just fine in opensuse 11.1 after I followed the same steps that I followed with 11.2.
There must be something different between the 2 releases of opensuse that interferes with iFolder.

I will try to compare them tomorrow (both VM are running now)

Thank you for your help

Some forums talk about permission issues. One of the is that wwwrun:www can not access /var/lib/wwwrun. That did not help me as well as changing the permissions on /etc/apache2
Do you think there is another folder that needs the proper permissions?

Would you recommend trying to install 11.1 and then iFolder? I am currently working on an up to date install of 11.2 without gnome or kde.

I will keep trying and I will let you know what I find.
Thank you again for your help and let me know if you have any suggestions.

Regards,

Thanks! Hmm… that’s a toughie…. If I had to guess, I’d have to say you got stuck with mono 2.0.x stuff instead of 2.4.x…. Do this and see what you get:
rpm -qa |grep -i mono

When I run it, I get these:
mono-data-sqlite-2.4.2.3-1.1
apache2-mod_mono-2.4.2-8.3
mono-data-2.4.2.3-1.1
mono-winforms-2.4.2.3-1.1
mono-core-2.4.2.3-1.1
mono-web-2.4.2.3-1.1

If you have the 2.0.x stuff, you probably got it because you didn’t use Yast (where you could see the versions) and you just dumped them in with zypper. How do I know? Because that’s how I did it the first time… Then I just had to force remove all the 2.0.x stuff, and replace it with the 2.4.x stuff… with Yast… Hence my caveat and warnings above…

Thank you for the detailed hwoto.
Unfortunately, in my setup it did not work. I followed every step and I was not able to log in as an admin.
As you pointed out above, I thought my issue had something to do with SSL so I set up simias, web, and admin without using SSL at all and I still can not log in as admin.
cat /iFolder/simias/log/Simias.log shows:

2009-12-10 17:05:00,936 [-79013616] INFO Simias.Storage.Provider.Provider – Created new store /iFolder/simias.
2009-12-10 17:05:01,658 [-79013616] ERROR Novell.Journaling.JournalService – Exception in Journal processEvent Object reference not set to an instance of an object at Simias.Storage.Identity.get_Credential () [0x00000]
at Simias.Storage.Identity.get_PublicKey () [0x00000]
at Simias.Storage.Store..ctor () [0x00000]

This error repeats all the time.

Any idea where to go from here?

Regards,

Christian
Dearborn, MI

I’ve seen that before in the Novell forums, and even had it happen to me once. It can be caused by a couple things, like perhaps SSL isn’t setup correctly, of the name resolution (short or long) don’t match between what you named the server and what you configured iFolder with. The time it happened to me, it was because I ran the admin setup and forced SSL, but my SSL wasn’t working 100%. I suggest re-running the admin setup with non-SSL, and see if that gets you logged in at least… then you know what’s at fault. If not that, then go back and make sure the naming is consistent all the way through…

- Jeremy