==================================================================
  Please DO NOT REPLY to this mail or send email to the developers
  about this bug. Please follow-up to Bugzilla using this link:
    http://bugs.contribs.org/show_bug.cgi?id=5391

  Have you checked the Frequently Asked Questions (FAQ)?
    http://wiki.contribs.org/SME_Server:Documentation:FAQ

  Please also take the time to read the following useful guide:
    http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
==================================================================

           Summary: du continually using CPU
           Product: SME Contribs
  Found-In-Version: 7.4
          Platform: PC
  Fixed-In-Version: Unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: smeserver-sme7admin
        AssignedTo: [email protected]
        ReportedBy: [email protected]
         QAContact: [email protected]


Kernel 2.6.9-78.0.22.EL.  This kernel was installed during a recent upgrade.

Process du started going continually following the first tape backup (LTO
Ultirum) after upgrade.  Reboot did not fix.  Alerts were "Your processor is
98.22 % loaded".

Top showed wa (waiting) % to be high.  The du process number kept increasing.

We've had this contrib for over 2 years and never had problem, the du -s was
always enabled (I think).  Setting Activate du -s to off fixed the problem.

I'm sure this is not enough information, but, I'm new to all this (1st bug
report).  Information below prompted by reading
http://wiki.contribs.org/Sme7admin

Name   : smeserver-sme7admin
Arch   : noarch
Version: 1.1.0
Release: 1
Size   : 355 k
Repo   : installed


Name   : sysstat
Arch   : i386
Version: 5.0.5
Release: 19.el4
Size   : 303 k
Repo   : installed

Name   : hddtemp
Arch   : i386
Version: 0.3
Release: 0.beta12.2.2.el4.rf
Size   : 89 k
Repo   : installed

Name   : perl-rrdtool
Arch   : i386
Version: 1.0.50
Release: 1.2.el4.rf
Size   : 279 k
Repo   : installed

Name   : rrdtool
Arch   : i386
Version: 1.0.50
Release: 1.2.el4.rf
Size   : 1.3 M
Repo   : installed

Have read the essay on bug reporting and realise I should be supplying some
hardware details too.  Not sure how to determine those but will have a go
(can't right now, remote from server).

I can also enable du -s before another tape backup and see if it occurs, but,
would like to know what I may be able to do by way of logging useful
information for that event (if that is possible).

The bug is not a problem for us as there are no SMART sensors on our server and
I see the HD useage in an email after every tape backup (full backup every
night).

-- 
Configure bugmail: http://bugs.contribs.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at http://lists.contribs.org/mailman/public/contribteam/

Reply via email to