Re: [CentOS] systemd-coredump service
> I am unable to locate systemd-coredump service on CentOS 7.5. It is not > listed under "systemctl -a" and also I'm unable to locate the associated > unit file (folder /usr/lib/systemd/system/ ). Am I missing any package > which installs this service? I don't really understand what you are looking for but don't you have /usr/lib/systemd/systemd-coredump and /usr/bin/systemd-coredumpctl on your system? Regards, Simon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] gcc 8/9 on CentOS 7
On 12/27/19 11:43 PM, sthustfo wrote: > I am looking to make use of gcc 8/9 on CentOS 7, which is currently with > gcc 4.8.5. How do I go about doing this? SCL repository provides the same > as part of devtoolset8, but devtoolset8 libstdc++-devel i686 package is > missing, without which I can not build 32 bit applications. > > Are there any repository sources from where I can get this? Otherwise, I am > open to building the packages from sources. Please let me know how can one > go about this. You will need to use the devtoolset builds to do this: There is a gcc 8 .. but not gcc 9 https://www.softwarecollections.org/en/scls/rhscl/devtoolset-8/ signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] systemd-coredump service
I am unable to locate systemd-coredump service on CentOS 7.5. It is not listed under "systemctl -a" and also I'm unable to locate the associated unit file (folder /usr/lib/systemd/system/ ). Am I missing any package which installs this service? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] tomcat package and repo for centos8
Thank you, I will try that. Am 19.12.19 um 17:40 schrieb Richard G: On Fri, Dec 13, 2019 at 3:04 PM Richard G wrote: On Fri, Dec 13, 2019 at 2:34 PM Rainer Traut wrote: Is there any other third party repository which builds tomcat for centos/rhel 8? I intend to build tomcat 8 and 9 for CentOS 8 in my harbottle-main repo ( https://harbottle.gitlab.io/harbottle-main ), just as I did for CentOS 7, but I'm having trouble with the log4j dependency in CentOS 8 (see my recent emails to this list). OK, I've built Tomcat 8 and 9 for CentOS 8. Docs here: https://gitlab.com/harbottle/harbottle-main/blob/master/docs/tomcat8.md https://gitlab.com/harbottle/harbottle-main/blob/master/docs/tomcat9.md Please test and let me know if they are OK. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Limiting what devices can pair over Bluetooth?
I've managed to get a Wacom Intuos Pro 2 (PTH-660) tablet working over Bluetooth to a CentOS 7 install. Well, I didn't actually have to do much to get it working ... However, we don't normally enable Bluetooth for security reasons, so I need to be able to configure things so Bluetooth can _only_ be used to pair with Wacom tablets As I never used Bluetooth in anger before, I'm struggling to find out where to start looking - does anyone know how to do this or any pointers on where I should start? Thanks James Pearson ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Nasty Fail2Ban update for Centos 7
On Tue, 2019-12-31 at 10:19 +0100, Nicolas Kovacs wrote:
> Le 31/12/2019 à 03:14, Allan a écrit :
> > Then gotta dig into Koji, to find the old version, download it,
> > and downgrade to that - and pew, everything is back to normal.
> >
> > The old one seems to be version 0.9.7 and the new one is 0.10.4
> >
> > I haven't had time to look into Fail2Bans info about these 2
> > version,
> > but since there is a major version change - is it really possible
> > to
> > just upgrade these ?
> >
> > Sure, I would love to have a working 0.10.4 for my Centos 7 - but
> > it
> > shouldn't destroy my existing system - or it should at least warn
> > me
> > about that - or what to fix.
>
> I have automatic updates with yum-cron on all my production servers.
> Fail2ban
> has been recently upgraded to 0.10.4 and still works perfectly.
We also had it updated and fail2ban worked perfectly except it did not
ban anymore on the sshd jail. This was caused by the
/etc/fail2ban/filter.d/sshd.conf file which should have been replaced
with a new one from the rpm (there was a sshd.conf.rpmnew file).
Below the error we found in /var/log/fail2ban.log :
2019-12-09 10:02:15,294 fail2ban.filtersystemd [13628]: INFO[sshd]
Added journal match for: '_SYSTEMD_UNIT=sshd.service + _COMM=sshd'
2019-12-09 10:02:15,295 fail2ban.filter [13628]: ERROR No
failure-id group in 'normal'
2019-12-09 10:02:15,295 fail2ban.transmitter[13628]: WARNING
Command ['set', 'sshd', 'addfailregex', 'normal'] has failed. Received
RegexException("No failure-id group in 'normal'",)
2019-12-09 10:02:15,295 fail2ban[13628]: ERROR NOK:
("No failure-id group in 'normal'",)
Regards,
Michel
--
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is
uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht
ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct
te informeren door het bericht te retourneren. Het Universitair Medisch
Centrum Utrecht is een publiekrechtelijke rechtspersoon in de zin van de W.H.W.
(Wet Hoger Onderwijs en Wetenschappelijk Onderzoek) en staat geregistreerd bij
de Kamer van Koophandel voor Midden-Nederland onder nr. 30244197.
Denk s.v.p aan het milieu voor u deze e-mail afdrukt.
--
This message may contain confidential information and is intended exclusively
for the addressee. If you receive this message unintentionally, please do not
use the contents but notify the sender immediately by return e-mail. University
Medical Center Utrecht is a legal person by public law and is registered at
the Chamber of Commerce for Midden-Nederland under no. 30244197.
Please consider the environment before printing this e-mail.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 as a Fibre Channel SAN Target
It took me some time to come back full circle to this. I've worked quite a bit
on this with little success so far. It seems like it's been done but on some of
the forums and Github, there are no responses yet. This is essentially a cross
post from a seemingly dead list. Hopefully someone here will have some
suggestions.
I've googled this particular issue and not really finding any good results on
how to resolve it.
I installed targetcli via yum on CentOS 7 and this is the version in the repo:
# targetcli
targetcli shell version 2.1.fb49
Copyright 2011-2013 by Datera, Inc and others.
For help on commands, type 'help'.
I downloaded the .zip of the targetcli-fb version and tried it too from the
scripts folder and same results.
Python:
# python --version
Python 2.7.5
Libs:
Installed Packages
python-configshell.noarch 1:1.1.fb25-1.el7 @base
python-rtslib.noarch 2.1.fb69-3.el7 @base
python-rtslib-doc.noarch 2.1.fb69-3.el7 @base
The error comes up when using create.
/> /qla2xxx create naa.xxx
Could not create Target in configFS
Below is the info on my FC
/> qla2xxx/ info
Fabric module name: qla2xxx
ConfigFS path: /sys/kernel/config/target/qla2xxx
Allowed WWN types: naa
Allowed WWNs list: naa.xxx, naa.xxx,
naa.xxx, naa.xxx, naa.xxx,
naa.xxx, naa.xxx, naa.xxx
Fabric module features: acls
Corresponding kernel module: tcm_qla2xxx
I have attached the log but don't see anything that really stands out. log.txt
I checked per the link
http://www.linux-iscsi.org/wiki/Fibre_Channel#Enable_target_mode to ensure that
I have initiator mode disabled
# cat /sys/module/qla2xxx/parameters/qlini_mode
disabled
The kernel modules are loaded.
# lsmod | grep qla2xxx
tcm_qla2xxx 32768 1
target_core_mod 335872 4 tcm_qla2xxx,iscsi_target_mod
qla2xxx 634880 1 tcm_qla2xxx
scsi_transport_fc 65536 3 bfa,qla2xxx,tcm_qla2xxx
configfs is mounted:
# cat /proc/mounts | grep configfs
configfs /sys/kernel/config configfs rw,relatime 0 0
In the kernel config:
CONFIG_CONFIGFS_FS=y
Kernel:
4.4.207-1.el7.elrepo.x86_64
Should I be able to create a directory in /sys/kernel/config/target/qla2?
# mkdir naa.10008c7cffc7ef01
mkdir: cannot create directory ‘naa.xxx’: Invalid argument
I did notice that when I rebooted, there was no qla2xxx folder in
/sys/kernel/config/target/ but after trying to use targetcli, it did make one
so I'm not sure what else would cause it to fail.
Suggestions?
Thank you,
Steffan Cline
stef...@hldns.com
602-793-0014
On 1/11/19, 12:01 AM, "Steffan A. Cline" wrote:
For quite some time I’ve been using FreeNAS to provide services as a NAS
over ethernet and SAN over Fibre Channel to CentOS 7 servers each using their
own export, not sharing the same one.
It’s time for me to replace my hardware and I have a new R720XD that I’d
like to use in the same capacity but configure CentOS 7 as a Fibre Channel
target rather than use FreeNAS any further.
I’m doing virtualization and this will allow me to have failover from one
node to the other since they’ll all be sharing the same export rather than me
simply backing up to the FreeNAS server the way I am now.
Does anyone know of any really good current articles that explain how to
set up CentOS 7 as the target in such a configuration and also setting up CLVMd
so they can all share an export over Fibre Channel from CentOS 7?
Steffan A. Cline
stef...@hldns.com
602-793-0014
[VERBOSE] 2019-12-27 23:55:29 Running command line 'qla2xxx/ info'.
[DEBUG] 2019-12-27 23:55:29
/usr/lib/python2.7/site-packages/configshell_fb/shell.py:757 _parse_cmdline()
Parsing commandline.
[DEBUG] 2019-12-27 23:55:29
/usr/lib/python2.7/site-packages/configshell_fb/shell.py:775 _parse_cmdline()
Parse gave path='qla2xxx/' command='info' pparams=[] kparams={}
[DEBUG] 2019-12-27 23:55:29
/usr/lib/python2.7/site-packages/configshell_fb/node.py:1846 get_node() Looking
for path 'qla2xxx'
[DEBUG] 2019-12-27 23:55:29
/usr/lib/python2.7/site-packages/configshell_fb/node.py:1398 execute_command()
Executing command info with pparams [] and kparams {}.
[DEBUG] 2019-12-27 23:55:29
/usr/lib/python2.7/site-packages/configshell_fb/node.py:1445 assert_params()
Min params: 0
[DEBUG] 2019-12-27 23:55:29
/usr/lib/python2.7/site-packages/configshell_fb/node.py:1446 assert_params()
Max params: 0
[DEBUG] 2019-12-27 23:55:29
/usr/lib/python2.7/site-packages/configshell_fb/node.py:1447 assert_params()
Required params:
[DEBUG] 2019-12-27 23:55:29
/usr/lib/python2.7/site-packages/configshell_fb/node.py:1448 assert_params()
Optional params:
[DEBUG] 2019-12-27 23:55:29
/usr/lib/python2.7/site-packages/configshell_fb/node.py:1449 assert_params()
Got 0 standard params.
[DEBUG] 2019-12-27 23:55:29
/usr/lib/python2.7/site-packages/configshell_fb/node.py:1450 assert_params()
Got 0
