Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Start a nNew thread

CentOS-announce Digest, Vol 134, Issue 3
by centos-announce-request＠centos.org 05 Apr '16

05 Apr '16

1 0

email
by gemma adlawan 05 Apr '16

05 Apr '16

1 0

How to install VPN server
by Chandran Manikandan 05 Apr '16

05 Apr '16

Hi All, I have running centos 6 server in my head quarters and branch offices. I need to access file server files in both location using VPN. How to setup vpn server in both location and how to access it. Could any one help me. -- *Thanks,* *Manikandan.C* *System Administrator*

2 1

EPEL - Clamav update?
by Rob Kampen 04 Apr '16

04 Apr '16

EPEL maintainers? I note messages in the log about updated version 0.99.1 of CLAMAV being available since Mar 5th. for CentOS 6 no update is available yet. I used to use rpmforge for this package but that languished for months before updates became available and eventually stopped altogether. Is there something I can do to assist in getting this package updated? I have no idea if this is a difficult package to compile with lots of dependancies or some otherwise complexities. In this era of constant SPAM and so many virus / trojan attempts to do harm to others, it is vital that we run this package to protect our users. Please let me know if / how I can assist. Kind regards Rob

5 4

Centos7: Mount problem (Unit mnt-bk\x2dbenvet\x2d01.mount is bound to inactive unit dev-disk-by\x2dlabel-bk\x2dbenvet\x2d01.device. Stopping, too.
by Dario Lesca 03 Apr '16

03 Apr '16

On a server Centos 7.2 I insert my 1Tb usb disk and run sudo mount LABEL=bk-benvet-01 /mnt/bk-benvet-01 the command seem to work but nothing is mounted Into log I see this issue: > apr 01 13:49:06 s-virt.dom.loc kernel: XFS (sdb1): Mounting V4 Filesystem > apr 01 13:49:06 s-virt.dom.loc kernel: XFS (sdb1): Ending clean mount > apr 01 13:49:06 s-virt.dom.loc systemd[1]: Unit mnt-bk\x2dbenvet\x2d01.mount is bound to inactive unit dev-disk-by\x2dlabel-bk\x2dbenvet\x2d01.device. Stopping, too. > apr 01 13:49:06 s-virt.dom.loc systemd[1]: Unmounting /mnt/bk-benvet-01... > apr 01 13:49:06 s-virt.dom.loc kernel: XFS (sdb1): Unmounting Filesystem > apr 01 13:49:06 s-virt.dom.loc systemd[1]: Unmounted /mnt/bk-benvet-01. I have try this: > [root@s-virt ~]# systemctl start dev-disk-by\x2dlabel-bk\x2dbenvet\x2d01.device > Job for dev-disk-byx2dlabel-bkx2dbenvetx2d01.device timed out. > [root@s-virt ~]# systemctl status dev-disk-by\x2dlabel-bk\x2dbenvet\x2d01.device > ● dev-disk-byx2dlabel-bkx2dbenvetx2d01.device > Loaded: loaded > Active: inactive (dead) > > apr 01 13:52:36 s-virt.vettorello.loc systemd[1]: Job dev-disk-byx2dlabel-bkx2dbenvetx2d01.device/start timed out. > apr 01 13:52:36 s-virt.vettorello.loc systemd[1]: Timed out waiting for device dev-disk-byx2dlabel-bkx2dbenvetx2d...ice. > apr 01 13:52:36 s-virt.vettorello.loc systemd[1]: Job dev-disk-byx2dlabel-bkx2dbenvetx2d01.device/start failed wi...ut'. > Hint: Some lines were ellipsized, use -l to show in full. > [root@s-virt ~]# systemctl status dev-disk-by\x2dlabel-bk\x2dbenvet\x2d01.device -l > ● dev-disk-byx2dlabel-bkx2dbenvetx2d01.device > Loaded: loaded > Active: inactive (dead) But nothing is changed How to resolve this problem? Many thanks -- Dario Lesca (inviato dal mio Linux Fedora 23 Workstation)

2 4

Re: [CentOS] EPEL - Clamav update?
by Richard 03 Apr '16

03 Apr '16

> Date: Sunday, April 03, 2016 14:39:04 +1200 > From: Rob Kampen <rkampen(a)kampensonline.com> > > EPEL maintainers? > I note messages in the log about updated version 0.99.1 of CLAMAV > being available since Mar 5th. > for CentOS 6 no update is available yet. > I used to use rpmforge for this package but that languished for > months before updates became available and eventually stopped > altogether. > Is there something I can do to assist in getting this package > updated? > I have no idea if this is a difficult package to compile with lots > of dependancies or some otherwise complexities. > In this era of constant SPAM and so many virus / trojan attempts to > do harm to others, it is vital that we run this package to protect > our users. > Please let me know if / how I can assist. > Kind regards > Rob I'm seeing 0.99.1-1.el6 of the various (x86_64) bits in epel-testing, so you could get it from there and update to the fully tested version when it is released. In general I think it is most important to keep your signatures current. I don't get the sense that the changes between [sub-]point-releases are earth shattering (despite the ominous warning that you will see in your logs).

1 0

RHEL 7.3 wish-list
by Alice Wonder 02 Apr '16

02 Apr '16

CentOS tracks RHEL and there is something I think probably can only be done in a point release but I believe should be done. Update to nss and curl. The problem - the version of curl that ships with CentOS does not support ECC cryptography. A newer version would, but requires manual specification of the ciphers if the TLS/SSL library used (NSS on RHEL/Fedora) does not have the ECC ciphers enabled by default, and the NSS in RHEL/CentOS 7 does not. This causes a problem when using CentOS 7 for something like a CDN that needs to pull content from a server using modern ECC cryptography without support for the older cryptography methods, and some sensitive servers are starting to do just that to avoid being vulnerable to various 0 day exploits that pop up with older cryptography. I think the NSS library should be rebuilt to have ECC ciphers enabled by default (I don't think that requires a version update) and that curl should be updated, with a newer build, that includes a bump to the .so version. Thoughts on this? I'm out of town, I plan to try and file a bugzilla for this when I get back, but if this sounds idiotic to most then I won't. I can solve it on my system with a local build. Thank you for your time. -- -=- Sent my from my laptop, may not be able to respond timely

2 1

CentOS-announce Digest, Vol 134, Issue 2
by centos-announce-request＠centos.org 02 Apr '16

02 Apr '16

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. Notice of Service Outage and followup LON1/UK Facility (Karanbir Singh) 2. Announcing release for Developer Toolset 4 on CentOS Linux 6 x86_64 SCL (Honza Horak) 3. Announcing release for Developer Toolset 4 on CentOS Linux 7 x86_64 SCL (Honza Horak) ---------------------------------------------------------------------- Message: 1 Date: Wed, 30 Mar 2016 11:25:19 +0100 From: Karanbir Singh <kbsingh(a)centos.org> To: CentOS Announcements List <centos-announce(a)centos.org> Subject: [CentOS-announce] Notice of Service Outage and followup LON1/UK Facility Message-ID: <56FBA98F.6000102(a)centos.org> Content-Type: text/plain; charset=utf-8 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 == What happened == On Wednesday February 24th, at 6pm UTC time, the DC hosting some of the CentOS equipments used for various roles had suffered from multiple electricity power outages. The facility was completely dark for just under 2 hrs, and we were able to start recovering services by 8pm UTC. By midnight we had most services restored, by 2:00AM UTC Feb 25th we had all services restored. That meant that the machines in those racks were running on batteries (ups in the racks) but finally went down in an uncontrolled way due to lack ot communication with that UPS. Subsequent on Monday March 14th, we suffered another power outage in the racks, this time due to a overload on the rack power circuits. == Services that were impacted == - severity critical : mirrorlist.centos.org node (IPv6) went down (while multiple mirrorlist.centos.org nodes for IPv4 nodes were still online). That means that machines with only IPV6 connectivity couldn't get yum to work to retrieve the list of nearest mirrors. - severity medium : Our main buildservices queue management services were down; note: this did not impact our ability to build, test and deliver updates. - severity medium : www.centos.org and www.centos.org/forums weren't reachable through IPv6 : at the moment, those services are natively reachable through IPv4, but proxied through nodes in that DC for IPv6 users. Most tested browsers were falling back to IPv4 during that period - severity medium : CentOS DevCloud (https://wiki.centos.org/DevCloud) : that means that CentOS Developers weren't able to instantiate new CentOS test VMs for their work, but also weren't able to reach the existing ones. - severity low : several publicly facing small services like http://planet.centos.org , http://seven.centos.org (not critical and could be restored quickly to other VMs elsewhere) - severity low : the server leading the armv7hl builds for the Plague build farm was also offline, meaning no armhfp build during that timeframe (but not updates were to be built, so mitigated issue) = Followup actions and notes Over the years, the baseline recovery model we've used and tried to enforce is one of 'restore in place', take a downtime hit if needed - and ensure we have service continuity for the user facing components ( the mirrorlist service, the centos update and content distribution services). For other resources, like the main website etc, we ensure there are good backups available in multiple places, usable to restore services should there be a need. This model has worked well for us over the years, and we've had very little, if any, service outages that had a user impact. The restore in place/restore outside HA also meant we were able to better utilise the exclusively sponsored machines we rely on. However, as the project grows, with a lot more infrastructure being consolidated into a few locations for non CDN services, our exposure to service downtime has dramatically increased. Its clear that we need to expand the scope of where we backup to, how we backup, how we anticipate failure and our ability to restore services in a timely manner should there be facilities outages. In the coming weeks, we are going to undertake a deep dive into our Infrastructure design and delivery and try to first come up with a consolidated set of risks we need to manage against, and then work towards reducing the risk, spreading the availability as needed. Our backend storage platform for the DevCloud and persistent storage for other nodes in the facility is run from a distributed, replicated Gluster setup. Inspite of the sudden loss of power, in a production environment with hundreds of running VMs and dozens of running data jobs, we were able to trivially recover our entire data set with minimum data loss. Some of the running VMs inside the DevCloud did see local filesystem issues, but we dont think that was a backing storage issue. This event has dramatically increased out confidence in the gluster technology stack and we will certainly be looking at extending deployments for it internally. == Comments about hosting facility == Their Status post about this http://status.uk2.net/2016/02/24/london-power-outage/ We have multiple racks at this facility, and have a long standing relationship with them going back to late Summer 2012. Over this period we have had a near perfect uptime record for our equipment there. And above all we have been consistently impressed with the speed of and the knowledgeable support we've recieved at the DC. In many cases, how the facility reacts to outage defines the real service value - and in this case, we can only commend the fantastic support we had through the outage hours. We do however feel there could be better monitoring and reporting of some of the facilities information and will be working with them to improve in those regards. Fabian Arrotin and Karanbir Singh The CentOS Project -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJW+6mPAAoJEI3Oi2Mx7xbtHo8IAI+RVIDjGwJOzgJ5Ry7mHwLe Zc+aBUQklDk5oRaDk7QZHsaGp1lclNsutBk3YujNlXwMC4hUKdPwkTVuX50usQ7s kd7qF1BlElNyfMPfFJGwchIQBDOZqZxkZP4uOrvQUnIZUYfyx6NnPnGS0uatBdnw hBJ6TbgP6i50h7U0fNWjHU2I8xe0zsx1jVrvNngDMlQcIHC0d1KMtpOgSMR5f9Bn bLwghfD4/yPyqJP1sc+021ANk1+a7uXs4KKG3MXpMlFyvYmv2ict0Q/sDtz0jzCx kbRgDGm/GF1TUUENciESkHPKy3kLWA1oCicOkiEhzNz2YwFQNdNpi9PqWEK/F5Q= =bDIN -----END PGP SIGNATURE----- ------------------------------ Message: 2 Date: Thu, 31 Mar 2016 17:38:07 +0200 From: Honza Horak <hhorak(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing release for Developer Toolset 4 on CentOS Linux 6 x86_64 SCL Message-ID: <56FD445F.8060304(a)redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed I am pleased to announce the immediate availability of Developer Toolset 4 on CentOS Linux 6 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: $ sudo yum install centos-release-scl $ sudo yum install devtoolset-4-toolchain $ scl enable devtoolset-4 bash At this point you should be able to use gcc and other tools just as a normal application. Examples of commands run might be: $ gcc hello.c $ sudo yum install devtoolset-4-valgrind $ valgrind ./a.out $ gdb ./a.out In order to view the individual components included in this collection, including additional development tools, you can run: $ sudo yum list devtoolset-4\* 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 collection devtoolset-4 delivers version 5.2.1 of the GNU Compiler Collection, GNU Debugger, and other development, debugging, and performance monitoring tools as RPMs. 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 Developer Toolset collection being released here, we also build and deliver databases, web servers, and language stacks including multiple versions of PostgreSQL, MariaDB, Apache HTTP Server, NodeJS, Ruby, Python and others. Software Collections SIG release was announced at https://lists.centos.org/pipermail/centos-announce/2015-October/021446.html You can learn more about Software Collections concepts at: http://softwarecollections.org You can find information on the SIG at https://wiki.centos.org/SpecialInterestGroup/SCLo ; this includes howto get involved and help with the effort. We meet every second Wednesday at 16:00 UTC in #centos-devel (ref: https://www.centos.org/community/calendar) for an informal open forum open to anyone who might have comments, concerns or wants to get started with SCL's in CentOS. Enjoy! Honza SCLo SIG member ------------------------------ Message: 3 Date: Thu, 31 Mar 2016 17:38:11 +0200 From: Honza Horak <hhorak(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing release for Developer Toolset 4 on CentOS Linux 7 x86_64 SCL Message-ID: <56FD4463.3040800(a)redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed I am pleased to announce the immediate availability of Developer Toolset 4 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: $ sudo yum install centos-release-scl $ sudo yum install devtoolset-4-toolchain $ scl enable devtoolset-4 bash At this point you should be able to use gcc and other tools just as a normal application. Examples of commands run might be: $ gcc hello.c $ sudo yum install devtoolset-4-valgrind $ valgrind ./a.out $ gdb ./a.out In order to view the individual components included in this collection, including additional development tools, you can run: $ sudo yum list devtoolset-4\* 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 collection devtoolset-4 delivers version 5.2.1 of the GNU Compiler Collection, GNU Debugger, Eclipse development platform, and other development, debugging, and performance monitoring tools as RPMs. 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 Developer Toolset collection being released here, we also build and deliver databases, web servers, and language stacks including multiple versions of PostgreSQL, MariaDB, Apache HTTP Server, NodeJS, Ruby, Python and others. Software Collections SIG release was announced at https://lists.centos.org/pipermail/centos-announce/2015-October/021446.html You can learn more about Software Collections concepts at: http://softwarecollections.org You can find information on the SIG at https://wiki.centos.org/SpecialInterestGroup/SCLo ; this includes howto get involved and help with the effort. We meet every second Wednesday at 16:00 UTC in #centos-devel (ref: https://www.centos.org/community/calendar) for an informal open forum open to anyone who might have comments, concerns or wants to get started with SCL's in CentOS. Enjoy! Honza SCLo SIG member ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 134, Issue 2 ***********************************************

1 0

SSD disk and SMART errors
by Miguel Medalha 02 Apr '16

02 Apr '16

Two days ago I installed a brand new SSDNow E50 series (Enterprise) disk on a server. I intend to move the OS there. I just did the physical install and copied a few files to and from it just to see if it was OK. I left it there, waiting for an opportunity to configure it to do real work. Now I have looked at it with smartctl -a and it gives me the following info: 1 Raw_Read_Error_Rate 0x0033 104 104 050 Pre-fail Always - 9127078 5 Reallocated_Sector_Ct 0x0033 100 100 003 Pre-fail Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 55 (241 12 0) 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 7 13 Read_Soft_Error_Rate 0x0032 104 104 000 Old_age Always - 9127078 100 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 4 170 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 8480 171 Unknown_Attribute 0x000a 100 100 000 Old_age Always - 0 172 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 174 Unknown_Attribute 0x0030 000 000 000 Old_age Offline - 6 177 Wear_Leveling_Count 0x0000 000 000 000 Old_age Offline - 0 181 Program_Fail_Cnt_Total 0x000a 100 100 000 Old_age Always - 0 182 Erase_Fail_Count_Total 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 090 Old_age Always - 0 187 Reported_Uncorrect 0x0012 100 100 000 Old_age Always - 0 194 Temperature_Celsius 0x0022 028 033 000 Old_age Always - 28 (Min/Max 20/33) 195 Hardware_ECC_Recovered 0x001c 120 120 000 Old_age Offline - 9127078 196 Reallocated_Event_Count 0x0033 100 100 003 Pre-fail Always - 0 198 Offline_Uncorrectable 0x0010 120 120 000 Old_age Offline - 75479755259904 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 201 Unknown_SSD_Attribute 0x001c 120 120 000 Old_age Offline - 9127078 204 Soft_ECC_Correction 0x001c 120 120 000 Old_age Offline - 9127078 230 Unknown_SSD_Attribute 0x0013 100 100 000 Pre-fail Always - 0 231 Temperature_Celsius 0x0000 100 100 011 Old_age Offline - 0 232 Available_Reservd_Space 0x0032 000 000 000 Old_age Always - 33 233 Media_Wearout_Indicator 0x0032 000 000 000 Old_age Always - 6 234 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 7 235 Unknown_Attribute 0x0033 100 100 002 Pre-fail Always - 0 241 Total_LBAs_Written 0x0032 000 000 000 Old_age Always - 7 242 Total_LBAs_Read 0x0032 000 000 000 Old_age Always - 5 Just look at the number under "198 Offline_Uncorrectable". Is this normal for this type of disk? Is smartctl misinterpreting the disk's features? The disk has been there essentially doing nothing and it presents such enormous numbers of errors. Why? This is under CentOS 7 (1511).

2 1

Is there a way to detect/validate DHCP static IP assignment?
by David Copperfield 01 Apr '16

01 Apr '16

Hi, We have tens of networks(VLANs) in data center with a central Linux DHCP server. each network has their router to do the DHCP relay. So, the DHCP server's configuration files has tens 'subnet' statements. Because PXE booting is standard in whole data center, there are also thousands of static MAC-IP mapping 'host' statements in dhcp configuration. The big challenge with a central dhcp server is how to detect typo in the thousands of MAC-IP 'host' statements? -- a single char/digit typo here will fail a PXE booting or download wrong post-installation snippets. Is there a tool to validate all 'host' statements from another Linux box? I tried nagios check-dhcp plugin, with a series of real MAC addresses(for hosts in other different networks). Surprisingly, the IP address came back were not the static IP addresses in 'host' statement, but dynamic addresses in the pool defined for this particular network (where I ran check-dhcp from). check_dhcp was run with the following arguments: /usr/lib64/nagios/plugins/check_dhcp --verbose --server=<my_dhcp_server> --interface=eth0 --mac=<real_Mac_for_servers_in_diff_networks> --unicast remove --unicast doesn't help but just see more DHCP replys. Interestingly, with a same MAC address, and the above same command, from two Centos boxes on different network there will be different dynamic IPs! instead the static IP defined with 'host' statement. So, how can we validate static IP assignment? Thanks. Best,David,

2 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss