MariaDB 10 replication strange behaviour
Ensure you have --log-slave-updates and --log-bin enabled in the servers.


  Normally, a slave does not write to its own binary log any updates
  that are received from a master server. This option causes the slave
  to write the updates performed by its SQL thread to its own binary
  log. For this option to have any effect, the slave must also be
  started with the --log-bin option to enable binary logging. Prior to
  MySQL 5.5, the server would not start when using the
  --log-slave-updates option without also starting the server with the --log-bin option, and would fail with an error; in MySQL 5.6, only a warning is generated. (Bug #44663) --log-slave-updates is used when
  you want to chain replication servers. For example, you might want to
  set up replication servers using this arrangement:
  
  A -> B -> C
  
  Here, A serves as the master for the slave B, and B serves as the
  master for the slave C. For this to work, B must be both a master and
  a slave. You must start both A and B with --log-bin to enable binary
  logging, and B with the --log-slave-updates option so that updates
  received from A are logged by B to its binary log.


Source: http://dev.mysql.com/doc/refman/5.6/en/replication-options-slave.html#option_mysqld_log-slave-updates