While working on my Ubuntu server with the Gitosis default setup, I ran into some problems along the way when trying to commit some changes:

1. Lost ability to update the gitosis-admin repository
2. Various python errors
3. Expected changes to gitosis.conf file but they were not being applied

Below is a description of what I did to trace down the error(s) and try to fix them.

Gitosis debug

Setting the debug into the gitosis.conf file really helped me out. To achieve this, you must have the following in your gitosis.conf file:

[gitosis]
loglevel = DEBUG

After this has been setup, you can run your push command to get a better idea of what is going wrong. Some of the problems I got are listed below with a explanation of what I did to try and resolve the issue:

gitosis.conf not updated after a push

This was a mystery. I cloned off the files from the gitosis-admin repo and then made some changes to the gitosis.conf file. Then after pushing them to the origin master, I noticed my changes did not take effect when looking at the file:

cat /srv/gitosis/.gitosis.conf

I noticed that there is a hook file in the directory of

/srv/gitosis/repositories/gitosis-admin.git/hooks/

with the filename of:

/usr/share/pyshared/gitosis/templates/admin/hooks/post-update

(Small note here, take note of the directory of where this file is because the part of /usr/share/pyshared is what you need for setting your PYTHONPATH) Running the above script occurs after applying a push to the gitosis-admin repository. I figured this was where the hold up was. After running this script manually, I got more errors (which I don’t have any more) and here is what you need to do to run this script:

sudo su
su gitosis
export set GIT_DIR="/srv/gitosis/repositories/gitosis-admin.git"
export set PYTHONPATH="/usr/share/pyshared"
/usr/share/pyshared/gitosis/templates/admin/hooks/post-update

That is, goto root account with sudo. Change users to gitosis. Set some variables (GIT_DIR, and PYTHONPATH). Then run script. This might give you more insight of to why the gitosis.conf file is not being updated.

Lost access to gitosis.conf file

This happened to me. Any commit I made to the gitosis-admin repo resulted in a permissions denied. So I logged on to my server, changed directories over to /srv/gitosis and edited the

.gitosis.conf

file and all was okay.

PERMISSION problems

Most of the time this was because the files in /srv/gitosis were not group writeable by the group of ‘gitosis’, or my account did not belong to the group ‘gitosis’, or that the ssh configuration file did not allow my account to login via ssh.

conclusion

Most of the time gitosis worked great. But sometimes, it did not work out. I hope this document will save me in the future as well as others. A really nice resource for gitosis can be found at http://ao2.it/wiki/How_to_setup_a_GIT_server_with_gitosis_and_gitweb

Cheers,

Aaron

readlink

which prints the full path of the file that the link is point at. So I came up with some bash shell code to do the job:

 Bash Script checking permissions

for f in `cat /etc/shells`
do
	#echo "checking $f"
	if [ -e $f ]; then

	if [ -L $f ]; then
		f=`readlink -f $f`
		results=`stat -c "%a" $f`
	else
		results=`stat -c "%a" $f`
	fi

	if [[ "$results" -le "755"  ]]; then
		echo "--- passed => $results - $f"
	else
		echo "-X- Failed => $results - $f"
	fi

	else
	echo "missing"
	fi
done

Explanation of bash script checking permissions

For all the text lines returned from “cat /etc/shells”, process a loop while setting each line from the text file /etc/shells as a variable of “f”. The first if statement checks to see if the file exists. The second if statement checks if the file in “f” is a link and if so, reassign the variable “f” to the returned value from running “readlink -f $f” then process the file with stat to get the octal value of permissions. If the file is not a link, try to process the file with stat to get the octal value. The next if statement checks to see the file in $f is less than or equal to 755. If the octal value is less than or equal to 755, a line will be printed indicating the file has passed the test. If the octal value is more than 755, a line will be printed indicating the file has not passed the test.

Here is a sample output from one of my servers:

--- passed => 755 - /bin/bash
--- passed => 755 - /bin/bash
--- passed => 755 - /sbin/nologin
--- passed => 755 - /bin/ash
--- passed => 755 - /bin/ash
--- passed => 755 - /bin/ksh
--- passed => 755 - /bin/ksh
--- passed => 755 - /bin/ksh
--- passed => 755 - /bin/tcsh
--- passed => 755 - /bin/tcsh
--- passed => 755 - /bin/zsh

Redmine-due-date-offset

I have many virtual hosts in Apache on a Linux server with two virtual hosts serving CFM files correctly from a ColFusion Multisite installation. But any new virtual hosts would produce the error “File not Found”.

This message is very deceiving, but I noticed that in the directory of:

/opt/jrun4/servers/cfusion/cfusion-ear/cfusion-war/

there is a CFM file, then the file is located. Bizarre! Anyways, the solution to this problem was really simple but I was thrown off by the error message. The solution is to make sure the ColdFusion user has executable rights on the directory being provided by Apache.

// how to pipe a output from child process into a webpage

// start with importing an http server
var http = require('http');
// import the spawn function
var spawn = require('child_process').spawn;

// create the server bound to port at bottom
http.createServer(function(request, response) {
	// write the header with 200 okay with content-type
	response.writeHead(200, {
		'Content-Type': 'text/plain'
	});

	// everytime there is a new request, spawn an child process
	var tail_child = spawn('tail', ['-f', '/var/log/system.log']);

	// kill tail_child everytime the connection ends to keep from many processes being created
	request.connection.on('end', function() {
		tail_child.kill();
	})

	// observe the output by binding to the data event
	//
	// because javascript is not good at handling buffers, use the function for buffering data
	tail_child.stdout.on('data', function(data) {
		// write it on the console
		console.log(data.toString());
		// send it to the browser because the browser will be waiting for the next chunk of data
		response.write(data);
	});

}).listen(4000);

 
var http = require(‘http’)

http.createServer(function(request, response) {
console.log(‘new request’);
response.writeHead(200, {
‘Content-Type’: ‘text/plain’
});
response.end(‘Hello World!’);

}).listen(4000);

http://whocallsme.com/

stat -c "%a %n" `awk -F":" '{print $6}' /etc/passwd` | awk '{
if ($1 <= 755 )
  print "--- pass","=>",$0;
else
  print "+++ Fail","=>",$0;
}'