Re: Re: Re: Administration of command line external gateway client
Aldevinas Katkus
4-30-18
The problem was that the server .exe name has an ending with "64". I have copied the slave executable to StandardERPServer64-Slave and it looks the main exe is trying to start the slave, but cannot. It's the same problem we have faced a few months ago (Slave exe thinks there is no RAM):


2018-04-30 08:52:27 Application shutdown properly...
2018-04-30 12:00:33 (-1) database cache may be max 80% of physical RAM (physical
RAM is: 0bytes, attempted to use: 100000bytes for DB cache)
2018-04-30 12:00:33 (-1) Exit


It may be related to our virtual server (Centos 7) configuration I guess, because the gateway runs on the Centos 7 on another virtual server.
Any more ideas?
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Latest Posts
David Delač
Hi Gastón, Please report a bug in our issue tracker and attach test database that you can repeat this in so I can have a look. Paste subject here once done...
09:46 14 May 2025
Paul Timms
From what I've read, using these will store the updated records in memory and then write them to the database in bulk, instead of each record writing to the database in turn. So perhaps there&apo...
17:53 29 Apr 2025