SV: Not currently in TRANSACTION state

[Tomas Andersson]

This is the /etc/hosts file

127.0.0.1       localhost.localdomain   localhost
192.168.90.12   server02.heatex.local   server02
192.168.90.12   mail.heatex.com         mail

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

Shouldn’t this work???


-----Ursprungligt meddelande-----
Från: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org]
För Thomas Arendsen Hein
Skickat: den 28 juli 2009 11:15
Till: kolab-users at kolab.org
Ämne: Re: Not currently in TRANSACTION state

* Tomas Andersson <tomas.andersson at heatex.com> [20090727 16:55]:
> Newly installed Kolab 2.2.2
> 
> User is trying to activate vacation message and gets following message.
> 
> Errors:
> 
> Not currently in TRANSACTION state

The web admin interface tries to connect to the tcp port 2000. For
this it does not use localhost, but the kolabHomeServer of the
corresponding user. Therefore (and for other reasons, too) a Kolab
server always needs to be able to reach itself by its own hostname.

If you use NAT and/or packet filtering this could fail. A quick
solution could be to add the IP of the server to its own /etc/hosts
and make sure that you do not have any iptables rules which block
access to itself.

Regards,
Thomas Arendsen Hein

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key:
0x5816791A
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B
18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

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