Comment 32 for bug 406397

I think I'm running into this bug on an Ubuntu Lucid server. I tried to install the rsyslog package on this server, but the start / stop / restart functions would never complete (hangs forever). In the end, I had to abandon rsyslog and go back to sysklogd — bad solution, I need rsyslog, but I obviously don't have a choice if it simply won't work.

There are a bunch of other packages on this same server which use upstart-job as their init scripts; they seem to work OK as far as I'm aware, but the fact that rsyslog won't work makes me nervous.

Lucid is supposed to be an LTS release with support until 2015 (server edition), but is that fact going to help me in practice (i.e., is upstart ever going to be fixed for Lucid)? If I were to decide to upgrade this server to Maverick, is there any realistic reason to suppose that would help?

Should I simply scrounge around for an old-style init script for rsyslog to run on this server?

Is there some other solution I should be looking at?