thubbardphysactg.com Posted October 16, 2009 Report Share Posted October 16, 2009 I have observed retroclient having an issue with memory consumption until all available memory is used resulting in a file server hanging requiring a hard reset. Is this a known issue with a resolution? ATTENTION:File service was denied for a connection request from MEMORY subsystem because your system is running at capacity. Please disconnect redundant connections. Please also contact tech support to learn how to upgrade your system smbd 10/16 7:51:30 AM I ATTENTION:File service was denied for a connection request from SWAP subsystem because your system is running at capacity. Please disconnect redundant connections. Please also contact tech support to learn how to upgrade your system smbd 10/16 7:51:30 AM W last message repeated 12 times 10/16 7:51:23 AM W last message repeated 14 times 10/16 7:50:28 AM W last message repeated 12 times 10/16 7:49:23 AM W last message repeated 14 times 10/16 7:46:24 AM W last message repeated 13 times 10/16 7:45:20 AM W last message repeated 14 times 10/16 7:42:17 AM W last message repeated 13 times 10/16 7:41:12 AM W last message repeated 14 times 10/16 7:38:09 AM W last message repeated 13 times 10/16 7:37:05 AM W last message repeated 14 times 10/16 7:34:01 AM W last message repeated 13 times 10/16 7:32:57 AM W last message repeated 14 times 10/16 6:49:22 AM W last message repeated 12 times 10/16 6:48:17 AM W last message repeated 13 times 10/16 6:45:18 AM W last message repeated 12 times 10/16 6:44:17 AM W last message repeated 14 times 10/16 6:41:14 AM W last message repeated 12 times 10/16 6:40:09 AM W last message repeated 14 times 10/16 6:37:09 AM W last message repeated 13 times 10/16 6:36:05 AM W last message repeated 13 times 10/16 6:33:02 AM W ServicePurge: service not found Retrospect[3307] 10/16 6:32:01 AM W ServicePurge: service not found Retrospect[3307] 10/16 5:49:16 AM W connTcpConnection: invalid code found: 145 Retrospect[3307] 10/16 5:49:16 AM W ServicePurge: service not found Retrospect[3307] 10/16 5:49:12 AM W connTcpConnection: invalid code found: 145 Retrospect[3307] 10/16 5:49:12 AM Quote Link to comment Share on other sites More sharing options...
rhwalker Posted October 16, 2009 Report Share Posted October 16, 2009 Terry, It might be useful to provide some configuration details. Version of Retrospect on the server, server details (hardware and OS), version of Retrospect client that is causing this problem, details (hardware and software) of the server on which the problem client is running, etc., and what the client was doing when this occurred. Russ Quote Link to comment Share on other sites More sharing options...
thubbardphysactg.com Posted October 16, 2009 Author Report Share Posted October 16, 2009 The server is Windows 2008, Retrospect server version is 7.6.2.101. The client is all our Linux Red Hat servers. Linux 2.6.18 Kernel for Red Hat 4 and 5, both 32 and 64 bit Dell 1950 and 2950 servers. Esx VMWare 3.5 and and Overland Storage snap server all exhibit this behavior. The events for the retrospect client are logged at the rate of up 10 12 per minute 24/7 when backups are running or when backups are idle. The client version is 7.6.107. This event generates a tremendous volume of entries in the log of all these clients. We are having to do scheduled restarts of these clients to prevent the server memory from being exhausted. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted October 16, 2009 Report Share Posted October 16, 2009 (edited) The client is all our Linux Red Hat servers. ...The client version is 7.6.107. Odd bug, odd that I haven't seen it reported before. Pretty severe failure mode. Also odd that the updates page reports that the Linux Red Hat client version is 7.6.100. Rather than rebooting the server, have you considered a cron job to launch the client just before backup and then kill it after backup? I have never used the Linux client, but have you seen this thread from a while back when the client came out? 7.6 Linux client broken Seems that you have to blow away any remnants of a prior client install. Is this a fresh install, or was there an older Linux client there before? Russ Edited October 16, 2009 by Guest Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.