Dear Louis ,

 

Many thanks for your help .

please  Can you send me step by step installation and configuration I will
flow it with you ..

am using centos 6 and I have 389 directory server installed in another
machine its ip 192.168.1.109 and dns install their too ,, ready to configure
with sogo ,

 

here is the log .. 

[root@mailserver1 ~]# cat /var/log/sogo/sogo.log

Aug 04 07:17:57 sogod [1672]: version 2.0.7 (build root@shiva.inverse
201307220922) -- starting

Aug 04 07:17:57 sogod [1672]: vmem size check enabled: shutting down app
when vmem > 384 MB

Aug 04 07:17:57 sogod [1672]: <0x0x29bf89c[SOGoProductLoader]> SOGo products
loaded from '/usr/lib/GNUstep/SOGo':

Aug 04 07:17:57 sogod [1672]: <0x0x29bf89c[SOGoProductLoader]>
SchedulerUI.SOGo, MainUI.SOGo, Appointments.SOGo, ContactsUI.SOGo,
Mailer.SOGo, PreferencesUI.SOGo, CommonUI.SOGo, Contacts.SOGo,
AdministrationUI.SOGo, MailPartViewers.SOGo, MailerUI.SOGo

Aug 04 07:18:03 sogod [1672]: <0x0x2ac2614[WOWatchDog]> listening on *:20000

Aug 04 07:18:03 sogod [1672]: <0x0x2ac2614[WOWatchDog]> watchdog process
pid: 1672

Aug 04 07:18:03 sogod [1672]: <0x0x479940[WOWatchDogChild]> watchdog request
timeout set to 10 minutes

Aug 04 07:18:03 sogod [1672]: <0x0x2ac2614[WOWatchDog]> preparing 3 children

Aug 04 07:18:03 sogod [1672]: <0x0x2ac2614[WOWatchDog]> child spawned with
pid 1748

Aug 04 07:18:03 sogod [1672]: <0x0x2ac2614[WOWatchDog]> child spawned with
pid 1749

Aug 04 07:18:03 sogod [1672]: <0x0x2ac2614[WOWatchDog]> child spawned with
pid 1751

2013-08-04 07:18:03.992 sogod[1749] could not open channel to sogo@localhost

Aug 04 07:18:03 sogod [1749]: [ERROR] <0x0x29ed084[GCSChannelManager]> could
not open channel <0x0x2a51b4c[PostgreSQL72Channel]: not-connected> for URL:
postgresql://sogo:sogo@localhost:5432/sogo/sogo_user_profile

Aug 04 07:18:03 sogod [1749]: [WARN] <0x0x29ed084[GCSChannelManager]>   will
prevent opening of this channel 5 seconds after 2013-08-04 07:18:03 -0700

2013-08-04 07:18:03.999 sogod[1748] could not open channel to sogo@localhost

Aug 04 07:18:03 sogod [1748]: [ERROR] <0x0x29ed084[GCSChannelManager]> could
not open channel <0x0x2a51b4c[PostgreSQL72Channel]: not-connected> for URL:
postgresql://sogo:sogo@localhost:5432/sogo/sogo_user_profile

Aug 04 07:18:03 sogod [1748]: [WARN] <0x0x29ed084[GCSChannelManager]>   will
prevent opening of this channel 5 seconds after 2013-08-04 07:18:03 -0700

2013-08-04 07:18:04.006 sogod[1751] could not open channel to sogo@localhost

Aug 04 07:18:04 sogod [1751]: [ERROR] <0x0x29ed084[GCSChannelManager]> could
not open channel <0x0x2a51b4c[PostgreSQL72Channel]: not-connected> for URL:
postgresql://sogo:sogo@localhost:5432/sogo/sogo_user_profile

Aug 04 07:18:04 sogod [1751]: [WARN] <0x0x29ed084[GCSChannelManager]>   will
prevent opening of this channel 5 seconds after 2013-08-04 07:18:03 -0700

Aug 04 07:24:47 sogod [1672]: <0x0x2ac2614[WOWatchDog]> Terminating with
SIGINT or SIGTERM

Aug 04 07:24:47 sogod [1672]: <0x0x2ad2514[WOWatchDogChild]> sending
terminate signal to pid 1751

Aug 04 07:24:47 sogod [1672]: <0x0x2ac9b24[WOWatchDogChild]> sending
terminate signal to pid 1749

Aug 04 07:24:47 sogod [1672]: <0x0x2a68d74[WOWatchDogChild]> sending
terminate signal to pid 1748

Aug 04 07:24:47 sogod [1672]: <0x0x2ac2614[WOWatchDog]> Terminating with
SIGINT or SIGTERM

Aug 04 07:24:47 sogod [1672]: <0x0x2ac2614[WOWatchDog]> Terminating with
SIGINT or SIGTERM

Aug 04 07:24:47 sogod [1672]: <0x0x2ac2614[WOWatchDog]> Terminating with
SIGINT or SIGTERM

Aug 04 07:24:47 sogod [1672]: <0x0x2ac9b24[WOWatchDogChild]> child 1749
exited

Aug 04 07:24:47 sogod [1672]: <0x0x2ad2514[WOWatchDogChild]> child 1751
exited

Aug 04 07:24:47 sogod [1672]: <0x0x2ac2614[WOWatchDog]> Terminating with
SIGINT or SIGTERM

Aug 04 07:24:47 sogod [1672]: <0x0x2a68d74[WOWatchDogChild]> child 1748
exited

Aug 04 07:24:47 sogod [1672]: <0x0x2ac2614[WOWatchDog]> all children exited.
We now terminate.

From: Louis-Philippe Gauthier [mailto:lpgauth...@gmail.com] 
Sent: Monday, August 05, 2013 4:33 PM
To: users
Subject: Re: [SOGo] help ...

 

Dear Husam 

and... You access SOGO via :20000 in the URL. Normally, you must access via
http(:80) or https (:443)... 

 

2013/8/5 Szládovics Péter <p...@szladovics.hu>

2013-08-04 02:06 keltezéssel, husam.shabeeb írta:

Dear Friend ,

I have send many emails here trying to get help now one answer me ..

am trying to configure sogo with 389 directory ..

And login user ,

 

 

Dear Husam,

Your SOGo.conf for apache is not correct, and the CSS is unavailable for
this reason.




-- 
Louis-Philippe Gauthier

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Reply via email to