W3exposé

Magento Default Product Info Column

W3exposé — Tue, 17 Jan 2012 20:22:39 +0000

Users of Magento will probably be familiar with how simply changing the product display to ‘Product Info Column’ when creating a product, can vastly improve the appearance of a product on the frontend. Leaving this to a client however is something that they could possibly forget to change while in the middle of adding hundreds of products. You can make ‘Product Info Column’ be selected by default by making a simple change in the database.

Find the table ‘eav_attribute’ and look for a row with the attribute code ‘options_container’ (ID 102 in Magento 1.6).
You will see a field called ‘options_container’, which is set by default to ‘container2′.
Just change to ‘container1′, then press the Go button at the bottom of the page.

Now Product Info Column will be your default choice when creating a product.

Configurar fecha en Ubuntu

W3exposé — Fri, 11 Nov 2011 23:22:29 +0000

Para cambiar zona horaria
dpkg-reconfigure tzdata

si no tiene tzdata, lo puede instalar de la siguiente forma

sudo aptitude install tzdata

Cambiar IP a un DNS en WHM/Cpanel

W3exposé — Wed, 09 Nov 2011 11:01:38 +0000

Hoy al mover un servidor Cpanel DNS only a otro datacenter, me tope con que el Cpanel/WHM (master) no podia conectar con el nuevo DNS cluster.

El problema estaba en q el WHM(master) aun conectaba a ns1.dominio.com en ip 192.168.1.2 cuando tenia q buscar ns1.dominio.com en el ip nuevo 192.168.1.5

Para corregirlo, cambia los valores en los siguientes archivos.

root@root[~]# cat /etc/nameserverips 198.168.0.1=ns1.test.com 198.168.0.5=ns2.test.com
Igual tambien en /var/cpanel/nameserverips.yaml

root@root [~]# cat /var/cpanel/nameserverips.yaml — ns1.test.com: “198.168.0.1″: 1 count: 1 zones: test.com ns2,.test.com: 198.168.0.2: 1 count: 1 zones: test.com

Finalmente reiniciar el servidor y listo.

Verificar puestos abiertos

W3exposé — Tue, 08 Nov 2011 17:41:39 +0000

El siguiente comando se ejecuta desde la consola y determina cuales puertos estan listo para coneccion TCP desde una red local o remota.

nmap -sT -O localhost o nmap -sT -O dominio.com

Para instalarlo en Centos
yum install nmap

[~]# nmap -sT -O localhost

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2011-11-08 12:39 EST Interesting ports on localhost.localdomain (127.0.0.1): Not shown: 1668 closed ports PORT STATE SERVICE 21/tcp open ftp 22/tcp open ssh 25/tcp open smtp 110/tcp open pop3 143/tcp open imap 443/tcp open https 465/tcp open smtps 783/tcp open spamassassin 993/tcp open imaps 995/tcp open pop3s 3306/tcp open mysql 8081/tcp open blackice-icecap

Como instalar CentOS 6 Via internet

W3exposé — Wed, 02 Nov 2011 03:00:37 +0000

Anoche mientras necesitaba instalar Centos 6 y el disco que tenia estaba dañado. Para ahorrarme un poco de tiempo y bandwidth al bajar 4.3GB, preferi utilizar la instalacion via red o net install de centos que pesa solo 170mb.

Cuando llegues a la parte donde te pregunte el URL de donde bajara las imagenes puedes especificarle una de tu red de area local o igual puedes utilizar las imagenes que estan en los mirrors de centos

Los siguientes URL te ahorraran el tiempo de buscarlos

32 bit: http://mirror.centos.org/centos/6/os/i386/ 64 bit: http://mirror.centos.org/centos/6/os/x86_64/
Es todo lo que el instalador necesita para una instalacion.

Como verificar la integridad de un RAID

W3exposé — Wed, 02 Nov 2011 01:59:31 +0000

Para monitorear cómo se encuentra nuestro raid podemos ejecutar el comando:

cat /proc/mdstats
A través de este comando podemos verificar lo siguiente:
1- cuántos RAID tenemos
2- qué particiones pertenecen a cada RAID
3- si hay una partición dañada, nos indicará cuál es
4- si se está sincronizando o ya se sincronizó un raid.

Resultado:
[root@server1 ~]# cat /proc/mdstat Personalities : [raid10] [raid1] md0 : active raid1 sdd1[3] sdc1[2] sdb1[1] sda1[0] 264960 blocks [4/4] [UUUU] md1 : active raid10 sdd2[3] sdc2[2] sdb2[1] sda2[0] 32772096 blocks 256K chunks 2 near-copies [4/4] [UUUU] md2 : active raid10 sdd3[3] sdc3[2] sdb3[1] sda3[0] 943464960 blocks 256K chunks 2 near-copies [4/4] [UUUU] [======>..............] resync = 34.8% (328547584/943464960) finish=94.8min speed=108010K/sec unused devices:

En detalle
Personalities : [raid10] [raid1] md0 : active raid1 sdd1[3] sdc1[2] sdb1[1] sda1[0] 264960 blocks [4/4] [UUUU]
Esto nos indica que md0 es un raid1, compuesto por sdd1, sdc1, sdb1 y sda1 (sda1 es el primer [0] disco, y sdd1 es el cuarto [3] disco)
El ejemplo anterior nos indica tambien que 4 de 4 discos [4/4] [UUUU] estan funcionando correctamente

Lo mismo con md1 y md2

Nota: Este ejemplo fue efectuado en un RAID 10

Testing Kaltura

W3exposé — Sun, 30 Oct 2011 07:44:14 +0000

Testing Kaltura server

video platform video management video solutions video player

Cpanel DNS Only On Amazon EC2

W3exposé — Thu, 06 Oct 2011 18:36:47 +0000

Just to let those looking to install DNS only on a EC2 Instance, that i successfully installed DNS Only on a Micro EC2

At the moment everything is working fine

> nslookup domain.com ns1.myserver.net (root) nameserver = C.ROOT-SERVERS.NET (root) nameserver = D.ROOT-SERVERS.NET (root) nameserver = E.ROOT-SERVERS.NET (root) nameserver = F.ROOT-SERVERS.NET (root) nameserver = G.ROOT-SERVERS.NET (root) nameserver = H.ROOT-SERVERS.NET (root) nameserver = I.ROOT-SERVERS.NET (root) nameserver = J.ROOT-SERVERS.NET (root) nameserver = K.ROOT-SERVERS.NET (root) nameserver = L.ROOT-SERVERS.NET (root) nameserver = M.ROOT-SERVERS.NET (root) nameserver = A.ROOT-SERVERS.NET (root) nameserver = B.ROOT-SERVERS.NET Server: UnKnown Address: x.x.x.x (ip of my EC2) Name: domain.com Address: x.x.x.x (ip of my web server)

Make sure DNS cluster configuration as follows:

* ensure that via WHM of the two DNS ONLY servers the Configure Cluster page defines the DNS role as “Standalone” to the cPanel/WHM server.
* Conversely, please ensure that via WHM of the cPanel/WHM server the Configure Cluster page defines the DNS role as “Synchronize Changes” to the DNS ONLY servers.

The install process is just as described in the documentation. no extra configuration is needed.

Amazon EC2 Instance used: scalr-centos56-x64 (ami-2c9e6145)

Thanks.

Change Nameserver Ips in Cpanel/WHM

W3exposé — Thu, 06 Oct 2011 07:30:07 +0000

If you want to change your nameservers ip in whm, you have to edit /etc/nameserverips

root@root[~]# cat /etc/nameserverips 198.168.0.1=ns1.test.com 198.168.0.2=ns2.test.com
Also in the following file /var/cpanel/nameserverips.yaml file.

root@root [~]# cat /var/cpanel/nameserverips.yaml — ns1.test.com: “198.168.0.1″: 1 count: 1 zones: test.com ns2,.test.com: 198.168.0.2: 1 count: 1 zones: test.com
Now check nameserver ips in WHM >> Main >> DNS Functions >> Nameserver IPs.

Ports used by Cpanel/WHM system

admin — Tue, 04 Oct 2011 03:47:33 +0000

Port	Service	Protocol	Direction	Notes
20	ftp	tcp	inbound/outbound
21	ftp	tcp,udp	inbound/outbound
22	ssh	tcp	inbound
25	smtp	tcp	inbound/outbound
26	smtp	tcp	inbound/outbound
37	rdate	tcp	outbound
43	whos	tcp	outbound
53	DNS	tcp/udp	inbound/outbound	Inbound only needed if you run your own DNS server
80	http	tcp	inbound/outbound
110	pop3	tcp	inbound
113	ident	tcp	outbound
143	imap4	tcp	inbound
443	https	tcp	inbound
465	smtp	tcp/ssl, tcp/udp	inbound/outbound
873	rsync	tpc/udp	outbound
993	imap4	ssl tcp	inbound
995	pop3	ssl tcp	inbound
2082	cpanel	tcp	inbound
2083	cpanel	ssl tcp	inbound
2086	whm	tcp	inbound
2087	whm ssl	tcp	inbound
2089	cp license	tcp	outbound
2095	webmail	tcp	inbound
2096	webmail	ssl tcp	inbound
3306	mysql	tcp	inbound	Only if you need to connect remotely
6666	chat	tcp	inbound