1) Once we were in live session, we opened a terminal and ran
[root]# fdisk -l
This lists out the partition table of the system and it looked something like this
Device Boot Start End Blocks Id System
/dev/sda1 * 1 4864 39070048+ 7 HPFS/NTFS
/dev/sda2 4865 6691 14675377+ 83 LVM2_member
...
2) The good news was that the system was at least able to distinguish the partitions. So, in order to backup the data, the next step was to access the /dev/sda2 partition. But since it is an lvm partition we will had to take some additional steps to mount it.
Now, run the pvs command. Please note that while in live session you may find that this is not installed by default. In order to install the required tools, run the following command.
[shredder12]$ sudo apt-get install lvm2
Of course, you should be connected to internet. Once you are done with this run pvs.
[root]# pvs
This will list the volume groups to which our physical volume /dev/sda2 belonged. It would be of the form
PV VG Fmt Attr PSize PFree
/dev/hda2 VolGroup01 lvm2 a- 148.94G 32.00M
The second field, VG, shows the Volume group. The above output is just an example, showing that we are concerned with the Volume group "VolGroup01". The next step is to list the information about this volume group.
[root]# lvdisplay /dev/VolGroup01
It will throw a bunch of ouput, but the one we are concerned with is LV Name. It will look something like this
LV Name /dev/VolGroup01/LogVol00
In our case, there were two entries of type LV Name, the other being LogVol01, the swap. The whole output along with it will help you to identify the target logical volume you are looking for. Assuming that the above one is the partition that we need to mount, just use the usual method to mount it.
[root]# mount /dev/VolGroup01/LogVol00 /mnt
Now, you can to find the data you were looking for in the /mnt folder.
NameVirtualHost Public IP Address:80
ServerName www.websitename.com
ServerAlias websitename.com
DocumentRoot /var/www/
Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED
Options +FollowSymlinks
RewriteEngine on
Order deny,allow
Allow from all
BalancerMember http://Local IP Address route=node1
BalancerMember http://Local IP Address route=node2
ProxySet stickysession=ROUTEID
ProxySet lbmethod=byrequests
ProxyPass /balancer-manager !
ProxyPass / balancer://mycluster/
ProxyPassReverse / http://Local IP Address/
ProxyPassReverse / http://Local IP Address/
SetHandler balancer-manager
Options FollowSymLinks
Order deny,allow
Allow from all
ErrorLog logs/sitename_error
CustomLog logs/sitename_custom "%t Time=%D %h LocalIP=%A FileName=%f FirstLineOfReq=%r RequestedURLWOQueryString=%U CanonicalServerName=%v Referrer=\"%{Referer}i\" Node=%{ROUTEID}C Worker=\"%{BALANCER_WORKER_NAME}e\""
ServerName www.Subdomain.websitename.com
ServerAlias subdomain.websitename.com
DocumentRoot /var/www/
Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED
Options +FollowSymlinks
RewriteEngine on
Order deny,allow
Allow from all
BalancerMember http://Local IP Address/advertiser route=node1
BalancerMember http://Local IP Address/advertiser route=node2
ProxySet stickysession=ROUTEID
ProxySet lbmethod=byrequests
ProxyPass /balancer-manager !
ProxyPass / balancer://mycluster/
ProxyPassReverse / http://Local IP Address/advertiser/
ProxyPassReverse / http://Local IP Address/advertiser/
SetHandler balancer-manager
Options FollowSymLinks
Order deny,allow
Allow from all
ErrorLog logs/sitename_error
#CustomLog logs/sitename_custom "%t %T %h %A %r %f %U %{ROUTEID}C %v %V %>s %b \"%{Referer}i\" \"%{BALANCER_WORKER_NAME}e\""
CustomLog logs/sitename_custom "%t Time=%D %h LocalIP=%A FileName=%f FirstLineOfReq=%r RequestedURLWOQueryString=%U CanonicalServerName=%v Referrer=\"%{Referer}i\" Node=%{ROUTEID}C Worker=\"%{BALANCER_WORKER_NAME}e\""
ServerName www.subdomain.websitename.com
ServerAlias subdomain.websitename.com
DocumentRoot /var/www/
Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED
Order deny,allow
Allow from all
BalancerMember http://Local IP Address/corporate route=node1
BalancerMember http://Local IP Address/corporate route=node2
ProxySet stickysession=ROUTEID
ProxySet lbmethod=byrequests
ProxyPass /balancer-manager !
ProxyPass / balancer://mycluster/
ProxyPassReverse / http://Local IP Address/corporate/
ProxyPassReverse / http://Local IP Address/corporate/
SetHandler balancer-manager
Order deny,allow
Allow from all
ErrorLog logs/sitename_error
#CustomLog logs/sitename_custom "%t %T %h %A %r %f %U %{ROUTEID}C %v %V %>s %b \"%{Referer}i\" \"%{BALANCER_WORKER_NAME}e\""
CustomLog logs/sitename_custom "%t Time=%D %h LocalIP=%A FileName=%f FirstLineOfReq=%r RequestedURLWOQueryString=%U CanonicalServerName=%v Referrer=\"%{Referer}i\" Node=%{ROUTEID}C Worker=\"%{BALANCER_WORKER_NAME}e\""
ServerName www.websitename.com
ServerAlias websitename.com
DocumentRoot /var/www/
Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED
Options +FollowSymlinks
RewriteEngine on
Order deny,allow
Allow from all
BalancerMember http://Local IP Address route=node1
BalancerMember http://Local IP Address route=node2
ProxySet stickysession=ROUTEID
ProxySet lbmethod=byrequests
ProxyPass /balancer-manager !
ProxyPass / balancer://mycluster/
ProxyPassReverse / http://Local IP Address/
ProxyPassReverse / http://Local IP Address/
SetHandler balancer-manager
Options FollowSymLinks
Order deny,allow
Allow from all
ErrorLog logs/sitename_error
CustomLog logs/sitename_custom "%t Time=%D %h LocalIP=%A FileName=%f FirstLineOfReq=%r RequestedURLWOQueryString=%U CanonicalServerName=%v Referrer=\"%{Referer}i\" Node=%{ROUTEID}C Worker=\"%{BALANCER_WORKER_NAME}e\""
ServerName www.Subdomain.websitename.com
ServerAlias subdomain.websitename.com
DocumentRoot /var/www/
Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED
Options +FollowSymlinks
RewriteEngine on
Order deny,allow
Allow from all
BalancerMember http://Local IP Address/advertiser route=node1
BalancerMember http://Local IP Address/advertiser route=node2
ProxySet stickysession=ROUTEID
ProxySet lbmethod=byrequests
ProxyPass /balancer-manager !
ProxyPass / balancer://mycluster/
ProxyPassReverse / http://Local IP Address/advertiser/
ProxyPassReverse / http://Local IP Address/advertiser/
SetHandler balancer-manager
Options FollowSymLinks
Order deny,allow
Allow from all
ErrorLog logs/sitename_error
#CustomLog logs/sitename_custom "%t %T %h %A %r %f %U %{ROUTEID}C %v %V %>s %b \"%{Referer}i\" \"%{BALANCER_WORKER_NAME}e\""
CustomLog logs/sitename_custom "%t Time=%D %h LocalIP=%A FileName=%f FirstLineOfReq=%r RequestedURLWOQueryString=%U CanonicalServerName=%v Referrer=\"%{Referer}i\" Node=%{ROUTEID}C Worker=\"%{BALANCER_WORKER_NAME}e\""
ServerName www.subdomain.websitename.com
ServerAlias subdomain.websitename.com
DocumentRoot /var/www/
Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED
Order deny,allow
Allow from all
BalancerMember http://Local IP Address/corporate route=node1
BalancerMember http://Local IP Address/corporate route=node2
ProxySet stickysession=ROUTEID
ProxySet lbmethod=byrequests
ProxyPass /balancer-manager !
ProxyPass / balancer://mycluster/
ProxyPassReverse / http://Local IP Address/corporate/
ProxyPassReverse / http://Local IP Address/corporate/
SetHandler balancer-manager
Order deny,allow
Allow from all
ErrorLog logs/sitename_error
#CustomLog logs/sitename_custom "%t %T %h %A %r %f %U %{ROUTEID}C %v %V %>s %b \"%{Referer}i\" \"%{BALANCER_WORKER_NAME}e\""
CustomLog logs/sitename_custom "%t Time=%D %h LocalIP=%A FileName=%f FirstLineOfReq=%r RequestedURLWOQueryString=%U CanonicalServerName=%v Referrer=\"%{Referer}i\" Node=%{ROUTEID}C Worker=\"%{BALANCER_WORKER_NAME}e\""
http://www.swiftcore.com/en/software/upgrade-php-52x-plesk-default-php-51x.html
Upgrade PHP to 5.2.x from Plesk default PHP 5.1.x
July 31, 2009 - 5:09pm — Yuan Quan
By default Plesk installation, the PHP version is 5.1.x, if you want to upgrade it to 5.2 or even 5.3, please follow these steps:
Login via SSH as root user first.
Upgrading PHP:
wget -q -O - http://www.atomicorp.com/installers/atomic.sh | sh
yum update php
Upgrade PHP to 5.2.x from Plesk default PHP 5.1.x
July 31, 2009 - 5:09pm — Yuan Quan
By default Plesk installation, the PHP version is 5.1.x, if you want to upgrade it to 5.2 or even 5.3, please follow these steps:
Login via SSH as root user first.
Upgrading PHP:
wget -q -O - http://www.atomicorp.com/installers/atomic.sh | sh
yum update php
How to Create a Shared Folder to Store Roaming User Profiles
Before you configure a user account to use a roaming user profile, you must create a shared folder on a Windows NT Server 4.0-based computer in the domain to store the roaming user profiles. This shared folder is often located on a domain controller, but it can also be located on any Windows NT Server 4.0-based computer in the domain.
To create a shared folder to store roaming user profiles:
1. Click Start, point to Programs, and then click Windows NT Explorer.
2. Click the drive on which you want to create a shared folder to store roaming user profiles.
3. On the File menu, point to New, and then click Folder.
4. Type a name for the new folder, and then press ENTER.
NOTE: Typically, the folder that is used to store roaming user profiles is called "Profiles". However, you can assign any name that you want to the folder.
5. Right-click the folder you created in step 3, and then click Sharing.
6. Click Shared As, type the name that you want to assign to the shared folder in the Share Name box, and then click OK.
NOTE: The Profiles folder is commonly shared as "Profiles."
7. Quit Windows NT Explorer.
Back to the top
How to Configure a User Account to Use a Roaming User Profile in a Windows-Based Domain
To configure user accounts in the domain, you can use any Windows NT Server 4.0, Windows 2000 Server, or Windows Server 2003-based computer in the domain or any Windows NT Workstation 4.0, Windows XP Professional, or Windows 2000 Professional-based computer that is running Windows NT Server Administration Tools in the domain. In addition, you must be logged on as either an administrator or as a user that is a member of the Administrators local group or the Account Operators local group in the domain.
To configure a user account to use a roaming user profile:
1. Click Start, point to Programs, point to Administrative Tools (Common), and then click User Manager for Domains or Active Directory Users and Computers for Windows Server 2000 or for Windows Server 2003.
2. Double-click the user account to which you want to assign a roaming profile, and then click Profile.
3. Type the complete path to the shared folder that contains the user's profile in the User Profile Path box, and then click OK.
Use the following format for the user profile path:
\\server_name\shared_folder_name\user_profile_folder_name
For example, if you want to store the user's roaming profile in a folder that has the same name as the user account in a shared folder that is named "Profiles" on a server that is named "Server1," type the following path:
\\Server1\Profiles\%username%
NOTE: Windows NT automatically replaces the %username% variable with the user account name when it creates and accesses the user profile. When you use this variable, you can type the same path for all users.
4. Click OK, and then quit User Manager for Domains or Active Directory Users and Computers.
The next time the user logs on, the user profile folder that you specified in step 3 is created. When the user logs off, the user's profile is copied to the new folder.
http://support.microsoft.com/kb/316353
http://technet.microsoft.com/en-us/library/cc780629%28WS.10%29.aspx
http://support.microsoft.com/kb/312138
Before you configure a user account to use a roaming user profile, you must create a shared folder on a Windows NT Server 4.0-based computer in the domain to store the roaming user profiles. This shared folder is often located on a domain controller, but it can also be located on any Windows NT Server 4.0-based computer in the domain.
To create a shared folder to store roaming user profiles:
1. Click Start, point to Programs, and then click Windows NT Explorer.
2. Click the drive on which you want to create a shared folder to store roaming user profiles.
3. On the File menu, point to New, and then click Folder.
4. Type a name for the new folder, and then press ENTER.
NOTE: Typically, the folder that is used to store roaming user profiles is called "Profiles". However, you can assign any name that you want to the folder.
5. Right-click the folder you created in step 3, and then click Sharing.
6. Click Shared As, type the name that you want to assign to the shared folder in the Share Name box, and then click OK.
NOTE: The Profiles folder is commonly shared as "Profiles."
7. Quit Windows NT Explorer.
Back to the top
How to Configure a User Account to Use a Roaming User Profile in a Windows-Based Domain
To configure user accounts in the domain, you can use any Windows NT Server 4.0, Windows 2000 Server, or Windows Server 2003-based computer in the domain or any Windows NT Workstation 4.0, Windows XP Professional, or Windows 2000 Professional-based computer that is running Windows NT Server Administration Tools in the domain. In addition, you must be logged on as either an administrator or as a user that is a member of the Administrators local group or the Account Operators local group in the domain.
To configure a user account to use a roaming user profile:
1. Click Start, point to Programs, point to Administrative Tools (Common), and then click User Manager for Domains or Active Directory Users and Computers for Windows Server 2000 or for Windows Server 2003.
2. Double-click the user account to which you want to assign a roaming profile, and then click Profile.
3. Type the complete path to the shared folder that contains the user's profile in the User Profile Path box, and then click OK.
Use the following format for the user profile path:
\\server_name\shared_folder_name\user_profile_folder_name
For example, if you want to store the user's roaming profile in a folder that has the same name as the user account in a shared folder that is named "Profiles" on a server that is named "Server1," type the following path:
\\Server1\Profiles\%username%
NOTE: Windows NT automatically replaces the %username% variable with the user account name when it creates and accesses the user profile. When you use this variable, you can type the same path for all users.
4. Click OK, and then quit User Manager for Domains or Active Directory Users and Computers.
The next time the user logs on, the user profile folder that you specified in step 3 is created. When the user logs off, the user's profile is copied to the new folder.
http://support.microsoft.com/kb/316353
http://technet.microsoft.com/en-us/library/cc780629%28WS.10%29.aspx
http://support.microsoft.com/kb/312138
mk-query-digest command and installation details
mk-query-digest maatkit-6457.tar.gz
tar –zxvf maatkit-6457.tar.gz
perl Makefile.PL
make install
mk-query-digest mysql slow quary log file path
http://www.maatkit.org/doc/mk-query-digest.html#downloading
mk-query-digest maatkit-6457.tar.gz
tar –zxvf maatkit-6457.tar.gz
perl Makefile.PL
make install
mk-query-digest mysql slow quary log file path
http://www.maatkit.org/doc/mk-query-digest.html#downloading
Login mysql
use db;
update mantis_user_table set password=md5('Asd@3se') where username='jconlon';
pasword : Asd@3se
username: jconlon
use db;
update mantis_user_table set password=md5('Asd@3se') where username='jconlon';
pasword : Asd@3se
username: jconlon
Register an Executable as Windows Service
Need to register a self programmed executable as a Windows Service, that will:
1) start whenever system request
2) allow it to start if the service it depended on has started (This will be another topic)
What you need is really easy.
1) Go to microsoft to download Windows Resource Toolkits which is found here:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd
2) Run the rktools to unpack it, Default directories it unpacked to is: "C:\\Program Files\Windows Resource Toolkits\Tools"
3) Go Start->Run->cmd, using dos command navigate to the directories specified in step 3.
4) Type in->instsrv (Your service name) (the location of the executables file)
e.g., instsrv MyService "c:\\MyService\\Test.exe"
Need to register a self programmed executable as a Windows Service, that will:
1) start whenever system request
2) allow it to start if the service it depended on has started (This will be another topic)
What you need is really easy.
1) Go to microsoft to download Windows Resource Toolkits which is found here:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd
2) Run the rktools to unpack it, Default directories it unpacked to is: "C:\\Program Files\Windows Resource Toolkits\Tools"
3) Go Start->Run->cmd, using dos command navigate to the directories specified in step 3.
4) Type in->instsrv (Your service name) (the location of the executables file)
e.g., instsrv MyService "c:\\MyService\\Test.exe"
Subscribe to:
Posts (Atom)