svn "Killed by signal 15."

Recently, a bunch of this error messages started popping out whenever we do a svn up.

[n@g ~]$ svn up /opt/n/
At revision 1492.
Killed by signal 15.

As we sync our script directory across a bunch of machines using svn, the output of svn gets sent in cron emails. The large amount of emails we were getting was really annoying. AFAIK, this bug only happened after subversion-1.6.11-7.el5.

What to do? Piping stdout and stderr to /dev/null fixed it

[n@g ~]$ svn up /opt/n/ > /dev/null 2>&1
[n@g ~]$

This is probably not good practice, but until CentOS fixed it, we have no choice.

Note: This is not the same bug in 1.6.6, of which the same symptoms are similar.

[n@g ~]$ svn up /opt/n/
At revision 1492.
Killed by signal 15.
[n@g ~]$ grep "ssh =" ~/.subversion/config
ssh = $SVN_SSH ssh -q

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s