Error: 'Server' object has no attribute 'protocol'
Hi everyone, I finally managed to upgrade debian to debian 7 I have now successfully installed the calendarserver 3.2. Now sometimes when I try to log in (currently for testing trough the web interface), nothing happens. The Server will ask again for the name and password. The Log entries: [PooledMemCacheProtocol,client] [twext.web2.server#error] [Failure instance: Traceback: <type 'exceptions.AttributeError'>: 'Server' object has no attribute 'protocol' [PooledMemCacheProtocol,client] [twext.web2.server#info] Exception rendering error page: [PooledMemCacheProtocol,client] [twext.web2.server#error] [Failure instance: Traceback: <type 'exceptions.ValueError'>: registering producer <twext.web2.stream.StreamProducer object at 0x3eaed10> before previous one (<twext.web2.stream.StreamProducer object at 0x3eae890>) was unregistered [PooledMemCacheProtocol,client] [twext.web2.server#info] Original exception: [PooledMemCacheProtocol,client] [twext.web2.server#error] [Failure instance: Traceback: <type 'exceptions.AttributeError'>: 'Server' object has no attribute 'protocol' [PooledMemCacheProtocol,client] Unhandled error in Deferred: [PooledMemCacheProtocol,client] Unhandled Error exceptions.ValueError: registering producer <twext.web2.stream.StreamProducer object at 0x3dffe10> before previous one (<twext.web2.stream.StreamProducer object at 0x3eae890>) was unregistered I didn't copied the tracebacks if youre intrested in them let me know. Thank you in advance Uli
So I figured out that testing trough the webbrowser was a bad idea. Because the error disappeared when I tested it with the Calendar App on my mac. Now I'm testing with the App. The Calendar App gives me an error message: "Authentication failed. Your username and password were rejected by the server." CalendarServer logs: "Could not locate URI: URINotFoundException: Could not find URI '{DAV:}unauthenticated'" Could it be a storage problem, I want to store the calendar on the filesystem not in a postgresql? Uli On 11.09.14 13:07, Ulrich Fourier wrote:
Hi everyone,
I finally managed to upgrade debian to debian 7 I have now successfully installed the calendarserver 3.2. Now sometimes when I try to log in (currently for testing trough the web interface), nothing happens. The Server will ask again for the name and password.
The Log entries:
[PooledMemCacheProtocol,client] [twext.web2.server#error] [Failure instance: Traceback: <type 'exceptions.AttributeError'>: 'Server' object has no attribute 'protocol' [PooledMemCacheProtocol,client] [twext.web2.server#info] Exception rendering error page: [PooledMemCacheProtocol,client] [twext.web2.server#error] [Failure instance: Traceback: <type 'exceptions.ValueError'>: registering producer <twext.web2.stream.StreamProducer object at 0x3eaed10> before previous one (<twext.web2.stream.StreamProducer object at 0x3eae890>) was unregistered [PooledMemCacheProtocol,client] [twext.web2.server#info] Original exception: [PooledMemCacheProtocol,client] [twext.web2.server#error] [Failure instance: Traceback: <type 'exceptions.AttributeError'>: 'Server' object has no attribute 'protocol' [PooledMemCacheProtocol,client] Unhandled error in Deferred: [PooledMemCacheProtocol,client] Unhandled Error exceptions.ValueError: registering producer <twext.web2.stream.StreamProducer object at 0x3dffe10> before previous one (<twext.web2.stream.StreamProducer object at 0x3eae890>) was unregistered
I didn't copied the tracebacks if youre intrested in them let me know.
Thank you in advance Uli
Hi Ulrich, --On September 11, 2014 at 3:15:04 PM +0200 Ulrich Fourier <ulrich.fourier@rockyourlife.de> wrote:
Could it be a storage problem, I want to store the calendar on the filesystem not in a postgresql?
Don't do that. The file store is now only supported as a means of migrating from legacy file store to the SQL store. All the new functionality we build is going into the SQL store. As a result the file store may well be broken for operations other than the migration step we use it for. That said the problem you are seeing may not be related to that. A browser should definitely work - in fact that is probably the first and easiest thing to try. The errors you saw with the browser suggestion some problem with perhaps using SSL when that isn't enabled. So I suggest you check that again. If you have no luck, turn the server off, clear out the error log file, then turn it on again and try again with the browser. Send the log file and we can look at the whole startup process and maybe spot the issue. -- Cyrus Daboo
On 11.09.14 15:22, Cyrus Daboo wrote:
Hi Ulrich,
--On September 11, 2014 at 3:15:04 PM +0200 Ulrich Fourier <ulrich.fourier@rockyourlife.de> wrote:
Could it be a storage problem, I want to store the calendar on the filesystem not in a postgresql?
Don't do that. The file store is now only supported as a means of migrating from legacy file store to the SQL store. All the new functionality we build is going into the SQL store. As a result the file store may well be broken for operations other than the migration step we use it for.
That said the problem you are seeing may not be related to that. A browser should definitely work - in fact that is probably the first and easiest thing to try. The errors you saw with the browser suggestion some problem with perhaps using SSL when that isn't enabled. So I suggest you check that again. If you have no luck, turn the server off, clear out the error log file, then turn it on again and try again with the browser. Send the log file and we can look at the whole startup process and maybe spot the issue.
Hi Cyrus, thank you, in that case I will setup a database. I attached both log files, I hope that they are helpful. Uli
Hi Ulrich, --On September 11, 2014 at 4:29:56 PM +0200 Ulrich Fourier <ulrich.fourier@rockyourlife.de> wrote:
thank you, in that case I will setup a database. I attached both log files, I hope that they are helpful.
OK, so a couple of things to look at from the error log: 1) 2014-09-11 16:13:33+0200 [-] [memcached-Default] can't run as root without the -u switch Looks like you are trying to run the server as root. That will prevent memcache from running. I would advise you to run as a normal user - or better create a user dedicated to running this server (that is what we do on OS X where we have a system "calendar" user for that purpose). 2) These LDAP errors: 2014-09-11 16:13:56+0200 [-] [caldav-0] [PooledMemCacheProtocol,client] [twistedcaldav.directory.ldapdirectory.LdapDirectoryService#debug] Faulting record for attribute 'shortname' with value 'UlrichFourier' 2014-09-11 16:13:56+0200 [-] [caldav-0] [PooledMemCacheProtocol,client] [twistedcaldav.directory.ldapdirectory.LdapDirectoryService#debug] LDAP query for types ['users'], indexType shortname and indexKey UlrichFourier 2014-09-11 16:13:56+0200 [-] [caldav-0] [PooledMemCacheProtocol,client] [twistedcaldav.directory.ldapdirectory.LdapDirectoryService#debug] Retrieving ldap record with base ou=people,dc=rockyourlife,dc=de and filter (&(&(!(objectClass=organizationalUnit))(objectClass=inetOrgPerson))(dn=UlrichFourier)). Those suggest that there is a problem looking up the LDAP record for "dn=UlrichFourier". Can you check your LDAP service to see what record you are supposed to be using? -- Cyrus Daboo
On 11.09.14 16:39, Cyrus Daboo wrote:
Hi Ulrich,
--On September 11, 2014 at 4:29:56 PM +0200 Ulrich Fourier <ulrich.fourier@rockyourlife.de> wrote:
thank you, in that case I will setup a database. I attached both log files, I hope that they are helpful.
OK, so a couple of things to look at from the error log:
1) 2014-09-11 16:13:33+0200 [-] [memcached-Default] can't run as root without the -u switch
Looks like you are trying to run the server as root. That will prevent memcache from running. I would advise you to run as a normal user - or better create a user dedicated to running this server (that is what we do on OS X where we have a system "calendar" user for that purpose).
2) These LDAP errors:
2014-09-11 16:13:56+0200 [-] [caldav-0] [PooledMemCacheProtocol,client] [twistedcaldav.directory.ldapdirectory.LdapDirectoryService#debug] Faulting record for attribute 'shortname' with value 'UlrichFourier' 2014-09-11 16:13:56+0200 [-] [caldav-0] [PooledMemCacheProtocol,client] [twistedcaldav.directory.ldapdirectory.LdapDirectoryService#debug] LDAP query for types ['users'], indexType shortname and indexKey UlrichFourier 2014-09-11 16:13:56+0200 [-] [caldav-0] [PooledMemCacheProtocol,client] [twistedcaldav.directory.ldapdirectory.LdapDirectoryService#debug] Retrieving ldap record with base ou=people,dc=rockyourlife,dc=de and filter (&(&(!(objectClass=organizationalUnit))(objectClass=inetOrgPerson))(dn=UlrichFourier)).
Those suggest that there is a problem looking up the LDAP record for "dn=UlrichFourier". Can you check your LDAP service to see what record you are supposed to be using?
Alright I guess I tried something there but forgot to change it back. I've fixed now both things. It still doesn't work, see my attached logs.
Hi Ulrich, --On September 11, 2014 at 5:03:32 PM +0200 Ulrich Fourier <ulrich.fourier@rockyourlife.de> wrote:
Alright I guess I tried something there but forgot to change it back. I've fixed now both things. It still doesn't work, see my attached logs.
Turn off digest authentication and use basic instead. The LDAP directory service only supports basic. -- Cyrus Daboo
On Sep 11, 2014, at 8:21 AM, Cyrus Daboo <cdaboo@apple.com> wrote:
Turn off digest authentication and use basic instead. The LDAP directory service only supports basic.
By default, basic auth is only allowed when using SSL, so make sure SSL is happy. Obviously you want SSL in this case :) It's possible to override this policy, but it's not a good idea. -dre
On 11.09.14 18:08, Andre LaBranche wrote:
On Sep 11, 2014, at 8:21 AM, Cyrus Daboo <cdaboo@apple.com> wrote:
Turn off digest authentication and use basic instead. The LDAP directory service only supports basic. By default, basic auth is only allowed when using SSL, so make sure SSL is happy. Obviously you want SSL in this case :) It's possible to override this policy, but it's not a good idea.
-dre Thank you guys, now everything is working fine except the calendarsharing. I cannot select the user with who I want to share my calendar with in the logs there is an exception although he logs that he finds users. See log files attached. Is it a LDAP misconfiguration I made?
participants (3)
-
Andre LaBranche
-
Cyrus Daboo
-
Ulrich Fourier