# Error doing clogin into a wpar

**URL:** <https://community.unix.com/t/error-doing-clogin-into-a-wpar/376020>\
**Category:** AIX\
**Created:** [July 30, 2019, 12:37pm UTC](https://community.unix.com/t/error-doing-clogin-into-a-wpar/376020 "2019-07-30T12:37:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sandra25350](https://community.unix.com/letter_avatar/sandra25350/32/5_5575768a8748004e209b776fc1b2916d.png) [@sandra25350](https://community.unix.com/u/sandra25350)\
**Post date:** [July 30, 2019, 12:37pm UTC](https://community.unix.com/t/error-doing-clogin-into-a-wpar/376020/1 "2019-07-30T12:37:45Z")

</div>

I have this error when I'm trying to do `clogin` from AIX 7200-00-00-0000 into a wpar with AIX 5.2

```nohighlight
abanksPaDesa2:/> clogin AbanksBDPA_wpar
exec: A file or directory in the path name does not exist

```

somebody can help me to fix this? I'm restoring the wpar from wpar mksysb not a mksysb from principal Lpar.

Thanks,

---

<div class="post-metadata">

**Author:** ![Neo](https://community.unix.com/user_avatar/community.unix.com/neo/32/22838_2.png) [@Neo](https://community.unix.com/u/Neo)\
**Post date:** [July 31, 2019, 1:26am UTC](https://community.unix.com/t/error-doing-clogin-into-a-wpar/376020/2 "2019-07-31T01:26:15Z")

</div>

You can also log into a system WPAR remotely by using a network-based login command, such as the `rlogin` command, the `telnet` command, or the `rsh` command.

---

<div class="post-metadata">

**Author:** ![bakunin](https://community.unix.com/letter_avatar/bakunin/32/5_5575768a8748004e209b776fc1b2916d.png) [@bakunin](https://community.unix.com/u/bakunin)\
**Post date:** [July 31, 2019, 3:21am UTC](https://community.unix.com/t/error-doing-clogin-into-a-wpar/376020/3 "2019-07-31T03:21:34Z")

</div>

> [@sandra25350](#):
>
> ```plaintext
> abanksPaDesa2:/> clogin AbanksBDPA_wpar
> exec: A file or directory in the path name does not exist
> 
> ```
> 
> somebody can help me to fix this? I'm restoring the wpar from wpar mksysb not a mksysb from principal Lpar.

It is not clear if the error comes from the host LPAR or the workload partition and you will have to investigate this first. It might be that the WPAR `mksysb` is faulty and missing something vital. Depending on what it is you might be able to circumvent it (i.e. by using normal network login as Neo suggested) or not. You also can try to put some missing file into the WPARs filesystem (which is accessible from the hosting LPAR) but for this you will need to know what it is that is missing.

If the error comes from the LPARs side perhaps something for the `clogin` command to work is missing and you need to correct this on your LPAR.

In other words: there are a lot of things that could be responsible for this error and we have simply not enough information. Care to describe your environment and the error in some greater detail?

I hope this helps.

bakunin