Discuss

discuss@lists.centos.org

34753 discussions

31 Jan '19

Hello, I run CentOS release 6.10 (Final) on a Dell Inspiron M6700. 2.6.32-754.el6.x86_64 boots, and is whaat I am running now none of these, updated ones, won't boot: 2.6.32-754.3.5.el6.x86_64 2.6.32-754.6.3.el6.x86_64 2.6.32-754.9.1.el6.x86_64 2.6.32-754.10.1.el6.x86_64 They all show the same 'symptom', grub says it is booting that kernel, screen blanks, solid corned in the left-top corner... and that's whee it stays. I know this is vague, but any ideas? thanks, Ron

3 4

SELinux policy vs. static web content
by Nicolas Kovacs 31 Jan '19

31 Jan '19

Hi, Some time ago I wrote an introductory article about SELinux on my blog. I'm currently updating it for my new blog, and I found a curious change in SELinux policy. Here goes. For demonstration purposes, I'm using some static webpages, more exactly the default pages found in /usr/share/httpd/noindex, which I simply copied over to /var/www/html. As a first practical example, I'm copying this stuff over to /tmp/backup and then move it back again. A vaguely similar example has been given by Thomas Cameron in his presentation "SELinux for mere mortals", and I'm reproducing it here with some minor modifications. $ cd /var/www/html/ $ mkdir /tmp/backup $ cp -R * /tmp/backup/ $ rm -rf * $ mv /tmp/backup/* . $ find . -type d -exec chmod 0755 {} \; $ find . -type f -exec chmod 0644 {} \; When I wrote the article back in november 2017, this resulted in a classic "Forbidden" error, since the SELinux context of these files is not httpd_sys_content_t as it should be, but user_tmp_t. But when I try to repeat the experiment now, Apache shows no error. Which seems strange. Any idea what's going on ? Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 2

Re: [CentOS] EPEL repo problem
by Stephen John Smoogen 30 Jan '19

30 Jan '19

On Wed, 30 Jan 2019 at 09:21, Kenneth Porter <shiva(a)sewingwitch.com> wrote: > --On Wednesday, January 30, 2019 6:57 AM -0500 Stephen John Smoogen > <smooge(a)gmail.com> wrote: > > > Can you run the code from: https://github.com/puiterwijk/check_metalink > to > > see if we can pin down the proxy which is the problem (there are 14 and > > our checks are showing they are ok so I need to pin this down somewhere). > > Since I'm seeing the same errors intermittently, I tried to run the > script. > Recall that CentOS still ships with Python 2. First I had to install > rh-python36 from SCL. Then I had to change the script's shebang to > "#!/usr/bin/env python". Now it complains that there's no requests module. > I don't know how to resolve Python3 dependencies for a python installed > from SCL. How far down the rabbit hole will I need to go to get the script > working? ;) > > Yeah.. sorry. I didn't see I had made this one little change to my version: diff --git a/check_metalink b/check_metalink index f2beeb5..380b16d 100755 --- a/check_metalink +++ b/check_metalink @@ -1,4 +1,4 @@ -#!/bin/python3 +#!/bin/python I will see if I can make this work without that pathc. > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > -- Stephen J Smoogen.

1 0

pip on C7
by Jerry Geis 30 Jan '19

30 Jan '19

I am trying to install the python-onvif package on C7. I did: pip install onvif Requirement already satisfied (use --upgrade to upgrade): onvif in /usr/lib/python2.7/site-packages Requirement already satisfied (use --upgrade to upgrade): suds>=0.4 in /usr/lib/python2.7/site-packages (from onvif) Requirement already satisfied (use --upgrade to upgrade): suds-passworddigest in /usr/lib/python2.7/site-packages (from onvif) You are using pip version 8.1.2, however version 19.0.1 is available. You should consider upgrading via the 'pip install --upgrade pip' command. How do I get it to go ahead and install ? Requirements are met. I don't desire to upgrade. Thanks, Jerry

2 3

Signature Pad (Evolis Signotec Sig100)
by Gregory P. Ennis 30 Jan '19

30 Jan '19

Everyone, Please forgive me for being off topic and really off list !!! I am trying to get a Sig100 signature pad to work with Centos 7.6 machine and am not getting much support from the manufacturer. The product is sold as linux compatible, but so far it is not. I have been able to download their software on a microsoft system and see that the unit does work on microsoft. My question to everyone on the list is have any of you had any brand of signature pad work with Centos 7.6? If so I would surely appreciate knowing the brand and how you did it. I have been able to get a HUION H610PRO wacom to easily work with Centos 7.6, but the use of this for a production application for signatures will not really work easily for a user. Any ideas? Thanks ahead for your thoughts!!!! Greg Ennis

3 6

Several tests failing
by Roee Agami 29 Jan '19

29 Jan '19

Hi, I’m attempting to build a 7.63.0 RPM for centos from a spec file I created. I am getting the following tests failures: “These test cases failed: 206 1049 1060 1061 1232 1241 1421” Here is an example of an output for test 206, any help to get insights into it would be greatly appreciated: test 0206...[HTTP proxy CONNECT auth Digest] ../libtool --mode=execute /usr/bin/valgrind --tool=memcheck --quiet --leak-check=yes --suppressions=./valgrind.supp --num-callers=16 --log-file=log/valgrind206 ../src/c url --output log/curl206.out --include --trace-ascii log/trace206 --trace-time http://test.remote.haxx.se.206:6490/path/2060002 --proxy http://127.0.0.1:6490 --proxy-u ser silly:person --proxy-digest --proxytunnel >log/stdout206 2>log/stderr206 2705 CMD (0): ../libtool --mode=execute /usr/bin/valgrind --tool=memcheck --quiet --leak-check=yes --suppressions=./valgrind.supp --num-callers=16 --log-file=log/valgrind206 ../src/curl --output log/curl206.out --include --trace-ascii log/trace206 --trace-time http://test.remote.haxx.se.206:6490/path/2060002 --proxy http://127.0.0.1:6490 --proxy-user silly:person --proxy-digest --proxytunnel >log/stdout206 2>log/stderr206 206: protocol FAILED: --- log/check-expected 2019-01-28 20:44:27.903988339 +0000 +++ log/check-generated 2019-01-28 20:44:27.903988339 +0000 @@ -4,7 +4,7 @@ [CR][LF] CONNECT test.remote.haxx.se.206:6490 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] -Proxy-Authorization: Digest username="silly", realm="weirdorealm", nonce="12345", uri="test.remote.haxx.se.206:6490", response="003e36decb4dbf6366b3ecb9b87c24ec"[CR][L F] +Proxy-Authorization: Digest username="silly", realm="weirdorealm", nonce="12345", uri="test.remote.haxx.se.206:6490", response="e6e133b332307d0e988962837d9e27a1"[CR][L F] Proxy-Connection: Keep-Alive[CR][LF] [CR][LF] GET /path/2060002 HTTP/1.1[CR][LF] == Contents of files in the log/ dir after test 206 === Start of file check-expected CONNECT test.remote.haxx.se.206:6490 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] Proxy-Connection: Keep-Alive[CR][LF] [CR][LF] CONNECT test.remote.haxx.se.206:6490 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] Proxy-Authorization: Digest username="silly", realm="weirdorealm", nonce="12345", uri="test.remote.haxx.se.206:6490", response="003e36decb4dbf6366b3ecb9b87c24ec"[CR][L F] Proxy-Connection: Keep-Alive[CR][LF] [CR][LF] GET /path/2060002 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] Accept: */*[CR][LF] [CR][LF] [DISCONNECT][LF] === End of file check-expected === Start of file check-generated CONNECT test.remote.haxx.se.206:6490 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] Proxy-Connection: Keep-Alive[CR][LF] [CR][LF] CONNECT test.remote.haxx.se.206:6490 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] Proxy-Authorization: Digest username="silly", realm="weirdorealm", nonce="12345", uri="test.remote.haxx.se.206:6490", response="e6e133b332307d0e988962837d9e27a1"[CR][L F] Proxy-Connection: Keep-Alive[CR][LF] [CR][LF] GET /path/2060002 HTTP/1.1[CR][LF] Host: test.remote.haxx.se.206:6490[CR][LF] Accept: */*[CR][LF] [CR][LF] [DISCONNECT][LF] === End of file check-generated === Start of file curl206.out HTTP/1.1 407 Authorization Required to proxy me my dear Proxy-Authenticate: Digest realm="weirdorealm", nonce="12345" Content-Length: 33 HTTP/1.1 200 OK swsbounce Server: no HTTP/1.1 200 OK Date: Thu, 09 Nov 2010 14:49:00 GMT Content-Length: 7 Connection: close Content-Type: text/html Funny-head: yesyes daniel === End of file curl206.out

1 0

C 7 and gssproxy
by mark 28 Jan '19

28 Jan '19

Ok, folks, I brought this up some time ago, and got no replies. We have a good number of systems - > 100 - and we use sssd. On the C 7 boxen, which is most of them, gssproxy *frequently* (like once a day or so) dies with a SEGV. It restarts fine. Dies again eventually. ARE other people seeing this? If so, I guess we get to file a bug report with upstream. Speaking as an old C programmer, dying with a SEGV? Really? In production? mark

3 2

Re: [CentOS] Centos 7 and backup solution
by Michael Schumacher 28 Jan '19

28 Jan '19

Sunday, January 27, 2019, 5:10:53 PM, you wrote: KP> rsync to a remote site and then BackupPC. (Use the BackupPC version 4 in KP> Software Collections.) I am using BackupPC too, but you don't need to rsync the data first. BackupPC can rsync data natively. I am using independent backup servers that are not accessible from the backup sources. Don't forget safety and integrity of your backed up data these days! Btw., it is not only a nice backup software, it is also very nice in recovering data through its web interface. best regards --- Michael Schumacher

1 0

How to get unrelease kernel, e.g. 3.10.0-341.el7
by wuzhouhui 28 Jan '19

28 Jan '19

Hi, I cloned https://git.centos.org/r/rpms/kernel.git and found that it only contains kernel version that CentOS released. So how do I get the kernel version that CentOS not release officialy, e.g. 3.10.0-341.el7 and 3.10.0-383.el7 (some kernel version I found in kernel.spec's changelog)? Thanks.

2 1

PXEBoot/Diskless client NFS issue
by John Cole 27 Jan '19

27 Jan '19

Hey CentOS list! I've got an oddity with a diskless client setup that I suspect is the result of the initrd.img I'm using, or some parameter I'm unaware -- or I need to build my own initrd image (and could use some assistance on what has to be done in that department) Testbed is defined as: VM A: ip: 192.168.250.10 with dhcp server, tftp server, nfs server VM B: pxeboot VM, with no local disk, bios set to pxe, same internal network as VM A Early on in the boot cycle, it grabs a DHCP address of 192.168.250.100, with correct mask, gw etc from VM A When I start the testbed setup: On the master VM I see log messages with the NIC of the client getting an address, and successfully loading pxelinux.0, pxelinux.cfg/default, vmlinuz and initrd.img. The PXE client on VM B boots up, downloads all the above images, unpacks and executes the inird image. I see drivers load and normal device registration for the nics just fine. After the PXE client VM shows the nic has its link up, this is where things go wrong... * The PXE client (that properly got an address in the 250 space to get its images) sends out a DHCP discover message as would be expected. * VM A responds with an offer of the same 192.168.250.100 address that was used to load * The PXE client comes back with a DHCPREQUEST for 192.168.85.128 * The DHCP server sends a DHCPNAK to the client, and offers the 250 address again. * The client never responds and the image seems to ignore the NAK/OFFER * Eventually the diskless client comes back with a dracut-initqueue message that (as a lease was not ACKed correctly reports) mount.nfs: Network is unreachable IF however, I run the identical configuration I mention above changing the addresses from 192.168.250.x to the 192.168.85.x space to match the initrd image request, everything works fine and the diskless client boots up normally and I get a command prompt. This would seem to indicate that I've got an otherwise working setup. The images I've always used for diskless boot are the ones prebuilt and posted on the centos mirrors site -- http://mirror.centos.org/centos/7/os/x86_64/images/pxeboot/ I've confirmed they and the pxeboot.0 file I'm using are the most recent being distributed. I've also unsuccessfully tried to use the ip parameters on the pxelinux.cfg/default line. As this seems to me as the most relevant config to post, here's what I've got there: label kiosk kernel kiosk/vmlinuz append initrd=kiosk/initrd.img ip=dhcp root=nfs:192.168.250.10:/var/lib/tftpboot/kiosk/root rw selinux=0 If other configs are requested, I'll gladly provide them, but again all works fine if I do this in the 192.168.85.x IP range. Once I've got this particular problem solved, I'm looking to boot up and bond BOTH NICs together, something I know should be possible, but I've not done myself yet. I believe that'd be handled in the append line as well. Any assistance in what I need to do to build a proper initrd image that doesn't suffer the problem of accepting a DHCP offered address, OR pointers to a config parameter I'm missing would be most appreciated. And a breadcrumb to help me with the dual nic once I'm out of the woods would be the "icing on the cake" but that's obviously a secondary concern right now! Thanks jc

2 2

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