And run compiz-check to see if there are any issues with your setup/hardware.
To get the features of OSX’s Docker, you’re going to want to install Cairo-Docker. Cairo-Docker is actually even MORE incredible than the traditional Docker, allowing for plugins and customization to the Nth degree.
I was recently contacted by someone who got stuck setting up Starling and realized that the documentation is relatively sparse on setting up Starling. The process is easy once you know how Starling works on the inside, but not looking in.
To get started, I will assume you have ruby and ruby gems already installed. This will depend on your flavor of distribution, but should not be difficult and come standard on every modern version of Linux I’ve used.
run:
gem install starling
Create the Starling queue directory in /var/spool/starling
Start staring with these minimum set of arguments:
Also, note that Starling creates a queue file for each key verbatim. So if a key is, ‘namespace/something’, then Starling will fail to do the set if the ‘namespace’ directory does not exist under the /var/spool/starling directory. You can also just not use ‘/’ in your keys.
Also, note that Starling does not automatically purge the queue files after it rotates them. You’ll want to cron a job to run periodically to delete them. We run this nightly to purge files not accessed in 4 days:
find /var/spool/starling/ -type f -atime +4 -delete
by creating a file in /etc/cron.daily/starling with those contents.
All that being said, we’re still very happy with it and process about a million jobs a day.
Please let me know in the comments if your still having problems!
VMWare can be a real bore to upgrade when there are major kernel updates. Very often, the supplied modules with VMWare will not compile.
For example, I got this today:
CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
/tmp/vmware-config0/vmmon-only/linux/driver.c:197: error: unknown field ‘nopage’ specified in initializer
/tmp/vmware-config0/vmmon-only/linux/driver.c:198: warning: initialization from incompatible pointer type
make[2]: *** [/tmp/vmware-config0/vmmon-only/linux/driver.o] Error 1
The solution is always to use the non-standard installer available at:
http://groups.google.com/group/vmkernelnewbies/files?pli=1
Download the latest vmware-any-any-update tarball, decompress it, and run the included runme.pl script inside. It works just like the vmware-install.pl script distributed with VMWare, but this version includes patches to make everything run without a hitch.
The memcache protocol requires that all lines in the server response end with CRLN (\r\n). The Starling server doesn’t strictly obey this for the STATS command. The fix is trivial and the author has been notified of the fix.
Edit lib/starling/handler.rb and add the following gsub right before .freeze in the STATS_RESPONSE:
%sEND\r\n”.gsub(/\r?\n/, “\r\n”).freeze
And the same for QUEUE_STATS_RESPONSE:
STAT queue_%s_expired_items %d\n”.gsub(/\r?\n/, “\r\n”).freeze
In the process of deserializing an object, it tried to instantiate a class which hadn’t yet been loaded. The autoloader wasn’t able to find the class and the spl autoload functionality therefore croaked.
The problem was that I had defined a property inside of one my model objects that referenced the sfWebRequest. This property should never have been serialized. Infact, only the properties of the object as defined in model should get serialized. The fix was defined a __sleep method in the model.
public function __sleep()
{
return MySampleObjectPeer::getFieldNames(BasePeer::TYPE_FIELDNAME);
}
Replace MySampleObjectPeer with the appropriate peer class.
add to del.icio.us
add to technorati favs
email this