ZDM 7 on OES2 sp3

Has anyone gotten ZDM 7 to work on OES2, sp3? I tried installing on 2 machines and got 2 different "non-fatal" errors which must have been fatal because I can't start the services. I only want workstation importing, thats it. Errors have to do with jclient/dclient, and some other things. I can post the real text from the install log if anyone has an idea. novell-zmd-awsi status says unknown file, and same for ZFDstart and ZFDstop in /opt/novell/zenworks/bin/whatever...
Thanks.

Originally Posted by jzamiska
Has anyone gotten ZDM 7 to work on OES2, sp3? I tried installing on 2 machines and got 2 different "non-fatal" errors which must have been fatal because I can't start the services. I only want workstation importing, thats it. Errors have to do with jclient/dclient, and some other things. I can post the real text from the install log if anyone has an idea. novell-zmd-awsi status says unknown file, and same for ZFDstart and ZFDstop in /opt/novell/zenworks/bin/whatever...
Thanks.
Along with Shaun's suggestion as it's related... also curious which ZDM install media you used (i.e. 7 SP1 IR4b)?
Cheers,
Willem

Similar Messages

Mac os 10.6.8 cannot login to OES2 sp3

i'm having issues logging into a clean install of OES2 SP3 Linux SLES10 sp4 server here's my log file:
Feb 20 03:23:31 Server-1 afptcpd[4407]: Created session: 10 <0x82afc38>, Socket: 60, Total sessions: 2
Feb 20 03:23:31 Server-1 afptcpd[4407]: Closing session: 10 <0x82afc38>, Socket: 60, Pending requests: 0
Feb 20 03:23:31 Server-1 afptcpd[4407]: Created session: 11 <0x82afc38>, Socket: 60, Total sessions: 2
Feb 20 03:23:31 Server-1 afptcpd[4407]: Closing session: 11 <0x82afc38>, Socket: 60, Pending requests: 0
Feb 20 03:23:41 Server-1 afptcpd[4407]: Created session: 12 <0x82afc38>, Socket: 60, Total sessions: 2
Feb 20 03:23:41 Server-1 afptcpd[4407]: [debug] LDAP user name: cn=horchemg,ou=springfield,o=missouri
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - INFO:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - WEBBACKUP:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - HORCHEMG:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - INFO:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - WEBBACKUP:\
Feb 20 03:23:41 Server-1 afptcpd[4407]: [error] Failed to get volume key for - HORCHEMG:\
Feb 20 03:23:42 Server-1 afptcpd[4407]: Closing session: 12 <0x82afc38>, Socket: 60, Pending requests: 0

On 21/02/2012 23:16, ataubman wrote:
> Also, has OES been patched up? You need at least the November 2011
> patches to get AFP to work with 10.6.8 , IIRC.
I think you're getting your Mac OS X versions mixed up as Snow Leopard
(10.6.x) was supported from the beginning with AFP in OES2 SP2 and
later. See
http://www.novell.com/products/opene...owleopard.html
It's OS X Lion (10.7.x) that requires the November 2011 (and earlier)
patches for AFP in OES2 SP3 but it is supported from beginning with OES11.
HTH.
Simon
Novell/SUSE/NetIQ Knowledge Partner
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.

Migrate NSS volume data from OES2-SP1 to OES2-SP3 server fails

Hello forums
I have a senario where we want to use miggui to migrate all files/folder
and trustees, to e new server using miggui.
When we try to migrate from the existing "VOL" from the old OES2-SP1
server, we get an error on the miggui log running on the new OES2-SP3
server like this:
ERROR - FILESYSTEM:migfiles:Error: nbackup: (libtsafs.so 6.50.0 269) No
data sets can be found or the resource is not available.
In the miggui the Volumes can be dragged and dropped fine.
I do not by not know the old OES2-SP1's patch level, nor the OES2-SP3's
at this time.
Any ideas of what causes this error?
- Michael

Have you looked at this?
Troubleshooting data migration issues with miggui
I'd check and maybe see if the sms/tsa code is working properly on the OES2 SP1 server.

OES2 SP3 DNS/DHCP Console

Just a quick note that currently, the latest DNS/DHCP Console isn't
available for download on Novell's site. You have to get it off of your
OES2 SP3 server instead.
http://servername/welcome/client-software.html
Then you can follow TID 7006450 to configure it so you can view leases.
-Mike

On 25/02/2011 21:35, TitanXV wrote:
> It will only be available if the novell-dnsdhcp-javaconsole rpm is
> installed, and you can also grab it from the directory at
> /srv/www/novell/clients/dnsdhcp
If you do not have the novell-dnsdhcp-javaconsole RPM installed but do
have access to the OES2 SP3 media (and don't want to install DNS/DHCP on
a server just to get the latest JavaConsole) then on a Linux box you can
extract the latest code via:
rpm2cpio /path/to/novell-dnsdhcp-javaconsole-2.0.1-0.33.<arch>.rpm |
cpio -idmv
(where <arch> is i586 or x86_64 depending on 32- or 64-bit - note same
files included in both)
You can then take the relevant DNSDHCP_SA.zip file and use it to install
the JavaConsole on your admin workstation(s).
HTH.
Simon
Novell Knowledge Partner (NKP)
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.

OES2 SP3: Master sends poison pill upon creation of new volumes

I'm experiencing problems when creating a clustered pool and volume on
OES2 SP3. After assigning a new FC LUN which is available on all nodes
I'm using iManager to create a new pool and volume on the master node as
described in the documentation. However, at some point in the procedure
the master starts killing other nodes. Inspection with nssmu shows that
the new pool is just available on some nodes. After a reboot everything
is working nicely.
Should I send the cluster to maintenance mode prior to adding a new
volume? How can I force OES2 to scan for new pools other than rebooting
the system? Is there a known problem or a TID for this behavior?
Gnther

Am 05.09.2012 09:38, schrieb Hans van den Heuvel:
> On Tue, 04 Sep 2012 18:00:53 +0000, Andy Konecny wrote:
>
> Hi Andy
>
>> From this TID, it does look like the fix isn't generally available yet,
>> especially given that the TID was last edited today.
>
> I have modified the wording in the TID, as the 'naming scheme' part
> seemed to be confusing here.
>
> The should have read as in this particular tree, specific services are
> installed and named in a specific way for easy identification purposes,
> and these newly created cluster resources just did not comply to that.
> They were just not named properly, nothing else.
Sorry, but right now I'm completely confused. What are you talking about?
From cluster administration manual:
"10.1.1 Naming Conventions for Cluster Resources
Cluster resource names can be up to 63 characters. Novell
Cluster Services supports only
alphanumeric characters and the underscore character in
cluster resource names:
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwx yz0123456789_
Special characters, such as the following, are not supported
in cluster resource names:
!@#$%&()
Because the NSS pool name and Linux volume names are
automatically used in the cluster resource
name, do not use special characters !@#$%&() in names of NSS
pools or Linux POSIX volumes that
you plan to cluster enable."
I did not use special characters in names of cluster resources, pools or
volumes. So will my problem be still related to this TID?
I will gave to go and check with CRM debugging.
Günther

Windows 8.1 and OES2 SP3

I've noticed that Windows 8.1 iprint is currently support for iPrint Appliance and OES 11 server only. Will Novell release update for iprint server code for OES2 SP3 to support Windows 8.1? I do not want to upgrade to OES11 at this point.
Thanks,

poweruser wrote:
>
> I've noticed that Windows 8.1 iprint is currently support for iPrint
> Appliance and OES 11 server only. Will Novell release update for
> iprint server code for OES2 SP3 to support Windows 8.1? I do not want
> to upgrade to OES11 at this point.
To add to Mysterious' post, OES 2 went out of general support 31 July
2013. As a result there are no further enhancements coming to OES 2.
If you don't want to upgrade to OES 11 you could always implement the
iPrint appliance and migrate printing over to it while leaving the rest
of your services on OES 2 until you'r eable to upgrade.
Your world is on the move. http://www.novell.com/mobility/
We know what your world looks like. http://www.novell.com/yourworld/

Netware 6.5 SP8 to OES2 SP3 Migration Error with migfiles

Hi,
at first. We would like to abuse the migfiles tool to mirror data from Netware to OES2 SP3 with trustees !! Do you know a better tool than migfiles, please let me know. Its very important for me to use a CLI Command tool like migfiles, because it should run automatically.
We want to mirror data from a Netware 6.5 SP8 NSS Volume to a OES2 SP3 NSS Volume with trustess. The first migration with following line works without any error:
migfiles -s IPAddress -V Daten -x /media/nss/D4/Test3/ -i
From this point we need the -sync parameter to keep the data current.
I use this:
migfiles -s IPAddress -V Daten -x /media/nss/D4/Test3/ -i --sync "22-07-2011 16:26"
But then i became this errors:
Error: nbackup: Failed to restore: DATEN:VOLDATA.TDF
Error: nbackup: Received error: 0xfffdffdc ((libtsafs.so 6.50.0 291) An invalid path was used.) from NWSMTSWriteDataSet
Error: nbackup: Failed to restore: DATEN:tsa5up24/NWTAPE/
Error: nbackup: Received error: 0xfffdffdc ((libtsafs.so 6.50.0 291) An invalid path was used.) from NWSMTSWriteDataSet
Error: nbackup: Failed to restore: DATEN:tsa5up24/NWTAPE/NWTAPE.CDM
Fatal: Failed to restore data. Could not find destination path. If the destination path is a cluster resource, then check whether the resource is moved.
Fatal: nbackup: Received error: 0xfffdffe5 ((libtsafs.so 6.50.0 282) The data set handle is invalid.) from NWSMTSOpenDataSetForRestore
When the Sync job is finished, no file which was changed on the Source was migrated to the destination.
For your information. With the Novell Migration Tools (GUI) i have the same error. But with the Windows version "Novell Server Consolidation and Migration Toolkit" it works without any errors. But its a GUI tool without the possibility to run it automatically.
Any ideas
Thanks Andreas

Hi,
thank you for your reply. This is the log:
D, [01-08-2011 14:33:07#4872] DEBUG -- migfiles: migfiles command started at 01-08-11 14:33:07
D, [01-08-2011 14:33:07#4872] DEBUG -- migfiles: migfiles command executed as: /opt/novell/migration/sbin/migfiles -s xxx.xxx.xxx.103 -V Daten -x /media/nss/D4/Test3/ -i --sync 22-07-2011 16:26 --debug
D, [01-08-2011 14:33:07#4872] DEBUG -- migfiles: Calling function getCredentialDetails
D, [01-08-2011 14:33:21#4872] DEBUG -- migfiles: Successfully taken credential Details of source and destination server from user
D, [01-08-2011 14:33:21#4872] DEBUG -- migfiles: nbackup command executed as LC_ALL=en_US.UTF-8 /opt/novell/sms/bin/nbackup -U "admin.havas" -R xxx.xxx.xxx.103 --list-tsa-version
D, [01-08-2011 14:33:21#4872] DEBUG -- migfiles: Major version of source tsafs is 3
D, [01-08-2011 14:33:21#4872] DEBUG -- migfiles: Minor version of source tsafs is 1
D, [01-08-2011 14:33:21#4872] DEBUG -- migfiles: ncpshell command executed as /opt/novell/ncpserv/sbin/ncpshell --ip=xxx.xxx.xxx.103 --u="admin.havas" --vinfo --parm1="Daten"
I, [01-08-2011 14:33:22#4872] INFO -- migfiles: Given destination path is NSS
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Source path is Daten:
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Destination path is /media/nss/D4/Test3/
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Successfully returned from function verifyAndFixSrcPath
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Destination volume type: NSS
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Calling function get_nss_vol_and_mnt_point_from_path
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Calling function is_compression_enabled
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: Started on: "1-8-2011 14:33:22"
D, [01-08-2011 14:33:22#4872] DEBUG -- migfiles: smstool cmd = LC_ALL=en_US.UTF-8 /opt/novell/sms/bin/smstool --srcuser ".admin.havas" --destuser "root" -R xxx.xxx.xxx.103 --sync-time "22-07-2011 16:26" --output-file /tmp/smstoolOutFile.4872 --finddiff "Daten: /media/nss/D4/Test3/" 2>&1
I, [01-08-2011 14:33:23#4872] INFO -- migfiles: Generating list of files and folders to be synced
D, [01-08-2011 14:33:23#4872] DEBUG -- migfiles: Executing nbackup command from syncfiles: LC_ALL=en_US.UTF-8 /opt/novell/sms/bin/nbackup -cF --disable-caching -U ".admin.havas" --expand-compressed-data -R xxx.xxx.xxx.103 -T /tmp/smstoolOutFile.4872 | LC_ALL=en_US.UTF-8 /opt/novell/sms/bin/nbackup -xvF -U "root" -r "Daten: /media/nss/D4/Test3/"
D, [01-08-2011 14:33:23#4872] DEBUG -- migfiles: nbackup cmd = LC_ALL=en_US.UTF-8 /opt/novell/sms/bin/nbackup -cF --disable-caching -U ".admin.havas" --expand-compressed-data -R xxx.xxx.xxx.103 -T /tmp/smstoolOutFile.4872 | LC_ALL=en_US.UTF-8 /opt/novell/sms/bin/nbackup -xvF -U "root" -r "Daten: /media/nss/D4/Test3/"
D, [01-08-2011 14:33:23#4872] DEBUG -- migfiles: Calling function doCmd
D, [01-08-2011 14:33:25#4872] DEBUG -- migfiles: Checkpoined at
D, [01-08-2011 14:33:25#4872] DEBUG -- migfiles: Checkpoined pair 0
E, [01-08-2011 14:33:25#4872] ERROR -- migfiles: nbackup: Failed to restore: DATEN:VOLDATA.TDF
E, [01-08-2011 14:33:25#4872] ERROR -- migfiles: nbackup: Received error: 0xfffdffdc ((libtsafs.so 6.50.0 291) An invalid path was used.) from NWSMTSWriteDataSet
E, [01-08-2011 14:33:25#4872] ERROR -- migfiles: nbackup: Failed to restore: DATEN:tsa5up24/NWTAPE/
E, [01-08-2011 14:33:25#4872] ERROR -- migfiles: nbackup: Received error: 0xfffdffdc ((libtsafs.so 6.50.0 291) An invalid path was used.) from NWSMTSWriteDataSet
E, [01-08-2011 14:33:25#4872] ERROR -- migfiles: nbackup: Failed to restore: DATEN:tsa5up24/NWTAPE/NWTAPE.CDM
F, [01-08-2011 14:33:25#4872] FATAL -- migfiles: Failed to restore data. Could not find destination path. If the destination path is a cluster resource, then check whether the resource is moved.
F, [01-08-2011 14:33:25#4872] FATAL -- migfiles: nbackup: Received error: 0xfffdffe5 ((libtsafs.so 6.50.0 282) The data set handle is invalid.) from NWSMTSOpenDataSetForRestore
Thank you
Andreas

IFolder keeps prompting upgrade after OES2 SP3

Hi everyone,
After applying OES2 SP3 our iFolder server keeps prompting upgrade on
Windows XP clients. It suggests upgrading to 3.8.0.4 but when you let it
run, it shows windows installer options install and uninstall, there is
a space where the upgrade button should be. Neither option works.
I've also downloaded from the web server page the ifolder client, but
doesn't seem to be that version number.
Is there any way to disable the annoying prompt?
Thanks,
Miguel.

Originally Posted by mcando
Is there any way to disable the annoying prompt?
Thanks,
Miguel.
Section 6.12 of the iFolder 3.8.4 Admin Guide lists a way to disable the upgrade prompt.
Edit the unix-version.config, mac-version.config, and/or version.config (aka windows-version.config) files located in either /opt/novell/ifolder3/lib/simias/web/update or /opt/novell/ifolder3/lib64/simias/web/update.
Replace the <version> </version> section of the .config files with the level of client your users already have. Then they should not be prompted to upgrade.
Andrew

Java and OES2 SP3

Good day,
Had a question concerning the following:
1.) There was a TID in regard to JAVA no longer being included in the Channel updates any longer, does anyone have that TID number, or know if this is still relevant?
2.) What is the latest version of JAVA on OES2 SP3?
Thank you,
DS

Hey Ds,
Originally Posted by dschaldenovell
1.) There was a TID in regard to JAVA no longer being included in the Channel updates any longer, does anyone have that TID number, or know if this is still relevant?
Java IBM 1.6 and 1.7 are still in the update channels AFAIK (for SLES 11), where did you remember reading that?
You do realize OES2 SP3 is out of general support (since July last year/2013)?
Originally Posted by dschaldenovell
2.) What is the latest version of JAVA on OES2 SP3?
Can't check, all my OES2 SP3 servers have been upgraded to OES11. A quick look on an SMT server shows this one : http://download.novell.com/Download?...d=KfMV2KXyWVs~ (java-1_6_0-ibm-1.6.0_sr14.0-0.11.1.x86_64.rpm / java-1_6_0-ibm 8657)
I'm curious why you are inquiring for this?
Cheers,
Willem

SLES10 SP4/OES2 SP3 32 bit Clean Install - Basic Questions

Hi everyone.
I am now an expert in installing the above software and ending up with a server which does not work as we require. Must be something I am doing wrong. Hope someone can spot it.
Have installed and supported Netware servers for 25 years without major problems. Decided now to move to SLES because Novell say we should and we need Groupwise 12 to replace GroupWise 8.
The operational environment we are targeting is an 80 user edirectory/NDS based single tree, single context containing two Netware 6.5 SP8 HP Proliant servers running uncomplicated file and print services , NSS volumes, Groupwise 8, DHCP, ifolder, Quickfinder and the like, spread across the two servers. It all works a treat. Client PCs are are all XP Pro with Novell client software.
The idea would be to replace one of the two Netware servers first with a SLES/OES server and then the second Netware server with a second SLES/OES server and move GroupWise functionality to one of the SLES/OES servers. Ideally users would continue to log on using their eDirectory accounts without noticing anything was going on in the background.
The test environment we have set up is a 5 user NDS/eDirectory single tree, single context already containing a single Netware 6.5 SP8 Proliant server running file and print, NSS volumes etc and Groupwise 8. Into this tree we are trying to install a 32 bit server with a empty 36 GB SCSI disc running SLES 10 SP4 with OES2 DP3 as an add in, with NSS data volumes.
Because it only takes a few hours to do we have repeatedly run the SLES 10/OES2 install (probably about 9 times!) with minor variations to see whether we can end up with a properly configured SLES/OES server but there is always one problem or another.
The major problem we have is how to configure NSS data volumes on the SLES server and how to allow users to be validated against their eDirectory entries and knowing whether the test server is 'good to go'.
The process we followed for each test install, after checking edirectory was clean and removing any entries placed in the tree by earlier attempts to install the SLES server in the same tree were:
1. Boot the SLES 10 SP4 32 DVD (downloaded ISO and burnt DVD) and selected Installation.
2. Followed the prompts on time zone and language etc and selected i386 OES CD (also downloaded ISO and burnt) as the Software Add-In.
3. Loaded SLES DVD and OES CD as and when requested
4. At the Partitioning stage we selected the EVMS proposal, and at the Software selection stage selected the base software, file server Role, Documentation, DHCP, eDirectory, iFolder, iPrint, Quickfinder, NSS and LDAP.
5. Miscellaneous errors would appear or not appear during the eDirectory stage (eg LUM error, or iFolder error) but the eDirectory stage would still seem to complete OK and get ticked.
6. The system would then reboot and appear to come up OK.
HOWEVER, we are not convinced we have created a fully working reliable server.
and
SPECIFICALLY we are unable to create NSS volumes and we cannot logon users via their eDirectory accounts.
NSSMU shows a single device sda (33.92 Gb) and three partitions sda1 (70Mb), sda2 (31.91GB), and sda3 (1.94GB). sda2 seems to contain all the 'spare' space on the disk (type Linux LVM) but says there is no spare space to create our NSS partitions.
iManager cannot see any devices to configure NSS data volumes on the SLES server but it connects OK
NSSCON status seems to show NSS to be running
EVMSGUI shows /dev/evms/lvm2/system/ro at 10 Gb, /dev/evms/lvm2/system/sw at 2GB and /dev/evms/sda1 at 70 Mb
So my questions are:
Does the above look right?
Why cannot we get at the spare disk space to set up NSS volumes? Did the EVMS proposal grab it all and if so how do we get it back?
Did not selecting the EVMS partitioning proposal do everything needed to run NSS?
[There seems to be some suggestion in the several hundred pages of SLES, OES and NSS Guides, Installation manuals, Configuration manuals etc that we have studied over several days, that we now have to edit a fstab file to make it work properly (Really? in this day and age where clicking on Setup.Exe will configure a fully working Windows server) Is that so? Is there anything else we need to do?]
How do we get the users to access their NDS accounts to log into SLES and Netware?
How do we know the server is OK for operaational use and 'works' ?
HELP!!!
ADB

alandbond wrote:
> I
> have already trawled the self help Forums believing that before SLES
> 11 came along everyone must have been setting up NSS volumes on SLES
> 10/OES2 as a matter of course as they moved from Netware and so me
> trying to do it now should not be akin to rocket science.
You are partially correct. Admins who used NSS on NetWare likely did
install NSS on OES Linux but I suspect they used a separate drive for
NSS either by installing an additional drive, by carving out a chunk of
space on their RAID array and assigning it to a separate LUN, or by
running OES in a VM where storage space on a single disk/array can
appear as separate drives.
> If Novell say in that guide as they do
> (just as do you and ab and Simon in responses to my post) that the
> IDEAL way to include NSS is to have a separate disk for Suse and NSS
> volumes, BUT as long as you use EVMS to manage the volumes it IS
> SUPPORTED, then I consider it should be possible without grief to do
> this and not considered as me putting round pegs in square holes.
Semantics!
IDEAL = Recommended; EVMS != IDEAL; EVMS != Recommended;
IMO, Novell recognised that they had to provide a way for customers to
install NSS on a system that only had a single disk and provided this
procedure as a workaround. By the way, they also support 2-node
clusters but they aren't recommended either. I have also seen cases
where a supported configuration was deemed no longer to be supported as
NTS became aware of additional complications.
My point (and Simon's and ab/Aaron's) is this: Just because it is
supported doesn't mean you should do it. If we can agree on this point,
I'll try to help you to get it working. The last thing I want to do is
give others the impression that by helping you find a solution we think
this is a good idea!!!
> This latest release of software even goes as far as including an EVMS
> Partitioning proposal which can be selected (as I did) within the
> clean install process.
>
> This is what it says:
Okay! I'm only looking at the information you provided. Let's analyse
it!
>
> A.2.1 Understanding the EVMSBased Partitioning Scheme
> Using EVMS to manage the system device allows you to later add NSS
> pools and volumes
Yes, NSS requires the volume manager to be EVMS and not LVM!
> on any *unpartitioned* free space on it.
But you have not left *any* unpartitioned free space!
> You must modify the partitioning scheme to use EVMS during the
> install. It is not possible to change the volume manager for the
> system device after the install.
True.
> Beginning in OES 2 SP3, the Partitioner in the YaST Install offers the
> Create EVMS Based Proposal option to automatically create an EVMS
> solution for the system device.
> For unpartitioned devices over 20 GB in size,
This is what you have...
> this option creates a boot partition
> and a container for the swap and / (root) volumes
> in up to the first 20 GB,
> and leaves the remainder of the space on the device
> as unpartitioned free space.
But it didn't (or you didn't)!
> Table A-1 shows the default proposed setup
> for a machine with 768 MB RAM.
> The default swap size is 1 GB or larger,
> depending on the size of the RAM on your machine.
> The remainder of the device is left as unpartitioned free space.
Let's look at the default proposal. This is *not* what you have.
> Table A-1 Default EVMS Proposal for Devices over 20 GB in Size
>
> Device Size Type Mount Point
> /dev/sda1 70.5 MB Ext2 /boot
> /dev/sda2 14.9 GB Linux LVM
> /dev/evms/lvm2/system 14.9 GB EVMS lvm2/system
> /dev/evms/lvm2/system/root 10.0 GB EVMS /
> /dev/evms/lvm2/system/swap 1.1 GB EVMS swap
A single (SATA/SAS/SCSI) drive will be known as sda (/dev/sda).
/dev/sda1 is the first partition. In the example and in your
configuration this is the /boot partition. In both cases it is 70.5 MB.
/dev/sda2 is the second partition. The partition uses LVM so logical
volumes of various sizes can be created within the partition. The total
size of all logical volumes cannot be larger than the size of the
partition.
In the above example:
/root is 10.0 GB and swap is 1.1 GB. This leaves: 14.9 - (10.0 + 1.1) =
3.8 GB of additional space within /sda2 which can be used to create
additional logical volumes. Furthermore sda1 + sda2 use only ~ 15 GB.
Only 15 GB of the disk has been allocated. The remainder of the disk is
*unallocated* and *unpartitioned*. Presumably, it was left that way so
that the space could be used for NSS.
In your case: sda2 is 31.91 GB
This does not follow the Default EVMS Proposal for Devices over 20 GB
in Size. Either YaST did not allocate space according to the default
proposal or you changed it. Either way, sda2 (+sda3) consume *all* of
the available disk space. It is no wonder that there is no space
available for NSS!
> What do you reckon???
I reckon that something went wrong along the way. If you did not
specifically change the default allocation yourself, then consider this
one example of kinds the things that can happen when one tries to
exploit seldom used, but supported, features!
It looks like it is time for yet another installation. This time, make
sure you leave enough unpartitioned space on the drive for NSS and let
me know how you make out.
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

Howto remove & (re)install Clusternode OES2 SP3

We have a 2 node sles10.3+oes2sp3 cluster.
We have some problems with the second node. To make a long story short, we have 2 options now:
1. reinstall the second node or
2. add a third node and remove the second one afterwards.
We have a shared storage via iSCSI - both nodes are iscsi initiators. We have 1 NSS Volume which is cluster enabled.
Our Questions:
1. Is there anything with regard to the sdb partition we have to take care about or can I just follow the steps in the ncs docu.
2. What happens to all the objects in eDir (oes objects, node2 object, ncp object etc.)? How can we remove the ALL objects related to the second node?
3. Which option would you recommend and how would u do it? Anything dangerous we have to take care about?
thx,
hugo

Well, having done this before myself (I messed up the 7th server installation because I wasn't paying attention).
So here's what I did:
1) I ran the ndsconfig -rm to remove the "messed up" cluster server from the tree.
2) cleaned up the eDir objects for THAT SERVER (meaning the PHYSICAL node objects--NOT any of the cluster stuff). So I basically searched (via consoleone) for: *servername* and deleted those objects.
3) I then reinstalled SLES 10/OES2 (without the NCS pattern), and gave it the same name/IP and put it into the proper eDir container this time.
4) Then I installed the NCS pattern (see my guides for how i did my install).
For the SDB partition, really the only thing you need to worry about is that (prior to installing NCS pattern):
a) Does the server "see" the SBD partition. In my case I use MPIO, so I made sure that a:
multipath -ll
command showed the SBD partition
I think there's the sbdutil -f or something command that you can run
2) For your "cleanup" I just used consoleone, "find" (make sure to start at the O=whatever in your tree and check the box for "search subcontainers) and then searched for *servername*. You do NOT want to delete any of the cluster objects (although I think they would have different names anyway). If my memory is correct.
I would not bother with option #2 (adding a third node and then deleting the 2nd one).
I hope this helps.
--Kevin

Transfer Trustees from Netware to OES2 SP3

Hi everbody,
with the last metamig, I saw, that saved data from trustee.nlm should be restored.
I saved on the original Netware Server with trustee save /R daten: daten:daten.txt.
But I was not able to restore to my OES 2 SP3, I got a lot of error, ie. invalid token.
The Volume Name is the same as on Netware. All data have the same path.
Can anybody tell me the correct syntax how to restore the trustees to oes?
Thanks for helping,
Regards from Austria,
Reinhold

Originally Posted by rsteini
Hi everbody,
with the last metamig, I saw, that saved data from trustee.nlm should be restored.
I saved on the original Netware Server with trustee save /R daten: daten:daten.txt.
But I was not able to restore to my OES 2 SP3, I got a lot of error, ie. invalid token.
The Volume Name is the same as on Netware. All data have the same path.
Can anybody tell me the correct syntax how to restore the trustees to oes?
Thanks for helping,
Regards from Austria,
Reinhold
I don't believe (I could be wrong) that you can take the trustee.nlm and save the output in a format that OES Linux will understand (the OES LInux uses a .xml format which I think is different)
You could manually read through the file (that NetWare generates) and figure out if you wanted to manually reassign them
Or you could use the miggui (migration utility) on OES Linux to migrate the data (and trustees) from NetWare.

OES2 SP3 AFP How to empty AFP log file

Hello All,
i find no information how i can empty the AFP log file in /var/log/afptcpd/afptcp.log. It has grown to 1,2 Gigabyte and is very uncomfortable to look for information in this big file.
Any ideas ?
Thank you
Andreas

If you get a lot of afp activity, your probably best off if you just set the log to rotate.
create a file under /etc/logrotate.d/ and name it whatever you want.
then just enter in something like this:
/var/log/afptcpd/afptcp.log {
compress
dateext
maxage 365
rotate 99
size=+4096k
notifempty
missingok
create 644 root root
postrotate
/etc/init.d/novell-afptcpd reload
endscript
Originally Posted by Skylon5000
Hello All,
i find no information how i can empty the AFP log file in /var/log/afptcpd/afptcp.log. It has grown to 1,2 Gigabyte and is very uncomfortable to look for information in this big file.
Any ideas ?
Thank you
Andreas

[SOLVED] Upgrade from SLES10 SP3 & OES2 SP2 to SP4/SP3 breaks NCS

Hi folks,
(This post was originally meant to be a rant and a request for help, but
while writing the final paragraph i found the solution. It's still a
rant, but i figured i'd post my solution here in case someone else runs
into the same issue.)
I've just spent several hours banging my head against a broken cluster
node. My system is a 32-bit SLES 10 VM running on VMware ESX 3.5.x.
I upgraded from SLES10 SP3 and OES2 SP2 to the next service packs for
each (using the move-to-oes-sp3 script in yast2 online_update).
Everything went well for the first few update/reboot sequences, then
after the final reboot on SLES10 SP4 & OES2 SP3, cluster services would
not load or join the cluster on restart.
I checked dmesg and found errors about "Loading module compiled for
kernel version 2.6.16.60-0.54.5-vmi" into a previous kernel version, so
i tried downgrading to that kernel version, only to find that it was
older than the one i had just upgraded from (it's the original SLES10
SP3 kernel). So i tried upgrading back to the same kernel which is
running on the other cluster node (2.6.16.60-0.77.1-vmi), but that did
not work any better.
<preaching>
I have to say that i'm not impressed that OES2 SP3 isn't even compiled
against the appropriate kernel, and because of SUSE's kernel RPM
overwrite policy there's no way i can select to boot from a previous
kernel to see if that fixes things. Note to SUSE and other distro
builders: if you're not doing kernel package upgrades like Red Hat or
Ubuntu (so that we can select to boot from the previous kernel from the
boot menu), you're doing it *WRONG*.
</preaching>
I then upgraded again to the latest recommended kernel for SLES10 SP4,
and still no joy. Dmesg shows this error before the rot starts:
allocation failed: out of vmalloc space - use vmalloc=<size> to increase
size.
When searching for this error i stumbled across
http://ubuntuforums.org/showthread.php?t=1613132
which pointed me to
http://www.mythtv.org/wiki/Common_Pr...lloc_too_small
Adding vmalloc=192M to /boot/grub/menu.lst and rebooting solved the
problem for me.
Regards,
Paul

Originally Posted by Paul Gear
On 13/10/11 07:36, magic31 wrote:
> ...
> Not sure if it's related to the issue you've hit, but along the lines
> of what Kevin already mentioned, there are issues that can arries when
> using the VMI kernel (that I've seen) if having multiple flavors of the
> kernel installed along with it (as in having both kernel-vmi as also
> kernel-smp packages installed) ...
> Curious, is that also the case with your setup?
The system in question has kernel-bigsmp and kernel-vmi installed. We
only ever boot from kernel-vmi.
> I've moved to only using the smp kernel on VMware (along with the
> clock=pit boot option to avoid time drift issues, or pmtr I think in
> your case when also running NCS services in the vm).
When we installed the system (on OES2 SP1, i believe) it was a while
ago, and kernel-vmi with clocksource=acpi_pm on the kernel command line
was the only solution we could find to get reliable time. If there are
updated best-practice documents, i'd be happy to hear about them.
However, this is a production cluster and my boss is (rightly) rather
reticent to make major changes.
Paul
the official Vmware paper on time is that IF you're using SLES 10.x 32-bit you will use VMI and NO kernel params (ie, get rid of the clockpit and clocksource=blah).
But if 64-bit then you're okay.
The easiest, IMO (especially with vmware) is to use the miggui (migration utility). That's how I'm converting all my 32-bit servers in vmware to 64-bit. Works quite well.
--Kevin

Migedir Error going from NW6.5SP8 to OES2 SP2 on SLES10 SP3

I've searched the forums and was not able to find this particular problem so hopefully someone more knowledgeable than I can help. I have an issue with the Transfer ID utility erroring out at the DIB copy portion of a NetWare 6.5 SP8 migration to 64-bit OES2 SP2. The eDirectory Precheck and Preparation portion of the Transfer ID complete successfully with green check marks. When the Transfer ID gets to the DIB copy part I get a series of error messages.
This is the error from the mignds.log file:
05-05-2011:09:56:20:Information: The DS version on the source server is 10554.
05-05-2011:09:56:20:Fatal: Setting up the NetWare eDirectory migration environment...
05-05-2011:09:56:20:Information: Package 'ncpfs' has been installed.
05-05-2011:09:56:20:Information: Mounting the SYS volume of 'xxx.xxx.xxx.xxx' at /var/opt/novell/.edir_migrate/mnt...
05-05-2011:09:56:20:Information: SYS mounted successfully.
05-05-2011:09:56:20:Information: 'novell-ncpserv' package is available.
05-05-2011:09:56:20:Information: Copied scp peer file (ncpmig.nlm) to source server successfully.
05-05-2011:09:56:20:Fatal: SERVER: load nlm ncpmig.nlm failed rc=158.
In the Transfer ID Migration Log this is what appears:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:*****************Command output start**********************************
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:eDirectory migration utility for Linux
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Version: 2.0 for OES Linux 2.0
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Copyright (c) 2007, Novell Inc. All rights reserved.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Creating the eDirectory migration file locations...
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Get the source server administrator credentials -
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir: Enter adminDN(e.g: cn=admin.o=administrators): Enter password:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Source server, xxx.xxx.xxx.xxx is reachable.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:The source server, xxx.xxx.xxx.xxx is running on NetWare platform.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:OS Version: v5.70.8
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Product Version: v6.50.8
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:NCP Engine Version: 1
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:NCP Engine Platform: 0:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:The NetWare source server is running on OES Platform
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:eDirectory packages are installed.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Performing pre-migration checks on the source server, 'xxx.xxx.xxx.xxx'...
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:ndscheck performed successfully.
2011-05-05 09:56:20,761 INFO - ServerIDSwap:migedir:Checking time synchronization between source and target servers.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Source and Target servers are in time synchronization
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Performing eDirectory migration...
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:This may take time depending on the size of the data on the server that is being migrated.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:The DS version on the source server is 10554.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Setting up the NetWare eDirectory migration environment...
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Package 'ncpfs' has been installed.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Mounting the SYS volume of 'xxx.xxx.xxx.xxx' at /var/opt/novell/.edir_migrate/mnt...
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:SYS mounted successfully.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:'novell-ncpserv' package is available.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:Copied scp peer file (ncpmig.nlm) to source server successfully.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:ERROR: Could not load secure NCP NLM, ncpmig.nlm on the source server - SERVER: load nlm ncpmig.nlm failed rc=158..
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:SERVER: load nlm ncpmig.nlm failed rc=158.
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:stty: standard input: Invalid argument
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:stty: standard input: Invalid argument
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:stty: standard input: Invalid argument
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:
2011-05-05 09:56:20,762 INFO - ServerIDSwap:migedir:*****************Command output end**********************************
It looks like the Mig utility can't run ncpmig.nlm on the source server for whatever reason. The previous steps completed successfully so I don't think it's an issue of login rights. The OES2 SP2 server is fully patched with all critical and optional patches. I'd like to add that I've done a couple migrations in my test lab prior to this and they both went through smoothly. I'm also following the exact same steps I used when I performed the lab migrations.
I've also tried the same migration using OES2 SP1 (fully patched and not), OES2 SP2 (non-patched) and OES2 SP3 (patched and not) with the exact same error message. This leads me to believe it's something in the source server causing the issue but I can't, for the life of me, figure out what.
Source server is running NW6.5 SP8 and eDir 8.7.3.10. Target server is OES2 SP2 and eDir 8.8.5 HP6. Does anyone have insight into why the Transfer ID is failing at the DIB copy? Thanks in advance.

Sorry for the late reply. Been extremely busy with our migrations and other issues. To answer the last question, our default administrator login to the tree is not called admin. We prefer not to use default names as they decrease security. I used my own login credentials, which also has full rights to the tree, to proceed with the migration. Determined, as a precaution, that the person performing the migration should add him or herself as a trustee to the source/destination servers AND the container the server objects live in. It's probably a redundant step but should decrease the likelihood of encountering the original issue.

ZDM 7 on OES2 sp3

Similar Messages

Maybe you are looking for