@Sebastian-Roth Thanks! That saves a lot of space so I can upgrade from 1.5.4.
Posts made by Dee
-
RE: Apache2 error-Won't download-We're DOWN :(
-
RE: Apache2 error-Won't download-We're DOWN :(
@Quazz Is it also safe to delete:
/homefog_web_1.3.5.BACKUP
/homefog_web_1.3.0.BACKUP
/homefog_web_1.4.2.BACKUP
if I keep the latest one /homefog_web_1.5.4.BACKUP?It would be nice if there was something in the Forum about what files can safely be removed unless I missed it.
-
RE: Apache2 error-Won't download-We're DOWN :(
@Quazz Thanks Quazz. Will delete two and older files before upgrading.
-
RE: Apache2 error-Won't download-We're DOWN :(
@Sebastian-Roth There were 7 computers scheduled to download image which shouldn’t be too many. OK I downloaded the file fog_1.5.5.tar.gz and it’s in my Downloads file. Just wanting to make sure this is the correct commands since I’m not thinking straight right now.
cd /Downloads
tar -xzf fog_1.5.5.tar.gz (or do I need to add the v in there?
/installfog.shIs that all there is?
Can I delete the old tar files safely?
Any other files you suggest removing to increase space? -
RE: Apache2 error-Won't download-We're DOWN :(
@Sebastian-Roth I’ll do that tomorrow morning. Guess if that works I’ll start researching how to get Debian (Virtual server) to see another drive so I can change the /home/image directory to another hard terabyte drive. Thanks Sebastian!
-
RE: Apache2 error-Won't download-We're DOWN :(
https://imgur.com/a/rxhfZxu
These images are a bit bigger so you can see more. -
RE: Apache2 error-Won't download-We're DOWN :(
@Tom-Elliott running version: 1.5.4 on Linux Debian 8
It won’t take the uploads request entry too large. Something went wrong with parsing server response.
![0_1544465050311_i601.JPG](Uploading 100%) -
Apache2 error-Won't download-We're DOWN :(
![0_1544462392051_IMG_0608.JPG](Uploading 100%) ![2_1544462470240_IMG_0617.JPG](Uploading 100%) ![0_1544462625729_IMG_0621.JPG](Uploading 100%)
Timing out, Removed apache2 logs, can’t download. How do I delete all the tasks that were running? Any help will be appreciated! -
RE: Not capturing image
@quinniedid Thanks for your help. You guys are the best!
-
RE: Not capturing image
@Sebastian-Roth Capturing is solved!!! Yeah you guys are the best!
-
RE: Not capturing image
@Sebastian-Roth
Removed more and it freed up some more space. -
RE: Not capturing image
@Sebastian-Roth
I ran the command and it freed up a small amount of space. Now instead of 475 GB it’s 450GB. Then I removed some images that are no longer used via the web client and no decrease in size which surprised me. -
RE: Not capturing image
@Dee Some images were deleted from /home/images and I’m wondering if the system is looking for sda7 as in the image_0496 and sda7 doesn’t seem to exist.
-
RE: Not capturing image
Looks like there are 12 part images but only 2 showing?
-
RE: Not capturing image
@quinniedid yes I do see that. When I look closely it says "failed to complete capture (savePartition) Args Passed: /dev/sda 7 1 /images/f48e38d9d9cd all. Exit code 141. I looked at the server and it appears that /dev/mapper/libraryfog --vg-home is out of space. Not sure what to do now. The highlighted line. Can I save my new images somewhere else since I don’t know what I can safely delete?
-
RE: Not capturing image
@quinniedid ![alt text]( image url
Here are the errors I’m seeing.ACPI BIOS Error (bug) : Failure looking up [_SB>PCI0>XHC.RHUB.HS11] AE_NOT_FOUND 920180105/dswload-211)
ACPI Error: AE_NOT_fOUND, During name lookup/catalog (20180105/psobject-252)
ACPI Error: AE_NOT_fOUND, (SSDT:DELL_UMA) while loading table (20180105/tbxfload)