Couldn't mount destination directory - Reinstalled Won't Run

Bug #425342 reported by tmort
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nssbackup
Invalid
Undecided
Unassigned

Bug Description

Initially I couldn't get NSSBackup to mount the destination directory. It connected to the remote ftp server and actually created a directory with a name, date, time but didn't copy any files to it.

I got the following error message:

I set the report option to error and got a log:

NSSBackup 'Default Profile' Logger

==============

2009-08-31 19:02:51,230 - ERROR - nssbackupd.py:__onError(226) - Given copy destination '/<email address hidden>/2009-08-31_18.57.11.754941.localhost.localdomain.ful' does not exist.
2009-08-31 19:02:51,266 - ERROR - nssbackupd.py:__onError(227) - Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/nssbackup/nssbackupd.py", line 217, in run
    self.__bm.makeBackup()
  File "/usr/lib/python2.6/site-packages/nssbackup/managers/BackupManager.py", line 364, in makeBackup
    self.__actualSnapshot.commit()
  File "/usr/lib/python2.6/site-packages/nssbackup/util/Snapshot.py", line 344, in commit
    self.__makebackup()
  File "/usr/lib/python2.6/site-packages/nssbackup/util/Snapshot.py", line 538, in __makebackup
    TAR.makeTarFullBackup(self)
  File "/usr/lib/python2.6/site-packages/nssbackup/util/tar.py", line 372, in makeTarFullBackup
    Util.nssb_copy( tmp_snarfile, snarfile )
  File "/usr/lib/python2.6/site-packages/nssbackup/util/__init__.py", line 113, in nssb_copy
    prep_src, prep_dst = _prepare_nssb_copy(src, dst)
  File "/usr/lib/python2.6/site-packages/nssbackup/util/__init__.py", line 160, in _prepare_nssb_copy
    raise IOError("Given copy destination '%s' does not exist." % _dst_dir)
IOError: Given copy destination '/<email address hidden>/2009-08-31_18.57.11.754941.localhost.localdomain.ful' does not exist.

I noticed that some of the errors related to python. Since I originally installed this I did a yum install python*. Although I used yum initially to install NSSBackup I thought it might be missing some python dependency. I did a yum remove nssbackup and then did a yum install nssbackup. Now it won't run at all. If I select it it says it is starting for a few seconds and then it closes and never does???

I am running Fedora 11 and since I can't open it I don't know the version of NSSBackup although I just installed it today (9/6/2009) using yum

the nssbackup.log for today as well as the .old log are empty

Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :

hi,

can you launch it through a command line and see what is written there ?
There might not be anything written in the logs but I believe something will be wirtten on the shell when you launch it.

If this shows nothing, you should try to rename ~/.config/nssbackup/nssbackup.conf to nssbackup.conf.old and try to relaunch the gui. This would assert if it's a configuration issue.

Changed in nssbackup:
assignee: nobody → Oumar Aziz OUATTARA (wattazoum)
status: New → Incomplete
Changed in nssbackup:
milestone: none → release0.2
Revision history for this message
tmort (tom-mort) wrote :

Here is the command line text:

[tmort@localhost nssbackup]$ sh nssbackup
2009-10-17 13:10:09,578 - ERROR - nssbackupd.py:__onError(226) - We are unable to mount the target dir !
2009-10-17 13:10:09,599 - ERROR - nssbackupd.py:__onError(227) - Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/nssbackup/nssbackupd.py", line 217, in run
    self.__bm.makeBackup()
  File "/usr/lib/python2.6/site-packages/nssbackup/managers/BackupManager.py", line 261, in makeBackup
    self.__fusefam.initialize()
  File "/usr/lib/python2.6/site-packages/nssbackup/managers/FuseFAM.py", line 197, in initialize
    self.__mount(self.__config.get("general","target"))
  File "/usr/lib/python2.6/site-packages/nssbackup/managers/FuseFAM.py", line 129, in __mount
    raise SBException("We are unable to mount the target dir !")
SBException: We are unable to mount the target dir !

Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :

oki, this is certainly due to your configuration file.
According to the way you launch it, you are using the configuration file in /home/tmort/.config/nssbackup/nssbackup.conf .

In that configuration you might have the target directory using a plugin. And the plugin might not be installed. Can you paste the "general" section of the configuration file (after removing sensitive information of course) ?

Revision history for this message
tmort (tom-mort) wrote :

[general]
splitsize = 0
target = ftp://tmort:***********.onlinestoragesolution.net/
format = gzip
mountdir = /home/tmort/.local/share/nssbackup/mountdir
purge = 30
maxincrement = 7
lockfile = /home/tmort/.local/share/nssbackup/nssbackup.lock

[report]
from = NSsbackup Daemon <email address hidden>

[exclude]

Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :

Did it already worked once ?
I suspect a problem of packaging in Fedora.
Is the ftp plugin installed ?
Is fuse working on fedora ?
can you install curlftpfs on it ?

Revision history for this message
tmort (tom-mort) wrote :

Did it already worked once ?

Yes it installed once and I could configure it and it looked like it created a file with no contents. I later did yum install python* because I saw the error message made refeernce to python. I noticed that some of the errors related to python. Since I originally installed this I did a yum install python*. Although I used yum initially to install NSSBackup I thought it might be missing some python dependency. I did a yum remove nssbackup and then did a yum install nssbackup. Now it won't run at all.

I suspect a problem of packaging in Fedora.

Is the ftp plugin installed ? Yes and up to date

Is fuse working on fedora ? Installed and up to date (don't know ow to test)

can you install curlftpfs on it ? Already installed and up to date

Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :

Thanks for the answer.

can you change your configuration file to set something like the following ?:

[log]
file = /home/tmort/.local/share/nssbackup/nssbackup.log
level = 10

The important part is the log level to set to 10.
Then you relaunch the build, conceal your password from the log file and attach it here.

Looking into the code, I see that putting the loglevel to ERROR can hide the real cause of this problem.

Changed in nssbackup:
status: Incomplete → In Progress
importance: Undecided → Medium
Revision history for this message
tmort (tom-mort) wrote :
Download full text (44.6 KiB)

Here is the last part from the terminal. It overfilled the terminal.

g up the link '/home/tmort/.cxoffice/win98/desktopdata/cxassoc/tagged_icons/cxoffice-42aee93b-0d87-4477-bddd-58b0d9830616.application_x-crossover-xlt.xpm' !
2009-10-18 09:37:13,763 - DEBUG - BackupManager.py:checkForExclude(458) - backing up the link '/home/tmort/.cxoffice/win98/desktopdata/cxassoc/tagged_icons/cxoffice-42aee93b-0d87-4477-bddd-58b0d9830616.application_x-crossover-gim.xpm' !
2009-10-18 09:37:13,764 - DEBUG - BackupManager.py:checkForExclude(458) - backing up the link '/home/tmort/.cxoffice/win98/desktopdata/cxassoc/tagged_icons/cxoffice-42aee93b-0d87-4477-bddd-58b0d9830616.application_x-crossover-gix.xpm' !
2009-10-18 09:37:13,765 - DEBUG - BackupManager.py:checkForExclude(458) - backing up the link '/home/tmort/.cxoffice/win98/desktopdata/cxassoc/tagged_icons/cxoffice-42aee93b-0d87-4477-bddd-58b0d9830616.application_x-crossover-xlb.xpm' !
2009-10-18 09:37:13,766 - DEBUG - BackupManager.py:checkForExclude(458) - backing up the link '/home/tmort/.cxoffice/win98/desktopdata/cxassoc/tagged_icons/cxoffice-42aee93b-0d87-4477-bddd-58b0d9830616.application_x-crossover-wab.xpm' !
2009-10-18 09:37:13,766 - DEBUG - BackupManager.py:checkForExclude(458) - backing up the link '/home/tmort/.cxoffice/win98/desktopdata/cxassoc/tagged_icons/cxoffice-42aee93b-0d87-4477-bddd-58b0d9830616.application_x-crossover-wsc.xpm' !
2009-10-18 09:37:13,767 - DEBUG - BackupManager.py:checkForExclude(458) - backing up the link '/home/tmort/.cxoffice/win98/desktopdata/cxassoc/tagged_icons/cxoffice-42aee93b-0d87-4477-bddd-58b0d9830616.application_x-crossover-mdt.xpm' !
2009-10-18 09:37:13,768 - DEBUG - BackupManager.py:checkForExclude(458) - backing up the link '/home/tmort/.cxoffice/win98/desktopdata/cxassoc/tagged_icons/cxoffice-42aee93b-0d87-4477-bddd-58b0d9830616.application_x-crossover-wizhtml.xpm' !
2009-10-18 09:37:13,768 - DEBUG - BackupManager.py:checkForExclude(458) - backing up the link '/home/tmort/.cxoffice/win98/desktopdata/cxassoc/tagged_icons/cxoffice-42aee93b-0d87-4477-bddd-58b0d9830616.application_x-crossover-mdn.xpm' !
2009-10-18 09:37:13,789 - DEBUG - BackupManager.py:checkForExclude(458) - backing up the link '/home/tmort/.cxoffice/win98/desktopdata/cxassoc/tagged_icons/cxoffice-42aee93b-0d87-4477-bddd-58b0d9830616.application_x-crossover-oft.xpm' !
2009-10-18 09:37:13,790 - DEBUG - BackupManager.py:checkForExclude(458) - backing up the link '/home/tmort/.cxoffice/win98/desktopdata/cxassoc/tagged_icons/cxoffice-42aee93b-0d87-4477-bddd-58b0d9830616.application_x-crossover-xll.xpm' !
2009-10-18 09:37:13,790 - DEBUG - BackupManager.py:checkForExclude(458) - backing up the link '/home/tmort/.cxoffice/win98/desktopdata/cxassoc/tagged_icons/cxoffice-42aee93b-0d87-4477-bddd-58b0d9830616.application_x-crossover-hta.xpm' !
2009-10-18 09:37:13,791 - DEBUG - BackupManager.py:checkForExclude(458) - backing up the link '/home/tmort/.cxoffice/win98/desktopdata/cxassoc/tagged_icons/cxoffice-42aee93b-0d87-4477-bddd-58b0d9830616.application_x-crossover-ade.xpm' !
2009-10-18 09:37:13,792 - DEBUG - BackupManager.py:checkForExclude(458) - backing up the link '/home/tmort/.cxo...

Revision history for this message
tmort (tom-mort) wrote :
Download full text (4.7 KiB)

Here's some more, it hadn't finished yet:

2009-10-18 09:38:09,276 - DEBUG - tar.py:__prepareTarCommonOpts(260) - Common TAR options : ['-cS', '--gzip', '--directory=/', '--ignore-failed-read', '--<email address hidden>/2009-10-18_09.37.00.296819.localhost.localdomain.ful/includes.list.tmp', '--exclude<email address hidden>/2009-10-18_09.37.00.296819.localhost.localdomain.ful/excludes.list.tmp', '--<email address hidden>/2009-10-18_09.37.00.296819.localhost.localdomain.ful/files.tar.gz']
2009-10-18 09:38:09,845 - DEBUG - tar.py:makeTarFullBackup(356) - Snapshot's snarfile: /<email address hidden>/2009-10-18_09.37.00.296819.localhost.localdomain.ful/files.snar
2009-10-18 09:38:09,846 - DEBUG - tar.py:makeTarFullBackup(357) - Temporary snarfile: /home/tmort/.local/share/nssbackup/tmp/files.snar
2009-10-18 09:38:11,149 - DEBUG - __init__.py:launch(211) - Lauching : ['tar', '-cS', '--gzip', '--directory=/', '--ignore-failed-read', '--<email address hidden>/2009-10-18_09.37.00.296819.localhost.localdomain.ful/includes.list.tmp', '--exclude<email address hidden>/2009-10-18_09.37.00.296819.localhost.localdomain.ful/excludes.list.tmp', '--<email address hidden>/2009-10-18_09.37.00.296819.localhost.localdomain.ful/files.tar.gz', '--listed-incremental=/home/tmort/.local/share/nssbackup/tmp/files.snar']
2009-10-18 09:43:23,925 - DEBUG - tar.py:makeTarFullBackup(368) - TAR Output :
2009-10-18 09:43:24,041 - ERROR - nssbackupd.py:__onError(226) - Given copy destination '/<email address hidden>/2009-10-18_09.37.00.296819.localhost.localdomain.ful' does not exist.
2009-10-18 09:43:24,102 - ERROR - nssbackupd.py:__onError(227) - Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/nssbackup/nssbackupd.py", line 217, in run
    self.__bm.makeBackup()
  File "/usr/lib/python2.6/site-packages/nssbackup/managers/BackupManager.py", line 364, in makeBackup
    self.__actualSnapshot.commit()
  File "/usr/lib/python2.6/site-packages/nssbackup/util/Snapshot.py", line 344, in commit
    self.__makebackup()
  File "/usr/lib/python2.6/site-packages/nssbackup/util/Snapshot.py", line 538, in __makebackup
    TAR.makeTarFullBackup(self)
  File "/usr/lib/python2.6/site-packages/nssbackup/util/tar.py", line 372, in makeTarFullBackup
    Util.nssb_copy( tmp_snarfile, snarfile )
  File "/usr/lib/python2.6/site-packages/nssbackup/util/__init__.py", line 113, in nssb_copy
    prep_src, prep_dst = _prepare_nssb_copy(src, dst)
  File "/usr/lib/python2.6/site-packages/nssbackup/util/__init__.py", line 160, in _prepare_nssb_copy
    raise IOError("Given copy destination '%s' does not exist." % _dst_dir)
IOError: Given copy ...

Read more...

Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :

You shouldn't have copied this directly into a comment. You should have attached it as a file or you should have used http://pastebin.ubuntu.com/. This kind of comments might make use loose information.

Anyway, this error is not the same as the other one. :-/

Revision history for this message
tmort (tom-mort) wrote :

I realized that afte I posted it. Can it be deleted?

Revision history for this message
tmort (tom-mort) wrote :

If I open from the gui an if I do a test of the remote directory now I get an error:

Failed : [Errno 17] File exists: '/<email address hidden>'

and also it says

The selected destinations is not writable with currrent permissions. The backups cannot be written there

Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :

it looks like the mount point stopped working and wasn't unmounted nor removed. that's why you're having issues after the test.

I'll investigate this deeper.

Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :
Revision history for this message
tmort (tom-mort) wrote :

Have you made any progress on this?

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Is this still an issue?

Changed in nssbackup:
status: In Progress → Incomplete
importance: Medium → Undecided
assignee: Oumar Aziz OUATTARA (wattazoum) → nobody
milestone: 0.2 → none
Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Setting status to Expired/Invalid.

Changed in nssbackup:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.