Discuss April 2015

discuss@lists.centos.org

168 participants
185 discussions

Selinux issues with 7.1 update
by Joseph L. Casale 05 Apr '15

05 Apr '15

I am trying to update some local policies for bacula that allow a series of clients with pre run scripts to su in order to perform some preparatory work for a backup. With selinux enforcing, the su is denied obviously execute as bacula_t tries su_exec_t. You only see this with enforcing enabled? So creating an initial policy for that (this is not the way to do this) allows one more avc to appear for execute_no_ as bacula_t tries su_exec_t again. The problem is once these are enabled with local policies they seem to be ignored producing the same avc's. Why are the initial avc's not generated in permissive allowing a complete policy to be derived? If they can't appear in permissive mode, even after playing wackamole with avc's one by one, there is no resolution as they continue to get denied. Anyone else seeing similar or know what I am missing? Bacula-fd runs as root/root. Thanks, jlc

1 0

Re: [CentOS] Fail2Ban Centos 7 is there a trick to making it work?
by James B. Byrne 05 Apr '15

05 Apr '15

On Mon, March 9, 2015 13:11, John Plemons wrote: > Been working on fail2ban, and trying to make it work with plain Jane > install of Centos 7 > > Machine is a HP running 2 Quad core Xeons, 16 gig or ram and 1 plus TB > of disk space. Very generic and vanilla. > > Current available epel repo version is fail2ban-0.9.1 > > Looking at the log file, fail2ban starts and stops fine, there isn't > output though showing any login attempts being restricted. > > 2015-03-09 12:54:37,930 fail2ban.server [14805]: INFO > Stopping all jails > 2015-03-09 12:54:37,931 fail2ban.server [14805]: INFO > Exiting Fail2ban > 2015-03-09 12:54:38,338 fail2ban.server [16678]: INFO > Changed logging target to /var/log/fail2ban.log for Fail2ban v0.9.1 > 2015-03-09 12:54:38,341 fail2ban.database [16678]: INFO > Connected to fail2ban persistent database > '/var/lib/fail2ban/fail2ban.sqlite3' > > I copied jail.conf and added the edited jail.local to the directory > /etc/fail2ban/ > > This is about as far as I have gotten with searches on how to > configure > with Centos 7. > > Any help would be welcome. What am I missing? > > john > This is what I have for ssh in jail.conf [ssh-iptables] enabled = true filter = sshd action = iptables[name=SSH, port=ssh, protocol=tcp] sendmail-whois[name=SSH, dest=x(a)harte-lyne.ca, sender=x(a)harte-lyne.ca, sendername=Fail2Ban] logpath = /var/log/secure maxretry = 5 And this (among many others) is what we have in /etc/fail2ban/action.d cat /etc/fail2ban/action.d/iptables.conf # Fail2Ban configuration file # # Author: Cyril Jaquier # # [INCLUDES] before = iptables-blocktype.conf [Definition] # Option: actionstart # Notes.: command executed once at the start of Fail2Ban. # Values: CMD # actionstart = iptables -N fail2ban-<name> iptables -A fail2ban-<name> -j RETURN iptables -I <chain> -p <protocol> --dport <port> -j fail2ban-<name> # Option: actionstop # Notes.: command executed once at the end of Fail2Ban # Values: CMD # actionstop = iptables -D <chain> -p <protocol> --dport <port> -j fail2ban-<name> iptables -F fail2ban-<name> iptables -X fail2ban-<name> # Option: actioncheck # Notes.: command executed once before each actionban command # Values: CMD # actioncheck = iptables -n -L <chain> | grep -q 'fail2ban-<name>[ \t]' # Option: actionban # Notes.: command executed when banning an IP. Take care that the # command is executed with Fail2Ban user rights. # Tags: See jail.conf(5) man page # Values: CMD # actionban = iptables -I fail2ban-<name> 1 -s <ip> -j <blocktype> # Option: actionunban # Notes.: command executed when unbanning an IP. Take care that the # command is executed with Fail2Ban user rights. # Tags: See jail.conf(5) man page # Values: CMD # actionunban = iptables -D fail2ban-<name> -s <ip> -j <blocktype> [Init] # Default name of the chain # name = default # Option: port # Notes.: specifies port to monitor # Values: [ NUM | STRING ] Default: # port = ssh # Option: protocol # Notes.: internally used by config reader for interpolations. # Values: [ tcp | udp | icmp | all ] Default: tcp # protocol = tcp # Option: chain # Notes specifies the iptables chain to which the fail2ban rules should be # added # Values: STRING Default: INPUT chain = INPUT HTH -- *** E-Mail is NOT a SECURE channel *** 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

3 3

perf trace
by Александр Кириллов 05 Apr '15

05 Apr '15

# perf trace perf: 'trace' is not a perf-command. See 'perf --help'. Should 'perf trace' work in C6.6 or this is a bug related to https://bugzilla.redhat.com/show_bug.cgi?id=892893? # rpm -qa perf perf-2.6.32-504.12.2.el6.x86_64

1 0

systemctl (again)
by J Martin Rushton 05 Apr '15

05 Apr '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been trying to get the timidity system running as a daemon. I wrote the following init script: #!/bin/sh # # timidity # ### BEGIN INIT INFO # Provides: timidity # Required-Start: # Required-Stop: # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Add and remove timidity # Description: ### END INIT INFO . /etc/rc.d/init.d/functions RETVAL=0 PROG=timidity EXEC=/bin/$PROG PIDFILE=/var/run/timidity.pid function start { [[ -x $EXEC ]] || exit 5 echo -n "Starting $PROG: " $EXEC -iAD RETVAL=$? echo return $RETVAL } function stop { echo -n "Stopping $PROG: " killproc $EXEC -TERM RETVAL=$? echo return $RETVAL } case "$1" in start) start RETVAL=$? ;; stop) stop RETVAL=$? ;; status) status $PROG RETVAL=$? ;; restart) stop start ;; reload) stop start ;; *) echo $"Usage: $prog {start|stop|status|restart|reload}" exit 1 esac exit $RETVAL When run through systemctl during startup it fails: [root@tamar init.d]# systemctl status timidity timidity.service - LSB: Add and remove timidity Loaded: loaded (/etc/rc.d/init.d/timidity) Active: active (exited) since Thu ... Process: 784 ExecStart=/etc/rc.d/init.d/timidity start (code=exited, status=0/SUCCESS) ... Starting LSB: Add and remove timidity... ... Starting timidity: ... jack_client_new: deprecated ... Started LSB: Add and remove timidity. ... Cannot connect to server socket err = No such file or directory ... Cannot connect to server request channel ... jack server is not running or cannot be started ... Couldn't open output device But when run directly is works fine: [root@tamar init.d]# ./timidity start Starting timidity: TiMidity starting in ALSA server mode Opening sequencer port: 128:0 128:1 128:2 128:3 If I use # service timidity start it also fails. I _think_ that what is happening is that systemctl is stripping off the switch. I've spent a couple of hours searching for any links or explanation and got nowhere. I even knocked up a script to try and separate the two parts: #!/bin/sh cd /etc/init.d ./timidity start but to no avail. If there is a simple fix could someone point me there, if it's complex don't bother, I only need the daemon when running MIDI and can start it by hand. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVHa+rAAoJEAF3yXsqtyBlKFUP/0olzOxF44xGa0/b1UI9LyKb 8LWLJ6XYXQfwJZvZ7N5v/r9g6WPesIuWf/TugXEz20MhrN0BhoqmUrkD9FjVnpFa B7zQxRQ/DUXs2Z/w2DCfHRs5QWr3o31EGNPw/cZtqMf2bq+Z0LXXlU6A4QozDFe8 Aq/ZYduOr5GG6D8DPRCSV2ggFGvs27I7vvp48bvCNZ4jh2dAjBSlygI42Koug2Ga UcAGllj4Litdm+O5hUpyPtsJC58umfNy4Lq9Y6HBxIpeZrioxNE+trNQHoZuzoP/ clLItDMwj990Hs7ft3eyt1oIihuCTsVQ3HOkn0fjZ0OAWPIudq7ZynzfHctMGtP2 Htx0A3coYxFFZ/fZZfYUkM4FQU6OA6fQ378u9hdxq9+XKayCh4938PZHmKjGHUTH DSu+iZVJ8DEc62pfgeLUWMidEgSu5/n5ROGIHed/wwt4nE6rGv/fz0D33ArMwD3t Ozybkt+FW2u8XK4qkA/ehgf3SBK4AIHMNg9IDWiWSaF4krQlInhKHGoCp1Xi1ISV 2C/Lb7exn2CX/Uohdhqy86HNOhHHbZ6mkOL1k8XTIIazjRWJWQ/+gkt6Bj39q+K8 NDnN03oVYsXgVz2nqFT3eQ001k/pRlkKn11ZYtEZ1fY77nzsOj+J3DD/txn8qTRi yNSvbWmxPj24hEVzSKu3 =CEIq -----END PGP SIGNATURE-----

5 15

Mysterious ICMP timeout?
by James B. Byrne 04 Apr '15

04 Apr '15

I am looking at these sorts of things as well: IN=eth0 OUT=eth1 SRC=129.250.200.121 DST=x.y.z.56 LEN=96 TOS=0x00 PREC=0x00 TTL=243 ID=32285 PROTO=ICMP TYPE=11 CODE=0 [SRC=x.y.z.56 DST=88.198.155.41 LEN=28 TOS=0x10 PREC=0x60 TTL=1 ID=1968 PROTO=UDP SPT=50131 DPT=6528 LEN=8 ] x.y.z.56 is a disused address in our netblock assignment. So whatever this is it is not legit. Does anyone recognize this? -- *** E-Mail is NOT a SECURE channel *** 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

Re: [CentOS] The future of centos
by James B. Byrne 04 Apr '15

04 Apr '15

On Fri, April 3, 2015 22:54, Always Learning wrote: > > On Fri, 2015-04-03 at 22:47 -0400, Digimer wrote: > >> No, people are speculating about the future of CentOS. > > . . . > The future is certain. To benefit from this free operating system, > tolerate the RH control and desire to ensure Centos and RHEL are not > exactly the same (including incompatible version numbers) or get > another operating system. It is that simple. > > Happy Easter to everyone. > > . . . There remain ClearOS and Scientific Linux. But, I am in no hurry to make any decision at the present time. I am not at all on-board with the "evil empire" takeover interpretation of recent events. I do not believe this to be the case. However, the golden rule holds that whoever pays the gold makes the rules. I do not think this situation will prove any different in the long run. When a "volunteer" board becomes dominated by a single commercial entity who pays employees to "volunteer" the long-term results are decisions that tend to favour that entity over all members. I have seen this happen first hand and our firm no long belongs to that particular national organisation in consequence. This is an interesting situation from a philosophical POV though. What are the ethics of attempting to monetize the intellectual property of others? What are the ethics of attempting to make use of the benefits that arise from that monetizing effort without paying for them? -- *** E-Mail is NOT a SECURE channel *** 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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64
by Ryan Qian 04 Apr '15

04 Apr '15

As a CentOs newbie, I'm not sure, will we still have CentOS 7.1 which derive from RHEL 7.1? or this is the new naming conversion for CentOS 7. Thanks! -Ryan > On Apr 1, 2015, at 12:30 AM, Karanbir Singh <kbsingh(a)centos.org> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > We would like to announce the general availability of CentOS Linux 7 > (1503) for 64 bit x86 compatible machines. > > This is the second major release for CentOS-7 and is tagged as 1503. > This build is derived from Red Hat Enterprise Linux 7.1 > > As always, read through the Release Notes at : > http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes > contain important information about the release and details about some > of the content inside the release from the CentOS QA team. These notes > are updated constantly to include issues and incorporate feedback from > the users. > > - ---------- > Updates, Sources, and DebugInfos > > This merges in all base, updates, and CR (continuous release) > components released in the month of March 2015. If you have been using > the CR repos on your previous CentOS Linux 7 install, you already have > all the components used to compose this new release. > > As with all CentOS Linux 7 components, this release was built from > sources hosted at git.centos.org. In addition, SRPMs that are a > byproduct of the build (and also considered critical in the code and > buildsys process) are being published to match every binary RPM we > release. Sources will be available from vault.centos.org in their own > dedicated directories to match the corresponding binary RPMs. Since > there is far less traffic to the CentOS source RPMs compared with the > binary RPMs, we are not putting this content on the main mirror > network. If users wish to mirror this content they can do so using the > reposync command available in the yum-utils package. All CentOS source > RPMs are signed with the same key used to sign their binary > counterparts. Developers and end users looking at inspecting and > contributing patches to the CentOS Linux distro will find the code > hosted at git.centos.org far simpler to work against. Details on how > to best consume those are documented along with a quick start at : > http://wiki.centos.org/Sources > > Debuginfo packages are also being signed and pushed. Yum configs > shipped in the new release file will have all the context required for > debuginfo to be available on every CentOS Linux install. > > This release supersedes all previously released content for CentOS > Linux 7, and therefore we highly encourage all users to upgrade their > machines. Information on different upgrade strategies and how to > handle stale content is included in the Release Notes. > > For the CentOS-7 build and release process we adopted a very open > process. The output of the entire buildsystem is made available, as it > is built, at http://buildlogs.centos.org/ - we hope to continue with > that process for the life of CentOS Linux 7, and hope to attempt > bringing CentOS-5 and CentOS-6 builds into the same system. > > - ---------- > Release file handling > > This release splits the /etc/centos-release from /etc/redhat-release > to better indicate the relationship between the two distributions. > There are also changes to the /etc/os-release file to incorporate > changes needed by the new abrt stack. > > - ---------- > Download > > In order to conserve donor bandwidth, and to make it possible to get > the mirror content sync'd out as soon as possible, we recommend using > torrents to get your initial installer images: > > Details on the images are available on the mirrors at > http://mirror.centos.org/centos/7/isos/x86_64/0_README.txt - that file > clearly highlights the difference in the images, and when one might be > more suitable than the others. > > The sizes, sha256 sums and torrents for the ISO files: > > * CentOS-7-x86_64-Minimal-1503.iso > Size: 591396864 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-Minimal-15 > 03.torrent > sha256sum: > 0b8482dc7e3076749f7fd914487ec6280539d3ba1f10c5b73c94b632f987f011 > > * CentOS-7-x86_64-DVD-1503.iso > Size: 4236247040 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-DVD-1503.t > orrent > sha256sum: > 1817a1689b3c646a6473c93012e06307c6b659000ccffd188a3f4d0a0b531ba9 > > * CentOS-7-x86_64-Everything-1503.iso > Size: 7517241344 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-Everything > - -1503.torrent > sha256sum: > 3cef58a3a03aff3ea194e63fdc95f03548b292e6f57e4a931a8d5453a6697661 > > * CentOS-7-x86_64-LiveGNOME-1503.iso > Size: 1124073472 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-LiveGNOME- > 1503.torrent > sha256sum: > 2cfc9fab2edb0be51b75ee63528b61cad79489129d2aad1713eeed1b4117ab47 > > * CentOS-7-x86_64-LiveKDE-1503.iso > Size: 1310720000 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-LiveKDE-15 > 03.torrent > sha256sum: > 6b2cd1c30092e9a141a458d40d0fcba74207b6c80e4f68dc7f800fbe1d7bae1b > > * CentOS-7-x86_64-LiveCD-1503.iso > Size: 729808896 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-LiveCD-150 > 3.torrent > sha256sum: > 96ee805573d0617ee11704e7973b55387adef13c6efdc82d50d287dba00dfaf1 > > * CentOS-7-x86_64-NetInstall-1503.iso > Size: 377487360 > Torrent: > http://mirror.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-NetInstall > - -1503.torrent > sha256sum: > 498bb78789ddc7973fe14358822eb1b48521bbaca91c17bd132c7f8c903d79b3 > > The iso files are also available for direct download from > http://mirror.centos.org/centos/7/isos/x86_64 > > * CentOS 7 1503 Docker Container: ' docker pull centos' will now give > you the 1503 container image. You can see the official CentOS Linux > container tags at : https://registry.hub.docker.com/_/centos/ > > - ---------- > Special Interest Groups > > The CentOS Linux distribution is built, managed, and released by the > CentOS Core SIG. In addition, we also have the following SIGs that are > doing an amazing job expanding and building on the base Linux platform: > > * Cloud SIG @ http://wiki.centos.org/SpecialInterestGroup/Cloud is > working to deliver various cloud controller infrastructure including > OpenStack. They have a fully functional, feature complete RDO stack > now available for testing with CentOS Linux 7 at > http://buildlogs.centos.org/centos/7/cloud/openstack-rdo/ > > * Cloud Instance SIG @ > http://wiki.centos.org/SpecialInterestGroup/CloudInstance aims to > deliver VM images for use in various cloud and virtualised ecosystems > including AWS ( > https://aws.amazon.com/marketplace/seller-profile?id=16cb8b03-256e-4dde- > 8f34-1b0f377efe89 > ) and Docker ( https://registry.hub.docker.com/_/centos/ ) > > * Virtualization SIG @ > http://wiki.centos.org/SpecialInterestGroup/Virtualization includes > upstream virtualization and hypervisor related projects including Xen > ( http://www.xenproject.org ), oVirt ( http://www.ovirt.org/ ), and > Docker ( http://docker.io ). They also work to build and release > support tools around these virtualization technologies. > > * Storage SIG @ http://wiki.centos.org/SpecialInterestGroup/Storage > includes the Gluster Project ( http://www.gluster.org/ ), Ceph ( > http://ceph.com ), OpenAFS ( http://www.openafs.org ) and the SCST > project ( http://scst.sourceforge.net/ ). Gluster builds for CentOS, > that track upstream community code are available for testing now at > http://buildlogs.centos.org/centos/7/storage/gluster/ > > * Software Collections SIG @ > http://wiki.centos.org/SpecialInterestGroup/SCLo is working on > documenting and then delivering software collections built for newer > versions of in-distro content. Their aim is to deliver a community and > contributor friendly mechanism for SCL's in an easy to consume format. > > * Atomic SIG @ http://wiki.centos.org/SpecialInterestGroup/Atomic is > working on building, maintaining, and delivering a CentOS Atomic host > ( http://projectatomic.io ). Testing and development builds including > AWS EC2 instances and Vagrant boxes are now available at > http://wiki.centos.org/SpecialInterestGroup/Atomic/Download > > In addition to these, the CentOS Artwork and CentOS Promo SIGs help > with promo content and helping organise Dojos around the world. > > SIGs are a great way for people to come together and deliver content > around a specific area into the wider CentOS ecosystem and we welcome > groups to come together with low barriers to entry and plenty of > resources to offer the groups. Details on the process can be found at > http://wiki.centos.org/SpecialInterestGroup > > - ---------- > Dojo > > We try and organise Dojos in various parts of the world as a one day > event, to bring together people who use CentOS and others who are keen > to learn about CentOS. The day's focus is on sharing technical > knowledge and success stories. It's also a great place to meet and > talk about upcoming technologies and learn how others are using them > on CentOS Linux. > > In the coming months we hope to host events in London, Bangalore, > Sweden, Germany, Spain, and in many parts of the USA. If you would > like to help organise a Dojo, do drop by the centos-promo list at > http://lists.centos.org/mailman/listinfo/centos-promo > > - ---------- > Getting Help > > The CentOS ecosystem is sustained by community driven help and > guidance. The best place to start for new users is at > http://wiki.centos.org/GettingHelp > > - ---------- > Contributors > > This release was made possible due to the hard work of many people, > foremost on that list are the Red Hat Engineers for producing a great > distribution, without them CentOS Linux would look very different. > > We are also looking for people to get involved with the QA process in > CentOS, if you would like to join this please introduce yourself on > the centos-devel list ( > http://lists.centos.org/mailman/listinfo/centos-devel ). > > > - ---------- > Thanks > > I would also like to thank our donors and sponsors for their continued > support for the project. And to everyone who contributed with ideas, > code, test feedback, and promoting CentOS Linux into the ecosystem. > > Enjoy! > > - -- > Karanbir Singh, Project Lead, The CentOS Project > +44-207-0094455 | http://www.centos.org/ | twitter.com/CentOS > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.14 (GNU/Linux) > > iQEcBAEBAgAGBQJVGsvBAAoJEI3Oi2Mx7xbt1xAH/0ZoWz65f/O8URzsleO4DaiD > Wy8YMWaPVTlLDnik7EukYSueT1bE9ziB3DxycQJVXz8HTABdjNugN6Ouy83bCY2a > 17t6F0VGY0ZRZe6Uqv8rb2xiFnFR/ssy9s921vJVcpzaSLgKl2/D5ed1aSsLaxLw > CdpYcC7t/8xbkpnCtoyQ2nko0Jzj8fYPr8wCUKTgnf0BXyXYYcuNsi+J6HKzlExc > KXHuvLDjXCjOVi4X7BLbn2F5N7bwBcmjYWC/hX1oAlD2uvbbNg/+mDbAu9QtWmeC > RthUq5uwpA05i9MvyMU5/ODS1NpIg3f+JybPLTp9zaFU6hXmJSvOR679wZbFdUc= > =Z60w > -----END PGP SIGNATURE----- > _______________________________________________ > CentOS-announce mailing list > CentOS-announce(a)centos.org > http://lists.centos.org/mailman/listinfo/centos-announce

26 93

Iptables config removed with 7.1 update
by Paul R. Ganci 04 Apr '15

04 Apr '15

I had turned off firewalld and was using iptables when I originally installed CentOS 7.0. Two days ago I upgraded my CentOS 7.0 to 7.1. Everything seemed to be fine. Today I discovered that my iptables configuration was removed with the update. Has anyone else experienced this on doing upgrade? Literally the /etc/sysconfig/iptables is gone and the /etc/sysconfig/iptables-config is the blank template that comes with the distribution. This seems to me to be a serious bug with the upgrade. -- Paul (ganci(a)nurdog.com) (303)257-5208

3 3

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64
by Always Learning 04 Apr '15

04 Apr '15

Posted on behalf of Mark (m.roth(a)5-cent.us) who is currently experiencing technical difficulties with his Internet connection --------------------------------- > On Fri, 2015-04-03 at 11:23 -0400, Lamar Owen wrote: > >> I really think that if someone is actually interested in helping the project, rather than being a backseat driver and griping at every change ........ Y'know, the whole thread with the naming, and the comments that it had been discussed, but only on the devel list, and the talk of an "ambassador" or whatever.... Couldn't some upcoming change like this have been mentioned in centos-announcements, and make sure it went to all the centos mailman lists? mark

3 2

CentOS-announce Digest, Vol 122, Issue 3
by centos-announce-request＠centos.org 04 Apr '15

04 Apr '15

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://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. Infra outage : bugs.centos.org (Fabian Arrotin) ---------------------------------------------------------------------- Message: 1 Date: Sat, 04 Apr 2015 12:01:35 +0200 From: Fabian Arrotin <arrfab(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] Infra outage : bugs.centos.org Message-ID: <551FB67F.9040305(a)centos.org> Content-Type: text/plain; charset=utf-8 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Due to a network routing issue happening outside of our infra, we have decided to migrate the CentOS bug tracker system (aka bugs.centos.org) to a new node today. Yesterday, around 2PM UTC, the company hosting the bugs.centos.org suffered from network connectivity loss (whole subnet not being routed/announced on bgp, etc ..). We've exchanged several phone calls to have an ETA, but it seems it was impossible to get any estimate. So, we decided to move the service to another node. (and service is now active). We had to restore the last good backup from that node, before machine was unreachable, so that means that we've lost some bug reports, and/or modified status/comments in the bug tracker. We're sorry for the inconvenience. on behalf of the Infra team, - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlUftn8ACgkQnVkHo1a+xU5K9QCfd+7l8ZE3e5+0SkJRlcxOeIe4 qtUAn1KY0zRuXfQzyWBvMbnV4CAspwwc =ySbp -----END PGP SIGNATURE----- ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 122, Issue 3 ***********************************************

1 0

← Newer
1
...
12
13
14
15
16
17
18
19
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss April 2015