EDG System Administration

Started getting this error in our samba logs and no one could mount a samba drive:

failed to bind to server ldap://server.uchicago.edu with dn="cn=Manager,dc=server,dc=uchicago,dc=edu" 
Error: Server is unwilling to perform unauthenticated bind (DN with no password) disallowed

I had just installed all the updates on the server, so I’m assuming this was related. I know that I ran smbpasswd -W to put the ldap password to use to bind in secrets.tdb. So, I just ran the command again and everything was fine. I guess that one of the updates either changed the format of the file or changed the file itself. Either way, we look to be ok now.

In the past, we’ve gotten errors from Cadence software about an incorrectly built binary, but the program would still run ok. The annoying errors were lost by editing /etc/csh.cshrc and adding the line:

setenv LD_ASSUME_KERNEL 2.4.1 # Gets rid of the "Incorrectly built binary" error

However, after the last software upgrade, any simple unix command was giving errors about libc.so.6: cannot open shared object file. These errors weren’t just annoying, they wouldn’t allow the simple programs, like hostname, who, etc. to run. So, the LD_ASSUME_KERNEL variable had to be unset.

On our server, I then got this error:

[maryh@server maryh]$ /net/sw/cad.rh/ic/ic5141/tools/dfII/bin/32bit/icms.exe: error while 
loading shared libraries: libXp.so.6: cannot open shared object file: No such file or directory

This was solved by running:

[root@server ~]# yum install xorg-x11-deprecated-libs

Now things work ok on the server, but as the csh.cshrc file gets pushed out to the other clients, it will have to be modified to put the LD_ASSUME_KERNEL line back in. This is because the clients are running rhel4 (the server is rhel5) and they need that line.

Our setup uses a regular windows xp computer with a 1.2TB drive as a file server. We want to install the Cadence software so that it’s on this shared (S:) drive, which will then be mounted by all the other windows computers in the shop. This is done by setting up a client install on the S: drive which will have a setup.exe file that will then be run on all the other computers to setup the Cadence software. Unfortunately, this client setup is not created when you run the setup.exe file from Cadence. You must run:

setup.exe admin

in order to have the client setup directory created.

hdiutil convert /path/to/.dmg -format UDTO -o /path/to/.iso

This sticks a .cdr extension on after the .iso, but I just deleted it.

or if creating from a disk, use Disk Utility and just change the Image Format to “DVD/CD Master”.

To see what different line types, styles, colors, etc. are available in gnuplot, start gnuplot, set the terminal and run test. The following picture will appear.

gnuplot> set terminal x11
Terminal type set to 'x11'
Options are '0'
gnuplot> test

Here is a plot showing the iperf results for some of our linux computers.

I decided to take all the old scsi disks that I have and attach them to an old pc and use the setup as a backup computer. I’ll put as many disks as I can into a software raid to use for backups and then put a dvd writer in the computer to use to write dvds.

Here is the scsi stuff attached:

Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: SEAGATE  Model: ST3146807LW      Rev: 0007
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 02 Lun: 00
  Vendor: SEAGATE  Model: ST336607LW       Rev: 0006
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 03 Lun: 00
  Vendor: SEAGATE  Model: ST336607LW       Rev: 0006
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 04 Lun: 00
  Vendor: SEAGATE  Model: ST336607LW       Rev: 0006
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 08 Lun: 00
  Vendor: SONY     Model: SDT-11000        Rev: 0200
  Type:   Sequential-Access                ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 09 Lun: 00
  Vendor: SEAGATE  Model: ST336607LW       Rev: 0007
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 11 Lun: 00
  Vendor: SEAGATE  Model: ST373307LW       Rev: 0007
  Type:   Direct-Access                    ANSI SCSI revision: 03

I’m going to combine all the ST336607LW disks into a software raid. First, create a new partition on each of these disks. Then create the raid.

# mdadm --create --verbose /dev/md0 --level=5 --raid-devices=4 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
# mkfs.ext3 -m0 -j -O dir_index,resize_inode,sparse_super /dev/md0
# tune2fs -c0 -i0 /dev/md0

After mounting, I have a 109GB drive mounted as the raid. Not much, but it’s a little more disk space to use. I’ll also mount the other disks, which are a little bigger to give me a bit more space.