Endpoint Protection

 View Only
Expand all | Collapse all

Replication problem

Migration User

Migration UserJan 26, 2010 10:48 AM

Migration User

Migration UserJan 26, 2010 10:51 AM

Migration User

Migration UserJan 26, 2010 12:23 PM

Migration User

Migration UserJan 27, 2010 06:42 AMBest Answer

  • 1.  Replication problem

    Posted Jan 25, 2010 07:55 AM
    Hello Everyone,
    One of our customers having a problem with replication. First of all 10 Sep Manager zones with replication worked with success. Nearly 2 months ago all zones started to fail in turn.
    I tried all things in forums and kb. Then i removed  all replications with all sites and installed a new site to a new machine(this will be 11th zone) and connect directly to central Sep Manager machine with a second nic.
    But nothing changes eventough just one zone connected directly.
    Because of the new installation of the site i try it with "Reconfigure Site Wizard",it successfully get the certificates and other thing,when that popup says "Replicating Database",the central server creates db files on the replication outbox folder.(nearly 670 mb,but the db is over 5 GB's,maybe this is the problem.)
    After the central server creates these files,the other machine creates inbox folder in the replication folder but no files added more.(complicated numerical named folders both created on central server and the other successfully.)

    After that no other data shared with each server,i also sniff the network traffic with a packet sniffer.
    After some time(nearly 3-4 hours) the popup on the zone site appears and says "Failed To Connect To Server"

    Also log says that.

    I decided to call support but just try forums before it.

    Thanks for your help.

    Finally both of servers are RU5

    And here's the log of zone;

    Port 2638 is available.
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    at java.net.Socket.connect(Socket.java:519)
    at java.net.Socket.connect(Socket.java:469)
    at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:646)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1064)
    at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
    at com.sygate.scm.common.communicate.Communicator.sendFileRequest(Communicator.java:682)
    at com.sygate.scm.server.replication.RemotePartnerCommunicator.getChangedMetadata(RemotePartnerCommunicator.java:352)
    at com.sygate.scm.install.util.SiteSynchronizer.getChangedMetadataFromRemoteSite(SiteSynchronizer.java:74)
    at com.sygate.scm.install.util.SiteSynchronizer.synchronizeSite(SiteSynchronizer.java:32)
    at com.sygate.scm.install.ui.MainFrame.replicateData(MainFrame.java:2874)
    at com.sygate.scm.install.ui.MainFrame.configureDB(MainFrame.java:1278)
    at com.sygate.scm.install.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:826)
    at com.sygate.scm.install.ui.MainFrame.access$400(MainFrame.java:180)
    at com.sygate.scm.install.ui.MainFrame$3$1.construct(MainFrame.java:607)
    at com.sygate.scm.install.util.SwingWorker$2.run(SwingWorker.java:121)
    at java.lang.Thread.run(Thread.java:619)
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    at java.net.Socket.connect(Socket.java:519)
    at java.net.Socket.connect(Socket.java:469)
    at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:646)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1064)
    at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
    at com.sygate.scm.common.communicate.Communicator.sendFileRequest(Communicator.java:682)
    at com.sygate.scm.server.replication.RemotePartnerCommunicator.getChangedMetadata(RemotePartnerCommunicator.java:352)
    at com.sygate.scm.install.util.SiteSynchronizer.getChangedMetadataFromRemoteSite(SiteSynchronizer.java:74)
    at com.sygate.scm.install.util.SiteSynchronizer.synchronizeSite(SiteSynchronizer.java:32)
    at com.sygate.scm.install.ui.MainFrame.replicateData(MainFrame.java:2874)
    at com.sygate.scm.install.ui.MainFrame.configureDB(MainFrame.java:1278)
    at com.sygate.scm.install.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:826)
    at com.sygate.scm.install.ui.MainFrame.access$400(MainFrame.java:180)
    at com.sygate.scm.install.ui.MainFrame$3$1.construct(MainFrame.java:607)
    at com.sygate.scm.install.util.SwingWorker$2.run(SwingWorker.java:121)
    at java.lang.Thread.run(Thread.java:619)
    com.sygate.scm.common.communicate.CommunicationException: Failed to connect to the server.

    Make sure that the server is running and your session has not timed out.
    If you can reach the server but cannot log on, make sure that you provided the correct parameters.
    If you are experiencing network issues, contact your system administrator. ErrorCode: 0x80020000
    at com.sygate.scm.common.communicate.Communicator.sendFileRequest(Communicator.java:731)
    at com.sygate.scm.server.replication.RemotePartnerCommunicator.getChangedMetadata(RemotePartnerCommunicator.java:352)
    at com.sygate.scm.install.util.SiteSynchronizer.getChangedMetadataFromRemoteSite(SiteSynchronizer.java:74)
    at com.sygate.scm.install.util.SiteSynchronizer.synchronizeSite(SiteSynchronizer.java:32)
    at com.sygate.scm.install.ui.MainFrame.replicateData(MainFrame.java:2874)
    at com.sygate.scm.install.ui.MainFrame.configureDB(MainFrame.java:1278)
    at com.sygate.scm.install.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:826)
    at com.sygate.scm.install.ui.MainFrame.access$400(MainFrame.java:180)
    at com.sygate.scm.install.ui.MainFrame$3$1.construct(MainFrame.java:607)
    at com.sygate.scm.install.util.SwingWorker$2.run(SwingWorker.java:121)
    at java.lang.Thread.run(Thread.java:619)
    Port 2638 is available.
    java.net.SocketTimeoutException: Read timed out
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:129)
    at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293)
    at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:746)
    at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
    at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
    at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:687)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1064)
    at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
    at com.sygate.scm.common.communicate.Communicator.sendFileRequest(Communicator.java:682)
    at com.sygate.scm.server.replication.RemotePartnerCommunicator.getChangedMetadata(RemotePartnerCommunicator.java:352)
    at com.sygate.scm.install.util.SiteSynchronizer.getChangedMetadataFromRemoteSite(SiteSynchronizer.java:74)
    at com.sygate.scm.install.util.SiteSynchronizer.synchronizeSite(SiteSynchronizer.java:32)
    at com.sygate.scm.install.ui.MainFrame.replicateData(MainFrame.java:2874)
    at com.sygate.scm.install.ui.MainFrame.configureDB(MainFrame.java:1278)
    at com.sygate.scm.install.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:826)
    at com.sygate.scm.install.ui.MainFrame.access$400(MainFrame.java:180)
    at com.sygate.scm.install.ui.MainFrame$3$1.construct(MainFrame.java:607)
    at com.sygate.scm.install.util.SwingWorker$2.run(SwingWorker.java:121)
    at java.lang.Thread.run(Thread.java:619)
    java.net.SocketTimeoutException: Read timed out
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:129)
    at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293)
    at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:746)
    at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
    at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
    at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:687)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1064)
    at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
    at com.sygate.scm.common.communicate.Communicator.sendFileRequest(Communicator.java:682)
    at com.sygate.scm.server.replication.RemotePartnerCommunicator.getChangedMetadata(RemotePartnerCommunicator.java:352)
    at com.sygate.scm.install.util.SiteSynchronizer.getChangedMetadataFromRemoteSite(SiteSynchronizer.java:74)
    at com.sygate.scm.install.util.SiteSynchronizer.synchronizeSite(SiteSynchronizer.java:32)
    at com.sygate.scm.install.ui.MainFrame.replicateData(MainFrame.java:2874)
    at com.sygate.scm.install.ui.MainFrame.configureDB(MainFrame.java:1278)
    at com.sygate.scm.install.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:826)
    at com.sygate.scm.install.ui.MainFrame.access$400(MainFrame.java:180)
    at com.sygate.scm.install.ui.MainFrame$3$1.construct(MainFrame.java:607)
    at com.sygate.scm.install.util.SwingWorker$2.run(SwingWorker.java:121)
    at java.lang.Thread.run(Thread.java:619)
    com.sygate.scm.common.communicate.CommunicationException: No response from the remote server ErrorCode: 0xd0010000
    at com.sygate.scm.common.communicate.Communicator.sendFileRequest(Communicator.java:728)
    at com.sygate.scm.server.replication.RemotePartnerCommunicator.getChangedMetadata(RemotePartnerCommunicator.java:352)
    at com.sygate.scm.install.util.SiteSynchronizer.getChangedMetadataFromRemoteSite(SiteSynchronizer.java:74)
    at com.sygate.scm.install.util.SiteSynchronizer.synchronizeSite(SiteSynchronizer.java:32)
    at com.sygate.scm.install.ui.MainFrame.replicateData(MainFrame.java:2874)
    at com.sygate.scm.install.ui.MainFrame.configureDB(MainFrame.java:1278)
    at com.sygate.scm.install.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:826)
    at com.sygate.scm.install.ui.MainFrame.access$400(MainFrame.java:180)
    at com.sygate.scm.install.ui.MainFrame$3$1.construct(MainFrame.java:607)
    at com.sygate.scm.install.util.SwingWorker$2.run(SwingWorker.java:121)
    at java.lang.Thread.run(Thread.java:619)
     


  • 2.  RE: Replication problem



  • 3.  RE: Replication problem

    Posted Jan 25, 2010 08:08 AM
     Thanks for your help but i tried to change java heap size and i have no bandwith problem because the two machines are connected directly to each other.


  • 4.  RE: Replication problem

    Posted Jan 25, 2010 09:20 AM

    Can you check the scm-server-0.log file located at  Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs

    and check for https 415 error. In case its there paste the relevant portion and we will troubleshoot further.

    Check for any recent changes in Firewall or Proxy


  • 5.  RE: Replication problem

    Posted Jan 25, 2010 10:10 AM

    Was it a  fresh installation setup when replication was enabled or it was a migration?

    If it was a migration what was the migrtaion path that was followed?



  • 6.  RE: Replication problem

    Posted Jan 25, 2010 10:18 AM
     the central server is migrated from mr4 before but the other server is freshly installed RU5,


  • 7.  RE: Replication problem

    Posted Jan 25, 2010 10:53 AM
    We had replication problems as well, 12 Sites including the Central server.  It seems that once your DB gets to a certain size, replication becomes nearly impossible.  I suggest checking and making sure you don't have your SEPMs to track every application that is run.  I found that this setting blew up my DB size exponetially.  Once I had removed this option, replication started working however it would replicate once a day to the remote sites for about a week then die, causing me to reboot the entire infrastructure.

    In all honesty, as a Symantec Customer I can suggest this...remove as many sites as you can, and utilze GUPs where you have bandwidth concerns.  We are looking to Collapse all but one of our Sites, then "demoting" the remote SEPMs to GUPs, and implementing a Public facing SEPM for Redundancy.  I have already started collapsing those sites that only have 200-400 clients and I am seeing a dramtic improvement in replication and performance in our SEP Infrastructure.

    SEPM replication is one of those technologies that looked great on paper, and even in a lab however when it went into a live environement just didn't stack up. 


  • 8.  RE: Replication problem

    Posted Jan 25, 2010 03:10 PM
     Thanks JMarauth  i tried your advices and now i started the replication process again,i'll be reply when it'll finish.

    Thanks


  • 9.  RE: Replication problem

    Posted Jan 26, 2010 10:48 AM
     Nope,It's doesn't work :(

    Any ideas?


  • 10.  RE: Replication problem

    Posted Jan 26, 2010 10:51 AM
    Nope,It's doesn't work :(

    Any ideas?



  • 11.  RE: Replication problem

    Posted Jan 26, 2010 10:57 AM
     Open ODBC - System DSN -Symantec Endpoint.....-- Configure - Network -Idle Timeout - ( default is 240 mins =4 hrs) change it to somewhere between 7-10 hrs say 600 .
    Then run replication again.


  • 12.  RE: Replication problem

    Posted Jan 26, 2010 11:30 AM
     Thanks Vikram
    I did network idle timeout like 600 both of sites and re-run replication,now i'm waiting :)


  • 13.  RE: Replication problem

    Posted Jan 26, 2010 11:40 AM
     Hello Vikram,
    Central server creates replication files in the outbox of replication folder but total size of that folder is nearly 670 mb,but my db is over 5gb.
    Is it a problem?
    I think the data folder may nearly same size with db on the first replication.

    note:
    It creates a folder in the replication folders inbox but no files coming here and i see no other network traffic between two machine.


  • 14.  RE: Replication problem

    Posted Jan 26, 2010 12:20 PM
     If you are using a older version of SEPM then you can use the dbunload tool to shrink the database.
    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008022616103648


  • 15.  RE: Replication problem

    Posted Jan 26, 2010 12:23 PM
     I'm using RU5 but also now trying to shrinking.


  • 16.  RE: Replication problem

    Posted Jan 26, 2010 12:31 PM
    In RU5 4 GB is system requirement for the database

    Hard Drive: 4 GB for the server, plus an additional 4 GB for the database
    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009072315265848 

    So 5 gb shouldn't be a lot..
    make sure your replication partner is also RU5


  • 17.  RE: Replication problem

    Posted Jan 26, 2010 12:48 PM
     My replication partner also RU5 and i think you misunderstood me,
    i mean my db size is over 5 gb, i have nearly 400 gb free space on both machine.


  • 18.  RE: Replication problem

    Posted Jan 26, 2010 01:09 PM
     I finished the shrinking and db size is now 3 gb.
    I also uninstall and reinstall replication site again and tried to replicate again but nothing change.
    I realized that the size(676 MB) of replication outbox folder same on every replication try(i always delete the folders in the outbox folder on every failure replication)
    I got these on the central servers db out.log and i also tried to change cache size from default to 1024mb as seen on the log. Any ideas,is it possible about disk fragments or no unique index key errors?

    I. 01/26 19:52:45. Running on Windows 2003 Build 3790 Service Pack 2
    I. 01/26 19:52:45. 1048576K of memory used for caching
    I. 01/26 19:52:45. Minimum cache size: 1048576K, maximum cache size: 1048576K
    I. 01/26 19:52:45. Using a maximum page size of 8192 bytes
    I. 01/26 19:52:45. Starting database "sem5" (C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db) at Tue Jan 26 2010 19:52
    I. 01/26 19:52:45. Performance warning: Database file "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" consists of 2202 disk fragments
    I. 01/26 19:52:46. Transaction log: sem5.log
    I. 01/26 19:52:46. Starting checkpoint of "sem5" (sem5.db) at Tue Jan 26 2010 19:52
    I. 01/26 19:52:46. Finished checkpoint of "sem5" (sem5.db) at Tue Jan 26 2010 19:52
    I. 01/26 19:52:46. Database "sem5" (sem5.db) started at Tue Jan 26 2010 19:52
    I. 01/26 19:52:46. Database server started at Tue Jan 26 2010 19:52
    I. 01/26 19:52:46. Trying to start SharedMemory link ...
    I. 01/26 19:52:46.     SharedMemory link started successfully
    I. 01/26 19:52:46. Trying to start TCPIP link ...
    I. 01/26 19:52:46. Starting on port 2638
    I. 01/26 19:52:46.     TCPIP link started successfully
    I. 01/26 19:52:46. Now accepting requests
    I. 01/26 19:52:54. Performance warning: No unique index or primary key for table "SERVER_SYSTEM_LOG_1" in database "sem5"
    I. 01/26 19:52:57. Starting checkpoint of "sem5" (sem5.db) at Tue Jan 26 2010 19:52
    I. 01/26 19:52:58. Finished checkpoint of "sem5" (sem5.db) at Tue Jan 26 2010 19:52
    I. 01/26 19:52:58. Starting checkpoint of "sem5" (sem5.db) at Tue Jan 26 2010 19:52
    I. 01/26 19:52:58. Finished checkpoint of "sem5" (sem5.db) at Tue Jan 26 2010 19:52
    I. 01/26 19:52:58. Starting checkpoint of "sem5" (sem5.db) at Tue Jan 26 2010 19:52
    I. 01/26 19:52:58. Finished checkpoint of "sem5" (sem5.db) at Tue Jan 26 2010 19:52
    I. 01/26 19:52:58. Starting checkpoint of "sem5" (sem5.db) at Tue Jan 26 2010 19:52
    I. 01/26 19:52:58. Finished checkpoint of "sem5" (sem5.db) at Tue Jan 26 2010 19:52
    I. 01/26 19:53:07. Performance warning: No unique index or primary key for table "SERVER_ADMIN_LOG_1" in database "sem5"
    I. 01/26 19:53:15. Performance warning: No unique index or primary key for table "SERIAL_NUMBERS" in database "sem5"



  • 19.  RE: Replication problem
    Best Answer

    Posted Jan 27, 2010 06:42 AM
    No way,i opened a case and waiting for response :(