I noticed a similar issue. The new services were all created as uid:gid 1000:1000 (I don't have a uid or gid of 1000). I manually recursively chowned the folders with their corresponding users and groups (chown -R sickbeard.sickbeard sickbeard-amd64/) and then everything worked fine. But until I did that, the services wouldn't start at all.
I got the same behavior today on FreeNAS 8.2.0 (x64). Installed the Sabnzbd 1.0 plugin into the jail which I had already set up with the Subsonic plugin. The sabnzbd files are set up with 1000:1000 permissions and there's no user like sabnzbd. Any reason why this happened? Subsonic uses the media user, which has UID/GID 40001/40001.
Code:
software# pwd /usr/pbi/sabnzbd-amd64 software# ls -l total 429 drwxr-xr-x 2 root 1000 2 Sep 27 19:52 .headerdir -rw------- 1 root 1000 181 Oct 10 12:28 .oauth -rw-r--r-- 1 root 1000 336972 Sep 27 19:56 .pbi-hash-list drwxr-xr-x 2 root 1000 6 Sep 27 19:52 .sbin drwxr-xr-x 13 root 1000 26 Oct 10 12:54 SABnzbd drwxr-xr-x 2 root 1000 56 Sep 27 19:52 bin -rwxrwxr-x 1 1000 1000 99 Sep 15 19:30 control -rwxrwxr-x 1 1000 1000 2310 Sep 15 19:30 control.py drwxr-xr-x 5 media media 8 Oct 10 12:54 data -rw-rw-r-- 1 1000 1000 885 Sep 15 19:30 default.png drwxr-xr-x 3 root 1000 5 Oct 10 12:28 etc -rw-rw-r-- 1 1000 1000 15 Sep 15 19:30 freenas drwxr-xr-x 5 root 1000 13 Sep 27 19:52 include drwxr-xr-x 4 root 1000 42 Sep 27 19:52 lib -rwxrwxr-x 1 1000 1000 610 Sep 15 19:30 sabnzbd-update.sh drwxrwxr-x 3 1000 1000 11 Oct 10 12:28 sabnzbdUI -rwxrwxr-x 1 1000 1000 203 Sep 15 19:30 tweak-rcconf