silbia's blog

[phpwiki]
I get this error while installing trac:

Trac detected an internal error:

No module named neo_cgi

Traceback (most recent call last):
File "/var/sites/myers.name/bob/cgi-bin/trac.cgi", line 25, in ?
trac.core.cgi_start()
File "/usr/lib/python2.3/site-packages/trac/core.py", line 477, in cgi_start
send_pretty_error(e, None)
File "/usr/lib/python2.3/site-packages/trac/core.py", line 412, in send_pretty_error
req.init_request()
File "/usr/lib/python2.3/site-packages/trac/core.py", line 312, in init_request
Request.init_request(self)
File "/usr/lib/python2.3/site-packages/trac/core.py", line 243, in init_request

You might come across this error while using trac-admin

trac-admin /opt/tracdb/uabgrid initenv
Traceback (most recent call last):
  File "/usr/local/bin/trac-admin", line 33, in ?
    from trac import util
ImportError: No module named trac

This error is caused because the python path for site-packages is not found. Set the environment variable PYTHONPATH

for example:

export PYTHONPATH=/usr/local/lib/python2.3/site-packages

[phpwiki]
You might come across this error while installing Trac:

Oops...

Trac detected an internal error:

No module named trac.core

Traceback (most recent call last):
File "/var/www/cgi-bin/trac.cgi", line 24, in ?
import trac.core
ImportError: No module named trac.core

This error is caused because the python path for site-packages is not found. Set the environment variable PYTHONPATH in your Apache configuration file for Trac to point to the correct path.

for example:
PYTHONPATH:/usr/local/lib/python2.3/site-packages

Enable the RewriteEngine and set the inherit option of the RewriteOptions in your ssl virtual host conf file.

Include the following in the ssl.conf file:

RewriteEngine on
RewriteOptions inherit

By default, rewrite configurations are not inherited. This means that you need to have a RewriteEngine on directive for each virtual host in which you wish to use it.

The option inherit forces the current configuration to inherit the configuration of the parent. In per-virtual-server context this means that the maps, conditions and rules of the main server are inherited. In per-directory context this means that conditions and rules of the parent directory's .htaccess configuration are inherited.

University of Melbourne's Alchemi .NET grid computing framework(part of the Gridbus project) has been installed on my Windows vmware. I could run the sample program as suggested on the site. Alchemi is written for .NET based applications, and can be used to construct grids and develop applications for grid using Alchemi API. Idle CPU time of machines on the grid is used; user programs are not impacted. It also has a web services interface for interoperability with other grid middleware.

Jobs werent executing on condor pool because the new nori wasnt rebooted after changing the hostname(from ceviche to nori).
After rebooting, I simply put off condor on nori, made changes to some files to reflect as nori, and restarted it. Works fine now.

I ran sample Fortran MPI programs (Fortran77) on medusa and proc1 using MPICH-G2. The programs are simple hello world and matrix programs.
They were compiled using MPICH-G2s mpif77 compiler. We apparently dont have an mpif90 compiler. Could some one comment on how to get Fortran90 code running.

__Globus Toolkit 2.4 SDK__ and __Client__ bundles have been installed on proc1 and located in /opt/globus-2.4. Commands like grid-proxy init and globusrun seem to be running fine. The globus hello world program runs fine too.
I had also previously installed GPT in proc1 at /opt/gpt. While building I encountered an error which was solved when I unset the environment variable LANG.

After unsuccessfully building MPICH-G2, I tried the same as root. No luck; gives the same error.
Its now configured in proc1.lab.ac.uab.edu in /var/tmp/mpich-1.2.5.2 . Also c.log and make.log in the directory give the output from the configure and make commands.

I scanned the Ldap-devel mailing list posts for the past two months to get a feel of what is happening in the lab.
Then got an overview of the pubcookie project from jpr and spent the rest of the time exploring the pubcookie website.(Documentation for Apache and ISAPI filter)

All in all, got to know quite a lot on my first day, and ofcourse, was quite interesting!