The Open Source Software for Innovation and Collaboration SIG (OSSIC SIG) is launching a series of Capability Building Workshops for Singapore Computer Society members.
The first in the series is on Open Source Database for Enterprises which will be held on 29 April from 8.30am to 1.00pm at SCS Resource Centre.
Also open to Non-Members….
As seats are limited, do register now.
I just received notice that CloudCamp Singapore is going to be held on Monday night (Sept 20th) at 5:30pm. Its a free event which will be held at PayPal’s office in Suntec Towers (map). I think you’ll love this event because Cloud Computing is hot, and unconferences are a great way to discuss hot topics.
Topics to be discussed are:
- "How to Build your own Private Cloud”
- "Choosing between IaaS and PaaS"
- "Migrating Enterprise Apps to the Cloud" and many others.
Other speakers will include:
- Dave Mitchell, Director of SaaS at IBM will present "Building SaaS applications in the Cloud"
- Chris Boesch of Singapore Management University will present "The benefits of PaaS vs. IaaS".
- Dave Nielsen, co-founder of CloudCamp, will give a talk about "The Economically Unstoppable Cloud"
Are you interested in, or have experience with the following subjects:
- Using Infrastructure-as-a-Service – EC2, Rackspace Cloud, etc.
- Using Platform-as-a-Service – App Engine, Heroku, Engine Yard, Force.com, Azure, etc.
- Scaling apps in the Cloud – H-Base, Membase, RabbitMQ
- Managing apps in the Cloud – Scalr, RightScale
- Migrating apps to the Cloud
- Cloud Security
- Big Data – Hadoop
If so, you should attend CloudCamp where you will learn from your peers and experts about Cloud Computing. Register here.
WHEN: September 20, 2010
PayPal Singapore (map)
#09-01 Suntec Tower 5
5 Temasek Boulevard
5:30pm: Registration & Networking
6:15pm: Lightning Talks
– "The Economically Unstoppable Cloud" - Dave Nielsen
– "OpenStack, Open Standards" - from Cloudscaling
– "Benefits of PaaS versus SaaS" – Chris Boesch, Singapore Management University
– Dave Mitchell, Director of SaaS at IBM
– "5 reasons or implications of moving enterprise app to the cloud" – Ryan Joseph of YBO
6:45pm: Lightning Panel
7:15pm: Begin Unconference
7:30pm: Unconference Session 1
– What is Cloud Computing? – Dave Nielsen, CloudCamp
– Benefits of PaaS such as Google App Engine – Chris Boesch, SMU
– How to build your own Cloud
– Interoperability and Open Source
– Cloud Security
8:30pm: Unconference Session 2
– How to Scale your application in the Cloud"
9:30pm: Wrap-up & Networking
I have been receiving this error for a few days now fueling my laziness to connect at the office. But unfortunately last week I was asked to assist in implementing a major change so I need to connect from home prompting me to fix this issue or else I need wake up early and haul my *ss to the office on a weekend.
The setup is I connect to the office VPN via the Nortel Contivity client utilizing SecureID token. I keep getting the error “Login failure due to remote host not responding” when I tried to connect. I didn’t have this problem before and can connect from my “virtualized” laptop (I did a Physical-to-Virtual (p2v) migration of my office laptop so that I don’t have to bring the laptop home often).
Going through the Nortel Contivity Client document, I found this:
This is typically caused by UDP500 traffic not getting back to the requesting client through a firewall and/or router. If your firewall/router supports IPSec passthrough you must enable IP50, IP51, UDP500 on both the source and destination (i.e. bidirectional) in order for the client to establish the connection. Some firewalls/routers have a generic setting "Enable IPSec" or "Enable IPSec Passthrough" and simply turning this on will usually solve the problem.
The keyword here is IPSec Passthrough. In order for IPsec to work through a NAT, the following protocols need to be allowed on the firewall:
- Internet Key Exchange (IKE) – User Datagram Protocol (UDP) port 500
- Encapsulating Security Payload (ESP) – IP protocol number 50
- Authentication Header (AH) – IP protocol number 51
I immediately login to my router administration panel and there it is, the IPSec Passthrough was disabled. This might have been disabled after a recent upgrade of the router’s firmware. After enabling this feature, the VPN client connected immediately.
DD-WRT –> Security -> VPN Passthrough
By the way, I have a Linksys WRT320N using a third-party firmware called DD-WRT.
Got this error after installing ESX 4 U1 as a virtual machine running under VMware Workstation 7 for some Lab work. After installation completed, the following error was shown on the ESX console:
TSC: 54361147 cpu0:0)NUMA: 706: Can’t boot system as genuine NUMA. Booting with 1 fake node(s).
Although this didn’t seem to cause any issues with the VM, it is annoying to see red error message.
According to Wikipedia:
Non-Uniform Memory Access or Non-Uniform Memory Architecture (NUMA) is a computer memory design used in multiprocessors, where the memory access time depends on the memory location relative to a processor. Under NUMA, a processor can access its own local memory faster than non-local memory, that is, memory local to another processor or memory shared between processors.
We’ll I don’t need NUMA for my Lab so after tinkering on the ESX settings, I found out that there’s a setting under Boot section of VMKernel that can be un-check to prevent the use of NUMA.
vSphere Client -> ESX/vCenter -> Left-click on the ESX server -> Configuration -> Advanced Settings -> Vmkernel -> vmkernel.boot.usenumainfo -> uncheck (this may require a reboot if it doesnt take effect right away)
We’ll a picture is worth a thousand words they say so here’s a screenshot:
After rebooting the ESX VM, no more annoying red message:
If you encounter the following error after installing VMWare Server 2.0 RCx to Ubuntu:
Using 2.6.x kernel build system.
make: Entering directory `/root/tmp/vmware-config0/vsock-only'
make -C /lib/modules/22.214.171.124-desktop-1mnb/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make: Entering directory `/usr/src/linux-126.96.36.199-desktop-1mnb'
CC [M] /root/tmp/vmware-config0/vsock-only/linux/af_vsock.o
In file included from /root/tmp/vmware-config0/vsock-only/linux/af_vsock.c:92:
/root/tmp/vmware-config0/vsock-only/./include/compat_wait.h:64: error: conflicting types for ‘poll_initwait’
include/linux/poll.h:65: error: previous declaration of ‘poll_initwait’ was here
/root/tmp/vmware-config0/vsock-only/linux/af_vsock.c:260: warning: initialization from incompatible pointer type
/root/tmp/vmware-config0/vsock-only/linux/af_vsock.c: In function ‘__VSockVmciCreate’:
/root/tmp/vmware-config0/vsock-only/linux/af_vsock.c:1789: warning: passing argument 1 of ‘sk_alloc’ makes pointer from integer without a cast
/root/tmp/vmware-config0/vsock-only/linux/af_vsock.c:1789: warning: passing argument 3 of ‘sk_alloc’ makes integer from pointer without a cast
/root/tmp/vmware-config0/vsock-only/linux/af_vsock.c:1789: warning: passing argument 4 of ‘sk_alloc’ makes pointer from integer without a cast
make: *** [/root/tmp/vmware-config0/vsock-only/linux/af_vsock.o] Error 1
make: *** --_module_/root/tmp/vmware-config0/vsock-only-- Error 2
make: Leaving directory `/usr/src/linux-188.8.131.52-desktop-1mnb'
make: *** http://vsock.ko Error 2
make: Leaving directory `/root/tmp/vmware-config0/vsock-only'
Unable to build the vsock module.
fret not since there is a workaround to this. Although this is just a minor inconvenience and your VM will still run fine, you’ll better off fixing it. Read on
The problem is that the 2.6.24 kernel as packaged by Ubuntu 8.04 “hardy” changed how its source code provides certain information. This can be fixed by modifying the vsock module’s source code.
vsock = VM communication interface socket
- The first thing to do is to unpack the vsock source:
$ tar xvf /usr/lib/vmware/modules/source/vsock.tar
- Change some of its auto-configuration.
$ cd vsock-only
$ sed -i 's/^\#include <linux\/autoconf\.h>//' autoconf/*.c
- The command above will traverse the autoconf folder and go through all the files that matches
*.c and remove all lines that looks like:
these are part of the test file that the build system uses to figure out what features are available:
- Build the code:
- Copy the driver over where VMware’s startup scripts can find it:
$ sudo cp vsock.o /lib/modules/$(uname -r)/misc
$ sudo ln -s vsock.o /lib/modules/$(uname -r)/misc/vsock.ko
- Create the dependency module so that the correct module dependencies will be available after booting the system
$ sudo depmod -a
- Now shut down all your running VMs and restart VMware’s services:
$ sudo invoke-rc.d vmware restart
For Fedora/RedHat (or derivatives)
$ sudo /sbin/service vmware restart
Now the vsock driver should load up properly. Try entering http://localhost/ui/ in your favorite browser (I supposed it’s Firefox). Tested on Ubuntu 8.04 (Hardy Heron). Now get that virtual server running……