Please can we get this in lucid as a backport since it's an LTS release?
--
openldap install bare bones need default DIT separate package
https://bugs.launchpad.net/bugs/442498
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in
I'll vote for gerry's patch.
--
tomcat fails to start with: /bin/bash already running.
https://bugs.launchpad.net/bugs/632554
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in ubuntu.
--
Ubuntu-server-bugs mailing list
On Wed, Nov 3, 2010 at 10:26 AM, gerry skerbitz
632...@bugs.launchpad.netwrote:
The problem is fixed if we add `-p $CATALINA_PID` to the
start-stop-daemon line in catalina_sh(). Isn't that something we should be
able to rely on?
{{{
*** tomcat6~2010-10-11 13:21:52.0 -0500
---
On Thu, Sep 9, 2010 at 5:48 AM, Thierry Carrez
thierry.car...@ubuntu.comwrote:
I agree that we should not force tomcat6 to run under a user that has no
bash running.
Note that the proposed patch breaks use of AUTHBIND. This should rather
be fixed by shipping once and for all the catalina.sh
Public bug reported:
Binary package hint: tomcat6
While it's not recommended to run tomcat as root, there are
circumstances that make it a necessity, like embedded systems. (IMHO
Linux should not enforce policy at this level)
Anyway, setting the following in /etc/default/tomcat6
** Patch added: This is a fix that does not alter the behavior in any way, but
fixes ths problem.
https://bugs.launchpad.net/bugs/632554/+attachment/1554204/+files/tomcat6-init.patch
--
tomcat fails to start with: /bin/bash already running.
https://bugs.launchpad.net/bugs/632554
You
Left debug info in patch...sorry. New patch attached.
** Patch added: Patch - without debug info and correct offsets this time.
https://bugs.launchpad.net/ubuntu/+source/tomcat6/+bug/632554/+attachment/1555462/+files/tomcat6-init.patch
--
tomcat fails to start with: /bin/bash already
Pin it back to Jaunty...groan.
Package: slapd
Pin: version 2.4.15-1ubuntu3
Pin-Priority: 1100
Package: ldap-utils
Pin: version 2.4.15-1ubuntu3
Pin-Priority: 1100
Package: libldap-2.4-2
Pin: version 2.4.15-1ubuntu3
Pin-Priority: 1100
-Bruce
On Thu, Jul 1, 2010 at 3:35 PM,
Can someone change this from wishlist to something more likely to get
fixed?
--
openldap install bare bones need default DIT separate package
https://bugs.launchpad.net/bugs/442498
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap
What is the functional state of openldap-dit? (https://launchpad.net
/openldap-dit/)
It hasn't seen any activity since 2009-12-02 and there are no milestones
and no available downloads. The trunk show last modified 20 weeks ago.
Is it functional, or the early stages of work in progress? The
Apologies in advance for the useless rant, but whose idea was it to
strip out the default ldap config?
I second the comments of everyone here that laments the time when slapd just
worked.
The cn=config change was difficult to swallow, but in the interest of progress,
OK, fine. This release
Just to get a feel for the state here, is there currently any work done
at all for this slapd-dit package?
Why is this marked as Won't fix? Is Ubuntu planning a new LTS release
with no LDAP? That'll go over well. Has anyone in canonocal mgmt even
seen this? Or is it a nasty little surprise
I'd like to bump the priority on this as it makes it impossible for
servers to come up clean.
For an LTS release, I would expect that having servers boot clean would
be a priority.
--
portmap is not started during boot process before autofs and hence autofs does
not work properly
Gets worse if you add SAN volumes that are NFS exported.
There's a corner case here that's not working at all:
1 - QLogic SAN - Fails to come up until I reload qla driver with modprobe
-r/modprobe
2 - NFS export, since #1 didn't come up, export also fails.
3 - Since #2 didn't come up, autofs
While I agree that it is possible to get the same behavior with the
addition of:
JAVA_OPTS=-Xdebug
-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n
-Djava.awt.headless=true -Xmx128M
to default/tomcat6, it is finding this information that is non-trivial.
A simple -d switch, or
** Attachment added: Adds jpda debug option to tomcat6 init.d
http://launchpadlibrarian.net/26639186/tomcatinit.patch
--
tomcat6 needs debug start mode with jpda
https://bugs.launchpad.net/bugs/375493
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
Binary package hint: tomcat6
I had filed this in the wrong place, but I don't see any links to it
now. Apologies if it's a dup.
Bits and pieces pasted here from different sources but it all describes
the prob.
tomcat 6 in jaunty:
dpkg -l | grep tomcat6
ii libtomcat6-java
Public bug reported:
Binary package hint: tomcat6
Here's a stack trace when I try to load my app with the ubuntu packaged
jaunty tomcat6:
May 10, 2009 11:11:28 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of
Forgot platform details:
This is an up to data jaunty 64 bit system.
It's running without an X server, if that matters. I know some java apps
barf because of this.
# update-java-alternatives -l
java-6-openjdk 1061 /usr/lib/jvm/java-6-openjdk
java-gcj 1042 /usr/lib/jvm/java-gcj
It's set to
** Attachment added: This is the web service that exhibits the problem on
tomcat6
http://launchpadlibrarian.net/26540236/service-war.war
--
tomcat6 with spring throws org/springframework/core/NestedExceptionUtils
https://bugs.launchpad.net/bugs/374567
You received this bug notification
Found a workaround, disabling TOMCAT_SECURITY in /etc/init.d/tomcat6
allows this app to run.
-Bruce
--
tomcat6 with spring throws org/springframework/core/NestedExceptionUtils
https://bugs.launchpad.net/bugs/374567
You received this bug notification because you are a member of Ubuntu
Server
21 matches
Mail list logo
