Installation problems with NowWAp server

Installation problems with NowWAp server SearchSearch
Author Message
zeila zafranco
New member
Username: Support

Post Number: 2
Registered: 08-2010
Posted on Thursday, September 02, 2010 - 03:14 am:   

Hello there, We need your expert advise on this Thanks.

a few weeks ago we decide to install security
updates/paths and Service Pack 2 on the Windows servers where NoWWAP App is running, the
crashes started after this updates.

A week ago we decide to de-install all the updates, after this the service looks stable
again,
could you advise if any update on the server will break the current configuration?, also
there is any suggestion and how we can manage to keep the server up-to-date and not be
afraid to break NoWWAP App again.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2475
Registered: 08-2008
Posted on Thursday, September 02, 2010 - 09:20 am:   

Hi Zella,

We are not aware of any compatibility issues related to updates. Which versi on of Windows are you referring to? 32 bit or 64 bit?

What updates did you deinstall?

We can do some more research based upon your feedback to these questions, bu t there are no issues that we are aware of.

-- Des NowSMS Support
zeila zafranco
New member
Username: Support

Post Number: 3
Registered: 08-2010
Posted on Friday, September 03, 2010 - 06:07 am:   

Hello !

Thanks for your feedback. I really appreciate it.

Zeila
zeila zafranco
New member
Username: Support

Post Number: 4
Registered: 08-2010
Posted on Tuesday, September 07, 2010 - 01:23 am:   

Hello there,

Please see our reply to your questions:


Which version of Windows are you referring to? 32 bit or 64 bit?

==> Windows Server 2003 Standard R2 32bits SP1


What updates did you deinstall?

==> Service Pack 2 of Windows Server


Thank you in advance.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2491
Registered: 08-2008
Posted on Wednesday, September 08, 2010 - 09:57 pm:   

We are performing more tests on Windows Server 2003 Standard R2 Service Pack 2 ... however, we are not seeing any problems.

What type of problem should we be attempting to recreate?

Also advise how much memory is in the server?

By any chance, is there any 3rd party firewall software running on that server? (Firewall software often causes problems for a busy WAP gateway because firewall software is not designed to handle higher volume of traffic, and it may be firewall software that is having a problem with the update.)
zeila zafranco
New member
Username: Support

Post Number: 6
Registered: 08-2010
Posted on Thursday, September 09, 2010 - 05:07 am:   

Hi again, thanks for you reply. Can you please advise us on this? Thanks in advance


Today the services produce some alarms on the process again, we see on our monitoring server that the NowWAP Process was unknown and then UP
again.


Our monitoring server uses RPC to keep monitoring the process, do you
have any suggestion on this?, can we scheduled a webex/remote session to
check the server and see if there is anything that can cause this
problem?
zeila zafranco
New member
Username: Support

Post Number: 7
Registered: 08-2010
Posted on Thursday, September 09, 2010 - 11:28 pm:   

Hi. I would like to add :


There is no firewall or any other antivirus software running in the server that might block access.


Can you please advise us on this? Thank you in advance.

Waiting for your reply. Thanks.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7920
Registered: 10-2002
Posted on Friday, September 10, 2010 - 12:13 am:   

What is the version of NowWAP?

How much RAM in the server?

In the NowWAP statistics screen what is a typical value for active requests and active sessions?

As a quick suggestion, on a very busy system you may want to lower the keep alive timeouts. One of the defaults is 90 seconds. Lower it to 15 if it is higher.

Can you monitor process memory usage? This may be helpful to us.

-bn
Bryce Norwood
NowSMS Support
zeila zafranco
New member
Username: Support

Post Number: 8
Registered: 08-2010
Posted on Friday, September 10, 2010 - 02:08 am:   

Thank you for your reply. Please see response below:


What is the version of NowWAP?

A: Now.WAP Proxy v2008.06.03


How much RAM in the server?

A: 4.0 GB of RAM, Intel Xeon CPU @1.6GHz x 4 Core processors


In the NowWAP statistics screen what is a typical value for active requests
and active sessions?

The typical values change at different times during a day, but right now the values appear
to be ok (see the attached image).



Can you please advise us on this? Thank you in advance.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7924
Registered: 10-2002
Posted on Friday, September 10, 2010 - 09:58 pm:   

I don't know what I can advise unless there is some sort of pattern of a problem.

The statistic information that you included above is worth monitoring to see if there are dramatic increases in the "max active" statistics, as that can be indicative of a problem.

It also provide a sanity check for whether or not the service has been automatically restarted, based upon how long it is reported as being active.

Exceptional error conditions may result in this type of automatic restart, especially low memory situations. I would not expect you to approach a low memory situation unless you had a 10-fold increase in traffic over the numbers above.

There were numerous internal changes between NowWAP 2008 and 2009 to improve performance and better handle memory usage with these larger number of connections.

It is possible that updating to the 2009 or 2010 release would resolve whatever problems you are experiencing.

Do you have a current maintenance contract with us that would allow you to update?

Barring an update, my suggestion would be to:

1.) Try to establish a pattern or frequency of these restarts.

2.) Monitor the statistics periodically to look for spikes in active user and active request counts (particularly the max active for the day and since service restart).

3.) Monitor process memory usage to see if it seems to be increasing over time.

4.) I previously made a reference to a configuration setting that I thought you should change. I will now be more specific. On the "HTTP" page of the configuration settings, there are the following settings:

"Max Keep-Alive for client connections" - default = 300 seconds. Changing this to 180 (or even 120) will lower some resource utilisation, and should not impact performance.

"Max Keep-Alive for server connections" - default = 90 seconds. Change this to 15, as I suggested in the previous posting.

-bn
NowSMS Support
zeila zafranco
New member
Username: Support

Post Number: 9
Registered: 08-2010
Posted on Friday, September 17, 2010 - 06:57 am:   

Hello. Thank you for your response.