← Back to team overview

registry team mailing list archive

[Bug 87122] Re: [needs-packaging] iFolder

 

I originally built and installed iFolder from source and was testing it
when I came across this discussion.

So I removed that version and installed the lucid version from the PPA
in my virtual machine and it worked. SO I played around with it for a
few days and found it be reliable. On my test machine I am still using
the client from my original build.

I decided to load on my Home Server a Viglen MPC, running the server
version of lucid.

The installation didn't go as smoothly as planned. When I originally
installed, then installation seemed to hang installing the mono-apache-
server process. After I got around this issue I could not get iFolder
working. So I used "apt-get purge" to remove all the packages, ensuring
I removed any configuration files created on my server.

I then proceeded to install ifolder3-enterprise again and this time it
did not have the same problem. I did however have an error coming from
the browser when trying to enter the admin program. I have attached a
screenshot of the error.

I looked in the Apache error.log and found this entry:

** (/usr/lib/mono/2.0/mod-mono-server2.exe:13566): WARNING **: The following ass
embly referenced from /tmp/www-data-temp-aspnet-0/91b03261/assembly/shadow/f6abe
9ac/b3c9c4c5_45622d69_00000001/Novell.iFolderAdmin.dll could not be loaded:
     Assembly:   log4net    (assemblyref_index=5)
     Version:    1.2.10.0
     Public Key: a5715cc6d5c3540b
The assembly was not found in the Global Assembly Cache, a path listed in the MO
NO_PATH environment variable, or in the location of the executing assembly (/tmp
/www-data-temp-aspnet-0/91b03261/assembly/shadow/f6abe9ac/b3c9c4c5_45622d69_0000
0001/).

I had noticed that on my TEST box I had a package called
"liblog4net1.2-cil", so I installed on my server, restarted apache and
everything worked after that.

I followed the procedure posted earlier, with the following changes
afterwards

1) Generated a Key for the box

$ sudo make-ssl-cert generate-default-snakeoil --force-overwrite

Not too sure if this is neccessary, just thought it was a good thing,
seeing it was the first time I ran a web server on the box.

2) Created a link between the iFolder configuration and the apache
configuration and then enabled the site

$ sudo ln -s /etc/ifolder-server/apache/ifolder_apache.conf /etc/apache2/sites-available/
$ a2ensite ifolder_apache.conf

3) Installed the log4net package

$ sudo apt-get install liblog4net1.2-cil

4) Amended the Public URL in the Servers area from
http://localhost/simias10 to http://<HOSTNAME>/simias10

And it all works. I am going to start trying out the client from the PPA
tonight.

Lastly, over my time playing with iFolder I have noticed some issues
with running the client through a Proxy Server. I don't run a Proxy
Server by default, but I do have one installed to run Dan's Guardian on,
for my kids. So I will have another look at that once I get the client
fully implemented on my home PCs

Keep up the good work.

Richard

** Attachment added: "Error from  Admin Web Interface"
   http://launchpadlibrarian.net/51503821/ifolder%20error.png

-- 
[needs-packaging] iFolder
https://bugs.launchpad.net/bugs/87122
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.