Finally a good use for the color picker in Google images 🙂
This post contains information/links to twitterers twittering useful information about the clashes in Iran, that started one year ago today (12th of june 2009)
Updated 12th june 2010, 12:45 GMT
Updated last hour:
EANewsFeed – Tweets about it
JShahryar – Tweets about it
dadashiii – Tweets about it
Bsalamati – Tweets about it
mumke – Tweets about it
lissnup – Tweets about it
DominiqueRdr – Tweets about it
RayMorrison – Tweets about it
mamad2020 – Tweets about it
If you want to read up about last years event, i reccomend http://www.thenation.com/blogs/notion/443634
Just a quick post on what i did to get Groupwise up and running on Ubuntu 64bit:
1) Installed a 32bit virtual Ubuntu machine, and converted the Groupwise installer to a .deb package with “alien -c filename”.
2) Moved the .deb package back to the host machine.
3) Installed 32bit java libraries “sudo apt-get install ia32-sun-java6-bin”
4) Forced installation of the Groupwise client “sudo dpkg -i –force-architecture novell-groupwise-gwclient_8.0.0-84911_i386.deb”
5) And it works 🙂
Getting the exception “org.apache.jasper.JasperException: java.lang.NumberFormatException” when developing a JavaEE-app?
If you are basing yourself on data from a query, make shure that you are doing a SELECT against the table name and NOT the individual fields!
username@host:/home/foo> fetchmail -f /opt/rt-fetchmail/fetchmail 2>&1 /dev/null
Enter password for username@/dev/null:
Solution: Change the cron entry / command to the following:
fetchmail -f /opt/rt-fetchmail/fetchmail > /dev/null 2>&1
This will stop -all- output from appearing.
As a JavaEE-codemonkey you have perhaps noticed this error:
java.lang.IllegalArgumentException: Object: Ting@193c227 is not a known entity type.
This will occur when you have redeployed an app f.ex through Eclipse to Glassfish, the Glassfish server has not quite understood that it`s time to update its version, so what you need to do then is to simply restart the server (or domain).
Here`s all you need! 🙂
When RT is upgraded, users can experience WSOD(White Screen Of Death), all the log will say is:
“Out of memory! Callback called exit.”. Not so informative eh?
The solution is pretty simple, run this query in the database:
“ALTER TABLE sessions CHANGE a_session a_session LONGBLOB;”
Then clear the table with:
TRUNCATE TABLE `sessions`;
Any logged in users will be logged out, but the problem should disappear.
Just a quick hint for those of you who are experiencing problem with getting node-agents up and running in a Glassfish cluster.
If the problem is that the asadmin start-agent command simply times out/uses a long time to start, and even possibly returning a filenotfoundexception. The problem could be as simple as a firewall blocking traffic to/from the master-node. A quick way to check it is to simply disable the FW.
Note that if the master-node does not see the node-agent status, it is also caused by FW-issues, fix the FW and then restart the node-agent(s), then it all should work like a charm!
A nice way of rebooting a frozen Linux-based server when you do not have a power switch available is to use the SysRq-abilities. (Ubuntu Example.) Blackbox does not have a default macro installed for just that, but you can create a new macro and insert the following:
This will create a working macro for writing any data in cache to disk, kill all processes (Sigkill), remount mounted disks and perform a reboot.
Sometimes the backspace button can be a real pain on SLES-systems, but the fix is simple!
Add this to ~/.vimrc: