# Using pmm-admin with "local" configuration

**URL:** <https://forums.percona.com/t/using-pmm-admin-with-local-configuration/7070>\
**Category:** PMM 1.x\
**Created:** [June 20, 2019, 10:01am UTC](https://forums.percona.com/t/using-pmm-admin-with-local-configuration/7070 "2019-06-20T10:01:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![alceu](https://avatars.discourse-cdn.com/v4/letter/a/54ee81/32.png) [@alceu](https://forums.percona.com/u/alceu)\
**Post date:** [June 20, 2019, 10:01am UTC](https://forums.percona.com/t/using-pmm-admin-with-local-configuration/7070/1 "2019-06-20T10:01:45Z")

</div>

Hi there,

I’m being experimenting PMM for a while now, but still didn’t figure out how to properly use the pmm-admin cli.

I tried to use pmm-admin for both VM based and Docker based PMM, both 1.17.1 version, and everytime I start a new one and try to use it, the result is the same:

```auto
[admin&#64;localhost ~]$ pmm-admin
pmm-admin requires superuser privileges to manage system services.
[admin&#64;localhost ~]$ sudo -i
[root&#64;localhost ~]# pmm-admin ls
PMM client is not configured, missing config file. Please make sure you have run 'pmm-admin config'.
[root&#64;localhost ~]# pmm-admin check-network
PMM client is not configured, missing config file. Please make sure you have run 'pmm-admin config'.

```

If I follow up the instructions and execute the configuration I can finally starting using it, but then I’ll start seeing messages that I have orphaned exporters, and if I try to use , I remove them, which fix the warnings, but now I don’t have the “local” exporter running anymore (for OS, Prometheus and MySQL local instances).

Is there any way that I could use the cli and keep the default configurations?

The web interface is super easy to use, but I would like to avoid repeating over and over the process to add new instances (more specifically, AWS RDS instances).

Thanks in advance,

Alceu