On Sat, Jan 5, 2013 at 8:19 AM, Travis Schwenke
<travis.schwenke AT gmail DOT com> wrote:
> I am obviously missing something very fundamental..
>
> Changed Password (check)  [sudu su - was the trick, then could run commands
> correctly]
>
> Then the issue..  I went and and changed the TopDir setting and did the mv
> command..  Now the server isn't running.  I tried to restart, no luck, tried
> to mv things back, no luck.  I think my misunderstanding is the filesystem
> and mounts...
>
> /dev/sda6   :  mounted as root filesystem
> /dev/sda9   :  mounted as /data01
> /dev/sda1   :  mounted as /home (don't think that matters in this case)
>
> I did NOT try to restart the apache2 service.
>
> Error: Unable to connect to BackupPC server

That's not going to work until the backuppc server starts...

>
> 2013-01-05 09:12:51 Can't create a test hardlink between a file in
> /var/lib/backuppc/pc and /var/lib/backuppc/cpool.  Either these are
> different file systems, or this file system doesn't support hardlinks, or
> these directories don't exist, or there is a permissions problem, or the
> file system is out of inodes or full.  Use df, df -i, and ls -ld to check
> each of these possibilities. Quitting...

So $TopDir isn't changed?   Or you are running a version earlier than
3.2.0?   Or permissions are wrong.  Or all of the above.

> So, I think the mv must be the issue and it didn't like something...  When I
> tried to move it back, I got an error on the log directory.

I thought most packaged versions would re-create everything in the
archive partition if it doesn't exist and permissions permit it.

> I have seen the one page about moving and copying, but some parts are not
> making sense, I think it must be due to some links.
>
> I don't want to uninstall and reinstall it all, as I want to understand how
> to do this correctly.  Maybe that is easiest and then go from there.

The first thing to understand is that if you started with the
sourceforge tarball you would run an install script that lets you put
things anywhere you want.   However, in the distribution-packaged
versions the packager has already done this step and made the decision
according to the distribution guidelines and you are trying to 2nd
guess it.   I'd do the re-install to get back to a known-good point.
But, my best guess at what is wrong is that you have a symlink at
/var/lib/backuppc pointing to something with the wrong
ownership/permissions.   If you try to create that hardlink yourself
as the backuppc user you might get a better diagnostic message.

-- 
   Les Mikesell
     lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122912
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/