Hi,
I have RHEL 6.1 on VM, where Big data is installed. Every 3-4 days, its web interface become very slow and I had to reboot this VM. I was checking with "top" and that shows that free memory is less. Can this be a reason for slowness ? No big load on CPU.
Not sure, if I need to limit heap size or edit sysctl file. Please suggest.
Hi All
We have one SCO Server here and it never gives us any trouble. Until Now!! Well its not earth shattering but we have one user who is complaining of a very slow response time when changing to his Home Directory. Other users who have similar profiles are OK. I have su'd to this user and I can... (0 Replies)
I'm facing a problem when trying to ssh to SUN servers with solaris OS,it takes a long time until prompted for password ..after connecting to the server everything work fine..how can I solve this issue??? (11 Replies)
Hi.. i have written a shell script and made this script to run on every day night 11: 55 pm using a cron job.
This cron job running for some days and is not running for some day. but i need this script to run every day night. Please help me.
Here is the cron tab entries,
55 23 * * *... (1 Reply)
Hi guys i need advice on the approach to this one......
I have a file say called
Thisfile.20130524.txt
i need to work out from the date 20130524 what day of the week that was and then process the file in 3 working days. (so not counting saturday or sunday....(will not worry about bank... (2 Replies)
How to find a file that's modified more than 2 days ago but was modified less than 5 days ago by use of any Linux utility ? (4 Replies)
Discussion started by: abdulbadii
4 Replies
LEARN ABOUT DEBIAN
make_combined_log2
make_combined_log.pl(1) General Commands Manual make_combined_log.pl(1)NAME
make_combined_log.pl - make combined logfile from SQL database
SYNOPSIS
make_combined_log.pl <days> <virtual host>
DESCRIPTION
This perl script extracts the httpd access data from a MySQL database and formats it properly for parsing by 3rd-party log analysis tools.
The script is intended to be run out by cron. Its commandline arguments tell it how many days' worth of access records to extract, and
which virtual_host you are interested in (because many people log several virthosts to one MySQL db.) This permits you to run it daily,
weekly, every 9 days -- whatever you decide.
NOTE
By "days" I mean "chunks of 24 hours prior to the moment this script is run." So if you run it at 4:34 p.m. on the 12th, it will go back
through 4:34 p.m. on the 11th.
KNOWN ISSUES
Because GET and POST are not discriminated in the MySQL log, we'll just assume that all requests are GETs. This should have negligible
effect on any analysis software. This could be remedied IF you stored the full HTTP request in your database instead of just the URI, but
that's going to cost you a LOT of space really quickly...
Because this is somewhat of a quick hack it doesn't do the most robust error checking in the world. Run it by hand to confirm your usage
before putting it in crontab.
AUTHOR
Edward Rudd <eddie@omegaware.com>
MAN PAGE CREATED BY
Michael A. Toth <lirul.lists@gmail.com> - based on comments of script
COMMENTS
This man page was written using xml2man (1) by the same author.
Manuals User make_combined_log.pl(1)