- #MAC OS CARBON COPY CLONER UPDATE#
- #MAC OS CARBON COPY CLONER FULL#
- #MAC OS CARBON COPY CLONER PRO#
- #MAC OS CARBON COPY CLONER SOFTWARE#
Tail -f /usr/local/var/log/httpd/error_log
#MAC OS CARBON COPY CLONER PRO#
Reviewed all the steps when I configured the AMP-based webserver via Brew – no problems, all OK.īefore I resign my fate to begin 2021 with long hours recoding my webserver for macOS Big Sur (and, yes, I need to buy a new M1 processor-based Mac since my 2016-bought “trashcan” Mac Pro (Late 2013) may be compatible only in 2 or 3 more future macOS releases), I tried again to stop, start and restart the webserver using Terminal.Īgain, no issues until I tried to diagnose for any error when Apache starts via the Terminal command: At, I fiddled with different domain name resolver configurations -only to find out that my previous setting was correct. Checked the IP gateway/Dynamic DNS -the one that renders your dynamic IP address given by your ISP to a static IP address needed to host a website at your choice location- for incorrect settings. Checked the router, access points & all settings (especially port forwarding) - OK.Ģ). Here’s what I did to troubleshoot the issue:ġ). To maintain my presence on the Web, I switched over to an older version of my website that runs on a Mac mini, then tackled the issue: why did the backup webserver on the Mac Pro fail to connect to the Internet when the source drive worked? Everything else worked properly on the backup drive except the ability of my AMP (Apache-MySQL-PHP)-based webserver to connect to the Web.
#MAC OS CARBON COPY CLONER FULL#
How is this possible? Aren’t backups, especially a cloned version, bit-by-bit copies of their originals? A bit alarmed now because of the looming task of debugging the entire webserver application, I hied off to the kitchen to brew a full carafe of my favorite blend.
While all my web pages now worked- at least, while I re-tested under RW- after I reverted to prior versions using the backup SSD, this time, a bigger issue came up – my website is no longer accessible on the Web! And, the backup worked, as usual, like a champ. So, I launched System Preferences > Startup Disk > switched to the backup SSD, and restarted the Mac Pro. I had scheduled the backup to run early Sunday of every week and that should contain the exact replica of my entire main boot SSD before I did those updates!
#MAC OS CARBON COPY CLONER SOFTWARE#
I have an ever-dependable-for Mac-only backup in Carbon Copy Cloner – I had been using this backup software since time immemorial.
#MAC OS CARBON COPY CLONER UPDATE#
This simple Stacks update rendered my entire website useless – always backup before you proceed with updates!īut, hey, no problem. It all depends on the RW theme and plugin(s) you’re using. Ouch!īut this is not to conclude that the Stacks V4.1.3 update would create problems for all Rapidweaver 8.x users. This had happened before (from Stacks 3 to Stacks 4) and I can’t seem to learn my lesson from the past. The Stacks V4.1.3 update came to haunt me as I found out later that majority of the web pages no longer worked. Again, and how stupid of me, I went ahead and did the update. This time, a plugin (or, API – application program interface) within Rapidweaver called Stacks, prompted me that there’s a new version, from V4.0.4 to V4.1.3 (Build #5361). No problems there and I continued to open up the file (.rw8) …and, bam! Another update prompt came up on the screen. Rapidweaver 8 has a new version update – from v8.6.2 to v8.7 – but proceed with caution! In the process of updating a few pages for 2021, Rapidweaver(the software that creates the pages of my main website) alerted an update from version 8.6.2 to 8.7, which was mostly additional support for the latest macOS, “ Big Sur” or version 11.Īlthough, RW has safety provisions -in case of incompatibilities- to either ‘ Skip This Version’ as well as ‘ Remind Me Later’, I went ahead and did the update. It was New Year’s Eve, doing routine maintenance on my cylindrical 12-core Mac Pro (Late 2013) and checking how all my webserver applications were doing when something unusual happened – my Rapidweaver software crashed.
0 kommentar(er)
