h3x.no

To reset the MySQL root password, do the following:

USE DATABASE mysql;
SET PASSWORD FOR root@localhost=PASSWORD(‘yournewpassword’);
FLUSH PRIVILEGES;

And voila! You have changed your password.

PS: If you have a “problem” with beeing able to login to MySQL without using password (even when it is set in MySQL), try to edit or delete ~/my.cnf, since that holds information used to avoid the login promt.

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

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).

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!

Sometimes the backspace button can be a real pain on SLES-systems, but the fix is simple!

Add this to ~/.vimrc:
set backspace=indent,eol,start