Unix Sysadmin » Uncategorized

Disable / Turn Off Linux Password expiration / Aging

elizar — Thu, 15 Dec 2011 07:48:06 +0000

Yep, another personal reference and to think that I should know these stuff by heard. Well, most of the servers I am handling now are solaris and for particular example, it’s for Linux..

I guess there will be some similarities but for this post, we’ll take Redhat linux as an example:

The command is chage (looks like a misspelled ‘change’ right? It’s actually “Change” “Age”)

/etc/shadow stores actual password in encrypted format for user’s account with additional properties related to user password.

The password expiration information for a user is contained in the last 6 fields. Password expiration for a select user can be disabled by editing the /etc/shadow file

However I recommend using chage command. The chage command changes the number of days between password changes and the date of the last password change. This information is used by the system to determine when a user must change his/her password.

To list current aging type chage command as follows:

# chage -l rg49945
Minimum: 0
Maximum: 99999
Warning: 7
Inactive: -1
Last Change: Jun 07, 2011
Password Expires: Never
Password Inactive: Never
Account Expires: Never
#
# chage -l ct92623
Minimum: 0
Maximum: 99999
Warning: 7
Inactive: -1
Last Change: Jun 07, 2011
Password Expires: Never
Password Inactive: Never
Account Expires: Never
#
# passwd rg49945
Changing password for user rg49945.
New password:
Re-enter new password:
Password changed.
passwd: all authentication tokens updated successfully.
#
# passwd ct92623
Changing password for user ct92623.
New password:
Re-enter new password:
Password changed.
passwd: all authentication tokens updated successfully.

Protect Your Users – Websites To Block From Your Network

elizar — Sun, 11 Dec 2011 00:10:43 +0000

As a System Administrator, one of our main responsibility if to protect our user from (themselves) internet sites that are not appropriate in the workplace.

On this article, let’s enumerate some of the websites that needs to be blocked and should not even reach the company servers.

TNAFlix
Xhamster
Redtube
Tube8
Empflix
Youjizz
Jizzhut
JizzOnline

These are just some of them. I will update the list as I discover them by reading the logs.

Subscribe now and be informed of these kind of sites.

ufsdump – How To Backup Solaris/Linux Root Filesystem

elizar — Tue, 11 Oct 2011 01:53:56 +0000

Alright, here’s how – usfsdump – How To Backup Solaris/Linux Root Filesystem. use ufsdump

Say for example you have this:

$ df -k /
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 673951 415497 197799 68% /
$ df -k /CMS
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t8d0s0 35009161 32305691 2353379 94% /CMS
$

yeah, the /CMS file system is almost full, but I think it can still accomodate a 674MB root filesystem from the slice /dev/dsk/c0t0d0s0, right?

Anyway, not sure if the 2GM limit is applicable to Solaris 8,9 or 10 but since this example is less than 1GB, we are ok to proceed.

myserver# cd /CMS
myserver# ufsdump -f dumpfile /dev/dsk/c0t0d0s0
DUMP: Date of this level 0 dump: Tue Jul 20 16:41:50 2004
DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/rdsk/c0t0d0s0 (myserver:/) to dumpfile.
DUMP: Mapping (Pass I) [regular files]
DUMP: Mapping (Pass II) [directories]
DUMP: Writing 32 Kilobyte records
DUMP: Estimated 366 blocks (183KB).
DUMP: Dumping (Pass III) [directories]
DUMP: Dumping (Pass IV) [regular files]
DUMP: 318 blocks (159KB) on 1 volume at 963 KB/sec
DUMP: DUMP IS DONE
krypton# ls -l
total 340
-rw——- 1 root other 163840 Jul 20 16:41 dumpfile
-rw-r–r– 1 haefnr2 instrume 11 Jul 20 16:38 test1
-rw-r–r– 1 haefnr2 instrume 21 Jul 20 16:38 test2
krypton# file dumpfile
dumpfile: ufsdump archive file

ufsrestore should do the trick in recovering the system.. hopefully

How To Restore Root (and /usr/) rfile system Solaris- restoresymtable –

elizar — Fri, 28 Jan 2011 13:57:53 +0000

Sun Solaris – Restoring root file system (/) – Solaris 9, Solaris 10 provides steps we need to follow to restore the root file system (/ system) in SPARC and x86 (intel) machines.
1) Log in as root user. It is a security practice to login as normal user and perform an su to take root user (super user) role.
2) Appearance of # prompt is an indication that the user is root
3) Use who -a command to get information about current user
4) When / (root filesystem) is lost because of disk failure. In this case we boot from CD or from the network.
5) Add a new system disk to the system on which we want to restore the root (/) file system
6) Create a file system using the command :
newfs /dev/rdsk/partitionname
7) Check the new file system with teh fsck command :
fsck /dev/rdsk/partitionname
Mount the filesystem on a temporary mount point :
mount /dev/dsk/devicename /mnt
9) Change to the mount directory :
cd /mnt
10) Write protect the tape so that we can’t accidentally overwrite it. This is an optional but important step
11) Restore the root file system (/) by loading the first volume of the appropriate dump level tape into the tape drive. The appropriate dump level is the lowest dump level of all the tapes that need to be restored. Use the following command :
ufsrestore -rf /dev/rmt/n
12) Remove the tape and repeat the step 11 if there is more than one tape for the same level
13) Repeat teh step 11 and 12 with next ddump levels. Always begin with the lowest dump level and use highest ump level tape
14) Verify that file system has been restored :
la
15) Delete the restoresymtable file which is created and used by the ufsrestore utility :
rm restoresymtable
16) Change to the root directory (/) and unmount the newly restored file system
cd /
umount /mnt
17) Check the newly restored file system for consistency :
fsck /dev/rdsk/devicename
18) Create the boot blocks to restore the root file system :
installboot /usr/platform/sun4u/lib/fs/ufs/bootblk /dev/rdsk/devicename — SPARC system
installboot /usr/platform/`uname -i`/lib/fs/ufs/pboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/devicename — x86 system
19) Remove teh last backup tape, and insert a new tape onto which we can write. Make a dump level 0 backup of the newly restored system by issuing the following command :
ufsdump 0ucf /dev/rmt/n /dev/rdsk/deviceName
This step is needed because ufsrestore repositions the files and changes the inode allocations – the old backup will not truly represent the newly restored file system
20) Reboot the system :
#reboot (or)
# init 6
System gets rebooted and newly restored file systems are ready to be used.

Solutions for Solaris SVM Needs Maintenance and Last Erred status

elizar — Fri, 24 Sep 2010 02:36:55 +0000

This post is because while patching a Solaris 10 server with patch level Generic_142900-02 to Generic_142900-13.. There’s a need maintenance error on one of the sub mirror:

When a slice in a mirror or RAID5 metadevice device experiences errors,
DiskSuite puts the slice in the “Maintenance” state. No further reads or
writes are performed to a slice in the “Maintenance” state. Subsequent
errors on other slices in the same metadevice are handled differently,
depending on the type of the metadevice.

A mirror may be able to tolerate many slices in the “Maintenance” state and still be read from and written to. A RAID5 metadevice, by definition, can only tolerate a single slice in the “Maintenance” state. When either a mirror or RAID5 metadevice has a slice in the “Last Erred” state, I/O is still attempted to the slice marked “Last Erred”. This is because a “Last Erred” slice contains the last good copy of data from DiskSuite’s point of view.

With a slice in the “Last Erred” state, metadevice behaves like a normal
device (disk) and returns I/O errors to an application. Usually, at this
point some data has been lost.
Always replace slices in the “Maintenance” state, followed by those in the
“Last Erred” state. After a slice is replaced and resynched, use the metastat
command to verify its state, then validate data to make sure it is good.
Here are the specifics for Mirrors and RAID5 devices:
1. Mirrors
If slices are in the “Maintenance” state, no data has been lost. You can
safely replace or enable the slices in any order. If a slice is in the “Last
Erred” state, you cannot replace it until you first replace all the other
mirrored slices in the “Maintenance” state. Replacing or enabling a slice in
the “Last Erred” state usually means that some data has been lost. Be sure
to validate the data on the mirror after repairing it.
2. RAID5 metadevices
A RAID5 metadevice can tolerate a single slice failure. You can safely
replace a single slice in the “Maintenance” state without losing data. If
an error on another slice occurs, it is put into the “Last Erred” state. At
this point, the RAID5 metadevice is a read-only device; you need to perform
some type of error recovery so that the state of the RAID5 metadevice is
non-errored and the possibility of data loss is reduced. If a RAID5
metadevice reaches a “Last Erred” state, there is a good chance it has
lost data. Be sure to validate the data on the RAID5 metadevice after
repairing it.
How to remove “maintenance” and “last erred” example, In this point maybe pay attention
in some case The “lost Erred” sub-mirror side have contained “maintenance” and “Okey” state

Metastat gives :
d0: Mirror
Submirror 0: d10
State: Needs maintenance
Submirror 1: d20
State: Needs maintenance
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 8395200 blocksd10: Submirror of d0
State: Needs maintenance
Invoke: after replacing “Maintenance” components:
metareplace d0 c1t0d0s0
Size: 8395200 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s0 0 No Last Erred
d20: Submirror of d0
State: Needs maintenance
Invoke: metareplace d0 c1t1d0s0
Size: 8395200 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s0 0 No Maintenance
d1: Mirror
Submirror 0: d11
State: Okay
Submirror 1: d21
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 8395200 blocksd11: Submirror of d1
State: Okay
Size: 8395200 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s1 0 No Okay
d21: Submirror of d1
State: Okay
Size: 8395200 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s1 0 No Okay
d4: Mirror
Submirror 0: d14
State: Needs maintenance
Submirror 1: d24
State: Needs maintenance
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4202688 blocksd14: Submirror of d4
State: Needs maintenance
Invoke: after replacing “Maintenance” components:
metareplace d4 c1t0d0s4
Size: 4202688 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s4 0 No Last Erred
d24: Submirror of d4
State: Needs maintenance
Invoke: metareplace d4 c1t1d0s4
Size: 4202688 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s4 0 No Maintenance
d5: Mirror
Submirror 0: d15
State: Okay
Submirror 1: d25
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 62918208 blocksd15: Submirror of d5
State: Okay
Size: 62918208 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s5 0 No Okay
d25: Submirror of d5
State: Okay
Size: 62918208 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s5 0 No Okay
d6: Mirror
Submirror 0: d16
State: Needs maintenance
Submirror 1: d26
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 52436928 blocksd16: Submirror of d6
State: Needs maintenance
Invoke: metareplace d6 c1t0d0s6
Size: 52436928 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s6 0 No Maintenance
d26: Submirror of d6
State: Okay
Size: 52436928 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s6 0 No Okay
d7: Mirror
Submirror 0: d17
State: Okay
Submirror 1: d27
State: Needs maintenance
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 6970560 blocksd17: Submirror of d7
State: Okay
Size: 6970560 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s7 0 No Okay
d27: Submirror of d7
State: Needs maintenance
Invoke: metareplace d7 c1t1d0s7
Size: 6970560 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s7 0 No Maintenance
-First dettach,delete master slice6 and resync with mirror side slice6,Because in this way the intact data only in mirror side:
# metadetach d6 d16
# metaclear d16
# metainit d16 1 1 c1t0d0s6
# metattach d6 d16
- Wait for “Okay” status for the master slice6,
- Then replace “Last erred” state disk before.
Run “metadetach” to detach all the sub-mirrors on the mirror disk from
their respective mirrors (see the following):
[b]# metadetach -f [/b]
NOTE: The “-f” option is not required if the metadevice is in an “okay”
state.
Then run metaclear to remove the configuration from the disk:
[b]# metaclear [/b]
# metadb -d c1t1d0s3
# luxadm remove_device /dev/rdsk/c1t1d0s2 (physical remove disk when prompt to pull out disk)
# devfsadm -C -c disk -v
# luxadm insert_device /dev/rdsk/c1t1d0s2 (physical insert disk when prompt to pull in disk)
# prtvtoc /dev/rdsk/c1t0d0s2 |fmthard -s – /dev/rdsk/c1t1d0s2
# metadb -afc 3 c1t1d0s3
Use “metainit” and “metattach” to re-create and attach those submirrors to
the mirrors to start the resync:
[b]# metainit 1 1 c#t#d#s#[/b]
[b]# metattach [/b]
When all slice resync are finished,Begin replace “Last Erred” master disk
Run “metadetach” to detach all the sub-mirrors on the master disk from
their respective mirrors (see the following):
[b]# metadetach -f [/b]
NOTE: The “-f” option is not required if the metadevice is in an “okay”
state.
Then run metaclear to remove the configuration from the disk:
[b]# metaclear [/b]
# metadb -d c1t1d0s3
# luxadm remove_device /dev/rdsk/c1t0d0s2 (physical remove disk when prompt to pull out disk)
# devfsadm -C -c disk -v
# luxadm insert_device /dev/rdsk/c1t0d0s2 (physical insert disk when prompt to pull in disk)
# prtvtoc /dev/rdsk/c1t1d0s2 |fmthard -s – /dev/rdsk/c1t0d0s2
# metadb -afc 3 c1t0d0s3
Use “metainit” and “metattach” to re-create and attach those submirrors to
the mirrors to start the resync:
[b]# metainit 1 1 c#t#d#s#[/b]
[b]# metattach [/b]
When all slice resync finished,the two sub-mirror is normal.

Cannot find required executable /usr/bin/7za

elizar — Wed, 24 Mar 2010 04:59:47 +0000

The complete error actually is:

Cannot find required executable /usr/bin/7za
pkgadd: ERROR: class action script din not complete successfully

That was the error message displaced when I tried installing two Sun packages as requested by a user, SUNWeu8os and SUNWeulof.

Packages can be found in tge Solaris 10 disk release 5/08. When i tried installing the package I got the error above.

There are two ways you can get that binary and one of them is by using the installation disk of Solaris 10 5/08.

Another one is by installing patch 137321-01 for sparc and 137322-01 for x86

Limesurvey PHPSurveyor

elizar — Wed, 24 Feb 2010 00:59:25 +0000

LimeSurvey (formerly PHPSurveyor) is a Webapplication that interacts with MySQL, MSSQL, orPostgres to develop surveys, publish surveys, andcollect responses to surveys.

Once a survey has been created, data can be inserted into the survey either by a “pretty” public screen which presents each question one at a time, or by a quick and nasty data entry screen. It includes the capacity to generate individualized “tokens”, so that invitation can be issued to participants. It also has the capacity to set conditions on whether questions will display (branching), numerous question types, and a basic statistics function. Changes: A Malay translation was added, several minor bugs were fixed, and translations were updated.

ZFS Quotas and Reservations

elizar — Thu, 29 Oct 2009 12:25:47 +0000

Notes on ZFS quotas, reservations and others.. like adding up disk for the pool and creating pool altogether.

First, create a pool using ‘zpool‘. Then use ‘zfs‘ to make the filesystems.

Creating Pool with zpool

Create a pool called pool1. The -m is optional. If given, it specifies a mount point for zfs filesystems created from the specified pool. The mount point should be empty or nonexistant. If the -m argument is omitted, mount point is “/”.

# zpool create -m /export/data01 ALB mirror c2t0d0 c4t0d0 # zpool status pool: pool1 state: ONLINE scrub: none requested config:
NAME STATE READ WRITE CKSUM pool1 ONLINE 0 0 0 mirror ONLINE 0 0 0 c2t0d0 ONLINE 0 0 0 c4t0d0 ONLINE 0 0 0

http://www.mattzone.com/site/index.php?name=News&file=article&sid=3

http://dlc.sun.com/osol/docs/content/ZFSADMIN/gazvb.html

http://prefetch.net/blog/index.php/2006/12/26/adding-disks-to-zfs-pools/

Creating ZFS filesystem from Pool

ld.so.1: cc: fatal: libpicl.so.1: open failed: No such file or directory

elizar — Thu, 17 Sep 2009 03:47:09 +0000

ld.so.1: cc: fatal: libpicl.so.1: open failed: No such file or directory – that’s the latest problem we encountered in installing Ruby on Rails… (well, not actually on Ruby but in some dependencies)…

Last time we did the GlassFish webstack installation (just to get RoR working) because the Ruby in Coolstack was an old version Ruby 1.8.6 something.

But as far as Ruby on Rails installation is concern, the Optimized Open Source Software Stack (Cool Stack) is working properly.. As well as the Glassfish installation.. The problem we’re getting is for some Gems that we’re trying to install (oracle gems and hobo and others)…

For this one, we’re trying to install the Oracle gem thing.. and it requires to compile something that needs CC.. we ended up installing Sun Studio 12.. (but I still believe gcc is a perfect alternative for cc).

Anyway, searching for “ld.so.1: cc: fatal: libpicl.so.1: open failed: No such file or directory” will give you unrelated websites (well, until this one gets indexed that is)..

As of this writing it only has 4 results:

What I did is i downloaded a Sun patch that contains the file and placed in my server same location:

Take this patch for example:

http://sunsolve.sun.com/search/document.do?assetkey=1-21-108528-29-1

libpicl.so.1 installs in /usr/lib/abi/abi_libpicl.so.1 , /usr/lib/abi/sparcv9/abi_libpicl.so.1, /usr/lib/libpicl.so.1

and others

Ubuntu New Release Ver. 9 Available for Download Free

elizar — Wed, 29 Apr 2009 02:31:25 +0000

Just want to confirm my hunch that this Ubuntu 9 sites that is all over the internet is nothing but worthless, infoless, another junk spread in the internet. But if you really want to download the new release or version of UBUNTU 9, there is a link in Review ninja you can go ahead and check out…

Here’s the original article about Ubuntu and the newly released Ubuntu 9 for both desktop and Server:

Tech Blog – Canonical has announced the released of Ubuntu 9 Desktop Edition, today you can download Ubuntu 9 Jaunty Jackalope for free here support, also released simultaneously with Ubuntu 9 desktop was Ubuntu 9.04 Server Edition and Ubuntu 9.04 Netbook Remix (UNR).

According to Canonical’s press conference Ubuntu 9.04 Desktop Edition delivers a range of feature enhancements to improve the user experience, like Shorter boot speeds which would ensure faster access to computing environment, Enhanced suspend-and-resume features, Intelligent switching between Wi-Fi and 3G environments, and more wireless devices and 3G cards, so check out the new Ubuntu 9 and experience Linux power.

Hope the search engine (powered by Linux, apprently) understands this post and index this one as soon as possible.