Re: Mysterious hangs since upgrading to Wheezy
Following up with an addendum: David Guntner grabbed a keyboard and wrote: Now, on my main desktop, I keep two windows always open, one running top and the other tailing the syslog. Top was showing a load in excess of 5.00 (which I think is a bit excessive...) and was gradually going down. The only thing of possible note that I could see in they syslog was that dbus (I don't remember seeing those messages in squeeze, so I'm guessing this is new and I'm wondering if it's something I actually need, but that's a different story :-) ) had just activated a service called org.freedesktop.PackageKit using service helper, and about 20 seconds after that was two messages saying that rsyslogd had been HUPed (this is not during the time when logrotate runs, so I'm pretty sure it wasn't logrotate that HUPed it). I just discovered that the upgrade thoughtfully added anacron back to my system (I removed it from squeeze because my system is used as a server, thus is up 24/7, thus doesn't need anacron). I note that anacron is a suggests in the entry for cron (aptitude show cron), so I'm guessing that apt/aptitude now installs things which are simply suggested? If that's so, is there a way to turn that off? It looks like logrotate did in fact run, thanks to the anacron, which looks like it uses the default values you'd get in /etc/crontab for the times to run things within its own configuration. Checking the syslog files confirms that a logrotate did take place at the time the HUPed message shows up in the log. Man, I hope that doing log rotation is not what's causing the system to hang so severely while it's running I'll continue to monitor the situation, and if I get anything new, I'll post here. --Dave smime.p7s Description: S/MIME Cryptographic Signature
Re: Mysterious hangs since upgrading to Wheezy
On Sun 04 Aug 2013 at 08:45:19 -0700, David Guntner wrote: I just discovered that the upgrade thoughtfully added anacron back to my system (I removed it from squeeze because my system is used as a server, thus is up 24/7, thus doesn't need anacron). I note that anacron is a suggests in the entry for cron (aptitude show cron), so I'm guessing that apt/aptitude now installs things which are simply suggested? If that's so, is there a way to turn that off? Installing suggests is not default behaviour. A look at your system and the output of 'apt-cache rdepends anacron' may help to track down why it was installed. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/04082013175052.12f2e3f99...@desktop.copernicus.demon.co.uk
Re: Mysterious hangs since upgrading to Wheezy
Brian grabbed a keyboard and wrote: On Sun 04 Aug 2013 at 08:45:19 -0700, David Guntner wrote: I just discovered that the upgrade thoughtfully added anacron back to my system (I removed it from squeeze because my system is used as a server, thus is up 24/7, thus doesn't need anacron). I note that anacron is a suggests in the entry for cron (aptitude show cron), so I'm guessing that apt/aptitude now installs things which are simply suggested? If that's so, is there a way to turn that off? Installing suggests is not default behaviour. A look at your system and the output of 'apt-cache rdepends anacron' may help to track down why it was installed. Thanks for the info. I gave it a try: $ apt-cache rdepends anacron anacron Reverse Depends: anacron:i386 update-notifier task-laptop task-desktop popularity-contest |logrotate update-notifier-kde kde-config-cron gnumed-server gnome-schedule fiaif email-reminder cron |checksecurity bcron-run backup-manager I checked a bunch of those. They all showed either requires cron and suggests anacron, or requires cron | anacron (which we know means it wants either - since cron was already in the system, I'm not sure if that would have triggered an anacron install during a dist-upgrade). Strange stuff, that. Either way, doing a purge of anacron (again grin) got rid of it, and there were no dependency complaints when I did it - the purge command got rid of only one package. Well, I'll continue to keep an eye on things. It does turn out that anacron was running the show at around the time I had my issue. Between log rotations, other things that it does, and tripwire (whoops, forgot to update that manually after the update, so I got a 3.2M E-Mail this morning listing all the things it saw as changed lol), it could just be that the system really *was* bogged down between all the heavy stuff going on at the time. I'm not typically awake at the time that cron runs all those things, so it will be hard to tell if future run-daily jobs will have as strong of an impact as it might have today. But I'll definitely be on the lookout for any additional strange system hangs --Dave smime.p7s Description: S/MIME Cryptographic Signature
Re: Mysterious hangs since upgrading to Wheezy
Hi David! Am Sonntag, 4. August 2013, 08:31:21 schrieb David Guntner: […] Since I upgraded from Squeeze to Wheezy yesterday, I've noticed periodic hangs, where the system seems to just be *seriously* loaded down. It happened again this morning - it was so bad I was just about to press the reset button to force a reboot because I thought the machine itself was hung. […] Now, on my main desktop, I keep two windows always open, one running top and the other tailing the syslog. Top was showing a load in excess of 5.00 (which I think is a bit excessive...) and was gradually going down. The only thing of possible note that I could see in they syslog was that dbus (I don't remember seeing those messages in squeeze, so I'm guessing this is new and I'm wondering if it's something I actually need, but that's a different story :-) ) had just activated a service called org.freedesktop.PackageKit using service helper, and about 20 seconds after that was two messages saying that rsyslogd had been HUPed (this is not during the time when logrotate runs, so I'm pretty sure it wasn't logrotate that HUPed it). I suggest using atop -r atop-raw-file -b 12:00 -e 13:00 as well as atopsar -O Report about top-3 processes consuming most processor capacity. -G Report about top-3 processes consuming most resident memory. -D Report about top-3 processes issueing most disk transfers. -N Report about top-3 processes issueing most IPv4/IPv6 socket transfers. To find out which processes are bogging down the system. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 signature.asc Description: This is a digitally signed message part.
Re: Mysterious hangs since upgrading to Wheezy
On 04/08/13 18:19, David Guntner wrote: I'm not typically awake at the time that cron runs all those things, so it will be hard to tell if future run-daily jobs will have as strong of an impact as it might have today. Another opportunity for a little plug for munin: http://munin-monitoring.org/ Very easy to set up, and lightweight system monitor, producing pretty graphs for when your eyes have gotten used to daylight again ;-) -- Klaus -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51feb0d1.3050...@gmail.com
Re: Mysterious hangs since upgrading to Wheezy
Martin Steigerwald grabbed a keyboard and wrote: Hi David! Am Sonntag, 4. August 2013, 08:31:21 schrieb David Guntner: […] Since I upgraded from Squeeze to Wheezy yesterday, I've noticed periodic hangs, where the system seems to just be *seriously* loaded down. It happened again this morning - it was so bad I was just about to press the reset button to force a reboot because I thought the machine itself was hung. […] Now, on my main desktop, I keep two windows always open, one running top and the other tailing the syslog. Top was showing a load in excess of 5.00 (which I think is a bit excessive...) and was gradually going down. The only thing of possible note that I could see in they syslog was that dbus (I don't remember seeing those messages in squeeze, so I'm guessing this is new and I'm wondering if it's something I actually need, but that's a different story :-) ) had just activated a service called org.freedesktop.PackageKit using service helper, and about 20 seconds after that was two messages saying that rsyslogd had been HUPed (this is not during the time when logrotate runs, so I'm pretty sure it wasn't logrotate that HUPed it). I suggest using atop -r atop-raw-file -b 12:00 -e 13:00 as well as atopsar -O Report about top-3 processes consuming most processor capacity. -G Report about top-3 processes consuming most resident memory. -D Report about top-3 processes issueing most disk transfers. -N Report about top-3 processes issueing most IPv4/IPv6 socket transfers. To find out which processes are bogging down the system. Interesting find for me on that one! It wasn't in the system, but is now. From what I've read so far in the man pages and so on, it looks like the running daemon collects the information and takes a snapshot of what was happening every 10 minutes. If this hang happens again, I'm not sure that this utility will catch it in the act unless things just happen to line up Just Right. :-) But it's certainly a cool tool to have, and I'm glad for knowing about it now. Just to be clear: The hang happened yesterday right after I rebooted the system after doing all the updates, only lasted for a minute at MOST (probably was a lot shorter, but we all know that when the system hangs for a bit, it *feels* a lot longer grin). Then again (at least, that I observed) this morning during the time when I believe anacron was running all the daily jobs with log rotations, other things, and tripwire doing it's thing (generating a HUGE E-Mail since everything changed from its last run). I'll keep an eye out and if it happens again, I'll run the command you mention above once it comes out of the hang to see if by any chance it caught the culprit in the act. --Dave smime.p7s Description: S/MIME Cryptographic Signature
Re: Mysterious hangs since upgrading to Wheezy
Klaus grabbed a keyboard and wrote: On 04/08/13 18:19, David Guntner wrote: I'm not typically awake at the time that cron runs all those things, so it will be hard to tell if future run-daily jobs will have as strong of an impact as it might have today. Another opportunity for a little plug for munin: http://munin-monitoring.org/ Very easy to set up, and lightweight system monitor, producing pretty graphs for when your eyes have gotten used to daylight again ;-) I've looked a bit at the website; looks interesting. And I note that munin seems to have packages as part of Debian, so that should make it easy to install. :-) I'll check into it. Thanks for the tip! --Dave smime.p7s Description: S/MIME Cryptographic Signature
