1021. Recovering from forgetting the root password

If you forget your root password, you need to edit the /etc/shadow file. The following procedure outlines how to boot from the Solaris 2.x CD-ROM and edit the /etc/shadow file. You must have a CD-ROM drive to perform this procedure.

  1. If possible, shut down the system with the init 0 command.

    If this is not possible, enter the sync command three times, then do an emergency shutdown by pressing the L1 and A keys simultaneously (the infamous L1-A).

     

  2. When the OK prompt appears, insert the Solaris CD-ROM into the drive and initiate a stand-alone boot as typing:

    OK boot cdrom -s
    The screen displays:
    Resetting...
    (many lines of bootup information that take quite a while)
    INIT:SINGLE USER MODE
    #
     

     

  3. Check the file system:

    # fsck /dev/rdsk/c0t3d0s0

     

  4. Mount the file system (use the correct value for your boot disk--it could be c0t0d0s0 so edit the following if necessary):

    # mount /dev/dsk/c0t3d0s0 /a

     

  5. Set the environment and open the shadow file for editing:

    # TERM=sun
    # export TERM
    # chmod 600 /a/etc/shadow
    # vi /a/etc/shadow

     

  6. Delete the encrypted password between the first pair of colons in the root entry, for example:

    root:09PsdfrJut:9259:::::::
    should be changed to this:
    root::9259::::::

     

  7. Write the file to disk and exit the vi program using :wq.

     

  8. Unmount the file system and reboot by entering the following:

    # cd /
    # umount /a
    # fsck /dev/rdsk/c0t3d0s0
    # init 6

     

  9. After the system reboots, you can login to root without a password. To establish a new root password, use the passwd command.

1022. No decoupling or partial decoupling only

Perform the follow procedures if you take a spectra and your peaks do not fully decouple or if they show no decoupling at all.

  1. Insert the C13 sensitivity sample and retrieve the test parameters in /vnmr/tests/gamah2.par for testing gammah2. Check that the probe is properly tuned for both C13 and H1.
  2. Run the gammah2 test and determine the correct decoupler power and dmf settings. Follow the procedures in the Acceptance Test Procedures manual.
  3. If your decoupler problem occurs when running homodecoupling (proton observe, proton decoupling), recalibrate using the 1H sensitivity sample. If your problem occurs with X nucleus decoupling, make sure that you are getting X nucleus decoupling to the probe.

Measurement Points and Signal Levels for Troubleshooting the Decoupler Path of INOVA and UNITYPlus

Transmitter #2 (these signals are measured straight into the oscilloscope)
P2X4 Synth Input: +10 dBm
J2X5 LO Output: +10 dBm
J2X3 Xmtr Output: +10 dBm

When doing homodecoupling, the decoupler signal is combined with the observe signal at J297.
AMT #1
J4073 Channel A Output: 0 dB

(measured through a 30-dB attenuator, about 1 W is needed to heterodecouple, less for homodecoupling)
J4072 Channel B Output: +24 - + 26 dBm (measured through a 30 dB attenuator)

The measurement at the probe input should be approximately the same as the AMT output.

Measurement Points and Signal Levels for Troubleshooting the Decoupler Path of UNITY and VXR

Transmitter #2 (these signals are measured straight into the oscilloscope)
P3306 Synth Input: +10 dBm
J3302 LO Output: +10 dBm
J3304 Xmtr Output: +16 dBm (BB decoupler), +30 dBm (fixed-frequency decoupler)

When doing homodecoupling, the decoupler signal is combined with the observe signal at AMT Channel A Input.

AMT #1
J4073 Channel A Output: 0 dB (measured through a 30-dB attenuator)

about 1 W is needed to heterodecouple, less for homodecoupling)

J4072 Channel B Output: +24 - + 26 dBm (measured through a 30-dB attenuator)

The measurement at the probe input should be about the same as the AMT output.

Measurement Points and Signal Levels for Troubleshooting the Decoupler Path of MERCURY

High-band Transmitter board

(these signals are measured straight into the scope and P66 REF IN 0.9 Vp-p (+3 dBm) SMB to BNC connector)

J62 LO Output: 0.6 Vp-p (+0 dBm)
J63 Xmtr Output: 0.7 Vp-p (+1 dBm)
Low-band Transmitter board
P44 REF IN: 0.9 Vp-p (+3 dBm)
J42 LO Output: 0.6 Vp-p (+0 dBm)
J43 Xmtr Output: 0.7 Vp-p (+1 dBm)
AMT amplifier
J207 Ch A Output: +0 dBm (measured through a 30-dB attenuator)
J211 Ch B Output: +24 - + 26 dBm (measured through a 30-dB attenuator)

When doing homodecoupling, the decoupler signal is combined with the observe signal at J23. Make sure your system has homodecoupling option.

Measurement Points and Signal Levels for Troubleshooting the Decoupler Path of Gemini

1H Transmitter board (these signals measured straight into the oscilloscope)
J2602 LO Output: 2 Vp-p (+10 dBm)
J2603 Xmtr Output: 20 Vp-p (+30 dBm) [400 MHz @ 2 Vp-p (+10 dBm)]
13C Transmitter board
J2702 LO Output: 2 Vp-p (+10 dBm)
J2703 Xmtr Output: 20 Vp-p (+30 dBm)
Broadband Transmitter board
J2702 LO Output: 2 Vp-p (+10 dBm)
J2703 Xmtr Output: 2 Vp-p (+10 dBm)
1H/13C Pulse Amplifier board
J2904 1H Output: +10 dBm @ 200 MHz, +14 dBm @ 300 MHz (through a 30-dB attenuator)
Kalmus amplifier
J2904 1H Output: +20 dBm (measured through a 30-dB attenuator)
J2902 13C Output: +22 dBm (measured through a 30-dB attenuator)

When doing homodecoupling, the decoupler signal is combined with the observe signal at J2904. Make sure your system has the homodecoupling option.

1023. VT is not responding or not heating

  1. Make sure the VT controller is on, the VT cable is connected to the probe, and the configuration of the VT is present in the config table.

     

  2. Reset the VT controller by turning the controller power off and on.

     

  3. If the message "VT not responding" still appears, check the serial cable that connects from the VT controller to the CPU board or the back plane of digital card cage. If all connections are good, the controller may have the problem.

     

  4. If the VT is not heating, the controller LED is flashing and displays normal room temperature, there may be a problem with the probe. Verify with another probe, if available.

     

  5. If the VT is heating but not regulating, there may be a problem with the probe. Verify with another probe, if available.

     

  6. If the VT is reading 209 or 999 with the cable is connected to the probe, there may be a problem with the VT cable.

1024. Probe has water and/or air has water

  1. To get rid of the excessive water, take the probe out and set it in a upside down position, and then blow N2 gas into the VT and cooling connections of the probe for about 30 minutes.

     

  2. Purge the air line by releasing the water from the air filter for about 10 minutes. Purge the rest of the air line by releasing air pressure without connecting to the probe.

     

  3. Put the probe back into the magnet and heat the probe at 50 degrees C for 30 minutes. Observe an NMR spectrum. If there is no spectrum, the probe may be damaged by water and need factory repair.

     

  4. To avoid further water problems, purge the air line everyday or buy a air dryer

1025. Why do I get error messages at shutdown?

Unmounting /vol error
INIT: failed write of utmpx...

We read this information in "Inside Solaris" magazine. April 1997

Unmounting /vol error

This problem is caused by an error in one of the Solaris .rc files.
 

Jan 21 20:32:18 /usr/sbin/vold[418]: problem
unmounting /vol; Interrupted system call

The system attempts to unmount the /vol file system before shutting down the vold daemon which is using /vol. By trying to unmount a used file system, an error is created. The solution is to kill the daemon before unmounting the file system.

Killing the vold daemon first will fix the problem. You will have to become root first. Then create a link to an existing shutdown script before entering run level 0.

Become root and enter the following:
# ln -s /etc/init.d/volmgt /etc/rc0.d/K68volmgt

The /etc/rc0.d directory contains scripts that are executed when Solaris enters run level 0 (Shut Down). Solaris runs all scripts starting with K and passes them "stop" as a parameter. The volmgt script found in the /etc/init.d directory already uses this protocol and the above procedure will cause vold to shutdown properly.
 


INIT: failed write of utmpx...

The error messages that is most frustrating, however, are this pair of messages. On some installations, We get these errors, and on other installations, We don’t.
 

INIT: f a i l e d o n w r i t e o f u t m p x entry:“sO”
INIT: f a i l e d o n w r i t e o f u t m p x entry:“fw”

For a long time, We’ve just been putting up with these error messages. It turns out that these messages occur for a similar reason as the previous error.
Here, the init command is trying to update the utmpx log file, which contains information about system run-level transitions, as well as user login and logout information. On some Solaris installations, the /var file system was on a separate partition!
When Solaris goes to run level 0, it un-mounts all the expendable file systems, such as /var. However, init then tries to enter this information in the log file, which is no longer accessible. That certainly clears things up!
Thus, all you do is provide a place for init to write your log file entries. If you really don’t care about the run-level transition messages, you can just write the information to/dev/null, and it’ll be thrown away without a trace. To do this, shut down your system and restart it. However, when you restart it, make sure you issue a boot -s command to boot it initially in single-user mode. Once you’ve booted up in single-user mode, enter these commands:

# umount /var
# mkdir /var/adm
# ln -s /dev/null /var/adm/utmpx
# ln -s /dev/null /var/adm/utmp

(If you try to bypass the boot -s step by executing the init S command to go to single-user mode, umount will tell you that the /var file system is busy. Don’t even try to circumvent the shutdown/boot -s procedure, it won’t work.)
Now we simply have a fake file system at the /var mount point. So when Solaris unmounts /var, the files /var/adm/utmpx and /var/adm/utmp will still exist. (They just won’t be the same ones.) Now, init won’t fail when it writes the log entries. You might wonder why we created both utmpx and utmp, when init was complaining only about utmpx. It turns out that if you create the utmpx file, init then complains about the utmp file. It writes log entries to both files, but writes to utmpx (and fails) first.
If you’d really rather keep all the log in-formation, you can try a similar trick. Instead of throwing away all the data, move your utmpx and utmp files to another location. Then create links to these new files at both their real locations and at the fake locations at the mount point. Then you can get rid of the messages and keep all your logging information.

1026. How do you fix a HeartBeat not found error?

Symptom: The following message appears:
 

'commfuncs.c'; line:378 no HeartBeat reply, restarting Exproc, SendProc, RecvProc

You can run Vnmr and analyze pre-existing data, but all attempts to collect new data fail.

 


To correct this problem:

  1. First be sure that Expproc and associated processes are not active.
    (This includes acqstat and acqi windows)

     

  2. Log in as vnmr1 and type the following:
    3. vnmr1> cd /vnmr/bin
    vnmr1> ls -al
    check the permission of the following files:

    /vnmr/bin/Vnmr, /vnmr/bin/send2Vnmr and /vnmr/acqbin/Expproc 

    -rwsr-sr-x   1 vnmr1    nmr      1575260 Dec 18  1996 Vnmr
-rwsr-sr-x   1 vnmr1    nmr         7916 Dec 18  1996 send2Vnmr
-rwsr-sr-x   1 vnmr1    nmr       113896 Dec 18  1996 Expproc

    If they do not have the UID and GID bit set, do the following correction:
     

    vnmr1> chmod 6755 Vnmr
    vnmr1> chmod 6755 send2Vnmr
    vnmr1> cd ../acqbin
    vnmr1> chmod 6755 Expproc
     

    (This will change the sticky bit for these files, if you looked at the permissions for these files they will look like this; -rwsr-sr-x)

     

  3. Log in as root and type the following:
    4. # cd /vnmr/bin
    # ./rmipcs a
     
        Answer y to the question.

     

  4. Reboot the spectrometer console and restart Expproc:
    5.     su acqproc

1027. Why doesn't the Print button work in the VNMR Config window?

The Print button in the config windows uses the vnmrprint command.  Unfortunately this requires you to create a print device LP.  The adddevices program will not let you create an entry called LP.  What you will need to do is add the device LP using the admintool program.  This can be done by performing the following(These procedures are for HP printers only):

 

  1. Open a shelltool, commandtool, or terminal window.  Become root by typing su and then enter the root password.

     

  2. Start the admintool program by typing  admintool &

     

  3. The admintool window will appear.  Select Browse, a pulldown window will open, then select printers.

     

  4. Your admintool window will now display the printers and plotters that you have already created.  Select Edit, and then select add from the pulldown window using the right mouse button. Another puldown window will appear, select add local printer.

     

  5. A window title Admintool:Add Local Printer will open.  Enter the following information:
    6. Printer Name:   lp
    Description:   This can be left blank
    Printer Port:  Select the correct port for your printer
    Printer Type:  HP Printer
    File Contents:   ASCII
    Options:  select default
    Select the OK button

Your Print button in the Config window should now work

1028. How do I "unlock" an experiment that is "locked"?

Usually the command unlock(n) where n, the experiment number, will "unlock" that experiment. If this does not work, check the file listings in vnmrsys (Example: /export/home/vnmr1/vnmrsys) for the user that you are logging in as. If there is more than 1 file of the format lock_?.primary (where "?" is the experiment number other than the one you are currently in) remove that "lock" file. To check for multiple locked files perform the following:

cd ~/vnmrsys

ls

(you will get a listing of the files in that directory that may be similar to the below example)

    data/            help/            manual/          shapelib/
    exp1/            imaging/         menulib/         shims/ 
    exp2/            lock_2.primary   psglib/          tablib/
    exp3/            lock_3.primary   pulsecal         templates/
    global           maclib/          seqlib/

rm lock_3.primary

(or rm lock_2.primary, whichever experiment you wish to unlock)

****NOTE**** You should always have one lock?_primary. This locks your current experiment so that remote logins cannot interfer with your current acquisition.

1029. In CDE, the color of VNMR window flashes. What do I do?

Open the Style Manager ( fourth ICON from the right on the ICON bar). Select "More Colors" button and select "More colors for applications". Click "OK". Log out and log back in.

1030. When logged into an SGI and trying to run VnmrX remotely, the following error message appears (and VNMR does not run): OPEN LOOK Toolkit Error in application "VNMR": Could not load 75-75-p-116-sunolglyph-1. What do I do?

Workaround:

The requested font, which is used by Sun's OpenLook for various screen displays is missing on the SGI. To create it:

On the SGI, become root.

cd /usr/lib/X11/fonts/misc

vi fonts.dir

In the file, find the line olgl12.pcf.Z-sun-open look glyph-----12-120-75-75-p-113-sunolglyph-1 Duplicate the line that starts with olgl12.pcf.Z and then change the 113 to 116 in the duplicate. The result will look like the following:

olgl12.pcf.Z -sun-open look glyph-----12-120-75-75-p-113-sunolglyph-1

olgl12.pcf.Z -sun-open look glyph-----12-120-75-75-p-116-sunolglyph-1

Save your changes to fonts.dir and exit from the editor. Now enter the UNIX command xset fp rehash