- Published:
- March 25, 2009 – 4:15 pm
- Author:
- By Dave
I just found a quick tip on the Installatron forums. By default Installatron disables all WordPress plugins when doing an upgrade. This is due to the WordPress best practices for upgrading the version of their system. When you have a lot of WordPress installs to go through this is a big pain because it usually breaks the site. According to this post, you disable the disabling of the plugins by creating a file named .dont_disable_plugins in the directory that wordpress is installed to. Via command line it is as simple as this: 1touch /path/to/wordpress/.dont_disable_plugins Execute that command on the command line (or upload an empty file via FTP/SCP) and the plugins will remain enabled. There is also an option in the installatron settings to enable this file creation upon install. Note that if you have a plugin that is not compatible with a new version of WordPress, it may break….
Categories: Configurations,Software,System Administration,Webdesign
Tagged: installatron, wordpress
- Published:
- March 23, 2009 – 9:14 am
- Author:
- By Dave
Recently I started seeing this error while provisioning Xen VPSes on a server with 8GB of RAM: 12[2009-03-23 15:51:40 xend.XendDomainInfo 3310] DEBUG (XendDomainInfo:1603) XendDomainInfo.destroy: domid=None [2009-03-23 15:51:40 xend 3310] ERROR (xmlrpclib2:184) (12, ‘Cannot allocate memory’) I checked the memory, and sure enough, all of the VPSes were using up the memory. More specifically, dom0 (the main server) had ‘ballooned’ and begun to take up 3GB of RAM, this is more than the system should need: 12[2009-03-22 18:03:08 xend.XendDomainInfo 3310] DEBUG (XendDomainInfo:1113) Setting memory target of domain Domain-0 (0) to 2903 MiB. [2009-03-22 18:03:09 xend 3310] DEBUG (balloon:127) Balloon: 537840 KiB free; need 537600; done. Basically when memory ballooning is set, the memory available to the main hypervisor will have a minimum value set and will balloon according to the current requirements. This setting is in the config file which for me is at /etc/xen/xend-config.sxp: 1234# Dom0 will balloon out when….
Categories: CentOS,Configurations,System Administration,Xen
Tagged: CentOS, dom0, memory, Xen
- Published:
- March 18, 2009 – 6:57 am
- Author:
- By Dave
I presented this paper to my class on March 17th, 2009. Hybrid Stealthy Networks – Paper Presentation Original paper: Hybrid Stealthy Communication Protocol (I got a 25/25!)
Categories: Other Technology,Reviews
Tagged: ad hoc, fiber, Security, wireless
- Published:
- March 17, 2009 – 3:58 pm
- Author:
- By Dave
Running sudo apt-get upgrade, I started getting this error: 1Reading package lists… Done 1W: GPG error: http://ppa.launchpad.net intrepid Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 313D312748A22A95 1W: You may want to run apt-get update to correct these problems Ah ha! But apt-get update is the command causing this problem. The solution is to import this key from the gpg servers; I don’t know why this isn’t done automatically, but here is it: 1sudo apt-key adv –recv-keys –keyserver keyserver.ubuntu.com 313D312748A22A95; gpg –export –armor 313D312748A22A95 | sudo apt-key add – Resulting in: 123456Executing: gpg –ignore-time-conflict –no-options –no-default-keyring –secret-keyring /etc/apt/secring.gpg –trustdb-name /etc/apt/trustdb.gpg –keyring /etc/apt/trusted.gpg –recv-keys –keyserver keyserver.ubuntu.com 313D312748A22A95 gpg: requesting key 48A22A95 from hkp server keyserver.ubuntu.com gpg: key 48A22A95: public key "Launchpad PPA for Filip Brcic" imported gpg: Total number processed: 1 gpg: unchanged: 1 OK Congrats! sudo apt-get….
Categories: Configurations,Shell,System Administration,Ubuntu
Tagged: apt-get, gpg, Ubuntu
