[update-motd] Re: ubuntu stucks

[NoOp]

On 03/16/2010 03:57 AM, Donatas Fetingis wrote:
> Hello,
> i have a problem on my backup machine with ubuntu with kernel 2.6.28-18.
> 
> Sometimes it just stucks and i have to manualy reboot (reset)
> syslog shows that it stuck under cron job update-modt. Where else i 
> should search for a problem?
> 
> Thank You!
> 
> Donatas

You didn't say what version you are running, but I reckon that by the
kernel you are running jaunty.

According to the update-motd package description:
http://packages.ubuntu.com/karmic/update-motd
====
superceded by pam_motd in libpam-modules

This package installs a script in /etc/profile.d that dynamically
generates a message-of-the-day by running scripts installed in
/etc/update-motd.d, in lexical order.

Other packages, or system administrators should symlink scripts into
/etc/update-motd.d, pre-pending a 2-digit number to handle ordering.

The functionality formerly provided by this package is now integrated
into pam_motd, in libpam-modules.

Canonical provides critical updates for update-motd until April 2011.
====

So you might either purge the package, or rename it & see if that
resolves the issue. Launchpad doesn't list any currenly open bugs:
https://launchpad.net/distros/ubuntu/+source/update-motd/+bugs
so you can file a bug against it if you wish. Doing an advance search:
<https://bugs.launchpad.net/ubuntu/+source/update-motd/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on>
doesn't seem to reveal any similar bugs. But you can certainly check
through each to see if there is anything related to your issue.