discuss-es September 2011

discuss-es@lists.centos.org

42 participants
33 discussions

Instalacion BlueFish en CentOS 6
by Ariel Hernández 08 Sep '11

08 Sep '11

Hola a todos, resulta que he estado cabeceandome para instalar bluefish en mi centos, el problema es que no he podido intente hacerlo instalando el repositorio extra rpmforge, pero sin embargo aún así me dice que no encuentra el paquete bluefish. Lo que hice ahora fue descargar de aquì<http://pkgs.org/centos-6-rhel-6/epel-i386/bluefish-2.0.3-4.el6.i686.rpm.html>, el paquete de bluefish, sin embargo, siguiendo un manual para instalarlo por terminal me da error. Lo que hice fue lo siguiente: *rpm -Uvh NombrePaquete.rpm * pero me da el siguiente error: * [root@local Descargas]# rpm -Uvh bluefish-2.0.3-4.el6.i686.rpm advertencia:bluefish-2.0.3-4.el6.i686.rpm: CabeceraV3 RSA/SHA256 Signature, ID de clave 0608b895: NOKEY error: Error de dependencias: bluefish-shared-data = 2.0.3-4.el6 se necesita para bluefish-2.0.3-4.el6.i686* Como puedo instalar de una vez bluefish?? Gracias por sus ayudas. Saludos. -- *Ariel Hernández Pastén* *Ingeniero Civil Informático*

2 1

php y mysql
by Marcelo Ochoa 08 Sep '11

08 Sep '11

Hola Lista: Sigue siendo de gran ayuda la comunidad, por eso, me permito molestarlos preguntando si alguno ha podido actualizar php y mysql en CentOS 6 tanto I386 y X64, me estoy volviendo un poco mas loco.Alguien lo ha conseguido? Por su paciencia muchas gracias Saludos Marcelo

1 0

YUM roto. No se puede instalar/actualizar nada
by Gerardo Barajas 07 Sep '11

07 Sep '11

Estimados de la lista. Sucede que recien obtuve un servidor virtual con las siguientes características. Linux neo-center 2.6.22.18-grsec2.1.11-vs2.2.0.6 #2 SMP Tue Feb 12 04:18:41 CST 2008 i686 i686 i386 GNU/Linux Ahora bien, intenté buscar/instalar algo vía yum, y esto es lo que obtengo: [root@neo-center ~]# yum search php-mysql Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Traceback (most recent call last): File "/usr/bin/yum", line 29, in ? yummain.user_main(sys.argv[1:], exit_code=True) File "/usr/share/yum-cli/yummain.py", line 309, in user_main errcode = main(args) File "/usr/share/yum-cli/yummain.py", line 178, in main result, resultmsgs = base.doCommands() File "/usr/share/yum-cli/cli.py", line 349, in doCommands return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds) File "/usr/share/yum-cli/yumcommands.py", line 627, in doCommand return base.search(extcmds) File "/usr/share/yum-cli/cli.py", line 806, in search for (po, keys, matched_value) in matching: File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 1834, in searchGenerator for sack in self.pkgSack.sacks.values(): File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 662, in <lambda> pkgSack = property(fget=lambda self: self._getSacks(), File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 502, in _getSacks self.repos.populateSack(which=repos) File "/usr/lib/python2.4/site-packages/yum/repos.py", line 232, in populateSack self.doSetup() File "/usr/lib/python2.4/site-packages/yum/repos.py", line 79, in doSetup self.ayum.plugins.run('postreposetup') File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 179, in run func(conduitcls(self, self.base, conf, **kwargs)) File "/usr/lib/yum-plugins/fastestmirror.py", line 181, in postreposetup_hook all_urls = FastestMirror(all_urls).get_mirrorlist() File "/usr/lib/yum-plugins/fastestmirror.py", line 333, in get_mirrorlist self._poll_mirrors() File "/usr/lib/yum-plugins/fastestmirror.py", line 376, in _poll_mirrors pollThread.start() File "/usr/lib/python2.4/threading.py", line 416, in start _start_new_thread(self.__bootstrap, ()) thread.error: can't start new thread ¿Alguna idea? Lei por ahi que ejecutando "yum clean all", podría mejorar el asunto, pero no. Saludos/Regards -- Ing. Gerardo Barajas Puente Proyectos Especiales | www.neocenter.com T:+52 (55) 8590-9000 x 7003

3 8

[off-topic] resirección a puerto IPS
by German 06 Sep '11

06 Sep '11

Cordial Saludo Estoy configurando un servidor web con Centos 6, el cual esta funcionando bien en la red local (ip => 192.168.0.100 gw => 192.168.0.1), pero tengo un inconveniente con mi ISP que me asigna una direccion IP Publica (190.xxx.xxx.xxx:8080), que hace forward hacia la direccion ip de mi servidor (192.168.0.100), el proveedor me dice que tengo que redireccionar el trafico de mi servidor hacia esa IP y ese puerto, pero he buscado y no encuentro cual es la forma. Agradezco cualquier dato que me sirva de guía.

1 0

Problema con USB Disk HELP!!
by Federico Don 06 Sep '11

06 Sep '11

Hola lista, tengo un problema con un disco usb, cuando enchufo el disco al server me asigno /dev/sdc1, el disco esta en EXT4 y mi centos es Linux version 2.6.18-164.11.1.el5 (Red Hat 4.1.2-46). Bien el problema es el siguiente, de un momento a otro ls: reading directory .: Input/output error, tiro un dmesg y veo qeu cambio el disco usb de particion: sdc: Write Protect is off sdc: Mode Sense: 38 00 00 00 sdc: assuming drive cache: write through SCSI device sdc: 1953525168 512-byte hdwr sectors (1000205 MB) sdc: Write Protect is off sdc: Mode Sense: 38 00 00 00 sdc: assuming drive cache: write through sdc:<6>EXT3 FS on dm-0, internal journal kjournald starting. Commit interval 5 seconds EXT3 FS on dm-1, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-5, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-6, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-7, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-3, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-8, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on sda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. Adding 8552440k swap on /dev/VolGroup00/LVSwap. Priority:-1 extents:1 across:8552440k powernow-k8: Pre-initialization of ACPI failed powernow-k8: Found 1 AMD Athlon(tm) II X2 245 Processor processors (2 cpu cores) (version 2.20.00) powernow-k8: Your BIOS does not provide _PSS objects. PowerNow! does not work on SMP systems without _PSS objects. Complain to your BIOS vendor. powernow-k8: Your BIOS does not provide _PSS objects. PowerNow! does not work on SMP systems without _PSS objects. Complain to your BIOS vendor. sdc1 sd 2:0:0:0: Attached scsi disk sdc sd 2:0:0:0: Attached scsi generic sg2 type 0 usb-storage: device scan complete NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver eth0: no IPv6 routers present EXT4-fs: barriers enabled kjournald2 starting: pid 2815, dev sdc1:8, commit interval 5 seconds EXT4 FS on sdc1, internal journal on sdc1:8 EXT4-fs: delayed allocation enabled EXT4-fs: file extents enabled EXT4-fs: mballoc enabled EXT4-fs: mounted filesystem sdc1 with ordered data mode eth0: link down. eth0: link up. eth0: link down. eth0: link up. eth0: link down. eth0: link up. eth0: link down. eth0: link up. eth0: link down. eth0: link up. eth0: link down. eth0: link up. eth0: link down. eth0: link up. eth0: link down. eth0: link up. tnslsnr[2946]: segfault at 0000000000000018 rip 0000003115a70485 rsp 00007fff0bcb96b0 error 4 tnslsnr[9084]: segfault at 0000000000000018 rip 0000003115a70485 rsp 00007fff101eaed0 error 4 usb 1-4: reset high speed USB device using ehci_hcd and address 2 usb 1-4: USB disconnect, address 2 sd 2:0:0:0: SCSI error: return code = 0x00010000 end_request: I/O error, dev sdc, sector 393094152 sd 2:0:0:0: rejecting I/O to device being removed sd 2:0:0:0: rejecting I/O to device being removed sd 2:0:0:0: rejecting I/O to device being removed sd 2:0:0:0: SCSI error: return code = 0x00010000 end_request: I/O error, dev sdc, sector 393094392 Aborting journal on device sdc1:8. sd 2:0:0:0: rejecting I/O to device being removed Buffer I/O error on device sdc1, logical block 121667584 lost page write due to I/O error on sdc1 JBD2: I/O error detected when updating journal superblock for sdc1:8. journal commit I/O error sd 2:0:0:0: rejecting I/O to device being removed Buffer I/O error on device sdc1, logical block 13107232 lost page write due to I/O error on sdc1 sd 2:0:0:0: rejecting I/O to device being removed Buffer I/O error on device sdc1, logical block 50855968 lost page write due to I/O error on sdc1 sd 2:0:0:0: rejecting I/O to device being removed Buffer I/O error on device sdc1, logical block 61866016 lost page write due to I/O error on sdc1 scsi 2:0:0:0: rejecting I/O to dead device ext4_abort called. EXT4-fs error (device sdc1): ext4_journal_start_sb: Detected aborted journal Remounting filesystem read-only usb 1-4: new high speed USB device using ehci_hcd and address 3 usb 1-4: configuration #1 chosen from 1 choice scsi3 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 3 usb-storage: waiting for device to settle before scanning Vendor: ST310005 Model: 20AS Rev: Type: Direct-Access ANSI SCSI revision: 04 SCSI device sdd: 1953525168 512-byte hdwr sectors (1000205 MB) sdd: Write Protect is off sdd: Mode Sense: 38 00 00 00 sdd: assuming drive cache: write through SCSI device sdd: 1953525168 512-byte hdwr sectors (1000205 MB) sdd: Write Protect is off sdd: Mode Sense: 38 00 00 00 sdd: assuming drive cache: write through sdd: sdd1 sd 3:0:0:0: Attached scsi disk sdd sd 3:0:0:0: Attached scsi generic sg2 type 0 usb-storage: device scan complete scsi 2:0:0:0: rejecting I/O to dead device scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device scsi 2:0:0:0: rejecting I/O to dead device scsi 2:0:0:0: rejecting I/O to dead device scsi 2:0:0:0: rejecting I/O to dead device scsi 2:0:0:0: rejecting I/O to dead device scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 EXT3-fs: sdd1: couldn't mount because of unsupported optional features (240). scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs error (device sdc1): ext4_find_entry: reading directory #2 offset 0 scsi 2:0:0:0: rejecting I/O to dead device scsi 2:0:0:0: rejecting I/O to dead device EXT4-fs: barriers enabled kjournald2 starting: pid 15697, dev sdd1:8, commit interval 5 seconds EXT4 FS on sdd1, internal journal on sdd1:8 EXT4-fs: delayed allocation enabled EXT4-fs: file extents enabled EXT4-fs: mballoc enabled EXT4-fs: recovery complete. EXT4-fs: mounted filesystem sdd1 with ordered data mode usbcore: registered new driver usbserial drivers/usb/serial/usb-serial.c: USB Serial support registered for generic usbcore: registered new driver usbserial_generic drivers/usb/serial/usb-serial.c: USB Serial Driver core drivers/usb/serial/usb-serial.c: USB Serial support registered for GSM modem (1-port) usbcore: registered new driver option drivers/usb/serial/option.c: USB Driver for GSM modems: v0.7.1 El equipo no se reinicio " uptime 10:51:04 up 6 days, 15:14, 1 user, load average: 0.03, 0.91, 2.25 " Alguien me puede guiar por donde puede venir el problema de que cambie por si solo!!?? ahora tengo montado asi= /dev/sdc1 917G 221G 650G 26% /mnt/disk2 /dev/sdd1 917G 221G 650G 26% /mnt/disk2 donde sdd1 es donde se encuentra en este momento y sdc1 no me permite desmontar umount /dev/sdc1 umount: /mnt/disk2: device is busy umount: /mnt/disk2: device is busy Help me!!!!! Gracias a todos por su tiempo!!

2 1

Problemas irq + datos
by victor santana 02 Sep '11

02 Sep '11

Detallo más información: [root@ ~]# mii-tool eth0: negotiated 100baseTx-FD, link ok eth1: negotiated 100baseTx-FD flow-control, link ok SIOCGMIIREG on eth2 failed: Input/output error eth2: negotiated 100baseTx-FD, link ok SIOCGMIIREG on eth3 failed: Input/output error eth3: negotiated 100baseTx-FD flow-control, link ok [root@ ~]# ifconfig eth2 eth2 Link encap:Ethernet HWaddr 00:15:17:12:68:A4 inet addr:192.168.22.2 Bcast:192.168.22.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:19965 errors:0 dropped:0 overruns:0 frame:0 TX packets:19595 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:20317531 (19.3 MiB) TX bytes:2303273 (2.1 MiB) Memory:fea80000-feaa0000 [root@ ~]# ifconfig eth3 eth3 Link encap:Ethernet HWaddr 00:15:17:12:68:A5 inet addr:192.168.222.2 Bcast:192.168.222.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:30940 errors:0 dropped:0 overruns:0 frame:0 TX packets:31692 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:37202523 (35.4 MiB) TX bytes:2986693 (2.8 MiB) Memory:feae0000-feb00000 ---------- Mensaje reenviado ---------- De: victor santana <reparaciononline(a)gmail.com> Fecha: 1 de septiembre de 2011 16:42 Asunto: Problemas irq Para: "centos-es(a)centos.org" <centos-es(a)centos.org> Hola a tod@s, hace tiempo escribi sobre un problema en mi servidor el cual se reiniciaba solo o se bloqueaba. El problema estaba en las 4 tarjetas de red integradas en placa las cual uso para la red interna y para las 3 conexiones de internet que usamos. Al volver a bloquearse y ver errores rx.tx decidi probar con 2 tarjetas duales pci express las cuales no han colgado el server. Ahora bien me sale para 1 de ellas un problema al hacer mii-tool error input output. Creo que es conflicto con algun irq. ¿Alguien sabe como resolverlo? -- _______________________ REPARACIONONLINE GARANTIA PARA SU PC ********************************

2 3

Instalar Asterisk
by Ariel Hernández 02 Sep '11

02 Sep '11

Hola a todos, resulta que quiero empezar a trabajar con asterisk, y encontre un post donde dice que se puede instalar este software solo con hacer: yum install asterisk. Mi pregunta es, que mas debo tener para poder correr correctamente Asterisk? Saludos. -- *Ariel Hernández Pastén* *Ingeniero Civil Informático*

3 2

Problemas irq
by victor santana 01 Sep '11

01 Sep '11

Hola a tod@s, hace tiempo escribi sobre un problema en mi servidor el cual se reiniciaba solo o se bloqueaba. El problema estaba en las 4 tarjetas de red integradas en placa las cual uso para la red interna y para las 3 conexiones de internet que usamos. Al volver a bloquearse y ver errores rx.tx decidi probar con 2 tarjetas duales pci express las cuales no han colgado el server. Ahora bien me sale para 1 de ellas un problema al hacer mii-tool error input output. Creo que es conflicto con algun irq. ¿Alguien sabe como resolverlo?

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

discuss-es September 2011