Description of problem: CLIENT_CONNECT event is missed due to a mismatch in the events format. Following error is logged in events.log [2017-09-19 09:35:06,785] WARNING [glustereventsd - 46:handle] - Unable to parse Event 1505793906 97 client_uid=f241-16363-2017/09/19-04:05:06:747558-gv1-client-0-0-0;client_identifier=192.168.122.208:49150;server_identifier=192.168.122.208:49152;brick_path=/bricks/b1,subdir_mount=(null) Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Setup Eventsapi listener 2. Create a volume and mount 3. All events will be displayed in dashboard but not CLIENT_CONNECT
REVIEW: https://review.gluster.org/18322 (eventsapi: Fix issue with CLIENT_CONNECT event) posted (#1) for review on master by Aravinda VK (avishwan)
COMMIT: https://review.gluster.org/18322 committed in master by Atin Mukherjee (amukherj) ------ commit 23649f9ab73448737ee5d9509502f96e4775dca3 Author: Aravinda VK <avishwan> Date: Tue Sep 19 09:39:31 2017 +0530 eventsapi: Fix issue with CLIENT_CONNECT event A mismatch in event format causing below error in events.log when it detects CLIENT_CONNECT event. [2017-09-19 09:35:06,785] WARNING [glustereventsd - 46:handle] - Unable to parse Event 1505793906 97 client_uid=f241-16363-2017/09/19-04:05:06:747558-gv1-client- 0-0-0;client_identifier=192.168.122.208:49150;server_identifier= 192.168.122.208:49152;brick_path=/bricks/b1,subdir_mount=(null) BUG: 1492968 Change-Id: Ie6d507725a7e6b54fca44651f9c5e66eca2be244 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: https://review.gluster.org/18322 Reviewed-by: Atin Mukherjee <amukherj> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Amar Tumballi <amarts> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Prashanth Pai <ppai>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.13.0, please open a new bug report. glusterfs-3.13.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/