The vRA 7 can't connect to vRO. So I restarted the embedded vRO but the following error message appeared:
How should I make the enough disk space? Probably I should delete log files but which log is acceptable to delete?
Hello Fwa,
Usually when I have seen log partitions fill up, it points to something else that is going on that is causing the logs to be large. Like an error that occurs every second. I would suggest using linux "du" command to find the largest logs and take a look at them to see if it points to an error that needs to be fixed. If you clean the logs, but the error persists, then the partition will just fill up again. VRA seems to do a decent job of rotating the logs. My log partition is only 13% full right now.
Regards,
Darren
I agree try find the root casue for the logs being filled, also using winscp and delting logs files older than a certain age will still allow you to free up space and troubleshoot.
vRA does not log rotate which is insane so always keep an eye on your logs. Errors of it filling up are shown before issues like this appear
Oh it doesn't rotate ?
Blimey .. didn't know that ...
I thought vRA does log rotation. When I look in the log directories, I see bzip files and dated log files?
# ls -1a /var/log/vmware/vcac/
.
..
access_log.txt
access_log.txt.1.bz2
access_log.txt.2.bz2
access_log.txt.3.bz2
access_log.txt.4.bz2
access_log.txt.5.bz2
catalina.2016-03-01.log
catalina.2016-03-03.log
catalina.2016-03-04.log
catalina.2016-03-07.log
catalina.2016-03-08.log
catalina.2016-03-09.log
catalina.2016-03-10.log
catalina.2016-03-11.log
catalina.2016-03-12.log
catalina.2016-03-14.log
catalina.2016-03-15.log
catalina.2016-03-16.log
catalina.2016-03-17.log
catalina.2016-03-18.log
catalina.2016-03-20.log
catalina.2016-03-22.log
catalina.2016-03-23.log
catalina.2016-03-24.log
catalina.2016-03-25.log
catalina.2016-03-28.log
catalina.2016-03-29.log
catalina.2016-03-30.log
catalina.2016-04-01.log
catalina.2016-04-02.log
catalina.2016-04-04.log
catalina.2016-04-05.log
catalina.2016-04-06.log
catalina.2016-04-07.log
catalina.2016-04-08.log
catalina.2016-04-09.log
catalina.2016-04-11.log
catalina.2016-04-12.log
catalina.2016-04-13.log
catalina.2016-04-14.log
catalina.2016-04-15.log
catalina.2016-04-16.log
catalina.2016-04-17.log
catalina.2016-04-18.log
catalina.2016-04-19.log
catalina.2016-04-20.log
catalina.2016-04-21.log
. . .
Maybe it just does not prune logs older than X days?
Darrenoid