On Monday, June 2, 2014 11:55 CEST, "Martijn Rijkeboer" <[email protected]> wrote: > Hi, > > I'm trying to use SOGo on OpenBSD 5.5 AMD64 but it is not working. When I > try to connect I get a timeout and the log file contains many lines with > the following errors: > > Loading two versions of SOGoEMailAlarmsManager. The class that will be > used is undefined > > Loading two versions of SOGoAppointmentOccurence. The class that will be > used is undefined > > Loading two versions of SOGoComponentOccurence. The class that will be > used is undefined > > Loading two versions of SOGoAppointmentObject. The class that will be > used is undefined > > Loading two versions of SOGoCalendarComponent. The class that will be > used is undefined > > Loading two versions of SOGoCalendarMailBodyPart. The class that will be > used is undefined > > Loading two versions of SOGoHTMLMailBodyPart. The class that will be used > is undefined > > Loading two versions of SOGoMailBodyPart. The class that will be used is > undefined > > Loading two versions of SOGoTrashFolder. The class that will be used is > undefined > > Loading two versions of SOGoDraftsFolder. The class that will be used is > undefined > > Loading two versions of SOGoSentFolder. The class that will be used is > undefined > > Loading two versions of SOGoMailObject. The class that will be used is > undefined > > Loading two versions of SOGoMailNamespace. The class that will be used is > undefined > > Loading two versions of SOGoMailFolder. The class that will be used is > undefined > > Loading two versions of SOGoSpecialMailFolder. The class that will be > used is undefined > > Loading two versions of SOGoMailAccount. The class that will be used is > undefined > > Loading two versions of SOGoMailAccounts. The class that will be used is > undefined > > Loading two versions of SOGoMailBaseObject. The class that will be used > is undefined > > Loading two versions of SOGoDraftObject. The class that will be used is > undefined
above classes are linked twice, that's normal. > > Calling [libxmlSAXLocator -lineNumber] with incorrect signature. Method > has i16@0:8, selector has q16@0:8 > > Calling [NGDOMElement -setLine:] with incorrect signature. Method has > v24@0:8q16, selector has v20@0:8i16 > > Calling [GSMutableArray -length] with incorrect signature. Method has > I16@0:8, selector has Q16@0:8 those should also not really matter. Is there more warnings/errors you get in sogo logs? Maybe you can start it manually: su - _sogo /usr/local/sbin/sogod -WOUseWatchDog NO -WOLogFile - -WONoDetach YES that should start sogod in foreground, when its loaded, it should write something as: listening on port: XXXXX Whatever port you configured sogo to listen on. Then, when you point your browser on it, what do you get then in the console. > > > The system has the following software: > - OS: OpenBSD 5.5 AMD64 GENERIC.MP > - SOGO: sogo-2.1.1.1p0 > - SOPE: sope-2.1.1.1 & sope-mysql-2.1.1.1 > - GNUSTEP: gnustep-base-1.24.6 & gnustep-libobjc2-1.7p0 & gnustep-make-2.6.6 I hope it's not because of sope-mysql, I've never tried it, since I run a postgresql in the background. Sebastian > > Any suggestions on how to fix this? > > Kind regards, > > > Martijn Rijkeboer > >
