what could be the problem?
Fatal error: Maximum function nesting level of '150' reached, aborting! in
http://jsfiddle.net/9faSV/
Related
Try to install a new c5-8.3.1 without result. I try php 5.6.32 and php 7.0.26 with the same errors.
When I try to install with the full site, Installation crashes during the import files session with error:
An exception occurred while executing 'SELECT t0.fslName AS fslName_1, t0.fslConfiguration AS fslConfiguration_2, t0.fslID AS fslID_3, t0.fslIsDefault AS fslIsDefault_4 FROM FileStorageLocations t0 WHERE t0.fslIsDefault = ? LIMIT 1' with params [1]: Error while sending QUERY packet. PID=5877.
Trace:
0 /home/u960240172/public_html/new/concrete/vendor/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(855):
Doctrine\DBAL\DBALException::driverExceptionDuringQuery(Object(Concrete\Core\Database\Driver\PDOMySqlConcrete5\Driver),
Object(Whoops\Exception\ErrorException), 'SELECT t0.fslNa...', Array)
.. follows 30 traces
When I try the Empty site option, it goes through, but when I log in as an Admin I get another error:
An unexpected error occurred.
An exception occurred while executing 'SHOW FULL TABLES WHERE Table_type = 'BASE TABLE'': SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
Any Idea?
This is a MySQL server error, not concrete5's.
See: Error while sending QUERY packet
Error while sending QUERY packet
I'm using sas management console to schedule job. The job end almost immediately and the error i recieve by email is :
Exited with exit code 116.
Resource usage summary:
CPU time : 0.28 sec.
Max Memory : 14 MB
Total Requested Memory : -
Delta Memory : -
(Delta: the difference between total requested memory and actual max usage.)
The output (if any) follows:
ERROR: Unrecognized SAS option name LOGU+00A0/FILEPATH/LOGNAME.LOG.
ERROR: (SASXKRIN): KERNEL RESOURCE INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.
Any ideas what the issue could be ?
Thanks in advance!
I scheduled around 70 concurrent queries using 70 logins to stress test Azure DW (DWU 200) and after a while started getting this error
[Execute SQL Task]
Error: Executing the query "SELECT Distinct S.[Nurse ID],S.[Trust Code],S.[Loc..." failed with the following error: "110802;An internal DMS error occurred that caused this operation to fail.
Details:
Exception: Microsoft.SqlServer.DataWarehouse.DataMovement.Workers.DmsSqlNativeException, Message: NativeOdbcConnection.Open, error in OdbcConnectionCreate: SqlState: HY000, NativeError: 10928, 'Error calling: SQLExecDirect(hstmt, (SQLWCHAR *) L"SELECT ##SPID", SQL_NTS), SQL return code: -1 |
SQL Error Info: SrvrMsgState: 1, SrvrSeverity: 20, Error <1>: ErrorMsg: [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Resource ID : 1. The request limit for the database is 1600 and has been reached. See 'http://go.microsoft.com/fwlink/?LinkId=267637' for assistance. |
ConnectionString: Driver={pdwodbc};APP=TypeC01-DmsNativeReader:DB22\mpdwsvc (69820)-ODBC;Trusted_Connection=yes;AutoTranslate=no;Server=\\.\pipe\DB.22-f8e91ff83e68\sql\query, ConnectionPooling: 1 | Error calling: pConn->Create(connectionString, useConnectionPooling, packetSize, connectionLoginTimeout, environmentSettings, spid) | state: FFFF, number: 19183, active connections: 266', Connection String: Driver={pdwodbc};APP=TypeC01-DmsNativeReader:DB22\mpdwsvc (69820)-ODBC;Trusted_Connection=yes;AutoTranslate=no;Server=\\.\pipe\DB.22-f8e91ff83e68\sql\query".
Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
But I can't find a corresponding 1600 limit, neither can I understand how I could have hit it? Any help would be truly appreciated, thanks.
Have you read the concurrency article on Azure.com? You are stress testing at 70 concurrent queries at a scale level that will, by design begin queueing those requests. My suspicion is that your queue of queued requests is increasing throughout your load test until you hit one of the limits in the system. The limit I expect you are hitting is the number of open sessions.
If you would like to be certain that is the case then you would need to open a support ticket. However, I would also suggest increasing the DWU to a higher figure if you want to run at 70 concurrent queries in a saturated load test.
We are getting deadlocks inside DMS at least 30% of the time or more on several of the larger sprocs which truncate and insert several million rows. However, there is only one query running, so I don't see how the deadlock can be my fault:
Msg 110802, Level 16, State 1, Line 1
110802;An internal DMS error occurred that caused this operation to fail. Details: Exception: Microsoft.SqlServer.DataWarehouse.DataMovement.Workers.DmsSqlNativeException, Message: SqlNativeBufferReader.Run, error in OdbcExecuteQuery: SqlState: 40001, NativeError: 1205, 'Error calling: SQLExecDirect(this->GetHstmt(), (SQLWCHAR *)statementText, SQL_NTS), SQL return code: -1 | SQL Error Info: SrvrMsgState: 71, SrvrSeverity: 13, Error <1>: ErrorMsg: [Microsoft][ODBC Driver 11 for SQL Server][SQL Server]Transaction (Process ID 2265) was deadlocked on lock | generic waitable object resources with another process and has been chosen as the deadlock victim. Rerun the transaction. | Error calling: pReadConn->ExecuteQuery(statementText, bufferFormat) | state: FFFF, number: 7801, active connections: 120', Connection String: Driver={pdwodbc};APP=TypeC01-DmsNativeReader:DB3\mpdwsvc (13732)-ODBC;Trusted_Connection=yes;AutoTranslate=no;Server=\\.\pipe\DB.3-b6c0a7b26544\sql\query
And:
110802;An internal DMS error occurred that caused this operation to fail. Details: Exception: Microsoft.SqlServer.DataWarehouse.DataMovement.Workers.DmsSqlNativeException, Message: SqlNativeBufferReader.Run, error in OdbcExecuteQuery: SqlState: 40001, NativeError: 1205, 'Error calling: SQLExecDirect(this->GetHstmt(), (SQLWCHAR *)statementText, SQL_NTS), SQL return code: -1 | SQL Error Info: SrvrMsgState: 71, SrvrSeverity: 13, Error <1>: ErrorMsg: [Microsoft][ODBC Driver 11 for SQL Server][SQL Server]Transaction (Process ID 804) was deadlocked on lock | generic waitable object resources with another process and has been chosen as the deadlock victim. Rerun the transaction. | Error calling: pReadConn->ExecuteQuery(statementText, bufferFormat) | state: FFFF, number: 8106, active connections: 240', Connection String: Driver={pdwodbc};APP=TypeC01-DmsNativeReader:DB38\mpdwsvc (14728)-ODBC;Trusted_Connection=yes;AutoTranslate=no;Server=\\.\pipe\DB.38-b6c0a7b26544\sql\query
Does this point at something obvious to check or fix? Or is an Azure support case the best road to a resolution?
update: support case 115111713384329 is open for this issue
update: our SQL DW got a new update March 4, 2016 which supposedly fixes this issue. (I can't reproduce it on demand so I can't say for sure.) If you run "select ##version" then
10.0.8224.5 or higher should have the fix. If you don't have the fix yet I would imagine opening a support case and requesting it or waiting a few weeks would get you the fix.
Creating an Azure support case would be best in this case. If you can share your stored procedure, that would help us root cause.
I am currently having problems with a MPI Application.
I am sporadically receiving MPI errors of the form:
Fatal error in MPI_Allreduce: Message truncated, error stack:
MPI_Allreduce(1339)...............: MPI_Allreduce(sbuf=0x7ffa87ffcb98, rbuf=0x7ffa87ffcba8, count=2, MPI_DOUBLE, MPI_SUM, MPI_COMM_WORLD) failed
MPIR_Allreduce_impl(1180).........:
MPIR_Allreduce_intra(755).........:
MPIDI_CH3U_Receive_data_found(129): Message from rank 0 and tag 14 truncated; 384 bytes received but buffer size is 16
rank 1 in job 1 l1442_42561 caused collective abort of all ranks
exit status of rank 1: killed by signal 9
However I do not know at where to look. I know that the error is happening in an Allreduce function call however there are multiple ones.
How do I know which function call produces the error? Simple printf debugging does not help as the function could be called a million times before the error occurs the first time.
It might also not occur at all or immediately after the start of the program.
I have been able to track down the origin of the error by calling
MPI_Errhandler_set(MPI_COMM_WORLD, MPI_ERRORS_RETURN)
and then checking the return value of each of the Allreduce functions for not being equal to MPI_SUCCESS. This is a location where an error occurs