![]() ![]() ![]() ![]() They’re usually linked to different pages or sections of your website. Nav links: These are text links with predefined padding and other styles.It is a parent element that contains all the navigation (nav) links. Nav menu: The nav menu is on the right of the navbar.Here you can add a logo or text or any other brand indication. Brand: The brand placeholder is a link block located on the left of the navbar.Your navbar is a container that centers a group of elements on the page. Since the navbar is self-contained, you can move it wherever and whenever you like. You can place the navbar anywhere in your site - there’s no right or wrong way to do this. Drag a Navbar from the Advanced section onto the Webflow canvas.I have Cloudwatch alarms in place to alert me if the disk space grows too large now. I still haven't been able to get to the bottom of why a small Ghost CMS should be taking up such a large amount of disk space, but for the moment I am happy that my site is up and running. I never thought I'd be so happy to see the output from a terminal! Summary Once I ran that command I was greeted with: ℹ Checking if logged in user is directory owner It can be used to enlarge or shrink an unmounted file system located on device.įinally, I started the Ghost CMS again with the following command: I ran the resize2fs command to resize my file system. Success! If I run the lsblk command to verify that partition 1 is expanded to 40 GB, I see the following: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT Whew! This bought me an additional 300 Mb which was just enough to run the growpart command again. I did this by typing the following command in the terminal: $ find /var/log -type f -delete I searched for other files to remove, but being a bit of an amateur with Linux, I decided to delete the safest files.the log files. Unfortunately, I was also met with the " No space left on device" error when I ran the command. I was screwed! One of the suggestions that was mentioned online was to use the $ apt-get autoremove command to remove those dependencies that were installed with applications and are no longer used by anything else on the system. However, when I did this I was presented with the following error: mkdir: cannot create directory ‘/tmp/growpart.2626’: No space left on deviceĪrrrgh! This meant that I didn't even have enough disk space to expand the disk space. The simple solution is to run the following command on the root partition and tell it to start using the new space it has been allocated: In my case the partition xvda1 is still assigned 10 GB, but the root xvda uses 40 GB. You can see this by SSH'ing into the instance and typing lsblk in the terminal. Without doing this, it is still assigned the old volume size and you haven't actually made use of the new space you've given it. You need to tell the partition to use the "new space" that you've just given it. ![]() Once you've increased the size of the volume, it turns out that there is still one more step that needs to take place. Next, select from the Actions drop down menu and choose Modify Volume.Ĭhoose the new size of the volume and select OK. You can do this from the EC2 Management Console by selecting the instance, choosing Storage and the clicking on the Volume ID (highlighted in yellow below). My first thoughts were to get the site back up and running by increasing the size of the volume (or disk space) assigned to the instance. This is a bit weird considering I had 10 GB assigned to the volume - after all, this is only a small blog! Increasing the size of the volume That didn't help.Īfter taking a closer look at the logs on Amazon, it turns out that I had actually run out of disk space on the instance. I thought this might just be an issue with the site, so I tried the usual Stop Instance and Restart Instance. Which is why I was quite surprised to found out that I was greeted with an annoying HTTP 503 error on my site over the Christmas period. The blog has largely remained untouched for a year or so. I've had a few on and off issues with Amazon EC2 Linux instances and this blog over time, but generally things were working as expected. Life often gets in the way of blogging, and I haven't made any new posts to this blog for a while. I've been really happy with Ghost - it's easy to set up and get running, and the Ghost community is really great. A few years ago, I transitioned my blog from a custom ASP.NET website to Ghost CMS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |