Meeting Agenda Item: Introduction Sebastian Borza (sebito91)
by Sebastian Borza
Hi team,
Really excited to get started within the community! I'm a Systems
Administrator based in NYC with a strong background in C and Python
programming, and I'm interested in all things metrics to support a
Production environment.
Current interests/projects include graphite-web, grafana, collectd,
opentsdb and tcollector amongst others. Also quite familiar with nagios +
icinga, as well as loadbalancers with HAProxy and keepalived.
If there's space, I'd love to join the team to help with any metrics
analysis requirements or just to help out in general.
See you all Thursday,
Sebastian
9 years, 6 months
Freeze break request: disable nagios event_handler for fedora-tagger
by Ralph Bean
Tagger started acting up recently and responding very slowly. Longer
term, I think this is due to the database outgrowing our original
expectations for it -- a "select count(*) from votes;" takes quite a
while to return on the db server.
This slowness is causing nagios to time out every now and then which
makes it then try to restart httpd to get things working again (and
notify us about this).
To cut down on spam, I'd just like to remove the event_handler with
the following patch. Any +1s?:
---
.../files/nagios/services/websites.cfg | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/roles/nagios_server/files/nagios/services/websites.cfg b/roles/nagios_server/files/nagios/services/websites.cfg
index c52c167..9595b3d 100644
--- a/roles/nagios_server/files/nagios/services/websites.cfg
+++ b/roles/nagios_server/files/nagios/services/websites.cfg
@@ -95,7 +95,7 @@ define service {
check_command check_website!localhost!/tagger/!Tagger
max_check_attempts 8
use internalwebsitetemplate
- event_handler restart_httpd
+ #event_handler restart_httpd
}
define service {
--
1.7.2.1
9 years, 6 months
bastion.fedoraproject.org sshd key changed ?
by Fabian Arrotin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I need to access a host in PHX2, so using bastion.fedoraproject.org as
a jump host.
It seems that the fingerprint for host key changed to
70:12:01:af:cc:8d:5b:65:a5:cb:79:1b:6e:03:65:b0.
Can someone confirm that and also, is that possible to get
notification about those kind of changes ? (or maybe that's a failover
host, but I'm not aware of that)
Feel free to point me to a more relevant list than infrastructure, it
that was not the correct one to use.
Kind Regards,
- --
Fabian Arrotin
gpg key: 56BEC54E | twitter: @arrfab
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlRLT9QACgkQnVkHo1a+xU6S/wCfeaq6NKyMEV+LqOTk8sGEuquD
VikAnjkIT2YWfk/lIw1OIJAAY7iUy46n
=t1wu
-----END PGP SIGNATURE-----
9 years, 6 months
Plan for tomorrow's Fedora Infrastructure meeting (2014-10-23)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2014-10-16 at 18:00 UTC in #fedora-meeting on the freenode network.
Suggested topics:
#topic New folks introductions and Apprentice tasks.
If any new folks want to give a quick one line bio or any apprentices
would like to ask general questions, they can do so in this part of the
meeting. Don't be shy!
#topic Freeze reminder
Just a reminder that we are in Beta freeze.
#topic Applications status / discussion
Check in on status of our applications: pkgdb, fas, bodhi, koji,
community, voting, tagger, packager, dpsearch, etc.
If there's new releases, bugs we need to work around or things to note.
#topic Sysadmin status / discussion
Here we talk about sysadmin related happenings from the previous week,
or things that are upcoming.
#topic nagios/alerts recap
Here we go over the last weeks alerts and see if we can find ways to
make it so they don't happen again.
#topic Upcoming Tasks/Items
https://apps.fedoraproject.org/calendar/list/infrastructure/
#topic Open Floor
Submit your agenda items, as tickets in the trac instance and send a
note replying to this thread.
More info here:
https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings
Thanks
kevin
9 years, 6 months
[release] Anitya 0.1.13
by Pierre-Yves Chibon
Hi all,
I have just rolled out a new release of Anitya, here is the changelog:
* Thu Oct 23 2014 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.13
- Update to 0.1.13
- Add a keyboard shortcut on `c` to check the version
- Log the error when calling a certain website of a project and something
goes wrong
- Support filtering by project name and log when viewing the list of project
that failed to update at the last cron run
- Add a way to find the projects that simply never updated
With the later two, I can now find all the projects that failed to update (or
never did) while using github:
https://release-monitoring.org/projects/updates/failed?log=github
https://release-monitoring.org/projects/updates/never_updated?log=github
Then I can go through them one by one and fix them, most of the time either the
backend is incorrect or the url is using http:// instead of https://.
There were 75 of such projects after the update, I'm already down to 26.
Pierre
9 years, 6 months
[release] Anitya 0.1.12
by Pierre-Yves Chibon
Hi everyone,
I just pushed a new version of anitya and here is its changelog:
* Wed Oct 22 2014 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.12
- Update to 0.1.12
- Update the project's log if we retrieved an update w/o problems
- Add log handler on the cron job to monitor its progress
- Handle the situation where the folder backend is used against a FTP source
- Document a way to test a regular expression for anitya
- Update the sourceforge url to use the new one
- Escape the '+' symbols in the name of the projects in the regular expression
Have a nice day,
Pierre
9 years, 6 months
