New installation does not work

[Gordon]

Awesome!

As for upgrading, I think that is a known issue. Solution if I remember correctly is to enter `change_distribution elvin` at the console and then do a `apt-get update`. It's also really not a bad idea to run those updates, as this will also upgrade the older Squeezebox Server to Logitech Media Server.

[BadTicket]

OK, I tried it but now I can't come on my B3 again with SHH. Here what I get when I try "ssh 10.0.1.19"

The authenticity of host '10.0.1.19 (10.0.1.19)' can't be established.
RSA key fingerprint is 51:af:31:ec:47:d6:71:74:23:14:12:e6:e1:fc:9e:12.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.0.1.19' (RSA) to the list of known hosts.
Password:

And nether "excito" or my admin password is accepted, I only get:

Permission denied (publickey,keyboard-interactive).

So I try "ssh 10.0.1.19 -l root" but also here no success

[Gordon]

This is by design. You need to create a user first through the regular web interface and allow that user shell access. Then you ssh into the B3 as that user. To become root you type `su` and enter the password `excito`.

[BadTicket]

Doesn't work... I can login to a user, use "su", but when I use "excito" or the password of the user I only get:

su: Sorry

Then I where I start bevor use ssh

[Gordon]

That should not happen.

Can you post result from

Code: Select all

grep -v "^#\|^$" /etc/pam.d/su

Also, do you see entries that correspond to you trying to become root in the system's auth log? Use webadmin to view this: menu `settings`, then `logs`

[BadTicket]

Here what I get with "grep -v "^#\|^$" /etc/pam.d/su":

auth sufficient pam_rootok.so
auth required pam_opendirectory.so
account required pam_group.so no_warn group=admin,wheel ruser root_only fail_safe
account required pam_opendirectory.so no_check_shell
password required pam_opendirectory.so
session required pam_launchd.so

The other I don't unterstand, what do you mean with "Webadmin"? Is that a software?

[Gordon]

http://b3/admin

But that listing already shows what's wrong. I ran a quick check on the payload file and I think you should be able to ssh in as user admin, then su to become root.

[BadTicket]

Definitely not. I can login in the Webadmin (as I know now what it is ) with "admin" and the password, but not with "ssh 10.0.1.19 -l admin". I can login with the user "test" and "ssh 10.0.1.19 -l test" and that password, but not with admin. It's also not possible to login with "ssh 10.0.1.19" and all used passwords, and also not with "ssh 10.0.1.19 -l root".
So since I have made the user "test" I can't login with what it works before. Really strange

[johannes]

not sure if this helps, but did you really re-install the machine, or just managed to boot it? It sounds like your root password is changed to something non-standard. Could this have happened on your old installation, for some reason?

(Also, direct ssh using admin or root is not allowed, by design. You need to enter using your test user, and then su to become root, so this is correct behaviour).

[BadTicket]

It must be a re-install, because the systems needs over half an our for formatting the disk before it starts the install process. And now I have System 2.3.1.1 on it which seems an order system to be, before I normally get every new update when there is one out.

I just tried it again, and still can login as "test" with "ssh 10.0.1.19 -l test", but when I use "su" I only get "su: Sorry". I also tried "su -l root" and "su -l admin" and always be ask for a password, but when I use it I only get "su: Sorry".
Is there an other possibility to change to root?

[Gordon]

It sounds like your root password is changed to something non-standard.

That would lead to an authentication failure. In this case it responds 'Sorry' and this is caused by pam being configured only to allow su to members of group admin and wheel. The problem is that the B3 user management interface does not provide a way to create such a user.

Can you verify that user admin is configured for shell access? Otherwise we'll need the rescue USB stick again to hack into the box and make the appropriate changes.

[BadTicket]

No, "admin" don't had a shell-access, even "test" not. As I can't change that at "admin" I changed it at "test" and then "su" is working. I scroll back what we want to do (update) and use "change_distribution elvin" and then "apt-get update" which gave me:

Hole:1 http://b3.update.excito.org elvin Release.gpg [198 B]
Ign http://b3.update.excito.org/ elvin/main Translation-de
Ign http://b3.update.excito.org/ elvin/main Translation-e
Hole:2 http://b3.update.excito.org upstream_squeeze Release.gpg [198 B]
Ign http://b3.update.excito.org/ upstream_squeeze/main Translation-de
Ign http://b3.update.excito.org/ upstream_squeeze/main Translation-en
Hole:3 http://b3.update.excito.org elvin Release [4'473 B]
Hole:4 http://b3.update.excito.org upstream_squeeze Release [9'827 B]
Ign http://b3.update.excito.org elvin/main armel Packages
Hole:5 http://b3.update.excito.org elvin/main armel Packages [62.2 kB]
Ign http://b3.update.excito.org upstream_squeeze/main armel Packages
Hole:6 http://b3.update.excito.org upstream_squeeze/main armel Packages [798 kB]
Es wurden 875 kB in 4 s geholt (211 kB/s)
Paketlisten werden gelesen... Fertig

As I don't see any changes, I restart by B3 but still have system 2.3.1.1

[Gordon]

You still need to run the updates. Either click upgrade in the web management interface or (as root) run `apt-get upgrade`

[BadTicket]

Wow, a lot of things that are running there... I used it as root, have to answer a question from something that is called "debian" or so (changing root things, I answered yes because it was recommended) and from samba (I choose stay at the used version) and after thousands of rows I can't find the Webadmin site I can use the Squeezebox Server (which is still the old version) and see the datas in the finder but nether the IP or http://b3/admin shows the web interface. Where it is gone???

[BadTicket]

I switch the B3 now of and then on again, but still now access with the web interface