Christopher Casey
asked on
Juniper SRX 240 request system storage cleanup has to be run daily?
Hello,
I am finding that I have to >run request system storage cleanup everyday. Any thoughts on what could cause this? Seems to cause the SRX to crash then after i run the command it's fine for 24 hrs.
Is it the logging? is there a way to port the logs off daily? Thanks.
I am finding that I have to >run request system storage cleanup everyday. Any thoughts on what could cause this? Seems to cause the SRX to crash then after i run the command it's fine for 24 hrs.
Is it the logging? is there a way to port the logs off daily? Thanks.
As above but also look at the file usage on the device.
show system storage
If we run this before and after the cleanup we can see exactly where the space is being used.
Also, when you run the clean up is gives a list of all the files it will delete/log rotate etc, these should also indicate where the traceoptions are enabled above.
show system storage
If we run this before and after the cleanup we can see exactly where the space is being used.
Also, when you run the clean up is gives a list of all the files it will delete/log rotate etc, these should also indicate where the traceoptions are enabled above.
ASKER
I disabled some of the logs that appear to be unnecessary. Will see how tonight goes.
Also this seems to happen at 12 AM on the dot.
Also this seems to happen at 12 AM on the dot.
The trace search in the config may show if you have a few large traces set up which may be affecting the disk space.
As for the midnight, I cant comment but I assume that its a regular time for auto log switches
As for the midnight, I cant comment but I assume that its a regular time for auto log switches
ASKER
Here is the output of the two commands referenced above. Match trace produced nothing
Match log did
root@office> show configuration | match trace
root@office> show configuration | match log
login {
syslog {
log {
format syslog;
default log-and-permit;
default log-and-permit;
default log-and-permit;
server-connectivity log-and-permit;
timeout log-and-permit;
too-many-requests log-and-permit;
default log-and-permit;
server-connectivity log-and-permit;
timeout log-and-permit;
too-many-requests log-and-permit;
over-limit log-and-permit;
over-limit log-and-permit;
log {
log {
Match log did
root@office> show configuration | match trace
root@office> show configuration | match log
login {
syslog {
log {
format syslog;
default log-and-permit;
default log-and-permit;
default log-and-permit;
server-connectivity log-and-permit;
timeout log-and-permit;
too-many-requests log-and-permit;
default log-and-permit;
server-connectivity log-and-permit;
timeout log-and-permit;
too-many-requests log-and-permit;
over-limit log-and-permit;
over-limit log-and-permit;
log {
log {
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I shut down the IDP service and that seemed to have "cured" it. We were not using IDP in this installation so there was no need to have it. But apparently at the time stated it attempted to download an update and not install.
So by disabling the IDP service it stopped D/L and no more space issues.
Thanks all for the help :)
So by disabling the IDP service it stopped D/L and no more space issues.
Thanks all for the help :)
Glad to help :P
From CLI, issue:
show conf | match trace
show conf | match log
With commands above you would get all the configuration lines where logging or traceoptions are enabled.
You can disable/delete or fine tune the level of logs/trace.
Please check and update.
Thank you.