Scalix Forums

Hi

We are trying to use mobile client for the first time, and whatever we type into th elogin box we always get the "wrong username or password" error. I have read through the forums and tried to learn from people who have had this problem before - but haven't been able to make any progress.

The main errors I can find relating to this are in the scalix-api.log file:
at java.lang.Thread.run(Unknown Source)
Caused by: javax.mail.AuthenticationFailedException: AUTHENTICATE failure, user
name or password rejected
at com.sun.mail.imap.IMAPStore.protocolConnect(Unknown Source)
at javax.mail.Service.connect(Unknown Source)
at com.scalix.api.auth.ImapAuthenticationService.authenticate(ImapAuthen
ticationService.java:71)
... 23 more
2007-05-08 23:04:43,030 ERROR [CheckAuthInterceptor.preHandle:57] Problem encout
ered during authentication
A00004 wrong username or password
at com.scalix.api.auth.ImapAuthenticationService.authenticate(ImapAuthen
ticationService.java:116)
at com.scalix.api.auth.Frontdoor.authenticate(Frontdoor.java:23)
at com.scalix.api.rest.CheckAuthInterceptor.preHandle(CheckAuthIntercept
or.java:47)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(Dispatch
erServlet.java:707)
at org.springframework.web.servlet.DispatcherServlet.doService(Dispatche
rServlet.java:658)
at org.springframework.web.servlet.FrameworkServlet.processRequest(Frame
workServlet.java:392)
at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServl
et.java:347)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja
va:684)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSock
et.java:876)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.mail.AuthenticationFailedException: AUTHENTICATE failure, user
name or password rejected
at com.sun.mail.imap.IMAPStore.protocolConnect(Unknown Source)
at javax.mail.Service.connect(Unknown Source)
at com.scalix.api.auth.ImapAuthenticationService.authenticate(ImapAuthen
ticationService.java:71)
... 23 more


The scalix-mobile.log file is completely empty.

Funnily enough when I checked the pgstartup.log file there WERE errors at the end relating to not being able to start IMAP because the port was in use, so I restarted the scalix-postgres and scalix-tomcat services. The postgres startup logfile now no longer contains any IMPA errors at the end but has made no difference; we still can't log in to mobile client. IMAP access from outlook works fine, as does SWA.

There are no errors in the apache log file.

Don't know if it's relevant, but we also have not been able to get searching working yet - I suspect this is something different.

I've also noticed that if I just put a username in (and no nodename) I get the following in catalina.out:

javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; rema
ining name 'o=Scalix'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.searchAux(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.c_search(Unknown Source)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(Unknown Source)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown So
urce)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown So
urce)
at javax.naming.directory.InitialDirContext.search(Unknown Source)
at com.scalix.api.directory.Directory.getAttributesBySmtpAddress(Directo
ry.java:51)
at com.scalix.api.auth.ImapAuthenticationService.authenticate(ImapAuthen
ticationService.java:168)
at com.scalix.api.auth.Frontdoor.authenticate(Frontdoor.java:23)
at com.scalix.api.rest.CheckAuthInterceptor.preHandle(CheckAuthIntercept
or.java:47)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(Dispatch
erServlet.java:707)
at org.springframework.web.servlet.DispatcherServlet.doService(Dispatche
rServlet.java:658)
at org.springframework.web.servlet.FrameworkServlet.processRequest(Frame
workServlet.java:392)
at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServl
et.java:347)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:148)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.ja
va:684)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSock
et.java:876)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:684)
at java.lang.Thread.run(Unknown Source)

But I suspect that might be normal?


Any ideas? We recently upgraded to 11.0.2.1in case that is relevant.. and we are running on SLES 9

Thx

Can anyone help???

webmail search does not work...... in case that is relevant....

lsof -i:5733 produces
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
postmaste 417 postgres 8u IPv4 25692397 TCP austin.internal:5733->au
stin.internal:39896 (ESTABLISHED)
postmaste 418 postgres 8u IPv4 25692400 TCP austin.internal:5733->au
stin.internal:39897 (ESTABLISHED)
postmaste 419 postgres 8u IPv4 25692403 TCP austin.internal:5733->au
stin.internal:39898 (ESTABLISHED)
postmaste 30908 postgres 8u IPv4 25664760 TCP austin.internal:5733->au
stin.internal:37433 (ESTABLISHED)
postmaste 30909 postgres 8u IPv4 25664767 TCP austin.internal:5733->au
stin.internal:37434 (ESTABLISHED)
java 31161 root 10u IPv4 25664759 TCP austin.internal:37433->a
ustin.internal:5733 (ESTABLISHED)
java 31161 root 19u IPv4 25692396 TCP austin.internal:39896->a
ustin.internal:5733 (ESTABLISHED)
java 31161 root 20u IPv4 25692399 TCP austin.internal:39897->a
ustin.internal:5733 (ESTABLISHED)
java 31161 root 21u IPv4 25692402 TCP austin.internal:39898->a
ustin.internal:5733 (ESTABLISHED)
java 31161 root 120u IPv4 25664766 TCP austin.internal:37434->a
ustin.internal:5733 (ESTABLISHED)
postmaste 31276 postgres 3u IPv4 23154475 TCP austin.internal:5733 (LI
STEN)


and the postgres startup log looks fine

Hi!

Are you able to login mobile-client for any other user. Can you login SWA using the same
username/password? What are the un-commented lines in the file
/var/opt/scalix/??/postgres/data/pg_hba.conf.

Can you send the result of the commands:
omshowu -n <username>/<mailnode>
omstat -a
omstat -s
ps ax | grep post
ps ax | grep tomcat
lsof -i:8009

Thanks,
Subir

Hi.

No, mobile client doesn't seem to work for anyone.
SWA works fine for all users (including tnscadmin which I'm using for testing)
Here are the results of the commands:

Uncommented lines in postgres file:

host scalix scalix 192.168.128.210/32 md5
local all all ident sameuser

austin:~ # omshowu -n tnscadmin/austin,internal
Authentication ID: tnscadmin
Globally Unique ID: 035000001aab9e44-012.821.861.291
User Name : tnscadmin /CN=tnscadmin
MailNode : austin,internal
Internet Address : TNSC Admin <tnscadmin@kwltd.com>
System Login : 60543
Password : unset
Admin Capabilities : NO
Mailbox Admin Capabilities : NO
Language : C
Mail Account: Unlocked
Last Signon : 05.10.07 15:59:07
Receipt of mail : ENABLED
Service level : 0
Excluded from Tidying : NO
Recovery Folder visible : NO
User Class : Full
SIS URL : sxidx://austin.internal/05c000001aab9e4 ... 21.861.291

austin:~ # omstat -a
PC Monitor Started NON-STOP 0
Directory Relay Server Started 05.08.07
Notification Server Started 05.08.07 0
Shared memory daemon Started NON-STOP
Notification Monitor Started NON-STOP
Session Monitor Started NON-STOP
Indexer Started NON-STOP
Stats Daemon Started NON-STOP
Container Access Monitor Started NON-STOP
Item Structure Server Stopped 03.31.07
Database Monitor Started 05.08.07
Licence Monitor Daemon Started NON-STOP
LDAP Daemon Started 05.08.07
Queue Manager Started NON-STOP
Item Delete Daemon Started NON-STOP
IMAP Server Daemon Started 05.08.07
SMTP Relay Started 05.08.07
Mime Browser Controller Started 12:18:17
Event Server Started 05.08.07

austin:~ # omstat -s
Service Router Started 05.08.07 0
Local Delivery Started 05.08.07 0
Internet Mail Gateway Started 05.08.07 0
Local Client Interface Enabled 05.08.07 1
Remote Client Interface Enabled 05.08.07 1
Test Server Started 05.08.07 0
Request Server Started 05.08.07 0
Print Server Started 05.08.07 0
Bulletin Board Server Started 05.08.07 0
Background Search Service Started 05.08.07 0
CDA Server Started 05.08.07 0
POP3 interface Started 05.08.07 0
Omscan Server Started 05.08.07 0
Archiver Started 05.08.07 0

austin:~ # ps ax | grep post
9617 ? S 0:00 /usr/bin/postmaster -D /var/lib/pgsql/data
9867 ? S 0:00 postgres: stats buffer process
9868 ? S 0:00 postgres: stats collector process
31276 ? S 0:00 /usr/bin/postmaster -i -h austin.internal -p 5733 -D /var/opt/scalix/an/postgres/data -k /var/opt/scalix/an/postgres/data
31278 ? S 0:00 postgres: stats buffer process
31279 ? S 0:00 postgres: stats collector process
15661 ? S 0:00 postgres: scalix scalix 192.168.128.210 idle
17424 ? S 0:00 postgres: scalix scalix 192.168.128.210 idle
17425 ? S 0:00 postgres: scalix scalix 192.168.128.210 idle
17426 ? S 0:00 postgres: scalix scalix 192.168.128.210 idle
19019 ? S 0:00 postgres: scalix scalix 192.168.128.210 idle
19929 pts/1 R+ 0:00 grep post
austin:~ # ps ax | grep tomcat
31161 ? Sl 19:53 /usr/java/jre1.5.0_06/bin/java -server -Djava.net.preferIPv4Stack=true -Xms512m -Xmx512m -Dscalix.instance=/var/opt/scalix/an -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/var/opt/scalix/an/tomcat/conf/logging.properties -Djava.endorsed.dirs=/opt/scalix-tomcat/common/endorsed -classpath /usr/java/jre1.5.0_06/lib/tools.jar:/opt/scalix-tomcat/bin/bootstrap.jar:/opt/scalix-tomcat/bin/commons-logging-api.jar -Dcatalina.base=/var/opt/scalix/an/tomcat -Dcatalina.home=/opt/scalix-tomcat -Djava.io.tmpdir=/var/opt/scalix/an/tomcat/temp org.apache.catalina.startup.Bootstrap start
19940 pts/1 S+ 0:00 grep tomcat

austin:~ # lsof -i:8009
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
httpd2-pr 845 wwwrun 15u IPv4 25868214 TCP austin.internal:50845->austin.internal:8009 (ESTABLISHED)
httpd2-pr 12207 wwwrun 15u IPv4 25868841 TCP austin.internal:50873->austin.internal:8009 (ESTABLISHED)
httpd2-pr 13925 wwwrun 15u IPv4 25871343 TCP austin.internal:51051->austin.internal:8009 (ESTABLISHED)
httpd2-pr 24169 wwwrun 15u IPv4 25868157 TCP austin.internal:50829->austin.internal:8009 (ESTABLISHED)
httpd2-pr 25572 wwwrun 15u IPv4 25857109 TCP austin.internal:50029->austin.internal:8009 (ESTABLISHED)
httpd2-pr 30676 wwwrun 15u IPv4 25864496 TCP austin.internal:50570->austin.internal:8009 (ESTABLISHED)
java 31161 root 38u IPv4 23154898 TCP austin.internal:8009 (LISTEN)
java 31161 root 175u IPv4 25868842 TCP austin.internal:8009->austin.internal:50998 (ESTABLISHED)
java 31161 root 245u IPv4 25863877 TCP austin.internal:8009->austin.internal:50568 (ESTABLISHED)
java 31161 root 246u IPv4 25864497 TCP austin.internal:8009->austin.internal:50829 (ESTABLISHED)
java 31161 root 253u IPv4 25864483 TCP austin.internal:8009->austin.internal:50570 (ESTABLISHED)
java 31161 root 254u IPv4 25857100 TCP austin.internal:8009->austin.internal:50029 (ESTABLISHED)
java 31161 root 258u IPv4 25868163 TCP austin.internal:8009->austin.internal:50845 (ESTABLISHED)
java 31161 root 261u IPv4 25868215 TCP austin.internal:8009->austin.internal:50873 (ESTABLISHED)
java 31161 root 262u IPv4 25870571 TCP austin.internal:8009->austin.internal:51051 (ESTABLISHED)
httpd2-pr 31586 wwwrun 15u IPv4 25870570 TCP austin.internal:50998->austin.internal:8009 (ESTABLISHED)
httpd2-pr 31590 wwwrun 15u IPv4 25864482 TCP austin.internal:50568->austin.internal:8009 (ESTABLISHED)

Hi!

Did you run Scalix Installer to re-configure any of the following components individually:
Scalix-DB or Scalix Messaging Services or Platform, if so, this is a known bug and this
cause users to be locked out when they later try to sign in to the Scalix Mobile Web Client.
(Bug 13947: http://bugzilla.scalix.com/show_bug.cgi?id=13947).

The workaround for the bug 13947 is:
If the PostgreSQL database password changes, it must also be changed in the
file, platform.properties, which is located at <instance>/platform/platform.properties.
This requires a restart of Tomcat. If the database is on a separate server from the
platform, this change must be done manually.

Check the following post that handles same issue, note there are two pages in this post:
viewtopic.php?t=6007

Hope this helps.

Thanks,
Subir

Hi.

No, we didn't reconfigure anything individually -we just did an upgrade to the current version.

I am curious - can you tell me which information I sent you suggests that the problem might be a postgres password problem? I couldn't see any error messages relating to postgres problems - the only message seems to be the authentication message saying that the username and passwrd had been rejected. Is it because SWA searching also doesn't work? That must also be a clue I suppose....

If this is NOT the reason, what can I try next?

I have read that article and my symptoms seem very similar to those reported by k4ci - however their problem went away by itself when k4ci restarted the services. It doesn't look like they fixed it using your advice....???

Hi!

When SWA-Mobile does not work, I normally doubt on Platform and Postgres, I missed the
lsof -i:5733 you sent earlier.

What is the value for platform.url in the file /var/opt/scalix/s4/mobile/mobile.properties? Do
you see any problem in httpd access_log or error_log?

What is the result for the command "lsof -i:8009"?

Thanks,
Subir

I have answered at least 2 of those questions already - see earlier replies...

What is the value for platform.url in the file /var/opt/scalix/s4/mobile/mobile.properties? Do
you see any problem in httpd access_log or error_log?

-Subir

Hi Greg,

I took a look at the source code to see if I can help unravel this error. Judging by location where the error message is generated, It appears that the mobile application is communicating successfully with the platform, and the platform is communicating with the IMAP server. Also, this error occurs before the platform initiates contact with postgres. Consequently, I think you can rule out problems with the connection settings for the IMAP server, postgres, and platform.

The error message, "AUTHENTICATE failure, user
name or password rejected", comes directly from the IMAP server in response to the connection attempt. Have you checked the IMAP server logs?

SWA and the mobile client use nearly identical methods for exchanging authorization data with the platform API, which is why it's surprising that one works and the other does not. However, unlike the mobile app, SWA will recover and use the IMAP server directly if it fails to utilize the platform API. Does the "AUTHENTICATE failure" message get written to the log when an SWA user logs in, or does it appear ONLY for logins from the mobile app?

Have you tried accessing the mobile app from a regular desktop browser instead of a mobile device? It would be interesting to know if the same browser that successfully connects to SWA cannot connect to the mobile app.

Hi

Which is the best file to check for SWA errors?

All my testing has been done from a normal browser and not from a mobile device...

I did also verify that IMAP works fine for that user when using outlook, if that helps...

Thanks
Greg

I tried watching the scalix-swa.log file whilst logging in to webmail, and nothing gets added to the file.....

gregwatson wrote:Hi

Which is the best file to check for SWA errors?

All my testing has been done from a normal browser and not from a mobile device...

I did also verify that IMAP works fine for that user when using outlook, if that helps...

Thanks
Greg

You should enable activity logging as detailed here :
http://www.scalix.com/wiki/index.php?ti ... g/api-logs
Then enable IMAP logging either manually if you know how to to that,
or using the script here :
http://www.scalix.com/wiki/index.php?ti ... /imap-logs