Discuss

discuss@lists.centos.org

34753 discussions

cups-1.3.7-32.el5_11.x86_64 may have a problem
by Greg Ennis 24 Jan '16

24 Jan '16

Everyone, I have a problem I have been chasing for about three weeks and only occurred after cups was updated with cups-1.6.3-22.el7. I would be interested as to whether any one else has had this problem, and would entertain suggestions as to how I can debug the problem. My Centos 5 server is a gateway as well as a cups print server that has been in place for 8 years and has continued to perform exceptionally well. My Centos 7 server is a mail server and archive file server that is in the same network as my Centos 5 server described above. I have cups active on this server, which communicates to the Centos 5 server described above as well as another remote Centos 5 cups print server and another remote Centos 6 cups print server. Each of the latter two print servers are on different networks than the Centos 7 server that has the problem. The problem that has been occurring for the last three weeks appears to be related to the Centos 7 server or communication failure between it and the Centos 5 print server in the same network. What happens is that when the Centos 7 archive server receives a command to print an archived file on one of the printers inside its own network it appears to send several print commands to the Centos 5 server which causes the file to be printed several times. What happens is that the users eventually turn off the printer to keep the file from being printed dozens of times, and eventually the cups print queue on the Centos 5 server becomes full and all the printers in that network become unreachable with print commands. It is interesting that the remote print servers appear to function normally during this time. The only way I have figured out to remedy the problem is the use the "cancel -u user" command on the Centos 5 server to get rid of the command on the Centos 5 server and to use cancel lpt2-xxxxx on the Centso 7 server to get rid of the command on the archive server. When I evaluate the logs, I am either blind to the problem or am not seeing much I can piece together. Both machines have all updates and are listed as : Gateway and Cups Print Server : CentOS release 5.11 (Final) with 2.6.18-407.el5.centos.plusxen kernel with cups-1.3.7-32.el5_11.x86_64 Mail server and Archive File server : CentOS Linux release 7.2.1511 (Core) with 3.10.0-327.4.4.el7.x86_64 kernel with cups-1.6.3-22.el7.x86_64 If any of you have ideas, would sure appreciate your help. Greg Ennis

2 2

How does Live CD find OS's?
by Timothy Murphy 24 Jan '16

24 Jan '16

If I boot into CentOS on my home server from a Live CD or USB stick and go to Troubleshoot, it lists OS's it finds on the machine. How does it find these OS's? Presumably it looks through all the partitions on all the hard disks for something that looks like an OS? But how exactly does it identify an OS? -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

3 4

HDD badblocks
by Alessandro Baggi 23 Jan '16

23 Jan '16

Hi list, I've a notebook with C7 (1511). This notebook has 2 disk (640 GB) and I've configured them with MD at level 1. Some days ago I've noticed some critical slowdown while opening applications. First of all I've disabled acpi on disks. I've checked disk for badblocks 4 consecutive times for disk sda and sdb and I've noticed a strange behaviour. On sdb there are not problem but with sda: 1) First run badblocks reports 28 badblocks on disk 2) Second run badblocks reports 32 badblocks 3) Third reports 102 badblocks 4) Last run reports 92 badblocks. Running smartctl after the last badblocks check I've noticed that Current_Pending_Sector was 32 (not 92 as badblocks found). To force sector reallocation I've filled the disk up to 100%, runned again badblocks and 0 badblocks found. Running again smartctl, Current_Pending_Sector 0 but Reallocated_Event Count = 0. Why each consecutive run of badblocks reports different results? Why smartctl does not update Reallocated_Event_Count? Badblocks found on sda increase/decrease without a clean reason. This behaviuor can be related with raid (if a disk had badblocks this badblock can be replicated on second disk?)? What other test I can perform to verify disks problems? Thanks in advance.

12 27

Re: [CentOS] How to get UEFI setting by shell?
by wk 23 Jan '16

23 Jan '16

Hi, another question.With secure boot on, I make a kernel module test.ko Then insmod test.ko: [root@localhost linux]# insmod test.ko insmod: ERROR: could not insert module test.ko: Required key not available How can I sign my test.ko for CentOS7.1? If I set secure boot off, insmod test.ko will be successful. w.k. ------------------ Original ------------------ From: "我自己的邮箱";<304702903(a)qq.com>; Date: Fri, Jan 22, 2016 03:07 PM To: "eero.volotinen"<eero.volotinen(a)iki.fi>; "gordon.messmer"<gordon.messmer(a)gmail.com>; Cc: "centos"<centos(a)centos.org>; Subject: Re: [CentOS] How to get UEFI setting by shell? volotinen and gordon.messmer: thank you for your answers. w.k. ------------------ Original ------------------ From: "Gordon Messmer";<gordon.messmer(a)gmail.com>; Date: Fri, Jan 22, 2016 02:13 PM To: "CentOS mailing list"<centos(a)centos.org>; Subject: Re: [CentOS] How to get UEFI setting by shell? On 01/21/2016 09:47 PM, wk wrote: > How to check/get UEFI information by shell/bash terminal ? example:if UEFI is enabled? if secure boot is enabled? Systems that boot via UEFI will have /sys/firmware/efi. You may have access to your secure boot setting in /sys/firmware/efi/efivars/, or in the output of "bootctl --path /boot/efi status" _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

5 15

How to get UEFI setting by shell?
by wk 22 Jan '16

22 Jan '16

Hi, CentOS7.1, Dell PowerEdge R730xd. How to check/get UEFI information by shell/bash terminal ? example:if UEFI is enabled? if secure boot is enabled? Thanks.

4 3

CentOS-announce Digest, Vol 131, Issue 7
by centos-announce-request＠centos.org 22 Jan '16

22 Jan '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. Announcing release for Gluster 3.6 and 3.7 on CentOS Linux 6 x86_64 (Niels de Vos) 2. CESA-2016:0054 Important CentOS 5 java-1.7.0-openjdk Security Update (Johnny Hughes) 3. CESA-2016:0054 Important CentOS 7 java-1.7.0-openjdk Security Update (Johnny Hughes) 4. CESA-2016:0049 Critical CentOS 7 java-1.8.0-openjdk Security Update (Johnny Hughes) 5. CESA-2016:0053 Critical CentOS 6 java-1.7.0-openjdk Security Update (Johnny Hughes) 6. CESA-2016:0050 Important CentOS 6 java-1.8.0-openjdk Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 21 Jan 2016 17:07:10 +0100 From: Niels de Vos <ndevos(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing release for Gluster 3.6 and 3.7 on CentOS Linux 6 x86_64 Message-ID: <20160121160710.GY4466(a)ndevos-x240.usersys.redhat.com> Content-Type: text/plain; charset="us-ascii" I am happy to announce the General Availability of Gluster 3.6 and 3.7 for CentOS 6 on x86_64. These packages are following the upstream Gluster Community releases, with one minor update for each version per month. Users of CentOS 6 can now simply install Gluster with only these two commands: # yum install centos-release-gluster # yum install glusterfs-server The centos-release-gluster content comes from the centos-release-gluster37 package delivered via CentOS Extras repos. This contains all the metadata and dependancy information, needed to install Gluster 3.7. For people looking at running Gluster 3.6, there is the centos-release-gluster36 package. In order to get this version, substitute the step-1 mentioned above with: # yum install centos-release-gluster36 We have a quickstart guide specifically built around the packages are available now, it makes for a good introduction to Gluster and will help get you started in just a few simple steps, this quick start is available at https://wiki.centos.org/SpecialInterestGroup/Storage/gluster-Quickstart More details about the packages that the Gluster project provides in the Storage SIG is available in the documentation: https://wiki.centos.org/SpecialInterestGroup/Storage/Gluster The centos-release-gluster* repositories offer additional packages that enhance the usability of Gluster itself. Users can request additional tools and applications to be provided, just send us an email with your suggestions. The current list of packages that is (planned to become) available can be found here: https://wiki.centos.org/SpecialInterestGroup/Storage/Gluster/Ecosystem-pkgs Gluster is the first project that provides packages through the Storage SIG. Other projects are in the process to do so too. General information about the SIG can be read in the wiki: https://wiki.centos.org/SpecialInterestGroup/Storage We welcome all feedback, comments and contributions. You can get in touch with the CentOS Storage SIG on the centos-devel mailing list ( https://lists.centos.org ) and with the Gluster developer and user communities at https://www.gluster.org/mailman/listinfo , we are also available on irc at #gluster on irc.freenode.net, and on twitter at @gluster . Cheers, Niels de Vos Storage SIG member & Gluster maintainer

1 0

CentOS 7 magically rebooted!
by Tom Robinson 22 Jan '16

22 Jan '16

CentOS Linux release 7.2.1511 (Core) Hi, Last night our CentOS 7 server rebooted. Seemingly it's a very clean reboot. I can't find a shred of evidence as to why it happened though. Things I've checked: * sa reports * /var/log/{messages,secure,dmesg,cron} * /var/log/audit/audit.log * lastlog The host is used for KVM virtualisation and connects via multipathing to our OmniOS SAN via infiniband. I can provide any logging you may think helpful Here's an excerpt from /var/log/messages at the time of reboot: ---8<--- Jan 21 23:32:01 daytona systemd: Starting Session 10964 of user root. Jan 21 23:32:12 daytona systemd: Started Amanda Backup System (192.168.0.31:703). Jan 21 23:32:12 daytona systemd: Starting Amanda Backup System (192.168.0.31:703)... Jan 21 23:33:01 daytona systemd: Started Session 10965 of user root. Jan 21 23:33:01 daytona systemd: Starting Session 10965 of user root. Jan 21 23:34:01 daytona systemd: Started Session 10966 of user root. Jan 21 23:34:01 daytona systemd: Starting Session 10966 of user root. Jan 21 23:35:01 daytona systemd: Started Session 10967 of user root. Jan 21 23:35:01 daytona systemd: Starting Session 10967 of user root. Jan 21 23:35:34 daytona systemd: Started Amanda Backup System (192.168.0.31:703). Jan 21 23:35:34 daytona systemd: Starting Amanda Backup System (192.168.0.31:703)... Jan 21 23:36:01 daytona systemd: Started Session 10968 of user root. Jan 21 23:36:01 daytona systemd: Starting Session 10968 of user root. Jan 21 23:36:50 daytona systemd: Started Amanda Backup System (192.168.0.31:703). Jan 21 23:36:50 daytona systemd: Starting Amanda Backup System (192.168.0.31:703)... Jan 21 23:37:02 daytona systemd: Started Session 10969 of user root. ---8<--- Jan 21 23:53:01 daytona systemd: Starting Session 10985 of user root. Jan 21 23:54:01 daytona systemd: Started Session 10986 of user root. Jan 21 23:54:01 daytona systemd: Starting Session 10986 of user root. Jan 21 23:55:01 daytona systemd: Started Session 10987 of user root. Jan 21 23:55:01 daytona systemd: Starting Session 10987 of user root. Jan 21 23:56:01 daytona systemd: Started Session 10988 of user root. Jan 21 23:56:01 daytona systemd: Starting Session 10988 of user root. Jan 21 23:57:01 daytona systemd: Started Session 10989 of user root. Jan 21 23:57:01 daytona systemd: Starting Session 10989 of user root. Jan 21 23:58:01 daytona systemd: Started Session 10990 of user root. Jan 21 23:58:01 daytona systemd: Starting Session 10990 of user root. Jan 22 00:05:10 daytona rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="6886" x-info="http://www.rsyslog.com"] start Jan 22 00:05:10 daytona rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Jan 22 11:02:38 daytona journal: Runtime journal is using 8.0M (max allowed 4.0G, trying to leave 4.0G free of 125.8G available → current limit 4.0G). Jan 22 11:02:38 daytona kernel: Initializing cgroup subsys cpuset Jan 22 11:02:38 daytona kernel: Initializing cgroup subsys cpu Jan 22 11:02:38 daytona kernel: Initializing cgroup subsys cpuacct Jan 22 11:02:38 daytona kernel: Linux version 3.10.0-327.4.4.el7.x86_64 (builder(a)kbuilder.dev.centos.org) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Tue Jan 5 16:07:00 UTC 2016 Jan 22 11:02:38 daytona kernel: Command line: BOOT_IMAGE=/vmlinuz-3.10.0-327.4.4.el7.x86_64 root=/dev/mapper/centos-root ro rd.lvm.lv=centos/swap rd.iscsi.firmware crashkernel=auto vconsole.keymap=us vconsole.font=latarcyrheb-sun16 ip=ibft bridge=br0:ibft0 rd.lvm.lv=centos/root LANG=en_AU.UTF-8 Jan 22 11:02:38 daytona kernel: e820: BIOS-provided physical RAM map: Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000095fff] usable Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem 0x0000000000096000-0x000000000009ffff] reserved Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007df5cfff] usable Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem 0x000000007df5d000-0x000000007e0c8fff] reserved Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem 0x000000007e0c9000-0x000000007e2d7fff] ACPI NVS Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem 0x000000007e2d8000-0x000000007f352fff] reserved Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem 0x000000007f353000-0x000000007f7fffff] ACPI NVS Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved ---8<--- Jan 22 11:05:00 daytona systemd: Starting Switch Root. Jan 22 11:05:00 daytona systemd: Starting Switch Root... Jan 22 11:05:00 daytona multipathd: 3600144f00000000000005272fc8f0002: stop event checker thread (139795286001408) Jan 22 11:05:00 daytona systemd: Switching root. Jan 22 11:05:00 daytona journal: Journal stopped Jan 22 00:05:03 daytona journal: Runtime journal is using 8.0M (max allowed 4.0G, trying to leave 4.0G free of 125.8G available → current li mit 4.0G). Jan 22 00:05:03 daytona journal: Runtime journal is using 8.0M (max allowed 4.0G, trying to leave 4.0G free of 125.8G available → current li mit 4.0G). Jan 22 00:05:03 daytona systemd-journald[322]: Received SIGTERM from PID 1 (systemd). Jan 22 00:05:03 daytona kernel: type=1404 audit(1453421101.209:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 Jan 22 00:05:03 daytona kernel: type=1403 audit(1453421101.610:3): policy loaded auid=4294967295 ses=4294967295 Jan 22 00:05:03 daytona systemd[1]: Successfully loaded SELinux policy in 425.378ms. The messages 'Starting Session ...' appear every minute for several hours due to a couple of ssh sessions I left logged in. Is that cause for concern? Other than that there were a couple of messages from the amanda backup. Then the host reboots. The timestamp at boot is of note: it reverts to UTC and then back to our local timezone at the end of the boot cycle. Is that normal and can it be configured otherwise? Any help is appreciated. Kind regards, Tom -- Tom Robinson IT Manager/System Administrator MoTeC Pty Ltd 121 Merrindale Drive Croydon South 3136 Victoria Australia T: +61 3 9761 5050 F: +61 3 9761 5051 E: tom.robinson(a)motec.com.au

2 1

snat packet going out a bridge
by Steve Clark 21 Jan '16

21 Jan '16

Hi List, I am running into a problem where I have 2 interfaces bridged with and ip address assigned. I have another interface in which traffic has ingress traffic that needs to go out the bridged interface. I am trying unsuccessfully to SNAT the traffic leaving the bridge interface to its assigned address. # brctl show xbrdg0 bridge name bridge id STP enabled interfaces xbrdg0 8000.000c297aa55f no eth0 eth1 # ip a s xbrdg0 11: xbrdg0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN link/ether 00:0c:29:7a:a5:5f brd ff:ff:ff:ff:ff:ff inet 192.168.100.3/24 scope global xbrdg0 # ip a s eth5 7: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:0c:29:7a:a5:7d brd ff:ff:ff:ff:ff:ff inet 10.10.0.1/29 scope global eth5 default via 192.168.100.1 dev xbrdg0 So I want traffic coming in eth5 with 10.10.0.x addresses to be source natted to 192.168.100.3. But my iptables nat statement never gets hit. Chain POSTROUTING (policy ACCEPT 172 packets, 31384 bytes) pkts bytes target prot opt in out source destination 0 0 SNAT all -- * xbrdg0 0.0.0.0/0 0.0.0.0 to:192.168.100.3 29 1933 MASQUERADE all -- * tun+ 0.0.0.0/0 0.0.0.0/0 # ping -I 10.10.0.1 8.8.8.8 # tcpdump -nli xbrdg0 icmp or arp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on xbrdg0, link-type EN10MB (Ethernet), capture size 65535 bytes 12:52:06.914295 IP 10.10.0.1 > 8.8.8.8: ICMP echo request, id 38932, seq 1, length 64 12:52:07.914592 IP 10.10.0.1 > 8.8.8.8: ICMP echo request, id 38932, seq 2, length 64 12:52:08.914579 IP 10.10.0.1 > 8.8.8.8: ICMP echo request, id 38932, seq 3, length 64 Any ideas? Thanks, Steve -- Stephen Clark

3 4

Radeon driver with HD 2600 pro and dual head
by Tim 21 Jan '16

21 Jan '16

Hey list, I got a problem with a Gigabyte radeon HD 2600 pro card regarding my multi head setup with . This card has two DVI connectors. The second monitor has the state of being disconnected after startup (xrandr -q). When I disconnect it and reconnect sometimes the screen comes up and the second monitor shows up in display settings. It doesn't matter which port of the card I use first - the other one is disconnected. Any idea where I can take a look at? Thanks in advance Regards Tim

1 0

signing RPM packages with SHA256
by Alice Wonder 21 Jan '16

21 Jan '16

hi, I noticed that RPM packages I sign use SHA1 Signature : RSA/SHA1, Fri 08 Jan 2016 10:50:58 AM PST, Key ID ad3b591d147abf59 Signatures from CentOS 7 use SHA256 Signature : RSA/SHA256, Wed 06 Jan 2016 08:54:58 AM PST, Key ID 24c6a8a7f4a80eb5 I'm trying to find where / how to use sha256 when I sign packages but I am not having much luck. Closest I have found is this : https://fedoraproject.org/wiki/RPM_file_format_changes_to_support_SHA-256 That page appears to be from 2009 and six years is a really long time, things change a lot. Is there an up to date reference somewhere on RPM package signing that I haven't stumbled upon yet? SHA1 is broken. I shouldn't be using it. CentOS 7 is all I build packages for. Thank you.

3 9

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss