Public bug reported:
On a fairly pristine 14.10, after installing tomcat8 and oracle-java8-installer
I get:
* no JDK or JRE found - please set JAVA_HOME
I found this error message is kind of confusing because even after setting
JAVA_HOME in /etc/enviromnent or any profiles, it is simply ignore
.
+ Fixes "Bad variable name" error when there are spaces in the current
directory path. (Closes: #763725)
* Urgency high due to fixing a grave bug.
* Updated the watch file, to not create silly named files. This
hopefully fixes the issue on tracker.d.o.
-- Gergely Nagy Sat, 0
FWIW, the Debian package ships the bash completion still (and is at
1.7.0-1).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322816
Title:
Bash Autocomplete Support
To manage notifications about th
Not sure it is worth converting to Upstart, because it won't be fixed in
12.04, nor in Trusty either, and the next LTS will have systemd (and
syslog-ng has been converted to systemd already).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Saucy and later do not have this bug.
** Changed in: syslog-ng (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103326
Title:
syslog-ng-3.3.4 seg
This has actually been fixed in Saucy already.
** Changed in: syslog-ng (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074074
Title:
mail log d
** Changed in: syslog-ng (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/760464
Title:
"WARNING: at /build/buildd/linux-2.6.38/kernel/printk.c:288
do_
** Changed in: syslog-ng (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074074
Title:
mail log destination and logrotate differ
To manage notifications
This has been fixed in later versions, and 3.5 in Trusty does not have
this problem anymore.
** Changed in: syslog-ng (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Can't reproduce this with neither 3.3, nor 3.5.
** Changed in: syslog-ng (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/550596
Title:
spikes u
This has been fixed quite a while ago.
** Changed in: syslog-ng (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936809
Title:
/etc/init.d/syslog-ng incorre
This has been fixed with module-autoloading in syslog-ng 3.4, and 3.5 is
in Trusty, so setting the state accordingly.
** Changed in: syslog-ng (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Likely, because noone took the effort. In any case, updated syslog-ng
packages are available at http://asylum.madhouse-
project.org/projects/debian/ - you are recommended to use that
repository if you need a newer syslog-ng on Lucid.
** Changed in: syslog-ng (Ubuntu)
Status: New => Opinion
Trusty will have 3.5, which has these issues fixed.
** Changed in: syslog-ng (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1049202
Title:
syslog-n
This really is a problem of ubuntu-minimal, which depends on rsyslog
alone, instead of rsyslog | system-log-daemon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242173
Title:
syslog-ng package fai
** Changed in: syslog-ng (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/919666
Title:
configuratoin example uses authentication and encryption parame
** Changed in: syslog-ng (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/678402
Title:
No need to use $SYSLOGNG_OPTS in case of reload
To manage notificati
** Changed in: syslog-ng (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/661745
Title:
reload fails with options in /etc/default/syslog-ng
To manage notifi
This is an old report, and the crash has likely been fixed by then, so
I'm setting it to Incomplete, because I can't reproduce it anymore, and
never received any more feedback, either.
** Changed in: syslog-ng (Ubuntu)
Status: New => Incomplete
--
You received this bug notification becaus
** Changed in: syslog-ng (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/649046
Title:
"/etc/init.d/syslog-ng reload" fails if SYSLOGNG_OPTS is set
To mana
I'm seeing the same too, but this only seems happens on amd64, my i386
chroot is not affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066445
Title:
Crashes doing update or upgrade operations
In all honesty, I believe the best would be to push 3.3.6 (or better
yet, 3.3.7 due on Oct 31) into the next LTS point release due to the
large amount of fixes both small and large that went into that release.
I'm not entirely sure whether that's possible, and if so, how, but with
my upstream hat o
FWIW, I fixed this in my git repository, and it will be fixed upstream
too, soon enough. Would it have been forwarded to Debian (or better,
upstream), we would have removed the obsolete keywords long ago.
In the future, when triaging bugs, consider forwarding them upstream, it
yields much faster r
Changes that are not strictly bugfixes (and can affect Ubuntu users)
are:
* The db-parser() will tag messages with '.classifier.unknown' if the message
does not match.
* The value of the $TAGS macro is added to pdbtool match output.
* An inconsistency within db-parser() introduced an incompatible
Source package is available from: http://madhouse-
project.org/algernon/ubuntu/precise/syslog-ng-3.3.4/
The install log (which also shows that the result starts, and appears to
work at least minimally) is attached.
** Attachment added: "Install & minimal functionality verification log"
https:
** Attachment added: "Build log"
https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/950799/+attachment/2839715/+files/syslog-ng_3.3.4.dfsg-2ubuntu1_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Attachment added: "NEWS between 3.3.1 and 3.3.4"
https://bugs.launchpad.net/bugs/950799/+attachment/2839713/+files/NEWS.3.3.1-3.3.4.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950799
Tit
Public bug reported:
I would like to request a freeze exception for syslog-ng, to replace the
current version in Precise (3.3.1+patches) with the version currently in
Debian testing (3.3.4+patches). The rationale being that there have been
a ton of bugfixes made since 3.3.1, and the version curren
dpatch-get-origtargz was removed in 2.0.32. I can't set wontfix, so...
fix released it is.
** Changed in: dpatch (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
This has been fixed in dpatch 2.0.32, Ubuntu has 2.0.33 as far as I see.
** Changed in: dpatch (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/121259
Tit
This is fixed in 0.1.4-1, uploaded to unstable a couple of hours ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/831233
Title:
libmongo-client version 0.1.3-1 failed to build in oneiric
To manag
This is harmless (see https://bugs.launchpad.net/ubuntu/+source/syslog-
ng/+bug/759590), and unrelated. As for restart: that probably won't
crash it. My suspicion is reload, under certain conditions. I'll play
with that tonight.
--
You received this bug notification because you are a member of Ub
Yeah, it's not feasible to run syslog-ng under strace all the time.
But if it takes days to crash... perhaps it happens when reloading
syslog-ng? That gave me an idea, thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
The kernel developers decided that one should use CAP_SYSLOG to access
/proc/kmsg, instead of CAP_SYS_ADMIN (a good change, in itself), and
that the kernel should warn once per process when a program tries to
access it with the old capability.
The easy solution or workaround for Natty is to disabl
I couldn't reproduce this on a freshly installed Ubuntu 11.04 (x86).
I'll try upgrading and x86-64 aswell..
Is there anything particular that triggers the crash, does it happen
randomly, or every time syslog-ng would receive a message?
(For the record, I only have file destinations: no program, n
I'm happy to report that this is now working for me after yesterday's
ubuntu update, now having kernel 2.6.31-15-generic #50-Ubuntu
thanks,
Greg
--
[i945GM] Display mirrored-ish after resume
https://bugs.launchpad.net/bugs/404509
You received this bug notification because you are a member of Ubu
36 matches
Mail list logo
