Go here for info on the current status of SCO Linux products
Caldera Volution Manager 1.1 Known Issues
----------------------------------------------------
GENERAL ISSUES
---For the most up-to-date information on Volution Manager 1.1, refer
to the Caldera Support Knowledge Base at:
http://support.sco.com
---For information on Caldera Worldwide Support Services, see the
Preface of the Volution Manager 1.1 Installation Guide.
---If you are running the Volution Manager Server (VM Server) in a
language other than English, complete the following after you install
Volution
Manager:
In a terminal window,
1. Stop the Tomcat daemon as follows:
/etc/rc.d/init.d/tomcat stop
2. Open and edit the Tomcat initialization script,
/etc/rc.d/init.d/tomcat, using a text editor.
a. After the line that reads:
. /etc/rc.d/init.d/functions
b. Add the following command:
unset LANG
3. Save the file, and restart Tomcat as follows:
/etc/rc.d/init.d/tomcat start
---Objects and their associated settings and status that are
created using a localized character set can only be accessed in that
language.
---The Volution Manager Computer Creation Daemon (volutionccd) can
handle up to 100 simultaneous requests for new computer objects. If
you are adding more than 100 new computers into the VM system at once,
spread the load out by only turning on up to 100 Volution Manager
Clients (VM Client) at a time.
If more than 100 computers are added or rebooted at a time, several
scenarios might occur. SSL connection errors might be reported in the
log file of the VM Clients or DENS errors might be reported.
Regardless of the error reporting, the VM Clients will initialize
correctly without intervention.
---If you need to restart volutionccd or the DENS daemon (densd) you
must also restart Tomcat. To restart Tomcat enter the following:
/etc/rc.d/init.d/tomcat restart
---You can set the Volution Manager logging level by using a
tag in the /etc/opt/volution/volutiond.conf file.
By default, volutiond logs messages beginning at "info"
level. You can change this default by inserting a XML tag into the
volutiond.conf file, as follows:
debug
With this setting, volutiond will log all messages. You will
still need to check your syslog configuration to make sure
that these messages will be logged by syslog.
Possible values for sysloglevel are:
debug info notice warning
err crit alert emerg
The entry should be placed in the volutiond.conf file as follows:
debug
.
.
.
--- If you have more than one gateway policy, only the first policy
takes effect.
---Status is not reported correctly when you schedule an action to
run using the "Length of time to run" option.
--- The date of the certificate generated during Volution Manager
Server installation must precede the system date on the
VM Client machine. If it does not, the VM Client will not be able to
authenticate until its system date becomes later than the one on the
certificate. This is only a problem when the date on the VM Client and
VM Server machines are not synchronized properly.
---To uninstall the VM Server:
1. Stop all Volution Manager daemons by running the following
commands:
/etc/rc.d/init.d/volutiond stop
/etc/rc.d/init.d/volutionccd stop
/etc/rc.d/init.d/volutionsrd stop
/etc/rc.d/init.d/densd stop
/etc/rc.d/init.d/ldap stop
/etc/rc.d/init.d/tomcat stop
2. Remove the Volution Manager RPMS by running the following command:
rpm -e volution volution-server volution-mgmt
3. Delete any leftover files, by running the following commands:
rm -rf /opt/volution
rm -rf /etc/opt/volution
---To uninstall VM Clients running Linux, use the following command:
rpm -e volution
---To uninstall VM Clients running UnixWare and Open UNIX, use the
following command:
pkgrm Volution
---To uninstall VM Clients running SCO OpenServer use the Software
Manager.
---If you inadvertently link an object to an action more than once,
you don't need to remove the extra links. Simply click refresh in your
browser to remove the duplicates.
---The SNMP daemon, snmpd, adds a file named "no" in the root
directory.
---If after creating an organizational unit it doesn't appear in the
VM Management Console, click Refresh in your browser.
---The VM Management Console allows users in without a password but no
action can be performed.
---In status messages, apostrophes incorrectly display as &apos.
---If there is more than one version of a specific RPM, Volution
Manager can not remove it using a profile. Create an action to remove
it instead.
---If you run a hardware inventory on VM Clients with internal IDE ZIP
drives, they are reported as hard drives or CDROMs.
---To use the Volution Manager Wizards you must use the default
organizational unit names. The default organizational unit names are
actions, computers, policies, profiles, Software Repository, and
Users.
---For information on upgrading from Volution 1.0 to Volution Manager
1.1, contact support.
---Volution Manager does not report the completion status when you
schedule an action to occur by Event.
VM SERVER ISSUES
---Minimum Hardware Requirements
The following includes updated information on Volution
Manager minimum hardware requirements.
VM Server
o A Pentium(R) III 500 or equivalent.
o A minimum of 256 MB of RAM.
o If your VM Server is also your LDAP Server an additional
128 MB of RAM for a total of 384 is recommended.
For large scale networks it is not recommended that you
install the LDAP Server on the same computer as the VM Server.
o OpenLinux requires a minimum of 1.3 GB of disk space for a
full installation. An additional 50 to 120 MB of diskspace might be
required for Volution Manager, depending on the packages selected
during the OpenLinux installation.
These minimum hardware requirements may not be sufficient
for managing a large scale network. Scale these requirements in
accordance with the size of your network.
---Turning on information or debug logging results in large
quantities of data on all VM Clients. If you need to do
this, apply it to only a few VM Clients as it could bring down
your mail server if that is what you are using as your gateway.
---When you create a Health Policy without setting notice or warning
levels, Volution Manager assumes they are set to 0.
---If your VM Management Console view changes unexpectedly it might be
because there are multiple VM Consoles open on different computers. If
the view is not the one you selected, refresh the screen by clicking
on the object (or the one above it) in the left pane of the VM
Management Console.
---If you schedule an action to occur and use an
invalid schedule (for example, using the daily schedule without
specifying a day) the action won't run and no status for the schedule
is reported in the VM Management Console. However, the error, "invalid
schedule given for " is reported in the debug
information.
VM CLIENT ISSUES
---While the Volution Online link appears in the software repository
for VM Clients running OpenServer, UnixWare, and Open UNIX,
currently, there is no Volution Online content for these VM Clients.
---Do not use multi-byte or extended characters (such as umlaut or
circumflex) in computer object names.
---If a VM Client is configured to use a RAID
drive, hardware inventories run on that client will not report
accurate results.
---When you delete a computer object it will still appear in the VM
Management Console. To remove the object from the VM Management
Console view, first stop the VM Client daemon (volutiond) as follows:
/etc/rc.d/init.d/volutiond stop
Then select Delete this Object from the Page
Views pane of the VM Management Console and confirm the action by
clicking OK.
If you no longer want to manage this computer, set the daemon to not
start on boot (you can use the KDE Control Center to do this) or
remove the VM Client package.
------The Mac OSX(R) of version Internet Explorer(R) doesn't work with
Volution Manager because it doesn't allow self-signed certificates.
However, it will work if your Apache certificate is generated
by Verisign(R), or some other accredited signing authority.
---Hardware inventories on VM Clients running TurboLinux do not
report accurate results.
---VM Client running TurboLinux 7.0 require a change to the ucd-snmp
RPM. Before you install the VM Client, remove the ucd-snmp that comes
with TurboLinux. It will be replaced by a different package during
the VM Client installation.
Remove the TurboLinux version of ucd-snmp with the following
commands:
rpm -e --nodeps `rpm -qa | grep ucd-snmp ` (mind the
back-ticks)
rm -f /etc/snmp/*
Then run the client/install.sh script from the Volution Manager CD.
--- To install the VM Client on Caldera OpenLinux eServer version 2.3
you must install all client RPMs with the --nodeps flag.
--- SCO OpenServer package objects are created without
dependencies, therefore VM cannot install them in the correct order
without information from the system administrator. An example of
where this comes into play is with the 506a update. When you put the
506a update into the software repository, package objects are created
for 4 products: - The USB supplement
- A sendmail update
- The body of the 506a update
- The 506a software manager supplement
The software manager supplement must be installed first,
followed by the 506a supplement and then the USB and sendmail
updates. In order for installation to succeed these products cannot
be installed at the same time. This is because the order in the
installation queue might not be correct. To ensure that this works
properly, distribute one product at a time verifying successful
installation before continuing.
--- Package Removal on SCO OpenServer will always fail if
you attempt to remove a package which is required for another
installed package. (Example: Attempting to remove the 506a software
manager supplement while the body of the 506a update is still
installed).
---Volution Manager can not remove the SCO OpenServer German
language supplement for 5.0.6.
---The diagnostics link in the VM Management Console does not work
on SCO OpenServer, UnixWare, or Open Unix when volutiond is run in
debug mode.
---The SNMP daemon, /etc/snmpd, must be started on SCO OpenServer
5.0.4 and 5.0.5 before diagnostics will work.
--- A few SCO OpenServer packages are in pkgadd format. This
package format is not supported for installation through Volution
Manager on SCO OpenServer. An example of a package of this type is
the oss630a security update for 5.06.
To work around this, do the following:
-Use the mkvol utility from the SkunkWare CD to package the file
appropriately
-Copy this file into the appropriate SRD directory (see the
Volution Manager Administration Guide). Install that file with
Volution Manager; then, run the following script:
pkgadd -q -d /opt/K/SCO/oss630a/1.0/oss630a all
This script should be added to the installation profile in
the post-install script field.
(Note: You cannot use the software distribution wizard if
you want to specify a post-install script.)
--- Some SCO OpenServer packages are in a file system format
which is not installable via Volution Manager, for example, the
software on the 5.06 optional services CD.
--- If you run the VM Client in debug mode on SCO OpenServer
(/opt/volution/bin/volutiond -d) you will see a lot of iconv
errors. This makes it very difficult to view the actual debug output.
To effectively view debug information from the VM Client, redirect
all output from standard error to /dev/null as follows:
/opt/volution/bin/volutiond -d 2>/dev/null
---Reboot VM Clients running SCO OpenServer after applying patches
that relink the kernel. Use the post install script option in
Profile to automate this.
---Unless you manually start the SNMP daemon (snmpd) the SCO
OpenServer 5, 504 and 505 VM Clients will not have a diagnostic link
available on the VM Management Console.
---Open UNIX Maintenance Pack creates 4 packages that can't be
installed individually. (libc, libC, libm and ou800m2).
Install ou8pk2 to capture all of the packages.
---When setting a constraint on a Profile for LKP on Open UNIX do
not select version 3.1.
---If the size of the software package you are installing on Open UNIX
or UnixWare exceeds the size of your /tmp directory, software
installation fails. To avoid problems, either unmount /tmp or
increase the size of the /tmp directory. In some cases the software
packages are not removed from /tmp. If this occurs, manually remove
them. If this is not done and /tmp fills up, further package
installations will fail.
---To get a complete hardware inventory of VM Clients running
UnixWare 7.1.1 you must install ptf7617c. If this supplement is
applied hardware inventories provide more information.
---When you run a hardware inventory on Unixware and Open UNIX, hard
drives that are not in use by either UnixWare or Open UNIX are not
detected.
---If you are running a hardware inventory on a VM Client
running SUSE 7.3 and the RAM and swapspace numbers are missing, check
for a dangling symlink(a symlink pointing to a nonexistant file) in
the /dev directory and correct it. Rerun the hardware inventory to
view these numbers.
LDAP ISSUES
---The following characters are illegal in LDAP names:
comma (,), equal sign (=), plus sign (+), backslash (\), single quote
('), pound sign (#), and semi colon (;)
OpenLDAP
---Currently, the Volution Manager directory administrator's password
(referred to in OpenLDAP as the root password) appears in the
slapd.conf file in clear text. To increase the security of your
system, we recommend that you encrypt it. To encrypt the
administrator's password, complete the following:
1. As root run the command:
slappasswd
2. Copy the output and use it to replace the password text in the
slapd.conf file.
See man slappasswd for details.
eDirectory
---eDirectory was designed to run with glibc v2.2.1 and the Linux
kernel v2.4.2. If you use OpenLinux 3.1.1 based on glibc 2.2.4 and the
2.4.13 kernel as the separate system to run eDirectory, you might see
slower performance or erratic behavior.
---VM Clients running UnixWare and Open UNIX require a change in
the certificate name in order to connect to eDirectory.
Disregard the message in ConsoleOne.
To setup NDS eDirectory as your LDAP data store you must
alter step 11 under "Setting Up the eDirectory Server Certificate" in
Appendix A of the Volution Manager Installation Guide. This step
should read:
11. You must edit the subject name as follows:
.CN=FQDN
Where FQDN is the Fully Qualified Domain Name of the LDAP server.
DO NOT follow the NDS suggestion.
---As the final step in setting up the eDirectory Server Certificate,
click the LDAP server object in ConsoleOne. On the Properties of LDAP
Server dialog click Refresh NLDAP Server now.
iPlanet
---When moving objects to the root of your LDAP directory tree, if you
named the administration domain the same as your root, then you will
be prompted with 2 check boxes that look similar. Do not choose the
one that says "o=NetscapeRoot" as the Location. This is referring to
the administration domain and not to the top of your tree. Instead
choose the one named LOCALLIBo=.
---While it is possible to run iPlanet on your VM Server, we
recommend using separate computers.
---The iPlanet Server runs on OpenLinux 3.1.1 while the iPlanet
Console runs on OpenLinux 2.4.
In order to run the server and console separately requires that you
configure the iPlanet security to allow you to do so.
To do this:
1. Install iPlanet.
2. From your iPlanet Server, run the following commands:
cd /usr/netscape/server4
./bin/admin/admconfig -serv : -u
: -setAdd
""
Note: Do not use the greater than and less than signs (<>) around your
entries.
Where:
- is your iPlanet server's name. Do not use
localhost.
- is the port number for the administration server. Press
Enter for the default.
- is the directory manager username. (usually cn=directory
manager)
- is the directory manager password.
- is the list of addresses of the computers from
which you want to be able to run the console. You can create a list by
using a comma. Do not use spaces. For example,
"10.10.10.*,10.11.11.*" now 2 class C's will be able to run the
console. You can use wild cards in your address list. For example,
10.10.10.* which would make the whole class C of
10.10.10. able to run
the console.
An example entry follows:
./bin/admin/admconfig -serv my311serv.localdomain.com:5555 -u
cn=directory manager:caldera -setAdd "10.10.10.*,10.10.11.*"
Note: If the domain name of the computer running the
console is different from the servers,(for example, if the servers
name is my311serv.sco.com and I want to run the console from
my311server.calderasystems.com) run the following command:
./bin/admin/admconfig -serv : -u
:
-setH ""
Same as above, except that domain list is a list of possible domain.
You can use wild cards and link multiples together with a comma.
An example entry would be:
./bin/admin/admconfig -serv my311serv.localdomain.com:5555 -u
cn=directory manager:caldera -setH
"*.sco.com,*.calderasystems.com"
Update these values and restart the administration server in order for
them to take effect, as follows:
./restart-admin
You can now access the administration console from another computer.
To test this, use Netscape to go to the administration server web page
by entering the URL of the server machine and the port number. An
example would be:
http://my311serv.sco.com:5555/
The administration web page appears.
If an error appears, repeat the steps and make sure to restart
the admin server.
---The instructions in Appendix A of the Volution Manager
Installation Guide, Post Installation Requirements for LDAP for
iPlanet require modifications. Use the following instructions in
place of the ones available in the guide.
When you install the VM Server using iPlanet, the Post Install
Diagnostics screen (the final screen) shows that the SRD daemon
(volutionsrd) failed to start. This is because the certificates
haven't been properly set up between Volution Manager and iPlanet.
Use the instructions in Appendix A to set up the certificates and
restart volutionsrd as follows:
/etc/rc.d/init.d/volutionsrd restart
This ensures that the volutionsrd is running properly.
Using iPlanet
Use the following instructions to complete the iPlanet
configuration for SSL communication.
1. Before installing Volution Manager, install iPlanet 4.13
on OpenLinux 3.1.1 and create a symbolic link between
/usr/lib/libtermcap.so.2 to /lib/libncurseses.so.5.2 by entering the
following:
ln -s /lib/libncurses.so.4.2/usr/lib/libtermcap.so.2
2. During the VM Server installation, select iPlanet as the
LDAP directory.
3. Copy the Certificate Authority certificate from
/etc/opt/volution/cacerts to the system you are installing iPlanet
on. The filename is volution-authority.cacert.
4. Start the iPlanet console. See "Using iPlanet" on page
13 of the Installation Guide.
5. In the iPlanet Console, expand the container,
yourserver.yourcompany.com and then expand the container, Server
Group.
6. Click on Directory Server and then click the Open button.
7. Select the Configuration tab and then Encryption tab.
8. Click the Enable SSL checkbox.
9. Select the RSA checkbox under Cipher Family.
Setting Up the Trusted Certificate Authority
1. Select the Certificate Setup Wizard.
2. Read the instructions and click Next.
3. Under Option 1 select internal (software).
4. Under Option 2 select Yes and click Next.
5. Read the instructions and click Next.
6. Enter a password for the Netscape Trust Database and
click Next.
7. Read the Status message and click Next.
8. Read the Install Server Certificate message and click
Next.
9. Select Trusted Certificate Authority and click Next.
10. Select "The certificate is located in this file:" and
type in the full path to the Volution Manager CA certificate you
copied from /etc/option/volution/cacerts to the system you are
installing iPlanet on. The filename is volution-authority.
cacert and click Next.
11. Verify that the information from the certificate is
correct and select Add to add this certificate.
12. Select Done to finish.
Generating a Certificate Request
1. Select the Certificate Setup Wizard.
2. Read the instructions and click Next.
3. Under Option 1 select internal (software).
4. Under Option 2 select No and click Next.
5. Read Generate Certificate Request and click Next.
6. Click New Certificate.
7. Click To CA's email address and enter your email address.
Click Next.
8. Enter you information. For Server Name enter the hostname
of your iPlanet server and click Next.
9. Enter your Trust Database password and click Next.
10. Read the Generate Certificate Request message and click
Next.
11. Read Install the Server Certificate message and click
Next.
Signing the Certificate Request
There are no changes to this section as it appears in the
Installation Guide.
Importing the Signed Certificate
From the iPlanet Console:
Start with step 6:
1. Select "To install a certificate for this server" and enter
the password (this should already be filled in) for the Netscape
Trust Database and click Next.
The rest of the instructions are correct.