Whirly Posted August 29, 2013 Report Share Posted August 29, 2013 Hello, I've got an installation of plastic SCM running on a windows server. It uses a mysql backend located on an Synology NAS. We started using Plastic almost one year ago and everything was fine. Today somebody tried to create a new repository on the server but he is unable to do so. We tried on several different computers using different account to no avail. In the server logfile we've got : 2013-08-29 16:40:32,989 00000000-0000-0000-0000-000000000000 AUTORITE NT\Système at JADE ERROR Operations - Plastic server version: 4.1.10.473 2013-08-29 16:40:32,989 00000000-0000-0000-0000-000000000000 AUTORITE NT\Système at JADE ERROR Operations - OnError catching exception The database scmrep_37 can't be created. Check the server log (plastic.server.log). Error: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. 2013-08-29 16:40:33,147 AUTORITE NT\Système at ERROR Codice.CM.Server.ExceptionTracerSink - Dumping in-transit exception:The database scmrep_37 can't be created. Check the server log (plastic.server.log). Error: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. 2013-08-29 16:40:33,150 AUTORITE NT\Système at INFO ChannelCall - recb: 542|rect: 0|sentb: 1595|sendt: 0|prt: 37031|th: 3356|dest: 0|mt: 37031|sert: 0|zip: 0| 192.168.1.94|CreateRepository 2013-08-29 16:40:47,926 (null) AUTORITE NT\Système at (null) INFO Channel - conn 1 Une connexion existante a dû être fermée par l’hôte distant When I have a look at the server, the table is created in the database. All others functions are working fine, we can update, commit and use the branch explorer without any problem. Any idea ? Link to comment Share on other sites More sharing options...
calbzam Posted August 30, 2013 Report Share Posted August 30, 2013 Hi, There is a timeout error when creating the databases. You can try to add a "Connection Timeout" stament into your db.conf file (C:\Program Files\PlasticSCM4\server\db.conf). You should have something similar to this: <DbConfig> <ProviderName>mysql</ProviderName> <ConnectionString>Server=localhost;User ID=root;Password=mypwd;Database={0};Pooling=true;Connection Timeout=120</ConnectionString> <DatabasePath></DatabasePath></DbConfig> You can try to increase the timeout on the MySQL server side. These links show you how doing it: http://edwin.baculso...ection-timeout/ http://forums.oscomm...ut-in-mysqlphp/ Once the timeout issue is solved, I think the databases will be created properly. Do you have any firewall? Regards, Carlos Link to comment Share on other sites More sharing options...
Whirly Posted August 30, 2013 Author Report Share Posted August 30, 2013 I forgot to add that I've done just that. Even with a 120s timeout I still got the same problem except that now the client wait longer before displaying the error message. Link to comment Share on other sites More sharing options...
calbzam Posted September 4, 2013 Report Share Posted September 4, 2013 Hi, It´s a bit strange. Can you also check if the user who creates the repository has permissions in Plastic and also you have "path permissions" in your repository folder? You can also change the connection timeout on the MySQL side: http://edwin.baculsoft.com/2010/11/set-mysql-connection-timeout/ Regards, Carlos Link to comment Share on other sites More sharing options...
Whirly Posted September 10, 2013 Author Report Share Posted September 10, 2013 Seems that after a couple days this problem solved itself. Thanks, Stéphane Link to comment Share on other sites More sharing options...
calbzam Posted September 11, 2013 Report Share Posted September 11, 2013 Good to know! It sounds more like a network issue. Regards, Carlos Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.