iFolder 3 Orphan Fix Utility

platforms

SUSE LINUX Enterprise Server 9

localizations

English

• how to use a download manager

This document (2973235) is provided subject to the disclaimer at the end of this document.

Associated File

Click the filename to download: orphanfixup.tar.gz 3813 bytes 08Feb2006 02:39PM

Abstract

Essentially the issue is caused by a user not being found when LDAP does a search for that user. This could happen if an admin accidently removes a user from the ifolder scope in LDAP and then tries to put the user back into scope. Or if the LDAP sync process successfully creates an LDAP connection but then sometime during the sync process can't access a user's object because of a network problem. When either of these happen, the user is deleted from the iFolder domain in Simias but the code failed to delete his POBox in Simias. When hooking up to eDirectory we use the same user GUID in Simias as exists in eDirectory so when the user tries to reprovision, we notice the POBox for that user already exists so we fail the provision.

Installation Instructions

This issue has been fixed in the iFolder 3.2 code. However that fix only prevents the problem from occurring. In your situation the problem has already occurred and some manual step will need to take place in order to correct the situation.

To fix the current issue, developement has created a utility that will reassoicate the users data with their iFolder account.

**Important** There are two cases that this utility will not handle

If a member of an iFolder set up an iFolder so that only the owner was deleted and then restrored. You will know if this is the case because the members client machine will continue to show a status of "1 item out of sync."

Solution: The member must revert the iFolder back to a regular folder and then set it up again.

If a member of an iFolder set up an iFolder where both the owner and member in question were deleted and then restored. You will know if this is the case because the member sets up the shared iFolder again and it disappears.

Solution: The owner is required to reinvite the member to the iFolder.

Reassociating the user with their iFolder Account (for the administrator)

The first thing that we need to do is download the utility provided by development to reassociate the user with their iFolder account. This can be found here: (under development)

Open a terminal and su to root.

su root

Extract the OrphanFixup.tar.gz file in a temporary location on the server.

tar xzfv OrphanFixup.tar.gz

Copy the orphanfixup, OrphanFixup.exe, and OrphanFixup.exe.config files to the /opt/novell/ifolder3/web directory.

cp orphanfixup OrphanFixup.exe OrphanFixup.exe.cofig /opt/novell/ifolder3/web

Shut down the Apache web server.

rcapache2 stop

Verify that Mono and Apache are not running.

ps aux | grep mono
ps aux | grep http

We need to switch to the wwwrun user, but before we can do that we need to go into the /etc/passwd file and change wwwruns user shell from /bin/false to /bin/hash

vi /etc/passwd

Press [Insert]

(change)
wwwrun:x:30:8:WWW daemon apache:/var/lib/wwwrun:/bin/false

(to)
wwwrun:x:30:8:WWW daemon apache:/var/lib/wwwrun:/bin/bash

Press [Esc]

Press [Shift] :

Type in wq and press [Enter]

Now we can change to the wwwrun user

su wwwrun

Now change to the /opt/novell/ifolder3/web directory

cd /opt/novell/ifolder3/web

Execute the orphanfixeup script with a --quiet paramenter. The --quite mode will show you which iFolders have been orphaned and will be restored without commiting to the changes.

./orphanfixup --quiet

(example output)
Changing collection Documents owner from admin to jharmon.
Changing collection POBox:0f066b74-758d-4b6c-a11c-e7758a342f35:49085e60-9803-01da-80c4-000c2916b5c2 owner from admin to jharmon.

If you were able to run the --quiet option with any internal exception errors, you can run the same utility using the --commit command. If you do see any internal exception errors, you are probably still in as root and didn't switch to the wwwrun user properly. The other error that you may run into is that the "user does not exist." This typically happens if you have deleted the user without syncing that information. However, since you deleted that user this error would just be informational.

./orphanfixup --commit

(example output)
Changing collection Documents:71809d75-454e-412c-af56-4e37c498d05a owner from admin:188f6ac8-f223-4b84-97b4-4356b4a3d64d to jharmon:49085e60-9803-01da-80c4-000c2916b5c2.
Changing collection POBox:0f066b74-758d-4b6c-a11c-e7758a342f35:49085e60-9803-01da-80c4-000c2916b5c2:7ccc4731-5941-46b0-95a4-0fedeeebec4d owner from admin:188f6ac8-f223-4b84-97b4-4356b4a3d64d to jharmon:49085e60-9803-01da-80c4-000c2916b5c2.

Switch back to the root user.

su root

Change wwwrun's user shell back to /bin/hash

vi /etc/passwd

Press [Insert]

(change)
wwwrun:x:30:8:WWW daemon apache:/var/lib/wwwrun:/bin/bash

(to)
wwwrun:x:30:8:WWW daemon apache:/var/lib/wwwrun:/bin/false

Press [Esc]

Press [Shift] :

Type in wq and press [Enter]

Restart the apache server.

rcapache2 start

Resyncing the users data (for the user)

The procedure is roughly the same for all three iFolder Clients (Windows, Linux, and Mac).

Start the iFolder client if it is not already running.

Right click on the iFolder icon in the Notification Panel, and select Accounts.

Select the iFolder account where this issue is occuring (probably the only one in the list) and then press the remove button.

At the confirmation dialog make sure there is NOT a checkmark in the "Remove my iFolders and files from the server." Then press the Yes Button.

Go to your file system and rename any folders that were setup as "iFolders" with some type of extension. (e.g. change a folder called "iFolder3" to "iFolder3.rpr" When you log in again, you will have to setup each of you iFolders again and let them download from the server. By changing the name it will keep them from conflicting with the existing folders. iFolder 3 will not do a cold merge of the data in an existing folder with an iFolder that is being setup.

Right click on the iFolder icon in the Notification Panel, and select Accounts.

Setup a new account with the server and use you current ID and password.

Click the login button.

Right click on the iFolder icon in the Notification Panel, and select iFolders. You should see a list of your iFolders in Black & White.

Select one of your iFolders and click on the Setup button. After you choose the location, the files should begin to download.

After the download has completed. You can copy any files that were modified during this outage from your renamed iFolder to the new iFolder that was just downloaded

Repeate Steps 10 and 11 for each iFolder on your system.

Issue

Symptom iFolder user has been disassociated with their data and their iFolder account.

Symptom Error: "An error was encountered while connecting to the iFolder server. Please verify the information entered and try again. If the problem persists please contact your network administrator. "

Symptom Error: "Object reference not set to an instance of an object."

Essentially the issue is caused by a user not being found when LDAP does a search for that user. This could happen if an admin accidently removes a user from the ifolder scope in LDAP and then tries to put the user back into scope. Or if the LDAP sync process successfully creates an LDAP connection but then sometime during the sync process can't access a user's object because of a network problem. When either of these happen, the user is deleted from the iFolder domain in Simias but the code failed to delete his POBox in Simias. When hooking up to eDirectory we use the same user GUID in Simias as exists in eDirectory so when the user tries to reprovision, we notice the POBox for that user already exists so we fail the provision.

File Contents

Self-Extracting File Name:  orphanfixup.tar.gz

Files Included       Size   Date         Time    Version   Checksum

\
ORPHANFIXUP.TAR.GZ       3813   08Feb2006    02:39PM

document

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.