Hi, I Just finished upgrade from FBSD-8.1-R fresh system to FBSD-8.3-p2. once done, i created regular accounts, in wheel group. first all was okay, but suddenly i found my self blocked out, because i can't ssh as root, and i can't su either, when i su i get this: %su - Password: and it stuck in that state whitout givving me root shell #. any ideas how to solve this problem? the system is in the servers farm and i need to drive 3 hours each direction, so if there is remote solution i would appreciate it. %more /etc/group # $FreeBSD: src/etc/group,v 1.35.10.2.2.1 2012/03/03 06:15:13 kensmith Exp $ # wheel:*:0:root,sody . . . sody:*:1001: Thanks in advance, -- Sami Halabi Information Systems Engineer NMS Projects Expert FreeBSD SysAdmin Expert
Sami Halabi <sodynet1@gmail.com> wrote: > I Just finished upgrade from FBSD-8.1-R fresh system to FBSD-8.3-p2. > once done, i created regular accounts, in wheel group. > > first all was okay, but suddenly i found my self blocked out, because i > can't ssh as root, and i can't su either, when i su i get this: > %su - > Password: > > and it stuck in that state whitout givving me root shell #. What's the output from "id"? Does it include "0(wheel)"? And are you 100% sure that you know the correct root password? If you don't, you will have to drive to the machine and fix it from the console, I'm afraid. There's no other way, unless you discover a yet-unknown local root exploit. ;-) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Gesch?ftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M?n- chen, HRB 125758, Gesch?ftsf?hrer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd With Perl you can manipulate text, interact with programs, talk over networks, drive Web pages, perform arbitrary precision arithmetic, and write programs that look like Snoopy swearing.
Hmm.. I don't get shell to send any commands, its just go a newline and stuck there until i hit CTRL-C and go back. waiting for long time doesn't work either.... Sami On Sat, Jun 9, 2012 at 3:24 PM, David Wolfskill <david@catwhisker.org>wrote:> On Sat, Jun 09, 2012 at 03:21:29PM +0300, Sami Halabi wrote: > > Hi, > > > > %id > > uid=1001(sody) gid=1001(sody) groups=1001(sody),0(wheel) > > % > > > > i have another account also id 1002 - sody2, also in group wheel. > > i can ssh using user sody/sody2, however su doesn't work if i do: su > sody2, > > when i logged in with user sody. > > it seems that su is broken somehow.... > > > > any ideas? > > You might want to check the output of "id" after you've done that, then. > > > ... > > Peace, > david > -- > David H. Wolfskill david@catwhisker.org > Depriving a girl or boy of an opportunity for education is evil. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. >-- Sami Halabi Information Systems Engineer NMS Projects Expert FreeBSD SysAdmin Expert
%su - Password: load: 0.00 cmd: su 30588 [ttydcd] 0.91r 0.00u 0.00s 0% 2092k load: 0.00 cmd: su 30588 [ttydcd] 3.99r 0.00u 0.00s 0% 2092k load: 0.00 cmd: su 30588 [ttydcd] 4.81r 0.00u 0.00s 0% 2092k load: 0.00 cmd: su 30588 [ttydcd] 5.34r 0.00u 0.00s 0% 2092k load: 0.00 cmd: su 30588 [ttydcd] 5.72r 0.00u 0.00s 0% 2092k load: 0.00 cmd: su 30588 [ttydcd] 6.21r 0.00u 0.00s 0% 2092k load: 0.00 cmd: su 30588 [ttydcd] 6.67r 0.00u 0.00s 0% 2092k load: 0.00 cmd: su 30588 [ttydcd] 7.14r 0.00u 0.00s 0% 2092k load: 0.00 cmd: su 30588 [ttydcd] 7.53r 0.00u 0.00s 0% 2092k load: 0.00 cmd: su 30588 [ttydcd] 7.89r 0.00u 0.00s 0% 2092k load: 0.00 cmd: su 30588 [ttydcd] 8.14r 0.00u 0.00s 0% 2092k load: 0.00 cmd: su 30588 [ttydcd] 8.35r 0.00u 0.00s 0% 2092k load: 0.00 cmd: su 30588 [ttydcd] 8.53r 0.00u 0.00s 0% 2092k Thanks, Sami On Sat, Jun 9, 2012 at 3:36 PM, David Wolfskill <david@catwhisker.org>wrote:> On Sat, Jun 09, 2012 at 03:32:44PM +0300, Sami Halabi wrote: > > Hmm.. I don't get shell to send any commands, its just go a newline and > > stuck there until i hit CTRL-C and go back. > > waiting for long time doesn't work either.... > > ^T can sometimes provide clues as to the resource for which the process > is waiting. > > Peace, > david > -- > David H. Wolfskill david@catwhisker.org > Depriving a girl or boy of an opportunity for education is evil. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. >-- Sami Halabi Information Systems Engineer NMS Projects Expert FreeBSD SysAdmin Expert
On Sat, 09 Jun 2012 09:55:28 +0200, Sami Halabi <sodynet1@gmail.com> wrote:> Hi, > I Just finished upgrade from FBSD-8.1-R fresh system to FBSD-8.3-p2. > once done, i created regular accounts, in wheel group. > > first all was okay, but suddenly i found my self blocked out, because i > can't ssh as root, and i can't su either, when i su i get this: > %su - > Password: > > and it stuck in that state whitout givving me root shell #. > > any ideas how to solve this problem? the system is in the servers farm > and > i need to drive 3 hours each direction, so if there is remote solution i > would appreciate it. > > > %more /etc/group > # $FreeBSD: src/etc/group,v 1.35.10.2.2.1 2012/03/03 06:15:13 kensmith > Exp $ > # > wheel:*:0:root,sody > . > . > . > sody:*:1001: > > Thanks in advance, >It does not solve your problem now, but if it is a couple of hours away arrange some remote serial console access. Ronald.
Hi, /var/log/messages - no new logs %id sody2 uid=1002(sody2) gid=1002(sody2) groups=1002(sody2),0(wheel) % i did top on one session and followed it after I issued "su -" the only new process issued is "su" and it stays there even after I supply the password... This is really strange, it never happend to me in earlier releases.... even "su sody2" worked, but stopped after a while... Help me please... Sami On Sat, Jun 9, 2012 at 4:05 PM, David Wolfskill <david@catwhisker.org>wrote:> On Sat, Jun 09, 2012 at 03:47:07PM +0300, Sami Halabi wrote: > > %su - > > Password: > > load: 0.00 cmd: su 30588 [ttydcd] 0.91r 0.00u 0.00s 0% 2092k > > load: 0.00 cmd: su 30588 [ttydcd] 3.99r 0.00u 0.00s 0% 2092k > > ... > > load: 0.00 cmd: su 30588 [ttydcd] 8.35r 0.00u 0.00s 0% 2092k > > load: 0.00 cmd: su 30588 [ttydcd] 8.53r 0.00u 0.00s 0% 2092k > > ... > > Well, that wasn't as helpful as it might have been, then -- though it > does clearly indicate that the process isn't waiting on (say) keyboard > input. > > Have you checked messages (e.g., /var/log/messages)? > > Also, while you're logged in as your primary account, the output of "id > sody2" may be useful. > > The other thing that comes to mind is that it may be useful for you to > login (as "sody") twice (i.e., from 2 different xterms, or using a > "terminal mux" program such as tmux(1) (in ports; sysutils/tmux) so from > one session, you can try "su sody2" and from the other, you can issue > commands such as "top" or "ps lwt ttydcd" to see what processes are > running on the (apparently stalled) session. > > It's also possible that there's something wrong with the login shell > initialization scripts used for sody2. The above commands may help > identify that case. > > Peace, > david > -- > David H. Wolfskill david@catwhisker.org > Depriving a girl or boy of an opportunity for education is evil. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. >-- Sami Halabi Information Systems Engineer NMS Projects Expert FreeBSD SysAdmin Expert
On 6/9/2012 20:29, Sami Halabi wrote:> Hi, > /var/log/messages - no new logsSorry if this has been asked, anything in dmesg?
its the same as /var/log/messages On Sat, Jun 9, 2012 at 4:32 PM, Adam Strohl <adams-freebsd@ateamsystems.com>wrote:> On 6/9/2012 20:29, Sami Halabi wrote: > >> Hi, >> /var/log/messages - no new logs >> > > Sorry if this has been asked, anything in dmesg? >-- Sami Halabi Information Systems Engineer NMS Projects Expert FreeBSD SysAdmin Expert
But how do I solve the problem? On Sun, Jun 10, 2012 at 7:17 PM, Eugene Grosbein <egrosbein@rdtc.ru> wrote:> 10.06.2012 01:45, Sami Halabi ?????: > > Hi, > > > > %sysctl kern.console > > kern.console: ttyv0,dcons,/dcons,ttyv0,uart,ucom, > > > > %tail /var/log/messages > > Jun 7 19:54:35 vps16 kernel: Trying to mount root from ufs:/dev/da0s1a > > Jun 7 19:54:36 vps16 kernel: bge0: link state changed to UP > > Jun 7 20:18:04 vps16 kernel: ugen0.2: <vendor 0x09da> at usbus0 > > Jun 7 20:18:04 vps16 kernel: ukbd0: <vendor 0x09da USB Keyboard, class > > 0/0, rev 1.10/2.50, addr 2> on usbus0 > > Jun 7 20:18:04 vps16 kernel: kbd2 at ukbd0 > > Jun 7 20:18:05 vps16 kernel: uhid0: <vendor 0x09da USB Keyboard, class > > 0/0, rev 1.10/2.50, addr 2> on usbus0 > > Jun 7 20:19:37 vps16 login: ROOT LOGIN (root) ON ttyv1 > > Jun 7 20:21:19 vps16 kernel: ugen0.2: <vendor 0x09da> at usbus0 > > (disconnected) > > Jun 7 20:21:19 vps16 kernel: ukbd0: at uhub0, port 1, addr 2 > (disconnected) > > Jun 7 20:21:19 vps16 kernel: uhid0: at uhub0, port 1, addr 2 > (disconnected) > > % > > > > the system was loaded with keyboard and disconnected later if i > understand > > the logs... > > > > New ideas are appreciated, and thanks in advance, > > Sami > > I still believe your problem concerns serial console: > su writes to it, indirectly - it notes root login through syslogd > that writes the message to /dev/console and locks in your case, locking su. > > Eugene Grosbein >-- Sami Halabi Information Systems Engineer NMS Projects Expert FreeBSD SysAdmin Expert
Anything in the /var/log files give you a clue? On Jun 10, 2012 10:29 AM, "Sami Halabi" <sodynet1@gmail.com> wrote:> But how do I solve the problem? > > On Sun, Jun 10, 2012 at 7:17 PM, Eugene Grosbein <egrosbein@rdtc.ru> > wrote: > > > 10.06.2012 01:45, Sami Halabi ?????: > > > Hi, > > > > > > %sysctl kern.console > > > kern.console: ttyv0,dcons,/dcons,ttyv0,uart,ucom, > > > > > > %tail /var/log/messages > > > Jun 7 19:54:35 vps16 kernel: Trying to mount root from ufs:/dev/da0s1a > > > Jun 7 19:54:36 vps16 kernel: bge0: link state changed to UP > > > Jun 7 20:18:04 vps16 kernel: ugen0.2: <vendor 0x09da> at usbus0 > > > Jun 7 20:18:04 vps16 kernel: ukbd0: <vendor 0x09da USB Keyboard, class > > > 0/0, rev 1.10/2.50, addr 2> on usbus0 > > > Jun 7 20:18:04 vps16 kernel: kbd2 at ukbd0 > > > Jun 7 20:18:05 vps16 kernel: uhid0: <vendor 0x09da USB Keyboard, class > > > 0/0, rev 1.10/2.50, addr 2> on usbus0 > > > Jun 7 20:19:37 vps16 login: ROOT LOGIN (root) ON ttyv1 > > > Jun 7 20:21:19 vps16 kernel: ugen0.2: <vendor 0x09da> at usbus0 > > > (disconnected) > > > Jun 7 20:21:19 vps16 kernel: ukbd0: at uhub0, port 1, addr 2 > > (disconnected) > > > Jun 7 20:21:19 vps16 kernel: uhid0: at uhub0, port 1, addr 2 > > (disconnected) > > > % > > > > > > the system was loaded with keyboard and disconnected later if i > > understand > > > the logs... > > > > > > New ideas are appreciated, and thanks in advance, > > > Sami > > > > I still believe your problem concerns serial console: > > su writes to it, indirectly - it notes root login through syslogd > > that writes the message to /dev/console and locks in your case, locking > su. > > > > Eugene Grosbein > > > > > > -- > Sami Halabi > Information Systems Engineer > NMS Projects Expert > FreeBSD SysAdmin Expert > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >
On 6/9/12 9:55 AM, Sami Halabi wrote:> Hi, > I Just finished upgrade from FBSD-8.1-R fresh system to FBSD-8.3-p2. > once done, i created regular accounts, in wheel group. > > first all was okay, but suddenly i found my self blocked out, because i > can't ssh as root, and i can't su either, when i su i get this: > %su - > Password: > > and it stuck in that state whitout givving me root shell #. > > any ideas how to solve this problem? the system is in the servers farm and > i need to drive 3 hours each direction, so if there is remote solution i > would appreciate it. > > > %more /etc/group > # $FreeBSD: src/etc/group,v 1.35.10.2.2.1 2012/03/03 06:15:13 kensmith Exp $ > # > wheel:*:0:root,sody > . > . > . > sody:*:1001: > > Thanks in advance, >Ok so, I've read all the replies so far and I'm a bit perplexed. Sami, before you drive 3 hours to and 3 hours fro, kindly log in as sody over SSH, then try "login" to connect *locally* as the root user. If that works, you'll at least have recovered root access and will be able to install sudo, which should help you a great deal. Of course there's still the matter of finding what's wrong with your machine, afterwards.