Error 500 when accessing or managing NetStorage

  • 7006381
  • 30-Jun-2010
  • 27-Apr-2012

Environment

Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 1
Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 2
Novell NetStorage

Situation

When a user accesses NetStorage running on a OES2 server, the browser will show a 500-error.
When trying to configure NetStorage via iManager, there will be a 500-error.

When checking the /var/log/messages, the following error will be displayed:
Apr 13 13:27:33 novlab02-de httpd2-worker: XSrvCChannel::connectSocket- Connection creation failed, error = 13
Apr 13 13:27:33 novlab02-de httpd2-worker: XSrvCChannel::init- Connection creation failed, error = 13
Apr 13 13:27:33 novlab02-de httpd2-worker: IPCCLNT -getCChannel- Channel Initialization failed for socket /var/opt/novell/xtier/xsrvd/srv-socket-4
Apr 13 13:27:33 novlab02-de httpd2-worker: IPCCLNT -SubmitReq- Channel unavailable
Apr 13 13:27:33 novlab02-de httpd2-worker: IPCCLNT -SubmitReq- Will attempt to retry RPC, count = 2

Resolution

During the installation something went wrong with the membership from user and groups.

When there are no problems the user involved have the following rights:
Users:
uid=30(wwwrun) gid=8(www) groups=8(www),81(novlxtier)
uid=81(novlxregd) gid=81(novlxtier) groups=81(novlxtier)

Groups:
novlxtier:x:81:novlxregd,novlxsrvd,wwwrun
www:x:8:wwwrun,novlxsrvd,admin

When it is going wrong the following rights are set for the user wwwrun:
uid=30(wwwrun) gid=8(www) groups=8(www)
The group novlxtier is missing.

The resolve this issue, add novlxtier to the membership of user wwwrun in NDS using iManager. After this is being synchronised, run a "namconfig cache_refresh" and also restart Apache2 (rcapache2 restart) on the OES2 server. This will solve the issue.

The problem is caused by the configuration of NSS. This has been solved with OES2 SP3 or OES2 SP2 including the January 2011 patch.

Note for OES2 SP2:
First installing and configuring NSS with OES2 SP2 shipping and then applying January 2011 patch, will not solve the problem.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.