pitrtools

In the cmd_archiver.ini file, if you don't specify the remote copy archive location with a trailing forward slash at the end, when you start to do WAL archiving, files will be created in the data directory of the slave, and the archive subdirectory will not be created. There is no such problem with or without the trailing forward slash for the local archive directory, l_archivedir.

To similulate the problem, set r_archivedir without a trailing slash, and make sure the $PGDATA/archive directory does not exist on the slave.
r_archivedir: /var/lib/postgresql/9.3/main/archive

To get it to run as expected, add the trailing slash and repeat the tests. Things work fine this way:
l_archivedir: /var/lib/postgresql/9.3/main/archive/