Darcs failed: problem gzwriting file
I got this error from a darcs installed on Etch:
tim@machine:/etc$ darcs record -am 'Initial checkin'
darcs failed: problem gzwriting file: _darcs/patches/20090406120803-59231-78a2a82198e9134e0cf5600d03958044b779cc47.gz-0
tim@machine:/etc$
Google didn’t turn up anything, so I used strace as a last resort. That quickly pointed out the problem, darcs couldn’t read one of the files I tried to add. If you use strace, scroll up a bit and look for something like this:
open("/etc/postgresql/8.1/main/pg_ident.conf", O_RDONLY|O_NONBLOCK|O_NOCTTY) = -1 EACCES (Permission denied)
That’s the file I either needed to remove from the record or add to boring (and remove it from the pending file). Or make readable.
Hope this helps someone.
Tags: a_bit_strange, credentials, debian, fix, lenny, mysql, permissions
1 comment
MySQL on Lenny and permissions
Ok, had something strange that I think is worth a share. I just upgraded a virtual machine to Lenny and installed MySQL and phpMyAdmin and apache and the like. Created a user for a Django project I’m working on and it couldn’t connect. I tried resetting the password several times, didn’t help. Then, out of frustration, I tried connecting without a password and… it worked!
Apparantly, by default, the MySQL in Lenny created access rules that allow all local users to access the database without a password. These have priority over the specific user controls. A bit unexpected and I suspect others to run into this. Could make you search for a problem if you’re installing a shared webhosting machine with a local MySQL database.
Solution:
delete from mysql.user where User='';
