Tool
As we know, 90% of OES problems can be traced back to one of the services in the OES stack not running, thereby affecting the services lower down in the stack.
I created this script to present a Menu so a basic administrator can log into the server and run the menu, then follow simple menu prompts to check for apparent issues with OES services, networking and eDirectory objects/users
See the screenshot below, then download the script and try it yourself!
| Attachment | Size |
|---|---|
| oeshealthcheck.sh_.zip | 2.2 KB |
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
Thank you, Peter! Great
Submitted by al_b on 14 December 2011 - 7:15pm.
Thank you, Peter!
Great script!
- Be the first to comment! To leave a comment you need to Login or Register
unexpected token on line 256
Submitted by deancarpenter1966 on 15 December 2011 - 6:47am.
On my sles10sp3 oes 2.0.3, I get line 256: syntax error near unexpected token `;;' What do I do to fix it? I love to have this tool. Thank you for writing this.
- Be the first to comment! To leave a comment you need to Login or Register
I got the same problem,
Submitted by simonpalmer123 on 16 December 2011 - 4:14am.
I got the same problem, deleting that line appears to work.
- Be the first to comment! To leave a comment you need to Login or Register
Same probblem, I removed line
Submitted by jeep on 16 December 2011 - 5:37am.
Same probblem, I removed line 256 (;;) and now it works.
- Be the first to comment! To leave a comment you need to Login or Register
unexpected token on line 256
Submitted by bwisupport on 16 December 2011 - 12:29am.
Great tool, very usefull for my colleagues with less OES expirience. Thanks for...
I'm not an developer but the above error can be fixed by commenting out the line 256 or maybe deleting the ';;'. This worked for me.
Tom
- Be the first to comment! To leave a comment you need to Login or Register
Fixed line 256
Submitted by peter6960 on 16 December 2011 - 11:10am.
My apologies. I fixed and reuploaded the script. Thanks for spotting it
- Be the first to comment! To leave a comment you need to Login or Register
- Be the first to comment! To leave a comment you need to Login or Register



7