Discuss November 2017

discuss@lists.centos.org

105 participants
101 discussions

How to encourage maintainers to update their software
by H 08 Nov '17

08 Nov '17

How do I best encourage maintainers to update the software they are responsible for in various repositories? Akema Yagi made sure kmod-jfs for CentOS 7 was updated amazingly fast which is greatly appreciated. On the other hand, I have requested updates of some other software packages and have heard absolutely nothing in months...

9 19

lets talk abaut gstreamer 1.10.5, gstreamer-libav, ffmpeg, bluray and vlc
by Andreas Benzler 07 Nov '17

07 Nov '17

Hello guys, my playground this days with gstreamer resources can be found at: http://centos.cms4all.org/repo/7/gstreamer/ The best thing for centos I think to compile the given one by gstream libav: Has ffmpeg 3.2.5 not ffmpeg 2.8.13 what is the background for vlc. In principal it's possible to build ffmpeg 3.4. http://centos.cms4all.org/repo/7/gstreamer-ffmpeg3/ vlc 2.26 is only compatible with ffmpeg 2.8.xx release. Hopefully i get response from the gstreamer guys to get bluray running with gstream-libav. In the past it was possible with gstreamer 1.4.5. As a side node as always: Got problems with dvd on usb blurayplayer, but this is another storry and can not be fixed from the kernel side. Buffer problems. Blurays & DVD (builtin drive) are playing with vlc. Totem can play anything, exclude bluray. http://centos.cms4all.org/repo/7/media/ Another little problem is vlc 3.0 can only compiled with gcc 4.9 and upper. Has to be rearrange for static gcclib, no real dependency by installation. http://vault.centos.org/7.4.1708/sclo/Source/rh/devtoolset-3/ Not yet on my todo list. Why 4.9? No g++ binary break. Bluray taken from my libbluray1 rpm otherwise i brick gvfs (bluray 0.2.3). Recompiled test wise. Think about to write a mail to redhat. Yes I replace the complete gstreamer 1.10.4 with 1.10.5, because of minor update. The original package was gstreamer-libav-0.6. It was complete inpossible to play anything good in totem. What do you think ? Sincerely Andy PS: I'm tired. Please forget my bad english this days...

1 0

yum-cron
by m.roth＠5-cent.us 07 Nov '17

07 Nov '17

Hi, folks, Has anyone else seen the issue of having an excludes= in /etc/yum.conf, but yum-cron appears to be ignoring it? This may have been the case earlier this year, where it seemed to partly install a new kernel, then not done the post-install. I *think* that's what I'm seeing on a box with twin Tesla cards, with yum.conf: exclude=kernel* xorg* cuda* kmod* and yet cron.daily reports: /etc/cron.daily/0yum-daily.cron: Failed to check for updates with the following error message: Failed to build transaction: kmod-nvidia-384.90-1.el7_4.elrepo.x86_64 requires nvidia-x11-drv = 384.90 nvidia-x11-drv-384.98-1.el7.elrepo.x86_64 requires nvidia-kmod = 384.98 mark

1 0

how do I use CDC usb ports?
by Michael Hennebry 07 Nov '17

07 Nov '17

I want to use a USB CDC port. I was under the impression that they were not all that hard to use. 'Tain't going well for me. lsusb | grep ega tells me Bus 007 Device 007: ID 2341:0042 Arduino SA Mega 2560 R3 (CDC ACM) As root, cat-ing /dev/bus/usb/007/007 gives me garbage. As anyone else, I get a permission denied error. Usually, though not lately, a /dev/ttyS? shows up at about the same time as the .../007/* device. How, without continuously running as root, do I get access to CDC usb devices? I've tried making myself a member of dialout, but it doesn't seem to take. I've tried both lgroupmod -M hennebry dialout oIt doesn't seem to take.and usermod -a -G dialout hennebry . How do I tell which one I want? I'm guessing I can't use /dev/bus/... . How do I tell which /dev/ttyS? I want? -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

1 0

Comparing directories recursively
by H 07 Nov '17

07 Nov '17

What is the best tool to compare file hashes in two different drives/directories such as after copying a large number of files from one drive to another? I used cp -au to copy directories, not rsync, since it is between local disks. I found a mention of hashdeep on the 'net which means first running it against the first directory generating a file with checksums and then running it a second time against the second directory using this checksum file. Hashdeep, however, is not in the CentOS repository and, according to the 'net, is possibly no longer maintained.\ I also found md5deep which seems similar. Are there other tools for this automatic compare where I am really looking for a list of files that exist in only one place or where checksums do not match?

6 14

Re: [CentOS] C7.4 and sshd restart problem [SOLVED]
by Alessandro Baggi 07 Nov '17

07 Nov '17

Hi list, I solved the problem. Anyone had answered but I report the solution for similar problem. The problem was caused by an sshd.service under /etc/systemd/system/. This file was placed because upgrading from 7.2 to 7.3 I got problem with ssh startup and someone suggested to add pidfile directive in sshd.service to solve the problem. Updating from 7.3 to 7.4 I think that 2 files for sshd caused some conflict that kill my sshd. Removing the first file problem is solved. Thanks to all. Il 06 Nov 2017 9:03 PM, "Alessandro Baggi" <alessandro.baggi(a)gmail.com> ha scritto: Hi list, Some days ago I updated my centos 7.3 to 7.4 on a dell server. After this update I noticed a strange behaviour by sshd. I noticed this problem because trying to connect to ssh I got connection refused or high latency between connecting and password req. So I noticed that sshd will be restarted every ~2 min. >From log I get this: Received signal 15; terminating Failed to start OpenSSH server daemon Unit sshd.service entered failed state sshd.service failed sshd.service holdoff time over, scheduling restart ....and sshd restart. This happens so fast that if I run systemctl status I can't get the failed status. Logs does not help also in debug facility. There is not any cronjob that kill sshd. I tried also to change some basic sshd_config directives and when running systemctl restart sshd it hangs until I type crtl-C and from log I see that sshd is restarted. In sshd_config there aren't errors and the config is the same since 2016. On another machine in the same network I have the same configuration and same software installed (replica with native c7.4) but the problem does not occurs. I checked also md5 of relative server /usr/sbin/sshd and they match. Selinux is disabled and using non standard port. I notices also that if I'm connected to sshd and sshd crashes/restart my current session is not killed. I have not stopped and restarted sshd because this is a dedicated server and until my provider does not attach a kvm switch I can't do other tests. I will try also to stop sshd and run from console using debug hoping that helps. What I can check to know the reason of this behaviour? This is sshd problem or other? Thanks in advance.

1 0

JOB | Permanent Sysadmin (Amsterdam OR remote)
by James Tobin 07 Nov '17

07 Nov '17

Hello, I'm working with an employer that is looking to hire a permanent sysadmin to help maintain their Hadoop and Kafka clusters at their Amsterdam, Netherlands office OR remote. Consequently I had hoped that some members of this mailing list may like to discuss further off-list using "JamesBTobin (at) Gmail (dot) Com". Kind regards, James

1 0

Nvidia error
by Jerry Geis 06 Nov '17

06 Nov '17

I am getting this error on CentOS 7.4 kernel: NVRM: API mismatch: the client has the version 384.98, but#012NVRM: this kernel module has the version 384.90. Please#012NVRM: make sure that this kernel module and all NVIDIA driver#012NVRM: components have the same version nvidia-detect -v Probing for supported NVIDIA devices... [10de:1288] NVIDIA Corporation GK208 [GeForce GT 720] This device requires the current 384.98 NVIDIA driver kmod-nvidia I have installed elrepo: yum-plugin-nvidia-1.0.2-1.el7.elrepo.noarch elrepo-release-7.0-3.el7.elrepo.noarch kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 nvidia-x11-drv-384.98-1.el7.elrepo.x86_64 nvidia-detect-384.98-1.el7.elrepo.x86_64 How do I resolve that ? I have uninstalled the above and reinstalled. Same issue. Thanks, Jerry

5 8

how to install pyserial on centos 6?
by Michael Hennebry 06 Nov '17

06 Nov '17

I tried yum import pyserial yum provides '*serial*' gave me distribution-gpg-keys-copr-1.15-1.el6.noarch : GPG keys for Copr projects Repo : epel Matched from: Filename : /usr/share/distribution-gpg-keys/copr/copr-ifas-pyserial.gpg python2-ivi-0.14.9-3.el6.noarch : %{sum} Repo : epel Matched from: Filename : /usr/lib/python2.6/site-packages/ivi/interface/pyserial.pyo Filename : /usr/lib/python2.6/site-packages/ivi/interface/pyserial.pyc Filename : /usr/lib/python2.6/site-packages/ivi/interface/pyserial.py yum install python2-ivi-0.14.9-3.el6.noarch "worked", but didn't help: [hennebry@localhost ~]$ python Python 2.6.6 (r266:84292, Aug 18 2016, 15:13:37) [GCC 4.4.7 20120313 (Red Hat 4.4.7-17)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import pyserial Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named pyserial >>> import serial Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named serial >>> What happened? How do I get pyerial? -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

2 1

C7.4 and sshd restart problem
by Alessandro Baggi 06 Nov '17

06 Nov '17

Hi list, Some days ago I updated my centos 7.3 to 7.4 on a dell server. After this update I noticed a strange behaviour by sshd. I noticed this problem because trying to connect to ssh I got connection refused or high latency between connecting and password req. So I noticed that sshd will be restarted every ~2 min. >From log I get this: Received signal 15; terminating Failed to start OpenSSH server daemon Unit sshd.service entered failed state sshd.service failed sshd.service holdoff time over, scheduling restart ....and sshd restart. This happens so fast that if I run systemctl status I can't get the failed status. Logs does not help also in debug facility. There is not any cronjob that kill sshd. I tried also to change some basic sshd_config directives and when running systemctl restart sshd it hangs until I type crtl-C and from log I see that sshd is restarted. In sshd_config there aren't errors and the config is the same since 2016. On another machine in the same network I have the same configuration and same software installed (replica with native c7.4) but the problem does not occurs. I checked also md5 of relative server /usr/sbin/sshd and they match. Selinux is disabled and using non standard port. I notices also that if I'm connected to sshd and sshd crashes/restart my current session is not killed. I have not stopped and restarted sshd because this is a dedicated server and until my provider does not attach a kvm switch I can't do other tests. I will try also to stop sshd and run from console using debug hoping that helps. What I can check to know the reason of this behaviour? This is sshd problem or other? Thanks in advance.

1 0

← Newer
1
...
5
6
7
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss November 2017