Debian/Ubuntu

Use which to find the location of the binary, then the dpkg –S to find the package. Finally you can use the lower case “-s” option to get detailed information about the package.

root@danny-Aspire-one:/# which zmu
/usr/bin/zmu
root@danny-Aspire-one:/# dpkg -S /usr/bin/zmu
zoneminder: /usr/bin/zmu
root@danny-Aspire-one:/# dpkg -s zoneminder

RedHat/SUSE

suse11:~ # which hwinfo
/usr/sbin/hwinfo
suse11:~ # rpm -qf /usr/sbin/hwinfo
hwinfo-15.33-0.2.19
suse11:~ # rpm -qi hwinfo

Solaris

$pkg check –l –p /usr/bin/ssh

Source: Find Which Package Owns A File on Setup Tips - Tips on setting up gadgets and software

The most authoritative source of documentation on Linux Bonding is at Kernel.org.  I have summarized some points from the document and added some of my own comments from my own experiences with examples below.  I will add links to detailed worked examples of bonding configuration for the various distributions of Linux in the future.

History Of Linux Bonding Driver

Linux bonding was originally part of the beowulf cluster patches for Linux 2.0 by Donald Becker, but it has changed much since then. Donald was also one of the original developers of the Ethernet drivers for Linux. Most distributions of Linux come with the bonding driver already available as a module.

Is Bonding Supported By My Operating System?

It is a simple check to see if the bonding driver is available in your operating system.

[root@redhat6 ~]# modprobe -l bonding
kernel/drivers/net/bonding/bonding.ko

Does My NIC Support Bonding?

The next question is does my NIC support bonding?  Yes all cards can support bonding, but NOT all cards support all of the schemes Linux Bonding has available for monitoring the network link health.  However, as we will see this is not a big issue.

MII Monitor (miimon)

Most network cards today implement the Media Independent Interface (MII) standard. Part of the standard defines use of the MII Status Word register which can be used to detect if an Ethernet NIC is connected to the network or not – of particular interest is the “0×0004 Link established” state.

The MII monitor (miimon) simply queries the state of this register (netif_carrier = 1) to determine the health of the network link.

It can also be configured to use ethtool as a last resort in attempting to obtain the same information (netif_carrier=0). So don’t worry if your card does not support MII.

There are two ways to test if your NIC supports MII

[root@redhat6 ~]# mii-tool
SIOCGMIIPHY on 'eth0' failed: Operation not supported
SIOCGMIIPHY on 'eth1' failed: Operation not supported
eth2: negotiated 100baseTx-FD, link ok
eth3: negotiated 100baseTx-FD, link ok

In the above example eth0 and eth1 do not support MII but eth2 and eth3 do.

If you operating system does not include mii-tool (SuSE) then you can use ethtool.

NOTE: Interestingly at the writing of this report SuSE does not include mii-tool in the net-tools package and is unlikely to ever do so in the future  due to the following statement in the net-tools release note:

*Wed Dec 08 2004 -
- Include linux/sockios.h to get the right ioctl [#48873]. This bug
is in mii-tool which is not included anymore, but better not risk
ever re-adding buggy stuff.

Here is how to use ethtool to determine if your NIC supports MII.  Just grep for the string “Current message level:”. If it appears in the ethtool output then MII is supported by your card. In the example below only eth2 and eth3 support MII.

[root@redhat6 ~]# ethtool eth0 | grep "Current message level:"
[root@redhat6 ~]# ethtool eth1 | grep "Current message level:"
[root@redhat6 ~]# ethtool eth2 | grep "Current message level:"
        Current message level: 0x00000007 (7)
[root@redhat6 ~]# ethtool eth3 | grep "Current message level:"
        Current message level: 0x00000007 (7)

ARP Monitor

Don’t worry if your NIC cards do not support MII. Most people wrongly assume that miimon is the superior monitor. But remember miimon only checks the local NIC link status. It has no way to establish the health of devices beyond it, such as the health of the switch or of the switch up port.  The ARP Monitor on the other hand can do this.

The ARP monitor sends ARP queries to one or more configured IP addresses on the network and uses the response back to indicate if the link is working. A good choice for these configured IP addresses are the routers at the other end of the switches.

NOTE: It’s good practice to define more then one IP address to monitor, especially in high availability environments.

In the example above (from my ESXi hypervisor test environment) for vSwitch1 the uplink vmnic1 is down (I just pulled the cable from my ESXi host) but all the virtual switch ports are still active – and ethtool and mii-tool report the links as still active. I have tested miimod monitoring with this configuration and it just will not work. However, ARP monitoring works perfectly.

NOTE: It should be noted that some switches can fail ports in response to general switch failures in which case miimod monitoring would work fine.

Bonding Manual Failover

You can perform manual failover of your active bonded slave for the active-backup mode of bonding.

You can determine the state of your bonding driver from the /proc  pseudo-file system.

[root@redhat6 ~]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.5.0 (November 4, 2008)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth2
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
ARP Polling Interval (ms): 1000
ARP IP target/s (n.n.n.n form): 192.168.1.1

Slave Interface: eth2
MII Status: up
Link Failure Count: 5
Permanent HW addr: 00:0c:29:f1:d9:a5

Slave Interface: eth3
MII Status: down
Link Failure Count: 303
Permanent HW addr: 00:0c:29:f1:d9:af

You can also use the  ifenslave to change which interface is active.

[root@redhat6 ~]# cat /proc/net/bonding/bond0 | grep eth2
Currently Active Slave: eth2
Slave Interface: eth2
[root@redhat6 ~]# ifenslave --change-active bond0 eth3
Master 'bond0', Slave 'eth3': Error: Change active failed

In the above example eth3 was down so the bonding driver prevented me failing over to it. After I plugged it back in and could see in /var/adm/messages that it’s link status was up again.

Mar 14 14:13:28 redhat6 kernel: bonding: bond0: link status definitely up for interface eth3.

Now the manual failover works!

[root@redhat6 ~]# ifenslave --change-active bond0 eth3
[root@redhat6 ~]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.5.0 (November 4, 2008)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth3
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
ARP Polling Interval (ms): 1000
ARP IP target/s (n.n.n.n form): 192.168.1.1

Slave Interface: eth2
MII Status: up
Link Failure Count: 5
Permanent HW addr: 00:0c:29:f1:d9:a5

Slave Interface: eth3
MII Status: up
Link Failure Count: 304
Permanent HW addr: 00:0c:29:f1:d9:af

Source: Linux Bonding | Channel Bonding | Ethernet Bonding | NIC Bonding on Setup Tips - Tips on setting up gadgets and software

It did get recognized at the PCI level, so the hardware is fine. It looks like my network card is just way too old to be supported anymore.

/var/log # lspci | grep "Ethernet"
000:004:00.0 Network controller: Marvell Technologies, Inc. 88E8053 PCI-E Gigabit Ethernet Controller [vmnic0]
000:006:00.1 Network controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme]
000:006:01.1 Network controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme]
000:006:02.1 Network controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme]
000:006:03.1 Network controller: Sun Microsystems Computer Corp. Happy Meal 10/100 Ethernet [hme]
/var/log #

UPDATE:

After reading a couple of blog posts I noticed that the RTL-8169 Ethernet card is supported in ESX 5.  So I purchased a very cheap Chinese import for about $10 US  (see the picture on the left). Big mistake!  It took me a whole afternoon to eventually determine that the card was broken.

#lspci | grep "Network controller:"
000:004:00.0 Network controller: Marvell Technologies, Inc. 88E8053 PCI-E Gigabit Ethernet Controller [vmnic0]
000:005:01.0 Network controller:

The above shows, that it was recognized by VMWARE as a Network controller at least, but VMWARE did not know the vendor.  So as a first step I decided to verify the specific vendor codes returned by my new network card..

#lspci -p
000:004:00.0 11ab:4362 15bd:1102  5/  5/0xc8 A V sky2         vmnic0
000:005:01.0 00ec:8169 00ec:8169  9/  9/0xb0 A V

Next, I looked at the file /usr/share/hwdata/pci.ids. Surprise, surprise!  Realtek’s vendor code is 10ec not 00ec. The card is broken.

/usr/share/hwdata/pci.ids
11ab  Marvell Technology Group Ltd.
        4362  88E8053 PCI-E Gigabit Ethernet Controller
               15bd 1003  Marvell 88E8053 Gigabit Ethernet Controller (DFI)

10ec  Realtek Semiconductor Co., Ltd.
       8169  RTL-8169 Gigabit Ethernet
               10bd 3202  EP-320G-TX1 32-bit PCI Gigabit Ethernet Adapter

I promptly, took the card back to the shop and got a replacement.

This time when I booted up my ESX host with the replacement I could see my new device on the console.

And now:

~ # lspci | grep "Ethernet"
000:004:00.0 Network controller: Marvell Technologies, Inc. 88E8053 PCI-E Gigabit Ethernet Controller [vmnic0]
000:005:01.0 Network controller: Realtek Realtek 8169 Gigabit Ethernet [vmnic1]

It’s ready to use.

~ # esxcfg-nics -l
Name    PCI           Driver      Link Speed     Duplex MAC Address       MTU    Description
vmnic0  0000:04:00.00 sky2        Up   1000Mbps  Full   00:01:29:a6:38:3f 1500   Marvell Technologies, Inc. 88E8053 PCI-E Gigabit Ethernet Controller
vmnic1  0000:05:01.00 r8169       Down 0Mbps     Half   00:a1:b0:8b:32:c2 1500   Realtek Realtek 8169 Gigabit Ethernet

Finally, let’s check the vendor codes.

~ # lspci -p | tail -2
000:004:00.0 11ab:4362 15bd:1102  5/  5/0xc8 A V sky2         vmnic0
000:005:01.0 10ec:8169 10ec:8169  9/  9/0xb0 A V r8169        vmnic1

That’s much better. Here is how they match up in /usr/share/hwdata/pci.ids:

10ec  Realtek Semiconductor Co., Ltd.
       8169  RTL-8169 Gigabit Ethernet

Meanwhile, back at the vSphere client GUI, all is good and at peace in the world as I can see my new card.

NOTE:

1. Here is how to install an ESX driver bundle if you card is not supported in the default installation.
2. Here is the /usr/share/hwdata/pci.ids file showing he list of recognized PCI cards in ESX 5.

Source: How To Add A New Network Adapter In VMware ESXi on Setup Tips - Tips on setting up gadgets and software

Boot into single user mode from grub

Ever encounter the dreaded Linux server that does not boot back up after a reboot?  Here is how to rescue a Linux server from the grub prompt or from a rescue disk and mount the file systems so you can at least determine what went wrong.

Method 1: Boot To Single User

You will need the root password for this method

Press ‘e’ when GRUB displays
Press ‘e’ again on kernel line
Add “single” to the end of the kernel line
Press ‘b’ to boot

Method 2: Use Rescue Mode

You will NOT need the root password for this method.

If you are using HP ILO or Dell DRAC then you can mount an ISO image of the boot disk as a virtual media CD rom.

Reset System and boot from CD Rom into rescue mode.

NOTE: Rescue mode does not do anything with LVM by default. So you will need to activate the volume groups.

#lvm vgscan
#lvm vgchange -ay
#lvm lvs
mount /dev/mapper/system-root /tmp/root
# now you can edit whatever you need to get your server running again. For example change the root password.

Source: How To Rescue Linux From The Grub Prompt on Setup Tips - Tips on setting up gadgets and software

I am not a big believer in root disk encapsulation with Veritas Volume Manager, now part of Symantec Storage Foundation. There have been a number of times when I have had to boot off the mirror disk, and had to completely de-encapsulate the mirror disk from Veritas Volume Manager to recover.

Here is how to do it with Solaris. It is pretty similar for Linux as well.

Firstly, lets boot off the mirror disk and disable Veritas Volume Manager from starting.

Executing last command: boot vx-rootmirror -a -s

Boot device: /pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a  File and args: -a -s

Enter filename [kernel/sparcv9/unix]:

Enter default directory for modules [/platform/FJSV,GPUZC-M/kernel /platform/sun4us/kernel /kernel /usr/kernel]:

Name of system file [etc/system]:  /dev/null

SunOS Release 5.10 Version Generic_127127-11 64-bit

Copyright 1983-2008 Sun Microsystems, Inc.  All rights reserved.

Use is subject to license terms.

root filesystem type [ufs]:

Enter physical name of root device

[/pci@83,4000/FJSV,ulsa@2,1/disk@0,0:a]:

Booting to milestone "milestone/single-user:default".

fjgi0:Using local MAC address

fjgi1:Using local MAC address

# example - in this case c0t0d0 corresponds to mirror disk

mount -F ufs -o remount,rw /dev/dsk/c0t0d0s0 /

/etc/system --- remove all vx lines

/etc/vfstab – go back to normal devices e.g. /dev/vx/c0t0d0 ..

# Now make sure Volume Manager does not start on the next boot:

touch /etc/vx/reconfig.d/state.d/install-db

# make sure you setup boot-device to boot of mirror from now on, very important for re-encapsulation step later

eeprom | grep dev

e.g. eeprom "boot-device=vx-rootmirror"

syc;sync;init 6

After the previous steps volume manager should not be running.

# vxdisk list

VxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible

Now, re-install Volume manager

bash-3.00# vxinstall

  VxVM uses license keys to control access.  If you have a SPARCstorage

  Array (SSA) controller or a Sun Enterprise Network Array (SENA) controller

  attached to your system, then VxVM will grant you a limited use license

  automatically.  The SSA and/or SENA license grants you unrestricted use

  of disks attached to an SSA or SENA controller, but disallows striping,

  RAID-5, and DMP on non-SSA and non-SENA disks.  If you are not running an

  SSA or SENA controller, then you must obtain a license key to operate.

  Licensing information:

    System host ID: 80f2a60a

    Host type: FJSV,GPUZC-M

    SPARCstorage Array or Sun Enterprise Network Array: No arrays found

Some licenses are already installed.  Do you wish to review them

[y,n,q,?] (default: y) Feb 23 22:16:56 ibsza3002 root[1501]: Starting agent n

Do you wish to enter another license key [y,n,q,?] (default: n)

Do you want to setup a system wide default disk group?

[y,n,q,?] (default: y) Feb 23 22:17:16 ibsza3002 syseventd[353]:

n

Do you want to use enclosure based names for all disks ?

[y,n,q,?] (default: n)

  The installation is successfully completed.

Check to see if Veritas can see your disks.

bash-3.00# vxdisk list

DEVICE       TYPE            DISK         GROUP        STATUS

c0t0d0s2     auto:sliced     -            -            online

c1t0d0s2     auto:sliced     -            -            online

Check to see if Veritas still thinks that it owns the disks.

vxdisk -o alldgs list

DEVICE       TYPE            DISK         GROUP        STATUS

c0t0d0s2     auto:sliced     -            (rootdg)     online

c1t0d0s2     auto:sliced     -            (rootdg)     online

If it does, make sure Veritas forgets about them completely.

bash-3.00# /etc/vx/bin/vxdiskunsetup -C c1t0d0

bash-3.00# /etc/vx/bin/vxdiskunsetup -C c0t0d0

Now follow the normal steps to re-encapsulate vx-rootmirror as your root disk and the other disk as your mirror disk.

Encapsulate root disk  (e.g. c0t0d0)

vxdiskadm – option 2

Mirror root disk to other disk (e.g. c1t0d0)

vxdiskadm – option 6

Source: Volume Manager Root Disk Encapsulation Recovery on Setup Tips - Tips on setting up gadgets and software

bash-3.00# dladm show-dev

e1000g0         link: up        speed: 1000  Mbps       duplex: full

e1000g1         link: unknown   speed: 0     Mbps       duplex: half

e1000g2         link: unknown   speed: 0     Mbps       duplex: half

e1000g3         link: unknown   speed: 0     Mbps       duplex: half

e1000g4         link: up        speed: 1000  Mbps       duplex: full

e1000g5         link: unknown   speed: 0     Mbps       duplex: half

Source: Check Network Speed In Solaris 10 on Setup Tips - Tips on setting up gadgets and software

1. Create a self-signed certificate.

Install ssl-cert if it is not already installed

root@ns2:/tmp# aptitude install ssl-cert

NOTE: VPS.NET now require 2048 bit certificates. So, edit ssleay.cnf from1024 bits to 2048 bits.

root@ns2:/tmp# cat /usr/share/ssl-cert/ssleay.cnf

#

# SSLeay example configuration file.

#

RANDFILE                = /dev/urandom

[ req ]

default_bits            = 2048

Now create a self-signed certificate for your web server domain. It will prompt you for your server Host Name. For the example below it would be your web server domain. We use  mydomain.com as an example throughout this guide.

root@ns1:/tmp# make-ssl-cert /usr/share/ssl-cert/ssleay.cnf /etc/ssl/private/mydomain.com.crt

After running this command you will end up with your private key and self-signed certificate in the same file – mydomain.com.crt. You must split this into two separate files using an editor.

/etc/ssl/private/domain.com.key   // the part surrounded by —– BEGIN/END RSA PRIVATE KEY

/etc/ssl/private/domain.com.pem // the part surrounded by —– BEGIN/END CERTIFICATE

2. Create a Certificate Signing Request (CSR)

VPS.NET use Comodo as a trusted Certificate Authority (CA). You need to generate a certificate signing request (CSR) from the private key created in the previous step and send it to the VPS.NET help desk. They will in turn forward your request to the Comodo Certificate Authority.

Here is the example for the domain mydomain.com.

NOTE: The important thing is to use your domain name for the Common Name when prompted.

root@ns1:/tmp# openssl req -new -key /etc/ssl/private/mydomain.com.crt -out /etc/ssl/private/mydomain.com.csr

You are about to be asked to enter information that will be incorporated

into your certificate request.

What you are about to enter is what is called a Distinguished Name or a DN.

There are quite a few fields but you can leave some blank

For some fields there will be a default value,

If you enter '.', the field will be left blank.

-----

Country Name (2 letter code) [AU]:US

State or Province Name (full name) [Some-State]:Florida

Locality Name (eg, city) []:Burlington

Organization Name (eg, company) [Internet Widgits Pty Ltd]:My Company Name

Organizational Unit Name (eg, section) []:IT

Common Name (eg, YOUR name) []:mydomain.com

Email Address []:admin@mydomain.com

Please enter the following 'extra' attributes

to be sent with your certificate request

A challenge password []:enter

An optional company name []:enter

3. Raise a VPS.NET Domain Name/SSL Support Ticket

The next step is to raise a “Domain Name/SSL Request” support ticket.

Make sure you include the following information in the Message part of the ticket  and also append the contents of the /etc/ssl/private/mydomain.com.csr file you created.

* Your Name: - Joe Blogs 

* Your Company: - mydomain.com 

* Contact Email address: admin@mydomain.com 

* Address 1: - 1 smith street 

* Address 2: -  

* Town: - BURLINGTON 

* County/Province: - FLORIDA 

* Postcode: - 12334 

* Country: - US

ip address: 174.127.111.29 

host: mydomain.com

Signing Request (CSR)

-----BEGIN CERTIFICATE REQUEST----- 

MIIB+DCCAWECAQAwgYMxCzAJBgNVBAYTAkhLMQswCQYDVQQIEwJOVDESMBAGA1UE

BxMJSG9uZyBLb25nMRIwEAYDVQQKEwlwbHNnby5jb20xCzAJBgNVBAsTAklUMRIw

EAYDVQQDE..

...

...

-----END CERTIFICATE REQUEST-----

It only takes VPS.NET support an hour or so to order a certificate from Comodo. You will get a response like this from VPS.NET support.

I have created new SSL certificate for you. 

You will be emailed when your certificate is available to download. 

Certificate for: mydomain.com 

Your order number is: 38383838

Please look out for a confirmation email to admin@mydomain.com 

- you'll need to follow the instructions in the email to verify that the domain is yours. 

Once you have followed the instructions in your confirmation mail, 

you will be able to download your certificate by going to the retrieve certificate page 

(https://ssl.uk2.net/cgi-bin/retrieve-certificate.pl) 

and entering the hostname and order number above. 

Thanks. 

-- 

Best regards, 

-- 

x smith 

Support Engineer 

After you get this response, go and check your email. Comodo will have also sent you an email verification email. Ensure that you open and accept the link they send.

From: Comodo Security Services <docs@comodo.com>

Date: Sat, Nov 26, 2011 at 4:58 PM

Subject: ORDER #38383838 - Domain Control Validation for mydomain.com

To: "admin@mydomain.com" <admin@mydomain.com>

Domain Control Validation for mydomain.com

Dear admin@mydomain.com,

We have received a request to issue an SSL certificate for mydomain.com.

*** Please ignore this email if neither you nor a trusted colleague made this request for a certificate ***

Otherwise, please browse here and enter the following "validation code":

vCqBZKIkejje838jfj2ldlfe838j33jjd833O0a

Kind Regards,

Comodo Security Services on behalf of uk2.net

Finally go to (https://ssl.uk2.net/cgi-bin/retrieve-certificate.pl) and fill in the requested fields. You will then be able to download a zip file containing your certificates.

4. Install The Certificates On Your Server

FTP the zip file you downloaded  to your server and then unzip the contents to a temporary directory on your server.

root@ns2:/tmp# ls

mydomain.com-certificate.zip

root@ns2:/tmp# unzip mydomain.com-certificate.zip

Archive:  mydomain.com-certificate.zip

 extracting: AddTrustExternalCARoot.crt

 extracting: UTNAddTrustServerCA.crt

 extracting: PositiveSSLCA.crt

 extracting: mydomain_com.crt

Next copy in your original key and the mydomain_com.crt certificate you unzipped

root@ns2:/tmp# cp mydomain_com.crt /etc/ssl/localcerts/mydomain.com.pem

root@ns2:/tmp# cp /etc/ssl/private/mydomain.com.key /etc/ssl/localcerts/

You will also need to add the comodo certificate chain bundle to your webserver configuration. This file is created by combining the other certificates you were given in the zip file. There are some notes on comodo support on how to make your certificate chain bundle, but here is the basic step.

root@ns2:/tmp# cat PositiveSSLCA.crt UTNAddTrustServerCA.crt AddTrustExternalCARoot.crt > mydomain.com.ca-bundle

Finally we need to ensure our apache webserver configuration is setup correctly to point to the new certificates.

vi /etc/apache2/sites-available/mydomain.com

<VirtualHost *:443>

    ServerName mydomain.com

    ....

    ....

    SSLEngine on

    SSLCertificateFile        /etc/ssl/localcerts/mydomain.com.pem

    SSLCertificateKeyFile     /etc/ssl/localcerts/mydomain.com.key

    SSLCertificateChainFile   /etc/ssl/localcerts/mydomain.com.ca-bundle

As a final step restart apache.

5. Check Your Certificate Installation

If your certificate install did not work you will still be presented with an untrusted certificate warning when you browse to the secure address of your domain

i.e. https : //www. mydomain. com

If everything worked fine. Then you will no longer see any warning messages.

You can also verify the certificate information in your browser by right clicking the web page and selecting view page info.

Source: VPS.NET SSL Certificate Installation On Ubuntu on Setup Tips - Tips on setting up gadgets and software

To change it to vim use the select-editor command

root@ns1:/etc# select-editor

Select an editor.  To change later, run 'select-editor'.

  1. /bin/nano        <---- easiest

  2. /usr/bin/vim.basic

  3. /usr/bin/vim.tiny

Choose 1-3 [1]: 2

Source: Setting Ubuntu Default Crontab Editor on Setup Tips - Tips on setting up gadgets and software

Memcached on Ubuntu has actually two components. A standalone program running on your server and a  client PHP extension. To be honest I noticed no increase in performance using memcached with the W3 Total Cache plugin.

root@ns1:~# aptitude install memcached

The following NEW packages will be installed:

  memcached

First we need to install the PEAR framework. This is a distribution system for handling reusable PHP components.

root@ns1:~# aptitude install php-pear

The following NEW packages will be installed:

  php-pear php5-cli{a}

Now we can install the PHP component using PEAR.  Type YES to all options prompted.

root@ns1:~# pecl install memcache

...

Installing '/usr/lib/php5/20090626/memcache.so'

install ok: channel://pecl.php.net/memcache-2.2.6

configuration option "php_ini" is not set to php.ini location

You should add "extension=memcache.so" to php.ini

root@ns1:/etc/php5/fpm/conf.d# cat /etc/php5/fpm/conf.d/memcache.ini

; uncomment the next line to enable the module

extension=memcache.so

[memcache]

memcache.dbpath="/var/lib/memcache"

memcache.maxreclevel=0

memcache.maxfiles=0

memcache.archivememlim=0

memcache.maxfilesize=0

memcache.maxratio=0

Now let’s verify

root@ns1:/etc/php5/fpm/conf.d# pgrep -fl memcached

27823 /usr/bin/memcached -m 64 -p 11211 -u memcache -l 127.0.0.1

root@ns1:/etc/php5/fpm/conf.d# netstat -an | grep 11211

tcp        0      0 127.0.0.1:11211         0.0.0.0:*               LISTEN

udp        0      0 127.0.0.1:11211         0.0.0.0:*

Configuration Files

/etc/memcached.conf

- you can increase the amount of memory in the memcache pool in this file. The default is 64M, which should be sufficient.

Log Files

/var/log/memcached.log

Source: Install Memcached on Ubuntu on Setup Tips - Tips on setting up gadgets and software

To find you iPhone serial number go to  Settings->General->Serial Number.

Source: Check iPhone Warranty Online on Setup Tips - Tips on setting up gadgets and software