LLRnet servers for NPLB

[gd_barnes]

Originally Posted by mdettweiler

Okay, it's 10:30 EST right now--I'll go ahead and reboot the machine. As for it needing to be connected to a monitor: hmm, I think I may have been getting confused about that. You see, during the "testing phase" for my quad, I had it sitting right behind my dualcore, and was live-swapping the monitor, keyboard, and mouse connections when I wanted to have a console on one or the other. Usually when either of the machines was unattended, I would leave the stuff plugged in to my dualcore, but then if the quad rebooted unexpectedly (it did that from time to time because of a since-fixed hard drive cable issue), when I plugged the stuff back into it I would find it at 640x480 resolution and the keyboard and mouse wouldn't work.

Then again, maybe there's a difference in the fact that my quad runs Windows instead of Linux like yours do. Not to mention that, if memory serves, you have a keyboard and mouse plugged in to all of your quads even when they don't have a monitor on them, correct?

Anyway, I'll go reboot the server shortly...

I'm just now back on. I have connected the monitor to it and I just now saw that you are shutting it down. (Kind of spooky. lol)

I'm confused. I generally have a monitor, keyboard and mouse connected to all machines but they go through 3 KVM switching boxes; 4 per box except there are only 2 of them on the 3rd box (since there are 10 machines). The server is on the box with 2 of them. In other words, I have 3 sets of monitors, keyboards, and mice; that's all that I need. It just so happens that at this moment I have one monitor and one keyboard upstairs (I have spare mice, no spare monitors/keyboards) so in order to have crunchford with a monitor and keyboard connected, I had to move them over from one of the other KVM switch boxes.

Hurry up and log in; will ya! lol I'm watching you work right now! It's been sitting at the username screen for 3-4 mins. now. What are you waiting on?


Gary

[gd_barnes]

It's been 20 mins. now sitting at the log on screen. Do you want me to log on for you or are you having problems such that you need to wait?

[mdettweiler]

Originally Posted by gd_barnes

I'm just now back on. I have connected the monitor to it and I just now saw that you are shutting it down. (Kind of spooky. lol)

I'm confused. I generally have a monitor, keyboard and mouse connected to all machines but they go through 3 KVM switching boxes; 4 per box except there are only 2 of them on the 3rd box (since there are 10 machines). The server is on the box with 2 of them. In other words, I have 3 sets of monitors, keyboards, and mice; that's all that I need. It just so happens that at this moment I have one monitor and one keyboard upstairs (I have spare mice, no spare monitors/keyboards) so in order to have crunchford with a monitor and keyboard connected, I had to move them over from one of the other KVM switch boxes.

Hurry up and log in; will ya! lol I'm watching you work right now! It's been sitting at the username screen for 3-4 mins. now. What are you waiting on?


Gary

First of all: The server is now restarted. All clients should now automatically catch up on anything they were behind on.

@Gary: Ah, I see, I didn't know you had a KVM switch. (I was sort of doing a "poor man's KVM switch" with my quad and dualcore, hence the problems that otherwise wouldn't show up.) In that case, no problem at all--I guess the monitor wasn't necessary after all.

As for why you didn't see me log in: that's because of the multi-user nature of Linux. Even though I've already logged in (though, in all fairness, I was distracted for about ~8 minutes between the time when I rebooted the server and when I logged on, so at the time you posted your message I indeed hadn't logged on), you still will only see the login screen. That's since Linux starts separate "sessions" for SSH and VNC, as if you had logged in twice, only one of your logged-in sessions is tied to your physical monitor/keyboard/mouse; another to the VNC session; and yet another to the SSH session (i.e. the command line remote control that I use a lot. It's set up to "tunnel" the VNC connection through the SSH thing so that the VNC connection is encrypted.) That is why you don't see the terminal window with all the LLRnet server stuff in it on your main desktop--because it's not on your main session, it's only on the VNC session. (Thus, if you VNC in, *boom*! The LLRnet server terminal window will suddenly become visible. )

Hope this, combined with what I said in my PM that I sent you a minute ago, explains things a bit.

Max

[gd_barnes]

Originally Posted by mdettweiler

First of all: The server is now restarted. All clients should now automatically catch up on anything they were behind on.

@Gary: Ah, I see, I didn't know you had a KVM switch. (I was sort of doing a "poor man's KVM switch" with my quad and dualcore, hence the problems that otherwise wouldn't show up.) In that case, no problem at all--I guess the monitor wasn't necessary after all.

As for why you didn't see me log in: that's because of the multi-user nature of Linux. Even though I've already logged in (though, in all fairness, I was distracted for about ~8 minutes between the time when I rebooted the server and when I logged on, so at the time you posted your message I indeed hadn't logged on), you still will only see the login screen. That's since Linux starts separate "sessions" for SSH and VNC, as if you had logged in twice, only one of your logged-in sessions is tied to your physical monitor/keyboard/mouse; another to the VNC session; and yet another to the SSH session (i.e. the command line remote control that I use a lot. It's set up to "tunnel" the VNC connection through the SSH thing so that the VNC connection is encrypted.) That is why you don't see the terminal window with all the LLRnet server stuff in it on your main desktop--because it's not on your main session, it's only on the VNC session. (Thus, if you VNC in, *boom*! The LLRnet server terminal window will suddenly become visible. )

Hope this, combined with what I said in my PM that I sent you a minute ago, explains things a bit.

Max

I'm confused. A lot of Greek here. I take it I could log on remotely and see my desktop but not locally? But I don't like that. I want to be able to see my desktop while I'm sitting here in the basement. I like to check the temperature from time to time and make sure that all 4 cores are running LLRnet.

Have you started LLRnet again on all 4 cores for me? I assume so but can't tell unless I run upstairs and log on remotely. Regardless, can you make it to where I can see it while sitting in front of the machine? This was never an issue before. I don't want to have to be upstairs on my laptop trying to see my downstairs machine remotely. The response time is much slower.

Perhaps I'm not understanding what I need to be doing sitting in front of my machine? Can I just try logging on like I would normally?

Edit: Me doing a "poor man's KVM switch" with 10 machines??? lol Do you realize how much headache that would be plugging and unplugging monitors, keyboards, and mice among 10 machines? That ain't gonna be happening! lol


Gary

[mdettweiler]

Originally Posted by gd_barnes

I'm confused. A lot of Greek here. I take it I could log on remotely and see my desktop but not locally? But I don't like that. I want to be able to see my desktop while I'm sitting here in the basement. I like to check the temperature from time to time and make sure that all 4 cores are running LLRnet.

Have you started LLRnet again on all 4 cores for me? I assume so but can't tell unless I run upstairs and log on remotely. Regardless, can you make it to where I can see it while sitting in front of the machine? This was never an issue before. I don't want to have to be upstairs on my laptop trying to see my downstairs machine remotely. The response time is much slower.

Perhaps I'm not understanding what I need to be doing sitting in front of my machine? Can I just try logging on like I would normally?


Gary

Okay, here. You *can* still see your desktop locally--just simply enter your password and log on as if you had started the machine. What's making this all confusing is the fact that in Linux, one user can have multiple, separate sessions logged on all at once. Hence I had one logged on via VNC, and you can simply start another one normally on the console by logging in.

Have you ever used a Windows 2000 terminal server session, maybe at work or something? If so, it's sort of like that--you can have one "copy" of a user logged on at, say, the console, and one--or maybe even more--logged on remotely via Terminal Services. Yet they don't directly interact, i.e. you don't see one's windows on the others' screens; and if you log one off, the others are still there until they're separately logged off. On Linux it's sort of the same thing, except with SSH/VNC stuff in place of Windows Terminal Services.

Max

[mdettweiler]

Originally Posted by gd_barnes

Edit: Me doing a "poor man's KVM switch" with 10 machines??? lol Do you realize how much headache that would be plugging and unplugging monitors, keyboards, and mice among 10 machines? That ain't gonna be happening! lol

LOL--well, I was thinking that, of course, you'd be doing it with a bunch of different monitors, i.e. 2 or 3 machines per monitor as with your real setup, except with manually plugging and unplugging the stuff. But still, yeah, that would be a headache. It was bad enough for me with just two machines.

P.S.: I'm currently logged in via SSH on crunchford and I can see you got on just now.

[gd_barnes]

Originally Posted by mdettweiler

Okay, here. You *can* still see your desktop locally--just simply enter your password and log on as if you had started the machine. What's making this all confusing is the fact that in Linux, one user can have multiple, separate sessions logged on all at once. Hence I had one logged on via VNC, and you can simply start another one normally on the console by logging in.

Have you ever used a Windows 2000 terminal server session, maybe at work or something? If so, it's sort of like that--you can have one "copy" of a user logged on at, say, the console, and one--or maybe even more--logged on remotely via Terminal Services. Yet they don't directly interact, i.e. you don't see one's windows on the others' screens; and if you log one off, the others are still there until they're separately logged off. On Linux it's sort of the same thing, except with SSH/VNC stuff in place of Windows Terminal Services.

Max

Got your PM; thanks. I logged on and everything is good.

I saw what you stated demonstrated on someone else's machine at work a couple of years ago but didn't know what all was involved with it. But I can see the correlation now. Yeah, you don't see the other that might be doing work on the machine.

Thanks for your help!


Gary

[IronBits]

A lot of noise in here that has nothing to do with NPLB servers and everything to do with you guys having fun learning about linux

[mdettweiler]

Hmm...seems that the G4000 LLRnet server crashed (that is, the server application, not the machine itself) just now. Weirdest thing ever, it gave an odd error that I didn't recognize. David, have you by chance ever seen one of your LLRnet servers produce an error like this?

llrnet: net.cxx:138: static void* net_Server_t::connection_thread(void*): Assertion `thd->socket >= 0' failed.
net_signal called with code 6
shutting down listening socket

[mdettweiler]

Originally Posted by mdettweiler

Hmm...seems that the G4000 LLRnet server crashed (that is, the server application, not the machine itself) just now. Weirdest thing ever, it gave an odd error that I didn't recognize. David, have you by chance ever seen one of your LLRnet servers produce an error like this?

llrnet: net.cxx:138: static void* net_Server_t::connection_thread(void*): Assertion `thd->socket >= 0' failed.
net_signal called with code 6
shutting down listening socket

Oh man, it just crashed again, same error! I still have no idea what might be causing this.

If it crashes again, I may recommend that users switch to IB400 or C443 instead, since I'll be going to bed soon and won't be able to restart the server if it crashes during the middle of the night.

[IronBits]

Looks like a total application crash.
Put a new copy of the binary in there and see if that fixes it.
It's not happy about something on the socket...
Could be another proxy server coming in.
Had all kinds of fits when Beyond was running is own llrnet server to connect to my Windows server, thus the major reason for switching to linux.
Who's mac addy is it that comes in when it crashes?
Good luck!