How to quickly fix iManager problems

  • 7007266
  • 29-Nov-2010
  • 27-Apr-2012

Environment

Novell Open Enterprise Server 2 (OES 2) Linux

Situation

iManager fails to start
iManager hangs, crashes, stalls
iManager broken, corrupt
iManager plugin update fails

Resolution

  • Copy the iManager files from any good, known working server at a similar patch level. 
    e.g.  From the console of the bad server:

    • rsync -avz --progress --verbose --human-readable root@<good_server>:/var/opt/novell/iManager/* /var/opt/novell/iManager/
  • Restart tomcat or reboot the server

    • rcnovell-tomcat5 restart
  • Reinstall any additional plugins as necessary

Additional Information

Good troubleshooting practice should always be followed in order to find and address the root cause of any problem. 

However, it is recognised that there are legitimate situations, where the cause of a failure is known (such as a power outage leading to file corruption) and when the system just needs to be up and running as quickly as possible.  In such cases, the above technique can be used with caution.  The root cause of the problem needs to be understood as soon as convenient in order to prevent it happening again.

If there is no working server readily available, it may be quicker to build one from scratch and use it as a source to copy the files from.  Alternatively, a file system backup could be used.

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