On Thursday, December 20, 2018 at 6:34:29 AM UTC-5, Jeffrey Walton wrote:
>
> The website and wiki is down at the moment. I accidentally blew it away
> while cleaning some old cruft from root's home directory. I tried to delete
> a local backup of the site called html. The problem was, it was a link to
> /var/www/html and not a local backup.
>
> We have an offsite backup created with duplicity 0.7.18.2, which was
> released October 2018. I think the pain point (for me) will be doing the
> restore from Google Drive.
>
> I'll start the restore shortly.
>
I was looking at Google Drive cryptopp_com_backup, and it looks like
Duplicity stopped working after about two months. The last backup we have
is dated December 2017. I'm guessing we are going to lose some wiki content.
Derp...
The really annoying thing about this is, I monitor the messages in dmesg
and /var/log, and I don't recall seeing any messages about Duplicity
failures. In fact this returns 0 hits:
[root@ftpit html]# grep -iIR duplicity /var/log
[root@ftpit html]#
But our cron job is still present:
# ls /etc/cron.daily/
yum-daily.cron gdrive-backup logrotate mlocate
I can't help but wonder, who the fuck thought it was a good idea to _not_
log problems in well known locations, like dmesg or /var/log/. That fucking
genius is probably the CTO of a fortune 500 company...
Jeff
--
You received this message because you are subscribed to "Crypto++ Users". More
information about Crypto++ and this group is available at
http://www.cryptopp.com and
http://groups.google.com/forum/#!forum/cryptopp-users.
---
You received this message because you are subscribed to the Google Groups
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
