January 9, 2006
This Readme discusses known issues for Novell® iFolder® 3.2 for OES SP2 Linux and for the iFolder™ client for iFolder 3.2.
In this document, Novell iFolder 3.2, iFolder 3.2, Novell iFolder, and iFolder (used alone) all refer to Novell iFolder 3.2 and its components. When referring to Novell iFolder 2.x server or client, the version 2.x is always specified. When referring to the iFolder client for Novell iFolder 3.2, iFolder client is specified.
Your server must satisfy the system requirements for OES SP2 Linux.
For details, see Prerequisites and Guidelines in the Novell iFolder 3.x Administration Guide.
The iFolder client for Linux* requires the Mono® framework for Linux, a GNOME* desktop, GTK-Sharp, and GTK-HTML2. The versions of Mono and GTK-Sharp that you need are included with the iFolder for Linux install package. GNOME and GTK-HTML2 are default install components of NLD.
The iFolder client for Windows requires the Microsoft* .NET v1.1 framework. Make sure you have installed the latest updates for .NET 1.1.
The iFolder client for Macintosh requires the Mono framework for Macintosh. The version of Mono that you need is included with the iFolder for Macintosh install package.
For details, see Prerequisites and Guidelines in the iFolder User Guide for Novell iFolder 3.x.
After you install an iFolder enterprise server, users can download the client install files from the server’s iFolder 3.x Welcome page. For instructions, see Downloading the iFolder Client Install Files in the iFolder User Guide for Novell iFolder 3.x.
For information, see the following:
For information, see the following sections in the Novell iFolder 3.x Administration Guide:
There is no automatic upgrade or migration path from previous versions of Novell iFolder 2.x on any platform. For information, see Coexistence and Migration Issues in the Novell iFolder 3.x Administration Guide.
For information, see Getting Started in the iFolder User Guide for Novell iFolder 3.x.
There is no automatic upgrade or migration path for existing Novell iFolder 2.x clients on any platform. For information, see Coexistence and Migration Issues in the iFolder User Guide for Novell iFolder 3.x.
This section describes known issues for the iFolder enterprise server and Web Access server.
During the iFolder enterprise server configuration, if the administrator specifies a new user in a new context for the iFolder Admin username or the iFolder Proxy username, YaST does not validate that the context exists and does not create a context for the usernames if it does not already exist. This causes the iFolder server configuration to fail because the user cannot be created.
To avoid this problem, specify only existing users and contexts. Make sure to create the new context before you configure iFolder.
When configuring services for an iFolder 3.x enterprise server in YaST, the should not be set to the root of a volume, such as at the root (/) or at the root of a mount point (such as /mnt/ifolder3). Make sure to add a directory, such as /data, to the end of the path. For example:
This issue does not affect upgrades; it applies only to the configuration of newly installed iFolder enterprise servers.
iFolder Web Access does not support the uploading and downloading of 10 MB or larger files. To upload or download files that are 10 MB or larger, users must use the iFolder client.
This section describes known interoperability issues with other Novell products.
iFolder does not support forward authentication for single sign-on through identity-based Web security services that control access to application and network resources across technical boundaries, such as Novell iChain® 2.3.
iFolder does not support path-based multi-homing mode for a Novell iChain accelerator.
For Windows users, when the iFolder server tries to trigger an automatic upgrade of the iFolder client for iFolder 3.0 to the iFolder client for iFolder 3.1 or later, the automatic upgrade fails if the user has the option set on the target Windows computer. A bug in the 3.0 client does not check for a client upgrade unless the user logs in manually when iFolder starts.
This problem does not occur if the option is not set, and the user logs in to the account manually.
To resolve this problem, users should do the following for each account where the option is set:
Click the icon, then select to open the Accounts dialog box.
Select the iFolder account.
Deselect (disable) .
Log out of the account by clicking .
On successful logout, log back in.
The user is prompted to upgrade the client.
IMPORTANT:This defect has been fixed in the iFolder client for Novell iFolder 3.1 and later.
This section describes known issues for backup and restore of iFolder data on the server.
If you are restoring an entire iFolder and want to ensure that its content is in the exact state it was in when it was backed up, you should first delete the iFolder from the server using a client or the iFolder 3.x plug-in to iManager. Deleting the iFolder is not necessary to restore any (or all) of the files in the iFolder.
If an entire iFolder 3.x store is restored while clients are connected to it, some clients might be asked to set up some of their iFolders when the restore has completed. A full restore deletes the store first, and if a client synchronizes to the store while its iFolders are deleted on the server, the client also deletes the iFolders (while leaving the actual files intact on the client). No data is lost or corrupted, but users might be confused by being asked to set up an ifolder that they believe already exists.
To avoid this issue, make sure to disconnect users from their iFolder accounts before initiating the full restore, then prevent the users from logging in to the accounts during the restore.
If your iFolder server is configured to use an NSS (Novell Storage Services™) volume, a rug pin update of OES Linux to OES SP1 Linux breaks the iFolder server. During the upgrade, NSS changes the location of the wwwrun user’s home directory from /home/wwwrun to /var/lib/wwwrun. After the upgrade, iFolder cannot find its configuration file, Simias.config, which is located in a path under the wwwrun user’s home directory.
In the initial release of OES, if iFolder is configured to use an NSS volume, the default location of Simias.config is
/home/wwwrun/.local/share/simias/Simias.config
In OES SP1 and later, the default location is
/var/lib/wwwrun/.local/share/simias/Simias.config
This issue affects only iFolder servers that are configured to use NSS volumes.
To resolve this problem, after the rug pin upgrade, do the following:
Open a terminal console, then log in as the root user.
Copy the Simias.config file to the new location. At a terminal console prompt, log in as the root user, then enter (all on the same line, of course)
cp /home/wwwrun/.local/share/simias/Simias.config /var/lib/wwwrun/.local/share/simias/.
Stop and start the Apache services. At a terminal console prompt, enter
/etc/init.d/apache2 stop
/etc/init.d/apache2 start
When Apache restarts, the iFolder configuration file is found, and iFolder services work as expected.
The novell-nrm-welcome packet was inadvertently left off the OES SP1 CD builds. To get a patch, see Recommended Update for Two OES Welcome Pages TIDab4c475d099117707906fb2e7ac27257.
When you upgrade from OES to OES SP1, some soft links that support the nightly rollover might be overwritten. If you use iFolder 3 in production in a high server utilization, you might observe that the nightly rollover fails after upgrading.
If you are experiencing rollover problems, try re-creating the following soft links.
Open a terminal console, enter su, then log in as the root user.
At the console prompt, enter the following ln commands (all on one line):
ln -f -s /opt/novell/ifolder3/etc/simias-start /etc/cron.daily/z-simias-start
ln -f -s /opt/novell/ifolder3/etc/simias-stop /etc/cron.daily/a-simias-stop
Attempting to access an iFolder 3.x server via an Apache virtual host fails with the following error:
Unable to connect to the iFolder Server
The request failed with HTTP status 302: Found
In some virtual server configurations, all requests go to the Apache Virtual Server’s DocumentRoot instead of the DocumentRoot of the server. If the inspection.wsil file does not exist in the Virtual server’s DocumentRoot, the clients are unable to connect to the server.
To work around this issue, copy the /opt/novell/ifolder3/etc/inspection.wsil into the virtual host’s DocumentRoot for each Apache VirtualHost that is configured.
Open a terminal console and log in as root.
At the console prompt, enter (all on one line)
cp /opt/novell/ifolder3/etc/inspection.wsil /VirtualHosts-DocumentRoot/.
Replace VirtualHosts-DocumentRoot with the path specified in your configuration.
Linux does not allow you to umount a volume if any file is currently open. If your system is going comatose when you try to unload the cluster, it is probably because you have open user connections and files on the volume. You must allow enough time for the connections to be closed before the umount is executed.
To avoid this problem, add the following lines between the commands for Request to stop service and Deleting the IP address:
#stop service otherwise
sleep 10
ignore_error fuser -k /$MOUNT-POINT
sleep 5
Replace /$MOUNT-POINT with the actual path of the mount point of your iFolder data store. For example:
#stop service otherwise
sleep 10
ignore_error fuser -k /mnt/ifolder3
sleep 5
Tune the script until the cluster no longer goes comatose under an operational load when the unload script is called. If the system goes comatose under a full load, increase the sleep time until the cluster is able to successfully execute the unload instead of going comatose.
This section describes known issues for iFolder client.
This section describes known issues for the iFolder client for Linux.
iFolder for NLD supports the GNOME desktop. The KDE desktop is not supported; however, users have reported that the iFolder client for Linux also works on KDE.
If you create iFolders on a FAT32 file system on Linux, avoid naming files in all uppercase characters. The VFAT or FAT32 file handling on Linux automatically changes the filenames that are all uppercase characters and meet the MS-DOS 8.3 file format from all uppercase characters to all lowercase characters. This creates synchronization problems for those files if the iFolder is set with the Read Only access right.
To avoid this problem for iFolders on FAT32 file systems on Linux, do one or more of the following:
Before you can create new iFolders or set up shared iFolders
on a FAT32 file system on your Linux computer, the iFolder user
must own the FAT32 mount point where you want to store the iFolders, and
the /etc/fstab file must
explicitly identify the user’s local user ID for the mount
point. For information, see Creating iFolders on a FAT32 Mount Point
(Linux)
in the iFolder User Guide for Novell
iFolder 3.x.
This is required because FAT32 does not support file permissions. Any other file system that does not support permissions would have the same issue.
The Japanese welcome page will probably appear with garbled characters until you change the encoding to Japanese (Shift-JIS).
In Mozilla, you can do this through the menu choices.
In the iFolder client for Linux, the Help URL always defaults to English instead of the actual locale of the client workstation. The default URL is
file:///opt/novell/ifolder3/share/ifolder3/help/en/doc/user/data/front.html
You can manually modify the URL in the Web browser to retrieve the Help files for your locale by replacing en with another supported language code listed in the following table:
This section describes known issues for the iFolder client for Windows.
When upgrading the iFolder client, if you specify a different location for installing the iFolder client files, the upgrade deletes the Simias directory, where information about your existing iFolder accounts and their iFolders is stored. When you start iFolder after the upgrade, iFolder prompts you to set up new accounts and iFolders.
To avoid this problem, do not change the install location when upgrading iFolder.
If you have already encountered this problem, you must set up your accounts and iFolders again.
For Windows users, when the iFolder server tries to trigger an automatic upgrade of the iFolder client for iFolder 3.0 to the iFolder client for iFolder 3.1 or later, the automatic upgrade fails if the user has the option set on the target Windows computer. A defect in the 3.0 client does not check for a client upgrade unless the user logs in manually when iFolder starts.
This problem does not occur if the option is not set, and the user logs in to the account manually.
To resolve this problem, users should do the following for each account where the option is set:
Click the icon, then select to open the Accounts dialog box.
Select the iFolder account.
Deselect (disable) .
Log out of the account by clicking .
On successful logout, log back in.
The user is prompted to upgrade the client.
IMPORTANT:This defect has been fixed in the iFolder client for Novell iFolder 3.1 and later.
When installing the iFolder client on a Chinese Windows operating system, the Chinese installer fails to properly detect whether the user’s Locale is set to Chinese Traditional or Chinese Simplified. Both Chinese Traditional and Chinese Simplified versions are installed instead of just one or the other.
The iFolder client for Windows does not support the .NET 2.0 Framework. The client requires the latest .NET 1.1 Framework to be installed on the machine.
This section describes known issues for the iFolder client for Macintosh.
At random instances, when the iFolder client for Macintosh starts, the synchronization process fails to start normally. When this problem occurs, the client responds as if there are no accounts set up on the client. It prompts the user with the option to set up an account. If the user attempts to set up an account, the setup fails, leaving the client in an unusable state.
To resolve this problem, exit the iFolder client, then start iFolder again. The problem corrects itself.
Rather than replacing the existing application files, upgrading the iFolder client for Macintosh from 3.0 to 3.1 or later leaves the 3.0 application files and adds the newer application files. After the upgrade, the user can start both the 3.0 and 3.1 or later applications. This causes problems because each of the applications access the same Simias process, and the user sees various errors occur.
Although the iFolder client for Macintosh install packages do provide an uninstall script, uninstalling 3.0 before installing 3.1 is not recommended because it removes the user’s Simias directory, which contains all of the iFolder account and iFolders information.
To avoid this problem, do the following before you upgrade the iFolder client for Macintosh from 3.0 to 3.1 or later:
If the iFolder client is running, shut it down by quitting the application.
Open a window, then navigate to the Applications directory.
Drag the iFolder application directory (the icon) to the trash.
Proceed with the iFolder 3.1 or later install or upgrade.
This section describes known issues for the Web Access interface.
iFolder Web Access does not support the uploading and downloading of 10 MB or larger files. To upload or download files that are 10 MB or larger, you must use the iFolder client.
The Portuguese-Brazilian (pt) translation of the iFolder Web Access Help is present, but shows up in English.
The following sources provide information about Novell iFolder and the iFolder client and are available on the Novell iFolder 3.x Documentation Web Site:
The following sources provide additional information:
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
A trademark symbol (®, ™, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.
Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to www.novell.com/info/exports/ for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2006 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.novell.com/company/legal/patents/ and one or more additional patents or pending patent applications in the U.S. and in other countries.
eDirectory is a trademark of Novell, Inc.
iChain is a registered trademark of Novell, Inc., in the United States and other countries.
iFolder is a trademark of Novell, Inc.
Mono is a registered trademark of Novell, Inc., in the United States and other countries.
Novell is a registered trademark of Novell, Inc., in the United States and other countries.
Novell iFolder is a registered trademark of Novell, Inc., in the United States and other countries.
Novell Storage Services is a trademark of Novell, Inc.
SUSE is a registered trademark of Novell, Inc., in the United States and other countries.
ZENworks is a registered trademark of Novell, Inc., in the United States and other countries.
All third-party trademarks are the property of their respective owners.