Koozali.org: home of the SME Server
Obsolete Releases => SME 9.x Contribs => Topic started by: stephdl on August 21, 2014, 11:52:16 PM
-
Ola
New version of smeserver-sogo (ONLY for SME9) with some cool features like sieve and active-sync, and also a panel in the server-manager to enable easily settings. To be honest I went to read the code of ipasserelle-groupware, and I have learnt many things that I didn't know before.
somehow, thank to daniel for that release. I use smeserver-dovecot-extras to add sieve and a function that I don't use Sharedmailbox (https://wikit.firewall-services.com/doku.php/smedev/dovecot).( see dovecot db (http://wiki.contribs.org/DB_Variables_Configuration#Dovecot))
This version is a bit bleeding age and needs to be improved, it is working for me, but I need your tests, feedbacks....
What you could test :
-The upgrade from smeserver-sogo-1.1
-All the sync from mobile, cardav, caldav, thunderbird
-track errors in logs (/var/log/messages, /var/log/httpd/admin_error_log/ , var/log/sogo/sogo.log)
....
In other words, please use it to debug it, however in first use virtual machine.
Until this version is fully tested, you have to download it manually before to install it.
wget http://mirror.de-labrusse.fr/Sme-Server/sogo/smeserver-dovecot-extras-0.1.1-1.el6.fws.noarch.rpm
wget http://mirror.de-labrusse.fr/Sme-Server/sogo/smeserver-sogo-1.3-3.el6.sme.noarch.rpm
yum install --enablerepo=sogo,epel smeserver-dovecot-extras-0.1.1-1.el6.fws.noarch.rpm smeserver-sogo-1.3-3.el6.sme.noarch.rpm
signal-event post-upgrade; signal-event reboot
-
new version, now sieve operates
wget http://mirror.de-labrusse.fr/Sme-Server/sogo/smeserver-dovecot-extras-0.1.1-1.el6.fws.noarch.rpm
wget http://mirror.de-labrusse.fr/Sme-Server/sogo/smeserver-sogo-1.3-4.el6.sme.noarch.rpm
yum install --enablerepo=sogo,epel smeserver-dovecot-extras-0.1.1-1.el6.fws.noarch.rpm smeserver-sogo-1.3-4.el6.sme.noarch.rpm
signal-event post-upgrade; signal-event reboot
no testers ?, i have had just one return about a french (merci jean-louis)
-
Hi,
Gave it a quick spin..
- Installs fine
- Sogo logfile is VERY verbose (I hope this can be turned off or levels lowered)
WOWhatdog shows many messages about killing processes and starting?
- /var log messages shows:
Sogod segfault with error 4 in libobjc.so.2.0.0
- Clicking Groups or Users in addressbook leads to error (Obect not found)
Did not test sync and thunderbird. Too much tech docs and manual settings :-)
guest
-
Hi,
Gave it a quick spin..
thank
- Installs fine
- Sogo logfile is VERY verbose (I hope this can be turned off or levels lowered)
indeed, every actions is logged and archived
WOWhatdog shows many messages about killing processes and starting?
- /var log messages shows:
Sogod segfault with error 4 in libobjc.so.2.0.0
not normal, i will look on that
- Clicking Groups or Users in addressbook leads to error (Obect not found)
that's a sogo bug, the next release should correct this
Did not test sync and thunderbird. Too much tech docs and manual settings :-)
guest
needs sogo guru therefore
-
Dear Stephane
while dealing with Sogo contrib, did you discover some more things about Sieve, particularly where Sieve script are located ?
Nicola
-
Sieve scripts are saved in users' home dir, eg
/home/e-smith/files/users/dani/sieve/sogo.sieve (the script itself, as saved by SOGo)
/home/e-smith/files/users/dani/.dovecot.svbin (the compiled version, as used by dovecot)
-
Hi Daniel
mmmm . . ..
the question was related to this post: http://forums.contribs.org/index.php/topic,51035.0.html
because I was trying to solve this little issue about "mail from"
I'll give a look.
Nicola
-
Looked: in effect for a user that has autoresponder enabled on Sogo I find /home/e-smith/files/users/dani/sieve/tmp (all empty) and the binary /home/e-smith/files/users/dani/.dovecot.svbin.
Nicola
-
Hi
I have made a test with a virtual machine using VirtualBox
SME 9 x64 – server-only , fresh install
The installation was fine, no errors
After sogo installation I create a group, and a user in server-manager, then I login, with the new user, in sogo and everything is fine.
So far so good...
After that I reboot the system, and when the system came up I can't login again on sogo.
Message : Wrong username or password
I thought I had done something wrong in the installation process, so I repeat all process from the begin, but he final result was the same. This time I take notes from every step.
These are all the steps that I made after the initial installation of SME-Server:
#yum update
#signal-event post-upgrade; signal-event reboot
#db yum_repositories set epel repository \
Name 'Epel - EL6' \
BaseUrl 'http://download.fedoraproject.org/pub/epel/6/$basearch' \
MirrorList 'http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=$basearch' \
EnableGroups no \
GPGCheck yes \
GPGKey http://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL \
Visible no \
status disabled
#signal-event yum-modify
#yum install gcc kernel-devel dkms --enablerepo=epel
#mkdir /media/cdrom
#mount -t iso9660 /dev/cdrom /media/cdrom/
#sh /media/cdrom/VBoxLinuxAdditions.run
#ln -s ../init.d/vboxadd /etc/rc7.d/S30vboxadd
#signal-event post-upgrade; signal-event reboot
#db yum_repositories set stephdl repository \
BaseURL http://mirror.de-labrusse.fr/smeserver/\$releasever \
EnableGroups no GPGCheck yes \
Name "Mirror de Labrusse" \
GPGKey http://mirror.de-labrusse.fr/RPM-GPG-KEY \
Visible yes status disabled
#db yum_repositories set sogo repository \
BaseURL http://inverse.ca/downloads/SOGo/RHEL6/\$basearch \
EnableGroups yes \
GPGCheck no \
Name "Inverse SOGo Repository" \
Visible yes \
status disabled
#signal-event yum-modify
#yum --enablerepo=stephdl,epel,sogo install smeserver-sogo
Output:
===================================================================================================
Package Arch Version Repository Size
===================================================================================================
Installing:
smeserver-sogo noarch 9:1.3-5.el6.sme stephdl 49 k
Installing for dependencies:
dovecot-pigeonhole x86_64 1:2.0.9-7.el6_5.1 updates 98 k
gnustep-base x86_64 1.23.0-1 sogo 1.6 M
gnustep-filesystem noarch 2.6.2-1.el6 epel 8.0 k
gnustep-make x86_64 2.6.2-1.el6 epel 265 k
lasso x86_64 2.3.6-1.centos6 sogo 664 k
libevent x86_64 1.4.13-4.el6 base 66 k
libmemcached x86_64 0.49-1 sogo 131 k
libobjc x86_64 4.4.7-4.el6 base 90 k
libwbxml x86_64 0.11.2-4.centos6 sogo 90 k
memcached x86_64 1.4.4-3.el6 base 68 k
python-memcached noarch 1.43-6.el6 base 32 k
smeserver-dovecot-extras noarch 0.1.1-1.el6.sme stephdl 9.5 k
sogo x86_64 2.2.9a-1.centos6 sogo 3.1 M
sogo-activesync x86_64 2.2.9a-1.centos6 sogo 74 k
sogo-ealarms-notify x86_64 2.2.9a-1.centos6 sogo 10 k
sogo-tool x86_64 2.2.9a-1.centos6 sogo 37 k
sope49-appserver x86_64 4.9-20140927_1664.el6.1 sogo 885 k
sope49-cards x86_64 2.2.9a-1.centos6 sogo 168 k
sope49-core x86_64 4.9-20140927_1664.el6.1 sogo 320 k
sope49-gdl1 x86_64 4.9-20140927_1664.el6.1 sogo 157 k
sope49-gdl1-contentstore x86_64 2.2.9a-1.centos6 sogo 56 k
sope49-gdl1-mysql x86_64 4.9-20140927_1664.el6.1 sogo 32 k
sope49-ldap x86_64 4.9-20140927_1664.el6.1 sogo 48 k
sope49-mime x86_64 4.9-20140927_1664.el6.1 sogo 279 k
sope49-sbjson x86_64 2.3.1-20140927_1664.el6.1 sogo 17 k
sope49-xml x86_64 4.9-20140927_1664.el6.1 sogo 193 k
xmlsec1 x86_64 1.2.19-3.el6 epel 172 k
xmlsec1-openssl x86_64 1.2.19-3.el6 epel 74 k
Transaction Summary
===================================================================================================
Install 29 Package(s)
#signal-event post-upgrade; signal-event reboot
In server-manager
I have created a group (sogousers) and a user (test) belonging to the group
in my /var/log/sogo/sogo.log I have:
Oct 07 16:02:41 sogod [1833]: [ERROR] [we-rm] did not find locale for language: Portuguese
Oct 07 16:02:41 sogod [1833]: <0x0x7f14706ebf28[LDAPSource]> <NSException: 0x7f147066e6b8> NAME:LDAPException REASON:operation bind failed: Invalid credentials (0x31) INFO:{login = "cn=test,ou=groups,dc=server1,dc=pt"; }
Oct 07 16:02:41 sogod [1833]: <0x0x7f14706ec548[LDAPSource]> <NSException: 0x7f1470753d28> NAME:LDAPException REASON:operation bind failed: Invalid credentials (0x31) INFO:{login = "uid=test,ou=users,dc=server1,dc=pt"; }
Oct 07 16:02:41 sogod [1833]: SOGoRootPage Login from '192.168.70.188' for user 'test' might not have worked - password policy: 65535 grace: -1 expire: -1 bound: 0
The error in first line is caused because I used a Portuguese version of Firefox to access sogo (I think that is not the cause of the problem).
Someone else had the same kind of problems ?
LuisM
-
With the user 'test', can you log to the horde webmail ?, do you have settled a password ?
-
Hi, stephdl
thanks for the fast reply
Yes I set a password, and yes I can login in horde after the reboot (I don't have tested before the reboot), and I also was able to login on sogo before reboot the system.
Before the reboot everything works perfectly, in both trials.
It's probably a stupid mistake that I make (twice), but I can't see where.
LuisM
-
please report
#rpm -qa sogo
-
#rpm -qa sogo
sogo-2.2.9a-1.centos6.x86_64
--------------------------------------------------------
New tries :
I created a new user (test2) and I was able to login and logout several times on Sogo, then I reboot again the system and the new user (test2) can't login also on Sogo.
And now the weirdest thing
I created a new user again (test3) was able to login sogo, then I remembered the test the user test3 on horde, and after several seconds, it show a message “Bad user or password”
-
Well I cannot reproduce but what I can see is that you have installed an alpha version (sogo 2.2.9a)
I have the feeling that Sogo is free to download of course but you are the beta/alpha testers, please note that for Microsoft you have to pay to be the testers.
-can you test without installed the virtualbox tools
-what is the history of this sme9 64, is it a recent installation, an upgrade of sme8 from an USB backup
-can you past the full sogo logs somewhere
-The log of installation could be also useful
-
Stephdl
For testing purposes on SME9 are details as posted above to be used or are procedures as detailed in the Wiki?
-
Nope nothing detailed, but feel free to add to the wiki. I'm considering to import the whole binaries of sogo in my server, but I worry for the bandwidth.
@luism: could you reproduce with another vm ?
-
In process of testing..
-
Nope nothing detailed, but feel free to add to the wiki. I'm considering to import the whole binaries of sogo in my server, but I worry for the bandwidth.
@luism: could you reproduce with another vm ?
My question was do I use the wiki instructions or the ones you posted here..because
This errors..
[root@sme9sogo ~]# wget http://mirror.de-labrusse.fr/Sme-Server/sogo/smeserver-sogo-1.3-4.el6.sme.noarch.rpm
--2014-10-08 15:19:09-- http://mirror.de-labrusse.fr/Sme-Server/sogo/smeserver-sogo-1.3-4.el6.sme.noarch.rpm
Resolving mirror.de-labrusse.fr... 87.106.94.114
Connecting to mirror.de-labrusse.fr|87.106.94.114|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2014-10-08 15:19:10 ERROR 404: Not Found.
-
You could follow the wiki instructions....the instruction here was to test the new rpm....now it is released in my repo
-
I am experiencing the same issue as the user luism.
VMware 5.5 clean install of SME9, not from a backup, apply all new updates.
Install sogo as per wiki, create user, create group, add user to group..
Start sogo and login with users details success..
Reboot
Now login fails with Wrong username or password
Try resetting password - fail
Add new user - login success
Reboot system
ALL logins to Sogo now fail.
-
Today I'm not near of my PC, and I will be away for 3 or 4 days, so I can't do new tests.
In the previous tests the SME9 64 was always a new installation, not a upgrade and I also did not make any restore from other systems when installing the SME.
About the version of sogo was the version that was installed when I entered
#yum --enablerepo=stephdl,epel,sogo install smeserver-sogo
As you can see on my first post in the output of the command above.
I'm not a alfa or beta tester of sogo, and I have used the repo information of the wiki procedure, so anyone who follows that procedure, should install the same versions.
LuisM
-
well what could be good is to test with a yum downgrade to 2.2.8, either by download all by hand, or by doing 'yum downgrade sogo\*'
@luism: the sogo repository doesn't let you the choice to select which version you want because the latest is chosen by yum. I know that the version 2.2.8 is workable, but the version 2.2.7 is buggy. The only good option I could have is to set my own repository and to release a selected version of sogo. You have installed a version with a 'a' (2.2.9a)
-
I am experiencing the same issue as the user luism.
VMware 5.5 clean install of SME9, not from a backup, apply all new updates.
Install sogo as per wiki, create user, create group, add user to group..
Start sogo and login with users details success..
Reboot
Now login fails with Wrong username or password
Try resetting password - fail
Add new user - login success
Reboot system
ALL logins to Sogo now fail.
Well it is not funny, i cannot reproduce :(
I have follow all your steps and I can perform a login. When you spoke about 'Reboot' you mean a 'post-upgrade & reboot' or a pure 'reboot' without reconfiguration
-
Well it is not funny, i cannot reproduce :(
I have follow all your steps and I can perform a login. When you spoke about 'Reboot' you mean a 'post-upgrade & reboot' or a pure 'reboot' without reconfiguration
Pure reboot and also tried a reboot and reconfig..everything is fine login works up until a reboot is performed
I'll find the log entries and attach or post section
-
If I create a new user I can login to Sogo, users already created etc are still not able to, on reboot new user becomes as for other users unable to login to Sogo.
192.168.2.11 - - [09/Oct/2014:10:36:59 GMT] "POST /SOGo/connect HTTP/1.1" 403 34/63 0.007 - - 0
Oct 09 10:38:03 sogod [2029]: <0x0x7fcd108e4338[LDAPSource]> <NSException: 0x7fcd103c5088> NAME:LDAPException REASON:operation bind failed: Invalid credentials (0x31) INFO:{login = "cn=terry3,ou=groups,dc=sme9,dc=fage,dc=esxi,dc=org"; }
Oct 09 10:38:03 sogod [2029]: SOGoRootPage successful login from '192.168.2.11' for user 'terry3' - expire = -1 grace = -1
Reboot
192.168.2.11 - - [09/Oct/2014:10:41:15 GMT] "GET /SOGo/so/terry3/logoff HTTP/1.1" 200 3977/0 3.300 12558 68% 5M
Oct 09 10:42:34 sogod [2049]: <0x0x7ff8c49e26a8[LDAPSource]> <NSException: 0x7ff8c4c06928> NAME:LDAPException REASON:operation bind failed: Invalid credentials (0x31) INFO:{login = "cn=terry3,ou=groups,dc=sme9,dc=fage,dc=esxi,dc=org"; }
Oct 09 10:42:34 sogod [2049]: <0x0x7ff8c49e6af8[LDAPSource]> <NSException: 0x7ff8c4ed0408> NAME:LDAPException REASON:operation bind failed: Invalid credentials (0x31) INFO:{login = "uid=terry3,ou=users,dc=sme9,dc=fage,dc=esxi,dc=org"; }
Oct 09 10:42:34 sogod [2049]: SOGoRootPage Login from '192.168.2.11' for user 'terry3' might not have worked - password policy: 65535 grace: -1 expire: -1 bound: 0
-
Well I cannot reproduce but what I can see is that you have installed an alpha version (sogo 2.2.9a)
No, it's not an alpha version. SOGo releases ends with "a", "b", "c" etc... when critical bugs are fixed after a release, but it doesn't worth a new release number. 2.2.9a is the last stable version today
-
moving to SME 9.x Contribs
-
@terry: could you clone first your vm and on your clone remove smeserver-sogo and install the previous version smeserver-sogo-1.1-2.el6
yum downgrade smeserver-sogo --enablerepo=stephdl
Please look if the problem is not present with this version of smeserver-sogo. IF not try to upgrade smeserver-sogo to see if the problem is reproducible.
-
OK stephdl back on this, I had posted a reply, at least I thought I did saying I was busy using all hardware resources on bug 6911..maybe it got swept up in the house cleaning :-)
-
OK Stephdl downgraded as requested:
[root@sme9sogoclone ~]# rpm -qa smeserver-sogo
smeserver-sogo-1.1-2.el6.sme.noarch
Still with current release of Sogo
[root@sme9sogoclone ~]# rpm -qa sogo
sogo-2.2.9a-1.centos6.x86_64
Current users are unable to login to Sogo..
Create a new user and they are able to login
Reboot system
New user is now as per all other users, NOT able to login to Sogo
-
I suppose that you have reconfigured the server with 'post-upgrade & reboot', if yes then the new package smeserver-sogo is not in cause
-
Definetly..
-
Further testing..
If I follow wiki and
Create a group
Reset the users password
Add user to the group
Then I am able to login to sogo using an existing user HOWEVER as soon as I do a reboot the behaviour returns ie can't login to sogo
-
Hi
If you try to downgrade sogo, is this workable
yum downgrade sogo\*-2.2.8 --enablerepo=sogo
-
I could be interested also to see if tables are well created in mysql
# mysql
# use sogo;
# show tables;
+-----------------------------+
| Tables_in_sogo |
+-----------------------------+
| sogo_alarms_folder |
| sogo_folder_info |
| sogo_sessions_folder |
| sogo_user_profile |
| sogohelene00160ab7fd5 |
| sogohelene00160ab7fd5_acl |
| sogohelene00160ab7fd5_quick |
| sogohelene00176d7e096 |
| sogohelene00176d7e096_acl |
| sogohelene00176d7e096_quick |
+-----------------------------+
10 rows in set (0.01 sec)
As you can see the user 'helene' is the unique user of sogo
-
Will downgrade next
mysql> show tables;
+-----------------------------+
| Tables_in_sogo |
+-----------------------------+
| sogo_alarms_folder |
| sogo_folder_info |
| sogo_sessions_folder |
| sogo_user_profile |
| sogoterry001788627f5 |
| sogoterry001788627f5_acl |
| sogoterry001788627f5_quick |
| sogoterry20016ae62fa8 |
| sogoterry20016ae62fa8_acl |
| sogoterry20016ae62fa8_quick |
| sogoterry30011a529a0d |
| sogoterry30011a529a0d_acl |
| sogoterry30011a529a0d_quick |
| sogoterry40015616b892 |
| sogoterry40015616b892_acl |
| sogoterry40015616b892_quick |
| sogoterry4002440bbcf2 |
| sogoterry4002440bbcf2_acl |
| sogoterry4002440bbcf2_quick |
+-----------------------------+
19 rows in set (0.00 sec)
Same behaviour from downgraded version
-
Well, could be nice that I can have access directly to the server by ssh/https, is this possible. Of course I need a sudo access and with the luck I have this last time, ma new nickname is 'dd'.....you are warned.
@daniel/sogo_gurus: No ideas of what could be explored, I cannot reproduce here.
-
Hi, I'm back,
I did several tests with different versions of sogo, with and without VBoxAdditions, with 2 different versions of VirtualBox in 2 different hosts, and always got the same result.
Seems to me that the problem is related to LDAP authentication, so I went looking for something in /var/log/ldap/current.log
Before the reboot when I login in sogo, the log file shows
@40000000543967711bb3aacc conn=1036 fd=13 ACCEPT from IP=127.0.0.1:38704 (IP=0.0.0.0:389)
@40000000543967711bb7d534 conn=1036 op=0 BIND dn="uid=test2,ou=users,dc=server1,dc=pt" method=128
@40000000543967711bcaad6c conn=1036 op=0 BIND dn="uid=test2,ou=Users,dc=server1,dc=pt" mech=SIMPLE ssf=0
@40000000543967711bcc7e44 conn=1036 op=0 RESULT tag=97 err=0 text=
@40000000543967711bd88c34 conn=1036 op=1 UNBIND
@40000000543967711bd8c6cc conn=1036 fd=13 closed
@4000000054396914384f003c conn=1037 fd=13 ACCEPT from IP=127.0.0.1:38719 (IP=0.0.0.0:389)
@4000000054396914385c2b54 conn=1037 op=0 BIND dn="uid=test2,ou=users,dc=server1,dc=pt" method=128
@4000000054396914385c5e1c conn=1037 op=0 BIND dn="uid=test2,ou=Users,dc=server1,dc=pt" mech=SIMPLE ssf=0
@4000000054396914385c8cfc conn=1037 op=0 RESULT tag=97 err=0 text=
@4000000054396914386468b4 conn=1037 op=1 UNBIND
@400000005439691438647084 conn=1037 fd=13 closed
When I reboot
@40000000543969d5223cf9fc slapd shutdown: waiting for 0 operations/tasks to finish
@40000000543969d52b647794 slapd stopped.
When I try to login again in sogo with no success
@4000000054396a5a29a2da04 conn=1001 fd=13 ACCEPT from IP=127.0.0.1:47155 (IP=0.0.0.0:389)
@4000000054396a5a29a65c74 conn=1001 op=0 BIND dn="cn=test2,ou=groups,dc=server1,dc=pt" method=128
@4000000054396a5a29aca9bc conn=1001 op=0 RESULT tag=97 err=49 text=
@4000000054396a5a2abd23a4 conn=1001 op=1 UNBIND
@4000000054396a5a2abd3b14 conn=1001 fd=13 closed
@4000000054396a5a2ad5dbc4 conn=1002 fd=13 ACCEPT from IP=127.0.0.1:47156 (IP=0.0.0.0:389)
@4000000054396a5a2ad850ac conn=1002 op=0 BIND dn="uid=test2,ou=users,dc=server1,dc=pt" method=128
@4000000054396a5a2ade4bec conn=1002 op=0 RESULT tag=97 err=49 text=
@4000000054396a5a2aea1f44 conn=1002 op=1 UNBIND
@4000000054396a5a2aeca7b4 conn=1002 fd=13 closed
I do not know if it's important, as I have no knowledge of LDAP.
Some LDAP guru could check this ?
-
Hi All,
Issue still there, new user, passwd, group able to log in to sogo, reboot the server, disaster!! no login possible...
thanks to all for the work you guys are doing...
-
Issue still there, new user, passwd, group able to log in to sogo, reboot the server, disaster!! no login possible...
Do your Installation is a fresh install or it is an upgrade from an older one.
please do and return
rpm -qa | grep -i sogo
-
For those who have this problem, can you install phpldapadmin (http://wiki.contribs.org/Phpldapadmin) and see if you can log and parse your ldap database, I have this error 'Unable to login.
Your HTTP based authentication is not accepted by the LDAP server'
Moreover I cannot see users settled in the server-manager with phpldapadmin (ou=Users)
In clear I worry that the problem comes from the core ldap and not sogo. I have tested on the VM of terry and compared with my server....My problem is that this bug is not easily reproducible
Please test and report
-
A bug should be opened to track this kind of issue. The forum is not a good place to diagnose. It can be opened against the SOGo contrib, and moved to the core is the problem appears to be in LDAP. When opening the bug, please attach your ldap logs snippet when trying to login (the same as posted by luism). You can also check on the command line:
ldapsearch -x -D cn=root,dc=server1,dc=pt -w $(cat /etc/pam_ldap.secret) -b ou=Users,dc=domain,dc=tld "uid=test2"
You can also try to bind with the user2 on LDAP:
ldapsearch -x -D uid=user2,ou=Users,dc=server1,dc=pt -W
And check if there's any output or an error message
-
bug opened http://bugs.contribs.org/show_bug.cgi?id=8611
-
bug opened http://bugs.contribs.org/show_bug.cgi?id=8611
For this interested in Sogo there has been some progress..