I don't set the home field manually. It's set by Mandriva Directory
Server. I think that the error come from that mail and home are, on my
config, un
I find it very wrong to consider that as a user fault because :
1) it was working previously and al least one existing configuration
(mine) was
Public bug reported:
Upgrading a working dovecot from karmic to lucid.
Cannot log anymore to Imap with error :
May 17 15:10:27 localhost dovecot: dovecot: Relative home directory paths not
supported (user pl...@ploum.net): maildir:/home/mail/pl...@ploum.net
It appears to be an error
in my config, I've the location configured as :
mail_location = maildir:/home/mail/%u
--
dovecot upgrade purposely breaks working configuration
https://bugs.launchpad.net/bugs/581718
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
chuck : the link is *not* a patch to solve the issue. The link is a
patch that introduced the issue itself.
The question is : what should people do if they have this error ? And
why was this patch introduced ?
--
dovecot upgrade purposely breaks working configuration
I'm using absolute path.
The problem is that the path was given by LDAP with :
user_attrs = mailbox=home (this is what is recommended in the
documentation)
It seems that, for whatever reason this string is passed directly to the
code and used as home. But because it starts with maildir:, it
Public bug reported:
Binary package hint: slapd
1) Take a working Ubuntu LDAP server using the pre-8.10 configuration
file : /etc/ldap/slapd.conf
2) Run the following python script :
#!/usr/bin/python
import ldap.schema
ssse, schema = ldap.schema.urlfetch(ldap://127.0.0.1;)
print ssse, schema
Here's the workaround. The bug is caused because the migration seems to
forbid anonymous access to subschema which is required by tools like
phpldapadmin and urlfetch.
1) Stop your ldap server.
2) modify the slapd.conf file to add the following :
access to dn=cn=subschema
by * read
#
I've been able to eventually migrate to Jaunty slapd. As I was
expecting, it was not configuration related because slaptest -u would
told me that my config fil was fine. Here are the step I followed :
1) Stop slapd. Backup and remove /etc/ldap and /var/lib/ldap. With them,
upgrade is impossible
** Changed in: openldap (Ubuntu)
Assignee: (unassigned) = Ubuntu Server Team (ubuntu-server)
--
Unable to migrate Intrepid configuration to Jaunty
https://bugs.launchpad.net/bugs/364531
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug
Changing the title as Salik seems to report that it's not related to
slapd.conf at all.
Is there any news on this issue or anything we should test ? It will be
time to migrate to Karmic soon and we are still using intrepid packages.
** Summary changed:
- Unable to migrate Intrepid slapd.conf
Public bug reported:
I'm upgrading my server from Intrepid to Jaunty. Straight upgrade,
nothing fancy. It should just work.
Note : etckeeper was misconfigured and I ctrl+c the first upgrade
attempt. It's the only bad thing I did (and I should be allowed to do
so).
Then, the whole upgrade
The workaround for now is to keep the following packages from intrepid :
ldap-utils
libldap-2.4-2
slapd
Any attempt to upgrade those packages will break the configuration.
** Summary changed:
- Incredibly painful Jaunty upgrade
+ Unable to migrate Intrepid configuration to Jaunty
--
Unable
** Changed in: suphp (Ubuntu)
Status: New = Confirmed
--
php5-cgi not working with suphp in Hardy
https://bugs.launchpad.net/bugs/253268
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
Ubuntu-server-bugs
Public bug reported:
apt-get dist-upgrade from my hardy server to intrepid :
Preparing to replace slapd 2.4.9-0ubuntu0.8.04.1 (using
.../slapd_2.4.11-0ubuntu5_i386.deb) ...
Stopping OpenLDAP: slapd.
/var/lib/dpkg/tmp.ci/config: line 944: local: can only be used in a function
dpkg: error
It seems to be related to the migration of the configuration because
slapd install fine if the /etc/ldap folder is removed.
--
[intrepid] cannot upgrade from hardy to intrepid : local can only be used in a
function
https://bugs.launchpad.net/bugs/288897
You received this bug notification
Public bug reported:
Upgrading a perfectly working Dovecot (using LDAP) server from Hardy to
Intrepid gives the message :
Aug 13 17:18:26 shaun dovecot: auth(default): Error in configuration file
/etc/dovecot/dovecot-ldap.conf line 10: Unknown setting: user_global_uid
Aug 13 17:18:26 shaun
In fact, it seems that, unlike in Debian, libapache2-mod-php5 takes
precedence over suphp. It means that you cannot install both and use
suphp only on specific locations because mod-php5 will be called.
In Debian, this is not the case.
--
php5-cgi not working with suphp in Hardy
Public bug reported:
Suphp doesn't work in Hardy. It seems that it is simply ignored and php
processes are executed under www-data.
It was working fine under Gutsy. I dist-upgraded a month ago but I
discovered the problem only recently (because one of my website was
unable to read a config file
I cannot access to file shared on the SMB network with Hardy. Nautilus
see the computers but, when I open them, Nautilus displays them empty.
Works fine with Gutsy, even on a live CD. I comment here because it
might be related. If this is the case, the status of this bug is quite
important because
I must add that it seems a pretty critical issue to me. (at least here,
I must stop a few Ubuntu migration until this problem is solved.) Anyone
to recommend a Gtk samba browser so I can still browse the shares
without rebooting Windows ?
--
nautilus-share report a warning about missing
20 matches
Mail list logo
