<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>spacewalk on David Hrbáč</title>
    <link>https://www.hrbac.cz/tags/spacewalk/</link>
    <description>Recent content in spacewalk on David Hrbáč</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 01 Jun 2017 07:02:03 +0000</lastBuildDate><atom:link href="https://www.hrbac.cz/tags/spacewalk/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Proper way to delete channel, repository, packages in Spacewalk</title>
      <link>https://www.hrbac.cz/2017/06/proper-way-to-delete-channel-repository-packages-in-spacewalk/</link>
      <pubDate>Thu, 01 Jun 2017 07:02:03 +0000</pubDate>
      
      <guid>https://www.hrbac.cz/2017/06/proper-way-to-delete-channel-repository-packages-in-spacewalk/</guid>
      
      <description>This is the way to remove the channel together with repository. It will also remove the packages from the file system. The workflow is as follows:
remove subchannels and master channel remove repos remove orphan packages sync/clean up file system with Spacewalk DB records remove broken links to RPM packages (optional) You can remove channels and repos within GUI. You can also perform it all on command line:
spacecmd softwarechannel\delete \channel\name\ spacecmd repo\delete \reponame\name\ spacecmd package\removeorphans spacewalk-data-fsck -r -S -C -O find /srv/satellite/rpms/ -xtype l -delete Comments: Managing Spacewalk Repos – A Place To Put Stuff - Jan 3, 2018</description>
      
    </item>
    
    <item>
      <title>Spacewalk not responding - &#34;Starting tomcat6: Error code 4&#34;</title>
      <link>https://www.hrbac.cz/2013/12/spacewalk-not-responding-starting-tomcat6-error-code-4/</link>
      <pubDate>Tue, 10 Dec 2013 14:25:46 +0000</pubDate>
      
      <guid>https://www.hrbac.cz/2013/12/spacewalk-not-responding-starting-tomcat6-error-code-4/</guid>
      
      <description>In case you see &amp;ldquo;Starting tomcat6: Error code 4&amp;rdquo;, make sure you have some free space on the file system&amp;hellip;
Comments: Tomáš Kašpárek - Mar 2, 2014
You can actually get this error any time even you have plenty of free space, following helps all the time rm /var/lock/subsys/tomcat6 rm /var/run/tomcat6.pid service tomcat6 start</description>
      
    </item>
    
  </channel>
</rss>
