Discuss

discuss@lists.centos.org

5 participants
34752 discussions

Firewalld and iptables
by Jon LaBadie 15 Dec '18

15 Dec '18

After a recent large update, firewalld's status contains many lines of the form: WARNING: COMMAND_FAILED: '/usr/sbin/iptables... Checking iptables.service status shows it to be masked. I realize that firewalld uses iptables, but should it be enabled and started as a service? Jon -- Jon H. LaBadie jcu(a)labadie.us 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)

4 9

SFTP - Private/Public Authentication Keysets Beyond The First Set
by Gary Braatz 15 Dec '18

15 Dec '18

I'm new to SFTP and using this mailing list was able to successfully create my first Private/Public keyset for a vendor hosting the SFTP server (I'm the client). I created the keyset by typing this: # ssh-keygen -t rsa When asked for the password/passphrase I hit <Enter> and afterwards "id_rsa" and "id_rsa.pub" were created in "/root/.ssh/". I provided "id_rsa.pub" to the vendor and when told they were ready I initiated an SFTP transfer. During the first connection I was asked for the vendor-provided password and after entering it was successfully connected to the vendor's sftp server. During successive connections I was not again asked for the password. This allowed me to create fully automated batch file transfers.my objective. Setting up my second vendor is not going as smoothly. I did exactly the same thing for my second vendor with the exception of typing "rsa_vendor2" during keyset generation (I assumed I had to use a different name for the new keyset). # ssh-keygen -t rsa_vendor2 Files "id_rsa_vendor2" and "id_rsa_vendor2.pub" were created in "/root/.ssh/" and I gave "id_rsa_vendor2.pub" to the second vendor. I initiated the first connection with the second vendor and was asked for the vendor-provided password which I entered and a successful connection was made. The problem is unlike with the first vendor I am asked for the password every time I connect to the second vendor's server. Because I am being asked for the password I am unable to create fully automated batch file transfers. The second vendor is telling me they added the public key to their server as required. Did I miss a step or do something wrong on my end? Was I correct using a different name for the new keyset or would the new keyset information have been appended to the information already in id_rsa and id_rsa.pub for the first vendor? Any help you can provide will be greatly appreciated.

4 8

CentOS7 kickstart question
by isdtor 14 Dec '18

14 Dec '18

Is it not possible to use an nfs based repo for kickstart under CentOS 7.5? E.g. repo --name=epel --baseurl=file://server/path/to/local/copy/of/epel With trial and error I figured out that this is the correct syntax to use for an nfs-based repo. But packages from this repo in the %packages section are not found. You have specificed that the package 'bla' should be installed. This package does not exist. ... It works with http off the same server and location, but I'd rather not use that. NFS installation as such, using nfs --server ... -- dir ..., off the same server and filesystem is working fine. So there is no problem here with nfs or repo setup.

3 6

Running a command at startup
by Robert Moskowitz 13 Dec '18

13 Dec '18

On a support forum, I was told that to turn off my board's blue led run: echo none | sudo tee /sys/class/leds/blue\:heartbeat/trigger Well, this does not survive a system reboot. So I was told: Add the off bit to /etc/rc.local Add it above "exit 0" So of course, CentOS is past using rc.local and recommends: # It is highly advisable to create own systemd services or udev rules # to run scripts during boot instead of using this fi So can someone point me to how to make this into a simple systemd service? thanks

7 11

core file generation
by sthustfo 13 Dec '18

13 Dec '18

On my cent os 7 system, I can trigger a running process to dump core by sending a signal from console (kill -SIGABRT pid). However after generating some core files in this way, the system no longer generates any more core dump files. The core file pattern is set to /tmp/store/core.%h.%e.%p.%t. Is there any way to find out why the core files are no longer generated? There is sufficient disk space and permission to the folder is also intact. The initial core files generated are found in the specified folder. Any logs help explain this behavior? Thanks.

1 0

Re: [CentOS] SFTP - Private/Public Authentication Keysets Beyond The First Set
by James B. Byrne 13 Dec '18

13 Dec '18

On Wed, December 12, 2018 16:40, Gary Braatz wrote: > Inclusion of the -i flag and the location of the private key solved > the > problem. > You can also set up a personalised ssh config file in the ~/.ssh directory of the user employed to establish the sftp/ssh connections: #BOF # /home/myuser/.ssh/config # Host parameter is any arbitrary string. # sftp remoteuserid(a)first.site.com == Host site1 HostName first.site.com User remoteuserid IdentityFile /home/myuser/.ssh/id_rsa # sftp otheruserid(a)second.other.com == Host site2 HostName second.other.com User otheruserid IdentityFile /home/myuser/.ssh/rsa_vendor2 #EOF Then just run 'sftp site1' or 'sftp site2' to connect as required. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

ClamAV installation is OUTDATED! as reported by freshclam utility on CentOS Linux release 7.6.1810 (Core)
by Kaushal Shriyan 13 Dec '18

13 Dec '18

Hi, I am running CentOS Linux release 7.6.1810 (Core) with ClamAV installed. When i am running freshclam i am seeing a Warning message and the details are described below:- # freshclam ClamAV update process started at Thu Dec 13 11:49:18 2018 WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.100.2 Recommended version: 0.101.0 DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr) nonblock_recv: recv timing out (30 secs) WARNING: getfile: Download interrupted: Operation now in progress (IP: 104.16.189.138) WARNING: Can't download daily.cvd from database.clamav.net Trying again in 5 secs... ClamAV update process started at Thu Dec 13 11:49:56 2018 WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.100.2 Recommended version: 0.101.0 DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr) Trying host database.clamav.net (104.16.188.138)... Downloading daily.cvd [100%] daily.cvd updated (version: 25202, sigs: 2176766, f-level: 63, builder: neo) bytecode.cvd is up to date (version: 327, sigs: 91, f-level: 63, builder: neo) Database updated (6743106 signatures) from database.clamav.net (IP: 104.16.188.138) # *OS Version* # cat /etc/redhat-release CentOS Linux release 7.6.1810 (Core) # yum update No packages marked for update # *EPEL Version* # rpm -qa | grep epel epel-release-7-11.noarch # *ClamAV Version* # rpm -qa | grep clamav clamav-lib-0.100.2-2.el7.x86_64 clamav-filesystem-0.100.2-2.el7.noarch clamav-update-0.100.2-2.el7.x86_64 clamav-0.100.2-2.el7.x86_64 # Please comment. Thanks in Advance. I look forward to hearing from you. Best Regards, Kaushal

2 1

CentOS 7.6 external USB dmesg issue
by Jerry Geis 12 Dec '18

12 Dec '18

I have a brand new 2T external Samsung SSD disk. (two of them) for backup. I tried the first one and had an issue, I tried the second one and got the same issue. Am I doing something wrong ? I find it hard to believe the SSD (both) are bad. I plugged in the USB 3.1 adapter, I fdisk /dev/sdd, n, p, default, default, w. then mkfs.ext4 -j /dev/sdd1, then just mount and rsync. [ 1085.193710] [<ffffffffa94dca7e>] ? account_entity_dequeue+0xae/0xd0 [ 1085.193715] [<ffffffffa9b67c49>] schedule+0x29/0x70 [ 1085.193719] [<ffffffffa9b65721>] schedule_timeout+0x221/0x2d0 [ 1085.193724] [<ffffffffa942a621>] ? __switch_to+0x151/0x580 [ 1085.193730] [<ffffffffa9501052>] ? ktime_get_ts64+0x52/0xf0 [ 1085.193735] [<ffffffffa9b672ed>] io_schedule_timeout+0xad/0x130 [ 1085.193740] [<ffffffffa94c2886>] ? prepare_to_wait_exclusive+0x56/0x90 [ 1085.193744] [<ffffffffa9b67388>] io_schedule+0x18/0x20 [ 1085.193750] [<ffffffffa9743de3>] get_request+0x243/0x7d0 [ 1085.193756] [<ffffffffa977c401>] ? __radix_tree_create+0x11/0x360 [ 1085.193761] [<ffffffffa94c2d00>] ? wake_up_atomic_t+0x30/0x30 [ 1085.193767] [<ffffffffa9746cae>] blk_queue_bio+0xfe/0x400 [ 1085.193772] [<ffffffffa9744ef7>] generic_make_request+0x147/0x380 [ 1085.193778] [<ffffffffa97451a0>] submit_bio+0x70/0x150 [ 1085.193786] [<ffffffffa967e555>] ? bio_alloc_bioset+0x115/0x310 [ 1085.193791] [<ffffffffa967a197>] _submit_bh+0x127/0x160 [ 1085.193797] [<ffffffffa967a1e0>] submit_bh+0x10/0x20 [ 1085.193808] [<ffffffffc1bd8424>] ext4_read_block_bitmap_nowait+0x4c4/0x640 [ext4] [ 1085.193828] [<ffffffffc1c16641>] ext4_mb_init_cache+0x181/0x6e0 [ext4] [ 1085.193834] [<ffffffffa95c5afe>] ? lru_cache_add+0xe/0x10 [ 1085.193840] [<ffffffffa95b74de>] ? find_or_create_page+0x5e/0xa0 [ 1085.193858] [<ffffffffc1c16cc6>] ext4_mb_init_group+0x126/0x230 [ext4] [ 1085.193874] [<ffffffffc1c16f54>] ext4_mb_good_group+0x184/0x1a0 [ext4] [ 1085.193889] [<ffffffffc1c19735>] ext4_mb_regular_allocator+0x1c5/0x470 [ext4] [ 1085.193906] [<ffffffffc1c12d0c>] ? __ext4_journal_stop+0x3c/0xb0 [ext4] [ 1085.193921] [<ffffffffc1c14bec>] ? ext4_mb_normalize_request+0x20c/0x560 [ext4] [ 1085.193936] [<ffffffffc1c1b59b>] ext4_mb_new_blocks+0x65b/0xa20 [ext4] [ 1085.193942] [<ffffffffa967918d>] ? __getblk+0x2d/0x300 [ 1085.193961] [<ffffffffc1c223cb>] ext4_ind_map_blocks+0xb9b/0xc20 [ext4] [ 1085.193968] [<ffffffffa94c6258>] ? hrtimer_cancel+0x28/0x40 [ 1085.193973] [<ffffffffa95d82c8>] ? zone_statistics+0x88/0xa0 [ 1085.193987] [<ffffffffc1bdfd35>] ext4_map_blocks+0x295/0x6e0 [ext4] [ 1085.193993] [<ffffffffa9657c7e>] ? do_select+0x73e/0x7c0 [ 1085.193999] [<ffffffffa961c0b2>] ? kmem_cache_alloc+0x1c2/0x1f0 [ 1085.194006] [<ffffffffa96787b1>] ? alloc_buffer_head+0x21/0x60 [ 1085.194018] [<ffffffffc1be035f>] _ext4_get_block+0x1df/0x220 [ext4] [ 1085.194030] [<ffffffffc1be03b6>] ext4_get_block+0x16/0x20 [ext4] [ 1085.194036] [<ffffffffa967ae78>] __block_write_begin_int+0x198/0x5f0 [ 1085.194041] [<ffffffffa961c0b2>] ? kmem_cache_alloc+0x1c2/0x1f0 [ 1085.194053] [<ffffffffc1be03a0>] ? _ext4_get_block+0x220/0x220 [ext4] [ 1085.194067] [<ffffffffc1be4c56>] ? ext4_write_begin+0x116/0x440 [ext4] [ 1085.194073] [<ffffffffa967b2e1>] __block_write_begin+0x11/0x20 [ 1085.194085] [<ffffffffc1be4ccf>] ext4_write_begin+0x18f/0x440 [ext4] [ 1085.194091] [<ffffffffa95b5f84>] generic_file_buffered_write+0x124/0x2c0 [ 1085.194098] [<ffffffffa95b88c2>] __generic_file_aio_write+0x1e2/0x400 [ 1085.194105] [<ffffffffa95b8b39>] generic_file_aio_write+0x59/0xa0 [ 1085.194116] [<ffffffffc1bda322>] ext4_file_write+0xd2/0x1e0 [ext4] [ 1085.194121] [<ffffffffa9640823>] do_sync_write+0x93/0xe0 [ 1085.194127] [<ffffffffa9641310>] vfs_write+0xc0/0x1f0 [ 1085.194132] [<ffffffffa964212f>] SyS_write+0x7f/0xf0 [ 1085.194138] [<ffffffffa9b74ddb>] system_call_fastpath+0x22/0x27 Thanks, Jerry

4 7

Re: [CentOS] CentOS 7.6 external USB dmesg issue
by mark 12 Dec '18

12 Dec '18

Jerry Geis wrote: >> Do you have any "history" with the adapter you connected them to? If >> not consider it as a possibility as well >> (from bad experience of total filesystem/partition corruption on two >> hard drives only to discover it was >something on the motherboard). > > Actually yes I used them many times back on C7.5 Both the motherboard > and USB adapter. > I'm a tad confused: you said the USB drive was brand new - did you use them with C 7.5, or not? Can you try to do a b/u using whatever drive you used before? mark

1 0

CentOS-announce Digest, Vol 166, Issue 3
by centos-announce-request＠centos.org 12 Dec '18

12 Dec '18

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 of PHP 7.2 (Jan Stan?k) 2. Announcing release of Varnish 6 (Jan Stan?k) 3. Announcing release of NodeJS 10 (Jan Stan?k) 4. Announcing release of nginx 1.14 (Jan Stan?k) 5. Announcing release of MySQL 8.0 (Jan Stan?k) 6. Announcing release of Git 2.18 (Jan Stan?k) ---------------------------------------------------------------------- Message: 1 Date: Tue, 11 Dec 2018 16:23:26 +0100 From: Jan Stan?k <jstanek(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing release of PHP 7.2 Message-ID: <5f81205f-1311-8186-44f3-12d6e89a284d(a)redhat.com> Content-Type: text/plain; charset="windows-1252" I am pleased to announce the immediate availability of PHP in version 7.2 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo) QuickStart ---------- You can get started in three easy steps: # 1. Install a package with repository for your system: $ sudo yum install centos-release-scl # 2. Install the collection: $ sudo yum install rh-php72 # 3. Start using the software collection: $ scl enable rh-php72 bash At this point you should be able to use php just as a normal application. Examples of commands run might be: $ sudo systemctl start rh-php72-php-fpm $ php my-app.php $ sudo yum install rh-php72-php-devel $ sudo yum install libxml2-devel $ sudo pear install Cache_Lite $ sudo pecl install xmldiff More information about this collection can be found at https://www.softwarecollections.org/en/scls/rhscl/rh-php72/ This collections is CentOS-based rebuild built by SCLo SIG community, and the packages have been available in Red Hat Software Collections 3.2 for RHEL: https://access.redhat.com/documentation/en-us/red_hat_software_collections/… So, for RHEL-based builds, follow the steps in the documentation above. About Software Collections -------------------------- Software Collections give you the power to build, install, and use multiple versions of software on the same system, without affecting system-wide installed packages. Each collection is delivered as a group of RPMs, with the grouping being done using the name of the collection as a prefix of all packages that are part of the software collection. The SCLo SIG in CentOS ---------------------- The Software Collections SIG group is an open community group co-ordinating the development of the SCL technology, and helping curate a reference set of collections. In addition to the collection NodeJS being released here, we also build and deliver databases, web servers, and language stacks including multiple versions of PostgreSQL, MariaDB, Apache HTTP Server, Python, Ruby, Ruby on Rails and others. You can learn more about Software Collections concepts at: https://softwarecollections.org You can find information on the SIG at https://wiki.centos.org/SpecialInterestGroup/SCLo ; this includes how to get involved and help with the effort. Enjoy! -- Jan Stanek Associate Software Engineer, Brno Red Hat Czech jstanek(a)redhat.com IM: jstanek

1 0

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