Manual Removal of iFolder 3.7 with Re-installation on OES 2 Linux


I had one of my remote branches that couldn't wait for Open Enterprise Server 2 Linux to get iFolder. The local server was NetWare 6 and therefore would require iFolder 2 and a migration in the near future. That wasn't the problem.

In the process of getting iFolder 3.7 to run on the OES 2 Linux server I had a bout of power outages that resulted in a corruption of the root partition and guess which part caught the corrupted blocks. Yep, iFolder's data store. I toyed with it for a while and then decided to just re-install it, especially since no one was using it yet.

Running simias-server-setup was very straightforward and simple, as long as you're root. My problem was it didn't fix my problem. I was still getting "Your session has been closed. Please log in." messages trying to login to the Admin Page.

I decided to rip and replace, or at least try, couldn't hurt, wasn't working anyway. It's not that difficult and no real pitfalls to speak of. Here is what I did to get it all back up and running.

Note: I would advise against this method on a critical or working iFolder server. It has not been tested on Master/Slave or cluster scenarios. This was done on a standalone iFolder server running iFolder 3.7 on OES 2 SP1 Linux. Please consult your physician.

First, we need to remove all iFolder packages from the server. Run YaST | OES Installation and Configuration or from the command line, yast oes-install.

I prefer to use Search and then enter "ifolder" and this will pull up a list of anything iFolder. We only need to remove three pieces:


You will get some dependencies about the plugins for migration. I resolved them by selecting to remove them also. (We'll re-install them later).

Select Next and wait for the uninstall to complete. Exit YaST and open a command line terminal. The following must be removed to ensure that there is no iFolder "residue" lingering around the server. This will also ensure a cleaner installation when we put iFolder back.

rm /etc/apache2/conf.d/simias.conf
rm /etc/apache2/conf.d/ifolder_admin.conf
rm /etc/apache2/conf.d/ifolder_web.conf
rm -rf /opt/novell/ifolder3
rm /tmp/mod_mono*

rm /var/adm/fillup-templates/sysconfig.ifldr3-novell
rm -rf /etc/sysconfig/novell/ifldr3
If you installed iFolder separately from the OES 2 Installation (Addon CD), then the two above lines would read:
rm /var/adm/fillup-templates/sysconfig.ifolder3-novell
rm -rf /etc/sysconfig/novell/ifolder3

The default data store for iFolder 3 is /var/simias

If you do not with to maintain this, then remove it and everything below,

rm -rf /var/simias

Otherwise, rename it or make a copy of it in a different location.

Now we need to reset the server to ensure there is nothing left hanging or some process is loaded.

Once the server is back on-line, login as root and either run YaST | OES Installation and Configuration, or command line, yast oes-install.

Select iFolder and accept to install the packages (ifolder-enterprise, ifolder-clients, ifolder-tsa) if you will be performing a migration, make sure you also install the enterprise plugin.

If you've run the configuration from YaST, click on the iFolder section and enter the needed parameters. When it's complete, restart apache2, by typing the following,

rcapache2 restart  

or you can restart the server once again, ensuring that iFolder loads upon reboot as expected.
Load the Web Admin as normal,


And login as your iFolder Administrator.

If you chose the default data store, you can add additional locations to where you put the original store, if desired.

Rip and replace isn't the recommended way of re-installing corrupt installations, but it is nice to know that you can, if your alternative is a complete server rebuild.



How To-Best Practice
Comment List