Cleanup failed to process the following paths:
- \\ourServer\ourDirectory\
In directory ‘\\ourServer\ourDirectory\images’
Error processing command ‘committed’ in ‘\\ourServer\ourDirectory\images’
Can’t move ‘\\ourServer\ourDirectory\images\.svn\props\imageName.jpg.svn-work’
to
‘\\ourServer\ourDirectory\images\.svn\prop-base\imageName.jpg.svn-base’:
Access is denied

We run VisualSVN server on Win7, serving up a local (Win 7) repository. All our files are checked out using Tortoise to a samba share under Debian. After some googling it turns out that a particular version of samba causes this error. To solve it I did a few things

1. Established what version of Samba we were running by running
   smbstatus
2. I then updated our samba by running
   apt-get update
   apt-get upgrade samba
3. I then edited smb.conf following the discussion at http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=989775, what to do can be found at http://tortoisesvn.tigris.org/faq.html#samba but basically
   nano /etc/samba/smb.conf
   find the line [global] and underneath add
   delete readonly = yes
4. Restart samba with
   /etc/init.d/samba restart

And things played nicely ever since!

If this helped you please check out the business directory I work for, for example here are Computer Consultants in Taunton, Somerset. You can get a free advert with us!

ERROR 1064 (42000) at line 3499917: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘Fatal error: Maximum execution time of 300 seconds exceeded in /usr/share/phpmyadmin/libraries/export/sql.php on line 757‘

Lots of googling kept pointing to changing the maximum execution time of Apache or PHP, by default Apache is 300 seconds (as per my error) and PHP 30 seconds. It didn’t make sense as I was doing am import at the CLI, which doesn’t use Apache or PHP. The mistake I made was using phpmyadmin to export the sql file I was trying to import. Despite the sql file downloading correctly from phpmyadmin and not reporting any errors, the last lines in my sql file were

[End of file snippet ...]
(3566987, 1225461, 4, 52530, ’2009-05-00′),
(3566988, 1225464, 4, 52530, ’2009-05-00′),
(3566989, 1577089, 4, 4422, ’2009-05-00′),
(3566990, 1762231, 8, 4422, ’2009-05-00′),
(3566991, 1768654, 8, 4422, ’2009-05-00′)<br />
<b>Fatal error</b>:  Maximum execution time of 300 seconds exceeded in <b>/usr/share/phpmyadmin/libraries/export/sql.php</b> on line <b>757</b><br />

The solution is of course to do things properly and use mysqldump -u [USERNAME] -p [DATABASE NAME] [TABLE] > [OUTPUT FILE NAME].sql.

e.g.

(find in the root and subdirectories anything with php.ini in it. And easier way to find your php.ini file is to look in php_info).

ftp [your domain/ip] – open ftp program from bash prompt
ls – list all files at ftp
!ls – list all files locally (! in front of most commands performs them on your local server)
prompt – turn prompting on/off, usefully to saving having to answer Y to each mget file
mget *.sql – (multi) get all files ending .sql
get mybackup.sql – get a single file called mybackup.sql
bye – quit ftp client

Top tip, when you ftp connect to the server ip, not the domain. When I was moving from old zclub.net server to new zclub.net server the new server resolved the domain to it’s own IP, and ftp’d to itself!

This created a tarball of my public_html folder, this was piped to the split tool, and I ended up with a lot of 200mb split archives ready for download.

This produced an md5 file for the archives, so once downloaded and reuploaded to the new server I could check their integrity. I moved all above created files (having done the same for my .sql backup) to the new server and then verified them using

If that’s reports the files are ok I rejoin the tar files using

Cat concatenates the files together, which are then piped to tar to extract them.

1. Grab the tar.gz file for the version you need, for example I used mysql-4.0.27.tar.gz which I found on an old mirror using google. Starting from the root folder
   1. debianbox:/# wget http://www.sfr-fresh.com/unix/misc/mysql-4.0.27.tar.gz -P /usr/local/src/

   This saved the version I needed in /usr/local/src/

   1. debianbox:/# tar -xvvzf /usr/local/src/mysql-4.0.27.tar.gz -C /usr/local/src/ ; rm /usr/local/src/mysql-4.0.27.tar.gz

   This extracts the folder into /usr/local/src then deletes the original archive.

2. 1. debianbox:/# cd /usr/local/src/mysql-4.0.27
3. I ran ./configure, and got the error
   1. checking for termcap functions library… configure: error: No curses/termcap library found

   To overcome this (I read this guide and) I had to run configure using the –with-named-curses-lib flag, pointing to my libncurses library, e.g. ./configure –with-named-curses-libs=/lib/libncurses.so.5. That worked, but then gave me all sorts of grief later. Having read this guide I found I should suffix ./configure with –prefix=/usr/local/mysql, so you should run./configure –with-named-curses-libs=/lib/libncurses.so.5 –prefix=/usr/local/mysql

4. 1. debianbox:/# make
   2. debianbox:/# make install
   3. debianbox:/# ./scripts/mysql_install_db
5. That completes the installation, but when I ran mysqld_safe to start the server I got
   1. debianbox:/usr/local/bin# mysqld_safe
   2. Starting mysqld daemon with databases from /usr/local/var
   3. STOPPING server from pid file /usr/local/var/debianbox.pid
   4. 080807 15:54:36  mysqld ended

   To understand why it was failing I needed to find the log file. I did this by running find . -name *.err from the root folder. The mysql error log file was called /usr/local/var/debianbox.err (debianbox is my machine name). This said

   1. 080807 18:45:09 mysqld started
   2. 080807 18:45:09 InnoDB: Started
   3. 080807 18:45:09 /usr/local/libexec/mysqld: Can't find file: './mysql/host.frm' (errno: 13)
   4. 080807 18:45:09 Fatal error: Can't open privilege tables: Can't find file: './mysql/host.frm' (errno: 13)
   5. 080807 18:45:09 Aborting
   6.  
   7. 080807 18:45:09 InnoDB: Starting shutdown…
   8. 080807 18:45:11 InnoDB: Shutdown completed
   9. 080807 18:45:11 /usr/local/libexec/mysqld: Shutdown Complete
   10.  
   11. 080807 18:45:11 mysqld ended
6. Firstly I checked the file host.frm existed
   1. debianbox:/# find / -name host.frm
   2. /var/lib/mysql/mysql/host.frm
   3. /usr/local/var/mysql/host.frm
   4. /usr/local/mysql/var/mysql/host.frm
7. errno: 13 is a permissions error. Next you need to add the mysql user and groups to the list of permissions as per the following
   1. debianbox:/# groupadd mysql
   2. debianbox:/# useradd -g mysql mysql
   3. debianbox:/# chown -R root /usr/local/mysql
   4. debianbox:/# chown -R mysql /usr/local/mysql/var
   5. debianbox:/# chgrp -R mysql /usr/local/mysql
8. That didn’t appear to help me at all, my problem was I was running mysqld_safe from the wrong location, so the relative link to ./mysql/host.frm was wrong.
   1. debianbox:/# cd /usr/local/mysql/bin
   2. debianbox:/# ./mysqld_safe –user=mysql &amp;

   Tada! I could then use the mysql client to connect and ‘show databases;’ produced an output.

9. Next up my phpmyadmin install, and anything using mysql through errors.
   1. Warning: mysql_connect() [function.mysql-connect]: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) in /myscript.php on line 4
   2. ERROR: Unable to connect to database server: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

   and when viewing phpmyadmin

   1. phpMyAdmin – error
   2. #2002 – The server is not responding (or the local MySQL server's socket is not correctly configured)

   The problem was that because I specified prefix when configuring my mysql install the default locations that apache looks in for mysql where all wrong. I found my sock file like this

   1. debianbox:/# find / -name *.sock
   2. /var/run/cups/cups.sock
   3. /tmp/mysql.sock

   Then edited my php.ini file on the line

   1. mysql.default_socket =

   to

   1. mysql.default_socket = /tmp/mysql.sock

   restarted apache, and everything (so far) works great!

http://markshrader.wordpress.com/2007/10/14/step-by-step-debian-webserver/

I actually dodged using VMWare (or Virtual PC 2007, my personal preference) and installed it on a fresh server.  To do that I just downloaded CD 1 of the Debian cd install sets (NOT the network install CD) and ran that, then used the net to download the remaining packages I needed.

NB: Just remember the packages in the setup (e.g. wget http://apache.rmplc.co.uk/httpd/httpd-2.2.4.tar.gz) are mostly out of date, so you’ll need to adjust accordingly (I used wget http://apache.rmplc.co.uk/httpd/httpd-2.2.9.tar.gz).

also try

and then run