Re: [BackupPC-devel] Posible bug

[Marc G. <m.g...@li...>]

Hi Craig,

I've resolved the email message.

However, I'm still having issues with one of the hosts taking far longer than I'd hope for to complete its first full backup. I've restarted BackupPC as you mentioned, and I've just started a full backup on the host. Straight away, it's been put into the queue. I am using BackupPC to backup 3 hosts, 2 of them are backing up perfectly, no issues whatsoever, however, there's one host that can't even complete its first full backup. I've included screenshots.

[cid:5c110e27-2d53-406a-9ade-bf2c8e5030dc]

[cid:78588b8e-6ac7-4a97-9c8f-315707d63e40]

[cid:6c1230a5-44bb-42df-81d9-570ff38cd0fb]

Could this be down to the network possible?

I would just like your opinion/advice on how I can get this server to complete its first full backup.

Thank you.

Kind regards,
Marc
________________________________
From: cr...@gm... <cr...@gm...> on behalf of Craig Barratt <cba...@us...>
Sent: 27 August 2017 22:24
To: Marc Gilliatt
Cc: Developers discussion
Subject: Re: [BackupPC-devel] Posible bug

Marc,

Ok; if you wait until the next wakeup, the old status should be removed.  Similarly if you restart BackupPC.

Craig

On Sun, Aug 27, 2017 at 12:26 PM, Marc Gilliatt <m.g...@li...<mailto:m.g...@li...>> wrote:
Hi,

Thanks for getting back to me.

I changed the hosts name by changing  the /etc/backuppc/hosts file.

And then changing it in the backuppc folder via mv old_host new_host.

Looking forward to your response.

Regards,

Marc

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: Craig Barratt via BackupPC-devel <bac...@li...<mailto:bac...@li...>>
Sent: Sunday, August 27, 2017 8:14:32 PM
To: Developers discussion
Cc: Craig Barratt
Subject: Re: [BackupPC-devel] Posible bug

Eduardo,

What did you do when you said "rename the host"?  Did you manually edit the hosts file, and mv /TOPDIR/pc/HOST_OLD to  /TOPDIR/pc/HOST_NEW?

BackupPC should remove the old status when it next reads the hosts file.  It does that on startup, on each wakeup if the mtime has changed, when it receives a HUP signal, or when it receives a "server reload" command.  So it's possible you noticed the stuck error before any of those events happened.

Craig

On Sat, Aug 19, 2017 at 8:35 PM, Eduardo Kaftanski <ek...@gm...<mailto:ek...@gm...>> wrote:

Hi,

 I think I found a small bug...

 How to reproduce:

-add a host
-try to make a backup and fail for soem reason (in my case was ssh privileges)
-rename the host

The error stays and wont go away until you create a host with the original name and then delete the host. I received warning mails until I did this.

I am running 3.3, I don't know if it was fixed in 4.x as I had not needed to upgrade yet.

thanks.



--
Eduardo Kaftanski
ed...@kd...<mailto:ed...@kd...>
ek...@gm...<mailto:ek...@gm...>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-devel mailing list
Bac...@li...<mailto:Bac...@li...>
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/