Troubleshooting
From iFolder
Here are some things to try if you need help using iFolder.
| Table of contents |
Turn on Debug Logging
Simias keeps a running log of events that happen in a file named Simias.log. By default, not many things are output into the file. The Simias.log's default location is:
Mac/Linux client - ~/.local/share/simias/Simias.log
Windows client - %USERPROFILE%\Local Settings\Application Data\simias\Simias.log
To change the level of logging to DEBUG, modify the Simias.log4net file. It's default location is:
Mac/Linux client - ~/.local/share/simias/Simias.log4net
Windows client - %USERPROFILE%\Local Settings\Application Data\simias\Simias.log4net
Change:
<level value="INFO" />
to
<level value="DEBUG" />
Check to make certain that the web service on the server is working
Many times it is difficult to know if the problem that you are having is a problem with the server or the client. One basic test to see if the server is responding to iFolder requests is to hit the Web Service directly using your web browser. To to this go to:
http://<servername or ip address>/simias10/DomainService.asmx
An authentication prompt will show and you will have to enter in proper iFolder credentials. After you have logged in, you will see a test page served up that lists some of the iFolder methods and such. If you see this page then you know that the server is listening for iFolder requests and is ready for business. If you can't get this page then you know that there is a problem with the server and not the clients. This is a useful first step when troubleshooting iFolder Enterprise problems.
Clear your ~/.wapi directory for Mac/Linux iFolder clients
Someone with more expertise on this one will have to give more detail, but every now and then, file locks or "whatever" gets messed up in Mono. Removing the ~/.wapi directory sometimes helps.
- Stop iFolder and any other mono processes
- rm -rf ~/.wapi
- Restart iFolder
As a last resort...
Now that things have become more stable, you don't really want to be doing this often because this will forget about ALL iFolders you've configured. But, if you need to reset your computer to a state where Simias/iFolder think they have never been run on your machine, you can delete the ~/.local directory for Mac/Linux clients or the %USERPROFILE%\Local Settings\Application Data\simias for Windows clients.
- Steps for Mac/Linux Client
- Stop iFolder
- killall -KILL mono
- rm -rf ~/.local
- Start iFolder
- Steps for Windows Client
- Stop iFolder. Verify in Task manager that the iFolderApp.exe and SimiasApp.exe are not running
- delete %USERPROFILE%\Local Settings\Application Data\simias
- Start iFolder
Now restart iFolder and hope for the best.
"n items not synchronized"
More information on this page.
"Unable to connect to iFolder server"
Ensure that Apache is listening for localhost connections. For example, add the following line to httpd.conf:
Listen 127.0.0.1:80
"Object reference not set to an instance of an object"
There are (at least) two possible reasons this might be occuring.
1. A personal firewall (Windows XP SP2 Firewall, McAfee Firewall, etc.) may not be allowing outgoing connections from simias.exe and/or iFolderApp.exe
You should configure your personal firewall to allow outgoing connections from simias.exe and iFolderApp.exe in order for things to work.
2. The path may not be correctly setup on a new iFolder server (see below)
If you have trouble logging in on a freshly installed iFolder server, and you receive the above message in the GUI client or the web access just won't log in, you probably don't have folders set up that iFolder needs for login operations. There is simple to fix, but you need to know exactly where to put the folders. This apparently varies per platform and/or release.
First, turn on debug logging. Change the two instances of 'INFO' in /var/lib/simias/Simias.log4net to 'DEBUG', restart Apache and try to log in with the ifolder client again.
Now check your log ( /var/lib/simias/log/Simias.log ) and search for 'Could not create user key store'. This should be immediately followed by the path name of the folder(s) you need to create (omit the 'keypairs' on the end of the path). Stop your web server. Create the folder path if it does not exist, and be sure that your web server has read and write access to it.
- For example, as on my Suse 10.1 running ifolder3-server 3.5.6138:
sudo mkdir -p /var/wwwrun/.config/.mono/ sudo chown -R wwwrun.www /var/wwwrun/.config/
Restart and go.
This problem may also occur if the folders exist, but have access permissions applied too broadly. The directory /var/www/html/.config/.mono/keypairs must have 0700 (o=rwx) permissions, or else Mono will fail with an "improperly secured keypairs" message. This message will be displayed in the Simias.log file when logging is in DEBUG mode.
3. This could happen also on an iFolder client on Linux. As a workaround you can also rename the folder /home/<your_user_name>/.config/.mono/keypairs to something else and restart iFolder, it will recreate the folder with the correct rights
FlaimWrapper error in web.log or couldnt login via web
Since a log period i had the problem that i coudnt login to the simiasserver, i found the solutuion by linking libflaim and FlaimWrapper by hand.
error:
vi /var/lib/simias/log/web.log
System.DllNotFoundException: FlaimWrapper at (wrapper managed-to-native) Simias.Storage.Provider.Flaim.Flaim4:FWCreateStore (string,intptr&,intptr&) at Simias.Storage.Provider.Flaim.Flaim4.CreateStore () [0x00000] at Simias.Storage.Provider.Flaim.FlaimServer.CreateStore () [0x00000] at Simias.Storage.Provider.Flaim.FlaimProvider.CreateStore () [0x00000] at Simias.Storage.Provider.Provider.Connect (Simias.Storage.Provider.ProviderConfig conf, System.Boolean& created) [0x00000] at Simias.Storage.Store..ctor () [0x00000] at Simias.Storage.Store.GetStore () [0x00000] at Simias.Security.Web.AuthenticationModule.get_StoreReference () [0x00000] at Simias.Security.Web.AuthenticationModule.VerifyPrincipalFromRequest (System.Web.HttpContext context) [0x00000] at Simias.Security.Web.AuthenticationModule.OnAcquireRequestState (System.Object source, System.EventArgs eventArgs) [0x00000] at (wrapper delegate-invoke) System.MulticastDelegate:invoke_void_object_EventArgs (object,System.EventArgs) at System.Web.HttpApplication+<>c__CompilerGenerated1.MoveNext () [0x00000] </pre></code>
solution:
# ldconfig -l /usr/lib/libflaim.so.4.1 # ldconfig -l /usr/local/lib/libFlaimWrapper.so
better:
# echo "PATH TO libFlaimWrapper.so.0.0.0" >> /etc/ld.so.conf
"Cannot create iFolders or accept current invitations on OSX Client"
This applies to versions 3.4 & 3.5 OSX iFolder Clients. It appears that the mono version 1.1.7.2 is causing the simias process to be terminated (assumably due to some sort of an access violation in native code). Testing has been done with mono version 1.1.13.8 and the OSX clients appear to work properly.
