Bug 1131327 - Zarafa ical and dagent fail authentication
Summary: Zarafa ical and dagent fail authentication
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gsoap
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mattias Ellert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-19 03:43 UTC by Juan Urroa
Modified: 2015-06-30 01:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 01:07:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Juan Urroa 2014-08-19 03:43:25 UTC
Description of problem:
I updated zarafa and now authentication to imap and ical fails

Version-Release number of selected component (if applicable):
7.1.10-2

How reproducible:
Try to open a calendar or receive messages using thunderbird


Actual results:
Authentication fails

Expected results:
Authentication succeds

Comment 1 Robert Scheck 2014-08-19 07:17:43 UTC
Can you try if replacing "http://localhost:236/zarafa" in /etc/zarafa/*.cfg
by "http://127.0.0.1:236/zarafa" helps? Afterwards the services need to be
restarted.

Comment 2 Juan Urroa 2014-08-20 00:05:22 UTC
It worked

Thanks!!

Comment 3 Robert Scheck 2014-08-24 22:42:11 UTC
Well, it is a bug (but in gSOAP): https://sourceforge.net/p/gsoap2/bugs/959/

Comment 4 Fedora Update System 2014-08-25 11:07:11 UTC
gsoap-2.8.12-6.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/gsoap-2.8.12-6.fc19

Comment 5 Fedora Update System 2014-08-25 11:07:18 UTC
gsoap-2.8.12-6.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/gsoap-2.8.12-6.fc20

Comment 6 Robert Scheck 2014-08-25 23:21:07 UTC
Mattias, I am sorry but the update does not really solve the issue here;
Zarafa still does not work - even with gsoap-2.8.12-6.fc20. Parts from the
strace:

[pid  1931] recvmsg(4, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"\24\0\0\0\3\0\2\0%\304\373S\213\7\0\0\0\0\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 20
[pid  1931] close(4)                    = 0
[pid  1931] socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4
[pid  1931] connect(4, {sa_family=AF_INET, sin_port=htons(236), sin_addr=inet_addr("127.0.0.1")}, 16) = 0
[pid  1931] getsockname(4, {sa_family=AF_INET, sin_port=htons(60280), sin_addr=inet_addr("127.0.0.1")}, [16]) = 0
[pid  1931] close(4)                    = 0
[pid  1931] socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 4
[pid  1931] connect(4, {sa_family=AF_INET6, sin6_port=htons(236), inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0
[pid  1931] getsockname(4, {sa_family=AF_INET6, sin6_port=htons(51180), inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
[pid  1931] close(4)                    = 0
[pid  1931] socket(PF_INET6, SOCK_STREAM, IPPROTO_TCP) = 4
[pid  1931] setsockopt(4, SOL_SOCKET, SO_SNDBUF, [65536], 4) = 0
[pid  1931] setsockopt(4, SOL_SOCKET, SO_RCVBUF, [65536], 4) = 0
[pid  1931] setsockopt(4, SOL_TCP, TCP_NODELAY, [1], 4) = 0
[pid  1931] fcntl(4, F_GETFL)           = 0x2 (flags O_RDWR)
[pid  1931] fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0
[pid  1931] connect(4, {sa_family=AF_INET6, sin6_port=htons(236), inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 EINPROGRESS (Operation now in progress)
[pid  1931] select(5, NULL, [4], NULL, {10, 0}) = 1 (out [4], left {9, 999998})
[pid  1931] getsockopt(4, SOL_SOCKET, SO_ERROR, [111], [4]) = 0
[pid  1931] close(4)                    = 0

It tries IPv4 (would be available) then IPv6 (which is not available) and
ends with EINPROGRESS?

Comment 7 Robert Scheck 2014-08-25 23:27:23 UTC
(In reply to Robert Scheck from comment #6)
> It tries IPv4 (would be available) then IPv6 (which is not available) and
> ends with EINPROGRESS?

The order is triggered by the order of 127.0.0.1 and ::1 in /etc/hosts. But
even switching the order does not make things working.

Comment 8 Fedora Update System 2014-08-27 01:30:15 UTC
Package gsoap-2.8.12-6.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gsoap-2.8.12-6.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-9757/gsoap-2.8.12-6.fc20
then log in and leave karma (feedback).

Comment 9 Mattias Ellert 2014-09-11 15:53:44 UTC
(In reply to Robert Scheck from comment #6)
> Mattias, I am sorry but the update does not really solve the issue here;
> Zarafa still does not work - even with gsoap-2.8.12-6.fc20. Parts from the
> strace:
> 
> It tries IPv4 (would be available) then IPv6 (which is not available) and
> ends with EINPROGRESS?

Can you try gsoap-2.8.12-7.fc20? It has an additional patch intended to address the EINPROGRESS failure.

Comment 10 Robert Scheck 2014-09-21 11:25:14 UTC
(In reply to Mattias Ellert from comment #9)
> Can you try gsoap-2.8.12-7.fc20? It has an additional patch intended to
> address the EINPROGRESS failure.

No, this unfortunately still doesn't work. Here is strace output from a test
system:

[pid  1951] open("/etc/hosts", O_RDONLY|O_CLOEXEC) = 4
[pid  1951] fstat(4, {st_mode=S_IFREG|0644, st_size=113, ...}) = 0
[pid  1951] mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f4144dca000
[pid  1951] read(4, "::1\tlocalhost\n127.0.0.1\t\tlocalhost.localdomain localhost\n#::1\t\tlocalhost6.localdomain6 localhost6\n#::1\tlocalhost\n", 4096) = 113
[pid  1951] read(4, "", 4096)           = 0
[pid  1951] close(4)                    = 0
[pid  1951] munmap(0x7f4144dca000, 4096) = 0
[pid  1951] socket(PF_NETLINK, SOCK_RAW, 0) = 4
[pid  1951] bind(4, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
[pid  1951] getsockname(4, {sa_family=AF_NETLINK, pid=1951, groups=00000000}, [12]) = 0
[pid  1951] sendto(4, "\24\0\0\0\26\0\1\3\354\264\36T\0\0\0\0\0\0\0\0", 20, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20
[pid  1951] recvmsg(4, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"D\0\0\0\24\0\2\0\354\264\36T\237\7\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1\10\0\2\0\177\0\0\1\7\0\3\0lo\0\0\24\0\6\0\377\377\377\377\377\377\377\377'\0\0\0'\0\0\0P\0\0\0\24\0\2\0\354\264\36T\237\7\0\0\2\30\0\0\2\0\0\0\10\0\1\0\300\250z\t\10\0\2\0\300\250z\t\10\0\4\0\300\250z\377\t\0\3\0eth0\0\0\0\0\24\0\6\0I\v\0\0I\v\0\0w\2\0\0w\2\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 148
[pid  1951] recvmsg(4, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"@\0\0\0\24\0\2\0\354\264\36T\237\7\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\24\0\6\0\377\377\377\377\377\377\377\377'\0\0\0'\0\0\0@\0\0\0\24\0\2\0\354\264\36T\237\7\0\0\n@\200\375\2\0\0\0\24\0\1\0\376\200\0\0\0\0\0\0PT\0\377\376\220\372\333\24\0\6\0\377\377\377\377\377\377\377\377\300\1\0\0\300\1\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 128
[pid  1951] recvmsg(4, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"\24\0\0\0\3\0\2\0\354\264\36T\237\7\0\0\0\0\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 20
[pid  1951] close(4)                    = 0
[pid  1951] socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 4
[pid  1951] connect(4, {sa_family=AF_INET6, sin6_port=htons(236), inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0
[pid  1951] getsockname(4, {sa_family=AF_INET6, sin6_port=htons(39943), inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
[pid  1951] connect(4, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
[pid  1951] connect(4, {sa_family=AF_INET, sin_port=htons(236), sin_addr=inet_addr("127.0.0.1")}, 16) = 0
[pid  1951] getsockname(4, {sa_family=AF_INET6, sin6_port=htons(34147), inet_pton(AF_INET6, "::ffff:127.0.0.1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
[pid  1951] close(4)                    = 0
[pid  1951] socket(PF_INET6, SOCK_STREAM, IPPROTO_TCP) = 4
[pid  1951] setsockopt(4, SOL_SOCKET, SO_SNDBUF, [65536], 4) = 0
[pid  1951] setsockopt(4, SOL_SOCKET, SO_RCVBUF, [65536], 4) = 0
[pid  1951] setsockopt(4, SOL_TCP, TCP_NODELAY, [1], 4) = 0
[pid  1951] fcntl(4, F_GETFL)           = 0x2 (flags O_RDWR)
[pid  1951] fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0
[pid  1951] connect(4, {sa_family=AF_INET6, sin6_port=htons(236), inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 EINPROGRESS (Operation now in progress)
[pid  1951] select(5, NULL, [4], NULL, {10, 0}) = 1 (out [4], left {9, 999998})
[pid  1951] getsockopt(4, SOL_SOCKET, SO_ERROR, [111], [4]) = 0
[pid  1951] close(4)                    = 0
[pid  1951] socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 4
[pid  1951] setsockopt(4, SOL_SOCKET, SO_SNDBUF, [65536], 4) = 0
[pid  1951] setsockopt(4, SOL_SOCKET, SO_RCVBUF, [65536], 4) = 0
[pid  1951] setsockopt(4, SOL_TCP, TCP_NODELAY, [1], 4) = 0
[pid  1951] fcntl(4, F_GETFL)           = 0x2 (flags O_RDWR)
[pid  1951] fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0
[pid  1951] connect(4, {sa_family=AF_INET, sin_port=htons(236), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 EINPROGRESS (Operation now in progress)
[pid  1951] select(5, NULL, [4], NULL, {10, 0}) = 1 (out [4], left {9, 999998})
[pid  1951] getsockopt(4, SOL_SOCKET, SO_ERROR, [0], [4]) = 0
[pid  1951] fcntl(4, F_GETFL)           = 0x802 (flags O_RDWR|O_NONBLOCK)
[pid  1951] fcntl(4, F_SETFL, O_RDWR)   = 0
[pid  1951] shutdown(4, SHUT_RDWR)      = 0
[pid  1951] close(4)                    = 0
[pid  1951] write(7, "\3[ 1951] Failed to login from 127.0.0.1 with invalid username \"tux\" or wrong password. Error: 0x80040115\0", 105) = 105
[pid  1951] write(7, "\6[ 1951] > a0001 NO LOGIN wrong username or password\0", 53) = 53
[pid  1951] sendto(0, "a0001 NO LOGIN wrong username or password\r\n", 43, 0, NULL, 0) = 43
[pid  1951] write(7, "\2[ 1951] Connection error.\0", 27) = 27
[pid  1951] write(7, "\4[ 1951] Client 127.0.0.1 thread exiting\0", 41) = 41
[pid  1951] close(0)                    = 0
[pid  1951] close(7)                    = 0
[pid  1951] close(3)                    = 0
[pid  1951] exit_group(0)               = ?

Comment 11 Fedora End Of Life 2015-01-09 22:41:06 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 12 Fedora End Of Life 2015-02-18 11:19:46 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 13 Robert Scheck 2015-03-03 23:40:43 UTC
IMHO the issue still exists on Fedora 20, reopening.

Comment 14 Fedora End Of Life 2015-05-29 12:40:19 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Fedora End Of Life 2015-06-30 01:07:32 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.