August 21, 2013: A painful reinstallation and rewrite of our extreme site.

It was working before extremely well with Quixote server. In my desire to upgrade to the latest QP , QPY webserver system, I have wrecked my hard work of so many years. But I know the developers of QP and QPY have a gem of a web server framework. It just occupies a few space in a Linux system. So we start documenting a fresh rewrite of our solvers using QP, QPY.

Here is what we did.

1. Download the installation files.




wget -ct 0 --no-check-certificate https://www.mems-exchange.org/software/DurusWorks/DurusWorks-1.2.tar.gz
wget -ct 0 --no-check-certificate https://www.mems-exchange.org/software/dulcinea/Dulcinea-0.22.tar.gz


2. Install DurusWorks first.

Unpack the tarball. tar xzvvf DurusWorks-1.2.tar.gz. This creates a directory DurusWorks-1.2/ with the following files: BUGFIX_AGREEMENT.txt CHANGES.txt LICENSE.txt README.txt setup.py

and the following sub directories: doc durus proto qp qpy sancho scgi

Reading the README.txt tells me that the installation instructions and other documentation are in docs/DurusWorks.html

As root create the following directories:

mkdir /www
mkdir /www/trunk
mkdir /www/pythonlib
mkdir /www/bin
mkdir /www/var;
chmod 777 /www/var
mkdir /www/qp_sites
mkdir /www/ssl
mkdir /www/cgi-bin
mkdir /www/conf


You are supposed to unpack the package at the /www/trunk directory. But if you unpacked it, you may just use a copy operation: sudo cp -Ruv * /www/trunk.

cd /www/trunk/DurusWorks
python setup.py build_ext -i
rm -r build

To be continued .....

Timeline for DurusWorks Installation

I should not have upgraded the working old version of QP/QPY but I was severely tempted to do so after updating the Operating System. The new QP/QPY/Durus package is now named DurusWorks, includes Sancho, Dulcinea

• March 13, 2013
The software is hosted at Mems-Exchange. According to the documentation, the steps to to define a new site named named hello, is to start with a copy of the proto site:

mkdir /www
mkdir /www/trunk
cp -r /www/trunk/DurusWorks/proto /www/trunk/hello 
ln -s /www/trunk/hello/lib /www/pythonlib/hello 
ln -s /www/trunk/hello/site /www/qp_sites/hello 

Edit /www/trunk/hello/lib/ui/slash.qpy to configure the service addresses (I did not change the defaults) Edit /www/trunk/hello/site/slash.py and change the import to this:

from hello.ui.slash import SitePublisher, SiteDirectory 

I got the following when starting the qp server.

> qp start
Using Python base classes for persistence.
Could not find sites in any of these places:
   /www/qp_sites
   /usr/local/lib/python2.7/dist-packages/qp/sites

Interestingly I get the following output when invoking qpcheck.py:

> qpcheck.py
./trunk/hello/lib/ui/slash.qpy: 'SitePublisher' is unused
./trunk/hello/lib/ui/slash.qpy: 'SiteDirectory' is unused

Here is the directory structure of the /www

$ ls -alR /www/*
/www/pythonlib:
total 8
drwxr-xr-x 2 root root 4096 Mar 13 17:21 .
drwxr-xr-x 5 root root 4096 Mar 13 17:20 ..
lrwxrwxrwx 1 root root   15 Mar 13 17:21 hello -> trunk/hello/lib

/www/qp_sites:
total 8
drwxr-xr-x 2 root root 4096 Mar 13 17:22 .
drwxr-xr-x 5 root root 4096 Mar 13 17:20 ..
lrwxrwxrwx 1 root root   16 Mar 13 17:22 hello -> trunk/hello/site

/www/trunk:
total 12
drwxr-xr-x 3 root root 4096 Mar 13 17:19 .
drwxr-xr-x 5 root root 4096 Mar 13 17:20 ..
drwxr-xr-x 6 root root 4096 Mar 13 17:19 hello

/www/trunk/hello:
total 24
drwxr-xr-x 6 root root 4096 Mar 13 17:19 .
drwxr-xr-x 3 root root 4096 Mar 13 17:19 ..
drwxr-xr-x 2 root root 4096 Mar 13 17:19 conf
drwxr-xr-x 2 root root 4096 Mar 13 17:19 doc
drwxr-xr-x 3 root root 4096 Mar 13 17:19 lib
drwxr-xr-x 2 root root 4096 Mar 13 17:19 site

/www/trunk/hello/conf:
total 12
drwxr-xr-x 2 root root 4096 Mar 13 17:19 .
drwxr-xr-x 6 root root 4096 Mar 13 17:19 ..
-rw-r--r-- 1 root root 1070 Mar 13 17:19 apache2_proto.conf

/www/trunk/hello/doc:
total 12
drwxr-xr-x 2 root root 4096 Mar 13 17:19 .
drwxr-xr-x 6 root root 4096 Mar 13 17:19 ..
-rw-r--r-- 1 root root   11 Mar 13 17:19 doc.txt

/www/trunk/hello/lib:
total 16
drwxr-xr-x 3 root root 4096 Mar 13 17:19 .
drwxr-xr-x 6 root root 4096 Mar 13 17:19 ..
-rw-r--r-- 1 root root  149 Mar 13 17:19 __init__.py
drwxr-xr-x 3 root root 4096 Mar 13 21:27 ui

/www/trunk/hello/lib/ui:
total 48
drwxr-xr-x 3 root root 4096 Mar 13 21:27 .
drwxr-xr-x 3 root root 4096 Mar 13 17:19 ..
-rw-r--r-- 1 root root 3712 Mar 13 17:19 forms.qpy
-rw-r--r-- 1 root root  229 Mar 13 17:19 __init__.py
-rw-r--r-- 1 root root 3665 Mar 13 17:19 qwiki.qpy
-rw-r--r-- 1 root root 9662 Mar 13 21:27 slash.qpy
-rw-r--r-- 1 root root 9661 Mar 13 17:28 slash.qpy~
drwxr-xr-x 2 root root 4096 Mar 13 17:19 static

/www/trunk/hello/lib/ui/static:
total 24
drwxr-xr-x 2 root root 4096 Mar 13 17:19 .
drwxr-xr-x 3 root root 4096 Mar 13 21:27 ..
-rw-r--r-- 1 root root 1054 Mar 13 17:19 all.css
-rwxr-xr-x 1 root root 3638 Mar 13 17:19 favicon.ico
-rw-r--r-- 1 root root   82 Mar 13 17:19 favicon.png
-rw-r--r-- 1 root root 1450 Mar 13 17:19 proto.js

/www/trunk/hello/site:
total 16
drwxr-xr-x 2 root root 4096 Mar 13 17:19 .
drwxr-xr-x 6 root root 4096 Mar 13 17:19 ..
-rw-r--r-- 1 root root  150 Mar 13 17:19 __init__.py
-rw-r--r-- 1 root root   86 Mar 13 17:19 slash.py
$ 

I wonder what is wrong!
• March 15, 2013
I followed to the letter the "standard installation" procedure published in https://www.mems-exchange.org/software/DurusWorks/DurusWorks-1.1.tar.gz/DurusWorks-1.1/doc/DurusWorks.html The problem in installation was that the scgi modules wanted the apxs compiler. We temporarily ignore this scgi and let qp serve pages temporarily. Now our problem is configuring with Apache2. I get the following error when restarting the web server!

 sudo /etc/init.d/apache2 restart
[Fri Mar 15 16:12:50 2013] [warn] module scgi_module is already loaded, skipping
[Fri Mar 15 16:12:50 2013] [warn] module scgi_module is already loaded, skipping
[Fri Mar 15 16:12:50 2013] [warn] module scgi_module is already loaded, skipping
Syntax error on line 35 of /www/conf/apache2_proto.conf:
Invalid command 'SSLEngine', perhaps misspelled or defined by a module not included in the server configuration
Action 'configtest' failed.
The Apache error log may have more information.
   ...fail!

It turned out that I have not enabled mod_ssl! just type sudo a2enmod ssl. but that is not all, the server will look for a certificate and key! Please read the instructions to do this from help.ubuntu.com The commands I typed were (you have to do this one line at a time!)

  openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt
  openssl genrsa -des3 -out server.key 1024
  openssl rsa -in server.key -out server.key.insecure
  mv server.key server.key.secure
  mv server.key.insecure server.key
  openssl req -new -key server.key -out server.csr
  mv server.csrt server.crt
  mv server.csr server.crt

Then restart the apache server.

Site has to be rewritten again!

March 13, 2013 I upgraded to latest version of qp/qpy now named as durusworks 1.0. That was a bad move. Now the site extreme.adorio-research.org is inaccessible. We will spend time on bringing it up again. I get the following console output when running qp:

qp start    
Using Python base classes for persistence.

Import failed for site in /home/XXXX/qp_sites/proto
 No module named proto.ui.slash


Import failed for site in /home/XXXXX/qp_sites/extreme
 No module named extreme

Could not find sites in any of these places:
   /home/XXXXX/qp_sites
   /usr/local/lib/python2.7/dist-packages/qp/sites