Hello listers,
Our datawarehouse machine suffers from a kernel bug. In the past year we
have had this issue, sometimes even every week. Usually the bug appears
when performing an archive but it also happens at other times. In all
cases the machine has a high IO load.
We have upgraded the
Hello Berry,
I have no advise on your specific problem, but a kernel bug, oops, warning or
panic is a very strong indication that this is a real code problem. I suggest
to open a service request/problem ticket.
hope this helps
Christian
Message from /var/log/messages:
kernel: kernel BUG at
On 1/5/09 7:18 PM, Thomas Kern tlk_sysp...@yahoo.com wrote:
Or set it to run as root under CRON and you can specify the filesystem
such as 'dsmc incremental / /srv /oradb'.
You can also have the output processed into a status message to be sent
to a central administrator or to XYMON
Hello Christian,
Yes, that was my idea also but there is a problem with my accounts at
Novell and IBM. I can't open any issue at this time and my manager
expects me to solve this within a few days.
Regards, Berry.
-Original Message-
From: Linux on 390 Port
We are currently running a SLES 10 SP2 guest (hostx) with access to
three networks (eth0, eth1, eth2). The issue we are having is that the
default route is not correct after an ipl. If I delete the incorrect
route (using: route del) and add the correct route (using: route add)
everything works
On 1/6/2009 at 11:59 AM, Sollenberger, Justin W Mr CIV US DISA CDB24
justin.sollenber...@csd.disa.mil wrote:
-snip-
Any ideas on why hostx and hostz come up with different default gateways
when the configuration files are the same? What am I missing? How can
I correct it? Thanks in advance
There's no guarantee in what order a network interface will initialize, so
I think the confusion is with multiple default route specifications, and
you're getting lucky with the other machine getting the right one. There
should be only one default route specified. The route add/del flushes the
On Tuesday, 01/06/2009 at 09:42 EST, van Sleeuwen, Berry
berry.vansleeu...@atosorigin.com wrote:
Yes, that was my idea also but there is a problem with my accounts at
Novell and IBM. I can't open any issue at this time and my manager
expects me to solve this within a few days.
Solving a
Justin,
We have systems with multiple network interfaces. I finally had to
modify the default route in
/etc/sysconfig/network/routes to look like this.
default 32.71.175.1 - qeth-bus-ccw-0.0.0600
Notice I had to use the persistent name for the interface. The eth0,
eth1 type of name
can
Mark,
Come to think of it, the last time I remember having device names change
on me was a few of the systems
that I upgraded to SLES10 SP2. I don't remember what level of code I
was coming from-SLES10 or
SLES10SP1.
I still think I will stick with the long names for the time being. On
most of
On 1/6/2009 at 9:40 AM, van Sleeuwen, Berry
berry.vansleeu...@atosorigin.com wrote:
Hello Christian,
Yes, that was my idea also but there is a problem with my accounts at
Novell and IBM. I can't open any issue at this time and my manager
expects me to solve this within a few days.
Even
Hello Mark,
Thanks for your comments. This workaround would be an option. We'll have
to look into that.
I did find that some work has been done when I was looking into the
aio.c. And also that some parts have been discussed for some time now.
The aio.c (and aio.h) have been changed to some
Thanks to all who replied. I was able to get it working properly by
removing all of the default routes except for one. I also replaced
those default routes (in the ifroute files) with the other more specific
routes.
Now my route table look like this:
Kernel IP routing table
Destination
On 1/6/2009 at 3:51 PM, Berry van Sleeuwen berry.vansleeu...@xs4all.nl
wrote:
-snip-
Just for my good understanding (and for some input tomorrow at our next
meeting). Suppose we would be able to open a service request, what would
be the chance a kernel bug can be fixed through a service
I've got a small problem. I have a daemon which I cannot easily restart
because it is production and people are using it. The daemon is started
with something like:
daemon args daemon.log
The file daemon.log is getting very huge. The correct way to fix this is
to stop the daemon, mv or rm the
On 1/6/09 1:50 PM, John McKown wrote:
I've got a small problem. I have a daemon which I cannot easily restart
because it is production and people are using it. The daemon is started
with something like:
daemon argsdaemon.log
The file daemon.log is getting very huge. The correct way to fix this
Sollenberger, Justin W Mr CIV US DISA CDB24 wrote:
We are currently running a SLES 10 SP2 guest (hostx) with access to
three networks (eth0, eth1, eth2). The issue we are having is that the
default route is not correct after an ipl. If I delete the incorrect
route (using: route del) and add
Perhaps logrotate can help you here.
From the manpage:
logrotate is designed to ease administration of systems that generate
large numbers of log files. It allows automatic rotation, compression,
removal, and mailing of log files. Each log file may be handled daily,
weekly, monthly, or when
18 matches
Mail list logo
