Christian’s blog

Here I am, preparing our environment for the first (of hopefully many) tester for our upcoming VTL project. So I ended up installing the ISC and Administration Center for Tivoli Storage Manager on a 64bit guest (that is SLES10 for AMD64), just because I forgot to include support for later versions with our current running one. Guess what, na-na na na na. Exactly, didn’t work, the same errors I got while trying it before in a virtual environment. “Portlet is not available.”

So I ended up redoing the whole thing on a 32bit guest and guess what … bada-bing. works … *shrug* I don’t know whether or not that’s a surprising thing .. but what surprises me, is that I do have a working 64bit Integrated Solutions Console and Administration Center running, only difference is that one is running on real hardware.

Anyway, after looking on how the Integrated Solutions Console (that is the Websphere environment - yes *yuck*) did it’s own start up after boot (you know, I’d like to restart an application if it’s hanging without the need to reboot the whole box), I found this particular line of code:

isc6:23:boot:/opt/tivoli/isc/PortalServer/bin/startISC.sh ISC_Portal

And since I was lazy (and it was already Friday afternoon), I ended up writing a small init script which rids you of the need of such a ugly way to start a service.

#! /bin/sh
#
# /etc/init.d/isc
#
### BEGIN INIT INFO
# Provides:       isc
# Required-Start: network
# Should-Start:
# Required-Stop:  network
# Default-Start:  2 3 5
# Default-Stop:
# Description:    Start the Tivoli Integrated Solutions console
### END INIT INFO
 
. /etc/sysconfig/isc
 
BINDIR=/sbin
 
. /etc/rc.status
rc_reset
 
case "$1" in
  start)
    echo -n "Starting Tivoli Integrated Solutions Console server"
    startproc -p /var/run/tivoli-isc.pid \
      $ISC_INSTALL/PortalServer/bin/startISC.sh \
      ISC_Portal 2>&1 >/var/log/tivoli-isc.log
    # I know, this is *real* ugly
    PID=$( tail -n 1 /var/log/tivoli-isc.log | cut -d\  -f10 )
    echo $PID >/var/run/tivoli-isc.pid
    rc_status -v
    ;;
  stop)
    echo -n "Stopping Tivoli Integrated Solutions Console server"
    $ISC_INSTALL/PortalServer/bin/stopISC.sh \
      ISC_Portal $ISC_ADMIN $ISC_PASSWORD \
      2>&1 >/var/log/tivoli-isc.log
    rc_status -v
    ;;
  restart)
    $0 stop
  	$0 start
  	rc_status
  	;;
  status)
    echo -n "Tivoli Integrated Solutions Console server:"
    checkproc -p /var/run/tivoli-isc.pid \
      $ISC_INSTALL/AppServer/java/bin/java
    rc_status -v
    ;;
  *)
  	echo "Usage: $0 {start|stop|status|restart}"
    exit 1
  ;;
esac
rc_exit

And the corresponding sysconfig file:

## Type:     string
## Default:  iscadmin
## Config:   ""
## ServiceRestart:  isc
#
# Adminstration user for the Portal
ISC_ADMIN="iscadmin"
 
## Type:     string
## Default:  iscadmin
## Config:   ""
## ServiceRestart:  isc
#
# Adminstration user password for the Portal
ISC_PASSWORD="iscadmin"
 
## Type:     string
## Default:  /opt/ISC/601
## Config:   ""
## ServiceRestart:  isc
#
# Full path to the ISC Portal installation root directory
ISC_INSTALL="/opt/tivoli/isc"

Et voilá, it’s done. Now just a `chkconfig -a isc‘ and it’s gonna startup nice and easy (when it really should) via the normal service startup and not get spawned from the inittab.

Life SLES10, Tivoli

We’re currently having a weird issue (which we had before); the Windows XP Embedded powering our Wyse V90’s isn’t applying any GPO settings if you log on with a user that has a configured profile.

Googling (is that a valid word yet ?!) for it, only resulted in one useful link, which is apparently a guy with the exact same problem … *shrug* I’m completely out of ideas by now, as I don’t even have a place to start (as in where the reason might be located).

Well, I do have a place to start with (that’s the local Events Viewer), which indeed lists some errors, but only such errors which ain’t making any sense. For example I see this:

• Userenv:1086 - “Windows cannot do loopback processing for downlevel or local users. Loopback processing will be disabled.“
• SceCli:1704 - “Security policy in the Group policy objects has been applied successfully.“
• Userenv:1085 - “The Group Policy client-side extension Folder Redirection failed to execute. Please look for any errors reported earlier by that extension.“

Life Active Directory, Thin Clients, Windows XP Embedded, Work

If you’re using a 2.6 based distribution, the FC HBA (or more correctly the corresponding driver) should create entries in /sys/class/scsi_host. Now you only need to get the host-number (basically the # of the host bus adapter) and you can get started ..

Simply doing this, is going to tell the FC HBA “rescan” and discover new devices ..

1

$ echo "1" > /sys/class/fc_host/host/issue_lip

That should do the trick, and you should be able to get udev to recognize the new devices attached via FibreChannel without the need to reboot the whole box (which might be a bit tricky).

Life safekeeping