Opening shell instantly tries to change directory

[eseanq]

I feel like this is a easy fix but for the life of me cannot figure out what changed or how to fix it, but when I open shell or an SSH session within a few seconds the active directory tries to be changed.

How do I fix this?

 

[winnielinnie]

Have you made any manual modification's to the root account's shell/config files? (Such as the .bashrc file.)

* This assumes that bash is the default shell for SCALE. I am not familiar with SCALE.

 

[eseanq]

I have not done that, no. And currently shell for the root account is set to zsh

 

[Patrick M. Hausen]

If you hit ENTER pwd ENTER in rapid succession, what is shown? I suspect nobody is trying to change your current directory but some background process running as root is spamming its error message to your SSH session.

 

[eseanq]

If you hit ENTER pwd ENTER in rapid succession, what is shown? I suspect nobody is trying to change your current directory but some background process running as root is spamming its error message to your SSH session.

Not sure if by coincidence but it seems to briefly stop, eventually coming back though.

 

[Patrick M. Hausen]

And the output of the pwd command is /root - your current directory. So my suspicion is probably correct. [1]

On my SCALE system the missing directory looks like this - it points to the system dataset:

Code:

lrwxrwxrwx  1 root 55 Jan 24 19:14 netdata -> /var/db/system/netdata-5a0a2a47cd884dbcbe527966286bfc29/

What you could try to do is assign the system dataset to a different pool from the one it is currently assigned to, and then back again. Perhaps that fixes things.

[1] Part of the reporting subsystem (probably) tries to change into that directory, fails because the directory is missing (probably) and pesters root about that.

 

[eseanq]

Hmm. I'll look into doing that.
The strange thing though is that the directory does exist.

Is it a permission thing?

 

[Patrick M. Hausen]

No idea, sorry.

 

[anodos]

A process lacking ability to chdir into a directory may also mean a permissions issue on a parent path. E.g. `/var/`, `/var/db`, or `/var/db/system`. In this case execute for "other" would be required on each path component.