low virtual memory

Hi,

How do i rectify following problem with low virtual memory.
This log i captured is from iwtrace.log

Regards
Chandra

Local system: "MGR101360"
[Fri Jan 24 12:01:15 2003] done. 6 users and 3 groups read.
[Fri Jan 24 12:01:23 2003] Warning: this system is configured with different values for the
[Fri Jan 24 12:01:23 2003] initial and maximum pagefile size. It's strongly recommended that
[Fri Jan 24 12:01:23 2003] you use the same value. Low memory condition is triggered based
[Fri Jan 24 12:01:23 2003] on the initial size.
[Fri Jan 24 12:01:23 2003] Cache size: 30000
[Fri Jan 24 12:02:56 2003] TFSEnvironment: inode cache 30000
[Fri Jan 24 12:03:01 2003] Batch Jobs Thread started
[Fri Jan 24 12:03:01 2003] d:\teamsite\iw-home\etc\iw.cfg: rpc_threadcount=64
Domain "ARIBADOMAIN" is added to the domain list, pdc="\\B2BCOE".
[Fri Jan 24 12:10:50 2003]

Your system is running low on virtual memory (100 Mb is available)
[Fri Jan 24 12:10:50 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:13:45 2003]

Your system is running low on virtual memory (69 Mb is available)
[Fri Jan 24 12:13:45 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:15:52 2003]

Your system is running low on virtual memory (87 Mb is available)
[Fri Jan 24 12:15:52 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:20:29 2003]

Your system is running low on virtual memory (63 Mb is available)
[Fri Jan 24 12:20:29 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:20:51 2003]

Your system is running low on virtual memory (81 Mb is available)
[Fri Jan 24 12:20:51 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:24:24 2003]

Your system is running low on virtual memory (64 Mb is available)
[Fri Jan 24 12:24:24 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:25:23 2003]

Your system is running low on virtual memory (58 Mb is available)
[Fri Jan 24 12:25:23 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:25:51 2003]

Your system is running low on virtual memory (84 Mb is available)
[Fri Jan 24 12:25:51 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:29:29 2003]

Your system is running low on virtual memory (63 Mb is available)
[Fri Jan 24 12:29:29 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:30:50 2003]

Your system is running low on virtual memory (93 Mb is available)
[Fri Jan 24 12:30:50 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:31:24 2003]

Your system is running low on virtual memory (63 Mb is available)
[Fri Jan 24 12:31:24 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:35:21 2003]

Your system is running low on virtual memory (59 Mb is available)
[Fri Jan 24 12:35:21 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:35:51 2003]

Your system is running low on virtual memory (93 Mb is available)
[Fri Jan 24 12:35:51 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:37:24 2003]

Your system is running low on virtual memory (59 Mb is available)
[Fri Jan 24 12:37:24 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:40:53 2003]

Your system is running low on virtual memory (75 Mb is available)
[Fri Jan 24 12:40:53 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Fri Jan 24 12:42:24 2003]

Your system is running low on virtual memory (54 Mb is available)
[Fri Jan 24 12:42:24 2003] Server will deactivate all stores if available memory falls below 50 Mb

Find more posts tagged with

Comments

Adam Stoller

(1) Talk to your IT department about available memory on that machine
(2) Make sure your machine meets the sizing requirements as set forth in the TeamSite Administrator's Guide
(3) Make sure you configure the settings for [iwserver] in your iw.cfg file appropriately for your configuration.
(4) Is your TeamSite server a dedicated TeamSite server - or are you running other, significant, applications on it (not recommended)

--fish
(Interwoven Senior Technical Consultant)

shanon

We're having the exact same problem on our development system. We upgraded from 5.0.2 to 5.5.2 SP2 and our system is totally unstable. We haven't changed any of the cache / threadcount values in iw.cfg. Our Win2K system has plenty of memory and such and is dedicated to TeamSite.. what's up with this?

Shanon Levenherz
Mercer eBusiness Team
shanon.levenherz@mercer.com
http://www.mercerhr.com

chandub

Fish,
It is a brand new machine and very good at RAM and harddisk too.No s/w otherthan teamsite,
started with TS installation.

I dont think it is the problem with my machine.
Later i have checked in some other machines also where in iwtrace.log is showing the same problem(all are TS5.5.2) on W2K

And today the Teamsite shutdown to most uncommon problem after giving such errors ,Even tough i can login into teamsite , i cannot view any branches.
Here is the log shown in iwtrace.log.

Your system is running low on virtual memory (69 Mb is available)
[Sat Jan 25 11:44:33 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Sat Jan 25 11:45:34 2003]

Your system is running low on virtual memory (78 Mb is available)
[Sat Jan 25 11:45:34 2003] Server will deactivate all stores if available memory falls below 50 Mb
[Sat Jan 25 11:47:05 2003]

Your system has run low on virtual memory (47 Mb is available)
[Sat Jan 25 11:47:08 2003] All stores are being deactivated
[Sat Jan 25 11:47:08 2003] Warning: this system is configured with different values for the
[Sat Jan 25 11:47:08 2003] initial and maximum pagefile size. It's strongly recommended that
[Sat Jan 25 11:47:08 2003] you use the same value. Low memory condition is triggered based
[Sat Jan 25 11:47:08 2003] on the initial size.
[Sat Jan 25 11:47:08 2003] Memory Monitor: releasing memory...
[Sat Jan 25 11:47:08 2003] Memory Monitor: deactivating stores...
[Sat Jan 25 11:47:08 2003] TEnvironment::Flush flushed 0, unlinked 0
[Sat Jan 25 11:47:10 2003] TEnvironment::Freeze freeze until Sun Jan 25 11:47:08 2004
[Sat Jan 25 11:47:11 2003] TEnvironment::dtor found 0 dirty.
[Sat Jan 25 11:47:11 2003] Deactivated store 0x64 default
[Sat Jan 25 11:47:11 2003] Please shutdown the server.

I have restarted my teamsite, started working but with the same trigger(low virtual memory)again in log file.

Anybody there, who knows how to rectify this problem.?

TIA
Chandra

tvaughan

I've never run IW on Windows, but have you looked into that error message "Warning: this system is configured with different values for the initial and maximum pagefile size. It's strongly recommended that you use the same value. Low memory condition is triggered based on the initial size."

Go to Start Menu --> Control Panel --> System

Click the "Advanced" tab, then the "Performance Options" button. Click the "Change" button and check to see what the memory settings are for initial and max.

Are they different? If they are, can you bump up the initial to be the same number as the max? Does that help?

Tom

Gregg Faus

I've had a problem with the iwproxy.exe process eating memory. I remember about a week ago it was running out of control at 800 MB. It normally uses about ~20k. Killing proxy didn't flush this process out either.

When this happened I too was receiving low virtual memory problems. Just thought I'd add this input to see if your iwproxy.exe process is consuming a lot of memory.

-gf

chandub

Thanks Tom,
that was great...working now...

For those who are facing the same problem (only there in 552)
Please read TS552 release notes in page 13.

Regrads
Chandra
http://www.wipro.com

tiroth

We also have problems with iwproxy memory leaks. Anecdotally, it seems that if you stop/restart iwproxy before it eats up too much RAM it is successful, but if you wait until it allocates >750MB the instance is unkillable.

We reported this issue a week ago and have yet to hear back from Interwoven. It is a rather serious bug. Have you filed a ticket on it gfaus?

rajnag

We have TeamSite 5.5.2 with service pack 5 still this problem occurs. Did you here any thing from interwoven on this issue if so let me know the workaround.

Thanks

nag.

KrisK

Did you get any solution to this issue? I've the similar issue on Solaris TS 552 SP4.
Regards,
K