sysklogd (1.4.1-21ubuntu3) gutsy; urgency=low
* debian/rc:
* Fix syslogd to run as syslog user. Fix LP: #120085.
* Add comment that points to /etc/default/syslogd to set default options.
Fix LP: #103232.
* debian/cron.daily, debian/cron.weekly:
* Rotate logs with the correct
I've added a new debdiff that fixes the above issue.
** Attachment added: "sysklogd_1.4.1-21ubuntu3-5.debdiff"
http://launchpadlibrarian.net/9311534/sysklogd_1.4.1-21ubuntu3-5.debdiff
** Attachment removed: "sysklogd_1.4.1-21ubuntu3-4.debdiff"
http://launchpadlibrarian.net/9284255/sysklogd_1.
Approved for Gutsy. Up until dapper, running it as system user worked
fine and we still have enough time to test it properly and fix it
further, if necessary.
--
Various problems running syslogd with "-u syslog" option
https://bugs.launchpad.net/bugs/120085
You received this bug notification beca
In your cron.{daily,weekly} modifications:
+[ -z "${USER}" ] && USER="root"
you should append || true, so that the script does not bail out if $USER
is not zero. That's only an issue if the script is under set -e, but
it's generally more robust.
--
Various problems running syslogd with "-u sysl
Attached another version which makes more sense.
** Attachment added: "sysklogd_1.4.1-21ubuntu3-4.debdiff"
http://launchpadlibrarian.net/9284255/sysklogd_1.4.1-21ubuntu3-4.debdiff
** Attachment removed: "sysklogd_1.4.1-21ubuntu3-2.debdiff"
http://launchpadlibrarian.net/9186373/sysklogd_1.4.1-
I've attached a new debdiff that checks whether the regex to extract a
user will match or not.
** Attachment added: "sysklogd_1.4.1-21ubuntu3-3.debdiff"
http://launchpadlibrarian.net/9284235/sysklogd_1.4.1-21ubuntu3-3.debdiff
--
Various problems running syslogd with "-u syslog" option
https:/
Moving milestone to beta.
This was raised at the meeting, who is going to make the call on whether
we change this?
** Changed in: sysklogd (Ubuntu)
Target: tribe-6 => ubuntu-7.10-beta
--
Various problems running syslogd with "-u syslog" option
https://bugs.launchpad.net/bugs/120085
You
** Changed in: sysklogd (Ubuntu)
Assignee: Ubuntu Server Team => Canonical Server Team
--
Various problems running syslogd with "-u syslog" option
https://bugs.launchpad.net/bugs/120085
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for U
On Fri, Sep 07, 2007 at 11:09:12PM -, Mathias Gug wrote:
> I've attached a new debdiff that also fixes the weekly and daily cron
> script from sysklogd.
Looks good. The only thing I question is whether it's a good idea to change
the default this late in the release cycle, as there may be othe
I've attached a new debdiff that also fixes the weekly and daily cron
script from sysklogd.
** Attachment added: "sysklogd_1.4.1-21ubuntu3-2.debdiff"
http://launchpadlibrarian.net/9186373/sysklogd_1.4.1-21ubuntu3-2.debdiff
** Attachment removed: "sysklogd_1.4.1-21ubuntu3.debdiff"
http://launc
On Thu, Sep 06, 2007 at 09:32:48PM -, Mathias Gug wrote:
> I've attached a debdiff that should fix the issue in gutsy.
>
> I've looked into the suggestion of dropping the root privilege before
> init. However it won't work as init parses the configuration file to
> open the log files. If netwo
On Thu, Sep 06, 2007 at 09:34:05PM -, Markus Schlager wrote:
> Yes indeed. In our case it started to fail on Saturday, June 16th due to
> the call of /etc/cron.daily/sysklogd.
>
Could you figure out which packages have been upgraded around that time
?
--
Various problems running syslogd wi
On Thu, 6 Sep 2007, Mathias Gug wrote:
> I'm trying to figure out what change caused you the problem. Is it a
> fresh install of dapper ?
Yes. (i.e. no upgrade from breezy)
> Was it working before but started to fail after an
> upgrade ?
>
Yes indeed. In our case it started to fail on Saturd
I've attached a debdiff that should fix the issue in gutsy.
I've looked into the suggestion of dropping the root privilege before
init. However it won't work as init parses the configuration file to
open the log files. If network logging is required (which is only known
after the configuration fil
On Thu, Sep 06, 2007 at 03:44:23PM -, Jörn Dreyer wrote:
> I used the workaround Markus Schlager proposed:
> changed SYSLOGD=" -u syslog" into SYSLOGD=" " in /etc/init.d/sysklogd
>
I'm trying to figure out what change caused you the problem. Is it a
fresh install of dapper ? Was it working b
I used the workaround Markus Schlager proposed:
changed SYSLOGD=" -u syslog" into SYSLOGD=" " in /etc/init.d/sysklogd
--
Various problems running syslogd with "-u syslog" option
https://bugs.launchpad.net/bugs/120085
You received this bug notification because you are a member of Ubuntu
Bugs, whic
It seems that there are two issues here, one for gutsy and one for
dapper.
The issue that was reported is for gutsy and shouldn't apply for dapper.
In dapper, the reload action in the init script stops then starts the
syslog daemon. In gutsy, the reload action in the init script sends a
HUP signa
On Wed, Sep 05, 2007 at 09:07:06PM -, Mathias Gug wrote:
>
> This problem doesn't affect the default configuration. The default
> configuration file doesn't mention the option to change the user under
> which the syslogd daemon is running.
> The comment in the init script may be removed as it
I disagree ... the problem is that in dapper ther is no
/etc/default/syslogd. The problem described by Markus Schlager and
confirmed by me still makes it quite critical I think.
--
Various problems running syslogd with "-u syslog" option
https://bugs.launchpad.net/bugs/120085
You received this bu
** Changed in: sysklogd (Ubuntu)
Assignee: (unassigned) => Ubuntu Server Team
--
Various problems running syslogd with "-u syslog" option
https://bugs.launchpad.net/bugs/120085
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
We can confirm this on dapper lts. Exactly the same behaviour as Markus
Schlager reported in
https://bugs.launchpad.net/ubuntu/+source/sysklogd/+bug/120085/comments/2
--
Various problems running syslogd with "-u syslog" option
https://bugs.launchpad.net/bugs/120085
You received this bug notificat
I've confirmed this behaviour here. Each and every time that syslogd is
reloaded (including by cron.daily), all logging ceases, as it fails to
open all of its log files.
** Changed in: sysklogd (Ubuntu)
Importance: Undecided => Critical
Status: New => Triaged
Target: None => trib
** Attachment added: "strace log"
http://launchpadlibrarian.net/9097266/strace.txt
--
Various problems running syslogd with "-u syslog" option
https://bugs.launchpad.net/bugs/120085
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu
better workaround for the moment:
changed SYSLOGD=" -u syslog" into SYSLOGD=" " in /etc/init.d/sysklogd.
Meanwhile the computer wouldn't even halt nor boot with this option
enabled.
--
Various problems running syslogd with "-u syslog" option
https://bugs.launchpad.net/bugs/120085
You received th
Thanx a lot for your explanations, Graeme!
I can confirm this on our server, running dapper-lts. We're experiencing these
problems since last Friday, 15.6.2007. The consequences are quite serious.
Since we're using an openLDAP-Server on this machine for user-authentification,
this bug in /etc/c
Sorry, the penultimate paragraph above is probably wrong, since auth.log
would normally exist at boot time, with mode 640.
--
Various problems running syslogd with "-u syslog" option
https://bugs.launchpad.net/bugs/120085
You received this bug notification because you are a member of Ubuntu
Bugs,
26 matches
Mail list logo
