02-02-2026 11:20 PM
Hello,
I have a FPR-4112-K9 firewall cluster with software version 2.16(1.147). It runs an ASA cluster with software version 7.22(1).
Since updating to the above versions two weeks ago, I get the following messages when logging in with ssh:
Firepower:
%AUTH-3-SYSTEM_MSG: error: Unable to load host key: /isan/etc/ssh_host_ecdsa_key - sshd[31426] %DAEMON-3-SYSTEM_MSG: error: lastlog_openseek: couldn't stat /var/log/lastlog: No such file or directory - sshd[31467]
ASA:
%ASA-3-199015: 3 February 07:22:43 sshd: PAM unable to resolve symbol: pam_sm_setcred %ASA-3-199015: 3 February 07:22:50 sshd: pam_lastlog(sshd:session): unable to open /var/log/btmp: No such file or directory
What can I do about this?
On my data centre switches (Nexus9000), I was able to start bash and create /var/log/btmp. That doesn't work here.
Many thanks in advance.
Solved! Go to Solution.
02-03-2026 03:54 AM
You can remove sending logs to the syslog server -
no logging message 199015
lower the severity.
logging message 199015 level X
=====️ Preenayamo Vasudevam ️=====
***** Rate All Helpful Responses *****
02-02-2026 11:54 PM
On FXOS, you may need to regenerate the FXOS SSH keys. This forces the system to re-create the missing file pointers.
check guide :
ASA cluster with software version 7.22(1).
I'm taking this as ASA code 9.22; I may try to recreate the SSH key from the console and test
example :
no ssh version 2
ssh version 2
crypto key generate rsa modulus 2048
=====️ Preenayamo Vasudevam ️=====
***** Rate All Helpful Responses *****
02-03-2026 02:07 AM
Oh yes, ASA code 9.22(2)20 is installed.
But what happens to my current SSH connection? I only have remote access.
02-03-2026 03:11 AM
It's safe to do from the console. If you already have an SSH connection, what is the issue? Is that only the Logs that are the issue?
You can ignore the log discriminator to report on the console.
=====️ Preenayamo Vasudevam ️=====
***** Rate All Helpful Responses *****
02-03-2026 03:32 AM
These are only messages that come to the monitoring server. The SSH connections work without any problems.
02-03-2026 03:54 AM
You can remove sending logs to the syslog server -
no logging message 199015
lower the severity.
logging message 199015 level X
=====️ Preenayamo Vasudevam ️=====
***** Rate All Helpful Responses *****
02-03-2026 04:16 AM
Thanks, the level is now Notification and that's fine. 😊
02-03-2026 12:12 AM
- @renateneike FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwc17197
M.
02-03-2026 02:02 AM
Does this workaround affect the current ssh session? I only have remote access with ssh.
02-03-2026 03:39 AM
- @renateneike The workaround does not affect the current SSH session ,
M.
02-03-2026 10:40 PM
Thank you very much for your help. Everything has worked well so far.
Now I have this message:
%DAEMON-3-SYSTEM_MSG: error: lastlog_openseek: couldn't stat /var/log/lastlog: No such file or directory - sshd[31467]How can I get rid of it? Can I create /var/log/lastlog?
02-03-2026 10:52 PM
- @renateneike Get a shell on your device and issue these commands :
sudo touch /var/log/lastlog
chmod 600 /var/log/lastlog
M.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide