Topic: Smeserver-sogo : Need tests

[stephdl]

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 ?

[TerryF]

In process of testing..

[TerryF]

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.

[stephdl]

You could follow the wiki instructions....the instruction here was to test the new rpm....now it is released in my repo

[TerryF]

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.

[luism]

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

[stephdl]

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)

[stephdl]

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

[TerryF]

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

[TerryF]

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

[Daniel B.]

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

[Stefano]

moving to SME 9.x Contribs

[stephdl]

@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

Code: [Select]

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.

[TerryF]

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

[TerryF]

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