Sep
5
2010
If you wonder why I haven’t post anything for the last few weeks…. this is because I’m on a holiday to the south of the USA. So check back in a few weeks!
Aug
13
2010
I’ve posted a couple of time but on Coolsolution from Novell there is a post about a script who can recreate all the SSL certificates on the right place for your OES1 and OES2 server.
As of Augustus 12 there is a new version out by jmeldrum.
Fixes and Enhancements:
- Version 1.1
- The script will now check if your are root
- OES2 x86_64 is now supported
- A relative path to the .pfx file can now be used.
- Version 2.0
- This script will now do pre and post checks to see if the certificates are good or bad
- Color was also added for easier reading
Jul
26
2010
After a upgrade to VMware vSphere 4.1 I couldn’t SSH to the Service Console. First I thought the password wasn’t correct, but after checking to login on the console directly I noticed that the password is correct. When I enabled rootlogin in the /etc/ssh/sshd_config -> permitrootlogin yes, I could login as root through SSH, so SSHD was working. So I must be a new security feature in vSphere 4.1. Then I changed the vSphere permission in the vSphere client to for my user to Administrator. After this I was able to SSH to the server. I’m haven’t had the time to check witch feature is responsible for this but I’m going to.
Jul
22
2010
During a lab of the N309o course (Deploying Novell Open Enterprise Server 2 for Linux) a student experienced a blue screen on this VMware Host workstation. This workstation was running Windows XP 64 bit with VMware Workstation build 203739.
The student was trying to install a package on a SLED 11 virtual machine through Yast. For this package Yast needed the SLED 11 DVD. The virtual CD-ROM player was configured as Auto, witch means that the physical CD-ROM player of the host is connected to the virtual CD-ROM player of the virtual machines.
If you Google on the error PFN_LIST_CORRUPT you will find that this error is mostly RAM corruption. In this case VMware Workstation passes wrong information to the memory therefore the blue screen.
Resolution: Configure the virtual CD-ROM player to use a ISO file.
I didn’t test this with VMware Workstation version 7.1. But this is on my list.
Jul
20
2010
By default is you create a NSS pool or volume, these are management by EVMS. EVMS is a disk manager original developed by IBM.
This is a quote about EVMS from the sourceforge website
The Enterprise Volume Management System (EVMS) Project has the goal of providing unparalleled flexibility and extensibility in managing storage. It represents a new approach to logical volume management for Linux. The architecture introduces a plug-in model that allows for easy expansion and customization of various levels of volume management.
EVMS provides a single, unified system for handling all of your storage management tasks. EVMS recognizes all of the disks on your system and allows for a variety of partitioning schemes. Software-RAID and logical volume groups can be managed in EVMS. Filesystems can be created and checked, and are automatically updated when changes are made to the underlying volumes. With EVMS, there is no longer a need for several individual utilities for performing each of these tasks.
In 2006 IBM discontinued development of the project. There have been no further releases until know. Therefor Novell announced in 2008 that they will be moving from EVMS to LVM for NSS.
From OES2 it’s possible to run NSS on LVM with some with some disadvantages:
- no iManager support
- no NSS tools who uses EVMS (like software RAID and the creation, modifiying and deletion of patitions)
- no NSSMU support (the feature F4 update NDS works!)
- no Clustering
Advantages of NSS on LVM are:
- Better support of LVM in Linux
- Creation of a aligned partition (VMware)
So how can we create a NSS Pool with LVM?
- Create a empty (aligned) partition with Yast
- Create the NSS Pool
mkfs -t nsspool -n nsspoolname devname - Create a directory for mouting the NSS Pool
mkdir /mnt/pooldir - Mount the pool
mount -t nsspool devname nsspoolmountpoint -o name=nsspoolname - Add the NSS pool to eDirectory
NSSMU | Pools | F4 (NDS Update) - Add the NSS Pool mountpoint to the fstab file
devname nsspoolmountpoint nsspool auto,rw,name=nsspoolname
And know the NSS Volume
- Create the NSS volume
mkfs -t nssvol -n nssvolname nsspoolname - Create the mountpoint for the NSS volume
mdkir /media/nss/nssvolname - Mount the NSS volume on the mountpoint
mount -t nssvol nssvolname volmountpoint -o name=nssvolname - Update eDirectory
NSSMU | Volume | F4 (NDS Update) - Add the NSS volume mountpoint to fstab file
nssvolname nssvolumemountpoint nssvol auto,rw,name=nssvolname
Now you have a NSS Pool and Volume with LVM
