HELP: Size Related Error.. I Think
Moderators: Developers, Moderators
HELP: Size Related Error.. I Think
Hello All!
This is my inaugural post, so firstly, thank you for having me into your community. I'm a help desk tech, less than two years into the industry and I don't have a lot of experience with servers and databases. However our senior hosting manager has moved on to a bigger company, and his roles have now become my roles. One of his last proclamations before he left was to always, always watch Cacti. How important it would be in helping me understand what going on in our rack and giving me an overall picture of the system's health.
Unfortunately Cacti is down...
I have another resource that may be able to help, however he's also the owner, wears numerous hats and has very little time. I'd like to try and get Cacti back online if I can on my own, but I'm not sure I possess enough knowledge and understanding of how everything works. I know that was a lot of background, and I should just get to the error already.
So here's the situation, we have Cacti running on a virtual machine on one of our physical servers. I noticed I wasn't getting any reports and decided to login to the portal to see what was going on. This is the error I found:
Naturally I went into the VM and I increased the size, I power the VM back up and get stuck on this screen that just continues to scroll the below text:
I let it run a good 15 minutes and that's all it kept displaying over and over. I did a little bit of Google'ing and found a couple answers that seemed to be a little different from each other, so I don't know exactly what to do. Both answers revolved around a log file being too big, if that helps. Again I'm fairly green when it comes to all this, so if you have a solution or some troubleshooting technique you want me to try please be explicit with the instructions. Any help is welcome!
This is my inaugural post, so firstly, thank you for having me into your community. I'm a help desk tech, less than two years into the industry and I don't have a lot of experience with servers and databases. However our senior hosting manager has moved on to a bigger company, and his roles have now become my roles. One of his last proclamations before he left was to always, always watch Cacti. How important it would be in helping me understand what going on in our rack and giving me an overall picture of the system's health.
Unfortunately Cacti is down...
I have another resource that may be able to help, however he's also the owner, wears numerous hats and has very little time. I'd like to try and get Cacti back online if I can on my own, but I'm not sure I possess enough knowledge and understanding of how everything works. I know that was a lot of background, and I should just get to the error already.
So here's the situation, we have Cacti running on a virtual machine on one of our physical servers. I noticed I wasn't getting any reports and decided to login to the portal to see what was going on. This is the error I found:
Naturally I went into the VM and I increased the size, I power the VM back up and get stuck on this screen that just continues to scroll the below text:
I let it run a good 15 minutes and that's all it kept displaying over and over. I did a little bit of Google'ing and found a couple answers that seemed to be a little different from each other, so I don't know exactly what to do. Both answers revolved around a log file being too big, if that helps. Again I'm fairly green when it comes to all this, so if you have a solution or some troubleshooting technique you want me to try please be explicit with the instructions. Any help is welcome!
information wants to be free
-
- Cacti Pro User
- Posts: 613
- Joined: Tue Aug 29, 2006 4:09 pm
- Location: NL
Re: HELP: Size Related Error.. I Think
Did you have a look at your final message? The errors (images) are not there. Please provide more info.
Maintainer of cacti in Debian (and Ubuntu).
Cacti 1.* is now officially supported on Debian Stretch via Debian backports
FAQ Ubuntu and Debian differences
Generic cacti debugging
Cacti 1.* is now officially supported on Debian Stretch via Debian backports
FAQ Ubuntu and Debian differences
Generic cacti debugging
Re: HELP: Size Related Error.. I Think
Not sure what you mean, are you saying you can't see the images I posted in my original forum post? If so I'll upload them to this post instead of linking them.
- Attachments
-
- This is the error I'm getting when I power the VM on.
- Cacti VM Error.png (19.54 KiB) Viewed 722 times
-
- This is the error I'm getting at the Cacti login portal.
- Cacti Login Page Error.png (21.01 KiB) Viewed 722 times
information wants to be free
Re: HELP: Size Related Error.. I Think
Are you saying this is happening at boot? If so, this really isn't the right forum as its not cacti problem but a MySQL/Linux one.
Please mark the topic solved if this resolves your problem.
Re: HELP: Size Related Error.. I Think
Yes this is happening at VM startup. As Cacti is the only thing running on this machine I was banking on it was Cacti related, however if your saying it's not I understand. I was just looking for a little help if anyone had seen this before.
information wants to be free
Re: HELP: Size Related Error.. I Think
Thst error is telling you that MySQL can't connect because of some issue with the MySQL.sock file. If you can login to maintenance of single user mode you might be able to fix that. You should google that error.
Please mark the topic solved if this resolves your problem.
Re: HELP: Size Related Error.. I Think
Anyone interested in helping me get this resolved and getting paid for it, see my other thread.
http://forums.cacti.net/viewtopic.php?f=21&t=49121
http://forums.cacti.net/viewtopic.php?f=21&t=49121
information wants to be free
- gandalf
- Developer
- Posts: 22383
- Joined: Thu Dec 02, 2004 2:46 am
- Location: Muenster, Germany
- Contact:
Re: HELP: Size Related Error.. I Think
Run a "du -k" to find out, whether any important filesystem is out of space (I expect that).
In this case, no new files (even small session files) can't be allocated and thus everything is mis-behaving.
Clean the filesystem in question from all temporary or unneeded data.
That's a guess, of course
R.
In this case, no new files (even small session files) can't be allocated and thus everything is mis-behaving.
Clean the filesystem in question from all temporary or unneeded data.
That's a guess, of course
R.
Who is online
Users browsing this forum: No registered users and 1 guest