Where can i find logs?

I’m trying to set up my new Jolla2026 and experienced some problems. Most were because i didn’t pay attention and i could solve them. but there is one atm that leaves me puzzled.

I managed to set up passwordless login for ssh via keys. it worked until it didn’t anymore. all of a sudden when i was about to copy data to the phone via rsync i was asked for a password again. i seriously can’t say what has caused this sudden change and now i’m trying to debug it. but i cannot find logs. journalctl says nothing about ssh or logins.

so if anybody could point me into a direction where i can find infos about logins and ssh within sailfish os i’d be very glad!

thanks in advance

jabgoe

You need to enable persistent logs:

3 Likes

Thanks, i had seen this before. but there i have the question: if nothing about logins and ssh shows up in the journalctl, what will be written about it into the persistent logs?

I understood that you didn’t get any logs at all.

You can increase the log level of sshd by increasing the LogLevel in the sshd config.

1 Like

I’d honestly start out logging on the client side first, unless you already have.
What does a ssh-copy-id do?

As others said, you should start with using -v or even -vvv cli options first.

About journalctl, if you don’t use it with devel-su you still might not see very much.

Also you probably should reboot your phone after enabling persistent logging.

just fyi: i managed to start the sshd service and the status there showed me my errors with ssh. i’m still missing something like an auth.log … but that might be for later.

thanks to all for their advice! :slight_smile:

This shouldn’t be necessary since SSH is socket-activated on SfOS.

but without starting it i couldn’t see any logs or reports of what was happening. as i mentionend i found nothing like the auth.log in sailfish os

It’s fine to do so for debugging.

Did you enable persistent logging? After that sth like devel-su journalctl should give you some insights. And yes, I understand you might need to temporarily start sshd manually to get there.