commit fails, *.pack not found and upload directory is missing

On Mon, 2008-09-15 at 08:22 +0000, Tim wrote:
> Public bug reported:
>
> Commit always fails on my project:
>
> > bzr commit
>
> Unable to load plugin u'xmloutput' from u'C:/Programme/Bazaar/plugins'
>
> bzr: ERROR: No such file: 'js7noyb1j0dt5uv6ikvi.pack': [Errno 2] No such
> file or directory

Hi Tim,

Could you please attach one of the stanzas of your bzr log file
from when you see this error?

"bzr version" will tell you where that is as ""Bazaar log file".

Thanks,

James

7.662 Traceback (most recent call last):
  File "bzrlib\commands.pyo", line 857, in run_bzr_catch_errors
  File "bzrlib\commands.pyo", line 797, in run_bzr
  File "bzrlib\commands.pyo", line 499, in run_argv_aliases
  File "bzrlib\builtins.pyo", line 2290, in run
  File "bzrlib\decorators.pyo", line 192, in write_locked
  File "bzrlib\workingtree_4.pyo", line 242, in commit
  File "bzrlib\decorators.pyo", line 192, in write_locked
  File "bzrlib\mutabletree.pyo", line 197, in commit
  File "bzrlib\commit.pyo", line 355, in commit
  File "bzrlib\branch.pyo", line 316, in get_commit_builder
  File "bzrlib\repository.pyo", line 996, in get_commit_builder
  File "bzrlib\repository.pyo", line 1044, in start_write_group
  File "bzrlib\repofmt\pack_repo.pyo", line 1791, in _start_write_group
  File "bzrlib\repofmt\pack_repo.pyo", line 1611, in _start_write_group
  File "bzrlib\repofmt\pack_repo.pyo", line 274, in __init__
  File "bzrlib\transport\local.pyo", line 317, in open_write_stream
  File "bzrlib\transport\local.pyo", line 280, in put_bytes_non_atomic
  File "bzrlib\transport\local.pyo", line 229, in _put_non_atomic_helper
  File "bzrlib\transport\__init__.pyo", line 306, in _translate_error
NoSuchFile: No such file: '1vtdewvp0v0f4ctl5ctx.pack': [Errno 2] No such file or directory

Hello,
did my last comment help you to tracke the error?

Kind regards and big shouts to the BZR developers. Incredible progress to be observed...

Hi,

It looks like it is having a problem when trying to write,
do you have a .bzr\repository\packs\ directory?

If you don't have a .bzr\repository\ directory then "bzr info"
should help you work out where that lives.

Thanks,

James

Hello,
I found this:

.bzr\repository\packs\3775b4b52e9d090fce0be8fcfe33ff0f.pack

What do I do next?

May this be a system issue?
I was using this repository on Win XP.

I'm curious if this is a permissions issue.

It looks like we are opening a file and trying to write to it, and then getting an error about the file not being there.

The specific directory is .bzr\repository\upload
(We write to a staging area before renaming it into the final location.)

I can also tell it is a temporary name because it has non hex-digits. (We md5 hash the file and rename it to the md5 name in the end.)

So what information can I provide?

Can you check the permissions on '.bzr\repository' and '.bzr\repository\upload' ? Are you able to create a file in ".bzr\repository\upload"?

Are you out of disk space?

I suppose it is possible that one of the directories is also missing, but that would be unusual. (If .bzr\repository\upload is missing, try creating it and see if that fixes the problem.)

Hello,
* no problems with disk space. still some GB left.
* the ".bzr\repository\upload" was not there, I created it.
* I can write in all directories under ".bzr"

It it really strange because I checked it out from an repository on the server where I uploaded it to from another computer with no problems.

* May there be a Windows/Linux switching issue?
* May it be that the locakl repositry format is not the right one?

Thanks in advance.

Please help me.
how do I create "3775b4b52e9d090fce0be8fcfe33ff0f.pack" or let the program go on here?

I would really like to commit the new code.

Hello, the problem persists in version 1.7

Hello,
today this occured again on another directory/repository:

D:\>bzr commit
bzr: ERROR: No such file: 'xqy6l51imqufu8x0v6iq.pack': [Errno 2] No such file or directory

D:\>bzr version
Bazaar (bzr) 1.8
  Python interpreter: C:\Programme\pythonxy\python\python.exe 2.5.2
  Python standard library: C:\Programme\qgis\python
  bzrlib: C:\Programme\pythonxy\python\lib\site-packages\bzr-1.8-py2.5-win32.egg\bzrlib

Please provide me with a hint here. It blocks my commits to the central repository.

Thanks.

Can you please create a new repository where this problem occurs, and then attach it as a zip file to this bug?

On Mon, 2008-10-27 at 13:06 +0000, Tim wrote:
> Hello,
> today this occured again on another directory/repository:
>
>
> D:\>bzr commit
> bzr: ERROR: No such file: 'xqy6l51imqufu8x0v6iq.pack': [Errno 2] No such file or directory
>
> D:\>bzr version

Can you do 'bzr info -v' here please.

Thanks,
Rob
--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

If this is an unfinished pack file, shouldn't it be called *.fetch and stored in the uploads directory?

OK, so please check again if you have a .bzr/repository/upload directory inside the server.

If not, did someone delete it? Could it be that some antivirus software blocked or deleted it, or someone deleted it to save space?

Actually, we don't print enough data in info; Martin and I were chatting about this - we have a hunch that it might be a virus checker removing the 'upload' directory because its 'suspicious'.

Recreate the .bzr\repository\upload directory for broken repositories and it will work; you probably need to find an option in your virus checker to fix this overly enthusiasic deletion of important directories.

> OK, so please check again if you have a .bzr/repository/upload directory inside the server.
On any project this occured on, the .bzr/repository/upload directory was missing (locally).

> If not, did someone delete it? Could it be that some antivirus software blocked or deleted it, or someone deleted it to save space?
* No one deleted it for space issues.
* I will have to find out how the virus scanner works.

Anyway, may there be an automatic option in bzr to check for existence of the .bzr/repository/upload directory and create it automatically when doing bzr commit/update?
Or raise a exception with a more helpful message "Please check if .bzr/repository/upload directory is in place, if not create it."
This would be very helpful.

Thanks for your help so far.

Additionally I add the information that R. Collins requested (Re: [Bug 270405] Re: commit fails, *.pack not found (permalink) - https://bugs.launchpad.net/bzr/+bug/270405/comments/15)

#############################

C:\myprogram>bzr info -v
Checkout (format: pack-0.92)
Location:
       checkout root: .
  checkout of branch: ftp://<email address hidden>/myprogram

Format:
       control: Meta directory format 1
  working tree: Working tree format 4
        branch: Branch format 6
    repository: Packs containing knits without subtree support

In the working tree:
       129 unchanged
         0 modified
         0 added
         0 removed
         0 renamed
         0 unknown
         1 ignored
        22 versioned subdirectories

Branch history:
         3 revisions
         3 committers
       159 days old
   first revision: Wed 2008-05-21 18:02:45 +0200
  latest revision: Tue 2008-10-28 10:09:22 +0100

Repository:

         3 revisions

On Tue, Oct 28, 2008 at 8:13 PM, Tim <email address hidden> wrote:
>> OK, so please check again if you have a .bzr/repository/upload directory inside the server.
> On any project this occured on, the .bzr/repository/upload directory was missing (locally).
>
>> If not, did someone delete it? Could it be that some antivirus software blocked or deleted it, or someone deleted it to save space?
> * No one deleted it for space issues.
> * I will have to find out how the virus scanner works.
>
> Anyway, may there be an automatic option in bzr to check for existence of the .bzr/repository/upload directory and create it automatically when doing bzr commit/update?
> Or raise a exception with a more helpful message "Please check if .bzr/repository/upload directory is in place, if not create it."
> This would be very helpful.
>
> Thanks for your help so far.

Maybe we should. I'd like to work out why it was missing first. In
general if something or someone else is deleting directories from
inside our repository all bets are off.

--
Martin <http://launchpad.net/~mbp/>

Also seeing this on pushes, in this case two concurrent pushes to the same shared repository - apparently the lock was given up by the other process, and then the error message was printed by this one:

df@cassafinn ~/bzr/mysql-5.1-build $ bzr push --remember bzr+ssh://<censored>/bzrroot/server/mysql-5.1-build/
Unable to obtain lock bzr+ssh://<censored>/bzrroot/server/.bzr/repository/lock
held by <censored> on host <censored> [process #3399]
locked 18 seconds ago
Will continue to try until 14:30:01, unless you press Ctrl-C
If you're sure that it's not being modified, use bzr break-lock bzr+ssh://<censored>/bzrroot/server/.bzr/repository/lock
bzr: ERROR: No such file: '/bzrroot/server/.bzr/repository/packs/026e4f1f327a6a4f29caa775af437528.pack'

Daniel, that looks like a different bug - please file a new bug and include the traceback from .bzr.log.

Some bugs to do with concurrent pushes were fixed a few months ago so please retest this with 1.18.1 or 2.0rc2

Just to try to move this along:

Tim, thanks for all your test feedback.

Does this happen 100% of the time? Is there any pattern? It looks like some other things are working for you. If you create the uploads directory does it disappear again later, or does it keep working?