Quantum Forum for DXi V5000
/var/log low on space
Hi,
I get an alert on my Quantum vmPRO that /var/log is low on space. I couldn't figure out how to delete old logs, wether on the GUI nor on the shell. Could you please brief me how to delete some logs? Espacially messages.2, messages.3 Messages.4 and Messages.5 logs have been growing very big.
Thank you!
Replies to This Discussion
-
Permalink Reply by Dominic Bucher on
-
Can someone please help me?
-
Permalink Reply by Jerry Schmidt on
-
Hello Dominic,
The logs can be truncated via the shell but typically this only done by a support engineer. It would be important to identify why the logs are growing so large.
One known issue is when you have the integrity check option enabled via the advanced settings in vmPro and vmPro is reporting check disk errors on VMs but no one is correcting the issue with the VMs, this can spam the logs and cause them to fill up /var/log.
You mentioned that the the messages logs are filling up, what is in those logs?
You could turn off your current vmPro ndoe, then deploy a new instance of vmPro and point it to the same NFS or CIFS share and see if the problem happens again, however this would require you to configure the folders and backup policies again from scratch.
-
Permalink Reply by Jon McNerny on
-
Please post what is spaming the messages logs so we might understand the root cause. What is the timestamp of the head of the oldest logs and the tail of the newest log? How quickly are logs filling or are they just not rotating?
-
-
Thank you for your answers.
All Message logs are filled with the following content:
Feb 22 01:00:48 qBackup-01 kernel: Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
Feb 22 01:00:48 qBackup-01 kernel: CIFS VFS: Send error in SessSetup = -13This only happend on february 22 and since then it never happend again. But Backups are all running well and there are no other known issues with de vmPRO backup. Log Rotating seems to work aswell.
-
-
Hi Dominic,
Good to hear all is well. Maybe this vmPRO is joined to a Active Directory Domain? Could that have caused spaming of the logs that day?
Thanks for the reply,
Jon
-
-
Hi Jon,
During 22 of February I was out of Office and there is no know Active Directory problem for this date. The fact that this error is not reoccuring, I assume this was a temporarly error. I would really aprechiate if you would provide me the correct Shell command to delete those large logs.
Thank you :-)
-
-
Hi Dominic,
I misunderstood, i believe. The logs are not rolling over cleaning up the larger logs now? I'll look for a non root access (you would need support to log on) way to truncate the logs.
Jon
-
-
no.. there are just huge log files in /var/logs which leads to a daily alert email. As i mentioned above, i figured out which logs are huge. And now I just like to delete them, is it that hard to give me a how-to?
-
-
The solution involves root access. We cannot provide root access. There is a Request for Enhancement bug to allow a customer facing binary to truncate logs. This should be an option in the future.
Your options currently are:
-Purchase a service contract, we'll be happy to get you a service request opened and help with log truncation.
-Redeploy the vmPRO image and point this toward your storage, should be a quick work around. You can also import the old UI configuration if you've selected to back these up in any of your policies.
© 2024 Created by Quantum Forum V.
Powered by
