Untitled

Oh no!!

We had a machine reporting some data to a Java service. The service suddenly started giving errors like : 

com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2106-05-04 11:01:31' for column 'Timestamp' at row 1        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4094)        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4028)        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2490)        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2683)

Caused by: org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; SQL [INSERT INTO TableT1(Timestamp, a,b,c) VALUES(?, ?, ?, ?)]; Data truncation: Incorrect datetime value: '2106-05-04 11:01:31' for column 'Timestamp' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2106-05-04 11:01:31' for column 'Timestamp' at row 1        at org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.doTranslate(SQLStateSQLExceptionTranslator.java:102)        at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:73)        at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81)        at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81)        at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:660)        at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:909)

it baffled us all at first, the reporting machine was running all fine and the data send seemed all legit at the reporting machine (checked from the logs).

We googled and searched a lot, and just then somebody near me said “wait a minute doesnt the date time look odd to you. 

well it read 2106-05-04 10:23:22 :) 

We contacted the server admin, why was the server on wrong date and he said due to some maintenance work the datetime drifted and he ran the date --set command.