[Valid RSS] This is a valid RSS feed.


This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.


  1. <?xml version="1.0" encoding="utf-8"?>
  3.  <?xml-stylesheet type="text/xsl" href="/style/rss.en.xsl"?>
  4.  <?xml-stylesheet type="text/css" href="/style/rss.css"?><rss version="2.0" xmlns:blogChannel="">
  5.  <channel>
  6.    <title>Sotirov-BG.Net News</title>
  7.    <link></link>
  8.    <description>News from Sotirov-BG.Net</description>
  9.    <language>en</language>
  10.    <copyright>Copyright (c) 2004-2020 Georgi D. Sotirov</copyright>
  11.    <pubDate>Sun, 17 Dec 2017 20:10:15 GMT</pubDate>
  12.    <lastBuildDate>Sun, 17 Dec 2017 20:10:15 -0000</lastBuildDate>
  13.    <managingEditor>[email protected] (Georgi D. Sotirov)</managingEditor>
  14.    <webMaster>[email protected] (Georgi D. Sotirov)</webMaster>
  15.    <generator>Perl 5.022002</generator>
  16.    <image>
  17.      <title>Sotirov-BG.Net News</title>
  18.      <url></url>
  19.      <link></link>
  20.    </image>
  21.    <item>
  22.      <title>Inaccessibility due to router replacement</title>
  23.      <link></link>
  24.      <description>&lt;p>Today between 12:30 &lt;a href="">
  25. &lt;abbr title="Eastern European Time">EET&lt;/abbr>&lt;/a> and 14:30 &lt;a
  26. href="">&lt;abbr
  27. title="Eastern European Time">EET&lt;/abbr>&lt;/a> the server was not accessible
  28. due to router replacement and change of &lt;abbr title="Internet Protocol">IP&lt;/abbr>
  29. addresses. Although, the replacement was planned and prepared previously, some
  30. unforeseen circumstances occurred with the configuration of the device itself
  31. as well as with the server.&lt;/p>
  32. &lt;p>The expected change with the replacement is better network performance for
  33. the increasing outer and inner traffic.&lt;/p></description>
  34.      <author>[email protected] (Georgi Sotirov)</author>
  35.      <guid isPermaLink="true"></guid>
  36.      <pubDate>Sun, 17 Dec 2017 20:10:15 GMT</pubDate>
  37.    </item>
  38.    <item>
  39.      <title>Downtime for disk replace</title>
  40.      <link></link>
  41.      <description>&lt;p>Last night while &lt;a hreflang="bg" href="">all
  42. students were celebrating&lt;/a>, I spent replacing a failing &lt;a
  43. href="">Samsung
  44. 830&lt;/a>&amp;nbsp;&lt;abbr title="Solid State Drive">SSD&lt;/abbr> on the server.
  45. The disk was so rotten that it's copy with &lt;code>dd&lt;/code> took about 5 hours,
  46. which is why the server was offline somewhere between 2017-12-08 22:00 &lt;a
  47. href="">&lt;abbr
  48. title="Eastern European Time">EET&lt;/abbr>&lt;/a> and 2017-12-09 05:00 &lt;a
  49. href="">&lt;abbr
  50. title="Eastern European Time">EET&lt;/abbr>&lt;/a>. The disk started failing in
  51. beginning of September, but recently the number of reallocated sectors become
  52. extremely high and I started detecting bad sectors on some system files. The
  53. read performance had also dropped and during the copy it fell to 5 &lt;abbr
  54. title="Mega Bytes per second">MB/s&lt;/abbr> (!), which explains the fore
  55. mentioned slow copy of just 64 &lt;abbr title="Giga Bytes">GB&lt;/abbr> between
  56. the old and new &lt;abbr title="Solid State Drive">SSD&lt;/abbr>. The disk
  57. failed only after about 24 000 power on hours (i.e. about 2 years and 9 months),
  58. which is rather strange, but maybe this is the normal life span of consumer
  59. &lt;abbr title="Solid State Drive">SSD&lt;/abbr>s?&lt;/p>
  60. &lt;p>Anyway, the drive is now replaced with a brand new &lt;a href="">ADATA SU800&lt;/a>
  61. 128 &lt;abbr title="Giga Bytes">GB&lt;/abbr>, which unfortunately is not yet in
  62. &lt;code>smartctl&lt;/code> database (see &lt;a href="">ticket 954&lt;/a>).
  63. The server is back online and fully operational.&lt;/p></description>
  64.      <author>[email protected] (Georgi Sotirov)</author>
  65.      <guid isPermaLink="true"></guid>
  66.      <pubDate>Sat, 09 Dec 2017 04:01:15 GMT</pubDate>
  67.    </item>
  68.    <item>
  69.      <title>Upgrade to Slackware 14.2</title>
  70.      <link></link>
  71.      <description>&lt;p>Last Sunday (28/08) the server was upgraded to &lt;a href="">Slackware&lt;/a>
  72. 14.2, which itself passed flawlessly, but then there was a need for re-install
  73. of all the additionally used Perl modules and upgrade of some packages (e.g. &lt;a
  74. href=";amp;slack=142&amp;amp;latestonly=1">OpenLDAP&lt;/a>,
  75. &lt;a href=";amp;slack=142&amp;amp;latestonly=1">RRDTool&lt;/a> and
  76. &lt;a href=";amp;slack=142&amp;amp;latestonly=1">FreeRadius&lt;/a>),
  77. which I haven't upgraded/rebuilt yet.&lt;/p>
  78. &lt;p>Yesterday, evening the datbase server was also upgraded to MySQL 5.7.13, so
  79. it now remains only to upgrade the kernel to a &lt;abbr title="Long Term Support">LTS&lt;/abbr>
  80. version from 4.4 series.&lt;/p></description>
  81.      <author>[email protected] (Georgi Sotirov)</author>
  82.      <guid isPermaLink="true"></guid>
  83.      <pubDate>Tue, 30 Aug 2016 09:34:17 GMT</pubDate>
  84.    </item>
  85.    <item>
  86.      <title>ISP Change</title>
  87.      <link></link>
  88.      <description>&lt;p>Last week the server was not accessible from 2015-07-14 21:20 &lt;a
  89. href="">&lt;abbr
  90. title="Eastern European Summer Time">EEST&lt;/abbr>&lt;/a> to 2015-07-16 16:35 &lt;a
  91. href="">&lt;abbr
  92. title="Eastern European Summer Time">EEST&lt;/abbr>&lt;/a>, because my &lt;abbr
  93. title="Internet Services Provider">ISP&lt;/abbr> &lt;a href="">MTel&lt;/a>
  94. (that bought &lt;a href="">Megalan&lt;/a> few years ago) was
  95. having problems with managing &lt;abbr title="Media Access Control">MAC&lt;/abbr>
  96. addresses and Layer 2 connectivity (i.e. as far as I understood it was due to
  97. some "provisioning"). No matter the case, I found it &lt;strong>totally
  98. unacceptable&lt;/strong> to be without Internet for almost 48 hours given there
  99. was no physical disruption of the connection. Mtel's support was not able to do
  100. anything to help me restore the connection (I was required to pass the so
  101. called "Captive Portal" even though it was clear that I'm not able to do so
  102. because of the issues on Mtel's side).&lt;/p>
  103. &lt;p>So I changed the &lt;abbr title="Internet Service Provider">ISP&lt;/abbr> last
  104. Friday (17.07) and I'm now with &lt;a href="">Vivacom&lt;/a>
  105. hopefully for the better. Of course the new &lt;abbr title="Internet Service Provider">ISP&lt;/abbr>
  106. come with the new static &lt;abbr title="Internet Protocol">IP&lt;/abbr> address
  107. (, so the server was not accessible also over the weekend until
  108. the &lt;abbr title="Domain Name Service">DNS&lt;/abbr>es were synchronized.&lt;/p></description>
  109.      <author>[email protected] (Georgi Sotirov)</author>
  110.      <guid isPermaLink="true"></guid>
  111.      <pubDate>Mon, 20 Jul 2015 16:43:15 GMT</pubDate>
  112.    </item>
  113.    <item>
  114.      <title>Upgrade to Slackware 14.0</title>
  115.      <link></link>
  116.      <description>&lt;p>In the evening of February 3-d and the morning of February 4-th the operating
  117. system of the server was finally upgraded to &lt;a href="">Slackware&lt;/a>
  118. 14.0 - an upgrade planned for the past several months, but delayed due to lack
  119. of time.&lt;/p>
  120. &lt;p>The major problems were again with Perl. All of the used modules by the
  121. different web application had to be reinstalled for the new version. Otherwise, the
  122. upgrade went smoothly, but it took some time for the whole process to complete
  123. and all the services to be reconfigured and become operational again.&lt;/p>
  124. </description>
  125.      <author>[email protected] (Georgi Sotirov)</author>
  126.      <guid isPermaLink="true"></guid>
  127.      <pubDate>Tue, 05 Feb 2013 10:15:15 GMT</pubDate>
  128.    </item>
  129.    <item>
  130.      <title>Downtimes: Repairs at home</title>
  131.      <link></link>
  132.      <description>&lt;p>Due to repairs at home (where it is still located), the server may be going
  133. down for large periods of time varying from several hours to more than 1 day.
  134. It was already down once from 2012-06-15 11:54 &lt;abbr title="Eastern European
  135. Summer Time">EEST&lt;/abbr> to 2012-06-15 12:54 &lt;abbr title="Eastern European
  136. Summer Time">EEST&lt;/abbr> and from 2012-06-15 18:50 &lt;abbr title="Eastern
  137. European Summer Time">EEST&lt;/abbr> to 2012-06-16 21:45 &lt;abbr title="Eastern
  138. European Summer Time">EEST&lt;/abbr> yesterday, but other downtimes are possible
  139. today and tomorrow.&lt;/p></description>
  140.      <author>[email protected] (Georgi Sotirov)</author>
  141.      <guid isPermaLink="true"></guid>
  142.      <pubDate>Sun, 17 Jun 2012 06:00:00 GMT</pubDate>
  143.    </item>
  144.    <item>
  145.      <title>Upgrade of the server</title>
  146.      <link></link>
  147.      <description>&lt;p>Last evening the server was upgraded to &lt;a href="">Slackware 13.37&lt;/a>,
  148. this way updating many of the existing packages. The only problem that was
  149. encountered was with Perl 5.12 on which both &lt;a href="">Bugzilla&lt;/a>
  150. and &lt;a href="">SlackPack&lt;/a> depend. This
  151. forced the downgrade to Perl 5.10 and use of the existing base of installed
  152. packages until solutions to &lt;a href="">the
  153. problems are found&lt;/a>.&lt;/p>
  154. &lt;p>The kernel was also upgraded to 2.6.39 without any problem.&lt;/p></description>
  155.      <author>[email protected] (Georgi Sotirov)</author>
  156.      <guid isPermaLink="true"></guid>
  157.      <pubDate>Mon, 30 May 2011 09:42:15 GMT</pubDate>
  158.    </item>
  159.    <item>
  160.      <title>Planned downtime: Earth hour</title>
  161.      <link></link>
  162.      <description>&lt;p>For first time this year Sotirov-BG.Net will took part in the
  163. &lt;a href="">Earth Hour&lt;/a> initiative to
  164. show support against climate and environment change. Today
  165. between 20:30 &lt;abbr title="Eastern European Time">EET&lt;/abbr>
  166. and 21:30 &lt;abbr title="Eastern European Time">EET&lt;/abbr> the
  167. server, as well as other equipment around it, would be switched
  168. off. Please, do not forget to join the initiative and think what else
  169. could you do to help.&lt;/p></description>
  170.      <author>[email protected] (Georgi Sotirov)</author>
  171.      <guid isPermaLink="true"></guid>
  172.      <pubDate>Sat, 26 Mar 2011 17:07:59 GMT</pubDate>
  173.    </item>
  174.    <item>
  175.      <title>Database upgrade</title>
  176.      <link></link>
  177.      <description>&lt;p>Today, between 17:00 EEST and 19:00 EEST there was database upgrade. The MySQL
  178. server was moved to the recommended release series 5.1. This was a planned
  179. upgrade, but it took time, because of incompatible changes, which required
  180. backup/restore of all the databases. Now everything is back to norml.&lt;/p></description>
  181.      <author>[email protected] (Georgi Sotirov)</author>
  182.      <guid isPermaLink="true"></guid>
  183.      <pubDate>Mon, 24 May 2010 16:24:00 GMT</pubDate>
  184.    </item>
  185.    <item>
  186.      <title>Database problems</title>
  187.      <link></link>
  188.      <description>&lt;p>Yesterday, about midnight the MySQL was upgraded and during the night backup the server was restarted.
  189. However, the InnoDB engine failed to start properly, because of inability to create temporary files (not an
  190. issue before). Thus, hosted sites were without data from about 0:15 to about 11:00 on 21 October 2008,
  191. when the problem was resolved.&lt;/p>
  192. &lt;p>I'm sorry, if this caused any inconvenience.&lt;/p></description>
  193.      <author>[email protected] (Georgi Sotirov)</author>
  194.      <guid isPermaLink="true"></guid>
  195.      <pubDate>Tue, 21 Oct 2008 09:53:01 GMT</pubDate>
  196.    </item>
  197.  </channel>
  198. </rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda