Backup Server: 4.142.2.58: [0] The ’shmget’ call failed with error number 22 (Invalid argument). Refer to your operating system documentation for further details.

To confirm, if maximum shared memory has been manually set,

# projects -l

user.asetest
projid : 101
comment: “Sybase ASE”
users  : (none)
groups : (none)
attribs: project.max-shm-memory=(privileged,4294967296,deny)

For instance, here we have set the Maximum Shared memory to 4GB to the user account which owns and runs the Sybase ASE. And, the last line “attribs: project.max-shm-memory=(privileged,4294967296,deny)” basically, sets the maximum shared memory for the user processes to 4GB (4294967296).

This is equivalent to doing

# cat /etc/projects

If something similar doesn’t exist then the ASE is using the system defaults.

In any case, we need to increase the Maximum Shared memory. In our case increasing it to 7GB fixed the problem.

To add a new Project entry,

# projadd -p 101 -U asetest -c “Sybase ASE” -K “max-shm-memory=(privileged,7GB,deny)” user.asetest

This would create a new project with ID 101, name user.asetest for user asetest and set the Maximum Shared Memory to 7GB.

To modify an existing Project entry,

# projmod -sK “project.max-shm-memory=(privileged,7GB,deny)” user.asetest

This should help!

-> reset /SP
Are you sure you want to reset /SP (y/n)? y
Performing hard reset on /SP failed
reset: No such inventory

or when you try to reset the ILOM password, you may get the error “Set: No such object value”
To resolve the problem, you can actually logon to the ILOM as the user “sunservice” with the password of the ILOM root user and then reboot the ILOM (equivalne to “reset /SP”) with the command “reboot” as follows. Clearly as you can see from this warning SUN doesn’t recommend it so use it at your own risk:

login as: sunservice
Using keyboard-interactive authentication.
Password:

Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.

WARNING: The “sunservice” account is provided solely to allow
Sun Services to perform diagnosis and recovery tasks. Customer use of
the “sunservice” account may interfere with the correct operation of
ILOM and is not supported other than to perform recovery procedures as
documented by Sun Microsystems. Normal ILOM operations should always be
performed using the root account. Further usage of the “sunservice”
account implies your agreement with these terms.
[(flash)root@SERV-ILOM:~]# reboot
/sbin/reboot

Run the command

# ipmitool fru | grep “Product Serial”

where “FRU” is a Field Replaceable Unit. The problem here is it’s going to output too many serial numbers to confuse. The one we are interested is a 10 digit alpha-numeric number.

However, extending the command as

# ipmitool fru print |egrep “Mainboard|/SYS” | awk ‘{print $7}’
91)

Would give you the ID number of the “/SYS” or “Mainboard” (91 here) which mostly has the serial number of the system. We then run the “ipmitool” as follows with that ID number to find the system serial number.

# ipmitool fru print 91 |grep “Product Serial” | awk ‘{print $4}’

where “91″ was the ID number.

Oct  8 12:26:14 myserver sshd[29288]: [ID 800047 auth.error] error: Could not get shadow information for NOUSER

It would look like a security incident with the “nouser” system account but not so to be. The error gets written to /var/adm/messages when a user tries to SSH to the server using a user account which doesn’t exist on the system (a typo error can contribute) or on your NIS/NIS+ systems.

So no panic!!!!

Installing Sybase Perl Module requires the following preinstalled

1. Sybase Server/Client already installed on your server
2. GNU Make

Install GNU Make

Assuming you have already installed Sybase Server/Client on your system, lets download and install GNU Make.

GNU Make package can be downloaded from sunfreeware.com website. At the time of writing, the version available for download is Make 3.81

Download GNU Make for Solaris 10 (SPARC)

Download Make for Solaris 10 (x86)

Unzip and Install GNU Make

From the directory where the file is downloaded

# gunzip make-3.81-sol10-x86-local.gz
# pkgadd -d make-3.81-sol10-x86-local

This should install “make” under /usr/local/bin

# which make
/usr/local/bin/make

Download Perl Modules from www.cpan.org. The modules we are interested in are

1. DBI (Database Independent Interface for Perl)

2. DBD::Sybase (Sybase database Driver for the DBI module)

NOTE: I find in Solaris 10 Update 6, DBI module is already installed which means we only need to install DBD::Sybase module.

To verify either of the modules is already installed on the system,

For DBI, file DBI.pm should exist under

x86

/usr/perl5/vendor_perl/5.8.4/i86pc-solaris-64int/DBI.pm

SPARC

/usr/perl5/site_perl/5.8.4/sun4-solaris-64int/DBI.pm

For DBD::Sybase

x86

/usr/perl5/site_perl/5.8.4/i86pc-solaris-64int/DBD/Sybase.pm

SPARC

/usr/perl5/site_perl/5.8.4/sun4-solaris-64int/DBD/Sybase.pm

Now, assuming both these modules are not installed

Install Perl DBI Module

Download the DBI Module from here

From the download directory,

# gunzip DBI-1.609.tar.gz
# tar -xvf DBI-1.609.tar
# cd DBI-1.609

The above steps should (g)unzip, untar the downloaded source files.

Export $SYBASE & $LD_LIBRARY_PATH environment variables. We have the Sybase client installed under

/opt/sybase/oc15.0-EBF16084/OCS-15_0

which means the libraries exist under

/opt/sybase/oc15.0-EBF16084/OCS-15_0/lib

# export SYBASE=/opt/sybase/oc15.0-EBF16084/OCS-15_0
# export LD_LIBRARY_PATH=/opt/sybase/oc15.0-EBF16084/OCS-15_0/lib:$LD_LIBRARY_PATH

If this step is skipped, the following error comes up in the next step:

Can’t find the lib directory under /export/home/sybase! at Makefile.PL line 118, <IN> line 44.

Now comes the tricky bit, use /usr/perl5/bin/perlgcc instead of default perl as follows:

# /usr/perl5/bin/perlgcc Makefile.PL

Let’s now compile and install using GNU Make from source directory

# /usr/local/bin/make
# /usr/local/bin/make test
# /usr/local/bin/make install

To make sure the install compelted successfully. Check if the DBI.pm file exists as shown earlier.

Install Perl DBD::Sybase module

Download DBD::Sybase perl module from here.

From the downloaded directory:

# gunzip DBD-Sybase-1.09.tar.gz
# tar -xvf DBD-Sybase-1.09.tar
# cd DBD-Sybase-1.09

The above should (g)unzip, untar the downloaded file and change into the source directory.

Export the $SYBASE & $LD_LIBRARY_PATH environment variables if you have already not done so.

# export SYBASE=/opt/sybase/oc15.0-EBF16084/OCS-15_0
# export LD_LIBRARY_PATH=/opt/sybase/oc15.0-EBF16084/OCS-15_0/lib:$LD_LIBRARY_PATH

Run perlgcc against the Makefile.PL as follows:

# /usr/perl5/bin/perlgcc Makefile.PL

Select the default CHAIN mode or modify as required, then enter the Sybase Server, a Sybase Username and password and a Database as and when promted. This will allow the installation test connection. Make sure this DB connection is updated in the Sybase “interfaces” file.

NOTE: Once the installation is completed. Either the PWD file created by this procedure or the entire Source directory should be deleted as the PWD file will contain these DB access details. Also, it is advisable to provide a test DB access detail rather than a live environment.

Let’s now compile and install using GNU Make from source directory

# /usr/local/bin/make

Now, re-export $SYBASE as follows:

# export SYBASE=/opt/sybase/oc15.0-EBF16084

[NOTE: This may vary in your environment]

# /usr/local/bin/make test
# /usr/local/bin/make install

This should install the Sybase Perl module. To confirm the installation was successful, look for Sybase.pm as explained earlier.

Let’s look at the “which” utility in Solaris and find which package installed the file.

The file path for which is /usr/bin/which

# which which
/usr/bin/which

To find the package which installed it use the “pkgchk” command with the “-l” “and -p” options and the full file path of the file as follows,

# pkgchk -l -p /usr/bin/which
Pathname: /usr/bin/which
Type: regular file
Expected mode: 0555
Expected owner: root
Expected group: bin
Expected file size (bytes): 1288
Expected sum(1) of contents: 25204
Expected last modification: Jan 21 23:32:39 2005
Referenced by the following packages:
SUNWcsu

You can see that the which utility is installed by the package “SUNWcsu”.

# pkginfo -l SUNWlibgcrypt
PKGINST:  SUNWlibgcrypt
NAME:  Libgcrypt – Cryptographic Library
CATEGORY:  EVO146,application,JDS3
ARCH:  sparc
VERSION:  1.1.12,REV=10.0.3.2004.12.15.17.57
BASEDIR:  /usr
VENDOR:  Sun Microsystems, Inc.
DESC:  Libgcrypt – Cryptographic Library
PSTAMP:  fire420041215175708
INSTDATE:  Sep 15 2008 12:08
HOTLINE:  Please contact your local service provider
STATUS:  completely installed
FILES:        6 installed pathnames
2 shared pathnames
2 directories
2 executables
595 blocks used (approx)

But, if you want to see what those files and directories are then “pkgchk” should be your toy. The following should show the list of files and pathnames installed by the package:

# pkgchk -l SUNWlibgcrypt|egrep “Pathname|Type”
Pathname: /usr/bin
Type: directory
Pathname: /usr/bin/libgcrypt-config
Type: regular file
Pathname: /usr/lib
Type: directory
Pathname: /usr/lib/libgcrypt.so
Type: symbolic link
Pathname: /usr/lib/libgcrypt.so.1
Type: symbolic link
Pathname: /usr/lib/libgcrypt.so.1.5.1
Type: regular file

FATAL: system is not bootable, boot command is disabled

Don’t panic!!!

This error indicates that interrupted the boot process prematurely, most likely when the memory checks were run with “STOP + A” or a break from console.

To resolve this problem simply Power OFF and power ON the system. Alternatively, you can perform a “reset-all” from the OK prompt.

This should help!

There are many ways to do this. Let’s start with the easy one look at each of them

1. Use dos2unix utility

Solaris pre-installs dos2unix utility into the system to do this job for you. As the name says, it converts the file from DOS format to UNIX format. To do this the syntax is

# dos2unix <file> <new file>

for instance

# dos2unix test.txt test2.txt

Where the test.txt is the file you want the ^M characters removed and test2.txt is the file stripped of the ^M characters.

You may also overwrite the existing file by mentioning the source and destination files as same:

# dos2unix test.txt test.txt

2. Using VI

Open the file with “vi” editor and type the following:

:%s/^M//g

NOTE: To get the ^M in there, you should type CTRL+V+M

3. Using “tr” utility

“tr” utility is used to translate characters. Using with “-d” deletes a listed string.

# tr -d ‘\r’ <old.file > <new.file>

Alternatively, use its octel representation as follows:

# tr -d ‘\015′ <old.file > <new.file>

dladm is the admin utility for Data-Link Interface which helps to display informarthe like Link Status (UP/DOWN), Speed, Duplex, MTU, VLAN Tagged and crucially statistics of network traffic on each of the interfaces historically as well as in real time. dladm can also configure and admin Link Aggregation on multiple NICs which we will not focus here.

Show Link Status/Speed/Duplex

# dladm show-dev
nxge0           link: down      speed: 0     Mbps       duplex: unknown
nxge1           link: down      speed: 0     Mbps       duplex: unknown
nxge2           link: up        speed: 1000  Mbps       duplex: full
nxge3           link: up        speed: 1000  Mbps       duplex: full

As you can see above the “show-dev” option lists all the network interfaces with Link Status (UP/DOWN), current speed in Mbps and Duplex (Half/Full)

Show Link Status

# dladm show-link
nxge0           type: non-vlan  mtu: 1500       device: nxge0
nxge1           type: non-vlan  mtu: 1500       device: nxge1
nxge2           type: non-vlan  mtu: 1500       device: nxge2
nxge3           type: non-vlan  mtu: 1500       device: nxge3

Here “show-link” option reveals the MTU and the VLAN tagging detail on each of the interfaces on the system.

Show Stats of all Interfaces for all time

# dladm show-dev -s
ipackets  rbytes         ierrors opackets        obytes      oerrors
nxge0           0         0           0       0         0           0
nxge1           0         0           0       0         0           0
nxge2           179625752557169463759657      581104982 3964684165410
nxge3           22240891  1834257868  0       5198483   395084708   0

The “-s” option along with “show-dev” or “show-link” displays network traffic statistics including Input/Output packets, input/output errors.

Stats in real-time

To show the stats of a particular interface in real-time use the “-i” option which is the interval in seconds. The first line shows again historic stats and later on the real-time information for every “n” seconds (5 seconds in our example)

# dladm show-link -s -i 5 nxge2
ipackets  rbytes         ierrors opackets        obytes      oerrors
nxge2           179637824757173944575957      581119516 3964706801670
ipackets  rbytes         ierrors opackets        obytes      oerrors
nxge2           961       319105             0       150       17874       0
ipackets  rbytes         ierrors opackets        obytes      oerrors
nxge2           887       263850             0       117       16505       0

If we fail to mention the interface then it takes the default interface (1st in the list). As you can see from the example below, we see stats for nxge0 which is not connected.

# dladm show-link -s -i 5
ipackets  rbytes         ierrors opackets        obytes      oerrors
nxge0           0         0           0       0         0           0
ipackets  rbytes         ierrors opackets        obytes      oerrors
nxge0           0         0           0       0         0           0