SUSE 10 oes2 operates very slowly

SUSE Product Topics SLES Networking
1

Everything was working fine for the last two months, but on the first
day of classes my suse server decided not to work.
I had created a web server and attached it to our edir tree. The last
few days I have been creating user accounts on a nss volume and hosting
secure web services. I wrote a program that creates the accounts on all
of our servers on the tree but I accidently pulled the power on the
workstation where the code is ran. It simply creats the folders and
assings the users to a mysql database for auth. I pulled the power on
the workstation while this was going on. Now I have lost connection to
the server and cannot get it to connect to edir. When I ping the
gateway I have about 80-90 percent packet loss. Also the mouse moves
very slowly. I have rebooted the server and the main server and still
nothing is working. When I login to the suse server I can see all my
volumes and everything but I cant brows the internet. It tires and says
that it is loading pages but it eventally gives up. I tried a ds repair
to see what the errors are and it finds the server but it gives an error
that I may need to use advanced options and repair the time sync. Done
it and it doesnt help.
any ideas???

Thanks
Dave.

–
dmiller

dmiller’s Profile: http://forums.novell.com/member.php?userid=10134
View this thread: http://forums.novell.com/showthread.php?t=450867

2

On Tue, 17 Jan 2012 17:26:02 +0000, dmiller wrote:
[color=blue]

I tried a ds repair
to see what the errors are and it finds the server but it gives an error
that I may need to use advanced options and repair the time sync. Done
it and it doesnt help.
any ideas???[/color]

Not sure why you’d do a dsrepair when the system is dragging - dsrepair
is a repair tool, not a diagnostic tool.

When the system is behaving slowly, try running ‘top’ and see what it
says is eating the CPU.

BTW, if this is an OES2 server, you might ask in the OES forums rather
than the SLES forums.

Jim

Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
Novell Knowledge Partner

3

“Not sure why you’d do a dsrepair when the system is dragging -
dsrepair
is a repair tool, not a diagnostic tool.”

Eh? What about ndsrepair -T or ndsrepair -E ? I use those 2 all the
time for a quick command line diagnostic.

At any rate, top is a good diag to use, I agree. But if you’re losing
packets, I would also check your network card and wiring.

–El

hendersj;2168430 Wrote:[color=blue]

On Tue, 17 Jan 2012 17:26:02 +0000, dmiller wrote:
[color=green]

I tried a ds repair
to see what the errors are and it finds the server but it gives an[/color]
error[color=green]
that I may need to use advanced options and repair the time sync.[/color]
Done[color=green]
it and it doesnt help.
any ideas???[/color]

Not sure why you’d do a dsrepair when the system is dragging -
dsrepair
is a repair tool, not a diagnostic tool.

When the system is behaving slowly, try running ‘top’ and see what it
says is eating the CPU.

BTW, if this is an OES2 server, you might ask in the OES forums rather
than the SLES forums.

Jim

Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
Novell Knowledge Partner[/color]

–
El LaGrew
elbert.lagrew#katun.com
elagrew on twitter

elagrew’s Profile: http://forums.novell.com/member.php?userid=10240
View this thread: http://forums.novell.com/showthread.php?t=450867

4

On Wed, 18 Jan 2012 17:26:01 +0000, elagrew wrote:
[color=blue]

“Not sure why you’d do a dsrepair when the system is dragging - dsrepair
is a repair tool, not a diagnostic tool.”

Eh? What about ndsrepair -T or ndsrepair -E ? I use those 2 all the
time for a quick command line diagnostic.[/color]

Years ago I switched to using iMonitor for doing diagnostics like this.
Usually a “quick command line diagnostic” leads me to need to go to
something else, and in general, it’s all there in iMonitor so I just
start there now.

But yeah, that’s informational and certainly OK. The thing is that
most people, when they say “I ran dsrepair to see what errors it
reports”, they mean they’ve run a database repair.

First rule of troubleshooting: Don’t change the environment while you’re
trying to diagnose it. That changes the problem and increases the time
to troubleshoot.

Repairing the database “to see what errors are fixed” counts as changing
the environment. And in general it’s not going to solve a network issue
(rarely it may fix a server-to-server authentication problem, but
usually comms problems are more fundamental than a corrupted key pair for
server authentication).
[color=blue]

At any rate, top is a good diag to use, I agree. But if you’re losing
packets, I would also check your network card and wiring.[/color]

Yes. And the switch port that the server’s plugged into - I’ve seen bad
ports cause problems like this. And make sure that you’ve got the duplex
properly configured (ISTR the general rule of thumb is leave everything
set to autoconfigure, though Massimo is the expert on that around here).

Jim

–
Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
Novell Knowledge Partner