This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Hi,
In the D:\ibm\HTTPServer\logs folder on our servers there is an access.log file that is over 14 GB. It looks like the http server has been updating this since we installed the servers two years ago.
I cannot open it since it's too large for Wordpad or Notepad++.
Is there a way to truncate this log or delete it without stopping the IBM HTTP server?
If I stop the server can I delete it?
Thanks,
Dave Bone
Ocean Spray Cranberries
Below are two options you could try:
1) Go to WebSphere admin console (can't recall under which section). You should be able to control the size limit of log files there. Once a log file reaches size limit threshold, a new log file will be created and old will be archived(renamed) to keep safe.
2) Use log reader software available in market (some of those are even free!!) to read log file, these software could open large files. Also, it could show you updates of log live without reopening the file again.
Regards...KuldeepNever Postpone The Joy !!!
--- On Mon, 6/27/11, in2data <in2data@yahoo.com> wrote:
From: in2data <in2data@yahoo.com>
Subject: [MAXIMO List] HTTP Server Access.log File is Huge and Growing
To: MAXIMO@yahoogroups.com
Date: Monday, June 27, 2011, 12:16 PM
Hi,
In the D:\ibm\HTTPServer\logs folder on our servers there is an access.log file that is over 14 GB. It looks like the http server has been updating this since we installed the servers two years ago.
I cannot open it since it's too large for Wordpad or Notepad++.
Is there a way to truncate this log or delete it without stopping the IBM HTTP server?
If I stop the server can I delete it?
Thanks,
Dave Bone
Ocean Spray Cranberries
Hi,
I had actually gone to
Application servers > MXServer > HTTP error and NCSA access logging
and unchecked the logging for all of the servers in the cluster.
Then I stopped and started the http server from WebSphere.
That dropped the huge log file and created a new one.
But the system is still logging like I never unchecked the logging.
That's got to be slowing down the server.
On my sandbox server I rebooted and did ripplestarts for the cluster and it's still logging away.
I've got a support request in.
Does anyone know how to kill the logging?
Thanks,
Dave Bone
--- In MAXIMO@yahoogroups.com, kuldeep lakhani <kuldeep_lakhani2000@...> wrote:
>
> Below are two options you could try:
> 1) Go to WebSphere admin console (can't recall under which section). You should be able to control the size limit of log files there. Once a log file reaches size limit threshold, a new log file will be created and old will be archived(renamed) to keep safe.
> 2) Use log reader software available in market (some of those are even free!!) to read log file, these software could open large files. Also, it could show you updates of log  live without reopening the file again.
>
> Â Regards...KuldeepNever Postpone The Joy !!!
>
> --- On Mon, 6/27/11, in2data <in2data@...> wrote:
>
> From: in2data <in2data@...>
> Subject: [MAXIMO List] HTTP Server Access.log File is Huge and Growing
> To: MAXIMO@yahoogroups.com
> Date: Monday, June 27, 2011, 12:16 PM
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Â
>
>
>
>
>
>
>
>
>
> Hi,
>
>
>
> In the D:\ibm\HTTPServer\logs folder on our servers there is an access.log file that is over 14 GB. It looks like the http server has been updating this since we installed the servers two years ago.
>
>
>
> I cannot open it since it's too large for Wordpad or Notepad++.
>
>
>
> Is there a way to truncate this log or delete it without stopping the IBM HTTP server?
>
>
>
> If I stop the server can I delete it?
>
>
>
> Thanks,
>
>
>
> Dave Bone
>
> Ocean Spray Cranberries
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Hi,
Jani972 on the IBM forum mentioned they had commented out the logging in the http.conf file.
I commented out the access.log entry in the http.conf file.
#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
# CustomLog logs/access.log common
That stopped it from logging.
So turning it off in WebSphere just stops the container logging option. You also have to disable it here.
Dave Bone
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> I had actually gone to
>
> Application servers > MXServer > HTTP error and NCSA access logging
>
> and unchecked the logging for all of the servers in the cluster.
>
> Then I stopped and started the http server from WebSphere.
>
> That dropped the huge log file and created a new one.
>
> But the system is still logging like I never unchecked the logging.
>
> That's got to be slowing down the server.
>
> On my sandbox server I rebooted and did ripplestarts for the cluster and it's still logging away.
>
> I've got a support request in.
>
> Does anyone know how to kill the logging?
>
> Thanks,
>
> Dave Bone
>
> --- In MAXIMO@yahoogroups.com, kuldeep lakhani <kuldeep_lakhani2000@> wrote:
> >
> > Below are two options you could try:
> > 1) Go to WebSphere admin console (can't recall under which section). You should be able to control the size limit of log files there. Once a log file reaches size limit threshold, a new log file will be created and old will be archived(renamed) to keep safe.
> > 2) Use log reader software available in market (some of those are even free!!) to read log file, these software could open large files. Also, it could show you updates of log  live without reopening the file again.
> >
> > Â Regards...KuldeepNever Postpone The Joy !!!
> >
> > --- On Mon, 6/27/11, in2data <in2data@> wrote:
> >
> > From: in2data <in2data@>
> > Subject: [MAXIMO List] HTTP Server Access.log File is Huge and Growing
> > To: MAXIMO@yahoogroups.com
> > Date: Monday, June 27, 2011, 12:16 PM
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Â
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi,
> >
> >
> >
> > In the D:\ibm\HTTPServer\logs folder on our servers there is an access.log file that is over 14 GB. It looks like the http server has been updating this since we installed the servers two years ago.
> >
> >
> >
> > I cannot open it since it's too large for Wordpad or Notepad++.
> >
> >
> >
> > Is there a way to truncate this log or delete it without stopping the IBM HTTP server?
> >
> >
> >
> > If I stop the server can I delete it?
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Dave Bone
> >
> > Ocean Spray Cranberries
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
Hi,
you can also set rotation of this log in http.conf file:
CustomLog "|bin/rotatelogs.exe logs/access.log 50M" common
Regards
Tomas
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> Jani972 on the IBM forum mentioned they had commented out the logging in the http.conf file.
>
> I commented out the access.log entry in the http.conf file.
>
> #
> # The location and format of the access logfile (Common Logfile Format).
> # If you do not define any access logfiles within a <VirtualHost>
> # container, they will be logged here. Contrariwise, if you *do*
> # define per-<VirtualHost> access logfiles, transactions will be
> # logged therein and *not* in this file.
> #
> # CustomLog logs/access.log common
>
> That stopped it from logging.
>
> So turning it off in WebSphere just stops the container logging option. You also have to disable it here.
>
> Dave Bone
>
>
> --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> >
> > Hi,
> >
> > I had actually gone to
> >
> > Application servers > MXServer > HTTP error and NCSA access logging
> >
> > and unchecked the logging for all of the servers in the cluster.
> >
> > Then I stopped and started the http server from WebSphere.
> >
> > That dropped the huge log file and created a new one.
> >
> > But the system is still logging like I never unchecked the logging.
> >
> > That's got to be slowing down the server.
> >
> > On my sandbox server I rebooted and did ripplestarts for the cluster and it's still logging away.
> >
> > I've got a support request in.
> >
> > Does anyone know how to kill the logging?
> >
> > Thanks,
> >
> > Dave Bone
> >
> > --- In MAXIMO@yahoogroups.com, kuldeep lakhani <kuldeep_lakhani2000@> wrote:
> > >
> > > Below are two options you could try:
> > > 1) Go to WebSphere admin console (can't recall under which section). You should be able to control the size limit of log files there. Once a log file reaches size limit threshold, a new log file will be created and old will be archived(renamed) to keep safe.
> > > 2) Use log reader software available in market (some of those are even free!!) to read log file, these software could open large files. Also, it could show you updates of log  live without reopening the file again.
> > >
> > > Â Regards...KuldeepNever Postpone The Joy !!!
> > >
> > > --- On Mon, 6/27/11, in2data <in2data@> wrote:
> > >
> > > From: in2data <in2data@>
> > > Subject: [MAXIMO List] HTTP Server Access.log File is Huge and Growing
> > > To: MAXIMO@yahoogroups.com
> > > Date: Monday, June 27, 2011, 12:16 PM
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Â
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hi,
> > >
> > >
> > >
> > > In the D:\ibm\HTTPServer\logs folder on our servers there is an access.log file that is over 14 GB. It looks like the http server has been updating this since we installed the servers two years ago.
> > >
> > >
> > >
> > > I cannot open it since it's too large for Wordpad or Notepad++.
> > >
> > >
> > >
> > > Is there a way to truncate this log or delete it without stopping the IBM HTTP server?
> > >
> > >
> > >
> > > If I stop the server can I delete it?
> > >
> > >
> > >
> > > Thanks,
> > >
> > >
> > >
> > > Dave Bone
> > >
> > > Ocean Spray Cranberries
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>