headers
Thomas Spuhler | 1 Aug 2010 01:43

Re: Partial Upgrade to 2.2.4

On Tuesday, July 27, 2010 02:18:31 am Carsten Burghardt wrote:
> Zitat von Thomas Spuhler <thomas <at> btspuhler.com>:
> > On Monday, July 26, 2010 05:50:43 pm Thomas Spuhler wrote:
> >> On Monday, July 26, 2010 05:15:52 am Carsten Burghardt wrote:
> >> > Zitat von Thomas Spuhler <thomas <at> btspuhler.com>:
> >> > > On Saturday, July 24, 2010 09:41:13 am Nicholas Moore wrote:
> >> > >> Hi Carsten,
> >> > >> 
> >> > >> I am in a similar situation to the one you describe. Did you make
> >> > >> any progress?
> >> > >> 
> >> > >> Nicholas
> >> > >> 
> >> > >> On Monday 19 Jul 2010 12:58:32 Carsten Burghardt wrote:
> >> > >> > Hi,
> >> > >> > 
> >> > >> > I would like to upgrade my Kolab 2.2.2 to 2.2.4 but as I used
> >> > >> > SuSE packages (11.2) so far I would prefer not to reinstall
> >> > >> > everything from scratch as that duplicates a lot of packages. Is
> >> > >> > there any chance to keep my existing installation and only
> >> > >> > compile kolab specific packages? SuSE is on OpenSSL 0.9.8 so
> >> > >> > that is a difference of course.
> >> > >> > 
> >> > >> > 
> >> > >> > Regards
> >> > >> > 
> >> > >> > Carsten
> >> > >> > 
> >> > >> > 
> >> > >> >
(Continue reading)

Permalink | Reply | 0 comments |
headers
jguy | 1 Aug 2010 07:16
Picon
Gravatar

kolab-server-2.2.4 installation from source, + exit 123 error: Bad exit status (perl)

  Following installation instructions from: 
http://files.kolab.org/server/release/kolab-server-2.2.4/sources/1st.README

Up to the step: sh install-kolab.sh 2>&1 | tee /root/kolab-install.log
All steps prior were followed, including bison and flex installed, 
SELinux turned off, gcc, make, libtool, automake and autoconf installed, 
   signature/checksums verified, running as root

The build stopped at the perl installation with the following log:

+ case "i686-linux2.6" in
+ cd /usr/include
+ PERL5LIB=/kolab/RPM/TMP/perl-5.10.0-root/kolab/lib/perl
+ export PERL5LIB
++ /kolab/RPM/TMP/perl-5.10.0-root/kolab/bin/perl -V:installarchlib
+ eval 'installarchlib='\''/kolab/lib/perl/5.10.0/i686-linux'\'';'
++ installarchlib=/kolab/lib/perl/5.10.0/i686-linux
+ echo FlexLexer.h _G_config.h a.out.h af_vfs.h aio.h aliases.h

<snip .h header file names>

wait.h sys/xattr.h
+ xargs /kolab/RPM/TMP/perl-5.10.0-root/kolab/bin/perl 
/kolab/RPM/TMP/perl-5.10.0-root/kolab/bin/h2ph -h -d

/kolab/RPM/TMP/perl-5.10.0-root/kolab/lib/perl/5.10.0/i686-linux
FlexLexer.h -> FlexLexer.ph
_G_config.h -> _G_config.ph

<snip header -> perl file names>
(Continue reading)

Permalink | Reply | 8 comments |
headers
Gavin McCullagh | 1 Aug 2010 12:15
Picon
Favicon

login to imapd with local username is killing me

Hi,

having finally migrated to our new kolab setup and had to change everyone's
username from <username> to <username> <at> <domain>, I'm not getting lots of
confused users who are not following instructions and persisting with the
old <username>.  

They _should_ be unable to login.  Instead, they login, see no email and
presume we've lost all of their email in the transition.  This is described
in issue2869:
	https://issues.kolab.org/issue2869

Can anyone think of a workaround to block people from logging in with the
local username?  This is really causing us a lot of problems.

Gavin

--

-- 
Gavin McCullagh
Senior System Administrator
IT Services
Griffith College 
South Circular Road
Dublin 8
Ireland
Tel: +353 1 4163365
http://www.gcd.ie
http://www.gcd.ie/brochure.pdf
http://www.gcd.ie/opendays
(Continue reading)

Permalink | Reply | 4 comments |
headers
Gavin McCullagh | 1 Aug 2010 12:35
Picon
Favicon

Re: login to imapd with local username is killing me

Hi,

On Sun, 01 Aug 2010, Gavin McCullagh wrote:

> having finally migrated to our new kolab setup and had to change everyone's
> username from <username> to <username> <at> <domain>, I'm not getting lots of
> confused users who are not following instructions and persisting with the
> old <username>.  
> 
> They _should_ be unable to login.  Instead, they login, see no email and
> presume we've lost all of their email in the transition.  This is described
> in issue2869:
> 	https://issues.kolab.org/issue2869
> 
> Can anyone think of a workaround to block people from logging in with the
> local username?  This is really causing us a lot of problems.

Okay, I've found what appears to be a reasonable workaround.  I've modified
/kolab/etc/kolab/templates/saslauthd.conf.template, as follows:

  # Avoid the "Domain/Realm not available" error message
  # ldap_default_realm:  <at>  <at>  <at> postfix-mydomain <at>  <at>  <at> 
  ldap_default_realm: xxx.ie

so that the ldap_default_realm is not set to any of our domains.  The
result of this seems to be what I want, people must use the full username
including domain _or_ they get a failed login.

Is there something that I'm missing here?  Will this have some nasty side
effect that I don't yet see?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alex Potter | 1 Aug 2010 13:45
Picon
Favicon

Re: kolab-server-2.2.4 installation from source, + exit 123 error: Bad exit status (perl)

On Sunday 01 August 2010 06:16:00 jguy wrote:
> I'll happily provide a link to the full install log if requested.

Please do, you've snipped the interesting bits...

Alex
Permalink | Reply | 7 comments |
headers
Gavin McCullagh | 1 Aug 2010 22:25
Picon
Favicon

Re: virtualhosts on kolab

On Sat, 31 Jul 2010, Nicholas Moore wrote:

> I have installed 2.2.4 into opensuse 11.3 using openpkg and following the
> 1st Readme, I then recovered all the backed up mail following the wiki
> backup page. It all worked like a charm - really smooth, congratulations.
> 
> I want to run some web sites on the same server, using apache
> virtualhosts - is that possible?

I have some virtual hosts configured.  I just put files in
	/kolab/etc/apache/apache.d/

and uncommented the inclusion of that directory in:
	/kolab/etc/kolab/templates/httpd.local.template

Apache is well able to run multiple vhosts with the right config.  I'd be
inclined to just configure the existing apache instance, rather than add a
second one.

Gavin
Permalink | Reply | 0 comments |
headers
Alex Potter | 2 Aug 2010 19:29
Picon
Favicon

Re: kolab-server-2.2.4 installation from source, + exit 123 error: Bad exit status (perl)

On Sunday 01 August 2010 12:45:38 Alex Potter wrote:
> On Sunday 01 August 2010 06:16:00 jguy wrote:
> > I'll happily provide a link to the full install log if requested.
> 
> Please do, you've snipped the interesting bits...

Thanks.

You /are/ installing as root?
Is /sys mounted ro?

Alex
Permalink | Reply | 0 comments |
headers
jguy | 2 Aug 2010 20:22
Picon
Gravatar

Re: Re: kolab-server-2.2.4 installation from source, + exit 123 error: Bad exit status (perl)

  On 2:59 PM, Alex Potter wrote:
> On Sunday 01 August 2010 06:16:00 jguy wrote:
>> I'll happily provide a link to the full install log if requested.
> Please do, you've snipped the interesting bits...
>
> Alex
>
>

Here's my install log: 
http://www.jaytechsystems.com/servertmp/kolab-install.log

Thanks,
Jason
Permalink | Reply | 5 comments |
headers
jguy | 2 Aug 2010 23:34
Picon
Gravatar

Re: kolab-server-2.2.4 installation from source, + exit 123 error: Bad exit status (perl)

On Monday 02 August 2010 19:29:59 Alex Potter wrote:
On Sunday 01 August 2010 12:45:38 Alex Potter wrote: > On Sunday 01 August 2010 06:16:00 jguy wrote: > > I'll happily provide a link to the full install log if requested. > > Please do, you've snipped the interesting bits... Thanks. You /are/ installing as root? Is /sys mounted ro? Alex

Yes, installing as root and /sys is read-only.
_______________________________________________
Kolab-users mailing list
Kolab-users <at> kolab.org
https://kolab.org/mailman/listinfo/kolab-users
Permalink | Reply | 4 comments |
headers
Alex Potter | 3 Aug 2010 09:38
Picon
Favicon

Re: kolab-server-2.2.4 installation from source, + exit 123 error: Bad exit status (perl)

On Monday 02 August 2010 22:34:56 jguy wrote:
> You /are/ installing as root?
> Is /sys mounted ro?
> 
> Alex
> 
> 
> 
> 
>  Yes, installing as root and /sys is read-only.

It looks to me like you have a permissions problem. 

As far as I can tell, at least one of the  failures shown in the log was an 
attempt to write to /sys....

Alex
Permalink | Reply | 0 comments |

Gmane