Since a couple days I get the above message if I try to connect via ssh to my vero2.
Since ssh server can be installed via myosmc appstore I figured i’ll report this issue here.
A reboot temporarely resolves the issue, I don’t know why or when this error comes up.
After a restart I could grab the logs:
http://paste.osmc.io/iyeguhuqil
Which OS are you using?
Which client?
Can you take a screenshot of the application.
A reboot of the Vero or your computer?
Not familiar with this application.
Do you have the problem on PC with Putty?
right now, no. Have to try it with putty after I get the message on juicessh again.
That would be a good test. Also make sure you have the latest Putty (some authentication has been dropped recently)
Hello, I wanted to pick this error up again. It’s not happening very frequently so if most of the time Ijust reboot vero2. Now I fired up my pc an putty gives this output:
What have you installed on the Vero 2? Not allocating a pseudo terminal is usually done for non privileged users to run a single command or because there are not enough resources to allocate one
If a reboot solves the issue it may be that your system is running low on memory
Memory should be ok
The thing with unprivileged user running a single command seems more interessting:
I have an app with tasker plugin that does this.
Tasker app lets me create a shortcut to a task on the homescreen. The task in this case is to rebbot vero2 with the help of the ssh plugin.
Do you think this ssh app/plugin somehow messes with ssh server? Maybe everytime it allocates memory but never releases it or so? …lol I feel thrown back to the few programming semesters I attended and the belonging exams I terribly failed
If the SSH plugin is rebooting your system, then you won’t be losing memory.
I think your problem may stem in that you’re logging in as the root user, and perhaps how you enabled root access. I would recommend just having the standard ‘osmc’ user.
If I recall right, I just changed permitt root login to yes in the ssh conf file. And in the beginning this worked flawlessly.
Do you have problems logging in as the OSMC user?
Haven’t tried since I want to login as root.
Meanwhile I did a reboot, so now it works anyway.
I don’t really know how to reproduce this either.
You can elevate to root, by logging in as the osmc user and running
sudo -s
Every single login, right?
Or does this survive more than one session?
Running as root constantly has negative ramifications
Every login, yes, unless you added it to your profile or bashrc
Ok, will test if running as root is actually the cause. Not sure if the plugin will still work, guess adding a sudo to the commands should work.