Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Matt_Taber
Contributor
Jump to solution

SCP to R81.20 after JHF 41 installation

Good morning,

We upgraded our MGMT servers (3) to R81.20 JHF41 yesterday, smooth process.

After the upgrade, however, we cannot scp TO a host that has JHF41 installed, get a weird message about flags that weren't even entered:

 

Working to R81.20 JHF26 host:

[Expert@mercury:0]# scp -p 20231213_cert_list.txt admin@192.168.2.251:
This system is for authorized use only.
admin@192.168.2.251's password:
20231213_cert_list.txt 100% 9082 9.3MB/s 00:00

Non working to R81.20 JHF41 host:

[Expert@mercury:0]# scp -p 20231213_cert_list.txt admin@192.168.2.6:
This system is for authorized use only.
admin@192.168.2.6's password:
CLINFR0329 Invalid command:'scp -p -t .'.

Not sure where the '-t' flag is coming from, I didn't type it. 🙂  

Ran it with -v:

debug1: Sending command: scp -v -p -t .
CLINFR0329 Invalid command:'scp -v -p -t .'.

Ran it with -v to the JHF26 host and it shows that it was also sending -v -p -t, so not sure what the issue is on JHF 41.

I ran a diff on /etc/ssh/sshd_config between the 2 JHFs, they're the same.   /usr/sbin/sshd is the same between the 2 takes.

 

Thanks for reading

0 Kudos
1 Solution

Accepted Solutions
Matt_Taber
Contributor

Disregard, I didn't realize that the shell was now /etc/cli.sh rather than /bin/bash for user 'admin'.    Usually when the shell changes after an upgrade, it flips it back to clish.  I've never seen it set it to cli.sh

 

Changed the shell to bash and all is well.     chsh --shell /bin/bash admin

 

 

View solution in original post

0 Kudos
3 Replies
Matt_Taber
Contributor

Also noting that restarting sshd on a JHF41 host did not make any difference.   

0 Kudos
Matt_Taber
Contributor

Disregard, I didn't realize that the shell was now /etc/cli.sh rather than /bin/bash for user 'admin'.    Usually when the shell changes after an upgrade, it flips it back to clish.  I've never seen it set it to cli.sh

 

Changed the shell to bash and all is well.     chsh --shell /bin/bash admin

 

 

0 Kudos
Bob_Zimmerman
Authority
Authority

Note that chsh is not a supported way to change the user's login shell. Changes made outside of clish do not update the clish config, and clish sometimes overwrites the external files you changed with versions which it generates based on its config. To change a user's login shell, you must use 'set user admin shell /bin/bash' in clish and you must run 'save config' afterwards.

I can't stand clish, and this is one of the things I most dislike about it.

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    Tue 23 Apr 2024 @ 11:00 AM (EDT)

    East US: What's New in R82

    Thu 25 Apr 2024 @ 11:00 AM (SGT)

    APAC: CPX 2024 Recap

    Tue 30 Apr 2024 @ 03:00 PM (CDT)

    EMEA: CPX 2024 Recap

    Thu 02 May 2024 @ 11:00 AM (SGT)

    APAC: What's new in R82

    Tue 23 Apr 2024 @ 11:00 AM (EDT)

    East US: What's New in R82

    Thu 25 Apr 2024 @ 11:00 AM (SGT)

    APAC: CPX 2024 Recap

    Tue 30 Apr 2024 @ 03:00 PM (CDT)

    EMEA: CPX 2024 Recap

    Thu 02 May 2024 @ 11:00 AM (SGT)

    APAC: What's new in R82
    CheckMates Events