[SOLVED] Intermittent users/status problem in the logs

Troubleshooting
1

Summary

We have several messages of “/api/v3/users/status” 404 being logged and I am not sure it’s related to 404 messages showing up in the users’ web interfaces.

Steps to reproduce

Not sure how to reproduce, it just started happening in a new v3.3.0 installation. Just followed the available production documentation for Ubuntu 14.04 with PG and NGINX/Let’s Encrypt. Absolutely nothing out of the ordinary.

Expected behaviour

From the System Console, I see several messages like this:

[2016/08/15 13:50:53 UTC] [INFO] Stopping Server...
[2016/08/15 13:50:53 UTC] [INFO] Closing SqlStore
[2016/08/15 13:50:53 UTC] [INFO] Loaded system translations for 'en' from '/home/mattermost/mattermost-dev/i18n/en.json'
[2016/08/15 13:50:54 UTC] [INFO] Current version is 3.3.0 (3.3.0/Fri Aug 12 20:27:37 UTC 2016/20735470185e0b0ac1d15b975041ed9a2e0e43bc/none)
[2016/08/15 13:50:54 UTC] [INFO] Enterprise Enabled: false
[2016/08/15 13:50:54 UTC] [INFO] Current working directory is /home/mattermost/mattermost-dev
[2016/08/15 13:50:54 UTC] [INFO] Loaded config file from /home/mattermost/mattermost-dev/config/config.json
[2016/08/15 13:50:54 UTC] [INFO] Server is initializing...
[2016/08/15 13:50:54 UTC] [INFO] Pinging sql master database
[2016/08/15 13:50:54 UTC] [INFO] Pinging sql replica-0 database
[2016/08/15 13:50:54 UTC] [INFO] Starting Server...
[2016/08/15 13:50:54 UTC] [INFO] Server is listening on :8065
[2016/08/15 13:50:54 UTC] [INFO] RateLimiter is enabled
[2016/08/15 13:51:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:51:24 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]
[2016/08/15 13:51:47 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:51:55 UTC] [EROR] /api/v3/users/profiles/: code=404 ip=186.203.7.150
[2016/08/15 13:52:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:52:26 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]
[2016/08/15 13:52:47 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:53:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:53:27 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]
[2016/08/15 13:53:47 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:54:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:54:29 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]
[2016/08/15 13:54:47 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:55:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:55:30 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]
[2016/08/15 13:55:47 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:56:07 UTC] [EROR] /api/v3/teams/channels/eybad1jzufbt7e3b3gfknxbgah/: code=404 ip=186.203.7.150
[2016/08/15 13:56:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:56:31 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]
[2016/08/15 13:56:47 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:57:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:57:33 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]

Observed behaviour

I would ignore this but sometimes the users receive a message bar saying that something went wrong and that a 404 occurred. But it is not 1 to 1 to the logs in the server, so I am not sure it’s correlated.

2

Hi,
having the exact same issue after updating v 3.3.0.
Nothing before with the v3.2.0

http://forum.mattermost.com/t/mattermost-team-edition-server-v3-3-0-eror-api-v3-users-status-code-404/2071

3

I’m also having this issue immediately after upgrading to 3.3.0. I noticed that I managed to make the 404 errors associated with my own IP address go away, but I’m not sure how. It might have been one of:

  • Restarting Mattermost enough times
  • Restarting my browser (chrome)
  • Restarting nginx

When my IP stopped showing up in the logs with this 404 error, my browser logged into Mattermost stopped displaying the top-bar complaint about an unexpected 404.

I’m still seeing the message reported every few seconds in the log with the IP addresses that I assume are other users who are logged in.

4

can you see this message when you’re using the native apps ?

I’ve been folowing exactly the install guide for RHEL7 and NGINX.
If there is any new stuff with the API v3 and nginx configuration, THEY should update their own guide.
You dont want this in a fresh installl.

5

We experience the same behaviour. Could you solve it?

6

In release note:
API Changes from v3.2 to v3.3
Updated admin routes:
Changed users/status from POST to GET

It must be that !

7

any update here? same issue for me after upgrading from 3.0.1 to 3.4. using nginx