<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Issue on ftp.fau.de news and statistics</title>
		<link>https://ftp.fau.de/news/tags/issue/</link>
		<description>Recent content in Issue on ftp.fau.de news and statistics</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 17 Jul 2026 11:27:17 +0200</lastBuildDate>
		
			<atom:link href="https://ftp.fau.de/news/tags/issue/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Problems with Opensuse Mirror</title>
				<link>https://ftp.fau.de/news/posts/problems-with-opensuse-mirror/</link>
				<pubDate>Fri, 17 Jul 2026 11:27:17 +0200</pubDate>
				<guid>https://ftp.fau.de/news/posts/problems-with-opensuse-mirror/</guid>
				<description>&lt;p&gt;There are currently problems with our mirror of opensuse.&lt;/p&gt;&#xA;&lt;p&gt;Since June 08, it has been having problems staying up-to-date.&lt;/p&gt;&#xA;&lt;p&gt;This is caused by infrastructure problems on opensuses end - their main upstream server delivers abysmal transfer rates to us. Unfortunately, transfer rates of about 2 Megabytes per second are not really enough to keep in sync with the rate of changes that opensuse has.&lt;/p&gt;&#xA;&lt;p&gt;We have tried to mitigate the situation by pulling updates from other sources, but these are incomplete.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Unplanned Outage on June 03 [solved]</title>
				<link>https://ftp.fau.de/news/posts/unplanned-outage-on-june-03-2020/</link>
				<pubDate>Thu, 04 Jun 2020 20:40:00 +0200</pubDate>
				<guid>https://ftp.fau.de/news/posts/unplanned-outage-on-june-03-2020/</guid>
				<description>&lt;p&gt;On June 03, 2020, at around 16:15 local time (14:15 UTC), disk accesses on ftp.fau.de became extremely slow. Less than an hour later, any attempts to access the disks with the ftp-data on it failed. Investigation revealed that the big RAID controller that manages all the external disk enclosures for the data had stopped responding completely.&#xA;While the failed controller could temporarily be brought back by a powercycle at around 18:00 local time (16:00 UTC), it failed again within 10 minutes of booting the machine.&#xA;Unfortunately, there was no compatible replacement for the failed controller onsite. A replacement has been ordered and shipped, but has not arrived yet. As all parcel services are severely overloaded due to the Corona crisis, it is currently unclear when it will arrive.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
