<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>owncloud &#8211; FU-BAR</title>
	<atom:link href="/tag/owncloud/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>Fucked Up Beyond All Recognition</description>
	<lastBuildDate>Thu, 07 Aug 2014 22:42:22 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>/wp-content/uploads/2020/07/cropped-eu-header-20200715-2-32x32.png</url>
	<title>owncloud &#8211; FU-BAR</title>
	<link>/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Mind your webserver&#8217;s timeout! #owncloud</title>
		<link>/2014/08/07/mind-your-webservers-timeout-owncloud/</link>
		
		<dc:creator><![CDATA[Rui Seabra]]></dc:creator>
		<pubDate>Thu, 07 Aug 2014 22:41:45 +0000</pubDate>
				<category><![CDATA[Free Software]]></category>
		<category><![CDATA[owncloud]]></category>
		<guid isPermaLink="false">/?p=2369</guid>

					<description><![CDATA[When Owncloud 7.0.0 came out I tried to upgrade my 6.0.4 instance and failed miserably and silently. When 7.0.1 came out, the same thing happened, but this time I happened to notice the HTTP Result Code 502, timout&#8230; that was happenning in the frontend and not in the instance, for some reason I didn&#8217;t think &#8230; <p class="link-more"><a href="/2014/08/07/mind-your-webservers-timeout-owncloud/" class="more-link">Continue reading<span class="screen-reader-text"> "Mind your webserver&#8217;s timeout! #owncloud"</span></a></p>]]></description>
										<content:encoded><![CDATA[<p>When <a href="https://owncloud.org/">Owncloud</a> 7.0.0 came out I tried to upgrade my 6.0.4 instance and failed miserably and silently.</p>
<p>When 7.0.1 came out, the same thing happened, but this time I happened to notice the HTTP Result Code 502, timout&#8230; that was happenning in the frontend and not in the instance, for some reason I didn&#8217;t think of looking there first (maybe because I only did it very late both times).</p>
<p>So I increased Apache&#8217;s TimeOut directive to a safe 900 seconds and now everything went fine.</p>
<p>Meanwhile, Björn Schießle from Owncloud gave me a very nice tip, for those who control the server and can ssh into it, one can do the upgrade with:</p>
<blockquote><p>./occ upgrade</p></blockquote>
<p>So there you go, nice and useful tips, two in one post. <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
