Loading Profile...
Pandion on Terminal Services High CPU
Hello. I'm running Pandion with eJabberd and it works fairly well. The only problem we've been having is with our Terminal Server (Win 2003 R2 x86). We have about 30 users and they work fine with Pandion. We have 2 generic users that about 15 PCs log into the server with. They all run Pandion. We often, 2-3 times a day, have 1 or 2 Pandion.exe processes running with the generic user taking up 50-75% of the CPU, which of course slows the server to a crawl for everyone.
Ending the process fixes the problem instantly.
The odd thing is the user is usually idle for a few minutes, not actively using the session.
Also is there anyway to force Pandion to not auto login (the checkbox at login), with regedit or changing some file? This might help so not so many people use it if not needed.
Thanks!
Ending the process fixes the problem instantly.
The odd thing is the user is usually idle for a few minutes, not actively using the session.
Also is there anyway to force Pandion to not auto login (the checkbox at login), with regedit or changing some file? This might help so not so many people use it if not needed.
Thanks!
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?You can pre-configure all options from the settings directory in the XML files.
Strange behaviour from the Terminal Services. I'm not too familiar with such an environment, can you explain what a generic user is and how it differs from the rest?
When the CPU spikes, are those Pandion instances still working as usual or are they frozen/locked up?
Does it happen after reconnecting, file transfer, locking the desktop, screensaver, opening/closing some window, or anything else that might be triggering? -
Inappropriate?I believe I have run into a very similar issue. I do not run terminal services with Pandion, but have run into the high CPU usage. I've noticed that when more than one person is logged into the same pandion/jabberd account, Pandion usually takes 100% of the processor time. The system becomes extremely unresponsive. Clicking the start menu may take about a minute for it to actually show the start menu. It doesn't usually affect both machines that I've noticed, and isn't always reproducable. As soon as you kill the Pandion process the system becomes responsive again. I manage about 230 Windows XP pro machines with service pack 2. The problem does not appear to be caused by file transfer (We rarely use file transfer) or locking the desktop. What appears to happen (this is just and educated guess) is that when one Pandion client connects use a jabberd account called johndoe and then a second Pandion client on a different computer connects to the same johndoe jabber account it sometimes causes this 100% cpu utilization on one or both of the computers.
The terminal services that Andy spoke of is similar to Remote Desktop in Windows, but instead of only have the 1 session on another computer it runs on a server and you can connect many computers many remote sessions on the server. It sort of a predecessor to virtualization... kind of.
http://en.wikipedia.org/wiki/Terminal...
I don't think that this issue is necessarily related to Terminal Services though, I think it has more to do with logging into the same jabberd account with two different Pandion clients at the same time.
Thanks,
Pete -
Inappropriate?Pete, when you connect Pandion from two machines to the same account, and the CPU spike happens, are the Pandion instances connected, disconnected, or constantly trying to reconnect? The server should send an error code when another client replaces the active session, thus telling the replaced Pandion that it should not reconnect. Otherwise two instances of Pandion can get stuck in a tug-o-war, forever reconnecting and bumping each other offline.
- Is the Pandion user interface responsive at all when the CPU spikes or does everything simply freeze?
- Have you seen this problem on machines other than XP SP2?
- Which version of Internet Explorer is installed on these machines?
-
Inappropriate?The impression that I have gotten in the past, is that it does seem like the 2 machines are fighting over the connection (it's been a while since I've worked on this issue, I usually just run taskkill remotely so that I don't have to fight with windows under 100% utilization). If I get the opportunity I will try to reproduce the problem. I suspect that the jabberd log may have something interesting in this case. I'll look into that and post results if I can.
- I don't think the Pandion Client is responsive, but I will test.
- I only have XP SP2 haven't upgraded to SP3 yet.
-I'm running IE6 on almost all computers. Another app isn't compatible with newer versions yet.
Thanks,
Pete
EMPLOYEE
