BRRABill's Field Report With Linux
-
@BRRABill said in BRRABill's Field Report With Linux:
@stacksofplates said in BRRABill's Field Report With Linux:
I've run into this multiple times in the past with Ubuntu. For some reason old kernel images aren't removed when space is running low. To check your current image use
uname -r. Then you can uninstall the older images.And I can delete every kernel image I am not using?
Can, yes. Best practice is to always keep at least one old one. But if you've been using the current one for a while, that's unnecessary.
-
@BRRABill said in BRRABill's Field Report With Linux:
Advanced OS. Bah!
No one ever claimed Ubuntu was advanced.
-
-
@BRRABill said in BRRABill's Field Report With Linux:
Advanced OS. Bah!
Advanced? More like a mishmash of old and new that ends up breaking lots of things.
-
So, was having some issues with my GrayLog instance. I have a feeling that it has run out of space. Would you agree?
I think LVM is confusing me again.
ubuntu@graylog:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 2.0G 12K 2.0G 1% /dev tmpfs 395M 420K 395M 1% /run /dev/dm-0 15G 15G 0 100% / none 4.0K 0 4.0K 0% /sys/fs/cgroup none 5.0M 0 5.0M 0% /run/lock none 2.0G 0 2.0G 0% /run/shm none 100M 0 100M 0% /run/user /dev/xvda1 236M 70M 154M 32% /boot overflow 1.0M 284K 740K 28% /tmp -
Yes, /dev/dm-o is full, which completely breaks graylog.
I had this happen to me as well, and just built a new vm. Once the VM was operational I reduced the indices by half.
-
@BRRABill said in BRRABill's Field Report With Linux:
So, was having some issues with my GrayLog instance. I have a feeling that it has run out of space. Would you agree?
I think LVM is confusing me again.
ubuntu@graylog:~$ df -h Filesystem Size Used Avail Use% Mounted on /dev/dm-0 15G 15G 0 100% /Yes you're out of space on your root directory.
-
@DustinB3403 said in BRRABill's Field Report With Linux:
Yes, /dev/dm-o is full, which completely breaks graylog.
I had this happen to me as well, and just built a new vm. Once the VM was operational I reduced the indices by half.
I figure this would be a good Linux learning experience.
I was thinking of following this link. It's for VMWare, but most of the Ubuntu commands should be the same, I would think.
http://docs.graylog.org/en/1.3/pages/installation/graylog_ctl.html#extend-disk-space
-
@DustinB3403 said in BRRABill's Field Report With Linux:
Yes, /dev/dm-o is full, which completely breaks graylog.
I had this happen to me as well, and just built a new vm. Once the VM was operational I reduced the indices by half.
What does that do to storage size?
I had a Splunk instance running for weeks and never had any issues like this, which is why it surprised me.
-
@BRRABill Yeah I was in the middle of bigger issues, and just didn't care to "fix" it.
I can copy the MAC address to make the same reservation, so no issues from my point.
The logs just sit on XS I believe if the log server can't be reached.
-
@BRRABill said in BRRABill's Field Report With Linux:
@DustinB3403 said in BRRABill's Field Report With Linux:
Yes, /dev/dm-o is full, which completely breaks graylog.
I had this happen to me as well, and just built a new vm. Once the VM was operational I reduced the indices by half.
I figure this would be a good Linux learning experience.
I was thinking of following this link. It's for VMWare, but most of the Ubuntu commands should be the same, I would think.
http://docs.graylog.org/en/1.3/pages/installation/graylog_ctl.html#extend-disk-space
In these directions, it says ...
"In order to extend the disk space mount a second drive on this path. Make sure to move old data to the new drive before and give the graylog user permissions to read and write here."Couldn't you also just extend the (whatever) ?
-
@BRRABill Adding a second drive to a VM is literally nothing though.
It would be better practice to add a drive, than to try and extend the existing one.
-
@DustinB3403 said in BRRABill's Field Report With Linux:
@BRRABill Adding a second drive to a VM is literally nothing though.
It would be better practice to add a drive, than to try and extend the existing one.
But in theory, that 15G partition is part of the 19.5GB VHD the GrayLog appliance sets up.
You're losing the 15G, right?
I know 15G isn't much, but I was just thinking for future reference, if it was more than 15G.
-
But you wouldn't be only modifying the 15GB partition, you'd be effecting the boot section of the drive etc.
It's much cleaner to just leave it there, and add a 100GB drive, and point all of the logging to that PV.
Which wouldn't be a bad topic on it's own.
-
@BRRABill said in BRRABill's Field Report With Linux:
@DustinB3403 said in BRRABill's Field Report With Linux:
@BRRABill Adding a second drive to a VM is literally nothing though.
It would be better practice to add a drive, than to try and extend the existing one.
But in theory, that 15G partition is part of the 19.5GB VHD the GrayLog appliance sets up.
You're losing the 15G, right?
I know 15G isn't much, but I was just thinking for future reference, if it was more than 15G.
Losing 15GB? Not if you are thin provisioned.
-
@scottalanmiller said in BRRABill's Field Report With Linux:
@BRRABill said in BRRABill's Field Report With Linux:
@DustinB3403 said in BRRABill's Field Report With Linux:
@BRRABill Adding a second drive to a VM is literally nothing though.
It would be better practice to add a drive, than to try and extend the existing one.
But in theory, that 15G partition is part of the 19.5GB VHD the GrayLog appliance sets up.
You're losing the 15G, right?
I know 15G isn't much, but I was just thinking for future reference, if it was more than 15G.
Losing 15GB? Not if you are thin provisioned.
Well, as of right now, this is how things rolled...
- Imported the GrayLog OVA appliance to XS.
- It creates a 19.5GB virtual disk where it does its magic.
- Part of that magic is this 15GB partition that is now full.
So, even thin provisioned, isn't that space already taken? (AKA once the data fills it, it still uses it even if the data is deleted, correct?)
-
@BRRABill said in BRRABill's Field Report With Linux:
@scottalanmiller said in BRRABill's Field Report With Linux:
@BRRABill said in BRRABill's Field Report With Linux:
@DustinB3403 said in BRRABill's Field Report With Linux:
@BRRABill Adding a second drive to a VM is literally nothing though.
It would be better practice to add a drive, than to try and extend the existing one.
But in theory, that 15G partition is part of the 19.5GB VHD the GrayLog appliance sets up.
You're losing the 15G, right?
I know 15G isn't much, but I was just thinking for future reference, if it was more than 15G.
Losing 15GB? Not if you are thin provisioned.
Well, as of right now, this is how things rolled...
- Imported the GrayLog OVA appliance to XS.
- It creates a 19.5GB virtual disk where it does its magic.
- Part of that magic is this 15GB partition that is now full.
So, even thin provisioned, isn't that space already taken? (AKA once the data fills it, it still uses it even if the data is deleted, correct?)
Sure it is, but after you copy that data to the new drive, you'll delete it from the old drive making it empty... Assuming XS can reclaim now empty space, you'll gain that 15 GB back.
-
@Dashrender said
Sure it is, but after you copy that data to the new drive, you'll delete it from the old drive making it empty... Assuming XS can reclaim now empty space, you'll gain that 15 GB back.
That's not how I understood thin provisioning to work.
You can take the VHD offline and resize it in WIndows, but I don't think you can in XS.
-
@BRRABill said in BRRABill's Field Report With Linux:
@scottalanmiller said in BRRABill's Field Report With Linux:
@BRRABill said in BRRABill's Field Report With Linux:
@DustinB3403 said in BRRABill's Field Report With Linux:
@BRRABill Adding a second drive to a VM is literally nothing though.
It would be better practice to add a drive, than to try and extend the existing one.
But in theory, that 15G partition is part of the 19.5GB VHD the GrayLog appliance sets up.
You're losing the 15G, right?
I know 15G isn't much, but I was just thinking for future reference, if it was more than 15G.
Losing 15GB? Not if you are thin provisioned.
Well, as of right now, this is how things rolled...
- Imported the GrayLog OVA appliance to XS.
- It creates a 19.5GB virtual disk where it does its magic.
- Part of that magic is this 15GB partition that is now full.
So, even thin provisioned, isn't that space already taken? (AKA once the data fills it, it still uses it even if the data is deleted, correct?)
Oh sorry, yes. Don't use appliances, build your own with proper specs
-
@Dashrender said in BRRABill's Field Report With Linux:
@BRRABill said in BRRABill's Field Report With Linux:
@scottalanmiller said in BRRABill's Field Report With Linux:
@BRRABill said in BRRABill's Field Report With Linux:
@DustinB3403 said in BRRABill's Field Report With Linux:
@BRRABill Adding a second drive to a VM is literally nothing though.
It would be better practice to add a drive, than to try and extend the existing one.
But in theory, that 15G partition is part of the 19.5GB VHD the GrayLog appliance sets up.
You're losing the 15G, right?
I know 15G isn't much, but I was just thinking for future reference, if it was more than 15G.
Losing 15GB? Not if you are thin provisioned.
Well, as of right now, this is how things rolled...
- Imported the GrayLog OVA appliance to XS.
- It creates a 19.5GB virtual disk where it does its magic.
- Part of that magic is this 15GB partition that is now full.
So, even thin provisioned, isn't that space already taken? (AKA once the data fills it, it still uses it even if the data is deleted, correct?)
Sure it is, but after you copy that data to the new drive, you'll delete it from the old drive making it empty... Assuming XS can reclaim now empty space, you'll gain that 15 GB back.
Yes, in reality this is all that you do. Make a new one, remove the old.
