Hi all.
I 'll go first, i'm trying to get vncviewer working under ubuntu 8.04lts i can use ssh between rigs no problems. But
i can't get vnc working no matter what i do, i've looked at the ubuntu fourms and it seems others have had the same type
of problem. I've played around with the firewall setting that didn't make a diff so, anyone tried it and got some advice
i want to do away with my KVM if i can and just connect over the LAN switch.
pete.
Are you having trouble connecting TO an Ubuntu box FROM a Windows box with VNC Viewer? Or viewing one Ubuntu (or Windows) box FROM another that's running vncviewer? Just need to make sure before I answer the wrong question
I use Remote Desktop Viewer at the client end and Remote Desktop at the "server" end. Works fine as long as the server has been set up to allow connections AND it has been set up for automatic login on startup.
Quote from: Webmaster Yoda on February 03, 2009, 02:25:47 PM
Are you having trouble connecting TO an Ubuntu box FROM a Windows box with VNC Viewer? Or viewing one Ubuntu (or Windows) box FROM another that's running vncviewer? Just need to make sure before I answer the wrong question
I use Remote Desktop Viewer at the client end and Remote Desktop at the "server" end. Works fine as long as the server has been set up to allow connections AND it has been set up for automatic login on startup.
Hi W.M.Y.
What windows :shock no two, soon to be three ubuntu 8.04 boxer's. I've set it up under system/preferences/remote desktop and under applications/internet/remote desktop viewer.
And in firestarter to allow vnc & port 5900 on both but nothing works, like i said ssh works fine so i just don't know what's going wrong.
pete.
OK, I don't use firestarter but it may well be that the issue is there.
You do need to be logged in on the other computer (the ne you're viewing). If it/they are sitting at the login screen, you will not be able to connect to them via Remote Desktop Viewer (only via SSH, which is what I do with mine)
Hi W.M.Y.
This is what i get from vnc viewer message (Connection to host "*.*.*.*:5900" was closed.) numbers removed) when i try to connect to either host.
Two are running on the KVM atm so i can play around with settings.
I've tryed to change setting in firestarter nothing makes a diff, i did see on one forum tread about opening port 20 or 22 can't remember which
but i don't want to open to many do i.
pete.
As I said, I don't use Firestarter. But if I did, I would not be too worried about internal traffic. Linux isn't as vulnerable as Windows :)
Anyway, in your remote desktop settings, you can (under the advanced tab) specify LOCAL traffic only and you can enable encryption as well. Plus you can assign a password. That way, only someone on the LOCAL network who knows the password can log in to the desktop
I actually get the same message you quoted when I try to connect to the remote desktop on all except one of my Linux boxes. The difference between that one and the rest is that I'm logged in to that one and the desktop is therefore open and available. The others are sitting at their login screen, so vinaigre (the "VNC server") is not answering (after all, there is no desktop to connect to)
As soon as I log in to one of those computers (via KVM), I can log to the remote desktop too.
Hi Pete
SSH works fine, you say, so the basic networking is good. It's either a VNC or firewall problem.
Have you fully configured VNC on the machine you're connecting to? I had problems connecting to one system that I hadn't set the VNC auth password on. Also double check that the VNC config is saved. I think one way you can test is open the VNC viewer on that same machine and try connecting to localhost.
Also if removing KVM make sure the BIOS is enabled for booting without keyboard. You probably know that but it had me puzzled for a minute... :)
No you don't want to open any firewall ports you aren't using. I would argue this is valid on a home network too, but that's your choice and I'm a bit paranoid! 22 is used for incoming SSH. IF tunnelling VNC over SSH then you need that enabled, but SSH is useful as a backup anyway if VNC dies. For VNC you should only need 5900 open although if using multiple logical displays then you will also need 5900+N where N is the display number.
WW
Hi W.M.Y. & WW.
I did setup all the setting's for VNC and i allowed the i.p. addi & port 5900 threw firestarter, it knows it's for vnc as soon as you put
the port number in, just won't work guess i have to buy that new bigger KVM o'well.
pete.
Security concerns aside (for a moment), try setting the "server" up without any security, i.e. no password for connection, no encryption, not restricted to local connections. See if it works then.
And as WW said, try it locally (viewing itself) too.
Dumb question - every now and then, a program running in Ubuntu will fade ... the screen goes black and white (in that program only) .... and the program cant be used for a while
On the task bar I can go into anyother program, and all is well - except for that one that has sort of 'dimmed'
It will come back to life after a while and will allow to be used again
Can someone help with what the problem is?
Cheers
@ONYX..I get the same thing occasionally. I think it is like when a program in , say, Windows, hangs for a while. I never get it for more than a few seconds though.
I would say it is due to "over comitment" of resources,... as my lappy, (dual core AMD @1.6Ghz, only 512 Mb RAM) does it more than any other computer, and "hangs" for longer.
The other boxes are all q6600's with at least 2Gb RAM, up to 4Gb RAM.
Hi all
I am updating my Ubuntu 7.10 Pc's as they have not been updated for months and months. I have the new linux milkyway apps on a usb but when I put in the usb memory stick what then. It is command line and I do not know what the command is to copy the files from the USB memory stick to the projects folder. I can't see the stick as I don't know where it is ??
Any help would be appreciated.
EDIT:
OK I found the answer:
Using sudo
mkdir mnt/usb
mount /dev/sdb1 /mnt/usb
[/i]
I am using Ubuntu 8.10 and recently deleted all reference to my previous versions of BOINC and installed version 6.4.5 in order to run CUDA devices. Not all is well however as it seems that the Links to access a workunit's webpage from the unit itself (either from Projects or Tasks) is broken or not set up properly. As it is more likely to be the later how do I set this feature up.?
Quote from: Cruncher Pete on April 06, 2009, 08:21:49 AM
I am using Ubuntu 8.10 and recently deleted all reference to my previous versions of BOINC and installed version 6.4.5 in order to run CUDA devices. Not all is well however as it seems that the Links to access a workunit's webpage from the unit itself (either from Projects or Tasks) is broken or not set up properly. As it is more likely to be the later how do I set this feature up.?
I remember this issue cropped up in the old forum. Something to do with your default browser settings from memory? Or perhaps local prefs file?
hmmm, I just had to change from 6.4.5 to 6.6.20, because the former wasn't seeing my card..!!
It diodn't mention "missing" libcudart.so or anything.. didn't mention a THING !
but now.... GPUgrid says it doesnt have work for my "type of computer".
just thought..maybe it's a prefs thing at the project.. looking now..
Quote from: veebee on April 06, 2009, 09:56:45 AM
hmmm, I just had to change from 6.4.5 to 6.6.20, because the former wasn't seeing my card..!!
It diodn't mention "missing" libcudart.so or anything.. didn't mention a THING !
but now.... GPUgrid says it doesnt have work for my "type of computer".
just thought..maybe it's a prefs thing at the project.. looking now..
No that is a common issue on GPUGID. Just wait a while and you will get work.
I uninstalled and re-installed the drivers, restarted boinc-client and computer a cpl times and it finally got work - but each WU errored out after about 3 seconds....
went through it all again and it is now "working"..
only problem is that the WU is "running " like a normal WU, in that the time taken is ticking over "normally".... not just showing those few seconds it steals from the cpu's... (or at least I think that's what it's showing..).
Anyone seen this "problem"? I wonder if it's a "fix" in the client (6.6.20).. to show the actuall time taken ??
I think it is a fix veebs - its ticking non stop on mine as well now (XP 32), rather than just the odd ticking haha
OK I am resurrecting this thread from the dead because its been a good 6 months since anyone visited it, and I dont want to start a new unneccessary thread!
My issue - I am dabbling with Ubuntu 9.1 again (64 bit)
My issue with BOINC as in the past - a whole heap of projects just error out the WU's instantaneously upon starting work on them. I remember this used to happen in the past.
Right now, I loaded up Rosetta, its fine and is doing its work. I started work on Spinhenge though, and it just errors out all WU's. I also tried Einstein, same thing.
I am sure it will do it on other projects.
Is there something I am missing? I have no idea why this is happening. I have installed BOINC from the Add/Remove programs place.
Please help - I want to get Ubuntu up and running again, and steer clear from Winbloze for once and for all.
I had trouble with almost every project on my Kubuntu box until I reversed the overclocking. Even 5% was too much for many projects. Don't really have a clue why, or if the same thing is affecting your set up.
Well, for the einstein wus to fail, the obvious reason (to me) is that they are 32 bit applications and you need to download and install the 32 bit libraries....... and I know I should know where they are and what they are called... brb.. (hoping I haven't deleted the bookmarks...)
sudo apt-get install ia32-libs
Reference (http://maketecheasier.com/run-32-bit-apps-in-64-bit-linux/2009/08/10)
Hope that works.
Yep, Furlozza is right on the money, those apps and WUs are failing because there is no 32 bit library support in the standard x64 install.
I've also found problems with IBERCIVIS WUs if I use "nice" or "renice" to adjust process priority after the WU has started. The WU unit completes, but often fails validation and hence no credit :cry2:
I'd agree the 32 bit libs are the problem as well.
I had an i7, 3 x Q6600's, 1 x E6300, 1 x E4400 and an AMD X2 lappy all running 64 bit Kubuntu and then Ubuntu.
Only EVER had the occasional WU error out here and there, exclusively due to probs in the WU's or apps themselves.
I always had ia32-libs AND libc6 installed.
THEN, you must make sure you stop (properly, not just clicking on the "x") the boinc client and restart it. (best way if you aren't sure is to do a reboot after installing the libs, although that isn't neccessary like it is in Windows...)
Hi ONYX.
Have a look at this page right at the bottom for Ubuntu, some projects might need others as well.
Hope it helps.
http://boinc.berkeley.edu/wiki/Installing_on_Linux#64_Bit_Considerations
TRhanks P.P.L... a good link...
I'll be swapping one of my i7's back to Ubuntu 64 bit myself when my Install dics for Win 7 Ult x64 turns up.... there are just some projects which run that much better under linux 64 bit - must take advantage with a reduced farm.
I'd just like to say that I popped into this forum to see some help you guys provided me with in here.
I am making the jump to Ubuntu for the about the 5th time .... but this time it looks permanent. Looks like its a definite winner this time around.
And I needed to refer to this thread again. Perfect.
Cheers to all - its been a while.
Good to see you again, Onyx.
Good luck with Linux, but maybe it is just that I am getting too old too soon and can't be bothered learning new tricks, hence the return to M$ and W7. However, iGnatious is still available should I ever decide to once more thumb my nose at M$.... oh and not worry about little things like..... OEM and the rules that drive ya mad :compbash: