cnystrom Absent Member.
Absent Member.
2948 views

iFolder 3.6 OES2 on NSS Volumes

Here is the scenario:

I've installed a new OES2 Linux server into our existing NetWare 6.5 TREE. I followed all the steps in the Installation Guide pertaining to the creation of NSS Volumes. After the server installation was complete, I installed iFolder and began configuring it. I pointed it to the /media/nss/DATA/ifolder storage location and finalized the configuration. I also added the wwwrun rights per the doucmentation to the root of the NSS Volume (rights -f /media/nss/DATA -r rwfcem trustee wwwrun.rrr.all.tree). Everything seems to finish fine and there are no errors. When I try to login to the iFolder Adminstration I repeatedly get "Your session has been closed. Please log in.". I've tried restarting Apache and Tomcat and rebooting the server with the same result. So, I then reconfigured iFolder and tested it with the Default Storage Location (/var/simias/data) and I am able to login without any issues. Is there something that I am missing ?

Please Help!
Labels (1)
0 Likes
12 Replies
Anonymous_User Absent Member.
Absent Member.

Re: iFolder 3.6 OES2 on NSS Volumes

cnystrom wrote:
> Here is the scenario:
>
> I've installed a new OES2 Linux server into our existing NetWare 6.5
> TREE. I followed all the steps in the Installation Guide pertaining to
> the creation of NSS Volumes. After the server installation was
> complete, I installed iFolder and began configuring it. I pointed it
> to the /media/nss/DATA/ifolder storage location and finalized the
> configuration. I also added the wwwrun rights per the doucmentation to
> the root of the NSS Volume (rights -f /media/nss/DATA -r rwfcem trustee
> wwwrun.rrr.all.tree). Everything seems to finish fine and there are no
> errors. When I try to login to the iFolder Adminstration I repeatedly
> get "Your session has been closed. Please log in.". I've tried
> restarting Apache and Tomcat and rebooting the server with the same
> result. So, I then reconfigured iFolder and tested it with the Default
> Storage Location (/var/simias/data) and I am able to login without any
> issues.



> Is there something that I am missing ?
>
> Please Help!
>
>


If so I missed it too. I had the same results...

Hopefully someone has a solution. No chance so far to get back to this
myself.


--
Will R
PMC Consulting
0 Likes
Vimal2 Absent Member.
Absent Member.

Re: iFolder 3.6 OES2 on NSS Volumes

Does the location /media/nss/DATA/ifolder exist and is it mounted? You have to create it manually as it is not created during the configuration.
You might also want to do a tail -f /var/log/apache2/error.log at the server to see if there are any permission problems.
fyi, I created the data storage location on the NSS volume using iManager, added wwwrun.as a trustee. It works fine.

🙂 New to OES2
0 Likes
cnystrom Absent Member.
Absent Member.

Re: iFolder 3.6 OES2 on NSS Volumes

YES the location exists and it is mounted. I've removed the server from my TREE and deleted all the existing objects and reinstalled. SAME result. I'm calling support today! After all, we are a Platinum Partner and have unlimited tech support for the Open Workgroup Suite. I'll post and let you know the solution!

Thanks for the help
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iFolder 3.6 OES2 on NSS Volumes

Hi,
One more question ? Can you check the log that is being created in
location /media/NSS/DATA/iFolder/simias/Simias.log.
Thanks
Nitin

cnystrom wrote:

>
> YES the location exists and it is mounted. I've removed the server from
> my TREE and deleted all the existing objects and reinstalled. SAME
> result. I'm calling support today! After all, we are a Platinum
> Partner and have unlimited tech support for the Open Workgroup Suite.
> I'll post and let you know the solution!
>
> Thanks for the help
>
>


0 Likes
jknash Absent Member.
Absent Member.

Re: iFolder 3.6 OES2 on NSS Volumes

I had the same issue and never got it fixed. I ended up configuring my server with EVMS volumes instead of NSS. I figured people shouldn't need to access the ifolder data volume directly anyway, so NSS is overkill.
0 Likes
cnystrom Absent Member.
Absent Member.

Re: iFolder 3.6 OES2 on NSS Volumes

After opening up a tech support call with Novell, granting control of my workstation and leaving to them for 2 days we got this issue resolved. The case is still open, as it appears (not confirmed yet) that there is a defect/bug in the product. Once I have more information, I will post it here.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iFolder 3.6 OES2 on NSS Volumes

cnystrom wrote:
> After opening up a tech support call with Novell, granting control of my
> workstation and leaving to them for 2 days we got this issue resolved.
> The case is still open, as it appears (not confirmed yet) that there is
> a defect/bug in the product. Once I have more information, I will post
> it here.
>
>


Not surprised. I banged my head against the wall for awhile on this one
-- just never had a chance to log a support call or a get back to it.


--
Will R
PMC Consulting
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iFolder 3.6 OES2 on NSS Volumes

Hi,
It will be more appropriate to check the log for this .I also got this issue
some time and the reason was my data base could not be created properly at
first instance . I just re-configured my server once again .

Thanks
Nitin
WillR wrote:

> cnystrom wrote:
>> After opening up a tech support call with Novell, granting control of my
>> workstation and leaving to them for 2 days we got this issue resolved.
>> The case is still open, as it appears (not confirmed yet) that there is
>> a defect/bug in the product. Once I have more information, I will post
>> it here.
>>
>>

>
> Not surprised. I banged my head against the wall for awhile on this one
> -- just never had a chance to log a support call or a get back to it.
>
>


0 Likes
skapanen2 Absent Member.
Absent Member.

Re: iFolder 3.6 OES2 on NSS Volumes

cnystrom wrote:
>
> After opening up a tech support call with Novell, granting control of my
> workstation and leaving to them for 2 days we got this issue resolved.
> The case is still open, as it appears (not confirmed yet) that there is
> a defect/bug in the product. Once I have more information, I will post
> it here.


Any news on this?

-sk

HAMK University - OES, NW, GW, NCS, eDir, Zen, IDM, NSL - www.hamk.fi
0 Likes
cnystrom Absent Member.
Absent Member.

Re: iFolder 3.6 OES2 on NSS Volumes

In the beginning we thought the problem was as simple as not having proper rights set to the WWWRUN user. However, when attempting to set the rights they did not take. There were issues with the GID and UID of LUM Enabled users. You can see the following correspondance between Novell and myself:


"Novell Engineer"

We changed the /etc/nam.conf to set the persistent cache to no rather than to yes. This is a temporary work around. To find the source of the problem we will need you to generate a core file.

You will need to set persistent cache to yes again so that we can duplicate the problem.

You'll need to set "ulimit -c unlimited" before loading namcd.

I would put it in the /etc/init.d/namcd script before namcd is actually loaded. Then stop namcd then start it up again with the ulimit setting in the namcd script


"ME"
I changed persistent cache to YES

Verified that ulimit -c unlimited was (it was there) in the NAMCD script.

Ran rcnamcd stop and then rcnamcd start

Attempted to login to the iFolder Admin page and it worked fine.

Not sure what is going on now, as I am now not able to replicate the problem......

Thanks
Calvin

"Novell Engineer"
Let's have you monitor it. We will keep this open for a week.

If the problem does not present itself again, it could have been caused by an object such as the www group not being associated to the sky unix workstation object or some attribute missing on an object that was populated with the changes to rights, and modifying group membership and associations to the unix workstation objects. Did you try several different users logging into iFolder?

It could have also been an issue with the initial creation of the cache file. We may have eliminated the issue by turning off persistent cache and then re-enabling it.

Thanks
Novell Engineer
0 Likes
RogerIThomas Absent Member.
Absent Member.

Re: iFolder 3.6 OES2 on NSS Volumes

I know this is a late answer but having just had the same issue I can provide some more info, for anyone else trying to do this install.

While the iFolder install allows the /var/simias/data path to be changed during the install it looks as if parts of the iFolder application also has this path hard coded. The apache logs of a system configured with a changed path show that the config file is still being read from /var/simias/data as part of the web based login.


Roger



> Here is the scenario:
>
> I've installed a new OES2 Linux server into our existing NetWare 6.5
> TREE. I followed all the steps in the Installation Guide pertaining to
> the creation of NSS Volumes. After the server installation was
> complete, I installed iFolder and began configuring it. I pointed it
> to the /media/nss/DATA/ifolder storage location and finalized the
> configuration. I also added the wwwrun rights per the doucmentation to
> the root of the NSS Volume (rights -f /media/nss/DATA -r rwfcem trustee
> wwwrun.rrr.all.tree). Everything seems to finish fine and there are no
> errors. When I try to login to the iFolder Adminstration I repeatedly
> get "Your session has been closed. Please log in.". I've tried
> restarting Apache and Tomcat and rebooting the server with the same
> result. So, I then reconfigured iFolder and tested it with the Default
> Storage Location (/var/simias/data) and I am able to login without any
> issues.


> Is there something that I am missing ?
>
> Please Help!
>
>
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: iFolder 3.6 OES2 on NSS Volumes

reinstall ifolder and you can change this path to anything that you want. if it is an nss volume wwwrun has to be a trustee to be able to read the config files that it places in the installation location.


>>> RogerIThomas<RogerIThomas@no-mx.forums.novell.com> 11/28/2008 9:56 AM >>>


I know this is a late answer but having just had the same issue I can
provide some more info, for anyone else trying to do this install.

While the iFolder install allows the /var/simias/data path to be
changed during the install it looks as if parts of the iFolder
application also has this path hard coded. The apache logs of a system
configured with a changed path show that the config file is still being
read from /var/simias/data as part of the web based login.


Roger



> Here is the scenario:
>
> I've installed a new OES2 Linux server into our existing NetWare 6.5
> TREE. I followed all the steps in the Installation Guide pertaining

to
> the creation of NSS Volumes. After the server installation was
> complete, I installed iFolder and began configuring it. I pointed it
> to the /media/nss/DATA/ifolder storage location and finalized the
> configuration. I also added the wwwrun rights per the doucmentation

to
> the root of the NSS Volume (rights -f /media/nss/DATA -r rwfcem

trustee
> wwwrun.rrr.all.tree). Everything seems to finish fine and there are

no
> errors. When I try to login to the iFolder Adminstration I

repeatedly
> get "Your session has been closed. Please log in.". I've tried
> restarting Apache and Tomcat and rebooting the server with the same
> result. So, I then reconfigured iFolder and tested it with the

Default
> Storage Location (/var/simias/data) and I am able to login without

any
> issues.



> Is there something that I am missing ?
>
> Please Help!
>
>



--
RogerIThomas
------------------------------------------------------------------------
RogerIThomas's Profile: http://forums.novell.com/member.php?userid=17612
View this thread: http://forums.novell.com/showthread.php?t=310850
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.