helfgott

[helfgott]

Hi @drichard

Btw confirmed with networking the current network has 10gb capability, that the moment of the incident this worked well.

!m technicians suggest a problem with the access to the database, they are working on a fix:

the initial results of benchmark tests in our labs allowed to identify two key points that can be improved. Database warnings have been also reproduced.

This however doesn’t happen if the same number of users is reached progressively (not all of them try to login at the same time).

Without logs from your environment we cannot confirm if the issues found in our labs are exactly the same, but in any case they need to be addressed.

1) Procedure to check users on the system slows down when the number of concurrent accesses increases.

As a workaround, add the following key to the end of /usr/NX/etc/server.cfg on the Enterprise Terminal Server host:

  DisableUsernameConversion 1

There’s no need to restart the server.

This ticket was about creating stress test by ourselves, I guess this can be closed as we are following the incident through the support team of NX.

[helfgott]

Hi @drichard

Yes, those are virtual Linux sessions.

8 Nodes 1 terminal server.

The TS acts as broker to the nodes.

This are the stats for 165 users right now:

TX:             cum:    574MB   peak:   28.7Mb                                                                        rates:   25.1Mb  24.1Mb  22.4Mb

RX:                     572MB           28.4Mb                                                                                 24.4Mb  24.0Mb  22.3Mb

TOTAL:                 1.12GB           57.1Mb                                                                                 49.6Mb  48.1Mb  44.7Mb

I never used this tool, checking it out!

 

And about this:

So you might have a high number of people opening browsers initially, and then slowly through the day their usage drops.

Our infra is quite complex. The NX clients will load with a generated template by script and load the X server via SSH, but yes, because its a bank the operations starts at certain time in the morning.

We had to rollback to our 300 servers of NX until we found out what is causing the issue.

I’ll try to read about configuring multiple network cards to see if that helps.

Regards.

H.

 

[helfgott]

This topic can be marked as solved.

The guest accounts do not work with multinode environments: https://www.nomachine.com/TR02Q09138

Since I can’t use productive users I could not use this approach.

H.

[helfgott]

@Gega thank you, confirmed that custom comments affect the behavior of the product.

Removing the custom comment worked.

Thanks.

H.

[helfgott]

This topic can be marked as solved!

[helfgott]

Thanks for your help @fisherman amd @mlyn

After applying the changes I was able to see the expected behavior. My user will be presented with the list of nodes on the client interface and other users outside the group LAPTOPS will be balanced automatically..

Those labels are quite useful! I’m renaming everything.

Thanks again!

Best regards.

H.

 

 

[helfgott]

Update:

 

Node selection works properly, but the NX interfaces it’s confusing.

I’m presented an Icon view where the information is:

“Default node name, Node Id: 1”

The Node Id isn’t the same as the Node Name.

 

 

[helfgott]

Wow, that’s amazing, I’ll be looking forward to this!!!

Thank you!!

Helfgott.

[helfgott]

1. Did you evaluate using guest users? They would allow to automatically create a new user for each client connections, environment would not be shared among them (different home directories) and your script would be easier.

Yes, guest sessions aren’t an option. Here’s the detail:

In our current scenario with free !m we have this:

• Workplace 1 – ScannerUser1,ScannerUser2,ScannerUser3,ScannerUser4,ScannerUser5
• Workplace 2 – ScannerUser1,ScannerUser2,ScannerUser3,ScannerUser4,ScannerUser5
• Workplace 3 – ScannerUser1,ScannerUser2,ScannerUser3,ScannerUser4,ScannerUser5
• … and so on…
• Workplace 599 – ScannerUser1,ScannerUser2,ScannerUser3,ScannerUser4,ScannerUser5

Because each Workplace it’s a !m node there’s no problem. We can’t change those users, several scripting processes run on them and we must identify them in that way. Our current problem with the paid version is only having 9 nodes where a huge amount of ScannerUser1 (it would be 599 ScannerUser1 in 9 nodes, i.e) will collide in the same node, that’s why we need to setup !m to create always a new session (in an interactive way).

2. Do users need to suspend and restore sessions, or when a user disconnects the session should rather be terminated?

No, when a user is disconnected the session can be terminated.

@Sil04 Another possibility would be to configure the server for always creating a new session. This applies only if the session must be terminated and there’s no need to reconnect it.

Yeah, that’s not a problem, the thing is it must be interactive, we already setup the server to create always a new session but you must click on “create new session” and we can’t afford that.

Further detail

As I’ve mentioned before we have a python script to do the login process (which do many things) imagine this scenario:

1. The user turn on the machine
2. A python window (PyQt4) appears and ask for User//Password
3. The user provide user//password
4. The script does its magic (which involves creating the nxs template)
5. The script launch the nxplayer + custom template
6. The user only sees a new window (full-screen) with it’s session

We have setup the server to always create new sessions, but we have a problem:

1. The user turn on the machine
2. A python window (PyQt4) appears and ask for User//Password
3. The user provide user//password
4. The script does its magic (which involves creating the nxs template)
5. The script launch the nxplayer + custom template
6. The user sees a !m window and must click in “create new session” <– this must be interactive
7. The user only sees a new window (full-screen) with it’s session

We can’t allow it. That’s why I’m looking for a way to create the session directly without asking to the user or presenting any dialog from !m.

Sorry for not answering quickly I was sick last week.

Regards,

Helfgott.

[helfgott]

Hi @Tor, thanks for answering.

We have a TS with 9 nodes, let’s say:

• TS_NM_SERVER
• Node_1
• Node_2
• ………_9

And we have some generic users:

• GenericUser1, GenericUser2, GenericUser3

With the free !M version we established our sessions through python and a .nxs template dynamically in 500 servers (each server was a node), at the end of the script we call:

• /usr/NX/bin/nxplayer –session custom_template.nx

Because we had 500 nodes each generic user would connect to each node, there was no chance to have two “GenericUser1” connected in the same node. So we had 500 GenericUser1 sessions at the same time, one in each node.

With the new paid infrastructure (TS) we only have available 9 nodes, so GenericUser1 (i.e) will be connecting to one of our 9 nodes, the issue is we need 500 sessions with the same generic user. That means GenericUser1 is going to be connected several times against each node, and each time it must have a new session, also the session must be dynamically created, we can’t allow users to click on “new_session” through the NX GUI.

I’ve looked for a flag kind of:

• /usr/NX/bin/nxplayer –session custom_template.nx –new_session

but that doesn’t seem to exist.

Please let me know if I’m clear with the example.

Regards

H.

[helfgott]

We’ll check it and I’ll come back with an answer.

[helfgott]

Hi @Tor

The session is established to a virtual desktop.

Server: Ubuntu 16_04 64b – NX Terminal Server 6.2.4 with nodes (it’s the latest)

Client: Ubuntu 12_04 with NoMachine 6.2.4_1_i386.deb

 

[Author]

Posts