**** BEGIN LOGGING AT Sun Sep 24 02:59:56 2006 Sep 24 11:08:04 something strange has happened to my slug Sep 24 11:08:10 suddnly i cannot ssh into it Sep 24 11:08:13 i can telnet in Sep 24 11:08:16 but not ssh Sep 24 11:08:49 maybe sshd is not running? Sep 24 11:09:03 it was last night when i went to bed :-s Sep 24 11:09:17 ps aux | grep ssh Sep 24 11:09:17 root 477 0.0 3.3 3200 1036 ? Ss Sep23 0:24 /opt/sbin/sshd Sep 24 11:09:17 ed 2196 0.0 1.4 2668 448 ttyp0 SN+ 12:15 0:00 grep ssh Sep 24 11:12:05 does that make sense? Sep 24 11:12:17 when i try to use putty to access the slug i get the following error message: Sep 24 11:12:37 "server unexpectedly closed network connection" Sep 24 11:12:45 but i can telnet in fine Sep 24 11:14:18 and from linux command line i get: Sep 24 11:14:34 ssh_exchange_identification: Connection closed by remote host Sep 24 11:19:11 anyone know why? Sep 24 11:19:37 is yahoogroups.com mailservice down? Ive posted a message to nslu2-general@yahoogroups.com yesterday and nohting is happend Sep 24 11:24:02 ok Sep 24 11:24:08 something bad has happened Sep 24 11:24:12 telnet in Sep 24 11:24:17 just wanted to cd to a directory Sep 24 11:24:22 and i got this: Sep 24 11:24:34 WARNING: terminal is not fully functional Sep 24 11:24:43 openssh is a directory Sep 24 11:24:46 well...that's new Sep 24 11:24:54 i got that when i tried to "less openssh" Sep 24 11:25:00 after being told i couldnt cd to it Sep 24 11:25:04 (but i'm logged in as root) Sep 24 11:25:37 it's normal for less to tell you that the file you're trying to view is a directory Sep 24 11:25:42 if it in fact is Sep 24 11:26:04 or hmm, maybe varies between versions Sep 24 11:26:18 my less on another computer shows the dir listing Sep 24 11:26:37 yeah Sep 24 11:26:38 but the busybox less may not handle such stuff Sep 24 11:26:44 i'd expect it to tell me that it was a directory too Sep 24 11:26:45 however Sep 24 11:26:55 it told me that my terminal was not fully fuynctional Sep 24 11:26:58 and i couldn't cd to it Sep 24 11:27:17 I don't know about the not-being-functional part, never had such a message Sep 24 11:27:49 though the only time I've ever really used telnet to login to a box has been with the slug, when installing Sep 24 11:27:55 same Sep 24 11:28:00 but it won't let me ssh in :-s Sep 24 11:28:55 i'm getting an annoying feeling i'm going to have to reset the slug or something Sep 24 11:29:09 about the warning, you could try setting TERM=linux Sep 24 11:29:20 export TERM=linux Sep 24 11:29:21 I mean Sep 24 11:29:51 well Sep 24 11:29:54 that seems to have worked Sep 24 12:00:08 well Sep 24 12:00:17 i've worked out what the problem is with getting ssh access Sep 24 12:00:34 (whilst my isp was messing me around by kicking me offline) Sep 24 12:00:57 the file permissions are not correct Sep 24 12:01:05 i have them too liberal (0777) on the key files Sep 24 12:01:10 which obviously is as insecure as possible Sep 24 12:01:15 but i'm not sure what i should change them too Sep 24 12:01:20 0666? Sep 24 12:01:29 but that doesn't seem right actually Sep 24 12:01:57 0744? Sep 24 12:04:23 try 0700 Sep 24 12:04:42 or, which key files? Sep 24 12:05:22 ok, 0700 works Sep 24 12:05:34 but now when starting the ssh service i get this error: Sep 24 12:05:48 "/var/empty must be owned by root and not group or world writable" Sep 24 12:05:55 but i can't remember the chown syntax Sep 24 12:06:03 chown root file Sep 24 12:06:20 or more generally: chown user:group file Sep 24 12:07:01 i need to do a chmod on it now ofc Sep 24 12:07:05 but i dont know what perms to use Sep 24 12:07:08 700 again? Sep 24 12:07:21 or would others need read access? Sep 24 12:07:21 well, anything that doesn't allow group and world to write on it Sep 24 12:07:31 probably not Sep 24 12:07:34 so 733? Sep 24 12:07:37 I think 700 is fine Sep 24 12:08:15 ok Sep 24 12:08:16 thanks Sep 24 12:08:17 733 is probably just as fine Sep 24 12:08:22 ssh access is back up and running :-D Sep 24 12:08:32 however Sep 24 12:08:43 for some reason, and this started yesterday Sep 24 12:08:48 i seem to have lost my bash shell Sep 24 12:08:51 it's still installed Sep 24 12:09:09 i can start it by typing "bash" Sep 24 12:14:05 so Sep 24 12:14:19 i presume i need to edit my /etc/passwd file to include /bin/bash as my shell Sep 24 12:14:20 ? Sep 24 12:44:24 is there a DEBIANSLUG dev here? Sep 24 12:45:40 i think there is a separate chan for that Sep 24 12:45:52 #nslu2-linux or #nslu2-debian Sep 24 12:45:54 something like tat Sep 24 12:45:58 don't know the chan-names though Sep 24 12:46:12 check on the nslu2 website and search for irc chans Sep 24 12:47:38 ok i tryit there Sep 24 12:48:16 dose there is a network speed difference between OpenDebianSlug and DebianSlug? Sep 24 14:07:29 i can't "su" on my slug Sep 24 14:07:32 i get: Sep 24 14:07:42 su: cannot set groups: Operation not permitted Sep 24 14:30:37 :-( Sep 24 14:30:42 nobody have any ideas? Sep 24 14:43:47 Jassovissovik: have you googled the message? That would likely be a general Linux issue, and not likely slug specific. Sounds like maybe something or somebody edited the password or groups file? Sep 24 14:52:35 yeah Sep 24 14:52:42 but i dont know hot to translate into slug stuff Sep 24 14:52:54 as i'm not good at linux troubleshooting Sep 24 14:57:22 i think it's to do with permissions of folders like /etc/passwd Sep 24 14:57:30 but i know they work oddly on the slug Sep 24 15:05:20 i edited /etc/passwd ages ago i think Sep 24 15:32:35 Sounds more like you lost the setuid bits on the su program. Sep 24 15:33:50 where is your su program: /bin/su, /opt/bin/su? Sep 24 15:34:13 What user id are you logged in as when you try to perform the su? Sep 24 15:36:53 when logged in via telnet as root i can "su" to root Sep 24 15:37:12 i have disabled ssh access to log in as root Sep 24 15:37:15 so i can't say about that Sep 24 15:37:49 mwester - both of those Sep 24 15:39:22 Try explicitly performing the "su" operation using each of the two exectuables; this will identify which one (or both) is having trouble. just type "/bin/su" or "/opt/bin/su" instead of su. What happens? Sep 24 15:40:27 ok Sep 24 15:40:42 /opt/bin/su i get the same errors Sep 24 15:40:57 /bin/su i get info about TinyLogin Sep 24 15:41:37 and "currently defined functions" are tinylogin, getting, login, passwd Sep 24 15:42:05 Ok, try /bin/su root then Sep 24 15:42:24 i get the same tinylogin spiel Sep 24 15:43:54 Ok, anyway: what's the output from "ls -la /opt/bin/su" Sep 24 15:44:50 -rwxrwxrwx 1 root root 16620 Jun 17 02:31 /opt/bin/su Sep 24 15:45:33 http://pastebin.com/793423 Sep 24 15:45:35 You lost the set-uid bit for /opt/bin/su somehow -- perhaps it got copied at some point, or something mishandled the executable. Odd. But easy to fix. Sep 24 15:45:55 yay - easy to fix - my favourite words Sep 24 15:46:01 how? :-) Sep 24 15:47:14 as root, type: chmod u+s /opt/bin/su Sep 24 15:48:10 and that's it? Sep 24 15:48:16 u=users s=?? Sep 24 15:48:36 it worked btw :-D Sep 24 15:58:28 so mwester - i should have no problems now? Sep 24 15:58:33 i can change user passwords etc? Sep 24 16:02:16 The "su" should work fine. If you didn't backup/restore /opt or /opt/bin, or copy those directories about, then I can only assume that su got installed incorrectly somehow. Sep 24 20:14:31 Good morning @all Sep 24 21:49:49 any debianslug users alive? Sep 24 21:54:40 barnseenio: yes sir Sep 24 21:55:03 barnseenio: though my usefulness will be inversely proportional to my beer consumption Sep 24 21:57:30 so hurry up with the Q ;) Sep 24 22:06:32 llol Sep 24 22:06:48 i have mt-daapd going Sep 24 22:07:07 but im trying to get one of the nightlies built (or use an ipk) as i want to try out flac support Sep 24 22:07:20 q1) can i use a ipk on debianslug Sep 24 22:16:29 NSUL2:~# dpkg -i --force-architecture mt-daapd_svn-1376-1_armeb.ipk Sep 24 22:16:29 dpkg-deb: `mt-daapd_svn-1376-1_armeb.ipk' is not a debian format archive **** ENDING LOGGING AT Mon Sep 25 02:59:56 2006