Installing GroupWise on SUSE Linux Enterprise Server
Novell Cool Solutions: Feature
By John Hurst
Digg This -
Posted: 31 Mar 2005
- Initial notes on installing SUSE Linux Enterprise Server
- Load eDirectory
- Install GroupWise
- GroupWise Commands
For full documentation on the GroupWise product for Linux go to http://www.novell.com/documentation/gw65/index.html
Initial notes on installing SUSE Linux Enterprise server.
- On install, pick Reiser file system
- Deselect Mail and News services. You will find this on the main groupings of software titles, underneath FILE & PRINT SERVER. If you accidentally do install these, after your Linux server boots, you can re-run YAST and get to SYSTEM ' RunLevel Editor. Runlevel Properties: scroll down to POSTFIX and make sure it is not running and will not load at any runlevel.
- If you decide to setup the IP specifications for your network card at this time, be sure to check a box that says IP routing.
- After the server is up and running load gettext. Gettext is required if you are going to run eDirectory. NOTE *** if you are installing SUSE Linux Enterprise, you will be allowed to select software titles upon install. You can select the gettext module at that time.
- Get into YAST and select SOFTWARE.
- Select Install or Remove Software.
- Select Search, select gettext.
- Double check that postfix is not checked.
- check mark it in the resulting window and check ACCEPT
- Also, make sure once the server is up and running you use YAST to do an Online Update of SUSE Linux Enterprise. You can use A16/skpwpq for a login name and password.
Install eDirectory onto the new Linux box.
- Put in the eDirectory for Linux CD
- Enter a Console prompt
- enter su - (switch user to root)
- type cd /media
- type l (to list media drives and find the name of the cdrom drive, using "l" instead of ls does a "ls -alF" which shows all the properties of your files)
- type mount cdrom (or mount <name of your CD device>)
- type cd cdrom (or cd <name of cdrom drive>)
- type cd Linux/setup
- First thing we need to do before we install eDirectory is to install NICI. Do this by typing rpm -i nici-2.6.4-0.05.i386.rpm (the -i says install, the rest of this line is the name of an install file you would see if you typed ls). This will load NICI onto your Linux server. Once this loads successfully you should see a message that says Initializing NICI ? done.
- type /bin/netstat -nr (this will tell you if the host is enabled for multicast routing)
- if this does not show you an entry for 126.96.36.199 0.0.0.0 then you will have to type the following:
- route add -net 188.8.131.52 netmask 240.0.0.0 dev -interface (example for -interface will probably be eth0.
NOTE: that we did not use a minus sign in front of eth0. ex: route add -net 184.108.40.206 netmask 240.0.0.0 dev etho )
- type ./nds-install
- you will be asked to view many pages of the license agreement. You can press 'q' to quit these screens then accept the license agreement.
- during eDirectory install you will be asked to select eDirectory server or eDirectory Administration Utilities. You can type in 1,2 which selects them both.
- now you will be asked for a Linux eDirectory license (an *.nfk file). If this is already on a floppy, type /media/floppy for the location of your *.nfk file.
- When eDirectory is finished installing you will have to add the following path: /usr/ldaptools/bin to path and /usr/ldaptools/man:/usr/man to manpath.
- vi profile
- Add these lines to the bottom of the file
(Type o opens a line below the cursor)
Press shift-zz (saves and exits)
Type source /etc/profile to make these changes take affect in your current environment.
Example: ndsconfig add -t Adventure16 -n o=main -a cn=admin.o=main
(this will add this Linux server to an existing eDirectory). You will be prompted for the admin password. Once all information is supplied, eDirectory will get busy joining this Linux server to the existing tree.
NOTE: if you are creating a NEW eDirectory tree you will want to use the following command:
Ndsconfig new -t <yourtreename> -n <context> -a cn=admin.o=<context>
Example: ndsconfig new -t Adventure16 -n o=main -a cn=admin.o=main
You will be prompted two times to supply an admin password.
More information on installing eDirectory for Linux can be found at http://www.novell.com/documentation/edir873/index.html.
- now we need to set our NTP source for this Linux server
- vi rc.config
- add the following line to this file START_XNTPD=yes. Shift-ZZ to save the file.
- Edit the ntp.conf file. Find the line that says SERVER and make sure the IP address of your REFERENCE, SINGLE or PRIMARY is on this line. (example: SERVER 192.168.1.101). NOTE: If this is the only server in your tree, you can omit the rest of these steps, unless you plan on using an Internet address as your time source.
- Issue a one time command to synchronize time now. ntpdate <ipaddress of your server in the previous step>. NOTE: you really don't need to do this since the next commands will continually check your time server for time.
- Issue the start command for NTP: rcxntpd start
- You can test your setup by issuing: ntpq -c peers. This should return the IP address of your time server w/ other information.
- ./c1-install. (Remember you may need to get back to your CD volume to complete this step. Also you may need to traverse to the /Linux/ConsoleOne directory.).
- You will be asked for the Language and which snap-ins you want to install. You will probably want to install all the snap-ins. Also you will be asked whether or not you want to install the Java runtime environment. If you have SUSE Linux versions over 9.x answer NO to this. Otherwise, answer YES to this. ConsoleOne on Linux installs to /usr/ConsoleOne/bin. To run ConsoleOne, execute /usr/ConsoleOne/bin/ConsoleOne
NOTE: Do not install this patch until you have installed ConsoleOne.
- You may want to make sure you patch your eDirectory before you go any further. To do so, go to www.novell.com/downloads and download any patches to your version of eDirectory. For this document, we were on version 8.7.3. For this step we download the edir8732_ls.tgz file into our documents folder.
- From the /home/<user>/documents folder (or any folder you downloaded the patch to, issue this command: gzip -dc <patch file> | tar xvf - for example: gzip -dc edir8732_ls.tgz | tar xvf -
- Change to the resulting directory the zip file created. Example: cd edir8732_ls
- Stop eDirectory momentarily so that you can apply the patch. /etc/init.d/ndsd stop
- Run the patch. For example: ./install.sh
- Start eDirectory backup. /etc/init.d/ndsd start
NOTE: Full documentation on installation exists at: http://www.novell.com/connectionmagazine/2004/07/tech_talk_2.html
- NOTE: before you issue the next command you have to make sure you have a location called /medio/iso. If you do not then type mkdir /media/iso
- If you are downloading from www.novell.com/download 6.5 eval version, save the ISO image. For our session, we downloaded GWLinux651e.iso. This command should mount the download file if you downloaded it to /home/jhurst/Documents (or /home/<login name>/Documents) directory. Mount -t iso9660 -o loop ./GWLinux651e.iso /media/iso. NOTE: if you get an error that says No such file or Directory when you try to mount the ISO image, check the file name. I've seen where downloading a file put a " (double quote sign) at the end of the word ISO. I had to rename the file to take off the ".
- Issue the following command xhost +localhost. If this fails with a message "unable to open display", try opening another terminal window and issuing this command BEFORE you issue the su - command for changing to root user.
- From the root of the folder area you unpacked GroupWise, (possibly /media/iso) type ./install. If you are running SUSE Linux Enterprise Server 9 and if you get an error message similar to this one:
Error: Traceback (most recent call last): File "install.py", line 2, in ? import frontend, sys File "frontend.py", line 4, in ? File "utils.py", line 3, in ? ImportError: /usr/lib/librpmdb-4.1.so: undefined symbol: poptSaveLong
You will have to modify the gwinst/install.sh file:Change the line that reads
Save the changes
If you are unable to edit this file, you will have to copy the entire contents of the GroupWise installation to another area where you do have rights to edit the install.sh file.
Also note, if you do not see an Xwindows type of screen that you would normally see on any installation of GroupWise (ie. You do not see a GUI screen giving you an option to Create or Update a GroupWise system), get out of the terminal window on your Linux box, start a new one and this time instead of issuing an XHOST + Localhost command followed by a SU -, issue as single command SUX -. This will allow you to login as root and let you use an Xwindows environment. (If you use SUX -, do not use XHOST + Localhost).
- Choose to Extend the Schema during the GroupWise install.
- Follow the rest of the on screen configuration options.
- Reboot the server.
Some GroupWise commands
- /etc/rc.d/grpwise start
Starts a GroupWise system manually
- /etc/init.d/grpwise stop
This stops all GroupWise services on your Linux server.
- /etc/rc.d/grpwise status
Checks the status of GroupWise
- /opt/novell/groupwise/agents/bin/gwmta - -show - -home <domain dir> &
This starts the GroupWise MTA on your Linux server. Note: there are two dashes before show and home. Also, there is an ampersand on the end of that line. The - - show tells the system to display an MTA screen on the Linux window. Example /opt/novell/groupwise/agents/bin/gwmta - -show - -home /grpwise/domain &
- /opt/novell/groupwise/agents/bin/gwpoa - - show - - home <po dir> &
This starts the GroupWise POA on the Linux server.
- To confirm if the GroupWise agents are loaded (or not)
Ps -eaf | grep gwmta
Ps -eaf | grep gwpoa
Ps -eaf | grep gwinter
If you have unloaded the mta and poa for example, the only gwmta and gwpoa process IDs you should see listed are the ones for the grep commands.
- To stop GroupWise processes that were started manually
First find out what the PIDs are for the MTA and POA. To do this, issue the ps commands listed above (ps -eaf | grep gwmta). Then use the ?
- Kill PID
Stops a GroupWise MTA or POA based on the PID given from the ps -eaf | grep <gwpoa or gwmta> commands.
- To stop and start apache and/or tomcat
- To stop and start GroupWise Webaccess
SMTP service - Error: Unable to listen on SMTP port. (Rc=2)
This error generally means you have something running on port 25. I've found situations where this will happen, however if you scan for open, listening ports, you won't find port 25. Make sure you don't have POSTFIX loaded. Make sure you don't have SENDMAIL running. If you do, type ps -ef | grep sendmail (or postfix) to get the PID number. Then type kill <pid number>. Finally, go to YAST and unload the software that you found was blocking port 25.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com