Posftix Permission denied problem to send email using Gmail on Prestashop

CentoS 6.6 

Recently I stuck with Presta installation which was unable to send emails using build in wp_mail function.

After investigation tail -f /var/log/messages I founded a pleasant line of code with really nice explanation:

sendmail: fatal: chdir /var/spool/postfix: Permission denied

In theory this should be a problem for sysadmin, but – I wanted to find faster solution.

After short adventure with Google I found a clue:

/usr/sbin/getsebool httpd_can_sendmail

My result was obvious:

httpd_can_sendmail --> off

Problem was solved by

setsebool httpd_can_sendmail 1

Permament solution is possible via

setsebool -P httpd_can_sendmail 1

And don’t forget that I’m working on: CentOS Linux release 6.6 (Final)




Configure Windows 2008 L4 DSR 

How to configure Loopback Adapter

Weak Host Model

http://technet.microsoft.com/en-us/magazine/2007.09.cableguy.aspx
http://technet.microsoft.com/ko-kr/library/bb878108(en-us).aspx

Name of Interface : service
Loopback Interface :  loopback

netsh interface ipv4 set interface "service" weakhostreceive=enabled
netsh interface ipv4 set interface "loopback" weakhostreceive=enabled
netsh interface ipv4 set interface "loopback" weakhostsend=enabled

loopback :  set metric with 254, in order to not respond ARP.

netsh interface ipv4 set interface "loopback" metric=254

XenServer Tips and Tricks, Minimize the Size of your Exported Virtual Machines

A physical or virtual disk drive is made up of a bunch of blocks. As you save new data on your disk it gets written to these blocks. Brand new blocks are empty but over time as you add and delete files the blocks get filled with data. And in the interest of making file delete operations fast when you delete a file the operating system does not actually clear all the blocks used by the files it just marks the space as free for future use.
Now when XenServer starts exporting the virtual disk it looks and sees data in these unused blocks and in the interest of not tossing anything away on the off chance you need it XenServer exports any blocks with data in them. This can end up making your export files larger than the need to be.
So what you want to do is a process called zeroing out the unused blocks. This will take any space that is no longer used and clear it out. Then when you do your export this data does not have to be exported and you get a smaller file. The process to clear or “zero” out the unused blocks is a little different between Linux and Windows.
NOTE: If you are using VHD backed file systems with XenServer such as NFS storage this has a side effect of maxing out the size of the VHD file on the XenServer box.
Freeing up Windows Blocks
Microsoft has a nifty little utility called SDelete that will run through and find any unused blocks with data and clear them out. You can download SDelete at the link below.
http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx
Once you download the program open up a command prompt and run the command sdelete -c and it will do its magic!
Freeing up Linux Blocks
On Linux you can run a command and get the same result. Open up a shell prompt on your system and then run the following command for each of your file systems:
for example, / or /home
# cat /dev/zero > zero.fill;sync;sleep 1;sync;rm -f zero.fill

That's the way to zero out all unused Space on a filesystem, you have to repeat this on every filesystem inside your vm.

Configure WinRM 2.0

http://www.microsoft.com/ko-kr/download/details.aspx?id=20430

Check version

windows>winrm id

Configuring systems individually

You may configure the Windows systems to monitor individually, without Windows Group Policy.

Note If you choose the default WinRM configuration, supply Kerberos authentication settings in

zProperties. The Kerberos authentication process requires a Key Distribution Center (KDC), which acts as

both an authentication server and a ticket granting server. Microsoft Active Directory is a KDC, so the zWinKDC

value must be set to the IP address of the Active Directory server, and Zenoss Core collectors must be able to send

TCP/IP packets to it. The value of zWinRMUserName must include a fully qualified domain name (for example,

jsmith@zenoss.com) and zWinRMPassword must include the password of the user account.

Follow these steps to enable this ZenPack to monitor a Windows system.

1 Log on to the Windows system to enable, and open the Windows Firewall with Advanced Security utility, or

its equivalent.

2 Open port 5985 (for HTTP) or 5986 (for HTTPS) for WinRM, and then close the utility.

3 Start a command window as Administrator.

winrm get winrm/config

4 Configure the system to accept WS-Management requests from other systems.

winrm quickconfig

5 Configure the maximum number of concurrent operations per user.

winrm s winrm/config/service

@{MaxConcurrentOperationsPerUser="4294967295"}

Note This is the maximum value. The default (5) is inadequate, because Zenoss Core opens concurrent

requests for each WQL query and set of Perfmon counters. If the maximum value is inappropriate for your

environment, 50 should be adequate.

6 Configure the maximum number of shells per user.

winrm s winrm/config/winrs @{MaxShellsPerUser="2147483647"}

7 Configure the idle timeout.

winrm s winrm/config/winrs @{IdleTimeout="7200000"}

8 Optional: Configure HTTP. The default is HTTPS.

winrm s winrm/config/service @{AllowUnencrypted="true"}

For more information about configuring HTTPS, see Configuring HTTPS on page 49.

9 Optional: Configure Basic Authentication. The default is Kerberos.

winrm s winrm/config/service/auth @{Basic="true"}

Change XenServer Management Interface 

#Vi /etc/xensource-inventory

Management Interface: xenbr0 -> Xenbr1

#xe-toolstack-restart

Install Xen Server Tool on VM Machine

A.     Linux

# monut /dev/xvdd /mnt

#/mnt/Linux/install.sh

#reboot

B.      Ubuntu

#mount /dev/cdrom /mnt

#/mnt/Linux/install.sh

#reboot

How to increase Disk Size in XenServer Linux VM 

Check Disk Partition and Space

1. # fdisk –l

2.

3. # pvscan  : Physical Disk usage

4. 

5. # df -h

6. 

7. # shutdown –h now

8. Increse Disk Size Using XenCenter

9. Start VM

10. # fdisk /dev/xvda

11. n

12. p

13. 3

14. Enter

15. Enter

16. t

17. 3

18. 8e

19. w

20. # reboot

21. # pvcreate /dev/xvda3

22. # vgextend VolGroup /dev/xvda3

23. # lvextend -L+3.99G /dev/VolGroup/lv_root

24. # resize2fs /dev/VolGroup/lv_root

25. # reboot

26. # df -h