[SOGo] yum install sogo + pel give these errors any help .?
[root@mailserver ~]# sudo rpm -Uhv http://mirror.bytemark.co.uk/fedora/epel/6/i386/epel-release-6-8.noarch.rpm Retrieving http://mirror.bytemark.co.uk/fedora/epel/6/i386/epel-release-6-8.noarch.rpm warning: /var/tmp/rpm-tmp.4vcL8l: Header V3 RSA/SHA256 Signature, key ID 0608b895: NOKEY Preparing...### [100%] 1:epel-release ### [100%] [root@mailserver ~]# yum update Loaded plugins: fastestmirror, security Loading mirror speeds from cached hostfile * base: ftp.itu.edu.tr * epel: kartolo.sby.datautama.net.id * extras: ftp.itu.edu.tr * updates: ftp.itu.edu.tr Setting up Update Process Resolving Dependencies -- Running transaction check --- Package iotop.noarch 0:0.3.2-3.el6 will be updated --- Package iotop.noarch 0:0.4.1-2.el5 will be an update -- Processing Dependency: python(abi) = 2.4 for package: iotop-0.4.1-2.el5.noarch --- Package perl-parent.i686 1:0.221-131.el6_4 will be updated --- Package perl-parent.noarch 1:0.225-6.el5 will be an update -- Processing Dependency: perl(:MODULE_COMPAT_5.8.8) for package: 1:perl-parent-0.225-6.el5.noarch --- Package python-paramiko.noarch 0:1.7.5-2.1.el6 will be updated --- Package python-paramiko.noarch 0:1.7.6-1.el5 will be an update -- Processing Dependency: python(abi) = 2.4 for package: python-paramiko-1.7.6-1.el5.noarch -- Finished Dependency Resolution Error: Package: python-paramiko-1.7.6-1.el5.noarch (epel) Requires: python(abi) = 2.4 Installed: python-2.6.6-37.el6_4.i686 (@updates) python(abi) = 2.6 Available: python-2.6.6-36.el6.i686 (base) python(abi) = 2.6 Available: python26-2.6.8-2.el5.i386 (epel) python(abi) = 2.6 Error: Package: 1:perl-parent-0.225-6.el5.noarch (epel) Requires: perl(:MODULE_COMPAT_5.8.8) Error: Package: iotop-0.4.1-2.el5.noarch (epel) Requires: python(abi) = 2.4 Installed: python-2.6.6-37.el6_4.i686 (@updates) python(abi) = 2.6 Available: python-2.6.6-36.el6.i686 (base) python(abi) = 2.6 Available: python26-2.6.8-2.el5.i386 (epel) python(abi) = 2.6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@mailserver ~]# rpm -e epel-release-6-8.noarch [root@mailserver ~]# sudo rpm -Uhv http://mirror.bytemark.co.uk/fedora/epel/6/i386/epel-release-6-8.noarch.rpm Retrieving http://mirror.bytemark.co.uk/fedora/epel/6/i386/epel-release-6-8.noarch.rpm warning: /var/tmp/rpm-tmp.ewaSij: Header V3 RSA/SHA256 Signature, key ID 0608b895: NOKEY Preparing...### [100%] 1:epel-release ### [100%] [root@mailserver ~]# [root@mailserver ~]# yum update Loaded plugins: fastestmirror, security Loading mirror speeds from cached hostfile * base: ftp.itu.edu.tr * epel: ftp.jaist.ac.jp * extras: ftp.itu.edu.tr * updates: ftp.itu.edu.tr Setting up Update Process Resolving Dependencies -- Running transaction check --- Package iotop.noarch 0:0.3.2-3.el6 will be updated --- Package iotop.noarch 0:0.4.1-2.el5 will be an update -- Processing Dependency: python(abi) = 2.4 for package: iotop-0.4.1-2.el5.noarch --- Package perl-parent.i686 1:0.221-131.el6_4 will be updated --- Package perl-parent.noarch 1:0.225-6.el5 will be an update -- Processing Dependency: perl(:MODULE_COMPAT_5.8.8) for package: 1:perl-parent-0.225-6.el5.noarch --- Package python-paramiko.noarch 0:1.7.5-2.1.el6 will be updated --- Package python-paramiko.noarch 0:1.7.6-1.el5 will be an update -- Processing Dependency: python(abi) = 2.4 for package: python-paramiko-1.7.6-1.el5.noarch -- Finished Dependency Resolution Error: Package: python-paramiko-1.7.6-1.el5.noarch (epel) Requires: python(abi) = 2.4 Installed: python-2.6.6-37.el6_4.i686 (@updates) python(abi) = 2.6 Available: python-2.6.6-36.el6.i686 (base) python(abi) = 2.6 Available: python26-2.6.8-2.el5.i386 (epel) python(abi) = 2.6 Error: Package: 1:perl-parent-0.225-6.el5.noarch (epel) Requires: perl(:MODULE_COMPAT_5.8.8) Error: Package: iotop-0.4.1-2.el5.noarch (epel) Requires: python(abi) = 2.4 Installed: python-2.6.6-37.el6_4.i686 (@updates) python(abi) = 2.6 Available: python-2.6.6-36.el6.i686 (base) python(abi) = 2.6 Available: python26-2.6.8-2.el5.i386 (epel) python(abi) = 2.6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@mailserver ~]# rpm -e epel-release-6-8.noarch [root@mailserver ~]# yum update Loaded plugins: fastestmirror, security Loading mirror speeds from cached hostfile * base: ftp.itu.edu.tr *
[SOGo] help ...
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 , attachment: sogo login error.png
RE: [SOGo] help ...
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 *:2 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 :2 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
RE: [SOGo] help ...
Dear Szládovics , 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 , My server installation : Contain .. apache 2,Mysql , postgresql,sogo SMTP server Postfix IMAP server Dovecot nano /var/lib/pgsql/data/pg_hba.conf 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 *:2 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: Szládovics Péter [mailto:p...@szladovics.hu] Sent: Monday, August 05, 2013 4:27 PM To: users@sogo.nu Subject: Re: [SOGo] help ... 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. attachment: sogo login error.png sogo.conf Description: Binary data SOGo requires the following : Update Server Epel Database server PostgreSQL LDAP server 389 Directory SMTP server Postfix IMAP server Dovecot Webmin Apache httpd Sogo ntp update Epel .. # yum update ... # sudo rpm -Uhv http://mirror.bytemark.co.uk/fedora/epel/6/i386/epel-release-6-8.noarch.rpm Database server PostgreSQL : yum install postgresql chkconfig
RE: [SOGo] help ...
Dear friend , Ok , thanks for this note any way I have wait very long time and I didn’t get any replay from you , so please accept my apologize . Best regards , Husam . From: Ludovic Marcotte [mailto:lmarco...@inverse.ca] Sent: Monday, August 05, 2013 10:52 PM To: users@sogo.nu Subject: Re: [SOGo] help ... On 2013-08-05 3:11 PM, husam.shabeeb wrote: 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 , It's not by copy/pasting the same stuff over and over to folks on the mailing list that you'll get help any faster. Worse, it might just drive people away from helping you. Be patient and try hitting yourself a couple of times with a cluebat - by actually reading the documentation available out there. -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] help
Dear friends , I need help , I have install the sogo . by yum .. But I can't access the web site .. for it I can't use command s Su - sogo . Not working .. Also I want to integrate it with 389 directory .. and its installed in another server . Best regards , And thanks in advanced .. -- users@sogo.nu https://inverse.ca/sogo/lists
RE: [SOGo] help
Dear Christian , Now I can access it , throw port :2000 But I can't login ,, I try sogo : sogo its not working , Its because of authentication need to be configured ? Can you help on that please ? Best regards , Husam , -Original Message- From: Christian Mack [mailto:christian.m...@uni-konstanz.de] Sent: Wednesday, July 31, 2013 4:03 PM To: users@sogo.nu Subject: Re: [SOGo] help Hello husam.shabeeb Am 2013-07-31 01:07, schrieb husam.shabeeb: I need help , I have install the sogo . by yum .. But I can't access the web site .. for it I can't use command s Su – sogo . Not working .. Sure, sogo is a service user now. So you can not login as that user, as he has no shell (see /etc/passwd). If I remember correctly this has changed in 2.0.5b. In order to get what you want, you have to use: sudo -u sogo bash Also I want to integrate it with 389 directory .. and its installed in another server . There is no problem with that, as long as you don't use Outlook with OpenChange. Just configure SOGo to use this server. See hostname, bindDN, bindPassword, bindFields and bindAsCurrentUser in SOGoUserSources. Kind regards, Christian Mack -- Christian Mack Gruppe Informationsdienste Rechenzentrum Universität Konstanz -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
RE: [SOGo] help
or SIGTERM Jul 31 16:07:28 sogod [6266]: 0x0xb57e927c[WOWatchDogChild] sending terminate signal to pid 6275 Jul 31 16:07:28 sogod [6266]: 0x0xb57d9364[WOWatchDog] Terminating with SIGINT or SIGTERM Jul 31 16:07:28 sogod [6266]: 0x0xb57d9364[WOWatchDog] Terminating with SIGINT or SIGTERM Jul 31 16:07:28 sogod [6266]: 0x0xb57e927c[WOWatchDogChild] child 6275 exited Jul 31 16:07:28 sogod [6266]: 0x0xb57d9364[WOWatchDog] all children exited. We now terminate. Jul 31 16:07:29 sogod [7398]: version 2.0.7 (build root@shiva.inverse 201307220922) -- starting Jul 31 16:07:29 sogod [7398]: vmem size check enabled: shutting down app when vmem 384 MB Jul 31 16:07:29 sogod [7398]: 0x0xb64a32b4[SOGoProductLoader] SOGo products loaded from '/usr/lib/GNUstep/SOGo': Jul 31 16:07:29 sogod [7398]: 0x0xb64a32b4[SOGoProductLoader] SchedulerUI.SOGo, MainUI.SOGo, Appointments.SOGo, ContactsUI.SOGo, Mailer.SOGo, PreferencesUI.SOGo, CommonUI.SOGo, Contacts.SOGo, AdministrationUI.SOGo, MailPartViewers.SOGo, MailerUI.SOGo Jul 31 16:07:29 sogod [7398]: 0x0xb63e63ec[WOWatchDog] listening on *:2 Jul 31 16:07:29 sogod [7398]: 0x0xb63e63ec[WOWatchDog] watchdog process pid: 7398 Jul 31 16:07:29 sogod [7398]: 0x0x5ff940[WOWatchDogChild] watchdog request timeout set to 10 minutes Jul 31 16:07:29 sogod [7398]: 0x0xb63e63ec[WOWatchDog] preparing 1 children Jul 31 16:07:29 sogod [7398]: 0x0xb63e63ec[WOWatchDog] child spawned with pid 7407 2013-07-31 16:07:30.034 sogod[7407] could not open channel to sogo@localhost Jul 31 16:07:30 sogod [7407]: [ERROR] 0x0xb6549054[GCSChannelManager] could not open channel 0x0xb67e8e44[PostgreSQL72Channel]: not-connected for URL: postgresql://sogo:sogo@localhost:5432/sogo/sogo_user_profile Jul 31 16:07:30 sogod [7407]: [WARN] 0x0xb6549054[GCSChannelManager] will prevent opening of this channel 5 seconds after 2013-07-31 16:07:29 -0400 -Original Message- From: Christian Mack [mailto:christian.m...@uni-konstanz.de] Sent: Wednesday, July 31, 2013 4:03 PM To: users@sogo.nu Subject: Re: [SOGo] help Hello husam.shabeeb Am 2013-07-31 01:07, schrieb husam.shabeeb: I need help , I have install the sogo . by yum .. But I can't access the web site .. for it I can't use command s Su – sogo . Not working .. Sure, sogo is a service user now. So you can not login as that user, as he has no shell (see /etc/passwd). If I remember correctly this has changed in 2.0.5b. In order to get what you want, you have to use: sudo -u sogo bash Also I want to integrate it with 389 directory .. and its installed in another server . There is no problem with that, as long as you don't use Outlook with OpenChange. Just configure SOGo to use this server. See hostname, bindDN, bindPassword, bindFields and bindAsCurrentUser in SOGoUserSources. Kind regards, Christian Mack -- Christian Mack Gruppe Informationsdienste Rechenzentrum Universität Konstanz -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
