install failed

I downloaded from belnet ftp (primarily because I know how
to download 
multiple files from ftp easily).  More precisely, the
version I selected 
was  located at 
ftp://ftp.belnet.be/packages/kolab/server/release/kolab-serv
er-2.1.0/ix86-debian3.1/

I'm installing on Ubuntu Feisty Fawn.  When I attempted to
install, I 
received the following log:

---- boot/build exchange %kolab ----

obmtool:NOTICE: did not find openpkg/rpm executable.
Checking/fetching binary sh.
OpenPKG 2.5-RELEASE Binary Bootstrap Package, version 2.5.4
Built for prefix /kolab on target platform ix86-debian3.1
++ hooking OpenPKG instance into system environment
++ fixating OpenPKG instance root directory
"/kolab"
++ extracting OpenPKG binary distribution
++ installing OpenPKG binary distribution
/kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh:
1000: ./openpkg.bzip2: not found
++ fixating OpenPKG instance filesystem hierarchy
/kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh:
1012: /kolab/bin/openpkg: not found
++ post-processing OpenPKG bootstrap installation
/kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh:
1048: /kolab/lib/openpkg/rpmdb: not found
cat: /kolab/etc/openpkg/platform: No such file or directory
/kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh:
1138: /kolab/lib/openpkg/rpmtool: not found
obmtool:ERROR: bootstrapping failed


What am I missing?
--Paul

-- 
Paul Douglas Franklin
Computer Manager, Union Gospel Mission of Yakima,
Washington
Husband of Danette
Father of 12

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

I'd guess that not all files downloaded. I downloaded the
same set of 
packages (ix86-debian3.1) from the same site via ftp (cli)
for a debian 
etch install and thus far all seems to be working
perfectly.

Cheers,

Alex C.

Paul Douglas Franklin wrote:
> I downloaded from belnet ftp (primarily because I know
how to download 
> multiple files from ftp easily).  More precisely, the
version I selected 
> was  located at 
>
ftp://ftp.belnet.be/packages/kolab/server/release/kolab-serv
er-2.1.0/ix86-debian3.1/
> 
> I'm installing on Ubuntu Feisty Fawn.  When I attempted
to install, I 
> received the following log:
> 
> ---- boot/build exchange %kolab ----
> 
> obmtool:NOTICE: did not find openpkg/rpm executable.
Checking/fetching binary sh.
> OpenPKG 2.5-RELEASE Binary Bootstrap Package, version
2.5.4
> Built for prefix /kolab on target platform
ix86-debian3.1
> ++ hooking OpenPKG instance into system environment
> ++ fixating OpenPKG instance root directory
"/kolab"
> ++ extracting OpenPKG binary distribution
> ++ installing OpenPKG binary distribution
>
/kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh:
1000: ./openpkg.bzip2: not found
> ++ fixating OpenPKG instance filesystem hierarchy
>
/kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh:
1012: /kolab/bin/openpkg: not found
> ++ post-processing OpenPKG bootstrap installation
>
/kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh:
1048: /kolab/lib/openpkg/rpmdb: not found
> cat: /kolab/etc/openpkg/platform: No such file or
directory
>
/kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh:
1138: /kolab/lib/openpkg/rpmtool: not found
> obmtool:ERROR: bootstrapping failed
> 
> 
> What am I missing?
> --Paul
> 

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

I have discovered the following:
1)  Ubuntu 7.04 64-bit version does not want to install
Kolab, but the 
I386 version will.
2)  LAMP and Kolab do not co-exist well on that Ubuntu
server for 
someone like me who has little knowledge.  They might for
someone who 
really knows what he's doing.
3)  apt-get remove apache2 did not remove apache2 even
though it said it 
did.
I'm now re-installing Ubuntu (finished that, actually) and
Kolab (it's 
working merrily away).  I expect this to go just fine from
here on out.
--Paul


-- 
Paul Douglas Franklin
Computer Manager, Union Gospel Mission of Yakima,
Washington
Husband of Danette
Father of 12

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

greetings,

1 - upgrading from 2.04 to 2.1
2 - after upgrade manager shows up as mantainer (not sure if
it should be 
something else)
3 - "services" link doesn't show up, therefore I
can't do any further 
configuration!
4 - checked LDAP db but couldn't find any reason.

any hints?

TIA,

JK

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

On Sunday 10 June 2007 23:04, J.C. França wrote:
> 1 - upgrading from 2.04 to 2.1
> 2 - after upgrade manager shows up as mantainer (not
sure if it should be
> something else)

It should stay "manager".
But not that you should work not as manager but as an admin
account.

> 3 - "services" link doesn't show up,
therefore I can't do any further
> configuration!

This would be to be expected if you only have mantainer
rights.

> 4 - checked LDAP db but couldn't find any reason.
>
> any hints?

Try to use the manager bind dn and password from
/kolab/etc/kolab/kolab.conf try to be manager again.


-- 
Managing Director - Owner: www.intevation.net       (Free
Software Company)
Germany Coordinator: fsfeurope.org. Coordinator:
www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB
18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr.
Jan-Oliver Wagner

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

On Friday 08 June 2007 04:14, Paul Douglas Franklin wrote:
> I have discovered the following:
> 1)  Ubuntu 7.04 64-bit version does not want to install
Kolab, but the
> I386 version will.

Kolab Server 2.1.0 still has some known issues with 64bit
machines,
using the 32bit version is the recommended workaround.

Note that the binaries are really for convenience Debian
Etch users,
you would want to start from source for other
distributions.

Bernhard

-- 
Managing Director - Owner: www.intevation.net       (Free
Software Company)
Germany Coordinator: fsfeurope.org. Coordinator:
www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB
18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr.
Jan-Oliver Wagner

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

On Monday 11 June 2007 09:50:15 Bernhard Reiter wrote:

> On Sunday 10 June 2007 23:04, J.C. França wrote:
> > 1 - upgrading from 2.04 to 2.1
> > 2 - after upgrade manager shows up as mantainer
(not sure if it should be
> > something else)
> It should stay "manager".
> But not that you should work not as manager but as an
admin account.
The odd thing is, at the beginning of the seup yesterday,
right after install, 
it showed an user "mana n/a" as mantainer

> > 3 - "services" link doesn't show up,
therefore I can't do any further
> > configuration!
> This would be to be expected if you only have mantainer
rights.
> > 4 - checked LDAP db but couldn't find any reason.
> > any hints?
> Try to use the manager bind dn and password from
> /kolab/etc/kolab/kolab.conf try to be manager again.
I tried. Everything seems to be fine with kolab.conf (is it
supposed to have 
both bind_pw and bind_pw_hash variables?).
Maybe something was missed when using the python script to
convert the LDAP db 
to 2.1. Shall I try to rebuilt the LDAP db? How would you
suggest doing this?

TIA,
JK

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

On Monday 11 June 2007 09:50:15 Bernhard Reiter wrote:

> On Sunday 10 June 2007 23:04, J.C. França wrote:
> > 1 - upgrading from 2.04 to 2.1
> > 2 - after upgrade manager shows up as mantainer
(not sure if it should be
> > something else)
> It should stay "manager".
> But not that you should work not as manager but as an
admin account.
The odd thing is, at the beginning of the seup yesterday,
right after install, 
it showed an user "mana n/a" as mantainer

> > 3 - "services" link doesn't show up,
therefore I can't do any further
> > configuration!
> This would be to be expected if you only have mantainer
rights.
> > 4 - checked LDAP db but couldn't find any reason.
> > any hints?
> Try to use the manager bind dn and password from
> /kolab/etc/kolab/kolab.conf try to be manager again.
I tried. Everything seems to be fine with kolab.conf (is it
supposed to have 
both bind_pw and bind_pw_hash variables?).
Maybe something was missed when using the python script to
convert the LDAP db 
to 2.1. Shall I try to rebuilt the LDAP db? How would you
suggest doing this?

TIA,
JK

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

<snip>
> > > 1 - upgrading from 2.04 to 2.1
> > > 2 - after upgrade manager shows up as
mantainer (not sure if it should
> > > be something else)
> >
> > > 4 - checked LDAP db but couldn't find any
reason.
> >

The group "admin" was missing in the LDAP tree.
Instead, there was an "admin" 
user. Fixed that and it worked.

Now there are 2 more questions:
1 - is the name mail=kolabxxx correct for a
distribution list? why is that?
2 - email with "From" different from the kolab
domain is returning:
------------------------------
<xxxx>: service unavailable. Command output: Invalid
From:
    header. "my name" <senderdifferent_domain> looks like a forged sender
------------------------------
I'm totally lost on this one due to my ignorance on mail
issues.

Any hints?

TIA,
JK

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users