When I was troubleshooting webwork + shibboleth integration, everything works fine except the wrong target URL for Shibboleth lazy session initialization generated by webwork shibboleth module. Webwork Shibboleth module uses perl CGI to get the URL of for redirecting target. The URL was always https://server/webwork2 instead of https://server/webwork2/COURSENAME, when I click on a course to login. I did some digging and found out that the SCRIPT_NAME was set to /webwork2 instead of /webwork2/COURSENAME.

The root of this problem is related to DocumentRoot was set incorrectly in apache config file. The DocumentRoot was set to /www_data/webwork2 where it should be /www_data. Another way to solve the problem is add Alias /webwork2 /www_data/webwork2 to map the path to correct local directory.

The error message:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit ‘replace facts’ command for ipeerdbprod1.ctlt.ubc.ca to PuppetDB at puppet.ctlt.ubc.ca:8081: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [unable to get local issuer certificate for /CN=puppet.ctlt.ubc.ca]

Cause:
Accidentally executed – puppet cert –clean –all

Fix:
mv /etc/puppetdb/ssl /etc/puppetdb/ssl.bak
/usr/sbin/puppetdb-ssl-setup -f
/sbin/service puppetdb restart

Check /var/log/puppetdb/puppetdb.log for any error.

I was having so much trouble with AnyConnect 2.5.x.

• Sometime after it connect, nothing received out (you can still see package sends out). Basically you lost connection.
• The split traffic doesn’t work. I would like to be able to access my LAN while I’m on VPN. I couldn’t figure out how it works.
• It replace my /etc/hosts file silently. You can work around it by editing /etc/hosts.ac. Sometime if I forget, my hosts file will be lost.
• It doesn’t save the username and password. Have to retype them every time.
• New version 3.x doesn’t solve the problem….

So I decided to switch to OpenConnect, which is an open source client for Cisco AnyConnect SSL VPN. (http://www.infradead.org/openconnect/). Under OSX, it can be easily installed through MacPorts (http://www.macports.org/).

1. Install MacPort (http://www.macports.org/install.php)
2. Install OpenConnect

   sudo port install openconnect

3. Connect with OpenConnect

   sudo openconnect -u USERNAME https://YOUR_VPN_SERVER

Notes:

• At the time of writing this blog, the version of openconnect on MacPorts is 3.18 and the latest version is 4.07. To use the latest version, I just replaced the Portfile in my ports repo. I also submitted the new version to MacPorts. Hopefully by the time you install it, it will be the latest version. If not, you can always download my Portfile from here (https://raw.github.com/xcompass/macports/master/net/openconnect/Portfile). Then copy the file to

  /opt/local/var/macports/sources/rsync.macports.org/release/ports/net/openconnect

  Or create a local repo as described here: http://guide.macports.org/#development.local-repositories

• To split the traffic, use this script: http://lists.infradead.org/pipermail/openconnect-devel/2012-June/000606.html. Replace the ROUTES at the top and path to vpnc-script at the bottom (should be /opt/local/etc/vpnc/vpnc-script for vpnc installed through MacPorts)

When doing the integration testing, we always want to use the test database. However, it is a little bit difficult with CakePHP when DB ACL is enabled in your application.

CakePHP try to be smart. It tries to create separate tables (prefixed with test_suite_) when we have our fixtures set up. However, DB ACL uses separate settings in Configure class:
Configure::read('Acl.database');

So when we do testing, we need to have an extra line in our setup before we run any test.
Configure::write('Acl.database', 'test_database');

Fixture setting may be needed as well.

Some posts mentioned using

App::import('User');
$user = new User();


The issue with this approche is when you access the database, it uses default configuration. There is no problem until you are testing the class with a test database configuration or asking CakePHP to generate the test_suite configuration.

The correct way of doing this is:
$modelName = ClassRegistry::init('ModelName');

A quick note to install those stuff.

Install EPEL repo (http://fedoraproject.org/wiki/EPEL).
yum install python26 python-devel subversion subversion-devel
Install setuptools
easy_install trac
wget http://subversion.tigris.org/downloads/subversion-1.6.17.tar.bz2
tar xjvf subversion-1.6.17.tar.bz2
cd subversion-1.6.17
wget http://www.sqlite.org/sqlite-amalgamation-3.6.13.tar.gz
tar xzvf sqlite-amalgamation-3.6.13.tar.gz
mkdir sqlite-amalgamation
cp sqlite-3.6.13/sqlite3.c /home/sysadmin/subversion-1.6.17/sqlite-amalgamation/sqlite3.c
cd /usr/bin
rm python
ln -s python2.6 python
cd –
./configure
make
make swig-py
make install-swig-py
cp -R /usr/local/lib/svn-python/libsvn /usr/lib/python2.6/site-packages/
cp -R /usr/local/lib/svn-python/svn /usr/lib/python2.6/site-packages/

/sbin/service httpd restart

It turned out CakePHP failed to link GroupSet and Groups. No go…..

For example, GroupSet hasMany Groups and Group hasAndBelongsToMany users. They can be saved using one saveAll call. No need to deal with the IDs.

One level hasMany saveAll looks like:

Array
(
    [GroupSet] => Array
        (
            [name] => "Title"
        )
    [Group] => Array
        (
            [0] => Array
                (
                    [name] => On Gwoo the Kungwoo
                )
            [1] => Array
                (
                    [name] => More on Gwoo
                )
        )
)

The multiple levels hasMany (or HABTM) should looks like this:

Array
(
    [GroupSet] => Array
        (
            [name] => "Title"
        )
    [Group] => Array
        (
            [0] => Array
                (
                    [Group] => Array
                             (

                              [name] => Group1

                             )
                    [GroupMember] => Array
                       (
                          [0] => Array
                              (
                                [user_id] => 1
                              )
                          [1] => Array
                              (
                                [user_id] => 2
                              )
         )
         [1] => Array
                (
                    [Group] => Array
                             (
                              [name] => Group2
                             )
                    [GroupMember] => Array
                       (
                          [0] => Array
                              (
                                [user_id] => 3
                              )
                          [1] => Array
                              (
                                [user_id] => 4
                              )
                        )

                )
 )
					

To remove a file or folder and all history from an SVN repository, create a dump of the existing repository and filter out the unwanted file or folder. Then create a new repository to replace the existing repository.

The process to completely remove a file or folder from a repository involves several steps. Use the following steps to completely remove an existing file or folder and all history from your current live repository:
Create a dump of the existing repository:

svnadmin dump [path_to_repo] > dumpfile1


Filter out the unwanted file/folder:

svndumpfilter exclude [path_to_file/folder] < dumpfile1 > filtered_dumpfile


Create a new repository, to swap for the live repository:

svnadmin create repo_temp

Load the filtered dumpfile to new repository:

svnadmin load repo_temp < filtered_dumpfile

Verify the new repository and replace the live repo with the new repository:

rm [path_to_live_repo] -rfmv repo_temp live_repo


From: http://help.collab.net/index.jsp?topic=/faq/removefile.html
Reference: http://svnbook.red-bean.com/en/1.0/ch05s03.html