forums › forums › Monyog › Monyog Deployment › Too Many 'aborted Connections' Received
Tagged: #aborted_connects #abort
- This topic is empty.
- 
		AuthorPosts
- 
		
			- 
December 22, 2015 at 12:52 pm #35589pankajk1608 ModeratorHello, Please provide us with the following information: 1. Are you using a direct connection or ssh connection to connect to your server through MONyog? 2. Is the user specified in the above error being used in any other applications other than MONyog? 3. Do you have any CSO (Custom SQL Object) enabled in MONyog? 4. Please send us the MONyog.log file, based on your installation and OS it can be found at: Windows: ProgramDataWebyogMONyogMONyog.log Linux System: for RPM: /usr/local/MONyog/MONyog.log 
 for .tar: /MONyog/MONyog.logAlso, please create a support ticket at [email protected], and we will continue there. Regards, Pankaj Team MONyog. 
- 
December 22, 2015 at 5:00 pm #35590monyog_user Member1. direct connections 2. user is only used from the application to connect to DB 3. Pre-existing CSOs are enabled 4. Every few hours , a series of messages repeat WARNING : Possible SQLite DB corruption ( has existed before the outage inour logs) Received signal SIGKILL/SIGSTOP…….. — IGNORING SIGNAL Monyog signaled to syop Monyog stopped Monyog is starting Monyog started 
- 
December 23, 2015 at 7:44 am #35591pankajk1608 ModeratorHello, We have upgraded our SQLite library in our latest release MONyog-6.51, can you please upgrade and see if the problem persists? Also, please send us the complete MONyog.log file to “[email protected]”, so that we could look into the issue. Regards, Pankaj Team MONyog. 
 
- 
- 
		AuthorPosts
- You must be logged in to reply to this topic.
