Section C.3, “NSS File Version Utility,” on page 119
C.1 Archive Server
“Archive Server Fails to Version Files” on page 115
“Job fails to start” on page 116
“Undefined Job Name” on page 116
“Versions are not available” on page 116
“Archive Server fails to start” on page 117
“Archive Server fails to start. Ensure that root is part of the novlxtier group” on page 117
“I am unable to view versions using vi,vim,gedit,kwrite?” on page 118
“Unable to get versions of the symbolic file” on page 118
“On the stopping the PostgreSQL instance of Archive service, the database status still displays running.” on page 118
“The database port change is not reflected on modifying arkConfig.xml file.” on page 118
“Browse icon not functional for restoring files with NetStorage in a Firefox browser” on page 119
Archive Server Fails to Version Files
Using iManager, job fails to run with an error, “Error authenticating connection, check if eDirectory user name and password are correct.” This error is logged in the debug log file.
Possible Cause: When the value of novlxtier gid is changed, xregd is unable to read the registry files and folders, due to change in ownership and results in failure of the versioning job.
Action: To resolve the issue, do the following:
1 To change the xtier directory ownership, enter
chown -R novlxregd:novlxtier /var/opt/novell/xtier/xregd 2 To restart XTierʹs registry daemon, enter
rcnovell-xregd restart
3 Using iManager, run the Archive jobs. The jobs run successfully and versions of the files are displayed.
Job fails to start
Using iManager, job fails to run with an error, “Error authenticating connection, check if eDirectory user name and password are correct.”
Possible Cause: The eDirectory user is not LUM enabled and part of novlxtier LUM group on the OES 2 server running Archive and Version Services.
Action: Ensure that the eDirectory user is LUM enabled on the server running Archive and Version Services.
1 For more information on LUM enabling the eDirectory user, see the OES 11 SP2: Novell Linux User Management Administration Guide.
2 Add the eDirectory user to the “novelxtier” LUM group. The group is created on installing the OES 2 server.
3 To refresh the LUM cache, run namconfig cache_refresh.
4 Start the Archive and Version Service.
rcnovell-ark start
On restarting the service job runs as per the schedule.
Possible Cause: If a job is manually configured in the arkConfig.xml file using IP address or hostname of the source server.
Action: Ensure that the IP address or hostname mentioned in the source element of the
arkConfig.xml is same as the IP address or hostname of the server, where the data to be versioned is located. On updating the IP address or hostname in the arkConfig.xml file, restart the Archive server.
Possible Cause: Casa credentials are not set correct
Action: To reset the password in the CASA store run the following command:
/opt/novell/arkmanager/bin/arkReconfig.sh --edir-admin=<adminusername>
You will be prompted for the password.
Restart the arkserver using rcnovell‐ark restart
Undefined Job Name
In iManager, Archive Versioning>Archive Jobs, name of the job is listed as Undefined Job Name under the Jobs section.
Possible Cause: In the Job settings page, source server name is without context.
Action: Delete the job named Undefined Job Name.Create a new job and ensure that the source server name is with context. For example, Archive‐server.org
Versions are not available
Possible cause: The user does not have access to Unix workstation or is not LUM‐enabled.
Action: The eDirectory user needs to be LUM‐enabled and given access to the Unix workstation by the administrator. For more information, see the Steps to LUM‐enable the user.
Possible cause: The Archive server and Client desktop workstation system clocks are not synchronized.
Action: Synchronize the Archive and Client desktop system time.
Archive Server fails to start
View the server log files available at /var/opt/novell/log/arkmanager/.
Possible cause: NSS is not running
Action: Use rcnovell-nss status to check if NSS is running. If it is not running, start NSS with the rcnovell-nss start command.
Possible cause: Adminfs is not running
Action: Check if adminfs is running with rcadminfs status. If it is not running, start adminfs with the rcadminfs start
Possible cause: Postgresql driver not found.
Action: Check if the postgresql-8.1-404.jdbc3.jar file is available in /usr/share/pgsql directory. If the file does not exist, you need to install the postgresql-jdbc.8.1.rpm file.
Possible cause: One of the cause could be the version of the JDBC driver. By default, the archive server functions with postgresql-8.1-404.jdbc2ee.jar file installed with Novell Open Enterprise Server x.x Product CD.
Action: By default, the archive server functions with postgresql-8.1-404.jdbc2ee.jar file installed with Novell Open Enterprise Server 2 Product CD.If you have installed any other version of .jar file on your system, you need to edit the classpath available in the novell-ark file.
For example, if you have installed the JDBC 3 driver and version of respective jar file is postgresql-8.2-504.jdbc3.jar. Edit the classpath in the novell-ark file as follows:
CP_PATH5: /usr/share/pgsql/postgresql-8.2-504.jdbc3.jar Possible cause: PostgreSQL database is not running.
Action: Delete the postmaster.pid file from the PostgreSQL database data path, then restart Archive server.
Archive Server fails to start. Ensure that root is part of the novlxtier group
Cause: You are running the Archive server as a root user.
Action: Reconfigure Archive and Version Services.
1 Reconfigure Archive and Version Service to run as a non‐root user.
2 Add the non‐root user to the “novelxtier” LUM group. The group is created on installing the OES 2 SP2 or later server.
3 Start Archive and Version Service rcnovell-ark start
I am unable to view versions using vi,vim,gedit,kwrite?
Possible cause: The text editor for example, vi, creates a swap file with a .swp extension on editing a file. The creation of the swap files avoids displaying versions of original files. As per the functionality of text editor, it creates temporary files during the process of modification and saves it with original name after successful modification. The Archive server is designed to capture changes to the file and create versions. So all the changes are tracked and versions are stored even for the temporary files.
Action: Create an Include or Exclude filter to avoid versioning of temporary files like .swp or .temp.
You can set filter using iManager, Archive Versioning> Archive Server Properties > Source Server information> Filter. Set a filter and specify the extension of files that you want to exclude in the Extension field. For example, .tmp
Unable to get versions of the symbolic file
Possible cause: The original file is not stored on NSS file system configured for Archive and Version Services.
Explanation: For example, if original file is stored on ext3, reiserfs or any other file system and symbolic link is created on NSS Primary volume. Any modification to the original file will not create versions on the Primary volume. Versions are available of files stored on NSS file system which is configured for Archive and Version Service.
On the stopping the PostgreSQL instance of Archive service, the database status still displays running.
Explanation: The PostgreSQL instance of Archive service is stopped. When you run rcpostgresql status PostgreSQL status may display as running. This is because the rcpostgresql script checks for any running instance of PostgreSQL database.
The database port change is not reflected on modifying arkConfig.xml file.
Possible cause: If you have configured Archive & Version Service using YaST utility, the scripts are automated and linked to each other. To reflect changes to port number or username through manual edits, you have to modify both the pg_restart.sh and arkConfig.xml file.
Action: For example, to change the port number to 2456, do the following:
1. Edit the arkConfig.xml located at /etc/opt/novell/arkmanager/conf/
Replace the number between the portNumber tags
<portNumber>2456</portNumber>
2. Edit pg_restart.sh file located at /opt/novell/arkmanager/bin
Replace the port number after –p option in the following line:
su dbuser4 c "postmaster D /var/opt/novell/arkmanager/data h 127.0.0.1 p 2456 -i"
This changes the database to run on port 2456.
Browse icon not functional for restoring files with NetStorage in a Firefox browser
Explanation: When you are restoring file versions with NetStorage in a Firefox browser, the Browse icon that allows you to browse for the location of the file to be restored is not functional.
Action: Enter the path manually in the Restore to field.
C.2 Migration Issues
“Migration fails with the error message ʺPostgreSQL authentication failed.ʺ” on page 119
“Migrating to the OES 11 SP2 server, Archive server fails to start.” on page 119
“Migrating Archive server to OES 11 SP2 fails randomly” on page 119
“Migration fails with the error message, “ Unable to open ArkConfig.xml file”.” on page 119
Migration fails with the error message "PostgreSQL authentication failed."
Possible cause: The username, password or database port number is invalid.
Action: Ensure that the PostgreSQL credentials are valid.
Migrating to the OES 11 SP2 server, Archive server fails to start.
Possible cause: Linux operating system is case sensitive. Archive server fails to start if the archive path is not in appropriate case.
Action: Ensure the volume name is in uppercase. For example, ARKVOL:\archive_directory
Migrating Archive server to OES 11 SP2 fails randomly
Possible cause: The migration tool fails randomly to migrate Archive and Version Services to OES 11 SP2 server.
Action: To migrate Archive and Version Services, run the sys:\system\arkmig.ncf file on your NetWare server, then run the migration tool on the OES 11 SP2 server. Archive and Version service migrates successfully.
Migration fails with the error message, “ Unable to open ArkConfig.xml file”.
Possible cause 1: ArkConfig.xml file name is case sensitive. Migration fails if the file name is not appropriate.
Possible cause 2: The spelling of the ArkConfig.xml file is incorrect.
Action: The file name is case‐sensitive. Ensure you have specified the file name as ArkConfig.xml.
C.3 NSS File Version Utility
“Restoring versions, using NSS File Version Utility on Windows workstation, displays an error, unable to locate MSVCR71.dll file.” on page 120
“How to debug issues with NSS File Version Utility.” on page 120
“On installing NSS File Version Utility, Restore Archived Versions option is not available using GNOME desktop.” on page 120
Restoring versions, using NSS File Version Utility on Windows workstation, displays an error, unable to locate MSVCR71.dll file.
Possible cause: MSVCR71.dll is not available in c:\windows\system32 folder.
Action: On installing Novell Client, the MSVCR71.dll file is installed on your system. Copy this file to c:\windows\system32 location. You will now be able to restore versions.
How to debug issues with NSS File Version Utility.
Possible cause: By default, the log file includes only fatal errors.
Action: To log debug or all messages, you have to configure the
NovellVersioningClient.exe.config file and edit the level value parameters to DEBUG or ALL.
<level value="DEBUG"> or <level value="ALL">
For more information on editing log files, refer the Apache Logging Services website (http://
logging.apache.org/log4net/)
On Windows 2000 and Windows XP, the default location for the log.txt file is Program Files\Application folder. For example, C:\Program Files\Novell\Versioning\log.txt.
On SLED 10 and SLED 10 SP1, the default location for the log.txt file is $home/.versioning folder.
In Windows Vista 32‐bit platform the log file is located at
c:\users\<username>\AppData\Local\VirtualStore\Program Files\Novell\Versioning.
In Windows Vista 64‐bit platform, to create log file, you need to configure the c:\Program Files\Novell\Versioning \NovellVersioningClient.exe.config file.
On installing NSS File Version Utility, Restore Archived Versions option is not available using GNOME desktop.
Action: When using GNOME desktop, you must login again to the Nautilus file manager to access the Restore Archived Versions option.
On un-installing NSS File Version Utility, Restore Archived Versions option is still displayed in the menu using GNOME desktop.
Action: When un‐installing NSS File Version Utility from GNOME desktop, you must login again to the Nautilus file manager to clear the Restore Archived Versions option from the menu list.
The warning window in KDE terminates, if you click the button Keep Running.
Action: On KDE, if you try close the NSS File Version Utility window when in a processing state, a warning is displayed.
If you click either the Terminate or Keep Running button, the process is terminated. This behavior occurs because KDE kills the process, assuming it is not responding.
D
DDocumentation Updates
This section contains information about documentation content changes made to the OES 11 SP2:
Novell Archive and Version Services Linux Administration Guide since the initial release of Novell Open Enterprise Server 2. If you are an existing user, review the change entries to readily identify modified content. If you are a new user, simply read the guide in its current state.
Refer to the publication date, which appears on the front cover and the Legal Notices page, to determine the release date of this guide.
In this section, content changes appear in reverse chronological order, according to the publication date. Within a dated entry, changes are grouped and sequenced, according to where they appear in the document itself. Each change entry provides a link to the related topic and a brief description of the change.
This document was updated on the following dates:
Section D.1, “January 2014,” on page 123