** Branch linked: lp:~cjwatson/ubuntu/trusty/rsyslog/repair-groups
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/484336
Title:
/etc/rsyslog.conf permissions incorrect/missing for creation of
** Branch linked: lp:ubuntu/trusty-proposed/rsyslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/484336
Title:
/etc/rsyslog.conf permissions incorrect/missing for creation of
dynamic files
To
This bug was fixed in the package rsyslog - 7.4.4-1ubuntu2
---
rsyslog (7.4.4-1ubuntu2) trusty; urgency=low
* debian/rsyslog.postinst: Make sure /var/log is owned by group syslog and
is group-writeable (LP: #1256695).
* Ensure that rsyslogd can create files in group adm, even
12.04.1 LTS
Workaround does not work.
But if you drop both Group and Owner to adm dynamic files can be created, have
not tried with directories.
$PrivDropToUser adm
$PrivDropToGroup adm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
We changed to this and chowned some dirs which needed but rarely needed.
$PrivDropToUser syslog
$PrivDropToGroup adm
On 22 February 2013 14:40, Vincens Mink vinc...@ribermink.com wrote:
12.04.1 LTS
Workaround does not work.
But if you drop both Group and Owner to adm dynamic files can be
Im another user who has experienced this bug in 12.04.
The drop privileges workaround supplied above does not fix the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/484336
Title:
I'm using Ubuntu 12.04 and the bug is still there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/484336
Title:
/etc/rsyslog.conf permissions incorrect/missing for creation of
dynamic files
To
So what happens?
Will it ever be fixed in Ubuntu repos or I need to create a deb package for
rsyslog myself and distribute it with my software?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/484336
I confirm that the patch in comment #1 works on Lucid. Setting the
$DirOwner and $DirGroup was essential to have rsyslog to creating new
directories that are part of the path to the dynamic files
(/var/log/central/%$YEAR%/%$MONTH%/%$DAY%/%HOSTNAME%.log).
I agree that using $PrivDropToGroup adm
I'm just discovering this same issue, and agree that $PrivDropToGroup
adm does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/484336
Title:
/etc/rsyslog.conf permissions incorrect/missing
Encountered on Ubuntu 11.04, changing $PrivDropToGroup adm does not
allow dynamic files to be created.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/484336
Title:
/etc/rsyslog.conf permissions
I ran into this problem today, too.
I do not fully understand about it yet, but changing $PrivDropToUser syslog
to $PrivDropToGroup adm looks like working for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I ran into this today. If I understand correctly the privilege drop
happens before the chown though it should be the other way around, the
chown should happen while root and then privileges should be dropped.
And in any case the failure of chown should not prevent the logs from
writing. The
No, that's the same.
Commenting out those lines makes rsyslogd run as root (which is very
dangerous)
Setting $PrivDropToGroup adm (to match $FileGroup adm) is a less
dangerous solution to the problem, although still not ideal from a
security point of view.
Now, rsyslogd has sufficient rights to
Edit: I ment to say I had to comment out... NOT uncomment
doing this
#$PrivDropToUser syslog
#$PrivDropToGroup syslog
---
Very strange. I had to uncomment these two lines for it to work
$PrivDropToUser syslog
$PrivDropToGroup syslog
Seems like the complete opposite of what everyone else here
Very strange. I had to uncomment these two lines for it to work
$PrivDropToUser syslog
$PrivDropToGroup syslog
Seems like the complete opposite of what everyone else here is saying.
Ubuntu 10.04.3 LTS x86
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For some informative discussion on this problem, see the following
message thread:
http://kb.monitorware.com/trouble-getting-dynamic-files-work-t10054.html
--
/etc/rsyslog.conf permissions incorrect/missing for creation of dynamic files
https://bugs.launchpad.net/bugs/484336
You received this
I agree with the security concerns brought up by @George Klein .
--
/etc/rsyslog.conf permissions incorrect/missing for creation of dynamic files
https://bugs.launchpad.net/bugs/484336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Same problem for me.
Changing $PrivDropToGroup syslog to $PrivDropToGroup adm fixes this.
Am using Ubuntu 10.04 LTS Server
** Changed in: rsyslog (Ubuntu)
Status: New = Confirmed
--
/etc/rsyslog.conf permissions incorrect/missing for creation of dynamic files
Using 10.04 LTS. After fixing privileges it works with dynamic files -
but only under very little load. When I pointed three ASA firewalls
(tens of messages per second each) to my server, rsyslog lost ability to
write files again. Aftre service restart it works for several seconds
and dies. RIP.
Just found this and it's covering similar ground to bug #407862. From
my experience in that bug:
I agree that $DirOwner and $DirGroup should be configured.
I agree that $DirGroup, $FileGroup and $PrivDropToGroup have to be the same for
rsyslog to create dynamic files properly.
However I don't
** Attachment added: Proposed patch for rsyslog.conf
http://launchpadlibrarian.net/35789407/rsync.conf.patch
--
/etc/rsyslog.conf permissions incorrect/missing for creation of dynamic files
https://bugs.launchpad.net/bugs/484336
You received this bug notification because you are a member of
** Description changed:
Binary package hint: rsyslog
- When using templates to create dynamic files with rsyslog, rsyslog fails
- to have the appropriate perms to access them.
+ When using templates to create dynamic directories and files with
+ rsyslog, rsyslog can create the directories,
23 matches
Mail list logo
