<?xml version='1.0' encoding='utf-8' ?>
<!--  If you are running a bot please visit this policy page outlining rules you must respect. http://www.livejournal.com/bots/  -->
<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:media='http://search.yahoo.com/mrss/' xmlns:atom10='http://www.w3.org/2005/Atom'>
<channel>
  <title>Journal for the Camarilla Servers</title>
  <link>http://cam-servers.livejournal.com/</link>
  <description>Journal for the Camarilla Servers - LiveJournal.com</description>
  <lastBuildDate>Fri, 01 Jul 2005 23:02:43 GMT</lastBuildDate>
  <generator>LiveJournal / LiveJournal.com</generator>
  <lj:journal>cam_servers</lj:journal>
  <lj:journalid>4471933</lj:journalid>
  <lj:journaltype>personal</lj:journaltype>
  <atom10:link rel='hub' href='http://pubsubhubbub.appspot.com/' />
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/8562.html</guid>
  <pubDate>Fri, 01 Jul 2005 23:02:43 GMT</pubDate>
  <title>mail (final update for this particular instance)</title>
  <link>http://cam-servers.livejournal.com/8562.html</link>
  <description>mail is flying out of the box like there&apos;s no tomorrow.  Once it cleans up a bit, I&apos;m gona stop it for long enough to fix a few more things.  I know a few of you wanted mail though...so there it is!</description>
  <comments>http://cam-servers.livejournal.com/8562.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>2</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/8399.html</guid>
  <pubDate>Fri, 01 Jul 2005 20:59:22 GMT</pubDate>
  <title>a good update!</title>
  <link>http://cam-servers.livejournal.com/8399.html</link>
  <description>ok, so it&apos;s on a livecd now.  Unfortunately, if I merely fixed it, that wouldn&apos;t be enough since there is a cd in the drive!  I can eject it, but if I reboot to run off the system itself (instead of the cd) then when the system is coming up, it will close the cd drive bay, and boot from the cd again.  Only, no one will be there to get it on the network, and start sshd...&lt;br /&gt;&lt;br /&gt;So here&apos;s what I now have to do:&lt;br /&gt;&lt;li&gt; fix it&lt;br /&gt;&lt;li&gt; get all services working off the kernel booted from the cdrom&lt;br /&gt;&lt;li&gt; do item2 while making it such that once the system is rebooted without that cd, it will work&lt;br /&gt;&lt;br /&gt;tada!  No worries, I&apos;ve done it before.  Actually, will be welcome, since this means I can do some hard-core scrubbing on the real / and /usr filesystems (since they aren&apos;t even mounted)&lt;br /&gt;&lt;br /&gt;going to try for getting it done tonight.  I had other plans, but you all make me feel so loved I just thought, eh!  Why not!  ;)</description>
  <comments>http://cam-servers.livejournal.com/8399.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>6</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/8109.html</guid>
  <pubDate>Fri, 01 Jul 2005 01:37:37 GMT</pubDate>
  <title>an update!</title>
  <link>http://cam-servers.livejournal.com/8109.html</link>
  <description>some of you may not be aware, but yes - cammail is still down!  It can&apos;t come up enough for me to get it back.  All I need is a shell...&lt;br /&gt;&lt;br /&gt;tomorrow, I&apos;m going to walk WW through getting a livecd working enough to get me back on the box, even if it means I won&apos;t be on the box&apos;s native kernel.  So hopefully, tomorrow, it will be back.&lt;br /&gt;&lt;br /&gt;All from a power loss that lasted overnight, or at least several hours?  So in this case, a UPS wouldn&apos;t have helped.</description>
  <comments>http://cam-servers.livejournal.com/8109.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>33</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/7892.html</guid>
  <pubDate>Tue, 28 Jun 2005 22:10:56 GMT</pubDate>
  <title>yes - we know (cammail)</title>
  <link>http://cam-servers.livejournal.com/7892.html</link>
  <description>electricity.&lt;br /&gt;&lt;br /&gt;Sounds repetitive, I know.  Apparently it&apos;s down hard, and isn&apos;t coming back up happily.&lt;br /&gt;&lt;br /&gt;And I thought I didn&apos;t have anything to do tonight...</description>
  <comments>http://cam-servers.livejournal.com/7892.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>13</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/7503.html</guid>
  <pubDate>Fri, 24 Jun 2005 22:57:51 GMT</pubDate>
  <title>mailman on the web</title>
  <link>http://cam-servers.livejournal.com/7503.html</link>
  <description>up!  was just messing with various things.  Lemme know about any mailman problems you see now.</description>
  <comments>http://cam-servers.livejournal.com/7503.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>1</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/7199.html</guid>
  <pubDate>Fri, 24 Jun 2005 15:38:44 GMT</pubDate>
  <title>updates and features</title>
  <link>http://cam-servers.livejournal.com/7199.html</link>
  <description>an update about the server move and some additional features.&lt;br /&gt;&lt;br /&gt;Server Move:&lt;br /&gt;&lt;li&gt;Rate of issues has slowed down a little... I&apos;m trying to keep up and get them fixed as soon as possible, but I need lots of information from all of you who log issues. &lt;br /&gt;&lt;li&gt;I&apos;m going to be spending a lot of time this weekend fixing issues (my girlfriend is out of town)... so if there are things you know are broken but haven&apos;t logged, do so now. &lt;br /&gt;&lt;li&gt;Log issues at &lt;a href=&quot;http://camarilla.white-wolf.com/bugs/&quot;&gt;http://camarilla.white-wolf.com/bugs/&lt;/a&gt;&lt;br /&gt;&lt;li&gt;I know bunches of people have the wrong (or weirdly formatted) cam number in the approvals database (or didnt have their second or third account linked). I can correct these, but I need you to log your current (linked) cam number and your old approvals login name in the bug request. &lt;br /&gt;&lt;br /&gt;New features:&lt;br /&gt;&lt;li&gt;I know several people have had some tribulations importing data to the prestige system. Because of this, I&apos;ve added a step to the import where you verify your entries before they get written to the database. You have to answer the question at the bottom for the import to actually do anything.&lt;br /&gt;&lt;li&gt;Also, some people have requested the ability to attach full emails, large details to prestige. I&apos;ve added a &quot;detailed notes&quot; section that you can reach by editing your prestige. When values are added to this field, it addes a new link in the notes section to show the full details of the entry. This field is limited to 4,294,967,296 characters... so try and be brief :)&lt;br /&gt;&lt;li&gt;Since formatting would be impossible you can&apos;t import detailed notes, you&apos;ll have to add them after the import... sorry.&lt;br /&gt;&lt;br /&gt;There&apos;s much much more... but I&apos;m getting long winded...&lt;br /&gt;&lt;br /&gt;Thanks for bearing with me, soon this will all be fun to look back on...</description>
  <comments>http://cam-servers.livejournal.com/7199.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>4</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/6969.html</guid>
  <pubDate>Thu, 16 Jun 2005 02:15:27 GMT</pubDate>
  <title>camarilla server move... complete</title>
  <link>http://cam-servers.livejournal.com/6969.html</link>
  <description>If you haven&apos;t noticed yet, camarilla.white-wolf.com has completed it&apos;s move.&lt;br /&gt;&lt;br /&gt;Please remember you need to link your White Wolf account to your Cam Membership by going to &lt;a href=&quot;http://www.white-wolf.com/camimport.php&quot;&gt;http://www.white-wolf.com/camimport.php&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Once that&apos;s done, you can use most of the features on the site that require a login.&lt;br /&gt;&lt;br /&gt;Please log issues to &lt;a href=&quot;http://camarilla.white-wolf.com/bugs&quot;&gt;http://camarilla.white-wolf.com/bugs&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;And please be gentle, the CRD (&lt;a href=&quot;http://camarilla.white-wolf.com/crd/&quot;&gt;http://camarilla.white-wolf.com/crd/&lt;/a&gt;) replaces the member database (and adds some new functionality, too).</description>
  <comments>http://cam-servers.livejournal.com/6969.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/6673.html</guid>
  <pubDate>Thu, 16 Jun 2005 02:11:51 GMT</pubDate>
  <title>server update</title>
  <link>http://cam-servers.livejournal.com/6673.html</link>
  <description>If it makes people feel better, I (me, not Brent) had to do this too, and was apprehensive...but it worked, and was simple.  :)&lt;br /&gt;&lt;br /&gt;----------&lt;br /&gt;Ladies and Gentlemen,&lt;br /&gt;&lt;br /&gt;As you may or may not have heard (or noticed), the new server came online&lt;br /&gt;tonight.&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://camarilla.white-wolf.com&quot;&gt;http://camarilla.white-wolf.com&lt;/a&gt; now will bring you to a new location with some&lt;br /&gt;new features.&lt;br /&gt;&lt;br /&gt;I&apos;ll let everyone explore for the most part, but there are a few things you need&lt;br /&gt;to know...&lt;br /&gt;&lt;br /&gt;1) In order to use most services on the new system you will need to link your&lt;br /&gt;cam number to your White Wolf account.&lt;br /&gt;&lt;br /&gt;To do this, first make sure you have signed up for a White Wolf account at&lt;br /&gt;&lt;a href=&quot;http://www.white-wolf.com&quot;&gt;http://www.white-wolf.com&lt;/a&gt; and are able to log into it. Once you have  an account&lt;br /&gt;go to &lt;a href=&quot;http://www.white-wolf.com/camimport.php&quot;&gt;http://www.white-wolf.com/camimport.php&lt;/a&gt; to link your Cam Number to your&lt;br /&gt;account. You will need to know the login password you used in the old member&lt;br /&gt;system to link this.&lt;br /&gt;&lt;br /&gt;Once you have linked your Cam Account and your White Wolf account, you should be&lt;br /&gt;able to access most items on the Camarilla system by logging into your White&lt;br /&gt;Wolf account.&lt;br /&gt;&lt;br /&gt;2) The old ccdb / member database has been replaced by the CRD. The new link is&lt;br /&gt;&lt;a href=&quot;http://camarilla.white-wolf.com/crd&quot;&gt;http://camarilla.white-wolf.com/crd&lt;/a&gt; . Please explore... but also give us some&lt;br /&gt;slack... it&apos;s new.&lt;br /&gt;&lt;br /&gt;3) To log issues against the CRD (or any of the tech services) please use the&lt;br /&gt;new bug tracking system, Mantis. It is available by going to&lt;br /&gt;&lt;a href=&quot;http://camarilla.white-wolf.com/bugs&quot;&gt;http://camarilla.white-wolf.com/bugs&lt;/a&gt; . The login for this is seperate from your&lt;br /&gt;Camarilla/White Wolf login for 2 reasons... it&apos;s a third party piece of software&lt;br /&gt;and you can log issues anonymously if you like.&lt;br /&gt;&lt;br /&gt;Thanks... and enjoy the new functionality.&lt;br /&gt;&lt;br /&gt;~brent cerrato&lt;br /&gt;US-NTA&lt;br /&gt;US2002022439</description>
  <comments>http://cam-servers.livejournal.com/6673.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>3</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/6475.html</guid>
  <pubDate>Tue, 07 Jun 2005 21:49:45 GMT</pubDate>
  <title>server being transitioned</title>
  <link>http://cam-servers.livejournal.com/6475.html</link>
  <description>cam1/camarilla/ol&apos; rattler has started &lt;a href=&quot;http://camarilla.white-wolf.com/menatwork.html&quot;&gt; its transition.&lt;/a&gt;  The approvals db, amoung other things, is now offline.  All logins (sans 2) are now offline.  The only thing remaining is content under /mst (or /MST) and only because I threatened to shoot &lt;span class=&apos;ljuser  ljuser-name_methuse&apos; lj:user=&apos;methuse&apos; style=&apos;white-space: nowrap;&apos;&gt;&lt;a href=&apos;http://methuse.livejournal.com/profile&apos;&gt;&lt;img src=&apos;http://l-stat.livejournal.com/img/userinfo.gif&apos; alt=&apos;[info]&apos; width=&apos;17&apos; height=&apos;17&apos; style=&apos;vertical-align: bottom; border: 0; padding-right: 1px;&apos; /&gt;&lt;/a&gt;&lt;a href=&apos;http://methuse.livejournal.com/&apos;&gt;&lt;b&gt;methuse&lt;/b&gt;&lt;/a&gt;&lt;/span&gt; if he forced me to take it down...in the end, I decided to just pay him $6 BILLION dollars.  Approvals are one thing, but someone might have an actual rules debate tonight or something.  They need the rules to be up.&lt;br /&gt;&lt;br /&gt;Anyway, wave goodbye...will be back soon.</description>
  <comments>http://cam-servers.livejournal.com/6475.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>14</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/6343.html</guid>
  <pubDate>Tue, 31 May 2005 13:11:45 GMT</pubDate>
  <title>mailman updates!</title>
  <link>http://cam-servers.livejournal.com/6343.html</link>
  <description>Mailman should be happy now; if you are still having problems, leave us a note here or contact any of us through the chain.&lt;br /&gt;&lt;br /&gt;/var had finally had enough, and thought it was allowing some writes, it was no longer stable.  It also was beyond repair, so I had to restore and replace it.  &lt;br /&gt;&lt;br /&gt;I&apos;ll put a redirect back up so that &lt;a href=&quot;http://cammail.white-wolf.com&quot;&gt; cammail.white-wolf.com&lt;/a&gt; automatically goes to &lt;a href=&quot;http://cammail.white-wolf.com/mailman/listinfo&quot;&gt; cammail.white-wolf.com/mailman/listinfo&lt;/a&gt; but beyond that, all should be avail.  If you don&apos;t see something in the archive, and you never saw it on the list, then resend it; it didn&apos;t get through.</description>
  <comments>http://cam-servers.livejournal.com/6343.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>3</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/6056.html</guid>
  <pubDate>Tue, 31 May 2005 11:17:51 GMT</pubDate>
  <link>http://cam-servers.livejournal.com/6056.html</link>
  <description>Hello there, &lt;br /&gt;&lt;br /&gt;As you may or may not be aware, the Camarilla Web Server is slated to&lt;br /&gt;be moved over to a new machine. This move will involve moving all&lt;br /&gt;files and service which currently reside on camarilla.white-wolf.com&lt;br /&gt;to a new machine, and then the redirection of the URL to the new box.&lt;br /&gt;&lt;br /&gt;During this downtime, we are taking the opportunity to make a few&lt;br /&gt;changes that we hope will make for a better member experience. I would&lt;br /&gt;like to take this opportunity to describe a few of these changes in&lt;br /&gt;more detail. Following the description of some of the new features is&lt;br /&gt;an important request of the membership.&lt;br /&gt;&lt;br /&gt;-Replacing the iCamarilla system with the Camarilla Resource Database- &lt;br /&gt;&lt;br /&gt;Over the past few months the Tech Team, with the help of a few key&lt;br /&gt;developers, has been working on a system that will be used to&lt;br /&gt;integrate all of the member functionality currently distributed to&lt;br /&gt;several applications. The framework of this change is the Camarilla&lt;br /&gt;Resource Database. The CRD (as it has been come to be known as) merges&lt;br /&gt;the organizational management of the iCamarilla system with the&lt;br /&gt;ability to store characters, browse venues, make announcements, and&lt;br /&gt;much more.&lt;br /&gt;&lt;br /&gt;-Unifying the Logins to Various Applications- &lt;br /&gt;&lt;br /&gt;With the growth of applications developed by the Tech Team and the&lt;br /&gt;need to maintain a little more control over content, a decision was&lt;br /&gt;made to unify the logins to as many of the logins as possible.&lt;br /&gt;&lt;br /&gt;White Wolf has provided us with a framework to unify the logins by&lt;br /&gt;linking your Camarilla Membership to your White Wolf account. This&lt;br /&gt;will allow a central location for logging into services, as well as a&lt;br /&gt;central location for personal data changes.&lt;br /&gt;&lt;br /&gt;-Linking your Membership to your White Wolf Account- &lt;br /&gt;&lt;br /&gt;As you probably guessed from the above section, your Camarilla&lt;br /&gt;Membership will have to be linked to a White Wolf account. Since most&lt;br /&gt;Camarilla Members already have such account, this was a natural&lt;br /&gt;central login to use for this purpose.&lt;br /&gt;&lt;br /&gt;This will also give White Wolf the ability to ensure that when you are&lt;br /&gt;logged into their site that you are a Camarilla Member... which will&lt;br /&gt;open up new content and sections of their site to the membership.&lt;br /&gt;&lt;br /&gt;------------------------ &lt;br /&gt;Now... the fun part. &lt;br /&gt;------------------------ &lt;br /&gt;&lt;br /&gt;In order to facilitate this move over, we will be removing access to&lt;br /&gt;the machine known as camarilla.white-wolf.com. This access block will&lt;br /&gt;occur shortly after NEGLECt. We hope that this outage will last no&lt;br /&gt;more than a week.&lt;br /&gt;&lt;br /&gt;During this time, services such as Approvals, iCamarilla, Ordeals,&lt;br /&gt;etc. will NOT be available. This is to ensure that ALL data is&lt;br /&gt;imported and moved to the new machine and is not changed after it is&lt;br /&gt;moved. The cammail.white-wolf.com server will remain online during&lt;br /&gt;this process.&lt;br /&gt;&lt;br /&gt;What I need from the membership is for their Org Unit, Expiration&lt;br /&gt;Date, and Cam Number are present in the Membership Database. These&lt;br /&gt;fields will be used to link your current membership to your White Wolf&lt;br /&gt;account.&lt;br /&gt;&lt;br /&gt;Also, if you need to get an approval complete or to finish an ordeal,&lt;br /&gt;it needs to be done BEFORE NEGLECt so that we can remove access&lt;br /&gt;without interrupting your needs.&lt;br /&gt;&lt;br /&gt;Please stay tuned to whatever method this message reached you, as&lt;br /&gt;updates will be coming soon. Also, please distribute this information&lt;br /&gt;to as many members as you can to ensure it reaches as much of the&lt;br /&gt;membership as possible.&lt;br /&gt;&lt;br /&gt;Thanks, &lt;br /&gt;~brent cerrato &lt;br /&gt;US-NTA &lt;br /&gt;US2002022439</description>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/5876.html</guid>
  <pubDate>Thu, 26 May 2005 12:15:38 GMT</pubDate>
  <title>mailman!</title>
  <link>http://cam-servers.livejournal.com/5876.html</link>
  <description>a filesystem of relative import (var) got too corrupted, and is not available (and it was ext3, which should be stable enough darn it).  It is preventing mail from going out temporarily...a week before NEGLECt!  I&apos;ll have to reconstruct/restore it for it to work.  This will be done tonight, with literally several &lt;b&gt;entire days&lt;/b&gt; left before the con. /humour</description>
  <comments>http://cam-servers.livejournal.com/5876.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>2</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/5392.html</guid>
  <pubDate>Wed, 11 May 2005 01:19:42 GMT</pubDate>
  <title>today, yesterday, etc</title>
  <link>http://cam-servers.livejournal.com/5392.html</link>
  <description>an instant on/off power outage last week wasn&apos;t stopped by the UPS that was feeding the cam server last week, so it died.  It&apos;s gotten beyond the point of wanting to deal with such things anymore, so it&apos;s not taking kindly to it.&lt;br /&gt;&lt;br /&gt;Yesterday, the UPS just completely died.  Power didn&apos;t go off at WW, the UPS just died (so I&apos;m told).  Today?  No idea.&lt;br /&gt;&lt;br /&gt;Net result - continuous power loss, which yields unhappy system.  It&apos;s working again now, but I need to actually &lt;b&gt;fix&lt;/b&gt; it again, which will require downtime sometime this coming weekend.  I&apos;m thinkin saturday morning, sometime around 8am EST.   Consider that to be the schedule unless I post otherwise.  Will be up by noon, because it&apos;s supposed to stay sunny and I&apos;d like to go on a wine tour this weekend :)&lt;br /&gt;&lt;br /&gt;updates, and such.  Soon this (in theory?) won&apos;t happen anymore....?</description>
  <comments>http://cam-servers.livejournal.com/5392.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/5281.html</guid>
  <pubDate>Thu, 21 Apr 2005 11:31:20 GMT</pubDate>
  <title>that was fun</title>
  <link>http://cam-servers.livejournal.com/5281.html</link>
  <description>Forgot about this thing.  Wouldn&apos;t have mattered; I wasn&apos;t able to get anywhere.&lt;br /&gt;&lt;br /&gt;First note:  do we live in a third world country or something?  For the second time in 2 weeks, someone knocked down a power line (different places) and I lost power to my house abruptly and for many hours.  I stayed home yesterday since I hadn&apos;t had a weekend in ages, and wanted to relax.  I started doing some stuff to the cam server, and suddenly my laptop screen dimmed - which mean&apos;s it&apos;s running off battery.  Crap.  Nice sunny day, at least.  Trouble is, I have a digital phone.  No cablemodem means no phone.&lt;br /&gt;&lt;br /&gt;Finally reached someone at WW, got stuff up - only to find device-mapper no longer saw any lvm disks in the system....??  I poked, I proded, I got in chat channels where absolutely no one had any suggestions (you&apos;d think a channel with 1,100 people in it would have at least 1 person who knew...).&lt;br /&gt;&lt;br /&gt;Without the large areas available, only the minimal stuff was there - which is more or less just enough for me to log in (and to display web pages, since they don&apos;t take much).  All&apos;s well now though :/&lt;br /&gt;&lt;br /&gt;If you&apos;re on a box and device-mapper suddenly forgets where everything is, lemme know and I&apos;ll tell you both what not to do, and exactly how to fix it.  It ended up only taking less than 30 minutes once I figured it out...</description>
  <comments>http://cam-servers.livejournal.com/5281.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/5001.html</guid>
  <pubDate>Wed, 16 Feb 2005 15:23:33 GMT</pubDate>
  <title>hola!</title>
  <link>http://cam-servers.livejournal.com/5001.html</link>
  <description>Just wanted to let everyone know that both of us were not even turned on when Charles came in this morning to check us out.  But with Charles on the scene, he was able to push our buttons and get us going again.&lt;br /&gt;&lt;br /&gt;Seems we&apos;ve had impotent power problems off and on lately, and yesterday one of us (cammail - the mailman server) was burping all over.  Why?  Well, papa will figure that out when he gets home and can play with us.  Maybe it was a brown out?  Maybe the UPS we&apos;re on isn&apos;t happy?  Maybe we&apos;re just brats?&lt;br /&gt;&lt;br /&gt;Either way, we should be talking to the world now.  It may be a bit before you get an email you&apos;re expecting, but that&apos;s probably just because there&apos;s a backlog.  Wait your turn!</description>
  <comments>http://cam-servers.livejournal.com/5001.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>1</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/4803.html</guid>
  <pubDate>Thu, 06 Jan 2005 11:33:39 GMT</pubDate>
  <title>Renewal Order Processing</title>
  <link>http://cam-servers.livejournal.com/4803.html</link>
  <description>Renewal Order Processing&lt;br /&gt;&lt;br /&gt;When ordering renewals to your membership, please remember that your&lt;br /&gt;billing information MUST match the credit card information for the&lt;br /&gt;card used. If the address you enter does not match, the card will be&lt;br /&gt;declined and you may experience errors ordering.&lt;br /&gt;&lt;br /&gt;When you are renewing for someone else, you must still put YOUR&lt;br /&gt;information in the order page. Give the Order Confirmation information&lt;br /&gt;to the member you bought the membership renewal for, and they can&lt;br /&gt;attach it to their account in the members section of the Camarilla&lt;br /&gt;website (&lt;a href=&quot;http://camarilla.white-wolf.com/members&quot;&gt;http://camarilla.white-wolf.com/members&lt;/a&gt;)&lt;br /&gt;&lt;br /&gt;This should greatly reduce the problems with renewal orders.&lt;br /&gt;&lt;br /&gt;Thanks!&lt;br /&gt;&lt;br /&gt;-----&lt;br /&gt;~brent cerrato&lt;br /&gt;US2002022439</description>
  <comments>http://cam-servers.livejournal.com/4803.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/4427.html</guid>
  <pubDate>Tue, 14 Dec 2004 03:51:59 GMT</pubDate>
  <title>old camarilla.white-wolf.com emails</title>
  <link>http://cam-servers.livejournal.com/4427.html</link>
  <description>I did a couple things that I /thought/ would take care of the old mailman emails, without disturbing the emails that we wanted to continue.  In my goal of being careful, I didn&apos;t catch them all.  You&apos;ll see a few old emails going to the lists, coming from the camarilla.white-wolf.com server.  If you reply to them, reply at cammail.white-wolf.com&lt;br /&gt;&lt;br /&gt;Anyway - carry on!  Approvals and ordeals should now be sending emails.</description>
  <comments>http://cam-servers.livejournal.com/4427.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>1</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/4293.html</guid>
  <pubDate>Mon, 13 Dec 2004 18:23:41 GMT</pubDate>
  <title>ordeal and approvals email</title>
  <link>http://cam-servers.livejournal.com/4293.html</link>
  <description>Greetings.  When mail was moved, it was shut down on camarilla.white-wolf.com to prevent things from stepping on each other.  I set to ignore new incoming mail not generated on localhost, let the spool empty for a bit, then shut it down altogether.&lt;br /&gt;&lt;br /&gt;There were many reasons for this - mostly, so that when something wasn&apos;t working on one I&apos;d know, and also to force people to make changes.  I was aware that other, non-mailman emails would suffer - but it should be right there on the server still.&lt;br /&gt;&lt;br /&gt;Tonight, I&apos;ll get postfix going on camarilla.white-wolf.com again, so that ordeals and approvals emails start going again.  Its not a bug or problem causing it to not currently happen - its just that postfix is intentionally not running there.  I might scale back to a more simple MTA for just sending out those emails regardless, just to make things as simple as possible on there.</description>
  <comments>http://cam-servers.livejournal.com/4293.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>1</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/4029.html</guid>
  <pubDate>Wed, 08 Dec 2004 01:03:04 GMT</pubDate>
  <title>update</title>
  <link>http://cam-servers.livejournal.com/4029.html</link>
  <description>ok.  To move the lists from cam1 to cam2, I have to first ball em up so I can toss them over.&lt;br /&gt;&lt;br /&gt;That ball has been being created for approaching 2 hours now.  Once it is made, then it will be moved over to cam2.  Then it will be unballed, and manually extracted from (at least, at first).&lt;br /&gt;&lt;br /&gt;Just an fyi.  The lists are intentionally down atm, since the ball is being created, and I don&apos;t want the files changing during the interm.</description>
  <comments>http://cam-servers.livejournal.com/4029.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>5</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/3787.html</guid>
  <pubDate>Tue, 07 Dec 2004 18:22:27 GMT</pubDate>
  <title>immediate plans this evening...</title>
  <link>http://cam-servers.livejournal.com/3787.html</link>
  <description>Attention:  there WILL be lost mail tonight.  No ifs, no maybes.&lt;br /&gt;&lt;br /&gt;Simple reason:  it will take *hours* to move the lists over.  Once they are moved over, they will come up on the other box.  I will set up camarilla.white-wolf.com to forward things over, but...once things are off camarilla.white-wolf.com, that box will be down for a few hours.  That will mean no web stuff, no..well, lots of things.  But mail will be back, as it will be on cammail.&lt;br /&gt;&lt;br /&gt;I will make extensive effort to get all lists moved over tonight and tomorrow.  They will be done in groups, with the newer IC lists done second, and the national and regional ooc lists done first (for communication).  Those two groups will be tonight&apos;s goal.  The remainder of the lists will be done tomorrow.&lt;br /&gt;&lt;br /&gt;Assuming, of course, the extensive errors I&apos;m currently seeing don&apos;t take the system down before I get home this afternoon...</description>
  <comments>http://cam-servers.livejournal.com/3787.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>6</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/3407.html</guid>
  <pubDate>Tue, 07 Dec 2004 13:01:30 GMT</pubDate>
  <title>as soon as...</title>
  <link>http://cam-servers.livejournal.com/3407.html</link>
  <description>the system is reset, it will be.  I&apos;m waiting (called in on friday) just like everyone else....sorry.&lt;br /&gt;&lt;br /&gt;In the mean time, cammail seems to be ready to take the lists without any problems.  Transfering the 11Gb of archives/lists over is all we&apos;re waiting on for that, which is waiting for the system to be up to make the move from.</description>
  <comments>http://cam-servers.livejournal.com/3407.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>4</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/3181.html</guid>
  <pubDate>Wed, 01 Dec 2004 18:15:14 GMT</pubDate>
  <title>sunday night, now</title>
  <link>http://cam-servers.livejournal.com/3181.html</link>
  <description>apparently there was a power surge sunday night (or was that monday?  I worked 15 hours yesterday and 12 on monday, so my timing might be skewed from that) that took out both servers.&lt;br /&gt;&lt;br /&gt;I got on cammail last night to start moving stuff over from camarilla, and found that...it wasn&apos;t there.  Rather, it was, but it wasn&apos;t responding to actual requests for info.&lt;br /&gt;&lt;br /&gt;Assuming it wakes up today at some point though, several OOC lists will be moving over to cammail tonight.  An additional large chunk will move over tomorrow.  The entirity of the OOC lists will be moved by the week&apos;s end.  IC lists are another matter, esp those that are for the old chronicle.&lt;br /&gt;&lt;br /&gt;Sorry for the delay in putting up this note - I&apos;ve been with vendors all day down in the server room, far from any system that I could update LJ from, and I simply didn&apos;t think to do it last night.</description>
  <comments>http://cam-servers.livejournal.com/3181.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>17</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/2978.html</guid>
  <pubDate>Tue, 09 Nov 2004 16:46:46 GMT</pubDate>
  <title>mail issues, explained</title>
  <link>http://cam-servers.livejournal.com/2978.html</link>
  <description>There seems to be continued confusion about the mail issue.  Let me explain it in a way that it will hopefully be understood.&lt;br /&gt;&lt;br /&gt;When I post an email to the ordo dracul list, camarilla.white-wolf.com checks the mx record for lmco.com.  It then says HELO (a mail server&apos;s command to introduce itself) to mailgwX.lmco.com (replace X with the actual number it goes to).  It gives it&apos;s name.  The ip is then gleened from the transmition, and mailgwX.lmco.com decides to find out who 206.65.59.149 is.&lt;br /&gt;&lt;br /&gt;It asks the root server(s).  This is what it gets in reply:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Asking a.root-servers.net for 149.59.65.206.in-addr.arpa PTR record:  &lt;br /&gt;       a.root-servers.net says to go to indigo.arin.net. (zone: 206.in-addr.arpa.)&lt;br /&gt;Asking indigo.arin.net. for 149.59.65.206.in-addr.arpa PTR record:  &lt;br /&gt;       indigo.arin.net [192.31.80.32] says to go to auth00.ns.uu.net. (zone: 65.206.in-addr.arpa.)&lt;br /&gt;Asking auth00.ns.uu.net. for 149.59.65.206.in-addr.arpa PTR record:  &lt;br /&gt;       auth00.ns.uu.net [198.6.1.65] says to go to Z1.NS.SJC1.GLOBIX.NET. (zone: 59.65.206.in-addr.arpa.)&lt;br /&gt;Asking Z1.NS.SJC1.GLOBIX.NET. for 149.59.65.206.in-addr.arpa PTR record:  Reports camarilla.white-wolf.com. [from 209.10.34.55]&lt;br /&gt;&lt;br /&gt;Answer:&lt;br /&gt;206.65.59.149 PTR record: camarilla.white-wolf.com. [TTL 86400s] [A=206.65.59.149]&lt;br /&gt;206.65.59.149 PTR record: www.camarilla.org. [TTL 86400s] [A=None] *ERROR* A record does not point back to original IP.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;At least, that&apos;s what we *hope* it gets, and exactly 50% of the time that is what happens.  The other 50% of the time, the last two lines (the answer) switch - the answer is www.camarilla.org.&lt;br /&gt;&lt;br /&gt;So when someone does a reverse lookup, they get back that answer - but they &lt;i&gt;only look at the first response&lt;/i&gt;.  Since www.camarilla.org is the first response 50% of the time, that mail gets rejected.&lt;br /&gt;&lt;br /&gt;What happens then?  The email is resent.  And resent again.  And resent again.  And again.  And again.&lt;br /&gt;&lt;br /&gt;What can be done about this?  3 things:&lt;br /&gt;&lt;li&gt;simply change 206.65.59.149 to a different ip, and point camarilla.white-wolf.com to that ip instead.  WW issue.&lt;br /&gt;&lt;li&gt;remove the damn www.camarilla.org record.  Earthlink (the authority on the name, apparently) refuses to do this.  WW has lawyers talking to them, or so I am told.&lt;br /&gt;&lt;li&gt;Start sending mail from cammail.white-wolf.com&lt;br /&gt;&lt;p&gt;Which are we planning on doing?  #3, currently.  Which will mean that in a couple weeks, all email will suddenly be coming from somewhere else!  This will take a bit of work in mailman to change everything over, and will break filters people have that explicitly name servers.&lt;br /&gt;&lt;br /&gt;So when an email doesn&apos;t arrive right now, this is the reason.  The emails are actually zooming through quite nicely with zero delays - email sent to a list returns in seconds generally (what your MX does with it then is their ball).  The servers aren&apos;t bogged down, there is simply a delay in retrying a failed attempt at sending a particular email.  At 50% a shot, that could -potentially- be a long delay.&lt;br /&gt;&lt;br /&gt;Let me know if this doesn&apos;t make sense.  No, not all mail servers do reverse lookups - those that don&apos;t are getting all mail instantly.  Its those of us that have mail servers run by anti-spam admins that have the issue (since the reverse lookup is done for anti-spam reasons).&lt;br /&gt;&lt;br /&gt;And yes - that means that we often look like a spam box to many servers out there...what with the volume of mail (sent to lists, not specific people), and the failed lookups.</description>
  <comments>http://cam-servers.livejournal.com/2978.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>1</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/2659.html</guid>
  <pubDate>Fri, 29 Oct 2004 20:26:17 GMT</pubDate>
  <title>updates saturday morning!</title>
  <link>http://cam-servers.livejournal.com/2659.html</link>
  <description>Saturday morning, approx 5min after I wake up (giving me time to eat some oatmeal or something), I will be updating apache and postfix on the servers.  I am planning on this being ~7am EST, and it won&apos;t be started later than 8:30am EST.  There will actually only be less than a minute of downtime with apache, and any downtime with postfix won&apos;t be noticable since mail will spool for the few minutes it is down (ie - no service impact).</description>
  <comments>http://cam-servers.livejournal.com/2659.html</comments>
  <lj:music>Covenant - Europa</lj:music>
  <media:title type="plain">Covenant - Europa</media:title>
  <lj:mood>geeky</lj:mood>
  <lj:security>public</lj:security>
  <lj:reply-count>1</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://cam-servers.livejournal.com/2423.html</guid>
  <pubDate>Thu, 28 Oct 2004 03:15:28 GMT</pubDate>
  <title>yes, we know</title>
  <link>http://cam-servers.livejournal.com/2423.html</link>
  <description>sorry for the delay in verifying that we know, but yes...we do in fact know.&lt;br /&gt;&lt;br /&gt;Both servers are gone, so failing over to the second one just won&apos;t be happening.  It also limits the number of things that can be reasonably expected to be the cause (since cam2 wasn&apos;t even being used this evening).&lt;br /&gt;&lt;br /&gt;Will have to wait until I can reach folks at WW in the morning...until then, relax and enjoy the moment of silence.</description>
  <comments>http://cam-servers.livejournal.com/2423.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>2</lj:reply-count>
</item>
</channel>
</rss>
