[CentOS-docs] Format for giving examples of commands
Hello, Is there a standard format for quoting examples of commands to be entered by the user? I've given the following example commands: cd /tmp wget http://www.skype.com/go/getskype-linux-beta-static cd /opt tar xjvf /tmp/skype_static-4.0.0.7.tar.bz2 rm /tmp/skype_static-4.0.0.7.tar.bz2 ln -s skype_staticQT-4.0.0.7 skype Someone changed them to add prompts: [root@host]# cd /tmp [root@host]# wget http://www.skype.com/go/getskype-linux-beta-static [root@host]# cd /opt [root@host]# tar xjvf /tmp/skype_static-4.0.0.7.tar.bz2 [root@host]# rm /tmp/skype_static-4.0.0.7.tar.bz2 [root@host]# ln -s skype_staticQT-4.0.0.7 skype I think my way is better, since the user can simply copy and paste the entire example into a terminal. Conversely, with a prompt, there's no chance that the example will be confused with a program listing, but I don't think that's likely to happen. Is either format preferred? Yves -- Yves Bellefeuille y...@storm.ca La Esperanta Civito ne rifuzas anticipe la kunlaboron de erarintoj, se ili konscias pri sia eraro. -- Heroldo Komunikas, n-ro 473. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Format for giving examples of commands
On Sun, Jun 17, 2012 at 11:37 AM, Yves Bellefeuille y...@storm.ca wrote: Hello, Is there a standard format for quoting examples of commands to be entered by the user? I've given the following example commands: cd /tmp wget http://www.skype.com/go/getskype-linux-beta-static cd /opt tar xjvf /tmp/skype_static-4.0.0.7.tar.bz2 rm /tmp/skype_static-4.0.0.7.tar.bz2 ln -s skype_staticQT-4.0.0.7 skype Someone changed them to add prompts: [root@host]# cd /tmp [root@host]# wget http://www.skype.com/go/getskype-linux-beta-static [root@host]# cd /opt [root@host]# tar xjvf /tmp/skype_static-4.0.0.7.tar.bz2 [root@host]# rm /tmp/skype_static-4.0.0.7.tar.bz2 [root@host]# ln -s skype_staticQT-4.0.0.7 skype I think my way is better, since the user can simply copy and paste the entire example into a terminal. Conversely, with a prompt, there's no chance that the example will be confused with a program listing, but I don't think that's likely to happen. Is either format preferred? I think people's opinions will split on this. When the above change was made, Karanbir Singh noted on IRC: kbsingh yeah, that also makes sure that people cant copy + paste stuff in one go kbsingh they need to copy bits in one piece at a time I tend to agree that we want to be sure users do not just copy the while thing in one shot. Another (actually main) purpose of presenting the prompt is to distinguish the commands that must (or must not) be run as root. Akemi ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Format for giving examples of commands
On Sunday 17 June 2012, Akemi Yagi amy...@gmail.com wrote: I think people's opinions will split on this. When the above change was made, Karanbir Singh noted on IRC: I guess I'll have to start following IRC. I tend to agree that we want to be sure users do not just copy the while thing in one shot. The main problem with copy and paste, I think, is that usually a carriage return is automatically added at the end, and so the command is immediately executed. Forcing users to copy and paste individual bits does nothing to prevent this. Yves -- Yves Bellefeuille y...@storm.ca La Esperanta Civito ne rifuzas anticipe la kunlaboron de erarintoj, se ili konscias pri sia eraro. -- Heroldo Komunikas, n-ro 473. ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-docs] Format for giving examples of commands
On 17.06.2012 22:23, Yves Bellefeuille wrote: The main problem with copy and paste, I think, is that usually a carriage return is automatically added at the end, and so the command is immediately executed. Forcing users to copy and paste individual bits does nothing to prevent this. Yes, but you cannot copypaste in one go, thus maybe destroying *all* data on your machine (but only a bit of it) :) For my lazyness cp in one go would be better, but for getting me to think about something, this is better. Regards, Ralph ___ CentOS-docs mailing list CentOS-docs@centos.org http://lists.centos.org/mailman/listinfo/centos-docs
Re: [CentOS-virt] Failing to start or create VM, cannot connect to hypervisor host
On 06/16/2012 11:14 PM, jbo...@meridianenv.com wrote: Greetings - I shutdown one of my Centos 6.2 VMs for some offline maintenance and am now unable to get it to restart. I am also unable to create and start a new VM. The host system is Centos 6.2, fully up to date. I have been searching Google for two days and have not been successful in getting a VM to start. I have restarted libvirtd, but did not want to shutdown my other two running VMs and reboot my host system, unless I felt confident that it would solve the problem. The other two VMs on the box are still running fine, but I am also unable to connect to a console in VirtManger with them. I was able to connect to all these VM consoles from the host system just a week or so ago. The only changes that I had recently made to the host system was to add some restrictions in my /etc/hosts.allow and hosts.deny files and installed Fail2ban. I have reversed all of the changes to my hosts.allow/deny files and have stopped the Fail2ban service. Still unable to start or create a VM. I am at the end of my rope here and am hoping someone will be able to direct me with where I should be looking next. My error and log messages are listed below. Thanks. Jeff Trying to start the VM using VirtManager at the console of the host results in the following error. error: Failed to start domain SequoiaVM error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4, 127.0.0.1, 5902) : Cannot assign requested address inet_listen_opts: FAILED Each attempt at a restart results in the following set of messages in /var/log/messages Jun 16 13:45:04 earth kernel: device vnet2 entered promiscuous mode Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering learning state Jun 16 13:45:04 earth qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering disabled state Jun 16 13:45:04 earth kernel: device vnet2 left promiscuous mode Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering disabled state Jun 16 13:45:04 earth kernel: libfcoe_device_notification: NETDEV_UNREGISTER vnet2 Log messages in /var/log/libvirt/libvirtd.log are similar to the console 2012-06-16 19:56:39.807+: 32175: error : virNetSocketReadWire:911 : End of file while reading data: Input/output error 2012-06-16 20:15:23.672+: 32176: error : qemuMonitorOpenUnix:290 : failed to connect to monitor socket: No such process 2012-06-16 20:15:23.672+: 32176: error : qemuProcessWaitForMonitor:1289 : internal error process exited while connecting to monitor: char device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4,127.0.0.1,5902): Cannot assign requested address inet_listen_opts: FAILED Log messages in /var/log/libvirt/qemu/SequoiaVM.log are similar 2012-06-16 13:45:04.572: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 2048 -smp 4,sockets=4,cores=1,threads=1 -name SequoiaVM -uuid 1ca3a14b-cd4b-f371-b3fe-1cd518480c09 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/SequoiaVM.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot order=dc,menu=on -drive file=/dev/vg_mei/lv_sequoiaroot,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -drive file=/dev/vg_mei/lv_sequoiaswap,if=none,id=drive-virtio-disk1,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=virtio-disk1 -drive file=/dev/vg_mei/lv_sequoiavar,if=none,id=drive-virtio-disk2,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk2,id=virtio-disk2 -drive file=/dev/vg_mei/lv_sequoiahome,if=none,id=drive-virtio-disk3,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,drive=drive-virtio-disk3,id=virtio-disk3 -drive file=/dev/vg_mei/lv_sequoiaecosystem,if=none,id=drive-virtio-disk4,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x9,drive=drive-virtio-disk4,id=virtio-disk4 -drive file=/dev/sr0,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:9d:b2:49,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:2 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xa char device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4,127.0.0.1,5902):
Re: [CentOS-virt] Failing to start or create VM, cannot connect to hypervisor host
Sorry for the mess on the message threading; responding from the daily digest. Thanks for the suggestion. I'll research any option that may provide a lead to a solution right now. I have not tried to touch /etc/qemu/krb5.tab. After a little research on what this file is for, I don't see that it would help me since I have never set up the system to use kerberos. I don't even have an /etc/qemu directory on my host. I would suspect that part of the error is a side effect of something else that is the main cause. Please keep coming with the suggestions though. I am working on a plan B to make the data files available to the staff on Monday morning. Jeff Message: 1 Date: Sat, 16 Jun 2012 14:14:04 -0700 (PDT) From: jbo...@meridianenv.com Subject: [CentOS-virt] Failing to start or create VM, cannot connect to hypervisor host To: centos-virt@centos.org Message-ID: 21752.184.157.241.237.1339881244.squir...@www.meridianenv.com Content-Type: text/plain;charset=iso-8859-1 Greetings - I shutdown one of my Centos 6.2 VMs for some offline maintenance and am now unable to get it to restart. I am also unable to create and start a new VM. The host system is Centos 6.2, fully up to date. I have been searching Google for two days and have not been successful in getting a VM to start. I have restarted libvirtd, but did not want to shutdown my other two running VMs and reboot my host system, unless I felt confident that it would solve the problem. The other two VMs on the box are still running fine, but I am also unable to connect to a console in VirtManger with them. I was able to connect to all these VM consoles from the host system just a week or so ago. The only changes that I had recently made to the host system was to add some restrictions in my /etc/hosts.allow and hosts.deny files and installed Fail2ban. I have reversed all of the changes to my hosts.allow/deny files and have stopped the Fail2ban service. Still unable to start or create a VM. I am at the end of my rope here and am hoping someone will be able to direct me with where I should be looking next. My error and log messages are listed below. Thanks. Jeff Trying to start the VM using VirtManager at the console of the host results in the following error. error: Failed to start domain SequoiaVM error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4, 127.0.0.1, 5902) : Cannot assign requested address inet_listen_opts: FAILED Each attempt at a restart results in the following set of messages in /var/log/messages Jun 16 13:45:04 earth kernel: device vnet2 entered promiscuous mode Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering learning state Jun 16 13:45:04 earth qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering disabled state Jun 16 13:45:04 earth kernel: device vnet2 left promiscuous mode Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering disabled state Jun 16 13:45:04 earth kernel: libfcoe_device_notification: NETDEV_UNREGISTER vnet2 Log messages in /var/log/libvirt/libvirtd.log are similar to the console 2012-06-16 19:56:39.807+: 32175: error : virNetSocketReadWire:911 : End of file while reading data: Input/output error 2012-06-16 20:15:23.672+: 32176: error : qemuMonitorOpenUnix:290 : failed to connect to monitor socket: No such process 2012-06-16 20:15:23.672+: 32176: error : qemuProcessWaitForMonitor:1289 : internal error process exited while connecting to monitor: char device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4,127.0.0.1,5902): Cannot assign requested address inet_listen_opts: FAILED Log messages in /var/log/libvirt/qemu/SequoiaVM.log are similar 2012-06-16 13:45:04.572: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 2048 -smp 4,sockets=4,cores=1,threads=1 -name SequoiaVM -uuid 1ca3a14b-cd4b-f371-b3fe-1cd518480c09 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/SequoiaVM.monitor,server, nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot order=dc,menu=on -drive file=/dev/vg_mei/lv_sequoiaroot,if=none,id=drive-virtio-disk0,format=raw,c ache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=vir tio-disk0 -drive file=/dev/vg_mei/lv_sequoiaswap,if=none,id=drive-virtio-disk1,format=raw,c ache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=vir tio-disk1 -drive file=/dev/vg_mei/lv_sequoiavar,if=none,id=drive-virtio-disk2,format=raw,ca che=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk2,id=vir tio-disk2 -drive
Re: [CentOS-virt] Failing to start or create VM, cannot connect to hypervisor host
Curious, is this system (the host) on a software raid? - aurf On Jun 17, 2012, at 10:35 AM, jbo...@meridianenv.com wrote: Sorry for the mess on the message threading; responding from the daily digest. Thanks for the suggestion. I'll research any option that may provide a lead to a solution right now. I have not tried to touch /etc/qemu/krb5.tab. After a little research on what this file is for, I don't see that it would help me since I have never set up the system to use kerberos. I don't even have an /etc/qemu directory on my host. I would suspect that part of the error is a side effect of something else that is the main cause. Please keep coming with the suggestions though. I am working on a plan B to make the data files available to the staff on Monday morning. Jeff Message: 1 Date: Sat, 16 Jun 2012 14:14:04 -0700 (PDT) From: jbo...@meridianenv.com Subject: [CentOS-virt] Failing to start or create VM,cannot connect to hypervisor host To: centos-virt@centos.org Message-ID: 21752.184.157.241.237.1339881244.squir...@www.meridianenv.com Content-Type: text/plain;charset=iso-8859-1 Greetings - I shutdown one of my Centos 6.2 VMs for some offline maintenance and am now unable to get it to restart. I am also unable to create and start a new VM. The host system is Centos 6.2, fully up to date. I have been searching Google for two days and have not been successful in getting a VM to start. I have restarted libvirtd, but did not want to shutdown my other two running VMs and reboot my host system, unless I felt confident that it would solve the problem. The other two VMs on the box are still running fine, but I am also unable to connect to a console in VirtManger with them. I was able to connect to all these VM consoles from the host system just a week or so ago. The only changes that I had recently made to the host system was to add some restrictions in my /etc/hosts.allow and hosts.deny files and installed Fail2ban. I have reversed all of the changes to my hosts.allow/deny files and have stopped the Fail2ban service. Still unable to start or create a VM. I am at the end of my rope here and am hoping someone will be able to direct me with where I should be looking next. My error and log messages are listed below. Thanks. Jeff Trying to start the VM using VirtManager at the console of the host results in the following error. error: Failed to start domain SequoiaVM error: internal error process exited while connecting to monitor: char device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4, 127.0.0.1, 5902) : Cannot assign requested address inet_listen_opts: FAILED Each attempt at a restart results in the following set of messages in /var/log/messages Jun 16 13:45:04 earth kernel: device vnet2 entered promiscuous mode Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering learning state Jun 16 13:45:04 earth qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering disabled state Jun 16 13:45:04 earth kernel: device vnet2 left promiscuous mode Jun 16 13:45:04 earth kernel: br0: port 4(vnet2) entering disabled state Jun 16 13:45:04 earth kernel: libfcoe_device_notification: NETDEV_UNREGISTER vnet2 Log messages in /var/log/libvirt/libvirtd.log are similar to the console 2012-06-16 19:56:39.807+: 32175: error : virNetSocketReadWire:911 : End of file while reading data: Input/output error 2012-06-16 20:15:23.672+: 32176: error : qemuMonitorOpenUnix:290 : failed to connect to monitor socket: No such process 2012-06-16 20:15:23.672+: 32176: error : qemuProcessWaitForMonitor:1289 : internal error process exited while connecting to monitor: char device redirected to /dev/pts/7 inet_listen_opts: bind(ipv4,127.0.0.1,5902): Cannot assign requested address inet_listen_opts: FAILED Log messages in /var/log/libvirt/qemu/SequoiaVM.log are similar 2012-06-16 13:45:04.572: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 2048 -smp 4,sockets=4,cores=1,threads=1 -name SequoiaVM -uuid 1ca3a14b-cd4b-f371-b3fe-1cd518480c09 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/SequoiaVM.monitor,server, nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot order=dc,menu=on -drive file=/dev/vg_mei/lv_sequoiaroot,if=none,id=drive-virtio-disk0,format=raw,c ache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=vir tio-disk0 -drive file=/dev/vg_mei/lv_sequoiaswap,if=none,id=drive-virtio-disk1,format=raw,c ache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk1,id=vir tio-disk1 -drive
Re: [CentOS-es] Compilar el Kernel en CentOS 6.1
Hola Ernesto. El archivo que bajé fue de la siguiente página... http://mirrors.coreix.net/elrepo/kernel/el6/x86_64/RPMS/ El archivo pesa 30 MB con respecto al archivo que bajé anteriormente, este fue el archivo. kernel-3.4.2-ml-1.el6.elrepo.x86_64.rpm http://mirrors.coreix.net/elrepo/kernel/el6/x86_64/RPMS/kernel-ml-3.4.2-1.el6.elrepo.x86_64.rpm Avisame si esta bien. Desde ya muchas gracias. El 15 de junio de 2012 14:22, Ernesto Pérez Estévez cen...@ecualinux.comescribió: On 06/15/2012 10:16 AM, Luciano Andrés Chiarotto wrote: Hola Ernesto. De esta página ( http://rpm.pbone.net/index.php3/stat/4/idpl/18147080/dir/redhat_el_6/com/kernel-ml-devel-3.4.2-1.el6.elrepo.x86_64.rpm.html ) bajé este paquete. kernel-ml-devel-3.4.2-1.el6.elrepo.x86_64.rpm hum, mira, este es el kernel-ml uno que compiló el autor de elrepo (si mal no recuerdo) pero que no es el original de centos. Te sugeriría mas bien que pruebes instalar simplemente el repo de elrepo y entonecs instales el kmod que te indiqué, para que te mantengas con el mismo kernel de centos. Además, no dudes que en kernels más modernos que el que tengas, ya esté este driver incluído, pues el upstream siempre provee nuevos módulos durante los primeros 5 años más o menos de existencia de la versión de CentOS saludos epe Te consulto, con la instalación de este paquete actualizo el kernel y a su vez los módulos de la placa de red ? La instalación la hago de la siguiente forma... rpm -Uvh kernel-ml-devel-3.4.2-1.el6.elrepo.x86_64.rpm y listo. Desde ya muchas gracias - epe. Saludos El 15 de junio de 2012 10:46, Ernesto Pérez Estévez cen...@ecualinux.comescribió: On 06/15/2012 08:11 AM, Luciano Andrés Chiarotto wrote: porque no me reconoce la placa de red (Realtek Semiconductor RTL 8168/8111 PCIe Gigabit Ethernet Adapter). sí te voy a indicar cómo: nunca se pone nada que no sea rpm en tu instalación, sino luego tendrás problemas al actualizar. no es requerido compilar el kernel, todo debe ser fácil sino no fuera linux: http://elrepo.org/tiki/kmod-r8168 prueba con elrepo, elrepo se especializa en módulos adicionales para los kernels de CentOS saludos epe ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es -- _(@^@)__ Luciano Andres Chiarotto Técnico Dpto. de Geología - UNSL San Luis. Técnico Universitario en Microprocesadores ___ CentOS-es mailing list CentOS-es@centos.org http://lists.centos.org/mailman/listinfo/centos-es
Re: [CentOS] Rhythmbox Replacement
On 17.06.2012 03:51, Mark LaPierre wrote: Hey Y'all, What application replaces the functionality of Rhythmbox for Cent OS 6.2? In particular I am interested in handling podcast feeds. Rhythmbox does support podcasts I believe. Anyway, from what I have at hand now I can say VLC and Clementine (KDE based) have support for podcasts; but you need to use 3rd party repos to install them (lime my own : ). -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] [HW/OT] Recommend vendor to recover data from LTO4 tapes
Posting here in the hope that some one may have encountered problems with recovery from backups on LTO4 media and found a solution. Back ups on FujiFilm LTO4 media (800/1600). Archives created using tar -cf /dev/nst0. The tapes were fine when the archives were created (tested by extracting random sample files from them) but something went wrong in storage (no physical damage). Now a few LTO4 tapes are giving I/O errors when I try to extract data from them. Tried dd_rescue and that too fails giving I/O errors. I am wondering if there are any service providers, to extract the data out of the magnetic tapes in a fashion similar to dead hard disks. Please share info if you know of any such provider. Thanks, -- Arun Khan ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Rhythmbox Replacement
On 06/17/2012 07:35 AM, Nux! wrote: On 17.06.2012 03:51, Mark LaPierre wrote: Hey Y'all, What application replaces the functionality of Rhythmbox for Cent OS 6.2? In particular I am interested in handling podcast feeds. Rhythmbox does support podcasts I believe. Anyway, from what I have at hand now I can say VLC and Clementine (KDE based) have support for podcasts; but you need to use 3rd party repos to install them (lime my own : ). I see that Rhythmbox is up to Rev. 2.97 on their home page. The current version in the el repo is 0.12.8. Looks to me like the repo has an old and creaky version. Rhythmbox 0.12.8 functions pretty well for catching podcasts and dropping them on my HD, but it does leave something to be desired. A new feed can be added but deleting a feed can only be done by manually editing the ~/.local/share/rhythmbox/rhythmdb.xml file. I tried the configure/make/install dance with the source for version 2.97 but I got resolvable dependencies. I'm thinking that's the reason why there is no newer version in the repo. Now to the point, VLC is useful for playing mp3 files once they are downloaded, but not so useful for collecting them. Clementine is also strongly music oriented. Great for playing podcasts but not so much for catching them. Anyway, what I'm looking for is a new pod catcher that isn't many years out of date, and is supported in the repos. I've learned over the years that mixing repos is a good recipe for disaster. -- _ °v° /(_)\ ^ ^ Mark LaPierre Registerd Linux user No #267004 www.counter.li.org ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fail2ban logrotate [was: Update on spam, postfix, fail2ban, centos 6]
Hello Bob,
On Sat, 2012-06-16 at 22:47 -0400, Bob Hoffman wrote:
1- you must use gamin as the setting or the log rotations will make
fail2ban fail
I noticed the failing of fail2ban after rotating the logs too.
Supposedly it works fine on CentOS 5 (from an IRC chat on
#fedora-epel(?)), but on CentOS 6 fail2ban will stop banning after log
rotation even though it should handle log rotation transparently.
However, you can fix your logrotate configuration to restart fail2ban
after rotating the logs. Sadly that will remove current bans, but at
least new bans will be added:
(mind the line wraps)
$ cat /etc/logrotate.d/syslog
/var/log/cron
/var/log/maillog
/var/log/messages
/var/log/secure
/var/log/spooler
{
sharedscripts
postrotate
/bin/kill -HUP `cat /var/run/syslogd.pid 2 /dev/null`
2 /dev/null || true
# reload fail2ban after log rotation
/usr/bin/fail2ban-client -x reload /dev/null
endscript
}
Regards,
Leonard.
--
mount -t life -o ro /dev/dna /genetic/research
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fail2ban logrotate [was: Update on spam, postfix, fail2ban, centos 6]
On 06/17/2012 10:16 AM, Leonard den Ottolander wrote:
Hello Bob,
On Sat, 2012-06-16 at 22:47 -0400, Bob Hoffman wrote:
1- you must use gamin as the setting or the log rotations will make
fail2ban fail
I noticed the failing of fail2ban after rotating the logs too.
Supposedly it works fine on CentOS 5 (from an IRC chat on
#fedora-epel(?)), but on CentOS 6 fail2ban will stop banning after log
rotation even though it should handle log rotation transparently.
However, you can fix your logrotate configuration to restart fail2ban
after rotating the logs. Sadly that will remove current bans, but at
least new bans will be added:
(mind the line wraps)
$ cat /etc/logrotate.d/syslog
/var/log/cron
/var/log/maillog
/var/log/messages
/var/log/secure
/var/log/spooler
{
sharedscripts
postrotate
/bin/kill -HUP `cat /var/run/syslogd.pid 2 /dev/null`
2 /dev/null || true
# reload fail2ban after log rotation
/usr/bin/fail2ban-client -x reload /dev/null
endscript
}
Regards,
Leonard.
I have been following this thread and I am interested to know what
kinda of notice your getting to know fail2ban has crashed
on a logrotate. I just did a force rotate and the only thing fail2ban
did was restart.
I am using Centos 6.2 + postfix + fail2ban-0.8.2-3.el6.rf
TIA
--
Brian - Get the latest Fremont, OH Weather
http://www.Fremont-OH-Weather.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fail2ban logrotate [was: Update on spam, postfix, fail2ban, centos 6]
On Sun, 2012-06-17 at 10:32 -0400, Mail Lists wrote: I have been following this thread and I am interested to know what kinda of notice your getting to know fail2ban has crashed on a logrotate. I just did a force rotate and the only thing fail2ban did was restart. There's no notice. For some reason it cannot find the log file(s) it's tracking anymore after a log rotate and stops adding IPs. The way I noticed this was happening is because fail2ban started to get awfully quiet (no ban mails). I am using Centos 6.2 + postfix + fail2ban-0.8.2-3.el6.rf The problem I'm seeing is with the EPEL build for CentOS 6. I don't know if the RF build is also affected. Regards, Leonard. -- mount -t life -o ro /dev/dna /genetic/research ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fail2ban logrotate [was: Update on spam, postfix, fail2ban, centos 6]
On 06/17/2012 10:38 AM, Leonard den Ottolander wrote: The problem I'm seeing is with the EPEL build for CentOS 6. I don't know if the RF build is also affected. Regards, Leonard. From what I am seeing the RF build is not effected. within seconds of my forced rotate I got notice of another ban. Thanks for the info.. -- Brian - Get the latest Fremont, OH Weather http://www.Fremont-OH-Weather.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fail2ban logrotate [was: Update on spam, postfix, fail2ban, centos 6]
On 6/17/2012 12:09 PM, Mail Lists wrote: On 06/17/2012 10:38 AM, Leonard den Ottolander wrote: The problem I'm seeing is with the EPEL build for CentOS 6. I don't know if the RF build is also affected. Regards, Leonard. From what I am seeing the RF build is not effected. within seconds of my forced rotate I got notice of another ban. Thanks for the info.. force rotate will not trigger the issue with fail2ban setup your logrotate file to go daily and see what happens the next day. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fail2ban logrotate [was: Update on spam, postfix, fail2ban, centos 6]
On 6/17/2012 12:32 PM, bob wrote: force rotate will not trigger the issue with fail2ban setup your logrotate file to go daily and see what happens the next day. to clarify, it is the rotation of the log files fail2ban is looking at that is the issue, not fail2ban rotating its own logs. without gamin being used with centos 6 it will get lost and stay on the old log file that was rotated..thus never logging anything again until restart/reload of fail2ban client ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] unfsd scalability issues
On Thu, Jun 14, 2012 at 1:15 PM, Boris Epstein borepst...@gmail.com wrote: On Wed, Jun 13, 2012 at 10:11 AM, m.r...@5-cent.us wrote: Boris Epstein wrote: On Sat, Jun 2, 2012 at 2:50 PM, John R. Dennison j...@gerdesas.com wrote: On Sat, Jun 02, 2012 at 10:59:13AM -0400, Boris Epstein wrote: snip To be specific, I use UNFSD to export a MooseFS file system. MooseFS, by the way, is userland-process based too. Be that as it may, I've seen situations where a comparably configured MooseFS client get to read at, say, 40 MB/s - which is fine - but the UNFSD at the same time reads at 40K/s(!) Why would that be? I mean, some degradation I can dig but 3 orders of magnitude? What is with this? Am I doing something wrong? snip I wonder... what's the architecture of what you're getting these results? I tried opening a bug with upstream over NFS4 and 6.x, and no one ever looked at it, and they closed it. 100% repeatably: unpack a package locally, seconds. unpack it from an NFS mount onto a local drive, about 1 min. unpack it from an NFS mount onto an NFS mount, even when the target is exported FROM THE SAME MACHINE* that the process is running on: 6.5 - 7 MINUTES. * That is, [server 1] [server 2] /export/thatdir --NFS--/target/dir /s2/source /source/dir --NFS--/s2/source and cd [server 2]:/target/dir and unpack from /s2/source I suppose I'll try logging into upstream's bugzilla using our official licensed id; maybe then they'll assign someone to look at it mark Mark, Thanks, my architecture is extremely similar to yours, except that in my case the second layer, if I may say so, is MooseFS ( http://www.moosefs.org/ ), not NFS. MooseFS itself is blazing, by the way. So the diagram in my case would look something like this: /export/thatdir --NFS--/target/dir /s2/source /source/dir -- MooseFS mount (mfsmount) --/s2/source The discrepancy in the resultant performance is comparable. Thanks. Boris. I may have discovered a fix. Still don't know why it is a fix - but for what it's worth... OK, if you put your UNFSD daemon on a completely different physical machine - i.e., with no MooseFS component running on it - it seems to work just fine. For a single client I got a performance of about 70 MB/s over 1 Gbit/s network. When multiple (up to 5) clients) do their reads the performance seems to degrade roughly proportionally. And this is strange. I've got MooseFS currently confined to just one machine (8 cores, 48 GB RAM): master server, meta server, chunk server, the whole thing. And that works fine. Add UNFSD - and it still works, and the load is still low (under 1) - and yet the UNFSD's performance goes down the drain. Why? I have no idea. By the way, the autonomous UNFSD server is far from a powerful piece of software - all it is is a P5-class 2-core machine with 2 GB of RAM. So go figure... Boris. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Rhythmbox Replacement
On Sat, 2012-06-16 at 22:51 -0400, Mark LaPierre wrote: Hey Y'all, What application replaces the functionality of Rhythmbox for Cent OS 6.2? In particular I am interested in handling podcast feeds. I use Banshee for all that multimedia stuff; including podcasts. It works *great*. But my desktop laptop are openSUSE. I don't know if Banshee is packaged for CentOS6 [which I use on servers]. signature.asc Description: This is a digitally signed message part ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [HW/OT] Recommend vendor to recover data from LTO4 tapes
2012/6/17 Arun Khan knu...@gmail.com: Posting here in the hope that some one may have encountered problems with recovery from backups on LTO4 media and found a solution. Back ups on FujiFilm LTO4 media (800/1600). Archives created using tar -cf /dev/nst0. The tapes were fine when the archives were created (tested by extracting random sample files from them) but something went wrong in storage (no physical damage). Now a few LTO4 tapes are giving I/O errors when I try to extract data from them. Tried dd_rescue and that too fails giving I/O errors. I am wondering if there are any service providers, to extract the data out of the magnetic tapes in a fashion similar to dead hard disks. Please share info if you know of any such provider. norman ibas? it's a bit expensive operation of course .. -- Eero ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Nagios 3.4.1 on CentOS 5.8
Hi I am trying to build nagios rpm from nagios.spec file on CentOS 5.8. I am getting into issues. nagios.spec http://fpaste.org/crOs/ rpmbuild -ba nagios.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.36485 + umask 022 + cd /usr/src/redhat/BUILD + cd /usr/src/redhat/BUILD + rm -rf nagios-3.4.1 + /bin/gzip -dc /usr/src/redhat/SOURCES/nagios-3.4.1.tar.gz + tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd nagios-3.4.1 /var/tmp/rpm-tmp.36485: line 31: cd: nagios-3.4.1: No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.36485 (%prep) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.36485 (%prep) http://fpaste.org/IYHQ/ which mentions about /var/tmp/rpm-tmp.36485 Any clue? Regards Kaushal ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Nagios 3.4.1 on CentOS 5.8
+ /bin/gzip -dc /usr/src/redhat/SOURCES/nagios-3.4.1.tar.gz + tar -xf - + STATUS=0 Ok, it unpacked. + '[' 0 -ne 0 ']' + cd nagios-3.4.1 /var/tmp/rpm-tmp.36485: line 31: cd: nagios-3.4.1: No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.36485 (%prep) But now it cant cd into the *expected* directory. Either fix the tar file, or amend the spec with the facilities provided that allow for this very circumstance. http://fedoraproject.org/wiki/How_to_create_an_RPM_package#.25prep_section:_.25setup_command ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Nagios 3.4.1 on CentOS 5.8
On Mon, Jun 18, 2012 at 8:38 AM, Joseph L. Casale jcas...@activenetwerx.com wrote: + /bin/gzip -dc /usr/src/redhat/SOURCES/nagios-3.4.1.tar.gz + tar -xf - + STATUS=0 Ok, it unpacked. + '[' 0 -ne 0 ']' + cd nagios-3.4.1 /var/tmp/rpm-tmp.36485: line 31: cd: nagios-3.4.1: No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.36485 (%prep) But now it cant cd into the *expected* directory. Either fix the tar file, or amend the spec with the facilities provided that allow for this very circumstance. http://fedoraproject.org/wiki/How_to_create_an_RPM_package#.25prep_section:_.25setup_command ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Joseph Any clue about http://fpaste.org/mcED/ Regards Kaushal ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fail2ban logrotate [was: Update on spam, postfix, fail2ban, centos 6]
Here is what I had to do to make fail2ban work with centos 6, fail2ban
from epel
This is a long letter and no html to make it read better.
It deals with failed jails during start, loss of ban/unban after systems
logrotates files, errors in jails,
sasl errors, logging file correctly to work with fail2ban and logwatch,
fail2ban logrotate.
I hope this helps others, it was a real bear and the first program/rpm I
used that really does not work very well as set up.
(a update was pushed a few weeks back, not sure how this affects
anything below...mine still works as is.)
Forgive me if I left something out.
first I added these programs to the EPEL repo ( I do not allow any
except those I use, so I use the following to limit the repo.)
includepkgs= fail2ban shorewall shorewall-core python-inotify gamin-python
Fail2ban has recently been updated on the epel repo and shorewall-core
is now needed too, this is new.
How the new updates affects any of the below is beyond me, but I doubt
it changed anything.
1st issue
--
/etc/fail2ban/jail.conf
change line 39 to
backend = gamin
Without this fail2ban will ignore log rotations by logrotate and stay on
the old file in your jails.
This was needed or it failed. No errors, nothing.
Force log rotate did not make this happen, only the program running each
morning did it.
I changed mine to a daily rotate of /var/log/secure,vsftpd.log, etc...
to test this.
Without gamin it failed every time.
(also you need to add this)
line 16 (add your ip (or ip block?) after the 127 ip) Use a space
between them all.
ignoreip = 127.0.0.1 yourip
2nd issue
---
with more than one jail you can (and will) get chances of errors when
starting fail2ban. Some people seem to attribute it centos 6
having an older version of netfilter. The program goes to fast for
iptables and chokes setting up the chains.
Sometimes they all go on, most times I would lose one to two chains
during each restart of fail2ban.
You have to have debug with at least 'info' to see these errors. When
stopping you will get a ton of these errors too, but they seem
to have no effect on anything.
To stop these errors and allow all jails to start properly you have to
add a sleep line deep in the code.
I have not tested since the update to see if this was overwritten but
will do that this week.
/usr/bin/fail2ban-client
Find the following code and add the time.sleep(0.1) in there as I have.
You need to press the tab 3 times to indent it, python pays attention to
white space, it will choke if you do not do this.
add sleep command into the following, (tab three times)
starts at line 142
def __processCmd(self, cmd, showRet = True):
beautifier = Beautifier()
for c in cmd:
time.sleep(0.1)
beautifier.setInputCmd(c)
try:
This lets netfilter catch up with the fail2ban client and allows all
jails to get started properly.
If you only use one jail this would not be needed, but each one after
that offers a chance of not being turned on.
3rd issue
---
The whole log thing is borked.
if you try to use fail2ban.log, fail2ban itself will choke on it.
If you try to use the repo's set up of using /var/log/messages than
logwatch will get borked on it.
However, if you set it all to /var/log/fail2ban as the log file, it will
work.
No matter which way you want it, logwatch, fail2ban, and logrotate all
point to different files for logging and it is a real mess.
Here is what I did to make it log and allow logrotate to work with it.
/etc/fail2ban/fail2ban.conf
line 25
logtarget = /var/log/fail2ban
/etc/logrotate.d/fail2ban
Below I changed the logtarget and stopped the 'restart' the repo wanted.
Thus it will keep running day after day.
/var/log/fail2ban {
missingok
notifempty
rotate 7
create 0600 root root
postrotate
/usr/bin/fail2ban-client set logtarget /var/log/fail2ban 2
/dev/null || true
endscript
}
finally for logwatch
/usr/share/logwatch/default.conf/logfiles/fail2ban.conf
LogFile = fail2ban
Archive = fail2ban-*
--
jails I set up...this is gonna be quick with little info, still writing
notes for the book on this one
I lowered the times in them for this letter, but mine are much higher.
I separated the ports for each for testing and safety. You could make
all the ports blocked if you wanted too.
The first ssh in the repo is enabled by default I think. Make sure if
you use these you check all others to make sure they
are not enabled.
[ssh-iptables]
enabled = true
filter = sshd
action = iptables[name=SSH, port=22444, protocol=tcp]
logpath = /var/log/secure
maxretry = 2
bantime = 3600
[apache-tcp]
enabled = true
filter = apache-auth
bantime = 1
action = iptables[name=ApacheAuth, port=80, protocol=tcp]
logpath = /var/log/httpd/error_log
maxretry = 3
Re: [CentOS] [HW/OT] Recommend vendor to recover data from LTO4tapes
Software We used recently Nucleus to recover an SLR100 tape and we get back about 80% of the surface intact; but you must think that each situation is different. http://www.nucleustechnologies.com/backup-recovery.html An other software but we don't know about it. http://www.kerneldatarecovery.com/buy-tape-backup-recovery.html Recovery service may be useful but we asked for quote and it was a bit heavy; that 's the reason we choose to recover from Nucleus and I think they should haven't been better. http://www.aldownloading.com/data-recovery/LTO-4-ultrium-4-recovery/LTO-4-ultrium-4-restore.htm http://www.krollontrack.com/data-recovery/data-recovery-services/tape-recovery/ Hope it help --- Michel Donais ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
