Why does 1s in enterprise mode freeze at the stage of loading configuration information?

Question

1C

There is a win2008r2 server, it has a platform 8.3 and Postgressql, several databases of different configurations hang, about 50 people work in different databases
recently (before that it worked fine for about a year) 1s works terribly: at any moment any database can stop opening in enterprise mode, 1c just hangs after selecting the base and that's it. Opens in configurator mode. This happens almost every day, it is treated only by rebooting 1s of the server. Tell me, please, where to dig and what could be the matter, and how to find on which side the error is - 1s or postgres ..

Answer 1

The solution was to set the "sleep sessions" shutdown time to 1 hour in the IB settings in the configurator. Sending rays of death 1s.

Answer 2

1) look at the amount of memory allocated by rphost on the 1C server. If you have an x32 version of the server, then the process will be able to use a maximum of 1.75 GB of RAM
. If there is not enough memory, the server cannot accept new connections or hangs when the current session needs additional memory
www.viva64.com/ru/k/0036
2) Look settings "Working server settings" may be set to incorrect settings. I had the same problem and the server kept crashing. My settings are in attachment. The server is allocated 11 GB.
3) There may be problems in setting up Postgressql.
Provide your server characteristics, database sizes, Postgressql configs. It's hard to say without information.
My PostgreSQL config: https://drive.google.com/file/d/0B2qGCc-vzEVDMERVW...
this config is matched to the available amount of RAM.
PostgreSQL installed on Linux, 3 GB RAM, 3 CPU cores.
1C8 server: 11 GB of RAM, 5 CPU cores,
4 bases approximately 1 GB each (uploaded in dt)
Give all the characteristics of your server: 1C8 server and database, physical or virtual, operating system, amount of RAM on each server, what CPU, how much RAM is occupied rphost processes, how many are there? Are you using a RAID array?
Previously, I myself used PostgreSQL, but, in the process, I encountered some problems when working with the database on PostgreSQL and recently switched to MS SQL.
Your server is not bad for data bases. In order to use PostgreSQL, you need to be very good at configuring it. When the bases are small, many tuning errors are "forgivable". When we just started implementing 1C + PostgreSQL, we also had very frequent problems with the database (there were frequent freezes, it worked slowly). PostgreSQL is better to use on Linux than on windows. I myself am not a database specialist, to set up the database server we hired a specialist from 1Sbit and he set it up for us and there were no problems in work after that.
Tip:
Do not be stingy with your databases, hire a database specialist who can set it up for you. One person cannot be an expert in everything.
1) how long ago did you check the database itself and reindex? VACUUM and REINDEX
2) Have you done testing and fixing the database using 1C for a long time?
3) is the database log file moved to a separate HDD?
4) Is the HDD heavily loaded?
Consider switching to MS Sql, often it requires "virtually" no configuration and is easier to use. Unlike PostgreSQL, MS Sql is ready to work out of the box, but PostgreSQL needs to be configured.
If you have any questions, write, maybe I can help in Skype: tisartisar
Hire a database setup specialist
Why did we switch to MS SQL:
we use the UT configuration and at the end of the month sometimes there were errors that could not be solved in any way. If you transfer the database to file mode and start closing the month, then everything was closed normally, the same database was uploaded to the PostgreSQL server when calculating the cost, errors occurred. At that moment, we were half a year behind in closing months due to the occurrence of floating errors. We created a test database on MS SQL and the month that could not be closed on PostgreSQL on MS Sql was closed. Also rounding of prices in the price list does not work correctly on PostgreSQL. In fact, the work of 1C on PostgreSQL is supported, but it is still recommended to use MS SQl.
Because of this, it was decided to switch to MS SQL. the stability of 1C is more expensive.
I'm glad I could help, please contact me if you have any questions or problems.
1) how much memory is allocated to MS SQL server? this is configured in the MS SQL server itself.
2) Test the database using 1C tools regularly
3) an article on how to set up backup and maintenance. This is important and should be done regularly. I do every day. Check out all 3 parts of the guide. interface31.ru/tech_it/2012/02/observation-baz-1...