Plain and simple of how to extend a volumn group in RHEL

Amusing you already added a Virtual disk and its presented to the server . If not check my this post.

[root@aurhel05 ~]# fdisk /dev/sdb

The number of cylinders for this disk is set to 3916.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/sdb: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System

Command (m for help): n
Command action
e   extended
p   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-3916, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-3916, default 3916):
Using default value 3916

Command (m for help): p

Disk /dev/sdb: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        3916    31455238+  83  Linux

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.
[root@aurhel05 ~]# fdisk -l

Disk /dev/sda: 32.2 GB, 32259548160 bytes
255 heads, 63 sectors/track, 3922 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         131     1052226   83  Linux
/dev/sda2             132         784     5245222+  83  Linux
/dev/sda3             785        1437     5245222+  83  Linux
/dev/sda4            1438        3918    19928632+   5  Extended
/dev/sda5            1438        1698     2096451   83  Linux
/dev/sda6            1699        1959     2096451   82  Linux swap / Solaris
/dev/sda7            1960        2220     2096451   82  Linux swap / Solaris
/dev/sda8            2221        2481     2096451   83  Linux
/dev/sda9            2482        2612     1052226   83  Linux
/dev/sda10           2613        3918    10490413+  83  Linux

Disk /dev/sdb: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        3916    31455238+  83  Linux

[root@aurhel05 ~]# mkfs.ext3 /dev/sdb1

mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
3932160 inodes, 7863809 blocks
393190 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
240 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 25 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

Extending the Volume VolGroup00-mysqldb by another 30GB :

1. Create a physical volume from a free disk or partition (e.g. /dev/sdb1 as a partition)
# pvcreate /dev/sdb1

2. Extend the volume group
# vgextend VolGroup00 /dev/sdb1

3. Extend the logical volume
# lvextend -L +30G /dev/mapper/VolGroup00-mysqldb

4. Extend an ext2/3/4 filesystem on the logical volume.
# resize2fs /dev/mapper/VolGroup00-mysqldb

 

Advertisements

parental-controls1

 

SquidGuard Configure

Posted: September 26, 2016 in Uncategorized

The best and easy way to install squidGuard is via YUM repo .Here how to do it .

1.With Squid working you can now go about installing SquidGuard.

You will need to install additional repositories in CentOS, in order to access to necessary software packages that are not available in the default repositories. Install the Extra Packages for Enterprise Linux (EPEL), the epel-release for the current version of Enterprise Linux (EL6). You can find it at the following website: http://fedoraproject.org/wiki/EPEL. A direct link to the RPM is in the command below. Eventually the link will be outdated and need to be replaced. For 64 bit systems you can change /i386/ to /x86_64/ in the command below.
# yum install http://ftp.osuosl.org/pub/fedora-epel/6/i386/epel-release-6-8.noarch.rpm

=========================================================================

[root@aueq-sproxy02 ~]# yum install http://ftp.osuosl.org/pub/fedora-epel/6/i386/epel-release-6-8.noarch.rpm
Loaded plugins: product-id, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Setting up Install Process
Examining /var/tmp/yum-root-8mVrB3/epel-release-6-8.noarch.rpm: epel-release-6-8.noarch
Marking /var/tmp/yum-root-8mVrB3/epel-release-6-8.noarch.rpm to be installed
Resolving Dependencies
–> Running transaction check
—> Package epel-release.noarch 0:6-8 will be installed
–> Finished Dependency Resolution

Dependencies Resolved

===============================================================================================================================================================================================================
Package Arch Version Repository Size
===============================================================================================================================================================================================================
Installing:
epel-release noarch 6-8 /epel-release-6-8.noarch 22 k

Transaction Summary
===============================================================================================================================================================================================================
Install 1 Package(s)

Total size: 22 k
Installed size: 22 k
Is this ok [y/N]:

 

==========================================================================

Now install SquidGuard.

# yum install squidGuard

 

[root@aueq-sproxy02 ~]# yum install squidGuard
Loaded plugins: product-id, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Setting up Install Process
epel/metalink | 2.8 kB 00:00
epel | 4.3 kB 00:00
epel/primary_db | 5.9 MB 00:00
Resolving Dependencies
–> Running transaction check
—> Package squidGuard.x86_64 0:1.4-10.el6 will be installed
–> Finished Dependency Resolution

Dependencies Resolved

===============================================================================================================================================================================================================
Package Arch Version Repository Size
===============================================================================================================================================================================================================
Installing:
squidGuard x86_64 1.4-10.el6 epel 7.1 M

Transaction Summary
===============================================================================================================================================================================================================
Install 1 Package(s)

Total download size: 7.1 M
Installed size: 7.4 M
Is this ok [y/N]:

 

2. cd /var/squidGuard/

tar -zxvf blacklists.tar.gz

mkdir db

mkdir log

chown -R squid:squid db
chown -R squid:squid log

mv blacklists/* db/

chown -R squid:squid db/*

3. Now edit the squidGuard.conf file to configure it to work with the testdomains file. You may want to back up the squidGuard.conf file before making changes.

 

[root@aueq-sproxy02 db]# cp /etc/squid/squidGuard.conf /etc/squid/squidGuard.conf.BAK

 

# vi /etc/squid/squidGuard.conf —> and change as following.

 

=============================================================

# Mohammad Alam 23/09/2016
# initial conf file for squidGuard

logdir /var/squidGuard/log
dbhome /var/squidGuard/db

dest whitelist {
domainlist whitelist/domains
urllist whitelist/urls
}

dest specBlacklist {
domainlist specBlacklist/domains
urllist specBlacklist/urls
}

dest ads {
domainlist ads/domains
urllist ads/urls
}

dest adult {
domainlist adult/domains
urllist adult/urls
}

dest aggressive {
domainlist aggressive/domains
urllist aggressive/urls
}

acl {
default {
pass whitelist !specBlacklist !ads !adult !aggressive !audio-video !drugs !porn !chat !warez !phishing !malware !in-addr all
redirect http://10.80.0.37/ERR_ACCESS_DENIED.html
}
}

 

==================================================================

 

4. Add this line to /etc/squid/squid.conf

url_rewrite_program /usr/bin/squidGuard -c /etc/squid/squidGuard.conf

5. Reload squidGuard db

squidGuard -b -d -C all

6. Restart Squid.

/etc/init.d/squid reload

7. Check the log file at /var/squidGuard/log

[root@aueq-sproxy02 log]# ls
squidGuard.log
[root@aueq-sproxy02 log]# tail -f squidGuard.log
2016-09-26 11:11:51 [2388] squidGuard 1.4 started (1474852311.153)
2016-09-26 11:11:51 [2388] squidGuard ready for requests (1474852311.167)
2016-09-26 11:11:51 [2389] squidGuard 1.4 started (1474852311.160)
2016-09-26 11:11:51 [2389] squidGuard ready for requests (1474852311.171)

 

 

 

 

 

 

 

 

 

 


Problem :

I experience this snapshot error with VEEAM backup and replication. For both  the error ,one single solution worked for me .

Error :

1) Consolidating virtual machine snapshots fails with the error: Change tracking target file already exists 

or

2) Creating Snapshot failed : The virtual disk is either corrupted or not a supported format.

 

Resolution :

To resolve this issue, the CBT files need to be moved out of the working folder of the affected virtual machine(s).

To move the CBT files and consolidate snapshots:
  1. Connect to the ESXi host that the virtual machine is running on using SSH.
  2. Navigate to the virtual machine folder using this command:

    cd /vmfs/volumes/datastore/virtual_machine/

  3. List the contents of the directory using the ls command and look for .ctk files.
  4. Create a temporary directory for the CBT files.

    For example:

    mkdir tmp

  5. Move the CBT files to this directory with this command:

    mv *-ctk.vmdk tmp/

  6. Run the snapshot  again.

Squirelmail Inbox error

Posted: February 24, 2016 in Redhat, Uncategorized

Problem:

After signing in , I was getting the following error for one of the inbox ..

ERROR: Could not complete request.
Query: SELECT “INBOX”
Reason Given: Internal error occured. Refer to server log for more information. [2016-02-21 13:25:45]

 

Solution :

  • Was checking the /var/log/maillog and got the following information –>  [Feb 24 16:05:18 griffin imap(appts.XXX): File isn’t in mbox format: /var/mail/appts.XXX]
  • Then open the file with any text editor like vi /var/mail/appts.XXX
    then Delete the garbage lines(one or two) at the beginning and save the file.

    Restart the service and everything shloud be OK now.

Canot Start Sendmail

Posted: March 17, 2015 in Redhat
Tags:

While trying to start sendmail it complains with the following error.

[root@augs-suatacd mail]# /etc/init.d/sendmail restart

Shutting down sm-client: [FAILED]
Shutting down sendmail: [FAILED]
Starting sendmail: 451 4.0.0 /etc/mail/sendmail.cf: line 87: fileclass: cannot open ‘/etc/mail/local-host-names’: World writable directory
451 4.0.0 /etc/mail/sendmail.cf: line 596: fileclass: cannot open ‘/etc/mail/trusted-users’: World writable directory
[FAILED]
Starting sm-client: /etc/mail/submit.cf: line 552: fileclass: cannot open ‘/etc/mail/trusted-users’: World writable directory
[FAILED]

Solution : 

Replacing line Fw/etc/mail/ local-host-names with line Fw-o /etc/mail/local-host-names in sendmail.cf, and Ft/etc/mail/trusted-users with line Ft-o /etc/mail/trusted-users in submit.cf and sendmail.cf.

Then restart Sendmail . Hope it will work.

Ashraf

Canot SCP to Checkpoint firewall

Posted: February 20, 2014 in CheckPoint

When you SCP to Checkpoint SPLAT firewall and get the error “lost connection”, this is what you may see

To resolve this do the following

1. make sure the admin shell has been changed from /bin/cpshell to /bin/bash

chsh admin
Changing shell for admin.
New shell [/bin/cpshell]: /bin/bash
Shell changed.

2. create a new file “touch /etc/scpusers”

3. edit the file and add the users you want to allow for scp

example:
more /etc/scpusers
admin

4. restart the ssh service ( I did not have to restart and it just worked)

service sshd restart