server_log used to have only 2MB in size on NAS 5.5 and earlier. NAS 5.6 increased the server_log to 4MB. This is enough to hold several days back in normal circumstances.
If you only have 24 hours back in the server_log, you might have some specify error message flooding the logs. Perhaps some facility is in verbose level. You can open a support case to check if there is any facility in verbose level.
Now if use the mnt dir to save all the log would I be causing the sytem to run out of space or have any problems? or should path it to a filesystem\share?
it depends how much data is being collected, the log file is being zipped but still .. you don't want Control Station to start running out of space so i would purge this directory from time to time. You can sftp data to another system.
DHoffman2
2 Intern
•
306 Posts
0
October 1st, 2009 07:00
jimkunysz
259 Posts
0
October 1st, 2009 07:00
there's also the /nbsnas/log that provides additional logs.- such as the cmd_log
jim
Peter_EMC
674 Posts
0
October 1st, 2009 07:00
nandas
4 Operator
•
1.5K Posts
0
October 1st, 2009 09:00
As Peter mentioned, this is all on the data mover log (server log) - there is no older copy of data mover log. The server log gets overwritten.
However, as Jimmentioned, you may get the older version of control station logs like messages, syslogs, cmd_log etc which may also be helpful.
My 2 cents:)
Sandip
gbarretoxx1
366 Posts
0
October 1st, 2009 11:00
server_log used to have only 2MB in size on NAS 5.5 and earlier.
NAS 5.6 increased the server_log to 4MB. This is enough to hold several days back in normal circumstances.
If you only have 24 hours back in the server_log, you might have some specify error message flooding the logs. Perhaps some facility is in verbose level.
You can open a support case to check if there is any facility in verbose level.
Gustavo Barreto.
droche71
11 Posts
0
October 13th, 2009 05:00
eg
server_log server_2 -a -s >> /mnt/nas_logs/dm02.logs
gbarretoxx1
366 Posts
0
October 13th, 2009 10:00
gbarretoxx1
366 Posts
0
October 13th, 2009 10:00
you could also have something like :
#########################################################
#!/bin/sh
DM=server_2
NAS_DB=/nas
export NAS_DB
STIME=`date '+%y%m%d%H%M'`
mkdir /mnt/test
$NAS_DB/bin/server_log $DM -s -a > /mnt/testlog.$DM.$STIME
gzip /mnt/test/log.$DM.$STIME
#########################################################
So, you would have control about the timestamps, and work with lower filesizes...
Gustavo Barreto.
dynamox
9 Legend
•
20.4K Posts
0
October 13th, 2009 10:00
$NAS_DB/bin/server_log $DM -s -a >
/mnt/testlog.$DM.$STIME
missing a "/" after "test" ?
monge1
24 Posts
0
April 23rd, 2010 10:00
Ok I got it. But is it safe to say that everytime the above scrip runs it will create a new test folder?
monge1
24 Posts
0
April 23rd, 2010 10:00
ok thanks.
Now if use the mnt dir to save all the log would I be causing the sytem to run out of space or have any problems? or should path it to a filesystem\share?
dynamox
9 Legend
•
20.4K Posts
0
April 23rd, 2010 10:00
you schedule it to run on the Control Station. Are you familiar with cron ? Google for "cron" to get some examples.
dynamox
9 Legend
•
20.4K Posts
0
April 23rd, 2010 10:00
yep, good observation. You can create it manually and remove it from the script. Also don't forget to fix this line
$NAS_DB/bin/server_log $DM -s -a > /mnt/testlog.$DM.$STIME
should be
$NAS_DB/bin/server_log $DM -s -a > /mnt/test/log.$DM.$STIME
dynamox
9 Legend
•
20.4K Posts
0
April 23rd, 2010 10:00
it depends how much data is being collected, the log file is being zipped but still .. you don't want Control Station to start running out of space so i would purge this directory from time to time. You can sftp data to another system.
monge1
24 Posts
0
April 23rd, 2010 10:00
I am not a linux person, but can this be done directly on the nas?