# Known Issues

This list is maintained in a best effort fashion and may not reflect all known issues.

{% hint style="success" %}
**Want to report a bug?**\
\
Please let us know by giving us a shout in the **#poweron-pro** channel on our [Discord](https://discord.gg/libum) or an email at <development@libum.io>.
{% endhint %}

## Files disappear during Remote Sym synchronization

If you've set up your Remote Syms and are attempting to synchronize but the files and directories appear and disappear or just don't seem to appear at all, this may have to do with the fact that your WSL environment doesn't have write access to the mounted path you're using for the [Local Symitar Path](https://docs.libum.io/poweron-pro/settings#local-symitar-path) setting.

### Updating the wsl.conf

Some users have shown resolved this by updating the `wsl.conf` in their WSL environment to include the following:

```bash
[automount]
enabled = true
options = "metadata,umask=22,fmask=11,uid=<your_uid>,gid=<your_gid>
```

* `uid` - comes from running `id -u` in the WSL environment
* `gid` - comes from running `id -g` in the WSL environment

After making the change, you will need to restart the WSL environment which can be done by running `wsl --shutdown` and `wsl` to start it back up again.

## Permission Denied

If you're seeing any sort of `Permission Denied` issue in logs or bubbled up through the notifications, this most likely has to do with you missing the `SYM###` group for the Sym you're pointed to for your AIX user.

{% hint style="info" %}
**Note**\
\
Even with an HTTPs connection to Symitar we still leverage SSH for some utility (e.g. file deletions, rename, etc.) and will require these groups until we migrate those remaining functions.\
\
If you're having this issue and using the [Validate PowerOn](https://docs.libum.io/poweron-pro/commands#validate-poweron) command, please see the [Offline Validation setting](https://docs.libum.io/poweron-pro/settings#offline-validation) to prevent the build up of the temporary PowerOn files.
{% endhint %}

### Checking your groups

First determine whether or not you have the right Symitar group for the Sym you're trying to use.

1. SSH into the Symitar host

```bash
# the '-t' flag assigns you a pseudo terminal
ssh <aix_user>@<aix_host> -t '/usr/bin/ksh'
```

2. Run the `groups` command from the `$` prompt

```bash
$ groups
staff SYM627
```

From here, you may be missing the `SYM###` which is what's causing the permission <https://www.jackhenry.com/>denied failure when we try to write to a subdirectory within the Sym. To update your groups, check out the next section.

### Updating your groups

If you are indeed missing the target Sym group, you'll need to update it which will require elevated permissions. If you're on-premise, `su` or `root` should do but if you're with a data provider like [EASE](https://www.jackhenry.com/), [Synergent](https://synergentcorp.com/), or [MDT](https://www.mdtmi.com/), you will likely need to reach out to them to perform the change.

1. Update using `usermod`

```bash
# Note: <target_sym> will be the SYM### you're trying to connect to
usermod -a -G <target_sym> <aix_user>
```

Be sure to check to make sure it was sucessful before retrying anything in PowerOn Pro.
