Re: [CentOS] How to get UEFI setting by shell?
http://unix.stackexchange.com/questions/157539/cant-load-zfs-kernel-module-on-fedora-with-secure-boot-required-key-not-avai So, module must be signed with trusted key, or else it just fails. Eero 22.1.2016 9.34 ap. "wk" <304702...@qq.com> kirjoitti: > 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: "我自己的邮箱";<304702...@qq.com>; > Date: Fri, Jan 22, 2016 03:07 PM > To: "eero.volotinen"; "gordon.messmer"< > gordon.mess...@gmail.com>; > Cc: "centos"; > 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";; > Date: Fri, Jan 22, 2016 02:13 PM > To: "CentOS mailing list"; > > 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@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to get UEFI setting by shell?
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: "";<304702...@qq.com>; Date: Fri, Jan 22, 2016 03:07 PM To: "eero.volotinen"; "gordon.messmer"; Cc: "centos"; 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";; Date: Fri, Jan 22, 2016 02:13 PM To: "CentOS mailing list"; 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@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
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@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to get UEFI setting by shell?
Hi, Read this page: https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface 2016-01-22 7:47 GMT+02:00 wk <304702...@qq.com>: > 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. > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] How to get UEFI setting by shell?
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. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] cups-1.3.7-32.el5_11.x86_64 may have a problem
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-x 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 --- Unfortunately, I am still contending with this problem. It appears that when the cups-1.6.3-22.el7.x86_64 sends a file to the server that has the printers defined which uses cups-1.3.7-32.el5_11.x86_64 the cups-1.6.3-22.el7.x86_64 continues to resend the file over and over again. I have the logs set to 'DEBUG', but the Logs do not tell me much other than the file is resent in the page log file. The entries below were duplicated about 250 times. lpt2 mail 3621 [21/Jan/2016:23:00:24 -0600] total 0 - localhost smile.pr.d4UBof.o - - lpt2 mail 3621 [21/Jan/2016:23:00:25 -0600] total 0 - localhost smile.pr.d4UBof.o - - lpt2 mail 3621 [21/Jan/2016:23:00:26 -0600] total 0 - localhost smile.pr.d4UBof.o - - lpt2 mail 3621 [21/Jan/2016:23:00:28 -0600] total 0 - localhost smile.pr.d4UBof.o - - lpt2 mail 3621 [21/Jan/2016:23:00:31 -0600] total 0 - localhost smile.pr.d4UBof.o - Any one have any ideas how I could debug this Greg ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 magically rebooted!
Try use memtest this problem crash memóry on segment. Good luck
Em 21/01/2016 20:28, "Tom Robinson" escreveu:
> 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
> (buil...@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
> 0x-0x00095fff] usable
> Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
> 0x00096000-0x0009] reserved
> Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
> 0x000e-0x000f] reserved
> Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
> 0x0010-0x7df5cfff] usable
> Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
> 0x7df5d000-0x7e0c8fff] reserved
> Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
> 0x7e0c9000-0x7e2d7fff] ACPI NVS
> Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
> 0x7e2d8000-0x7f352fff] reserved
> Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
> 0x7f353000-0x7f7f] ACPI NVS
> Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
> 0x8000-0x8fff] 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 da
[CentOS] CentOS 7 magically rebooted!
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
(buil...@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
0x-0x00095fff] usable
Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
0x00096000-0x0009] reserved
Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
0x000e-0x000f] reserved
Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
0x0010-0x7df5cfff] usable
Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
0x7df5d000-0x7e0c8fff] reserved
Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
0x7e0c9000-0x7e2d7fff] ACPI NVS
Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
0x7e2d8000-0x7f352fff] reserved
Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
0x7f353000-0x7f7f] ACPI NVS
Jan 22 11:02:38 daytona kernel: BIOS-e820: [mem
0x8000-0x8fff] 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: 3600144f05272fc8f0002: 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
Re: [CentOS] snat packet going out a bridge
On 20/01/2016 19:55, Steve Clark wrote: 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 First you should try to match without SNAT at all with a simple log target and see if it matches. I would start with: iptables -t nat -I POSTROUTING -s 10.0.0.1 -o xbrdg0 -j LOG --log-prefix "Should-SNAT: " --log-level 4 And then: iptables -t nat -I POSTROUTING -s 10.0.0.1 -o xbrdg0 -j SNAT --to-source 192.168.100.3 And see what happens. Also there might be something about this bridge settings and it maybe needs the "-o eth1" but it would be a bit weird. Eliezer ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Radeon driver with HD 2600 pro and dual head
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 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] signing RPM packages with SHA256
On 01/21/2016 09:23 AM, Gordon Messmer wrote: %_gpg_digest_algo sha256 Thank you! That worked beautifully. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] snat packet going out a bridge
On 01/21/2016 03:49 AM, Steve Clark wrote: Thanks, but forwarding is turned on and my FW rules are empty. Try specifying the physical device the packets are going out, rather than the bridge, in your postrouting rule. Apparently you also need an ebtables rule to prevent the return packets from being merely bridged? http://serverfault.com/questions/349688/iptables-bridge-nat-setup I'd test it, but have a look if you get the outbound traffic working and return traffic doesn't. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] signing RPM packages with SHA256
On 01/20/2016 01:37 AM, Alice Wonder wrote: 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 This thread has been a whole bunch of confusion. What you're trying to do requires that you add one line to your .rpmmacros file: %_gpg_digest_algo sha256 The _binary_filedigest_algorithm and _source_filedigest_algorithm don't affect the signature, they affect the file digest. That is, they set the checksum by which files will be verified by rpm -V. You can see the digest of each file using "rpm -qp --dump". I'm still not getting it to work - I am trying outside of mock. As far as I know, mock doesn't sign packages, so you don't need to change your mock configuration at all. Before just _signature_gpg and _gpg_name were defined Because I'm curious, I checked Only _gpg_name and _gpg_digest_algo need to be set. "%_signature gpg" is either the default, or it's unused. I'm not sure which. I am wondering if my issue is related to my gpg configuration but I don't even know where the hell the user specific configuration is kept now. I think it's normally created when you create your keys, but it doesn't seem to be needed. No idea if the gpg configuration could be the issue, and the gpg2 man page doesn't seem to indicate where the configuration file is kept now. Yes, it does. The file is gpg.conf in --homedir (which defaults to ~/.gnupg). ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] HDD badblocks
On 01/20/2016 01:43 PM, Chris Murphy wrote: On Wed, Jan 20, 2016, 7:17 AM Lamar Owen wrote: The standard Unix way of refreshing the disk contents is with badblocks' non-destructive read-write test (badblocks -n or as the -cc option to e2fsck, for ext2/3/4 filesystems). This isn't applicable to RAID, which is what this thread is about. For RAID, use scrub, that's what is for. The badblocks read/write verification would need to be done on the RAID member devices, not the aggregate md device, for member device level remap. It might need to be done with the md offline, not sure. Scrub? There is a scrub command (and package) in CentOS, but it's meant for secure data erasure, and is not a non-destructive thing. Ah, you're talking about what md will do if 'check' or 'repair' is written to the appropriate location in the sysfs for the md in question. (This info is in the md(4) man page). The badblocks method fixes nothing if the sector is persistently bad and the drive reports a read error. The badblocks method will do a one-off read/write verification on a member device; no, it won't do it automatically, true enough. It fixes nothing if the command timeout is reached before the drive either recovers or reports a read error. Very true. And even if it works, you're relying on ECC recovered data rather than reading a likely good copy from mirror or parity and writing that back to the bad block. Yes, for the member drive this is true. Since my storage here is primarily on EMC Clariion, I'm not sure what the equivalent to EMC's background verify would be for mdraid, since I've not needed that functionality from mdraid. (I really don't like the term 'software RAID' since at some level all RAID is software RAID, whether on a storage processor or in the RAID controller's firmware.). It does appear that triggering a scrub from sysfs for a particular md might be similar functionality, and would do the remap if inconsistent data is found. This is a bit different from the old Unix way, but these are newer times and such the way of doing things is different. But all of this still requires the proper configuration. Yes, this is very true. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] ifenslave vs. /etc/sysconfig/network-scripts
How does the ifenslave command relate to "normal" network slave configuration in /etc/sysconfig/network-scripts? Does config-file-based setup use ifenslave or is it more complicated than that? ThanksNick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] snat packet going out a bridge
On 01/20/2016 04:21 PM, Gordon Messmer wrote: On 01/20/2016 09:55 AM, Steve Clark wrote: Any ideas? IP forwarding needs to be enabled, and you also need rules in your FORWARD chain to allow the packets. Thanks, but forwarding is turned on and my FW rules are empty. Chain INPUT (policy ACCEPT 359K packets, 136M bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 55801 packets, 4736K bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 319K packets, 141M bytes) pkts bytes target prot opt in out source destination -- Stephen Clark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Failed to start polkit.service: Connection timed out
This is related to another earlier post regarding "realm discover" I want to set the timezone to Melbourne/Australia which failed with: [root@sssd-testing ~]# timedatectl set-timezone Australia/Melbourne Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to set time zone: Connection timed out I found the following which suggests the error is caused by the polkit service failing to start: http://unix.stackexchange.com/questions/249575/systemctl-keeps-timing-out-on-service-restart When I reinstall and try to start the polkit service in accordance with the post above I receive the following: [root@sssd-testing ~]# systemctl start polkit Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to start polkit.service: Connection timed out When I call the service directly in accordance with the post above I receive: [root@sssd-testing ~]# /usr/lib/polkit-1/polkitd Successfully changed to user polkitd Error getting system bus: Could not connect: Permission denied ** (polkitd:922): WARNING **: Error getting system bus: Could not connect: Permission denied 10:44:10.564: Loading rules from directory /etc/polkit-1/rules.d 10:44:10.564: Loading rules from directory /usr/share/polkit-1/rules.d 10:44:10.564: Finished loading, compiling and executing 2 rules Entering main event loop 10:44:10.564: Lost the name org.freedesktop.PolicyKit1 - exiting Shutting down Exiting with code 0 The post below identifies a similar issue with the polkit service not starting however I have confirmed dbus is running and the polkitd user does exist. https://bbs.archlinux.org/viewtopic.php?id=161291 [root@sssd-testing ~]# ps ax | grep dbus 221 ?Ss 0:00 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation 929 pts/1S+ 0:00 grep --color=auto dbus [root@sssd-testing ~]# getent passwd polkitd polkitd:x:997:995:User for polkitd:/:/sbin/nologin ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
