Search results for query "Linux ./configure"
- 6358 messages
Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6?
by Robinson Tiemuqinke
I've tried with cr kernel, not it moves much faster but still fails -- fails at the partition failure, this setup is S3 backed image.
root (hd0)
Filesystem type is ext2fs, using whole disk
kernel /boot/vmlinuz-2.6.32-131.17.1.el6.x86_64 ro root=/dev/sda1 rd_NO_LUKS rd
_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTY
PE=pc KEYTABLE=us crashkernel=auto crashkernel=auto
initrd /boot/initramfs-2.6.32-131.17.1.el6.x86_64.img
close blk: backend at /local/domain/0/backend/vbd/8/2049
close blk: backend at /local/domain/0/backend/vbd/8/2064
close blk: backend at /local/domain/0/backend/vbd/8/2080
close blk: backend at /local/domain/0/backend/vbd/8/2096
close blk: backend at /local/domain/0/backend/vbd/8/2112
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.32-131.17.1.el6.x86_64 (mockbuild(a)c6b5.bsys.dev.centos.org) (gcc version 4.4.5 20110214 (Red Hat 4.4.5-6) (GCC) ) #1 SMP Thu Oct 6 19:24:09 BST 2011
Command line: ro root=/dev/sda1 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto crashkernel=auto
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
Centaur CentaurHauls
ACPI in unprivileged domain disabled
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 00000000000a0000 (usable)
Xen: 00000000000a0000 - 0000000000100000 (reserved)
Xen: 0000000000100000 - 00000001c0000000 (usable)
DMI not present or invalid.
last_pfn = 0x1c0000 max_arch_pfn = 0x400000000
last_pfn = 0x100000 max_arch_pfn = 0x400000000
init_memory_mapping: 0000000000000000-0000000100000000
init_memory_mapping: 0000000100000000-00000001c0000000
RAMDISK: 02028000 - 0460c000
No NUMA configuration found
Faking a node at 0000000000000000-00000001c0000000
Bootmem setup node 0 0000000000000000-00000001c0000000
NODE_DATA [0000000000008000 - 000000000003bfff]
bootmap [000000000003c000 - 0000000000073fff] pages 38
(8 early reservations) ==> bootmem [0000000000 - 01c0000000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [000540f000 - 000543e000] XEN PAGETABLES ==> [000540f000 - 000543e000]
#2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
#3 [0001000000 - 0002007524] TEXT DATA BSS ==> [0001000000 - 0002007524]
#4 [0002028000 - 000460c000] RAMDISK ==> [0002028000 - 000460c000]
#5 [000460c000 - 000540f000] XEN START INFO ==> [000460c000 - 000540f000]
#6 [0000100000 - 00008d3000] PGTABLE ==> [0000100000 - 00008d3000]
#7 [000543e000 - 0005a41000] PGTABLE ==> [000543e000 - 0005a41000]
Reserving 129MB of memory at 96MB for crashkernel (System RAM: 7168MB)
Zone PFN ranges:
DMA 0x00000001 -> 0x00001000
DMA32 0x00001000 -> 0x00100000
Normal 0x00100000 -> 0x001c0000
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000001 -> 0x000000a0
0: 0x00000100 -> 0x001c0000
SFI: Simple Firmware Interface v0.7 http://simplefirmware.org
SMP: Allowing 8 CPUs, 0 hotplug CPUs
No local APIC present
APIC: disable apic facility
PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
PCI: Warning: Cannot find a gap in the 32bit address range
PCI: Unassigned devices with 32bit resource registers may break!
Allocating PCI resources starting at 1c0100000 (gap: 1c0100000:400000)
Booting paravirtualized kernel on Xen
Xen version: 3.4.3-2.6.18 (preserve-AD)
NR_CPUS:4096 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
PERCPU: Embedded 30 pages/cpu @ffff88002804f000 s92504 r8192 d22184 u122880
pcpu-alloc: s92504 r8192 d22184 u122880 alloc=30*4096
pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7
Xen: using vcpu_info placement
Built 1 zonelists in Node order, mobility grouping on. Total pages: 1807817
Policy zone: Normal
Kernel command line: ro root=/dev/sda1 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto crashkernel=129M@0M
PID hash table entries: 4096 (order: 3, 32768 bytes)
Checking aperture...
No AGP bridge found
AMD-Vi disabled by default: pass amd_iommu=on to enable
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Placing 64MB software IO TLB between ffff880020000000 - ffff880024000000
software IO TLB at phys 0x20000000 - 0x24000000
Memory: 6955572k/7340032k available (5013k kernel code, 388k absent, 384072k reserved, 7291k data, 1232k init)
Hierarchical RCU implementation.
NR_IRQS:33024 nr_irqs:336
Console: colour dummy device 80x25
console [tty0] enabled
console [hvc0] enabled
...
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
registered taskstats version 1
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vbd/2064
XENBUS: Device with no driver: device/vbd/2080
XENBUS: Device with no driver: device/vbd/2096
XENBUS: Device with no driver: device/vbd/2112
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/console/0
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Initalizing network drop monitor service
Freeing unused kernel memory: 1232k freed
Write protecting the kernel read-only data: 10240k
Freeing unused kernel memory: 1112k freed
Freeing unused kernel memory: 1796k freed
dracut: dracut-004-33.2.el6_0
dracut: rd_NO_LUKS: removing cryptoluks activation
dracut: rd_NO_LVM: removing LVM activation
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.20.6-ioctl (2011-02-02) initialised: dm-devel(a)redhat.com
udev: starting version 147
dracut: Starting plymouth daemon
dracut: rd_NO_DM: removing DM RAID activation
dracut: rd_NO_MD: removing MD RAID activation
xlblk_init: register_blkdev major: 202
blkfront: xvde1: barriers disabled
blkfront: xvdf: barriers disabled
xvdf:
unknown partition table
blkfront: xvdg: barriers disabled
xvdg: unknown partition table
blkfront: xvdh: barriers disabled
xvdh: unknown partition table
blkfront: xvdi: barriers disabled
xvdi: unknown partition table
Boot has failed, sleeping forever.
________________________________
From: Robinson Tiemuqinke <hahaha_30k(a)yahoo.com>
To: Johnny Hughes <johnny(a)centos.org>
Cc: CentOS mailing list <centos(a)centos.org>
Sent: Wednesday, November 23, 2011 10:48 AM
Subject: Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6?
Hi Johnny,
Thanks a lot. I'll upgrade kernel to the cr repository, and give it a try now.
--Guolin
________________________________
From: Johnny Hughes <johnny(a)centos.org>
To: centos(a)centos.org
Sent: Wednesday, November 23, 2011 9:55 AM
Subject: Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6?
On 11/23/2011 11:40 AM, Robinson Tiemuqinke wrote:
> I tried several ways but still no help. The following are the output (stock Centos 6 2.6.32-71.29.1.el6.x86_64 kernel), grub works fine and it located kernel and initial ramdisk. but kernel booting faied at the very beginning...
>
> Any suggestions are more than appreciated.
>
>
> --------------------------------------------------
>
> 2011-11-23T17:19:21+0000
> Xen Minimal OS!
> start_info: 0x1890000(VA)
> nr_pages: 0x1e0000
> shared_inf: 0xb2cea000(MA)
> pt_base: 0x1893000(VA)
> nr_pt_frames: 0x11
> mfn_list: 0x990000(VA)
> mod_start: 0x0(VA)
> mod_len: 0
> flags: 0x0
> cmd_line: root=/dev/sda1 ro 4
> stack: 0x94f860-0x96f860
> MM: Init
> _text: 0x0(VA)
> _etext: 0x6000d(VA)
> _erodata: 0x78000(VA)
> _edata: 0x80b00(VA)
> stack start: 0x94f860(VA)
> _end: 0x98fe68(VA)
> start_pfn: 18a7
> max_pfn: 1e0000
> Mapping memory range 0x1c00000 - 0x1e0000000
> setting 0x0-0x78000 readonly
> skipped 0x1000
> MM: Initialise page allocator for 27a0000(27a0000)-1e0000000(1e0000000)
> MM: done
> Demand map pfns at 1e0001000-21e0001000.
> Heap resides at 21e0002000-41e0002000.
> Initialising timer interface
> Initialising console ... done.
> gnttab_table mapped at 0x1e0001000.
> Initialising scheduler
> Thread "Idle": pointer: 0x21e0002010, stack: 0x36f0000
> Initialising xenbus
> Thread "xenstore": pointer: 0x21e00027c0, stack: 0x3700000
> Dummy main: start_info=0x96f960
> Thread "main": pointer: 0x21e0002f70, stack: 0x3710000
> "main" "root=/dev/sda1" "ro" "4"
> vbd 2049 is hd0
> ******************* BLKFRONT for device/vbd/2049 **********
>
>
> backend at /local/domain/0/backend/vbd/162/2049
> Failed to read /local/domain/0/backend/vbd/162/2049/feature-barrier.
> Failed to read /local/domain/0/backend/vbd/162/2049/feature-flush-cache.
> 20971520 sectors of 512 bytes
> **************************
> vbd 2064 is hd1
> ******************* BLKFRONT for device/vbd/2064 **********
>
>
> backend at /local/domain/0/backend/vbd/162/2064
> Failed to read /local/domain/0/backend/vbd/162/2064/feature-barrier.
> Failed to read /local/domain/0/backend/vbd/162/2064/feature-flush-cache.
> 880732160 sectors of 512 bytes
> **************************
> vbd 2080 is hd2
> ******************* BLKFRONT for device/vbd/2080 **********
>
>
> backend at /local/domain/0/backend/vbd/162/2080
> Failed to read /local/domain/0/backend/vbd/162/2080/feature-barrier.
> Failed to read /local/domain/0/backend/vbd/162/2080/feature-flush-cache.
> 880732160 sectors of 512 bytes
> **************************
> [H[J
> GNU GRUB version 0.97 (7864320K lower / 0K upper memory)
>
> [m[4;2H+-------------------------------------------------------------------------+[5;2H|[5;76H|[6;2H|[6;76H|[7;2H|[7;76H|[8;2H|[8;76H|[9;2H|[9;76H|[10;2H|[10;76H|[11;2H|[11;76H|[12;2H|[12;76H|[13;2H|[13;76H|[14;2H|[14;76H|[15;2H|[15;76H|[16;2H|[16;76H|[17;2H+-------------------------------------------------------------------------+[m
> Use the ^ and v keys to select which entry is highlighted.
> Press enter to boot the selected OS, 'e' to edit the
> commands before booting, or 'c' for a command-line.[5;78H [m[7m[5;3H CentOS (2.6.32-71.29.1.el6.x86_64) [5;75H[m[m[6;3H [6;75H[m[m[7;3H [7;75H[m[m[8;3H [8;75H[m[m[9;3H
> [9;75H[m[m[10;3H [10;75H[m[m[11;3H [11;75H[m[m[12;3H [12;75H[m[m[13;3H [13;75H[m[m[14;3H
> [14;75H[m[m[15;3H [15;75H[m[m[16;3H [16;75H[m[16;78H [5;75H[23;4H The highlighted entry will be booted automatically in 5 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 4 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 3 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 2 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 1 seconds. [5;75H[H[J Booting 'CentOS (2.6.32-71.29.1.el6.x86_64)'
>
> root (hd0)
> Filesystem type is ext2fs, using whole disk
>
> kernel /boot/vmlinuz-2.6.32-71.29.1.el6.x86_64 ro root=/dev/sda1 rhgb quiet
> initrd /boot/initramfs-2.6.32-71.29.1.el6.x86_64.img
>
> close blk: backend at /local/domain/0/backend/vbd/162/2049
> close blk: backend at /local/domain/0/backend/vbd/162/2064
> close blk: backend at /local/domain/0/backend/vbd/162/2080
> PCI: Warning: Cannot find a gap in the 32bit address range
> PCI: Unassigned devices with 32bit resource registers may break!
> PCI: Fatal: No config space access function found
>
> Boot has failed, sleeping forever.
>
>
>
>
>
>
> ________________________________
> From: Robinson Tiemuqinke <hahaha_30k(a)yahoo.com>
> To: CentOS mailing list <centos(a)centos.org>
> Sent: Tuesday, November 22, 2011 3:35 PM
> Subject: [CentOS] EC2 compatible kernel for centos 6?
>
> Hi all,
>
> I'm just scrambling to collect clues to build an Amazon AWS AMI based on Centos 6. the AWS PV-GRUB kernel loads my kernel but failed immediately. I'm using stock Centos 6 kernel 2.6.32-71.29.1.el6. and the kernel seems have xen? support? My questions are:
>
> 1, Are the centos 6 stock kernels, like kernel-2.6.32-71.29.1.el6.x86_64, EC2 compatible?
>
> 2, If the answer to the above #1 question is NO, the are the centos plus kernels, like kernel-2.6.32-71.29.1.el6.centos.plus.x86_64, EC2 compatible?
>
> 3, If the answers to both above are 'NO', then Are there any instructions to build a EC2 kernel based on kernel source RPMs?
>
>
> Any help are greatly appreciated.
>
> --Tie
I do not use amazon services, but does this help:
https://forums.aws.amazon.com/thread.jspa?threadID=78007
_______________________________________________
CentOS mailing list
CentOS(a)centos.org
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS(a)centos.org
http://lists.centos.org/mailman/listinfo/centos
14 years, 4 months
Re: [CentOS-es] Configurar Telefono Cisco 7940G !
by angel jauregui
@Andres vaya :D, se agradece la puesta antencion a mi problema.
Y efectivamente, estoy mostrando el DHCP en busca de opinion...
Hasta ahorita ya consegui que los dos telefonos funcionen, y en base a la
experiencia que obtuve, el procedimiento generico de un CISCO 7940g es:
1- enciende el telefono y autoconfigura VLAN.
2- pide IP.
3- debe configurarse el DHCP Server con la direccion del TFTP y los "code"
request que mencione.
4- una vez asignada la IP, el telefono consulta al TFTP por el
SIPDefault.cnf.xml
5- El miso SIPDefault contiene el nombre del Firmware a cargar.
6- El telefono consulta el firmware que se le indico.
7- el telefono se reinicia.
8- El telefono incia con el firmware cargado en su flash memorya, por
ende *ahora
si veras la leyenda de* "SIP".
9- El telefono consulta por la configuracion de el mismo:
SIPMACDELTELEFONO.cnf
10- aplica la configruacion y listo :D
Los modelos mas recientes piden SIPMACDELTELEFONO.cnf.xml, en este caso el
CISCO 9740 basta con el CNF.
Doy este tema por terminado, ya que los telefonos estan al 100% con su SIP.
En el sig hilo que abrire, sera sobre el modulo que se carga de Asterisk en
el CISCO, que al parecer "segun el manual" debe tomarse el archvio
"skinny.conf".
Saludos !
El 12 de noviembre de 2013 14:23, Andres Genovez
<andresgenovez(a)gmail.com>escribió:
> Estimado EPE pidiendote las disculpas necesarias, en realidad el compañero
> está subiendo su tftp y dhcp en CentOS, me imagino ;)
>
> Angel te paso la configuración SIPBLABLABLA.cnf
> ---code-----------
> image_version: P0S3-08-11-00
> line1_name: "906"
> line1_authname: "906"
> line1_shortname: "DT"
> line1_password: "hackme"
> line1_displayname: "DT"; no utilizar nombres largos, caracteres especiales
> o sino sale como UNPROVISIONED
> proxy1_port: "5060"
> proxy1_address: "172.16.289.254"
> nat_enable: "1"
> outbound_proxy: "172.16.289.254"
> outbound_proxy_port: "5060"
> proxy_register: "1"
> timer_register_expires: "1"
> sntp_mode: "directedbroadcast"
> sntp_server: "133.300.400.1"; servidor de hora
> time_zone: "CST"
> time_format_24hr: "1"
> phone_label: "sietepingas.com " ; add a space at the end, looks neater
> phone_password: "cisco" ; Limited to 31 characters (Default - cisco)
> user_info: none
> telnet_level: 2
> logo_url: "http://192.887.988.400/logo-pepito.bmp"
> ----code--------------
>
> Obvio las ips son ficticias las tendrás que colocar de acuerdo a tus
> configuraciones.
>
> Saludos.
>
>
>
> El 12 de noviembre de 2013 10:42, angel jauregui
> <darkdiabliyo(a)gmail.com>escribió:
>
> > LEs confirmo que ya pude hacer que se descargara el firmware al telefono
> y
> > pusiera la vendita leyenda de "SIP".
> >
> > El problema estaba en mi DHCP, les dejo mi configuracion:
> >
> > *shell# cat /etc/dhcp/dhcpd.conf*
> > ddns-update-style interim;
> > ddns-updates on;
> > ddns-domainname "midominio.com";
> > ddns-rev-domainname "in-addr.arpa.";
> > ignore client-updates;
> > authoritative;
> > default-lease-time 600;
> > max-lease-time 7200;
> > option ip-forwarding off;
> > option domain-name "midominio.com";
> > option tftp-server-name "10.0.1.1";
> > option boot-server code 66 = string;
> > option boot-server "10.0.1.1";
> > option option-66 code 66 = text;
> > option option-67 code 67 = text;
> > option vlan-flag code 190 = unsigned integer 8;
> > option voice-vlan-id code 191 = unsigned integer 16;
> > option data-vlan-id code 192 = unsigned integer 16;
> > # option voip-tftp-servers 10.0.1.1;
> > # option voip-tftp-servers code 150 = ip-address;
> > option ntp-servers 0.pool.ntp.org, 1.poo.ntp.org, 2.pool.ntp.org,
> > 3.pool.ntp.org;
> > log-facility local7;
> > allow bootp;
> > allow booting;
> >
> > include "/etc/rndc.key";
> >
> > zone 1.0.10.in-addr.arpa. {
> > primary 127.0.0.1;
> > key rndc-key;
> > }
> >
> > zone midominio.com. {
> > primary 127.0.0.1;
> > key rndc-key;
> > }
> >
> > shared-network midominiocom {
> > subnet 10.0.1.0 netmask 255.255.255.0 {
> > option routers 10.0.1.1;
> > option subnet-mask 255.255.255.0;
> > option broadcast-address 10.0.1.255;
> > option domain-name-servers ns1.midominio.com;
> > option netbios-name-servers 10.0.1.1;
> > range 10.0.1.100 10.0.1.150;
> > filename "pxelinux.0";
> > }
> > host diabliyo {
> > option host-name "diabliyo.midominio.com";
> > hardware ethernet 44:1E:A1:D7:B7:83;
> > fixed-address 10.0.1.10;
> > }
> > host diabliyo2 {
> > option host-name "diabliyo2.midominio.com";
> > hardware ethernet AC:81:12:92:34:12;
> > fixed-address 10.0.1.11;
> > }
> > host ciscophone1 {
> > option host-name "ciscophone1.midominio.com";
> > hardware ethernet 00:14:F2:AE:65:29;
> > fixed-address 10.0.1.201;
> > next-server 10.0.1.1;
> > # filename "XMLDefault.cnf.xml";
> > }
> > host ciscophone2 {
> > option host-name "ciscophone2.midominio.com";
> > hardware ethernet 00:15:63:4D:22:CE;
> > fixed-address 10.0.1.202;
> > next-server 10.0.1.1;
> > }
> >
> >
> > Y los archivos que mantengo en el /home/tftp son:
> >
> > *shell# ls -l /home/tftp*
> > XMLDefault.cnf.xml
> > SIPDefault.cnf
> > SEPAABBCCDDEEFF.cnf
> > SEPAABBCCDDEEFF.cnf.xml
> > P0S3-8-12-00.sb2
> > P0S3-8-12-00.loads
> > P0S3-8-12-00.sbn
> > P0S3-8-12-00.bin
> > OS79XX.TXT
> > List.xml
> > dialplan.xml
> > cmterm-7940-7960-8.2.00-sip.cop
> >
> > Aun me falta configurar bien el SEPAABBCCDDEEFF.cnf y
> > SEPAABBCCDDEEFF.cnf.xml que es el que carga la configuración especifica
> > para el telefono con mac AA:BB:CC:DD:EE:FF.
> >
> > En cuanto quede les paso contenido de los archivos ya testeado y
> > funcionando :D
> >
> > *Quiero agregar* que uno de los 2 (dos) teléfonos continua teniendo
> > problemas, vaya después de resetearlo hace solo esto:
> >
> > - Configuring VLAN
> > - Configuring IP
> > - Protocol Application Invalid.
> >
> > En cambio el otro telefono, SI pasa a la parte de cargar el Firmware y lo
> > demas...
> >
> > Saludos !
> >
> >
> > El 12 de noviembre de 2013 08:23, angel jauregui
> > <darkdiabliyo(a)gmail.com>escribió:
> >
> > > @Gerardo algo lei sobre el firmware SIP y que para identificarlo debe
> > > aparecer en laparte superior de la pantalla, pero *no veo nada* que
> diga
> > > SIP, es solo una bara negra...
> > >
> > > Aparte no logro se conecte al TFTP :S, ya que en las opciones donde
> dice
> > > "TFTP Server" esta vacio :'(. Se supone debe mencionar la direccion de
> mi
> > > TFTP, pero nada.
> > >
> > > Por esta misma razon puse la configuracion de mi TFTP (en la primer
> > > publicacion), ya que no consigo se baje el Firmaware que subi al TFTP
> > > (/home/tftp/)
> > >
> > > Saludos !
> > >
> > >
> > > El 11 de noviembre de 2013 21:10, Gerardo Barajas <
> > > gerardo.barajas(a)gmail.com> escribió:
> > >
> > > Ya tienes el firmware para SIP?
> > >> On Nov 11, 2013 6:27 PM, "angel jauregui" <darkdiabliyo(a)gmail.com>
> > wrote:
> > >>
> > >> > Encontre este sitio donde hay un monton de Firmwares
> > >> > http://files.domoticaforum.eu/Cisco/Firmware/7960/
> > >> > Pero aun no puedo cargarle nada :(... vaya me baje el archivo "
> > >> > P0S3-8-12-00.zip<
> > >> > http://files.domoticaforum.eu/Cisco/Firmware/7960/P0S3-8-12-00.zip
> >",
> > >> > despues cree el directorio del TFTP los archivos:
> > >> >
> > >> > shell# ls -l /home/tftp/
> > >> > OS79XX.TXT
> > >> > P003-8-12-00.bin
> > >> > P003-8-12-00.sbin
> > >> > P003-8-12-00.loads
> > >> > P003-8-12-00.sb2
> > >> > SEPaabbddcceeff.cnf.xml
> > >> > SEPaabbddcceeff.cnf
> > >> >
> > >> > El ZIP que les comente anteriormente me provee los archivo *.bin,
> > >> *.sbin,
> > >> > *.loas y *.sb2...
> > >> > El XML y CNF lo arme con este ejemplo:
> > >> >
> > >> > XML -->
> > >> >
> http://www.minded.ca/wp-content/uploads/2009/12/SEP7940.cnf_.xml_.txt
> > >> > CNF -->
> > >> http://www.minded.ca/wp-content/uploads/2009/12/SIP7940.cnf_.txt
> > >> >
> > >> > Pero dejo pendiente el resultado, ya que me sali d la ofi y no probe
> > >> > reiniciar el telefono.
> > >> >
> > >> > Hasta aqui, voy bien (teoricamente) ??? me falta algo ?
> > >> >
> > >> > Saludos !
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > El 11 de noviembre de 2013 15:50, Andres Genovez
> > >> > <andresgenovez(a)gmail.com>escribió:
> > >> >
> > >> > > Basicamente el proceso es similar,
> > >> > >
> > >> > > http://www.crice.org/?q=node/444
> > >> > >
> > >> > > Solo que tendría que conseguir el Firmware del 7940,
> > >> > >
> > >> > > Saludos.
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > El 11 de noviembre de 2013 16:46, angel jauregui
> > >> > > <darkdiabliyo(a)gmail.com>escribió:
> > >> > >
> > >> > > > Buenas.
> > >> > > >
> > >> > > > Acabo de conseguir un par de teléfonos Cisco 7940G que quiero
> > >> echarlos
> > >> > > > andar con asterisk+freepbx. Antes de entrar a asterisk+freepbx
> > >> quisiera
> > >> > > por
> > >> > > > favor me orientaras sobe las configuraciones que tengo que hacer
> > con
> > >> > los
> > >> > > > teléfonos CISCO.
> > >> > > >
> > >> > > > Estuve buscando en Google y leyendo, pero al parecer muchos
> > >> ejemplos de
> > >> > > > basan en una version de firmware que es mayor a la que tienen
> mis
> > >> > > > teléfonos.
> > >> > > >
> > >> > > > En fin, todas son *suposiciones....* el manual que estoy
> siguiendo
> > >> es
> > >> > > este:
> > >> > > >
> > >> >
> > >>
> > http://www.minded.ca/2009-12-16/configure-cisco-ip-phones-with-asterisk/
> > >> > > >
> > >> > > > Hasta ahorita tengo esto:
> > >> > > >
> > >> > > > 1- Montado mi servidor DNS y asignando IP's a mis equipos. En
> > >> > especifico
> > >> > > > para los teléfonos (son 2), por MAC les estoy dando un IP
> > >> especifico:
> > >> > > > 10.0.1.201 y 10.0.1.202.
> > >> > > >
> > >> > > > 2- El dns esta configurado asi:
> > >> > > >
> > >> > > > *shell# cat /etc/dhcp/dhcpd.conf*
> > >> > > > ddns-update-style interim;
> > >> > > > ddns-updates on;
> > >> > > > ddns-domainname "midominio.com";
> > >> > > > ddns-rev-domainname "in-addr.arpa.";
> > >> > > > ignore client-updates;
> > >> > > > authoritative;
> > >> > > > default-lease-time 600;
> > >> > > > max-lease-time 7200;
> > >> > > > option ip-forwarding off;
> > >> > > > option domain-name "midominio.com";
> > >> > > > option ntp-servers 0.pool.ntp.org, 1.poo.ntp.org,
> 2.pool.ntp.org,
> > >> > > > 3.pool.ntp.org;
> > >> > > > log-facility local7;
> > >> > > > allow bootp;
> > >> > > > allow booting;
> > >> > > >
> > >> > > > include "/etc/rndc.key";
> > >> > > >
> > >> > > > zone 1.0.10.in-addr.arpa. {
> > >> > > > primary 127.0.0.1;
> > >> > > > key rndc-key;
> > >> > > > }
> > >> > > >
> > >> > > > zone midominio.com. {
> > >> > > > primary 127.0.0.1;
> > >> > > > key rndc-key;
> > >> > > > }
> > >> > > >
> > >> > > > shared-network midominio {
> > >> > > > subnet 10.0.1.0 netmask 255.255.255.0 {
> > >> > > > option routers 10.0.1.1;
> > >> > > > option subnet-mask 255.255.255.0;
> > >> > > > option broadcast-address 10.0.1.255;
> > >> > > > option domain-name-servers ns1.midominio.com;
> > >> > > > option netbios-name-servers 10.0.1.1;
> > >> > > > range 10.0.1.100 10.0.1.150;
> > >> > > > filename "pxelinux.0";
> > >> > > > }
> > >> > > >
> > >> > > > host ciscophone1 {
> > >> > > > option host-name "ciscophone1.midominio.com";
> > >> > > > hardware ethernet aa:bb:cc:dd:ee:ff;
> > >> > > > fixed-address 10.0.1.201;
> > >> > > > filename "XMLDefault.cnf.xml";
> > >> > > > }
> > >> > > >
> > >> > > > host ciscophone2 {
> > >> > > > option host-name "ciscophone1.midominio.com";
> > >> > > > hardware ethernet gg:hh:ii:jj:kk:ll;
> > >> > > > fixed-address 10.0.1.201;
> > >> > > > filename "XMLDefault.cnf.xml";
> > >> > > > }
> > >> > > >
> > >> > > > Alguien puede orientarme ?
> > >> > > > Como ven tengo activalo el PXEBoot, ya que para equipos en red
> > puedo
> > >> > > > reinstalar linux o alguna ISO de respaldo en caliente.
> > >> > > >
> > >> > > > Por el lado de los telefonos, solo se les asigna el IP que le
> > >> > > corresponde,
> > >> > > > pero nadamas :S.... no sale el XML que se supone carge ni nada
> :S
> > >> > > >
> > >> > > > Saludos !
> > >> > > >
> > >> > > > --
> > >> > > > M.S.I. Angel Haniel Cantu Jauregui.
> > >> > > >
> > >> > > > Celular: (011-52-1)-899-871-17-22
> > >> > > > E-Mail: angel.cantu(a)sie-group.net
> > >> > > > Web: http://www.sie-group.net/
> > >> > > > Cd. Reynosa Tamaulipas.
> > >> > > > _______________________________________________
> > >> > > > CentOS-es mailing list
> > >> > > > CentOS-es(a)centos.org
> > >> > > > http://lists.centos.org/mailman/listinfo/centos-es
> > >> > > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > --
> > >> > > Atentamente
> > >> > >
> > >> > > Andrés Genovez Tobar / DTIT
> > >> > > Tel: 842388 ext 177
> > >> > > Perfil profesional http://lnkd.in/gcdhJE
> > >> > > _______________________________________________
> > >> > > CentOS-es mailing list
> > >> > > CentOS-es(a)centos.org
> > >> > > http://lists.centos.org/mailman/listinfo/centos-es
> > >> > >
> > >> >
> > >> >
> > >> >
> > >> > --
> > >> > M.S.I. Angel Haniel Cantu Jauregui.
> > >> >
> > >> > Celular: (011-52-1)-899-871-17-22
> > >> > E-Mail: angel.cantu(a)sie-group.net
> > >> > Web: http://www.sie-group.net/
> > >> > Cd. Reynosa Tamaulipas.
> > >> > _______________________________________________
> > >> > CentOS-es mailing list
> > >> > CentOS-es(a)centos.org
> > >> > http://lists.centos.org/mailman/listinfo/centos-es
> > >> >
> > >> _______________________________________________
> > >> CentOS-es mailing list
> > >> CentOS-es(a)centos.org
> > >> http://lists.centos.org/mailman/listinfo/centos-es
> > >>
> > >
> > >
> > >
> > > --
> > > M.S.I. Angel Haniel Cantu Jauregui.
> > >
> > > Celular: (011-52-1)-899-871-17-22
> > > E-Mail: angel.cantu(a)sie-group.net
> > > Web: http://www.sie-group.net/
> > > Cd. Reynosa Tamaulipas.
> > >
> >
> >
> >
> > --
> > M.S.I. Angel Haniel Cantu Jauregui.
> >
> > Celular: (011-52-1)-899-871-17-22
> > E-Mail: angel.cantu(a)sie-group.net
> > Web: http://www.sie-group.net/
> > Cd. Reynosa Tamaulipas.
> > _______________________________________________
> > CentOS-es mailing list
> > CentOS-es(a)centos.org
> > http://lists.centos.org/mailman/listinfo/centos-es
> >
>
>
>
> --
> Atentamente
>
> Andrés Genovez Tobar / DTIT
> Tel: 842388 ext 177
> Perfil profesional http://lnkd.in/gcdhJE
> _______________________________________________
> CentOS-es mailing list
> CentOS-es(a)centos.org
> http://lists.centos.org/mailman/listinfo/centos-es
>
--
M.S.I. Angel Haniel Cantu Jauregui.
Celular: (011-52-1)-899-871-17-22
E-Mail: angel.cantu(a)sie-group.net
Web: http://www.sie-group.net/
Cd. Reynosa Tamaulipas.
12 years, 4 months
Re: [CentOS-pt-br] Cluster no CentOS. Ajuda..
by CássioElias .
Viche Antônio, fiz um negocio aqui e não estou entendendo.
Os servidores estavam funcionando perfeitamente. Fui tentar então ativar o firewall do CentOS para ir já normalizando tudo de uma forma mais segura.
Peguei as portas configuradas para os serviços do DRBD e do Corosync e fui liberar no gui do Firewall.
Rebootei as máquinas e veio o B.O....
Agora as máquinas estão sim funcionando como master e slave. Só que não sai disso aqui:
URANO 1:
[root@urano1 ~]# cat /proc/drbdversion: 8.3.15 (api:88/proto:86-97)GIT-hash: 0ce4d235fc02b5c53c1c52c53433d11a694eab8c build by phil@Build64R6, 2012-12-20 20:09:51 0: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----- ns:0 nr:0 dw:116 dr:3553 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:200 1: cs:StandAlone ro:Primary/Unknown ds:UpToDate/DUnknown r----- ns:0 nr:0 dw:4 dr:1085 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:4
URANO 2:
[root@urano2 ~]# cat /proc/drbdversion: 8.3.15 (api:88/proto:86-97)GIT-hash: 0ce4d235fc02b5c53c1c52c53433d11a694eab8c build by phil@Build64R6, 2012-12-20 20:09:51 0: cs:StandAlone ro:Secondary/Unknown ds:UpToDate/DUnknown r----- ns:0 nr:0 dw:456 dr:7709 al:5 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:176 1: cs:StandAlone ro:Secondary/Unknown ds:UpToDate/DUnknown r----- ns:0 nr:0 dw:100 dr:2525 al:4 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:80
Os serviços do corosync+pacemaker estão de boa. Mas não há mais sincronização entre os servidores. Ao que parece o DRBD não está mais entendendo os servidores. Fiz um teste de criar um arquivo no primário e colocar ele em standby, mas no secundário o arquivo não aparece. Ele não sincroniza mais.
Tem alguma sugestão?
> Date: Mon, 9 Sep 2013 08:12:10 -0300
> From: asmartins(a)uem.br
> To: centos-pt-br(a)centos.org
> Subject: Re: [CentOS-pt-br] Cluster no CentOS. Ajuda..
>
>
> ----- "CássioElias ." <cassioelias(a)hotmail.com> escreveu:
>
> > De: "CássioElias ." <cassioelias(a)hotmail.com>
> > Para: "Lista de Discussão CentOS-BR" <centos-pt-br(a)centos.org>
> > Enviadas: Segunda-feira, 9 de Setembro de 2013 7:28:46 (GMT-0300) Auto-Detected
> > Assunto: Re: [CentOS-pt-br] Cluster no CentOS. Ajuda..
> >
> > Por exemplo Antônio. Se eu fizesse assim
> >
> >
> > Servidor 1 = urano1
> > Servidor 2 = urano2
> > Servidor 3 = urano3
> >
> >
> > Durante todo o dia, o servico do drbd estaria parado no servidor
> > urano3. Dai a meia noite eu daria um stop no serviço do drbd no
> > servidor urano2 e daria um start no serviço do drbd no servidor
> > urano3. Funcionaria assim também? Somente dando start e stop ?
>
>
> Olá Cássio,
>
> Bem, existem algumas formas de se fazer isso. A primeira é usar um
> recurso do DRBD aqui: http://www.drbd.org/users-guide-8.3/s-three-nodes.html
>
> Você teria uma sincronização entre 1 e 2, e outra entre o disco já
> replicado e 3. Funciona, mas não é exatamente como a sincronização, e para
> 3 ser usado deverá ser de forma manual. Mas, como é para uma recuperação de
> desastre é uma forma muito bom. Tenho um colega que tem os servidores 1 e 2
> lado a lado, e o 3 em outro prédio.
>
> Outra forma, que pode facilitar a recuperação, é ter em 1 dois arquivos de
> configuração, o primeiro para a operação normal entre 1 e 2, e outro para o
> "backup", entre 1 e 3. Ai durante a noite, para o drbd em 1 e 2, altera o arquivo
> e sobre entre 1 e 3. Após sincronizar, volta ao estado original. Caso ocorra uma
> pane em 1, pode-se sincronizar 2 e 3.
>
> Espero não ter lhe confundido ainda mais. Mas, o método na documentação do DRBD
> é o que vai funcionar de forma mais simples.
>
> Att.,
>
> Antonio.
>
>
> >
> >
> > > Date: Fri, 6 Sep 2013 08:28:30 -0300
> > > From: asmartins(a)uem.br
> > > To: centos-pt-br(a)centos.org
> > > Subject: Re: [CentOS-pt-br] Cluster no CentOS. Ajuda..
> > >
> > > Olá Cássio,
> > >
> > > Legal que funcionou! Como lhe disse, temos máquinas aqui funcionando
> > já a um bom tempo!
> > >
> > > Quanto a replicação para mais de 2 nós, tem com 3 (um backup) veja:
> > http://www.drbd.org/users-guide-8.3/s-three-way-repl.html
> > >
> > > E com imaginação dá para fazer muita coisa também! Como o tempo de
> > sync do DRBD não é muito grande
> > > se a quantidade de alterações de seus dados não for enorme, você
> > pode montar um
> > > esquema em que, p.ex., toda noite, você "troca" o nó secundário,
> > sincronizando com outros nós.
> > > Dai em caso de uma perda total do hardware do primário, você já tem
> > outra máquina para assumir.
> > >
> > > Att.,
> > >
> > > Antonio.
> > >
> > > ----- "CássioElias ." <cassioelias(a)hotmail.com> escreveu:
> > >
> > > > De: "CássioElias ." <cassioelias(a)hotmail.com>
> > > > Para: "Lista de Discussão CentOS-BR" <centos-pt-br(a)centos.org>
> > > > Enviadas: Sexta-feira, 6 de Setembro de 2013 8:16:53 (GMT-0300)
> > Auto-Detected
> > > > Assunto: Re: [CentOS-pt-br] Cluster no CentOS. Ajuda..
> > > >
> > > > É...vivendo e tentando aprender.... XD.
> > > >
> > > >
> > > > Acredito que a saga do Cluster no CentOS 6 chegou ao fim Antônio.
> > > > Ontem fiquei até 00:00 "brincando" um pouco nesses servidores e
> > nas
> > > > replicações.
> > > > Agora está funcionando beleza. Os servidores fazem a ajuda entre
> > si e
> > > > as replicações. As replicações está perfeitas. Configurei tudo
> > ontem
> > > > no pacemaker. O failover também está perfeito. Quando uma estação
> > cái,
> > > > ou entra em standby a outra assume na hora.
> > > > Fiz tudo em 2 máquinas virtuais criadas no VMWare ESXi.
> > > > O ideal era eu deixar uma virtual e outra em Servidor Físico. Mas
> > isso
> > > > eu vejo com a parte financeira da empresa depois..hehe.
> > > >
> > > >
> > > > Outra pergunta, o DRBD não trabalha com mais de 2 servidores não
> > né?
> > > > Andei lendo que ele trabalha apenas com 2 servidores. Se quiser
> > > > trabalhar com mais de 2 tem que ser com a ferramenta paga deles.
> > > >
> > > >
> > > > Bom, veja como ficou minhas configurações:
> > > >
> > > >
> > > > Informações do Servidor Urano1 que são as mesmas do Urano2:
> > > >
> > > >
> > > >
> > > > [root@urano1 ~]# uname -a
> > > > Linux urano1 2.6.32-358.18.1.el6.x86_64 #1 SMP Wed Aug 28 17:19:38
> > UTC
> > > > 2013 x86_64 x86_64 x86_64 GNU/Linux
> > > >
> > > >
> > > >
> > > > # /etc/corosync/corosync.conf
> > > >
> > > >
> > > > #Opção do protocolo totem
> > > > totem {
> > > > version: 2
> > > >
> > > >
> > > > #Tempo para verificar perca de pacotes em (ms)
> > > > token: 3000
> > > >
> > > >
> > > > #Quantas verificações antes de gerar notificações
> > > > token_retransmits_before_loss_const: 10
> > > >
> > > >
> > > > #Quanto tempo esperar para agrupar as notificações em (ms)
> > > > join: 60
> > > >
> > > >
> > > > #Quanto tempo esperar para uma solução antes de começar uma nova
> > > > verificação (ms)
> > > > consensus: 3600
> > > >
> > > >
> > > > #Filtro de sincronismo virtual desabilitado
> > > > vsftype: none
> > > >
> > > >
> > > > #Número de mensagens processadas na recepção de pacotes
> > > > max_messages: 20
> > > >
> > > >
> > > > #Limite de cluster assinados
> > > > clear_node_high_bit: yes
> > > >
> > > >
> > > > #Criptografia desabilitada
> > > > secauth: off
> > > >
> > > >
> > > > #Quantas threads usadas para criptografar/descriptografar
> > > > threads: 0
> > > >
> > > >
> > > > #Atribui ID em um cluster fixo (opcional)
> > > > # nodeid: 1234
> > > >
> > > >
> > > > #Especifica que em modo de redundancia, não pode havar nenhum
> > cluster
> > > > ativo ou passivo.
> > > > rrp_mode: none
> > > >
> > > >
> > > > interface {
> > > > #Número de clusters (0 default)
> > > > ringnumber: 0
> > > > #Início de ips utilizados por cluster 10.101.0.0 é 10.101.0.0/24
> > aqui
> > > > mude para
> > > > #O endereço da sua rede ex: 192.168.0.0 que seria 192.168.0.0/24
> > > > bindnetaddr: 192.168.0.0
> > > > #Fim de ips utilizados por cluster
> > > > mcastaddr: 226.94.1.1
> > > > #Porta utilizaad pelo corosync
> > > > mcastport: 5405
> > > > }
> > > > }
> > > >
> > > >
> > > > #Configuração de AIS Availability Management Framework
> > > > amf {
> > > > mode: disabled
> > > > }
> > > >
> > > >
> > > > service {
> > > > #Carregamento do serviço para gerenciamento
> > > > ver: 1
> > > > name: pacemaker
> > > > }
> > > >
> > > >
> > > > #Temos que setar o usuário e grupo como root para o ais ser capaz
> > de
> > > > gerenciar os recursos do pacemaker
> > > > aisexec {
> > > > user: root
> > > > group: root
> > > > }
> > > >
> > > >
> > > >
> > > >
> > > > #Configuração de log
> > > > logging {
> > > > fileline: off
> > > > to_stderr: yes
> > > > to_logfile: yes
> > > > logfile: /var/log/corosync/corosync.log
> > > > #Aqui estou desabilitando os logs para o syslog, pq senão zoa
> > demais o
> > > > arquivo
> > > > to_syslog: no
> > > > syslog_facility: daemon
> > > > debug: off
> > > > timestamp: on
> > > > logger_subsys {
> > > > subsys: AMF
> > > > debug: off
> > > > tags: enter|leave|trace1|trace2|trace3|trace4|trace6
> > > > }
> > > >
> > > >
> > > >
> > > > [root@urano1 ~]# ls /etc/drbd.d
> > > > global_common.conf http.res mysql.res
> > > >
> > > >
> > > >
> > > > [root@urano1 ~]# cat /etc/drbd.d/http.res
> > > > resource http {
> > > > on urano1{
> > > > device /dev/drbd1;
> > > > disk /dev/vg_urano1/lv_web;
> > > > address 192.168.0.181:7789;
> > > > meta-disk internal;
> > > > }
> > > >
> > > >
> > > > on urano2{
> > > > device /dev/drbd1;
> > > > disk /dev/vg_urano2/lv_web;
> > > > address 192.168.0.182:7789;
> > > > meta-disk internal;
> > > > }
> > > > }
> > > >
> > > >
> > > >
> > > > [root@urano1 ~]# cat /etc/drbd.d/mysql.res
> > > > resource mysql {
> > > > on urano1{
> > > > device /dev/drbd0;
> > > > disk /dev/vg_urano1/lv_mysql;
> > > > address 192.168.0.181:7790;
> > > > meta-disk internal;
> > > > }
> > > >
> > > >
> > > > on urano2{
> > > > device /dev/drbd0;
> > > > disk /dev/vg_urano2/lv_mysql;
> > > > address 192.168.0.182:7790;
> > > > meta-disk internal;
> > > > }
> > > > }
> > > >
> > > >
> > > >
> > > > [root@urano1 ~]# lvs
> > > > LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert
> > > > lv_home vg_urano1 -wi-ao--- 4,88g
> > > > lv_mysql vg_urano1 -wi-ao--- 4,88g
> > > > lv_root vg_urano1 -wi-ao--- 4,88g
> > > > lv_swap vg_urano1 -wi-ao--- 3,94g
> > > > lv_usr vg_urano1 -wi-ao--- 4,88g
> > > > lv_var vg_urano1 -wi-ao--- 4,88g
> > > > lv_web vg_urano1 -wi-ao--- 4,88g
> > > >
> > > >
> > > >
> > > > [root@urano1 ~]# crm configure show
> > > > node urano1 \
> > > > attributes standby="off"
> > > > node urano2 \
> > > > attributes standby="off"
> > > > primitive Failover ocf:heartbeat:IPaddr2 \
> > > > params ip="192.168.0.200" cidr_netmask="24" nic="eth0" \
> > > > op monitor interval="10s"
> > > > primitive Httpd lsb:httpd
> > > > primitive MysqlData ocf:linbit:drbd \
> > > > params drbd_resource="mysql" \
> > > > op monitor interval="60s"
> > > > primitive MysqlFS ocf:heartbeat:Filesystem \
> > > > params device="/dev/drbd0" directory="/var/lib/mysql"
> > fstype="ext4"
> > > > primitive Mysqld lsb:mysqld
> > > > primitive Vsftpd lsb:vsftpd
> > > > primitive WebData ocf:linbit:drbd \
> > > > params drbd_resource="http" \
> > > > op monitor interval="60s"
> > > > primitive WebFS ocf:heartbeat:Filesystem \
> > > > params device="/dev/drbd1" directory="/var/www/html" fstype="ext4"
> > > > ms MysqlDataClone MysqlData \
> > > > meta master-max="1" master-node-max="1" clone-max="2"
> > > > clone-node-max="1" notify="true"
> > > > ms WebDataClone WebData \
> > > > meta master-max="1" master-node-max="1" clone-max="2"
> > > > clone-node-max="1" notify="true"
> > > > location cli-prefer-Httpd Httpd \
> > > > rule $id="cli-prefer-rule-Httpd" inf: #uname eq urano1
> > > > location cli-prefer-Mysqld Mysqld \
> > > > rule $id="cli-prefer-rule-Mysqld" inf: #uname eq urano1
> > > > location cli-prefer-Vsftpd Vsftpd \
> > > > rule $id="cli-prefer-rule-Vsftpd" inf: #uname eq urano1
> > > > colocation Htpd-with-WebFS inf: Httpd WebFS
> > > > colocation Mysqld-with-MysqlFS inf: Mysqld MysqlFS
> > > > colocation fs_on_drbd inf: MysqlFS MysqlDataClone:Master
> > > > colocation fs_on_drbd1 inf: WebFS WebDataClone:Master
> > > > colocation website-with-ip inf: Httpd Failover
> > > > order Httpd-after-WebFS inf: WebFS Httpd
> > > > order MysqlFS-after-MysqlData inf: MysqlDataClone:promote
> > > > MysqlFS:start
> > > > order Mysqld-after-MysqlFS inf: MysqlFS Mysqld
> > > > order WebFS-after-WebData inf: WebDataClone:promote WebFS:start
> > > > order httpd-after-ip inf: Failover Httpd
> > > > property $id="cib-bootstrap-options" \
> > > > dc-version="1.1.9-2.2-2db99f1" \
> > > > cluster-infrastructure="classic openais (with plugin)" \
> > > > expected-quorum-votes="2" \
> > > > stonith-enabled="false" \
> > > > no-quorum-policy="ignore"
> > > >
> > > >
> > > >
> > > > [root@urano1 ~]# crm_mon -1
> > > > Last updated: Fri Sep 6 08:13:19 2013
> > > > Last change: Fri Sep 6 07:44:54 2013 via crm_attribute on urano1
> > > > Stack: classic openais (with plugin)
> > > > Current DC: urano2 - partition with quorum
> > > > Version: 1.1.9-2.2-2db99f1
> > > > 2 Nodes configured, 2 expected votes
> > > > 10 Resources configured.
> > > >
> > > >
> > > >
> > > >
> > > > Online: [ urano1 urano2 ]
> > > >
> > > >
> > > > Failover (ocf::heartbeat:IPaddr2): Started urano1
> > > > Httpd (lsb:httpd): Started urano1
> > > > Mysqld (lsb:mysqld): Started urano1
> > > > Vsftpd (lsb:vsftpd): Started urano1
> > > > Master/Slave Set: MysqlDataClone [MysqlData]
> > > > Masters: [ urano1 ]
> > > > Slaves: [ urano2 ]
> > > > MysqlFS (ocf::heartbeat:Filesystem): Started urano1
> > > > Master/Slave Set: WebDataClone [WebData]
> > > > Masters: [ urano1 ]
> > > > Slaves: [ urano2 ]
> > > > WebFS (ocf::heartbeat:Filesystem): Started urano1
> > > >
> > > >
> > > >
> > > > [root@urano1 ~]# cat /proc/drbd
> > > > version: 8.3.15 (api:88/proto:86-97)
> > > > GIT-hash: 0ce4d235fc02b5c53c1c52c53433d11a694eab8c build by
> > > > phil@Build64R6, 2012-12-20 20:09:51
> > > > 0: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
> > > > ns:372 nr:316 dw:688 dr:4109 al:0 bm:7 lo:0 pe:0 ua:0 ap:0 ep:1
> > wo:f
> > > > oos:0
> > > > 1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
> > > > ns:104 nr:180 dw:284 dr:792 al:0 bm:4 lo:0 pe:0 ua:0 ap:0 ep:1
> > wo:f
> > > > oos:0
> > > >
> > > >
> > > >
> > > >
> > > > Tudo funcionando redondinho...Agradeço muito a sua ajuda Antônio.
> > Você
> > > > foi peça chave para eu conseguir fazer essa configuração. Muito
> > > > obrigado mesmo. E muito obrigado a comunidade também que também me
> > > > ajudou muito!
> > > >
> > > >
> > > > Fica a dica ai para quem quiser fazer cluster no CentOS. Funciona,
> > tem
> > > > que ralar um pouco mais funciona!
> > > >
> > > >
> > > > Hehe :)
> > > >
> > > >
> > > > > Date: Fri, 6 Sep 2013 07:46:50 -0300
> > > > > From: asmartins(a)uem.br
> > > > > To: centos-pt-br(a)centos.org
> > > > > Subject: Re: [CentOS-pt-br] Cluster no CentOS. Ajuda..
> > > > >
> > > > >
> > > > > ----- "CássioElias ." <cassioelias(a)hotmail.com> escreveu:
> > > > >
> > > > > > De: "CássioElias ." <cassioelias(a)hotmail.com>
> > > > > > Para: "Lista de Discussão CentOS-BR" <centos-pt-br(a)centos.org>
> > > > > > Enviadas: Quinta-feira, 5 de Setembro de 2013 17:12:49
> > (GMT-0300)
> > > > Auto-Detected
> > > > > > Assunto: Re: [CentOS-pt-br] Cluster no CentOS. Ajuda..
> > > > > >
> > > > > > Certo...entendido..
> > > > > >
> > > > > >
> > > > > > Outra pergunta. Mas para o pacemaker entender isso, eu terei
> > que
> > > > > > configura-lo ou ele entende isso por padrão?
> > > > > >
> > > > >
> > > > > Olá Cássio,
> > > > >
> > > > > Você tem que configurar o Pacemaker, da mesma forma que faz para
> > o
> > > > > Apache/MySQL/IPAddr2 são recursos. Você vai configurar um
> > recurso
> > > > DRBD,
> > > > > tem OCF::Resource para isso também (é preferivel a usar o lsb,
> > como
> > > > você
> > > > > fez com o Apache).
> > > > >
> > > > > De uma olhada aqui:
> > > > http://www.drbd.org/users-guide-8.3/ch-pacemaker.html
> > > > >
> > > > > E por falar em documentação! Você deveria ler a documentação do
> > > > Pacemaker e
> > > > > do DRBD toda, e não ficar atrás de receita de bolo (HowTo). :D
> > Tem
> > > > muita coisa
> > > > > que a turma faz errado nestes HowTos, a principal é instalar a
> > > > partir dos fontes
> > > > > quando existem pacotes nos repositórios! Se é para usar fonte,
> > use
> > > > Slackware!
> > > > >
> > > > > Att.,
> > > > >
> > > > > Antonio.
> > > > >
> > > > > --
> > > > > Antonio da Silva Martins Jr.
> > > > > Analista de Suporte
> > > > > NPD - Núcleo de Processamento de Dados
> > > > > UEM - Universidade Estadual de Maringá
> > > > > email: asmartins(a)uem.br
> > > > > fone: +55 (44) 3011-4015 / 3011-4411
> > > > > inoc-dba: 263076*100
> > > > >
> > > > > "Real Programmers don’t need comments — the code is obvious."
> > > > >
> > > > > --
> > > > > Esta mensagem foi verificada pelo sistema de antivirus e
> > > > > acredita-se estar livre de perigo.
> > > > >
> > > > > _______________________________________________
> > > > > CentOS-pt-br mailing list
> > > > > CentOS-pt-br(a)centos.org
> > > > > http://lists.centos.org/mailman/listinfo/centos-pt-br
> > > >
> > > > --
> > > > Esta mensagem foi verificada pelo sistema de antivírus e
> > > > acredita-se estar livre de perigo.
> > > > _______________________________________________
> > > > CentOS-pt-br mailing list
> > > > CentOS-pt-br(a)centos.org
> > > > http://lists.centos.org/mailman/listinfo/centos-pt-br
> > >
> > > --
> > > Antonio da Silva Martins Jr.
> > > Analista de Suporte
> > > NPD - Núcleo de Processamento de Dados
> > > UEM - Universidade Estadual de Maringá
> > > email: asmartins(a)uem.br
> > > fone: +55 (44) 3011-4015 / 3011-4411
> > > inoc-dba: 263076*100
> > >
> > > "Real Programmers don’t need comments — the code is obvious."
> > >
> > > --
> > > Esta mensagem foi verificada pelo sistema de antivirus e
> > > acredita-se estar livre de perigo.
> > >
> > > _______________________________________________
> > > CentOS-pt-br mailing list
> > > CentOS-pt-br(a)centos.org
> > > http://lists.centos.org/mailman/listinfo/centos-pt-br
> >
> > --
> > Esta mensagem foi verificada pelo sistema de antivírus e
> > acredita-se estar livre de perigo.
> > _______________________________________________
> > CentOS-pt-br mailing list
> > CentOS-pt-br(a)centos.org
> > http://lists.centos.org/mailman/listinfo/centos-pt-br
>
> --
> Antonio da Silva Martins Jr.
> Analista de Suporte
> NPD - Núcleo de Processamento de Dados
> UEM - Universidade Estadual de Maringá
> email: asmartins(a)uem.br
> fone: +55 (44) 3011-4015 / 3011-4411
> inoc-dba: 263076*100
>
> "Real Programmers don’t need comments — the code is obvious."
>
> --
> Esta mensagem foi verificada pelo sistema de antivirus e
> acredita-se estar livre de perigo.
>
> _______________________________________________
> CentOS-pt-br mailing list
> CentOS-pt-br(a)centos.org
> http://lists.centos.org/mailman/listinfo/centos-pt-br
12 years, 6 months
Re: [Arm-dev] Kernel problems on APM X-Gene
by Phong Vo
> -----Original Message-----
> From: Arm-dev [mailto:arm-dev-bounces@centos.org] On Behalf Of Jeremiah
> Rothschild
> Sent: Saturday, January 27, 2018 3:18 AM
> To: Conversations around CentOS on ARM hardware
> Subject: Re: [Arm-dev] Kernel problems on APM X-Gene
>
> On Fri, Jan 26, 2018 at 10:07:03PM +0700, Phong Vo wrote:
> > Jeremy,
> >
> > Edit the grub command line and remove both or one of console= or
> > earlycon= below
> >
> > console=ttyS0,115200 earlycon=uart8250,mmio32,0x1c020000
> >
> > to see if proceeds any further.
>
> Wow, removing "console=" worked! Can you please explain?
>
The UARTSerialBus macro in Tianocore is used to define the characteristics
of a slave
device attached to the UART bus. It should be put in Resource template of
a different Device node rather than
the UART controller node. With a rather recent commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/
?id=e361d1f85855ded967bd4803e8293445a6ce301a
the visible of UARTSerialBus forces ACPI subsystem to think that the UART
controller node is a slave device node
thus fails to open the console device.
> > -Phong
> >
> > -----Original Message-----
> > From: Arm-dev [mailto:arm-dev-bounces@centos.org] On Behalf Of
> > Jeremiah Rothschild
> > Sent: Friday, January 26, 2018 5:04 PM
> > To: Conversations around CentOS on ARM hardware
> > Subject: Re: [Arm-dev] Kernel problems on APM X-Gene
> >
> > On Fri, Jan 26, 2018 at 04:48:24PM +0700, Phong Vo wrote:
> > > Jeremy,
> >
> > Hi Phong. Thanks for the reply! Also, thank you for the tools &
> > instructions to flash the Tianocore. That process worked great. :)
> >
> > > Is this on which board?
> >
> > Gigabyte MP30-AR0 (uart0).
> >
> > > Unless you provide a log file, it is difficult to tell,
> >
> > Understood. I have attached boot.log to this message. After this
> > point, it freezes/hangs.
> >
> > > but latest CentOS 7.4 (kernel 4.11) boots fine on X-Gene platforms.
> > >
> > > I am not sure how you built kernel, but this is what you can check.
> > > To boot X-Gene using acpi, you need to enable
> > > CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y. CentOS (RPM) default
> > > configuration should already have this enabled.
> >
> > Interesting. It is enabled in the failing kernel:
> >
> > [root@hammer ~]# grep CONFIG_ARM64_ACPI_PARKING_PROTOCOL
> > /boot/config-4.11.0-45.el7.aarch64
> > CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y
> >
> > but it is not enabled in the working kernel that Gordan built for me:
> >
> > [root@hammer ~]# grep CONFIG_ARM64_ACPI_PARKING_PROTOCOL
> > /boot/config-4.9.60-1.el7.centos.aarch64
> > [root@hammer ]#
> >
> > > -Phong
> > >
> > > +-----Original Message-----
> > > +From: Arm-dev [mailto:arm-dev-bounces@centos.org] On Behalf Of
> > > +Jeremiah Rothschild
> > > +Sent: Friday, January 26, 2018 4:35 PM
> > > +To: Conversations around CentOS on ARM hardware
> > > +Subject: Re: [Arm-dev] Kernel problems on APM X-Gene
> > > +
> > > +On Sat, Nov 04, 2017 at 05:37:54PM +0000, Gordan Bobic wrote:
> > > +> Apologies for taking so long to return to this thread, it took
> > > +> way longer than expected to get to the machine and get it up and
> > > +> running
> > > +again.
> > > +
> > > +Thanks for the update & apologies as well on my delayed follow-up.
> > > +
> > > +Last time I wrote the mailing list about my kernel problems, I was
> > > +told (by jperrin(a)centos.org) that my system was not in a supported
> > > +state because I was daisy-chaining Tianocore EFI via U-Boot. I was
> > > +directed to flash the Tianocore firmware and remove U-Boot from
> the
> > equation.
> > > +Although I was skeptical of this answer, I finally was able to do
> this.
> > > +
> > > +Unfortunately, however, this does not change behavior. I still
> > > +cannot successfully boot into any kernels beyond 4.5 unless I use
> 'acpi=off'.
> > > +
> > > +I am, interestingly enough, able to run the 4.9.60 kernel that you
> > > +supplied.
> > > +
> > > +So:
> > > +
> > > +(1) My experience leads me to believe that it is still a
> > > +possibility that a kernel related bug exists.
> > > +
> > > +(2) I am confused as to why your kernel worked. I built kernel-
> alt-
> > > +4.11.0-22.el7a from source and it fails like the others. Were
> there
> > > +any special steps you took in building the rpm's you supplied me?
> > > +
> > > +(3) Is it true that you are able to boot into the (> 4.5) distro-
> > > +supplied kernels? Or have you only tried/succeeded with your
> custom
> > > +builds?
> > > +
> > > +Thanks again!
> > > +
> > > +j
> > > +
> > > +> I also just updated the build to the latest 4.9.60.
> > > +>
> > > +> Here is a download link to both binaries and src.rpm (download
> > > +> the kernel tarball from kernel.org manually to build from
> src.rpm):
> > > +> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/RPMS/
> > > +> http://ftp.redsleeve.org/pub/misc/kernel/aarch64/SRPMS/
> > > +>
> > > +> To recap - I am also running with Tianocore EFI chain-loaded
> from
> > > +> u-boot, and mainling 4.9.x boots just fine on it.
> > > +>
> > > +> No need for disabling ACPI on the kernel command line, no need
> to
> > > +> run EFI firmware as a 1st stage boot loader, it just works.
> > > +> Do feel free to try it - if that works for you but the distro
> > > +> supplied 4.5.x kernel doesn't, it seems reasonably conclusive
> > > +> that it is the CentOS kernel that is broken for this board.
> > > +>
> > > +> I'd also be interested in learning whether you have any luck
> > > +> getting PCIe cards to work with it without problems - I haven't
> > > +> tried it since upgrading to 4.9.x, but certainly on 4.4.x
> > > +> mainline the machine used to reliably lock up as soon as the
> > > +> driver for the
> > PCIe card loads.
> > > +>
> > > +> Gordan
> > > +>
> > > +>
> > > +> On Fri, Sep 22, 2017 at 12:06 PM, Jeremiah Rothschild
> > > +> <jeremiah(a)franz.com>
> > > +> wrote:
> > > +>
> > > +> > On Fri, Sep 22, 2017 at 11:59:00AM +0100, Gordan Bobic wrote:
> > > +> > > On Fri, Sep 22, 2017 at 11:54 AM, Jeremiah Rothschild <
> > > +> > jeremiah(a)franz.com>
> > > +> > > wrote:
> > > +> > >
> > > +> > > > On Fri, Sep 22, 2017 at 11:39:19AM +0100, Gordan Bobic
> wrote:
> > > +> > > > > If you are interested, I'm more than happy to share my
> > > +> > > > > src.rpm for
> > > +> > 4.9.x,
> > > +> > > > > but won't be able to get to it before tomorrow morning
> as
> > > +> > > > > the
> > > +> > machine was
> > > +> > > > > recently mothballed.
> > > +> > > >
> > > +> > > > Thanks. I actually need to test with as new of a version
> as
> > > +> > > > I can
> > > +> > because I
> > > +> > > > have been experiencing an occasional "page allocation
> failure"
> > > +> > > > kernel panic.
> > > +> > > > No idea if/when that was fixed but I figure the newest
> > > +> > > > version is my
> > > +> > best
> > > +> > > > hope.
> > > +> > > >
> > > +> > >
> > > +> > > I've been on my own 4.9.x more or less since I got the
> > > +> > > machine, it was in
> > > +> > > 24/7 use, and I never experienced that issue. So it may be
> > > +> > > worth a cross-check with the kernel that I'm running to see
> > > +> > > whether the fault follows your machine or whether it is
> > > +> > > kernel
> > dependent.
> > > +> >
> > > +> > You're right. It would be a good extra data point. Feel free
> to
> > > +> > mail me directly once you're sorted and I'll gladly check out
> > > +> > your 4.9
> > > +build.
> > > +> > Thanks
> > > +> > again!
> > > +> >
> > > +> >
> > > +> >
> > > +> > > _______________________________________________
> > > +> > > Arm-dev mailing list
> > > +> > > Arm-dev(a)centos.org
> > > +> > > https://lists.centos.org/mailman/listinfo/arm-dev
> > > +> >
> > > +> > _______________________________________________
> > > +> > Arm-dev mailing list
> > > +> > Arm-dev(a)centos.org
> > > +> > https://lists.centos.org/mailman/listinfo/arm-dev
> > > +> >
> > > +
> > > +> _______________________________________________
> > > +> Arm-dev mailing list
> > > +> Arm-dev(a)centos.org
> > > +> https://lists.centos.org/mailman/listinfo/arm-dev
> > > +
> > > +_______________________________________________
> > > +Arm-dev mailing list
> > > +Arm-dev(a)centos.org
> > > +https://lists.centos.org/mailman/listinfo/arm-dev
> > > _______________________________________________
> > > Arm-dev mailing list
> > > Arm-dev(a)centos.org
> > > https://lists.centos.org/mailman/listinfo/arm-dev
> > _______________________________________________
> > Arm-dev mailing list
> > Arm-dev(a)centos.org
> > https://lists.centos.org/mailman/listinfo/arm-dev
> _______________________________________________
> Arm-dev mailing list
> Arm-dev(a)centos.org
> https://lists.centos.org/mailman/listinfo/arm-dev
8 years, 2 months
[CentOS] GSM back door to shell with Centos and Palm handhelds
by J.J. Garcia
Hi folks,
Don't know if it could be interesting or not, even useful, but past days
i was spending my time trying to use an old gsm motorola v150 mobile
phone to get access to my host from my palm device with pssh
(http://www.sealiesoftware.com/pssh/) these are the steps i did to
accomplish it, feel free to suggest or improve it, anyway i found it
usefull.
First, this motorolla has an usb interface to the host, it's quite
simple to attach the phone to the host running CentOs, i dont like very
much usb 'things' but things are like this... anyway, if you do so
you'll notice in syslog:
<...>
Aug 8 20:54:13 spoolbox kernel: cdc_acm 1-2:1.0: ttyACM0: USB ACM
device
<...>
Don't know other mobile phones with an usb interface but it could be
similar in others with an operational modem (i have to admit that im not
an expert in GSM neither telephony...)
Anyway, if you inspect the usb line, you can see:
[root@spoolbox crash]# cat /proc/bus/usb/devices
...>
T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 9 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=02(comm.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=22b8 ProdID=3802 Rev= 0.01
S: Manufacturer=Motorola Inc.
S: Product=Motorola Phone (V150)
C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr= 20mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=01 Driver=cdc_acm
--------------- !!!!!
E: Ad=89(I) Atr=03(Int.) MxPS= 16 Ivl=10ms
I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm
--------------- !!!!!
E: Ad=01(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 16 Ivl=0ms
...>
Then, in /dev you will have:
[root@spoolbox crash]# l /dev/ttyACM0
crw------- 1 root root 166, 0 ago 8 20:54 /dev/ttyACM0
In my case, i wasn't sure about this phone modem facilities, and i start
playing with init secuences to discover the modem with 'minicom' tool,
without success. Finally i decided to use 'wvdialconf' utility to check
out my lack of kwlg. :
[root@spoolbox crash]# wvdialconf newconffile
Scanning your serial ports for a modem.
Port Scan*1>: S0 S1 S2 S3 S4 S5 S6 S7
ttyACM0*1>: ATQ0 V1 E1 -- OK
ttyACM0*1>: ATQ0 V1 E1 Z -- OK
ttyACM0*1>: ATQ0 V1 E1 S0=0 -- OK
ttyACM0*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyACM0*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyACM0*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyACM0*1>: Modem Identifier: ATI -- 144
ttyACM0*1>: Speed 4800: AT -- OK
ttyACM0*1>: Speed 9600: AT -- OK
ttyACM0*1>: Speed 19200: AT -- OK
ttyACM0*1>: Speed 38400: AT -- OK
ttyACM0*1>: Speed 57600: AT -- OK
ttyACM0*1>: Speed 115200: AT -- OK
ttyACM0*1>: Speed 230400: AT -- OK
ttyACM0*1>: Speed 460800: AT -- OK
ttyACM0*1>: Max speed is 460800; that should be safe.
ttyACM0*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyUSB0*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyUSB0*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyUSB0*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Found an USB modem on /dev/ttyACM0.
Modem configuration written to newconffile.
ttyACM0Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
[root@spoolbox crash]# l newconffile
-rw-r----- 1 root root 232 jul 30 18:11 newconffile
[root@spoolbox crash]# cat newconffile
[Dialer Defaults]
Modem = /dev/ttyACM0
Baud = 460800
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = USB Modem
; Phone = Target Phone Number>
; Username = Your Login Name>
; Password = Your Password>
With this information, i updated the init sequence in 'minicom'
parameters:
[root@spoolbox crash]# LANG=C; minicom
Welcome to minicom 2.00.0
OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n
Compiled on Feb 21 2005, 19:32:30.
Press CTRL-A Z for help on special keys
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
┌──────[Modem and dialing parameter setup]────────────────┐
│
│
│ A - Init string .. ~^M~ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0^M │
│ B - Reset string . ^M~ATZ^M~ │
<...>
I did an AT command and i get the correspoding OK, cool :)
AT
OK
ATZ
OK
ATD <phone-number>
And my other mobile phone was ringing with an incomming data call.
Up to here fine since the old motorola phone was able to perform calls,
that's not the point unless you want a dial-out line (56k).
What i needed was a dial-in facilities, go on with 'mgetty-sendfax':
First change the /etc/inittab to start using the line:
[root@spoolbox crash]# cat /etc/inittab
<...>
# Modem back line listen
# Data only and two tones b4 connect
T1:2345:respawn:/sbin/mgetty ttyACM0 -D /dev/ttyACM0
<...>
To enable dial-in uncomment the corresponding line at '/etc/mgetty
+sendfax/login.config' file with the previously created profile:
[root@spoolbox crash]# cat /etc/mgetty+sendfax/login.config
<...>
/AutoPPP/ - - /usr/sbin/pppd file /etc/ppp/options.server
<...>
You can even trim more for incomming calls using the corresponding
features at '/etc/mgetty+sendfax/dialin.config', in my case i left it
untouched without restrictions.
And config the line in '/etc/mgetty+sendfax/mgetty.config':
<...>
# Motorola V150/Usb connected to ttyACM0/1: don't do fax, less logging
#
port ttyACM0
debug 9
data-only y
speed 460800
<...>
Up to here, you have the line preset correctly, now you have to use it
to dial-in.
Create a ppp profile file to use in dial-in whatever the line will be:
[root@spoolbox crash]# cat /etc/ppp/options.server
# Do not fork to become a background process
-detach
# To allow pppd to work over a rlogin/telnet connection
asyncmap 0
# Use the modem control lines
modem
# Use hardware flow control
crtscts
# Specifies that pppd use the UUCP-style lock on the serial device
lock
# Adds an entry into the ARP table with the IP address of the client and
the IP address of the NIC
proxyarp
#
# Auth:
# PAP (Password Authentication Protocol) is one of the two protocols
that PPP uses to authenticate
# peers.
# The other is CHAP (Challenge Handshake Authentication Protocol).
# CHAP is a more secure protocol, but is not as widely supported as PAP
require-pap
refuse-chap
#require-chap
#refuse-pap
# if 'login' option (follows) is used, the file /etc/ppp/pap-secrets
need not exist. In fact, it
# might interfere with the proper functioning of PAP. You can remove the
file, or it can contain
# the following line:
# * * ""
# The advantage of maintaining /etc/ppp/pap-secrets with this line is
that it leaves you the option
# of denying PPP access to individual accounts that have entries
in /etc/passwd. To do so, below
# the above line, enter the following line:
# username * -
# where "username" is the username of the account you wish to deny PPP
access. Example:
# #user server secret addrs
# * * "" *
# jdoe * - *
#
#login
# The first DNS server IP address for this network.
ms-dns 192.168.0.1
# The second DNS server IP address for this network.
ms-dns 62.42.230.24
Third, create the specific profile for /dev/ttyACM0 line, where our
phone is:
[root@spoolbox crash]# cat /etc/ppp/options.ttyACM0
# The first IP address is the servers IP address, the second IP address
is
# the free static IP address that can be assigned to the computer
dialing
# in on the modem. This number cannot be in use.
192.168.0.3:192.168.0.69
# The net mask of the LAN the server is connected to.
netmask 255.255.255.0
And since we are using PAP to auth, create the password
at /etc/ppp/pap.secrets:
[root@spoolbox crash]# cat /etc/ppp/pap-secrets
# Secrets for authentication using PAP
# client server secret IP addresses
sm0ketst * password *
Now, let's see what's happeninig with all of this stuff:
# telinit q
And check out the syslog:
<...>
Aug 8 21:25:49 spoolbox init: Re-reading inittab
<...>
And check also '/var/log/mgetty.log.ttyACM0':
[root@spoolbox ~]# tail -F /var/log/mgetty.log.ttyACM0
<...>
--
08/08 20:58:28 CM0 mgetty: experimental test release 1.1.31-Jul24
08/08 20:58:28 CM0 check for lockfiles
08/08 20:58:28 CM0 checklock: no active process has lock, will remove
08/08 20:58:28 CM0 locking the line
08/08 20:58:28 CM0 makelock(ttyACM0) called
08/08 20:58:28 CM0 do_makelock: lock='/var/lock/LCK..ttyACM0'
08/08 20:58:28 CM0 lock made
08/08 20:58:29 CM0 tio_get_rs232_lines: status: RTS CTS DTR
08/08 20:58:29 CM0 WARNING: DSR is off - modem turned off or bad cable?
08/08 20:58:29 CM0 lowering DTR to reset Modem
08/08 20:58:29 CM0 tss: set speed to 460800 (10004)
08/08 20:58:29 CM0 tio_set_flow_control( HARD )
08/08 20:58:29 CM0 waiting for line to clear (VTIME=1), read:
08/08 20:58:30 CM0 send: \dATQ0V1H0[0d]
08/08 20:58:30 CM0 waiting for ``OK''
08/08 20:58:30 CM0 got: ATQ0V1H0[0d]
08/08 20:58:30 CM0 CND: ATQ0V1H0[0d][0a]OK ** found **
08/08 20:58:30 CM0 send: ATS0=0Q0&D3&C1[0d]
08/08 20:58:30 CM0 waiting for ``OK''
08/08 20:58:30 CM0 got: [0d]
08/08 20:58:30 CM0 CND: OK[0a]ATS0=0Q0&D3&C1[0d]
08/08 20:58:30 CM0 CND: ATS0=0Q0&D3&C1[0d][0a]OK ** found **
08/08 20:58:30 CM0 waiting for line to clear (VTIME=3), read: [0d][0a]
08/08 20:58:30 CM0 removing lock file
08/08 20:58:30 CM0 waiting...
Up to here, the hard part is done except the netfilter part i'll show
later, but from now we can ring our motorola to get access from 'pssh'
in our palm device (in my case i use a bluetooth conn with a Nokia
6600).
If we also want to get access the network from palm device, you have to
tweak the /etc/sysconfig/iptables file in the host where the phone is
connected in the following way:
a) At the top of the file, add the following lines:
# Firewall configuration written by system-config-securitylevel
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
# Rule for sharing eth0 with ppp0/ttyACM0 <------- ADD
-A FORWARD -i ppp0 -j ACCEPT <------- ADD
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT
<...>
b) At the end of the file, add the following lines:
<...>
# Rest
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Rule for dial-in network sharing
# Remark: Remember to update the /etc/sysctl.conf
# Controls IP packet forwarding
# net.ipv4.ip_forward = 1
# or # echo 1 > /proc/sys/net/ipv4/ip_forward
*nat
:PREROUTING ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A POSTROUTING -o eth0 -j MASQUERADE
COMMIT
And as you can see, enable packet forwarding by hand or in
'/etc/sysctl.conf'
After that restart iptables
[root@spoolbox ~]# service iptables restart
And check out the 'whole thing':
1st- enable bluetooth on phone,
2nd- enable bluetooth on palm, and connect
[root@spoolbox ~]# tail -F /var/log/mgetty.log.ttyACM0
<...>
--
08/08 21:38:50 CM0 select returned 1
08/08 21:38:50 CM0 checking lockfiles, locking the line
08/08 21:38:50 CM0 makelock(ttyACM0) called
08/08 21:38:50 CM0 do_makelock: lock='/var/lock/LCK..ttyACM0'
08/08 21:38:50 CM0 lock made
08/08 21:38:50 CM0 wfr: waiting for ``RING''
08/08 21:38:50 CM0 got: [0d][0a]RING[0d]
08/08 21:38:50 CM0 CND: RING
08/08 21:38:50 CM0 wfr: rc=0, drn=0
08/08 21:38:50 CM0 CND: check no: 'none'
08/08 21:38:50 CM0 send: ATA[0d]
08/08 21:38:50 CM0 waiting for ``CONNECT''
08/08 21:38:50 CM0 got: ATA[0d]
08/08 21:38:50 CM0 CND: OKATA[0d][0a]CONNECT ** found **
08/08 21:39:03 CM0 send:
08/08 21:39:03 CM0 waiting for ``_''
08/08 21:39:03 CM0 got: [0d]
08/08 21:39:03 CM0 CND: CONNECT[0a] ** found **
08/08 21:39:03 CM0 waiting for line to clear (VTIME=3), read:
08/08 21:39:03 CM0 looking for utmp entry... (my PID: 14150)
08/08 21:39:03 CM0 utmp + wtmp entry made
08/08 21:39:04 CM0 tio_set_flow_control( HARD )
08/08 21:39:04 CM0 print welcome banner (/etc/issue)
08/08 21:39:04 CM0 getlogname (AUTO_PPP), read:~[ff]}#[c0]!
08/08 21:39:05 CM0 input finished with '\r', setting ICRNL ONLCR
08/08 21:39:05 CM0 tio_get_rs232_lines: status: RTS CTS DSR DTR DCD RI
08/08 21:39:05 CM0 login: use login config file /etc/mgetty
+sendfax/login.config
08/08 21:39:05 CM0 match: user='/AutoPPP/', key=''
08/08 21:39:05 CM0 match: user='/AutoPPP/', key=''
08/08 21:39:05 CM0 match: user='/AutoPPP/', key='/AutoPPP/'*** hit!
08/08 21:39:05 CM0 calling login: cmd='/usr/sbin/pppd', argv[]='pppd
file /etc/ppp/options.server'
08/08 21:39:05 CM0 setenv: 'CALLER_ID=none'
08/08 21:39:05 CM0 setenv: 'CONNECT='
08/08 21:39:05 CM0 setenv: 'DEVICE=ttyACM0'
08/08 21:39:05 ##### data dev=ttyACM0, pid=14150, caller='none',
conn='', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'
And in syslog:
<...>
Aug 8 21:39:05 spoolbox mgetty[14150]: data dev=ttyACM0, pid=14150,
caller='none', conn='', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'
Aug 8 21:39:05 spoolbox pppd[14150]: pppd 2.4.2 started by LOGIN, uid 0
Aug 8 21:39:05 spoolbox pppd[14150]: Using interface ppp0
Aug 8 21:39:05 spoolbox pppd[14150]: Connect: ppp0 <--> /dev/ttyACM0
Aug 8 21:39:10 spoolbox pppd[14150]: PAP peer authentication succeeded
for sm0ketst
Aug 8 21:39:13 spoolbox pppd[14150]: found interface eth0 for proxy arp
Aug 8 21:39:13 spoolbox pppd[14150]: local IP address 192.168.0.3
Aug 8 21:39:13 spoolbox pppd[14150]: remote IP address 192.168.0.69
When disconnected syslog will show:
<...>
Aug 8 21:40:38 spoolbox pppd[14150]: IPCP terminated by peer
Aug 8 21:40:39 spoolbox pppd[14150]: LCP terminated by peer
Aug 8 21:40:42 spoolbox pppd[14150]: Connection terminated.
Aug 8 21:40:42 spoolbox pppd[14150]: Connect time 1.6 minutes.
Aug 8 21:40:42 spoolbox pppd[14150]: Sent 98 bytes, received 86 bytes.
Aug 8 21:40:42 spoolbox pppd[14150]: Connect time 1.6 minutes.
Aug 8 21:40:42 spoolbox pppd[14150]: Sent 98 bytes, received 86 bytes.
Aug 8 21:40:42 spoolbox pppd[14150]: Exit.
And the mgetty log (/var/log/mgetty.log.ttyACM0)
<...>
--
08/08 21:40:42 CM0 mgetty: experimental test release 1.1.31-Jul24
08/08 21:40:42 CM0 check for lockfiles
08/08 21:40:42 CM0 checklock: no active process has lock, will remove
08/08 21:40:42 CM0 locking the line
08/08 21:40:42 CM0 makelock(ttyACM0) called
08/08 21:40:42 CM0 do_makelock: lock='/var/lock/LCK..ttyACM0'
08/08 21:40:42 CM0 lock made
08/08 21:40:43 CM0 tio_get_rs232_lines: status: RTS CTS DSR DTR DCD RI
08/08 21:40:43 CM0 WARNING: DCD line still active, check modem settings
(AT&Dx)
08/08 21:40:43 CM0 lowering DTR to reset Modem
08/08 21:40:43 CM0 tss: set speed to 460800 (10004)
08/08 21:40:43 CM0 tio_set_flow_control( HARD )
08/08 21:40:43 CM0 waiting for line to clear (VTIME=1), read:
[0a][0a]NO CARRIER[0a][0a]
08/08 21:40:43 CM0 send: \dATQ0V1H0[0d]
08/08 21:40:44 CM0 waiting for ``OK''
08/08 21:40:44 CM0 got: ATQ0V1H0[0d]
08/08 21:40:44 CM0 CND: ATQ0V1H0[0d][0a]OK ** found **
08/08 21:40:44 CM0 send: ATS0=0Q0&D3&C1[0d]
08/08 21:40:44 CM0 waiting for ``OK''
08/08 21:40:44 CM0 got: [0d]
08/08 21:40:44 CM0 CND: OK[0a]ATS0=0Q0&D3&C1[0d]
08/08 21:40:44 CM0 CND: ATS0=0Q0&D3&C1[0d][0a]OK ** found **
08/08 21:40:44 CM0 waiting for line to clear (VTIME=3), read: [0d][0a]
08/08 21:40:44 CM0 removing lock file
08/08 21:40:44 CM0 waiting...
Now you can get shell access from your palm, use your favourite www palm
browser and send-receive emails, etc... with some tweaks from your palm,
all of this using your host as your gateway.
I think that's all and i didn't forget anything, feel free to knock the
door on me if something fails... but since phone companies are providing
no-cost for certain calls, i found it usefull to get a shell on my palm
to launch certain commands on the host at 0-cost, yes, at 56K, but it's
free :)
Jose.
--
-----------------------------------------------------------------
sparkbox.stigmatedbrain.net 2.6.9-34.0.2.ELsmp i686 GNU/Linux
21:40:01 up 7 days, 1:52, 44 users, load average: 3.18, 1.91, 1.62
-----------------------------------------------------------------
The Moral Law causes the people to be in complete
accord with their ruler, so that they will follow him
regardless of their lives, undismayed by any danger.
--The Art of War by Sun Tzu
Chapter I: Laying Plans
19 years, 7 months
Re: [CentOS-es] [DNS] Problemas para resolucion directa :S !
by David González Romero
Existe una herramienta en casi todos los posibles servicios de GNU/Linux
para chequear la configuración:
named-checkconf
named-checkzone
Con eso siempre podrán comprobar las configuraciones de bind9 y sus
archvios de zonas.
Saludos,
David
2013/10/22 angel jauregui <darkdiabliyo(a)gmail.com>
> Un maldito ";" (punto y coma) que no habia puesto en el named.conf era lo
> que fastidiaba todo :S...
>
> Ya funciona la solucion interna, la externa no la he probado del todo
> porque aun estoy haciendo mivimientos con los servers y me falta migrar el
> apache a otro sitio, asi que... hasta entonces esto queda pendiente :D
>
> Les dejo lo que puse en mis scripts, igual *repito NO* he probado la
> resolucion externa (desde internet). Acepto criticas :D
>
> *shell# cat /etc/dhcp/dhcpd.conf*
> ddns-update-style interim;
> ddns-updates on;
> ddns-domainname "midominio.com";
> ddns-rev-domainname "in-addr.arpa.";
> ignore client-updates;
> authoritative;
> default-lease-time 600;
> max-lease-time 7200;
> option ip-forwarding off;
> option domain-name "midominio.com";
> option ntp-servers 0.pool.ntp.org, 1.poo.ntp.org, 2.pool.ntp.org,
> 3.pool.ntp.org;
> log-facility local7;
>
> include "/etc/rndc.key";
>
> zone 1.0.10.in-addr.arpa. {
> primary 127.0.0.1;
> key rndc-key;
> }
>
> zone crver.net. {
> primary 127.0.0.1;
> key rndc-key;
> }
> shared-network midominiocom {
> subnet 10.0.1.0 netmask 255.255.255.0 {
> option routers 10.0.1.1;
> option subnet-mask 255.255.255.0;
> option broadcast-address 10.0.1.255;
> option domain-name-servers 10.0.1.1;
> option netbios-name-servers 10.0.1.1;
> range 10.0.1.100 10.0.1.150;
> }
> }
>
> *shell# cat /etc/named.conf*
> options { listen-on port 53 { any; }; listen-on-v6 port 53 { any; };
> directory "/var/named"; dump-file "/var/named/data/cache_dump.db";
> statistics-file "/var/named/data/named_stats.txt"; memstatistics-file
> "/var/named/data/named_mem_stats.txt"; allow-query { any; }; forwarders {
> 8.8.8.8; 8.8.4.4; }; forward first; recursion yes;
> bindkeys-file "/etc/named.iscdlv.key"; managed-keys-directory
> "/var/named/dynamic"; }; include "/etc/rndc.key"; logging { channel
> default_debug { file "data/named.run"; severity dynamic; }; category
> lame-servers { null; }; }; controls { inet 127.0.0.1 allow { 127.0.0.1; }
> keys { "rndc-key"; }; };
> acl internals { 127.0.0.1; 10.0.1.0/24; }; acl externals { mi.ip.fi.ja; };
> view "internal" { match-clients { internals; }; recursion yes; include
> "/etc/named.rfc1912.zones"; include "/etc/named.root.key"; zone "." IN {
> type hint; file "named.ca"; }; zone "midominio.com" { type master; file
> "data/redlocal.zone"; allow-update{ none; }; }; zone "1.0.10.in-addr.arpa"
> { type master; file "data/1.0.10.in-addr.arpa.zone"; allow-update{ none; };
> };
> };
> view "external" { match-clients { externals; }; recursion yes; zone "." IN
> { type hint; file "named.ca"; }; zone "midominio.com" { type master; file
> "data/ext_redlocal.zone"; allow-update{ none; }; };
> zone "miipfija.inver.tida.in-addr.arpa" { type master; file "data/
> miipfija.inver.tida.in-addr.arpa.zone"; allow-update{ none; }; };
> };
>
>
> Saludos !
>
>
> 2013/10/21 Yanis Guenane <yguenane(a)gmail.com>
>
> > Hola Angel,
> >
> > Puedes ensenaros tres cosas :
> >
> > 1. El contenido de /etc/resolv.conf
> > 2. La salida de dig db.midominio.com
> > 3. La salida de dig db.midominio.com @10.0.0.1
> >
> > Si 2 no funciona, pero 3 si, entonces tendrias que ver a la configuration
> > de tu /etc/dhcp/dhcpd.conf y asegurarte que tienes la linea
> >
> > > option domain-name-servers 10.0.0.1;
> > >
> > Saludos,
> >
> > --
> > Yanis Guenane
> >
> >
> > On Mon, Oct 21, 2013 at 11:42 AM, angel jauregui <darkdiabliyo(a)gmail.com
> > >wrote:
> >
> > > Buenas.
> > >
> > > Instale un equipo nuevo en el cual quiero colocar DNS, DHCP y Otros...
> > > El DHCP ya asigna IPs y tambien asigna las estaticas a las MACs que
> > > especifique.
> > >
> > > El problema es el DNS, que no consigo una resolucion directa:
> > >
> > > # resolucio inversa
> > > *shell# host 10.0.1.2*
> > > 2.1.0.10.in-addr.arpa domain name pointer db.midominio.com.
> > > 2.1.0.10.in-addr.arpa domain name pointer smtp.midominio.com.
> > > 2.1.0.10.in-addr.arpa domain name pointer pop.midominio.com.
> > > 2.1.0.10.in-addr.arpa domain name pointer imap.midominio.com.
> > > 2.1.0.10.in-addr.arpa domain name pointer ftp.midominio.com.
> > > 2.1.0.10.in-addr.arpa domain name pointer mail.midominio.com.
> > >
> > > # resolucion directa
> > > *shell# host db.midominio.com*
> > > Host db.midominio.com not found: 3(NXDOMAIN)
> > >
> > > Esta es mi configuracion de *named.conf*:
> > >
> > > *shell# cat /etc/named.conf*
> > > options {
> > > listen-on port 53 { any; };
> > > listen-on-v6 port 53 { any; };
> > > directory "/var/named";
> > > dump-file "/var/named/data/cache_dump.db";
> > > statistics-file "/var/named/data/named_stats.txt";
> > > memstatistics-file "/var/named/data/named_mem_stats.txt";
> > > allow-query { any; };
> > > forwarders {
> > > 8.8.8.8;
> > > 8.8.4.4;
> > > };
> > > forward first;
> > > recursion yes;
> > >
> > > //dnssec-enable yes;
> > > //dnssec-validation yes;
> > > //dnssec-lookaside auto;
> > >
> > > /* Path to ISC DLV key */
> > > bindkeys-file "/etc/named.iscdlv.key";
> > >
> > > managed-keys-directory "/var/named/dynamic";
> > > };
> > >
> > > logging {
> > > channel default_debug {
> > > file "data/named.run";
> > > severity dynamic;
> > > };
> > > category lame-servers { null; };
> > > };
> > > controls {
> > > inet 127.0.0.1 allow { 127.0.0.1; } keys { "rndc-key"; };
> > > };
> > >
> > > include "/etc/rndc.key";
> > >
> > > acl internals {
> > > 127.0.0.1;
> > > 10.0.1.0/24;
> > > };
> > >
> > > view "internal" {
> > > match-clients { internals; };
> > > recursion yes;
> > >
> > > zone "redlocal" {
> > > type master;
> > > file "data/redlocal.zone";
> > > allow-update{ none; };
> > > };
> > > zone "1.0.10.in-addr.arpa" {
> > > type master;
> > > file "data/1.0.10.in-addr.arpa.zone";
> > > allow-update{ none; };
> > > };
> > > include "/etc/named.rfc1912.zones";
> > > include "/etc/named.root.key";
> > > };
> > >
> > > // pendiente resolucion a peticionex externas
> > > view "external" {
> > > match-clients { any; };
> > > recursion no;
> > > zone "." IN {
> > > type hint;
> > > file "named.ca";
> > > };
> > > };
> > >
> > > Y las zonas:
> > >
> > > *shell# cat /var/named/data/redlocal.zone*
> > > $TTL 86400
> > > @ IN SOA ns1.midominio.com. root.midominio.com. (
> > > 2013102101 ; numero de serie
> > > 28800 ; tiempo de refresco
> > > 7200 ; tiempo entre reintentos de consulta
> > > 604800 ; tiempo tras el cual expira la zona
> > > 86400 ; tiempo total de vida
> > > )
> > >
> > > @ IN NS ns1
> > > IN MX 10 mail
> > > IN A 10.0.1.1
> > > server IN A 10.0.1.1
> > > www IN CNAME midominio.com.
> > > ns1 IN A 10.0.1.1
> > > smb IN A 10.0.1.1
> > > nfs IN A 10.0.1.1
> > > asterisk IN A 10.0.1.1
> > > megatron IN A 10.0.1.2
> > > db IN A 10.0.1.2
> > > smtp IN A 10.0.1.2
> > > pop IN A 10.0.1.2
> > > imap IN A 10.0.1.2
> > > ftp IN A 10.0.1.2
> > > mail IN A 10.0.1.2
> > >
> > > *shell# cat /var/named/data/1.0.10.in-addr.arpa.zone*
> > > $TTL 86400
> > > @ IN SOA ns1.midominio.com. root.midominio.com. (
> > > 2013102101 ; numero de serie
> > > 28800 ; tiempo de refresco
> > > 7200 ; tiempo entre reintentos de consulta
> > > 604800 ; tiempo tras el cual expira la zona
> > > 86400 ; tiempo total de vida
> > > )
> > >
> > > @ IN NS ns1.midominio.com.
> > > 1 IN PTR server.midominio.com.
> > > 1 IN PTR smb.midominio.com.
> > > 1 IN PTR nfs.midominio.com.
> > > 1 IN PTR asterisk.midominio.com.
> > > 2 IN PTR megatron.midominio.com.
> > > 2 IN PTR db.midominio.com.
> > > 2 IN PTR smtp.midominio.com.
> > > 2 IN PTR pop.midominio.com.
> > > 2 IN PTR imap.midominio.com.
> > > 2 IN PTR ftp.midominio.com.
> > > 2 IN PTR mail.midominio.com.
> > >
> > > Saludos !
> > >
> > > --
> > > M.S.I. Angel Haniel Cantu Jauregui.
> > >
> > > Celular: (011-52-1)-899-871-17-22
> > > E-Mail: angel.cantu(a)sie-group.net
> > > Web: http://www.sie-group.net/
> > > Cd. Reynosa Tamaulipas.
> > > _______________________________________________
> > > CentOS-es mailing list
> > > CentOS-es(a)centos.org
> > > http://lists.centos.org/mailman/listinfo/centos-es
> > >
> >
> >
> >
> > --
> > *Yanis Guenane*
> > _______________________________________________
> > CentOS-es mailing list
> > CentOS-es(a)centos.org
> > http://lists.centos.org/mailman/listinfo/centos-es
> >
>
>
>
> --
> M.S.I. Angel Haniel Cantu Jauregui.
>
> Celular: (011-52-1)-899-871-17-22
> E-Mail: angel.cantu(a)sie-group.net
> Web: http://www.sie-group.net/
> Cd. Reynosa Tamaulipas.
> _______________________________________________
> CentOS-es mailing list
> CentOS-es(a)centos.org
> http://lists.centos.org/mailman/listinfo/centos-es
>
12 years, 5 months
Re: [CentOS] yum update / kernal update failed - remove or repair
by Kay Diederichs
On 1/22/20 3:57 PM, Gary Stainburn wrote:
> I have managed to find out what happened in the yum update and it turns out it was a mess. It looks like the server ran out of memory in the middle and things then started to fail. Any advice on how to recover from this would be greatly appreciated
>
> The log below shows:
>
> [root@vps2 ~]# yum history info 22
> Loaded plugins: fastestmirror, langpacks
> Repository mariadb is listed more than once in the configuration
> Transaction ID : 22
> Begin time : Sun Jan 19 18:15:33 2020
> Begin rpmdb : 795:6c5cd82e3ada047c7071fea1524f41fd13fab6a1
> End time : 19:19:32 2020 (63 minutes)
> End rpmdb : 801:6d1b278ccbeef6f68ff494cb28eaed5c7be4124b
> User : root <root>
> Return-Code : Failure: 1
> Command Line : update
> Transaction performed with:
> Installed rpm-4.11.3-40.el7.x86_64 @anaconda
> Installed yum-3.4.3-163.el7.centos.noarch @anaconda
> Installed yum-plugin-fastestmirror-1.1.31-52.el7.noarch @anaconda
> Packages Altered:
> Updated MariaDB-client-10.4.10-1.el7.centos.x86_64 @mariadb
> Update 10.4.11-1.el7.centos.x86_64 @mariadb
> Updated MariaDB-common-10.4.10-1.el7.centos.x86_64 @mariadb
> Update 10.4.11-1.el7.centos.x86_64 @mariadb
> Updated MariaDB-compat-10.4.10-1.el7.centos.x86_64 @mariadb
> Update 10.4.11-1.el7.centos.x86_64 @mariadb
> ** Updated MariaDB-server-10.4.10-1.el7.centos.x86_64 @mariadb
> Loading mirror speeds from cached hostfile
> * base: mirror.as29550.net
> * epel: www.mirrorservice.org
> * extras: www.mirrorservice.org
> * remi-php73: mirrors.ukfast.co.uk
> * remi-safe: mirrors.ukfast.co.uk
> * updates: www.mirrorservice.org
> ** Update 10.4.11-1.el7.centos.x86_64 @?mariadb
> ** Updated MariaDB-shared-10.4.10-1.el7.centos.x86_64 @mariadb
> Update 10.4.11-1.el7.centos.x86_64 @mariadb
> ** Updated ca-certificates-2018.2.22-70.0.el7_5.noarch @anaconda
> ** Update 2019.2.32-76.el7_7.noarch @?updates
> Updated certbot-0.39.0-1.el7.noarch @epel
> Update 1.0.0-1.el7.noarch @epel
> Updated clamav-0.101.4-1.el7.x86_64 @epel
> Update 0.101.5-1.el7.x86_64 @epel
> Updated clamav-data-0.101.4-1.el7.noarch @epel
> Update 0.101.5-1.el7.noarch @epel
> Updated clamav-devel-0.101.4-1.el7.x86_64 @epel
> Update 0.101.5-1.el7.x86_64 @epel
> Updated clamav-filesystem-0.101.4-1.el7.noarch @epel
> Update 0.101.5-1.el7.noarch @epel
> Updated clamav-lib-0.101.4-1.el7.x86_64 @epel
> Update 0.101.5-1.el7.x86_64 @epel
> Updated clamav-update-0.101.4-1.el7.x86_64 @epel
> Update 0.101.5-1.el7.x86_64 @epel
> Updated clamd-0.101.4-1.el7.x86_64 @epel
> Update 0.101.5-1.el7.x86_64 @epel
> Updated curl-7.29.0-54.el7.x86_64 @anaconda
> Update 7.29.0-54.el7_7.1.x86_64 @updates
> Updated fail2ban-0.9.7-1.el7.noarch @epel
> Update 0.10.4-1.el7.noarch @epel
> Updated fail2ban-firewalld-0.9.7-1.el7.noarch @epel
> Update 0.10.4-1.el7.noarch @epel
> Updated fail2ban-sendmail-0.9.7-1.el7.noarch @epel
> Update 0.10.4-1.el7.noarch @epel
> Updated fail2ban-server-0.9.7-1.el7.noarch @epel
> Update 0.10.4-1.el7.noarch @epel
> Updated fail2ban-systemd-0.9.7-1.el7.noarch @epel
> Update 0.10.4-1.el7.noarch @epel
> Updated fribidi-1.0.2-1.el7.x86_64 @anaconda
> Update 1.0.2-1.el7_7.1.x86_64 @updates
> Updated iproute-4.11.0-25.el7.x86_64 @anaconda
> Update 4.11.0-25.el7_7.2.x86_64 @updates
> Install kernel-3.10.0-1062.9.1.el7.x86_64 @updates
> Updated kernel-headers-3.10.0-1062.4.3.el7.x86_64 @updates
> Update 3.10.0-1062.9.1.el7.x86_64 @updates
> Updated kernel-tools-3.10.0-1062.4.3.el7.x86_64 @updates
> Update 3.10.0-1062.9.1.el7.x86_64 @updates
> Updated kernel-tools-libs-3.10.0-1062.4.3.el7.x86_64 @updates
> Update 3.10.0-1062.9.1.el7.x86_64 @updates
> Updated libblkid-2.23.2-61.el7.x86_64 @anaconda
> Update 2.23.2-61.el7_7.1.x86_64 @updates
> Updated libcurl-7.29.0-54.el7.x86_64 @anaconda
> Update 7.29.0-54.el7_7.1.x86_64 @updates
> Updated libgs-9.25-2.el7_7.2.x86_64 @updates
> Update 9.25-2.el7_7.3.x86_64 @updates
> Updated libmount-2.23.2-61.el7.x86_64 @anaconda
> Update 2.23.2-61.el7_7.1.x86_64 @updates
> Updated libsmartcols-2.23.2-61.el7.x86_64 @anaconda
> Update 2.23.2-61.el7_7.1.x86_64 @updates
> Updated libsss_idmap-1.16.4-21.el7.x86_64 @anaconda
> Update 1.16.4-21.el7_7.1.x86_64 @updates
> Updated libsss_nss_idmap-1.16.4-21.el7.x86_64 @anaconda
> Update 1.16.4-21.el7_7.1.x86_64 @updates
> Updated libuuid-2.23.2-61.el7.x86_64 @anaconda
> Update 2.23.2-61.el7_7.1.x86_64 @updates
> Updated libwebp7-1.0.2-1.el7.remi.x86_64 @remi-safe
> Update 1.0.3-1.el7.remi.x86_64 @remi-safe
> ** Updated microcode_ctl-2:2.1-53.3.el7_7.x86_64 @updates
> Update 2:2.1-53.7.el7_7.x86_64 @updates
> Updated nss-3.44.0-4.el7.x86_64 @anaconda
> Update 3.44.0-7.el7_7.x86_64 @updates
> Updated nss-softokn-3.44.0-5.el7.x86_64 @anaconda
> Update 3.44.0-8.el7_7.x86_64 @updates
> Updated nss-softokn-freebl-3.44.0-5.el7.x86_64 @anaconda
> Update 3.44.0-8.el7_7.x86_64 @updates
> Updated nss-sysinit-3.44.0-4.el7.x86_64 @anaconda
> Update 3.44.0-7.el7_7.x86_64 @updates
> Updated nss-tools-3.44.0-4.el7.x86_64 @anaconda
> Update 3.44.0-7.el7_7.x86_64 @updates
> Updated nss-util-3.44.0-3.el7.x86_64 @anaconda
> Update 3.44.0-4.el7_7.x86_64 @updates
> Updated numactl-libs-2.0.12-3.el7.x86_64 @anaconda
> Update 2.0.12-3.el7_7.1.x86_64 @updates
> Updated pgdg-redhat-repo-42.0-5.noarch @/pgdg-centos10-10-2.noarch
> Update 42.0-6.noarch @pgdg10
> Updated php-7.3.12-1.el7.remi.x86_64 @remi-php73
> Update 7.3.13-1.el7.remi.x86_64 @remi-php73
> Updated php-cli-7.3.12-1.el7.remi.x86_64 @remi-php73
> Update 7.3.13-1.el7.remi.x86_64 @remi-php73
> Updated php-common-7.3.12-1.el7.remi.x86_64 @remi-php73
> Update 7.3.13-1.el7.remi.x86_64 @remi-php73
> Updated php-gd-7.3.12-1.el7.remi.x86_64 @remi-php73
> Update 7.3.13-1.el7.remi.x86_64 @remi-php73
> Updated php-json-7.3.12-1.el7.remi.x86_64 @remi-php73
> Update 7.3.13-1.el7.remi.x86_64 @remi-php73
> Updated php-ldap-7.3.12-1.el7.remi.x86_64 @remi-php73
> Update 7.3.13-1.el7.remi.x86_64 @remi-php73
> Updated php-mysqlnd-7.3.12-1.el7.remi.x86_64 @remi-php73
> Update 7.3.13-1.el7.remi.x86_64 @remi-php73
> Updated php-odbc-7.3.12-1.el7.remi.x86_64 @remi-php73
> Update 7.3.13-1.el7.remi.x86_64 @remi-php73
> Updated php-pdo-7.3.12-1.el7.remi.x86_64 @remi-php73
> Update 7.3.13-1.el7.remi.x86_64 @remi-php73
> ** Updated php-pear-1:1.10.10-2.el7.remi.noarch @remi-php70
> ** Update 1:1.10.10-4.el7.remi.noarch @?remi-php73
> Updated php-pgsql-7.3.12-1.el7.remi.x86_64 @remi-php73
> Update 7.3.13-1.el7.remi.x86_64 @remi-php73
> Updated php-process-7.3.12-1.el7.remi.x86_64 @remi-php73
> Update 7.3.13-1.el7.remi.x86_64 @remi-php73
> Updated php-xml-7.3.12-1.el7.remi.x86_64 @remi-php73
> Update 7.3.13-1.el7.remi.x86_64 @remi-php73
> Updated php-xmlrpc-7.3.12-1.el7.remi.x86_64 @remi-php73
> Update 7.3.13-1.el7.remi.x86_64 @remi-php73
> Updated postgresql10-10.11-1PGDG.rhel7.x86_64 @pgdg10
> Update 10.11-2PGDG.rhel7.x86_64 @pgdg10
> Updated postgresql10-contrib-10.11-1PGDG.rhel7.x86_64 @pgdg10
> Update 10.11-2PGDG.rhel7.x86_64 @pgdg10
> Updated postgresql10-libs-10.11-1PGDG.rhel7.x86_64 @pgdg10
> Update 10.11-2PGDG.rhel7.x86_64 @pgdg10
> ** Updated postgresql10-server-10.11-1PGDG.rhel7.x86_64 @pgdg10
> Update 10.11-2PGDG.rhel7.x86_64 @pgdg10
> ** Updated proftpd-1.3.5e-7.el7.x86_64 @epel
> Update 1.3.5e-8.el7.x86_64 @epel
> Updated python-perf-3.10.0-1062.4.3.el7.x86_64 @updates
> Update 3.10.0-1062.9.1.el7.x86_64 @updates
> Updated python-requests-2.6.0-7.el7_7.noarch @updates
> Update 2.6.0-8.el7_7.noarch @updates
> Updated python2-acme-0.39.0-1.el7.noarch @epel
> Update 1.0.0-1.el7.noarch @epel
> Updated python2-certbot-0.39.0-1.el7.noarch @epel
> Update 1.0.0-1.el7.noarch @epel
> Updated python2-certbot-apache-0.39.0-1.el7.noarch @epel
> Update 1.0.0-1.el7.noarch @epel
> Updated selinux-policy-3.13.1-252.el7.1.noarch @updates
> Update 3.13.1-252.el7_7.6.noarch @updates
> Updated selinux-policy-targeted-3.13.1-252.el7.1.noarch @updates
> Update 3.13.1-252.el7_7.6.noarch @updates
> Updated sos-3.7-7.el7.centos.noarch @updates
> Update 3.7-10.el7.centos.noarch @updates
> ** Updated sssd-client-1.16.4-21.el7.x86_64 @anaconda
> Update 1.16.4-21.el7_7.1.x86_64 @updates
> Updated tcpdump-14:4.9.2-4.el7.x86_64 @anaconda
> Update 14:4.9.2-4.el7_7.1.x86_64 @updates
> Updated util-linux-2.23.2-61.el7.x86_64 @anaconda
> Update 2.23.2-61.el7_7.1.x86_64 @updates
> Scriptlet output:
> 1 error: Couldn't fork %post(libsss_idmap-1.16.4-21.el7_7.1.x86_64): Cannot allocate memory
> 2 error: Couldn't fork %post(libsss_nss_idmap-1.16.4-21.el7_7.1.x86_64): Cannot allocate memory
> 3 error: Couldn't fork %pre(ca-certificates-2019.2.32-76.el7_7.noarch): Cannot allocate memory
> 4 error: ca-certificates-2019.2.32-76.el7_7.noarch: install failed
> 5 error: Couldn't fork %post(certbot-1.0.0-1.el7.noarch): Cannot allocate memory
> 6 error: Couldn't fork %pre(MariaDB-server-10.4.11-1.el7.centos.x86_64): Cannot allocate memory
> 7 error: MariaDB-server-10.4.11-1.el7.centos.x86_64: install failed
> 8 error: Couldn't fork %post(sssd-client-1.16.4-21.el7_7.1.x86_64): Cannot allocate memory
> 9 error: Couldn't fork %post(kernel-tools-3.10.0-1062.9.1.el7.x86_64): Cannot allocate memory
> 10 error: Couldn't fork %pre(php-pear-1:1.10.10-4.el7.remi.noarch): Cannot allocate memory
> 11 error: php-pear-1:1.10.10-4.el7.remi.noarch: install failed
> 12 warning: /etc/clamd.d/scan.conf created as /etc/clamd.d/scan.conf.rpmnew
> 13 error: Couldn't fork %triggerin(microcode_ctl-2:2.1-53.7.el7_7.x86_64): Cannot allocate memory
> 14 error: php-pear-1:1.10.10-2.el7.remi.noarch: erase skipped
> 15 error: MariaDB-server-10.4.10-1.el7.centos.x86_64: erase skipped
> 16 error: Couldn't fork %preun(MariaDB-shared-10.4.10-1.el7.centos.x86_64): Cannot allocate memory
> 17 error: MariaDB-shared-10.4.10-1.el7.centos.x86_64: erase failed
> 18 error: Couldn't fork %postun(MariaDB-compat-10.4.10-1.el7.centos.x86_64): Cannot allocate memory
> 19 error: ca-certificates-2018.2.22-70.0.el7_5.noarch: erase skipped
> 20 error: Couldn't fork %preun(microcode_ctl-2:2.1-53.3.el7_7.x86_64): Cannot allocate memory
> 21 error: microcode_ctl-2:2.1-53.3.el7_7.x86_64: erase failed
> 22 error: Couldn't fork %preun(postgresql10-server-10.11-1PGDG.rhel7.x86_64): Cannot allocate memory
> 23 error: postgresql10-server-10.11-1PGDG.rhel7.x86_64: erase failed
> 24 error: Couldn't fork %postun(libmount-2.23.2-61.el7.x86_64): Cannot allocate memory
> 25 error: Couldn't fork %preun(sssd-client-1.16.4-21.el7.x86_64): Cannot allocate memory
> 26 error: sssd-client-1.16.4-21.el7.x86_64: erase failed
> 27 error: Couldn't fork %postun(libblkid-2.23.2-61.el7.x86_64): Cannot allocate memory
> 28 error: Couldn't fork %postun(postgresql10-10.11-1PGDG.rhel7.x86_64): Cannot allocate memory
> 29 error: Couldn't fork %postun(clamav-lib-0.101.4-1.el7.x86_64): Cannot allocate memory
> 30 error: Couldn't fork %postun(kernel-tools-3.10.0-1062.4.3.el7.x86_64): Cannot allocate memory
> 31 error: Couldn't fork %postun(libcurl-7.29.0-54.el7.x86_64): Cannot allocate memory
> 32 error: Couldn't fork %postun(nss-3.44.0-4.el7.x86_64): Cannot allocate memory
> 33 error: Couldn't fork %postun(nss-softokn-3.44.0-5.el7.x86_64): Cannot allocate memory
> 34 error: Couldn't fork %postun(nss-util-3.44.0-3.el7.x86_64): Cannot allocate memory
> 35 error: Couldn't fork %postun(postgresql10-libs-10.11-1PGDG.rhel7.x86_64): Cannot allocate memory
> 36 error: Couldn't fork %postun(libuuid-2.23.2-61.el7.x86_64): Cannot allocate memory
> 37 error: Couldn't fork %postun(libsss_idmap-1.16.4-21.el7.x86_64): Cannot allocate memory
> 38 error: Couldn't fork %postun(libsss_nss_idmap-1.16.4-21.el7.x86_64): Cannot allocate memory
> 39 error: Couldn't fork %postun(libsmartcols-2.23.2-61.el7.x86_64): Cannot allocate memory
> 40 error: Couldn't fork %postun(libwebp7-1.0.2-1.el7.remi.x86_64): Cannot allocate memory
> 41 error: Couldn't fork %postun(fribidi-1.0.2-1.el7.x86_64): Cannot allocate memory
> 42 error: Couldn't fork %preun(proftpd-1.3.5e-7.el7.x86_64): Cannot allocate memory
> 43 error: proftpd-1.3.5e-7.el7.x86_64: erase failed
> 44 error: Couldn't fork %postun(numactl-libs-2.0.12-3.el7.x86_64): Cannot allocate memory
> 45 error: Couldn't fork %posttrans(kernel-3.10.0-1062.9.1.el7.x86_64): Cannot allocate memory
> 46 error: Couldn't fork %posttrans(microcode_ctl-2:2.1-53.7.el7_7.x86_64): Cannot allocate memory
> history info
> [root@vps2 ~]#
>
Before you try the update again, you'll have to fix the reason for the
failure - add memory, or at least add a swap file.
You could check with
rpm -qa --last | head -20
which the latest packages are that were installed.
If the rpm database is corrupted, rebuild it with
rpm --rebuilddb
You can reinstall packages that may not be completely installed, using
rpm --reinstall PACKAGE_FILE
I'd rpm --erase the kernel package that does not boot.
HTH,
Kay
6 years, 2 months
Re: [CentOS] Re: The scariest set up of all: Printer Support -- step-by-step: Canon PIXUS iP3100
by Simone
Hi, really think you shouldn't give up. In fact I tryied to configure a
Pixma IP3000 just now and it works (at least printed the test page).
These my steps:
installed libxml package for fedora3 (since bjfilter was complaining
about it and I couldn't find rpm for centos4/rhel4)
ftp://ftp.nluug.nl/pub/os/Linux/distr/fedora/core/updates/3/i386/libxml-1.8.17-12.i386.rpm
installed
bjfilter-common-2.50-2.i386.rpm
bjfilter-pixusip3100-lprng-2.50-2.i386.rpm
bjfilter-pixusip3100-2.50-2.i386.rpm
Then I fortunately missed how to import PPD from the printing GUI so I
switched to KDE and installed correctly using the control panel, printed
the test page, all working (edited the ppd file as indicated on the
article). Went back to gnome, found the Action-->import PPD in the GUI,
added the correct ppd and happily tryied to print, but I got your same
error, or better, nothing was coming out. Found that the 2 files (one
added by KDE the other by gnome) in /etc/cups/ppd/ where different, so
copied and pasted the working one to the other, restarted cups and now
it is working. This is my working /etc/cups/ppd/pixma.ppd file:
*PPD-Adobe: "4.3"
*% CUPS add-on PPD file for Canon Bubble Jet Printer.
*% Copyright CANON INC. 2001-2005
*% All Rights Reserved.
*%
*% This program is free software; you can redistribute it and/or modify
*% it under the terms of the GNU General Public License as published by
*% the Free Software Foundation; either version 2 of the License, or
*% (at your option) any later version.
*%
*% This program is distributed in the hope that it will be useful,
*% but WITHOUT ANY WARRANTY; without even the implied warranty of
*% MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
*% GNU General Public License for more details.
*%
*% You should have received a copy of the GNU General Public License
*% along with this program; if not, write to the Free Software
*% Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA
02111-1307 USA
*FileVersion: "1.0"
*FormatVersion: "4.3"
*LanguageEncoding: ISOLatin1
*LanguageVersion: English
*Manufacturer: "Canon"
*ModelName: "Canon PIXUS iP3100"
*NickName: "Canon PIXUS iP3100 Ver.2.50x"
*PCFileName: "CNPX3100.PPD"
*Product: "(pixusip3100)"
*PSVersion: "(3010.000) 550"
*PSVersion: "(3010.000) 651"
*PSVersion: "(3010.000) 705"
*ShortNickName: "PIXUSIP3100"
*ColorDevice: True
*DefaultColorSpace: RGB
*Throughput: "1"
*LandscapeOrientation: Plus90
*cupsFilter: "application/vnd.cups-postscript 0 pstocanonbj"
*cupsManualCopies: True
*cupsModelNumber: 180
*cupsVersion: 1.1
*MaxMediaWidth: "612"
*MaxMediaHeight: "1656"
*CenterRegistered: False
*HWMargins: 9.64 14.17 9.64 8.50
*LeadingEdge Short: ""
*DefaultLeadingEdge: Short
*VariablePaperSize: True
*ParamCustomPageSize Width: 1 points 255.12 612.0
*ParamCustomPageSize Height: 2 points 340.16 1656.0
*ParamCustomPageSize WidthOffset: 3 points 0 0
*ParamCustomPageSize HeightOffset: 4 points 0 0
*ParamCustomPageSize Orientation: 5 int 1 1
*CustomPageSize True: "pop pop pop <</PageSize [5 -2 roll] /ImagingBBox
null>>setpagedevice"
*OpenUI *PageSize/Paper Size: PickOne
*DefaultPageSize: a4
*PageSize a5/A5: "<</CNPageSizeName(a5)/PageSize[420 595]/ImagingBBox
null>>setpagedevice"
*PageSize a4/A4: "<</CNPageSizeName(a4)/PageSize[595 842]/ImagingBBox
null>>setpagedevice"
*PageSize b5/B5: "<</CNPageSizeName(b5)/PageSize[516 729]/ImagingBBox
null>>setpagedevice"
*PageSize letter/Letter: "<</CNPageSizeName(letter)/PageSize[612
792]/ImagingBBox null>>setpagedevice"
*PageSize legal/Legal: "<</CNPageSizeName(legal)/PageSize[612
1008]/ImagingBBox null>>setpagedevice"
*PageSize postcard/Hagaki 100x148mm:
"<</CNPageSizeName(postcard)/PageSize[283 420]/ImagingBBox
null>>setpagedevice"
*PageSize postdbl/Hagaki 2 148x200mm:
"<</CNPageSizeName(postdbl)/PageSize[567 420]/ImagingBBox
null>>setpagedevice"
*PageSize envj4p/Youkei 4 105.5x235mm:
"<</CNPageSizeName(envj4p)/PageSize[298 666]/ImagingBBox
null>>setpagedevice"
*PageSize envj6p/Youkei 6 98x190mm:
"<</CNPageSizeName(envj6p)/PageSize[278 539]/ImagingBBox
null>>setpagedevice"
*PageSize l/L 89x127mm: "<</CNPageSizeName(l)/PageSize[252
360]/ImagingBBox null>>setpagedevice"
*PageSize 2l/2L 127x178mm: "<</CNPageSizeName(2l)/PageSize[360
505]/ImagingBBox null>>setpagedevice"
*PageSize panorama/P 89x254mm: "<</CNPageSizeName(panorama)/PageSize[252
720]/ImagingBBox null>>setpagedevice"
*PageSize businesscard/Card 2.16x3.58in 55x91mm:
"<</CNPageSizeName(businesscard)/PageSize[156 256]/ImagingBBox
null>>setpagedevice"
*PageSize creditcard/Credit Card 2.13x3.39in 54x86mm:
"<</CNPageSizeName(creditcard)/PageSize[153 244]/ImagingBBox
null>>setpagedevice"
*CloseUI: *PageSize
*OpenUI *PageRegion: PickOne
*DefaultPageRegion: a4
*PageRegion a5/A5: "<</CNPageSizeName(a5)/PageSize[420 595]/ImagingBBox
null>>setpagedevice"
*PageRegion a4/A4: "<</CNPageSizeName(a4)/PageSize[595 842]/ImagingBBox
null>>setpagedevice"
*PageRegion b5/B5: "<</CNPageSizeName(b5)/PageSize[516 729]/ImagingBBox
null>>setpagedevice"
*PageRegion letter/Letter: "<</CNPageSizeName(letter)/PageSize[612
792]/ImagingBBox null>>setpagedevice"
*PageRegion legal/Legal: "<</CNPageSizeName(legal)/PageSize[612
1008]/ImagingBBox null>>setpagedevice"
*PageRegion postcard/Hagaki 100x148mm:
"<</CNPageSizeName(postcard)/PageSize[283 420]/ImagingBBox
null>>setpagedevice"
*PageRegion postdbl/Hagaki 2 148x200mm:
"<</CNPageSizeName(postdbl)/PageSize[567 420]/ImagingBBox
null>>setpagedevice"
*PageRegion envj4p/Youkei 4 105.5x235mm:
"<</CNPageSizeName(envj4p)/PageSize[298 666]/ImagingBBox
null>>setpagedevice"
*PageRegion envj6p/Youkei 6 98x190mm:
"<</CNPageSizeName(envj6p)/PageSize[278 539]/ImagingBBox
null>>setpagedevice"
*PageRegion l/L 89x127mm: "<</CNPageSizeName(l)/PageSize[252
360]/ImagingBBox null>>setpagedevice"
*PageRegion 2l/2L 127x178mm: "<</CNPageSizeName(2l)/PageSize[360
505]/ImagingBBox null>>setpagedevice"
*PageRegion panorama/P 89x254mm:
"<</CNPageSizeName(panorama)/PageSize[252 720]/ImagingBBox
null>>setpagedevice"
*PageRegion businesscard/Card 2.16x3.58in 55x91mm:
"<</CNPageSizeName(businesscard)/PageSize[156 256]/ImagingBBox
null>>setpagedevice"
*PageRegion creditcard/Credit Card 2.13x3.39in 54x86mm:
"<</CNPageSizeName(creditcard)/PageSize[153 244]/ImagingBBox
null>>setpagedevice"
*CloseUI: *PageRegion
*OpenUI *MediaType/Media Type: PickOne
*DefaultMediaType: plain
*MediaType plain/Plain Paper: "<</MediaType(plain)>>setpagedevice"
*MediaType prophoto/Photo Paper Pro: "<</MediaType(prophoto)>>setpagedevice"
*MediaType superphoto/Photo Paper Plus Glossy:
"<</MediaType(superphoto)>>setpagedevice"
*MediaType doublesidephoto/Photo Paper Plus Double Sided:
"<</MediaType(doublesidephoto)>>setpagedevice"
*MediaType matte/Matte Photo Paper: "<</MediaType(matte)>>setpagedevice"
*MediaType glossypaper/Glossy Photo Paper:
"<</MediaType(glossypaper)>>setpagedevice"
*MediaType highres/High Resolution Paper:
"<</MediaType(highres)>>setpagedevice"
*MediaType ijpostcard/Inkjet Hagaki:
"<</MediaType(ijpostcard)>>setpagedevice"
*MediaType postcard/Hagaki: "<</MediaType(postcard)>>setpagedevice"
*MediaType tshirt/T-Shirt Transfer: "<</MediaType(tshirt)>>setpagedevice"
*MediaType ohp/Transparency: "<</MediaType(ohp)>>setpagedevice"
*MediaType envelope/Envelope: "<</MediaType(envelope)>>setpagedevice"
*CloseUI: *MediaType
*OpenUI *InputSlot/Paper Feed: PickOne
*DefaultInputSlot: asf
*InputSlot asf/Auto Feeder: ""
*InputSlot cassette/Cassette: ""
*CloseUI: *InputSlot
*OpenUI *Resolution/Output Resolution: PickOne
*DefaultResolution: 1200
*Resolution 600/600 dpi: "<>setpagedevice"
*Resolution 1200/1200 dpi: "<>setpagedevice"
*Resolution 2400/2400 dpi: "<>setpagedevice"
*CloseUI: *Resolution
*OpenUI *CNQuality/Quality: PickOne
*DefaultCNQuality: 3
*CNQuality 2/High: "2"
*CNQuality 3/Normal: "3"
*CNQuality 4/Standard: "4"
*CNQuality 5/Economy: "5"
*CloseUI: *CNQuality
*OpenUI *ColorModel/Color Model: PickOne
*DefaultColorModel: rgb
*ColorModel rgb/RGB: "<</cupsColorOrder 0/cupsColorSpace
1/cupsCompression 0/cupsBitsPerColor 8>>setpagedevice"
*CloseUI: *ColorModel
*DefaultImageableArea: a4
*ImageableArea a5: "9.64 14.17 409.89 586.77"
*ImageableArea a4: "9.64 14.17 585.64 833.39"
*ImageableArea b5: "9.64 14.17 506.27 720.00"
*ImageableArea letter: "18.14 14.17 594.14 783.50"
*ImageableArea legal: "18.14 14.17 594.14 999.50"
*ImageableArea postcard: "9.64 14.17 273.83 411.02"
*ImageableArea postdbl: "9.64 14.17 557.29 411.02"
*ImageableArea envj4p: "9.64 75.12 288.00 657.64"
*ImageableArea envj6p: "9.64 75.12 268.16 530.08"
*ImageableArea l: "9.64 14.17 242.65 351.50"
*ImageableArea 2l: "9.64 14.17 350.36 496.06"
*ImageableArea panorama: "9.64 14.17 242.65 711.50"
*ImageableArea businesscard: "9.64 14.17 146.27 249.45"
*ImageableArea creditcard: "9.64 14.17 143.43 235.28"
*DefaultPaperDimension: a4
*PaperDimension a5: "420 595"
*PaperDimension a4: "595 842"
*PaperDimension b5: "516 729"
*PaperDimension letter: "612 792"
*PaperDimension legal: "612 1008"
*PaperDimension postcard: "283 420"
*PaperDimension postdbl: "567 420"
*PaperDimension envj4p: "298 666"
*PaperDimension envj6p: "278 539"
*PaperDimension l: "252 360"
*PaperDimension 2l: "360 505"
*PaperDimension panorama: "252 720"
*PaperDimension businesscard: "156 258"
*PaperDimension creditcard: "153 244"
*%CNPpdToOptKey PageSize --papersize
*%CNPpdToOptKey MediaType --media
*%CNPpdToOptKey InputSlot --paperload
*%CNPpdToOptKey CNCartridge --cartridge
*%CNPpdToOptKey CNQuality --quality
*%CNPpdToOptKey CNHalftoning --halftoning
*%CNPpdToOptKey CNRenderIntent --renderintent
*%CNPpdToOptKey CNGamma --gamma
*%CNPpdToOptKey CNBalanceC --balance_c
*%CNPpdToOptKey CNBalanceM --balance_m
*%CNPpdToOptKey CNBalanceY --balance_y
*%CNPpdToOptKey CNBalanceK --balance_k
*%CNPpdToOptKey CNDensity --density
*%CNPpdToOptKey CNGrayscale --grayscale
*%CNPpdToOptKey CNLocation --location
*%CNPpdToOptKey CNPercent --percent
*%CNPpdToOptKey CNCopies --copies
*%CNPpdToOptKey CNPaperGap --papergap
Hope this helps.
Ciao
Dave Gutteridge wrote:
>
>> system-config-printer-gui
>
>
> Ah! There it is.
>
> Well, Everything went according to plan as far as the web site
> instructions went.
>
> However, when trying to print a test page, I got the following error
> output:
>
> I [19/Aug/2005:18:07:16 +0900] Adding start banner page "none" to job 3.
> I [19/Aug/2005:18:07:16 +0900] Adding end banner page "none" to job 3.
> I [19/Aug/2005:18:07:16 +0900] Job 3 queued on 'Canon' by 'root'.
> I [19/Aug/2005:18:07:16 +0900] Started filter
> /usr/lib/cups/filter/pstops (PID 6160) for job 3.
> I [19/Aug/2005:18:07:16 +0900] Started filter
> /usr/lib/cups/filter/foomatic-rip (PID 6161) for job 3.
> I [19/Aug/2005:18:07:16 +0900] Started backend
> /usr/lib/cups/backend/usb (PID 6162) for job 3.
>
> And at the command prompt where I had originally started
> system-config-printer-gui, I got these error messages:
>
> No match for USB device:
> mfr "Canon"
> model "iP_3100"
> desc "Canon iP_3100"
> cmdset "BJL,BJRaster3,BSCCe"
> Please report this message in Bugzilla:
> https://bugzilla.redhat.com/bugzilla
> Choose 'foomatic' as the component.
>
> Does anyone smarter than me (which is anyone) have any idea if there
> are any potential clues in this?
> Note that I'm fully prepared for my printer to not work. But I'm not
> ready to give up quite yet.
>
> Dave
> _______________________________________________
> CentOS mailing list
> CentOS(a)centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
20 years, 7 months
Re: [CentOS-devel] Is there any way to follow errata for Stream 8?
by Josh Boyer
On Fri, Aug 20, 2021, 5:16 PM Neal Gompa <ngompa13(a)gmail.com> wrote:
> On Fri, Aug 20, 2021 at 4:09 PM Josh Boyer <jwboyer(a)redhat.com> wrote:
> >
> > On Fri, Aug 20, 2021 at 3:36 PM Neal Gompa <ngompa13(a)gmail.com> wrote:
> > >
> > > On Fri, Aug 20, 2021 at 2:41 PM Josh Boyer <jwboyer(a)redhat.com> wrote:
> > > >
> > > > On Fri, Aug 20, 2021 at 1:37 PM Carl George <carl(a)redhat.com> wrote:
> > > > >
> > > > > On Fri, Aug 20, 2021 at 11:35 AM Neal Gompa <ngompa13(a)gmail.com>
> wrote:
> > > > > >
> > > > > > On Fri, Aug 20, 2021 at 12:28 PM Johnny Hughes <
> johnny(a)centos.org> wrote:
> > > > > > >
> > > > > > > On 8/19/21 11:21 PM, John R. Dennison wrote:
> > > > > > > > On Fri, Aug 20, 2021 at 06:05:49AM +0200, Steven Rosenberg
> via CentOS-devel wrote:
> > > > > > > >> Even emails like I see for for CentOS 7 would be ok.
> > > > > > > >
> > > > > > > > Considering that people have had nearly 2 years to get such
> notices out
> > > > > > > > for 8 and it's still not happened I wouldn't hold my breath
> if I were
> > > > > > > > you.
> > > > > > > >
> > > > > > >
> > > > > > > I would provide the information if i could, it is not easy to
> do because
> > > > > > > of modularity.
> > > > > > >
> > > > > > > The thing that builds el8 modules is called MBS .. if you look
> at MBS
> > > > > > > operations, one of the things that gets generated as part of
> the
> > > > > > > filename. Here is an example:
> > > > > > >
> > > > > > > https://koji.mbox.centos.org/koji/buildinfo?buildID=18783
> > > > > > >
> > > > > > > Part of the file name is dynamic, created by MBS at build
> time. For
> > > > > > > example, one of the Source RPM filenames generated is:
> > > > > > >
> > > > > > > runc-1.0.0-74.rc95.module_el8.4.0+886+c9a8d9ad.src.rpm
> > > > > > >
> > > > > > > That is not it's filename in RHEL8. In RHEL 8 .. the filename
> is:
> > > > > > >
> > > > > > > runc-1.0.0-74.rc95.module+el8.4.0+11822+6cc1e7d7.src.rpm
> > > > > > >
> > > > > > > There is no easy way to figure out the file names that match
> up between
> > > > > > > the two systems. I took me 15 minutes to figure out that one
> filename,
> > > > > > > this does not scale.
> > > > > >
> > > > > > Everything prior to ".module" should be unique, identifiable, and
> > > > > > identical between RHEL and CentOS. MBS whacks %dist to add MBS
> > > > >
> > > > > Not exactly. Sometimes RHEL maintainers add digits after %dist,
> which
> > > > > results in NVRs like foo-1.0-1.module_el8.4.0+123+a0a0a0a0.1. It's
> > > > > not impossible to parse, but it's much more complicated that just
> > > > > ignoring everything after ".module".
> > > > >
> > > > > > information at the end. So there is some mapping. Additionally,
> when
> > > > > > the RPMs are imported from RHEL into CentOS, the original NVR is
> > > > > > present as a tag. Ignoring transmodrifier remapping modulemd
> commits
> > > > > > between RHEL and CentOS, you have enough baseline references to
> be
> > > > > > able to connect the dots because the RHEL dist-git shorthash is
> > > > > > present in the import tag, which would exist in the imported
> modulemd
> > > > > > before transmodification.
> > > > > >
> > > > > > That process could be automated, but I was never particularly
> > > > > > motivated to do it because of the historical attitude around
> providing
> > > > > > errata for CentOS users like Fedora users get.
> > > > >
> > > > > I'm not aware of any policy against allowing this in the project.
> If
> > > > > there is I hope board members will speak up and clarify that. I
> > > > > suspect it's more of a resource thing than anything.
> > > >
> > > > I think lack of awareness of a publicly documented policy against
> > > > allowing this in the project is likely true, but also irrelevant. We
> > > > don't have a policy against allowing a FreeBSD kernel or using
> > > > Ubuntu's version of gcc, yet we wouldn't do those. In the absence of
> > > > meticulously detailed bylaws, we have historical precedent setting
> > > > defacto policy. I don't expect this to change.
> > > >
> > > > That being said, an update metadata mechanism for CentOS Stream is
> > > > certainly hampered by resource constraints both in terms of tooling
> > > > and in terms of the impact on the people developing the OS through
> the
> > > > CentOS Stream project. For a continuously developed and continuously
> > > > delivered OS, we expect a large amount of churn on a day to day
> basis.
> > > > Updates are a regular occurence, and they're important either because
> > > > of fixes or because of new features. Changes are documented in MRs,
> > > > RPM changelogs, and referenced bugs for those interested.
> > > >
> > >
> > > It's always been possible to have updateinfo generated as build
> > > submissions go through. That's literally how it's done in Fedora with
> > > Bodhi.
> > >
> > > It's not that much of a stretch to say "deploy Bodhi, make voting
> > > advisory or turn it off, and have builds submitted through it with the
> > > right information and auto-release based on gating checks". That
> > > structured data can be pulled in and used for Red Hat update
> > > advisories internally too, which simplifies the pipeline to validate
> > > and release updates. Or if you have a beef against Bodhi, then why not
> > > use the tooling Scientific Linux created to make updateinfo? Troy and
> > > Pat are very familiar with it, and it's publicly available:
> > > https://pagure.io/python-Updateinfo
> > >
> > > Okay, let's say we can't do it for CentOS Stream 8 because of resource
> > > constraints. Well then, what about CentOS Stream 9, where the RHEL
> > > developers themselves are submitting the builds? There's no logical
> > > resourcing problem there. Deploy Bodhi for update submissions and tie
> >
> > You have clearly never worked on making a change to a RHEL package :).
> > I will promise you that there are already a significant number of
> > steps that developers must do to even get to the point where they can
> > file an MR. Putting more process and tooling and hurdles in their way
> > before the code even gets into RHEL is absolutely a resource problem
> > and I am not going to sign them up to do that. If anything, we're
> > trying to simplify even though many will tell you it doesn't look like
> > that.
> >
> > I know you meant that with good intention, but it's easy to read it as
> > "there's no resourcing problem because someone else has to do the
> > work."
> >
>
> I certainly have made changes to RHEL packages. My name exists in
> changelogs and commits in enough packages in RHEL and CentOS Stream
> that I think that would be an unfair characterization. :)
> I'm aware of most of the steps for making package changes in RHEL, and
> I already am aware that packagers for RHEL have to go through the
> effort of declaring what an update is, what it's for, and whether it
> requires relogin/reboot to fully apply.
These are the core properties
> that are defined in updateinfo. Defining them to push a build in
> CentOS Stream is something that I don't think is an unreasonable ask.
> It's the same thing we ask community folks in Fedora to do, after all.
>
We don't ask the Fedora community to do it twice through two different
tools though. Again, I'm not adding more process to an already arduous
process.
Also, it's a case of frequency as well. An errata in RHEL has to be
finalized officially once before it's released. Some maintainers do it
multiple times as they go, but many do not. Bugs attached, notes updated,
etc need to be completed before GA, every 6 months. Your proposal would
require them to do this for every build. That's expensive.
> > the gating into the auto-release criteria. The Fedora CI folks were
> > > already doing that for Fedora Rawhide, so it's no stretch to have it
> > > for CentOS Stream too.
> > >
> > > The idea is not new: I've talked to the CentOS project folks about it
> > > many times in the past. They get *extremely* uncomfortable and tell me
> > > that they can't do it for various reasons even though they want to.
> > > It's one of the biggest complaints everyone has about the project.
> > > It's made worse by the fact that none of the ecosystem tooling for
> > > updates works in any useful manner without updateinfo. RPM changelogs
> > > are no substitute because no automation works with that. You know that
> > > as well as everyone else here.
> >
> > Producing that information isn't only about tooling, and the fact that
> > people would immediately rely on it for automation makes it difficult
> > to suggest anyone else doing it on the side is a viable solution. If
> > it's wrong, that has bad consequences. I'd certainly be against it
> > under the project umbrella if it wasn't part of the official delivery
> > anyway.
> >
> > I still question the utility of it though. It's a continuous delivery
> > model. You have to update. Want to know if you have all available
> > bug fixes? Update. If your bug isn't fixed, it doesn't change the
> > fact that you have all *available* bug fixes. There are no batches or
> > releases. It's called Stream for a reason.
> >
>
> That doesn't mean I shouldn't have the ability to configure
> dnf-automatic to apply all updates automatically that don't require
> relogin and reboot and then have it email me to notify me for updates
> that *do* require that so I can schedule time to actually go and apply
> it.
The list that sets needs reboot via errata is literally hard coded to a few
packages, and we have other tools being introduced that will actually
measure this via runtime heuristics via dnf plugins. I'm happy to just
give you the list, (kernel, glibc, systemd, maybe one or two others) and
you're welcome to use the improved tools already in the distro.
josh
4 years, 7 months
Re: [CentOS] CentOS Digest, Vol 140, Issue 1
by SUDHANSHU BHUTANI
On Thu, Sep 1, 2016 at 5:30 PM, <centos-request(a)centos.org> wrote:
> Send CentOS mailing list submissions to
> centos(a)centos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.centos.org/mailman/listinfo/centos
> or, via email, send a message with subject or body 'help' to
> centos-request(a)centos.org
>
> You can reach the person managing the list at
> centos-owner(a)centos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of CentOS digest..."
>
>
> Today's Topics:
>
> 1. Re: CentOS 6 - logwatch report not in HTML format (Arun Khan)
> 2. Re: NODEJS010-NPM is not getting installed due to dependency
> errors on Custom Centos ISO installation (Jim Perrin)
> 3. Re: CentOS 6 - logwatch report not in HTML format
> (Alexander Farber)
> 4. Re: CentOS 6 - logwatch report not in HTML format (Arun Khan)
> 5. Re: CentOS 6 - logwatch report not in HTML format
> (Alexander Farber)
> 6. Re: group write permissions not being respected (Gordon Messmer)
> 7. Re: CentOS 6 - logwatch report not in HTML format (Arun Khan)
> 8. Re: group write permissions not being respected (Pat Haley)
> 9. Re: group write permissions not being respected (m.roth(a)5-cent.us)
> 10. Re: group write permissions not being respected (Pat Haley)
> 11. Re: group write permissions not being respected (Chris Murphy)
> 12. Perl Unsafe Module Path Handling Directory Traversal
> Vulnerability ( CVE-2016-1238) (Sidharth Sharma)
> 13. Bind Vulnerability CVE-2016-2775 (Sidharth Sharma)
> 14. Re: "Windows" share issue; access via smb:// fails, "mount -t
> cifs" works (Toralf Lund)
> 15. Re: Bind Vulnerability CVE-2016-2775 (James Pearson)
> 16. Re: Bind Vulnerability CVE-2016-2775 (Mike Burger)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 31 Aug 2016 07:11:11 -0700
> From: Arun Khan <knura9(a)gmail.com>
> To: CentOS mailing list <centos(a)centos.org>
> Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format
> Message-ID:
> <CAHhM8gCz6SDqu8i5aHkUU58Sb91cHdNKUy=J_rYP25X48gk22Q(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Mon, Aug 29, 2016 at 10:24 PM, Alexander Farber
> <alexander.farber(a)gmail.com> wrote:
>> No, I mean there is sometimes a variable for mail format too:
>
> The HTML formatting is a logwatch option, invoked through the
> logwatch.conf file.
>
> -- Arun Khan
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 31 Aug 2016 09:20:26 -0500
> From: Jim Perrin <jperrin(a)centos.org>
> To: centos(a)centos.org
> Subject: Re: [CentOS] NODEJS010-NPM is not getting installed due to
> dependency errors on Custom Centos ISO installation
> Message-ID: <a607d751-c5e7-91eb-9e81-b6cdb379ecfa(a)centos.org>
> Content-Type: text/plain; charset=windows-1252
>
>
>
> On 08/31/2016 03:48 AM, SUDHANSHU BHUTANI wrote:
>> Hi,
>>
>> I have built successfully all the dependent packages of nodejs010 and npm.
>>
>> I have used following command:-
>> *rpmbuild --define 'scl nodejs010' --bb SPEC/name_of_spec.spec*
>
> You should really use mock, so that you don't have unintended libraries
> from your build host included/linked/required in the resulting rpm.
Thanks Jim for responding.
I tried with mock configuration, but, not sure, i am still getting the
same errors via repoclosre tool:-
This directory has got all the RPMs formed by mock.
[root@localhost YUM_CISCO_RPMS]# repoclosure -r Cisco-yum-dep-check
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 1
Cisco-yum-dep-check
Num Packages in Repos: 1515
package: nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch
from Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(readable-stream) < 0:2
package: nodejs010-nodejs-cmd-shim-2.0.0-2.el7.centos.noarch from
Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(graceful-fs) < 0:4
package: nodejs010-nodejs-columnify-1.3.2-3.el7.centos.noarch from
Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(strip-ansi) >= 0:2.0.0
package: nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.centos.noarch
from Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(minimatch) < 0:3
package: nodejs010-nodejs-gauge-1.2.2-3.el7.centos.noarch from
Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(has-unicode) < 0:2
package: nodejs010-nodejs-init-package-json-1.9.1-1.el7.centos.noarch
from Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(promzard) >= 0:0.3.0
package: nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch
from Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(retry) >= 0:0.8.0
nodejs010-npm(request) >= 0:2.47.0
nodejs010-npm(concat-stream) >= 0:1.4.6
package: nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch from
Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(is-absolute) < 0:0.2
The only difference from my (for build of
nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch.rpm) build-log and
http://cbs.centos.org/kojifiles/packages/nodejs010-nodejs-are-we-there-yet/…
is following line:-
*Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates)
nodejs010-npm(readable-stream)* - >> THIS IS FROM CBS mock log
and following is my build log:-
*Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates) >= 0.1.0
nodejs010-npm(delegates) < 0.2 nodejs010-npm(readable-stream) >=
1.1.13 nodejs010-npm(readable-stream) < 2*
I am not sure, why parsing of these version is defining a range, maybe
its coming from package.json file.
I feel, its related to nodejs010-build package which has
root/usr/lib/rpm/nodejs010.req, i defined mock configuration like
this:-
config_opts['root'] = 'epel-7-x86_64'
config_opts['target_arch'] = 'x86_64'
config_opts['legal_host_arches'] = ('x86_64',)
config_opts['chroot_setup_cmd'] = 'install @buildsys-build
scl-utils-build nodejs010-build'
Do they look good?
Following is my build.log
[sbhutani@localhost ~]$ cat nodejs-build/nodejs010-
Display all 316 possibilities? (y or n)
[sbhutani@localhost ~]$ cat
nodejs-build/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.src.rpm/build.log
Mock Version: 1.2.18
ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target
x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'],
chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=FalseprintOutput=Falseenv={'LANG':
'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME':
'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"',
'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1':
'<mock-chroot> \\s-\\v\\$
'}gid=135user='mockbuild'timeout=0logger=<mockbuild.trace_decorator.getLog
object at 0x22e3390>uid=1000)
Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs
--target x86_64 --nodeps
/builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG':
'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME':
'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"',
'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1':
'<mock-chroot> \\s-\\v\\$ '} and shell False
Building target platforms: x86_64
Building for target x86_64
Wrote: /builddir/build/SRPMS/nodejs-are-we-there-yet-1.0.4-1.el7.centos.src.rpm
Child return code was: 0
Mock Version: 1.2.18
ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target
x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'],
chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=FalseprintOutput=Trueenv={'LANG':
'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME':
'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"',
'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1':
'<mock-chroot> \\s-\\v\\$
'}gid=135user='mockbuild'timeout=0logger=<mockbuild.trace_decorator.getLog
object at 0x1772390>uid=1000)
Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs
--target x86_64 --nodeps
/builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG':
'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME':
'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"',
'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1':
'<mock-chroot> \\s-\\v\\$ '} and shell False
Building target platforms: x86_64
Building for target x86_64
Wrote: /builddir/build/SRPMS/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.src.rpm
Child return code was: 0
Mock Version: 1.2.18
ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target
x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'],
chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=FalseprintOutput=Falseenv={'LANG':
'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME':
'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"',
'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1':
'<mock-chroot> \\s-\\v\\$
'}gid=135user='mockbuild'timeout=0logger=<mockbuild.trace_decorator.getLog
object at 0x142d390>uid=1000)
Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs
--target x86_64 --nodeps
/builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG':
'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME':
'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"',
'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1':
'<mock-chroot> \\s-\\v\\$ '} and shell False
Building target platforms: x86_64
Building for target x86_64
Wrote: /builddir/build/SRPMS/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.src.rpm
Child return code was: 0
ENTER ['do'](['bash', '--login', '-c', u'/usr/bin/rpmbuild -bb
--target x86_64 --nodeps
/builddir/build/SPECS/nodejs-are-we-there-yet.spec'],
chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=Falseuid=1000env={'LANG':
'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME':
'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"',
'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1':
'<mock-chroot> \\s-\\v\\$
'}gid=135user='mockbuild'timeout=0private_network=Truelogger=<mockbuild.trace_decorator.getLog
object at 0x142d390>printOutput=False)
Executing command: ['bash', '--login', '-c', u'/usr/bin/rpmbuild -bb
--target x86_64 --nodeps
/builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG':
'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME':
'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"',
'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1':
'<mock-chroot> \\s-\\v\\$ '} and shell False
Building target platforms: x86_64
Building for target x86_64
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.cNqdgI
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf package
+ /usr/bin/gzip -dc /builddir/build/SOURCES/are-we-there-yet-1.0.4.tgz
+ /usr/bin/tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd package
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ rm -rf node_modules
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.iiP8RP
+ umask 022
+ cd /builddir/build/BUILD
+ cd package
+ exit 0
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.IFmFuX
+ umask 022
+ cd /builddir/build/BUILD
+ '[' /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64
'!=' / ']'
+ rm -rf /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64
++ dirname /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64
+ mkdir -p /builddir/build/BUILDROOT
+ mkdir /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64
+ cd package
+ mkdir -p /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/lib/node_modules/are-we-there-yet
+ cp -pr package.json index.js
/builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/lib/node_modules/are-we-there-yet
+ /usr/lib/rpm/nodejs010-symlink-deps
/opt/rh/nodejs010/root/usr/lib/node_modules
+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz
--dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000
/builddir/build/BUILD/package
/usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 0 CRC32s did match.
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/brp-scl-compress /opt/rh/nodejs010/root
+ /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/brp-scl-python-bytecompile /usr/bin/python 1
/opt/rh/nodejs010/root
+ /usr/lib/rpm/brp-python-hardlink
+ /usr/lib/rpm/redhat/brp-java-repack-jars
Processing files: nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch
Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.7DYIy5
+ umask 022
+ cd /builddir/build/BUILD
+ cd package
+ DOCDIR=/builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/share/doc/nodejs010-nodejs-are-we-there-yet-1.0.4
+ export DOCDIR
+ /usr/bin/mkdir -p
/builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/share/doc/nodejs010-nodejs-are-we-there-yet-1.0.4
+ cp -pr README.md
/builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/share/doc/nodejs010-nodejs-are-we-there-yet-1.0.4
+ exit 0
Finding Provides: /usr/lib/rpm/nodejs010.prov
Finding Requires(interp):
Finding Requires(rpmlib):
Finding Requires(verify):
Finding Requires(pre):
Finding Requires(post):
Finding Requires(preun):
Finding Requires(postun):
Finding Requires(pretrans):
Finding Requires(posttrans):
Finding Requires: /usr/lib/rpm/nodejs010.req
Provides: nodejs010-nodejs-are-we-there-yet = 1.0.4-1.el7.centos
nodejs010-npm(are-we-there-yet) = 1.0.4
Requires(rpmlib): rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <=
3.0.4-1
Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates) >= 0.1.0
nodejs010-npm(delegates) < 0.2 nodejs010-npm(readable-stream) >=
1.1.13 nodejs010-npm(readable-stream) < 2
Checking for unpackaged file(s): /usr/lib/rpm/check-files
/builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64
Wrote: /builddir/build/RPMS/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.yi6hbn
+ umask 022
+ cd /builddir/build/BUILD
+ cd package
+ /usr/bin/rm -rf
/builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64
+ exit 0
Child return code was: 0
[sbhutani@localhost ~]$
Can any one catch difference between my build.log and CBS build.log.
If hhorak is on this mailing list who actually built this package on
CBS, can help?
Appreciate your inputs.
>>
>> Following is the list of RPMs cloned and built from GIT:-
>>
>
> <snip>
>
>
>>
>> *However, when we copy these RPMS to our ISO, anaconda installer fails
>> to install due to dependency errors:-*
>
>
> You should use the 'repoclosure' utility to make sure that you have met
> all the dependencies of packages in the repo on your iso.
>
>
>
>> How is it possible, to get these errors, how come packages are not
>> satisfying minimum dependency for working of NPM?
>
>
> repoclosure should tell you. You may be missing something scl related.
>
>
>>
>> If i do yumdownloader for all these above RPMs from repo: [centos-sclo-rh]
>> : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/) then i
>> get following RPMs without "centos" name:-
>
>
> Correct. This is an rpm macro change. by default the 'centos' is added
> in there.
>
>
>>
>> *If i copy paste above RPMS to my custom ISO, then anaconda
>> successfully installs these packages, without any errors*
>
>
> This would suggest something is wrong with your build. See previous
> statement about using mock vs rpmbuild.
>
>
>> *What is there is these already built RPMs (taken from repo: [centos-sclo-rh]
>> : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/) which
>> is not there in my built RPMS?*
>
> That's kind of up to you to figure out, since we can't see your custom
> built ones.
>
>
>> Any pointers for this, as we feel, there is some inconsistency in the
>> version available on git.centos.org/git/rpms/<name_of_pkg>.git ?
>
> More likely it's in your build method.
>
>
> --
> Jim Perrin
> The CentOS Project | http://www.centos.org
> twitter: @BitIntegrity | GPG Key: FA09AD77
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 31 Aug 2016 16:58:17 +0200
> From: Alexander Farber <alexander.farber(a)gmail.com>
> To: CentOS mailing list <centos(a)centos.org>
> Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format
> Message-ID:
> <CAADeyWiMVpHh=CDZ6zi_OEq+5HwysoqTAOABDnM4mkYeFDhxYA(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> logwatch is run as cronjob.
>
> On Wed, Aug 31, 2016 at 4:11 PM, Arun Khan <knura9(a)gmail.com> wrote:
>
>> On Mon, Aug 29, 2016 at 10:24 PM, Alexander Farber
>> <alexander.farber(a)gmail.com> wrote:
>> > No, I mean there is sometimes a variable for mail format too:
>>
>> The HTML formatting is a logwatch option, invoked through the
>> logwatch.conf file.
>>
>> -- Arun Khan
>> _______________________________________________
>> CentOS mailing list
>> CentOS(a)centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 31 Aug 2016 08:31:28 -0700
> From: Arun Khan <knura9(a)gmail.com>
> To: CentOS mailing list <centos(a)centos.org>
> Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format
> Message-ID:
> <CAHhM8gDhhgRNb1C2rKRdE+v8w_fEhBmCvarf3MxO=njxL7w3-g(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Wed, Aug 31, 2016 at 7:58 AM, Alexander Farber
> <alexander.farber(a)gmail.com> wrote:
>> logwatch is run as cronjob.
>
> Let's take cron out of the picture. Invoking logwatch from an
> interactive shell -- no joy. The report still goes out in text
> format.
>
> -- Arun Khan
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 31 Aug 2016 17:59:44 +0200
> From: Alexander Farber <alexander.farber(a)gmail.com>
> To: CentOS mailing list <centos(a)centos.org>
> Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format
> Message-ID:
> <CAADeyWiYQ_TNjZHZ9af2x3TM_Lq+U9LE+y4aheb6BXV_TBwGaQ(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> You should have provided more info initially.
>
> "goes out in text format" might mean several things.
>
> On Wed, Aug 31, 2016 at 5:31 PM, Arun Khan <knura9(a)gmail.com> wrote:
>
>> On Wed, Aug 31, 2016 at 7:58 AM, Alexander Farber
>> <alexander.farber(a)gmail.com> wrote:
>> > logwatch is run as cronjob.
>>
>> Let's take cron out of the picture. Invoking logwatch from an
>> interactive shell -- no joy. The report still goes out in text
>> format.
>>
>> -- Arun Khan
>> _______________________________________________
>> CentOS mailing list
>> CentOS(a)centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 31 Aug 2016 09:50:45 -0700
> From: Gordon Messmer <gordon.messmer(a)gmail.com>
> To: CentOS mailing list <centos(a)centos.org>
> Subject: Re: [CentOS] group write permissions not being respected
> Message-ID: <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 08/30/2016 03:01 PM, Pat Haley wrote:
>> the owner of a directory can still write to that directory but any
>> other member of the associated group cannot, even though the directory
>> clearly has group write permissions set
>
>
> Use "getfacl" on both the client and server side to view the complete
> permission set. What do those look like?
>
>
>
> ------------------------------
>
> Message: 7
> Date: Wed, 31 Aug 2016 10:00:42 -0700
> From: Arun Khan <knura9(a)gmail.com>
> To: CentOS mailing list <centos(a)centos.org>
> Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format
> Message-ID:
> <CAHhM8gBBc+i9VH=eiGM+K7ePerQbv4Nraa5ck7YMEixrhbzaoQ(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Wed, Aug 31, 2016 at 8:59 AM, Alexander Farber
> <alexander.farber(a)gmail.com> wrote:
>> You should have provided more info initially.
>>
>> "goes out in text format" might mean several things.
>>
>
> I don't know what you mean by "several things"
>
> In the context of logwatch the only options are HTML or TEXT. Please see my OP.
>
> Thanks for your assistance.
>
> -- Arun Khan
>
>
> ------------------------------
>
> Message: 8
> Date: Wed, 31 Aug 2016 13:11:09 -0400
> From: Pat Haley <phaley(a)mit.edu>
> To: centos(a)centos.org
> Cc: Steve Postma <SPostma(a)ztechnet.com>
> Subject: Re: [CentOS] group write permissions not being respected
> Message-ID: <8d59038f-3dbe-5bff-9673-fbada1d3f31c(a)mit.edu>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
>
> So far, those look the same
>
> client:
>
> [root@mseas FixOwn]# getfacl /gdata/bibliography/Work/GroupBib/trunk/
> getfacl: Removing leading '/' from absolute path names
> # file: gdata/bibliography/Work/GroupBib/trunk/
> # owner: phaley
> # group: mseasweb
> # flags: -s-
> user::rwx
> group::rwx
> other::r-x
>
> server:
>
> [root@mseas-data2 ~]# getfacl /gdata/bibliography/Work/GroupBib/trunk/
> getfacl: Removing leading '/' from absolute path names
> # file: gdata/bibliography/Work/GroupBib/trunk/
> # owner: phaley
> # group: mseasweb
> # flags: -s-
> user::rwx
> group::rwx
> other::r-x
>
>
> On 08/31/2016 12:50 PM, Gordon Messmer wrote:
>> On 08/30/2016 03:01 PM, Pat Haley wrote:
>>> the owner of a directory can still write to that directory but any
>>> other member of the associated group cannot, even though the
>>> directory clearly has group write permissions set
>>
>>
>> Use "getfacl" on both the client and server side to view the complete
>> permission set. What do those look like?
>>
>> _______________________________________________
>> CentOS mailing list
>> CentOS(a)centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>
> --
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Pat Haley Email: phaley(a)mit.edu
> Center for Ocean Engineering Phone: (617) 253-6824
> Dept. of Mechanical Engineering Fax: (617) 253-8125
> MIT, Room 5-213 http://web.mit.edu/phaley/www/
> 77 Massachusetts Avenue
> Cambridge, MA 02139-4301
>
>
>
> ------------------------------
>
> Message: 9
> Date: Wed, 31 Aug 2016 14:04:28 -0400
> From: m.roth(a)5-cent.us
> To: "CentOS mailing list" <centos(a)centos.org>
> Subject: Re: [CentOS] group write permissions not being respected
> Message-ID:
> <b9abfd5a5a37f29bff085aae6174877f.squirrel(a)host290.hostmonster.com>
> Content-Type: text/plain;charset=utf-8
>
> Stupid question, and note I missed most of the earlier posts in this
> thread: what are the permissions on the directory that this directory are
> in?
>
> mark
>
>
>
> ------------------------------
>
> Message: 10
> Date: Wed, 31 Aug 2016 15:06:25 -0400
> From: Pat Haley <phaley(a)mit.edu>
> To: centos(a)centos.org
> Subject: Re: [CentOS] group write permissions not being respected
> Message-ID: <d9ac7e12-3283-ea9e-a5b0-5dcd8d27d87d(a)mit.edu>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
>
> For example the directory /gdata/bibliography/Work/GroupBib/trunk/ can
> be written in by user phaley but not by other users who are member of
> the group mseasweb. The directory has permissions
>
> [root@mseas ~]# ls -lh /gdata/bibliography/Work/GroupBib
> total 12K
> drwxrwsr-x 4 phaley mseasweb 4.0K Aug 30 12:31 trunk
>
> The parent directory (/gdata/bibliography/Work/GroupBib) has permissions
>
> [root@mseas ~]# ls -lh /gdata/bibliography/Work/
> total 8.0K
> drwxrwsr-x 6 phaley mseasweb 4.0K Aug 30 14:01 GroupBib
>
>
>
> On 08/31/2016 02:04 PM, m.roth(a)5-cent.us wrote:
>> Stupid question, and note I missed most of the earlier posts in this
>> thread: what are the permissions on the directory that this directory are
>> in?
>>
>> mark
>>
>> _______________________________________________
>> CentOS mailing list
>> CentOS(a)centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>
> --
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Pat Haley Email: phaley(a)mit.edu
> Center for Ocean Engineering Phone: (617) 253-6824
> Dept. of Mechanical Engineering Fax: (617) 253-8125
> MIT, Room 5-213 http://web.mit.edu/phaley/www/
> 77 Massachusetts Avenue
> Cambridge, MA 02139-4301
>
>
>
> ------------------------------
>
> Message: 11
> Date: Thu, 01 Sep 2016 03:38:11 +0000
> From: Chris Murphy <lists(a)colorremedies.com>
> To: CentOS mailing list <centos(a)centos.org>
> Subject: Re: [CentOS] group write permissions not being respected
> Message-ID:
> <CAJCQCtTfr6rvPGH7uMNzYE9-Q+BfZ784a5n=4S5NekA7O8VxAA(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Try booting with enforcing=0 and if that fixes it, you need to find out
> what security label is needed for gluster.
>
> Chances are it's easiest to use -o context= mount option on the brick, but
> if the brick is not exclusive to gluster you'll need chcon -R.
>
> If that's not it, maybe try the gluster client instead of using NFS. See if
> you get a different result that narrows down what's going on.
>
> My vague recollection is for Samba, without the correct SELinux label, I
> could neither read nor write.
>
>
> Chris Murphy
>
>
> ------------------------------
>
> Message: 12
> Date: Thu, 1 Sep 2016 11:03:30 +0530
> From: Sidharth Sharma <sharma.sidharth86(a)gmail.com>
> To: centos(a)centos.org
> Subject: [CentOS] Perl Unsafe Module Path Handling Directory Traversal
> Vulnerability ( CVE-2016-1238)
> Message-ID:
> <CAAQ4EFk7qgWvq=ZtSOugxsgQ1S54y8cFbiG33POQme8+cDrcSw(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hello Experts,
>
> When we can expect Security Update for Perl Vulnerability CVE-2016-1238 on
> CentOS 6.8 and 7.2?
>
> --
> With Thanks & Regards:
> Sidharth Sharma
>
>
> ------------------------------
>
> Message: 13
> Date: Thu, 1 Sep 2016 11:05:36 +0530
> From: Sidharth Sharma <sharma.sidharth86(a)gmail.com>
> To: centos(a)centos.org
> Subject: [CentOS] Bind Vulnerability CVE-2016-2775
> Message-ID:
> <CAAQ4EF=2AeThtVjJitR3JHGhuunRJ4AZHiYDcrp4vcKFxUV=UQ(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hello Experts,
>
> When we can expect Security Update for Bind Vulnerability on Centos 6.8/7.2?
> ISC BIND Lightweight Resolver Protocol Req Processing Dos Vulnerability:
> CVE-2016-2775
>
> --
> With Thanks & Regards:
> Sidharth Sharma
>
>
> ------------------------------
>
> Message: 14
> Date: Thu, 1 Sep 2016 10:26:34 +0200
> From: Toralf Lund <toralf.lund(a)pgs.com>
> To: CentOS mailing list <centos(a)centos.org>
> Subject: Re: [CentOS] "Windows" share issue; access via smb:// fails,
> "mount -t cifs" works
> Message-ID: <2265d62b-32b6-6d51-5848-df84f5800723(a)pgs.com>
> Content-Type: text/plain; charset="utf-8"; format=flowed
>
> On 30/08/16 10:00, Toralf Lund wrote:
>> Hi,
>>
>> Is anyone here using smb:// URLs to access "Windows" shares? I've been
>> doing this for a while with common file systems at work, and it used
>> to work just fine. Then I while back, I started getting issues; I will
>> now just keep getting asked for a password when I try to access
>> something through smb://. I thought at first that this meant there had
>> been some kind of change related to permissions on the shares, but now
>> I find that I can mount them just fine using "mount -t cifs".
> I found out a bit more about this - I believe that I have the issue
> described here:
>
> http://community.netapp.com/t5/Network-Storage-Protocols-Discussions/samba-…
>
> In other words, the problem is that "SPNEGO" fails. If I add "client use
> spnego = no" to /etc/samba/smb.conf, smbclient access works (I found
> that I also got a problem there), but unfortunately, gvfs-mount still
> doesn't. The debug output that I get if I run gvfsd on the command line
> with "GVFS_DEBUG=1" and "GVFS_SMB_DEBUG=99" actually still report SPNEGO
> errors, so it would appear that the smp.conf option is for some reason
> ignored. In other words the question may be:
>
> How do I disabled SPNEGO for gvfs-mount?
>
> Also, the above suggest that whether this problem occurs depends on
> whether "you have SMB signing turned on or not under the 'cifs' options
> section", but it not clear to me what options exactly this refers to.
> Anyone?
>
> Oh, and some other posts I found seem to indicate that mount.cifs
> doesn't support SPNEGO yet, so I guess that's why a "normal" mount works.
>
> - Toralf
>
>
>>
>> In other words, I get:
>>
>> gvfs-mount smb://mydomain\;toralf.lund@theserver/myshare
>> Password required for share myshare on theserver
>> Password:
>> Password required for share myshare on theserver
>> Password:
>> Password required for share myshare on theserver
>> Password:
>>
>> [ I enter the correct password, but gvs-mount keeps asking...
>> Behaviour is the same if I try to open the URL in the file manager
>> instead. ]
>>
>> mount -t cifs -o user=toralf.lund,workgroup=mydomain
>> //theserver/myshare /tmp_mnt/
>> Password:
>>
>> [ At this stage the filesystem is mounted, as long as I enter the
>> correct password. ]
>>
>> Does anyone have any idea what is going on here? Why does the VFS
>> mount fail when mount.cifs works on the same share? Is there a
>> difference in the way authentication works, or something? Has there
>> been a change to the smb support that might explain this?
>>
>> This is on a CentOS 6 x86_64 installation with all updates applied.
>>
>> - Toralf
>>
>
>
>
> ------------------------------
>
> Message: 15
> Date: Thu, 1 Sep 2016 08:34:08 +0000
> From: James Pearson <james-p(a)moving-picture.com>
> To: CentOS mailing list <centos(a)centos.org>
> Subject: Re: [CentOS] Bind Vulnerability CVE-2016-2775
> Message-ID:
> <85C0B54E4752CA4F873E7C78CF0B26F5010FB3748D(a)LNDWSMBX01.ad.mpc.local>
> Content-Type: text/plain; charset="us-ascii"
>
> Sidharth Sharma:
>>
>> When we can expect Security Update for Bind Vulnerability on Centos 6.8/7.2?
>> ISC BIND Lightweight Resolver Protocol Req Processing Dos Vulnerability:
> >CVE-2016-2775
>
> See:
>
> https://access.redhat.com/security/cve/cve-2016-2775
>
> James Pearson
>
> ------------------------------
>
> Message: 16
> Date: Thu, 01 Sep 2016 07:45:04 -0400
> From: Mike Burger <mburger(a)bubbanfriends.org>
> To: CentOS mailing list <centos(a)centos.org>
> Subject: Re: [CentOS] Bind Vulnerability CVE-2016-2775
> Message-ID: <400e82588e4172b96a928e1e3aeef9e3(a)bubbanfriends.org>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> On 2016-09-01 4:34 am, James Pearson wrote:
>> Sidharth Sharma:
>>>
>>> When we can expect Security Update for Bind Vulnerability on Centos
>>> 6.8/7.2?
>>> ISC BIND Lightweight Resolver Protocol Req Processing Dos
>>> Vulnerability:
>> >CVE-2016-2775
>>
>> See:
>>
>> https://access.redhat.com/security/cve/cve-2016-2775
>
> Ouch!
>
> Affected Packages State
> Platform Package State
> Red Hat Enterprise Linux 5 bind97 Will not fix
> Red Hat Enterprise Linux 6 bind Will not fix
> Red Hat Enterprise Linux 5 bind Will not fix
> Red Hat Enterprise Linux 7 bind Will not fix
>
> --
> Mike Burger
> http://www.bubbanfriends.org
>
> "It's always suicide-mission this, save-the-planet that. No one ever
> just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1
>
>
> ------------------------------
>
> _______________________________________________
> CentOS mailing list
> CentOS(a)centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
>
> End of CentOS Digest, Vol 140, Issue 1
> **************************************
9 years, 7 months