Meshlium stopped syncing with external database

Development questions: create new plugins, add new features...
libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

Re: Meshlium stopped syncing with external database

Post by libelium-dev » Tue Apr 18, 2017 9:51 am

Hi,

Please empty large log files and try again, use these commands:

Code: Select all

> /mnt/user/logs/db_sync.log

Code: Select all

> /mnt/user/logs/syncDB.log

Code: Select all

> /mnt/user/logs/sensorParser.log
Then check if errors still appears. Show our your thoughts.

Regards

JeffreyArts
Posts: 35
Joined: Thu Sep 01, 2016 4:39 pm

Re: Meshlium stopped syncing with external database

Post by JeffreyArts » Tue Apr 18, 2017 11:38 am

Hey libelium-dev,

I have deleted the specified log files. The Meshlium is now working and accessible again.

Also, the Wifiscanner is working: the data is successfully retrieved and synchronised to the external database.
However, the sensorParser is still not synchronising its data to the external database.

Thanks for the help.

libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

Re: Meshlium stopped syncing with external database

Post by libelium-dev » Tue Apr 18, 2017 11:55 am

Hi JeffreyArts,

Please show us the ouput for the sensorParser.log file:

Code: Select all

tail -f /mnt/user/logs/sensorParser.log
Also perform a ping to your external IP:

Code: Select all

ping YOUR_EXTERNAL_IP_DB

Code: Select all

> /mnt/user/logs/db_sync.log
Run your synchronization again and show us the output for external synchronization log:

Code: Select all

tail -f /mnt/user/logs/db_sync.log
Check again your external database synchronization and show us the output for the files and commands.

Regards

JeffreyArts
Posts: 35
Joined: Thu Sep 01, 2016 4:39 pm

Re: Meshlium stopped syncing with external database

Post by JeffreyArts » Tue Apr 18, 2017 1:37 pm

Hey libelium-dev,

Here is the sensorParser.log:
http://chopapp.com/#vjkkw2hn

This is a short snippet from the ping result to our external database:

Code: Select all

64 bytes from IP_WAS_HERE: icmp_seq=1 ttl=55 time=13.8 ms
64 bytes from IP_WAS_HERE: icmp_seq=2 ttl=55 time=12.6 ms
Here is the db_sync.log. Just prior to this, I pressed the 'synchronise now' button, to synchronise the sensorparser.
http://chopapp.com/#xmubjcix

Thanks for the help.

libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

Re: Meshlium stopped syncing with external database

Post by libelium-dev » Tue Apr 18, 2017 2:40 pm

Hi JeffreyArts,

Code: Select all

tail -f /mnt/user/logs/syncDB.log
Please show us the output of this file too.

Also check that sensorParser is running:

Code: Select all

ps aux | grep sensorParser.jar
Regards

JeffreyArts
Posts: 35
Joined: Thu Sep 01, 2016 4:39 pm

Re: Meshlium stopped syncing with external database

Post by JeffreyArts » Fri Apr 21, 2017 9:58 am

Hey libelium-dev,

Here is a snipped from my syncDB log. There's more but I think this indicates what the problem might be:

Code: Select all

2017-04-18 13:24:49.528 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:14:05.0' for column 'timestamp' at row 1
2017-04-18 13:24:49.558 - Error synchronizing with remote DB.

2017-04-18 13:24:49.559 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:14:05.0' for column 'timestamp' at row 1
2017-04-18 13:24:49.587 - Error synchronizing with remote DB.

2017-04-18 13:24:49.588 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:14:05.0' for column 'timestamp' at row 1
2017-04-18 13:24:49.613 - Error synchronizing with remote DB.

2017-04-18 13:24:49.614 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:14:25.0' for column 'timestamp' at row 1
2017-04-18 13:24:49.639 - Error synchronizing with remote DB.

2017-04-18 13:24:49.64 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:14:25.0' for column 'timestamp' at row 1
2017-04-18 13:24:49.668 - Error synchronizing with remote DB.

2017-04-18 13:24:49.669 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:14:25.0' for column 'timestamp' at row 1
2017-04-18 13:24:49.697 - Error synchronizing with remote DB.

2017-04-18 13:24:49.698 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:14:25.0' for column 'timestamp' at row 1
2017-04-18 13:24:49.725 - Error synchronizing with remote DB.

2017-04-18 13:24:49.726 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:14:44.0' for column 'timestamp' at row 1
2017-04-18 13:24:49.974 - Error synchronizing with remote DB.

2017-04-18 13:24:49.975 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:14:44.0' for column 'timestamp' at row 1
2017-04-18 13:24:50.002 - Error synchronizing with remote DB.

2017-04-18 13:24:50.003 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:14:44.0' for column 'timestamp' at row 1
2017-04-18 13:24:50.031 - Error synchronizing with remote DB.

2017-04-18 13:24:50.032 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:14:44.0' for column 'timestamp' at row 1
2017-04-18 13:24:50.063 - Error synchronizing with remote DB.

2017-04-18 13:24:50.064 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:15:02.0' for column 'timestamp' at row 1
2017-04-18 13:24:50.1 - Error synchronizing with remote DB.

2017-04-18 13:24:50.101 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:15:02.0' for column 'timestamp' at row 1
2017-04-18 13:24:50.129 - Error synchronizing with remote DB.

2017-04-18 13:24:50.139 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:15:02.0' for column 'timestamp' at row 1
2017-04-18 13:24:50.165 - Error synchronizing with remote DB.

2017-04-18 13:24:50.166 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:15:02.0' for column 'timestamp' at row 1
2017-04-18 13:24:50.193 - Error synchronizing with remote DB.

2017-04-18 13:24:50.194 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:15:21.0' for column 'timestamp' at row 1
2017-04-18 13:24:50.225 - Error synchronizing with remote DB.

2017-04-18 13:24:50.226 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:15:21.0' for column 'timestamp' at row 1
2017-04-18 13:24:50.255 - Error synchronizing with remote DB.

2017-04-18 13:24:50.256 - DETAILED INFO: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Incorrect datetime value: '2017-03-26 01:15:21.0' for column 'timestamp' at row 1
2017-04-18 13:24:50.258 - Synchronization OK
'ps aux | grep sensorParser.jar' returns the following result:

Code: Select all

meshlium_2f84:~# ps aux | grep sensorParser.jar
root      4564  0.5  7.4 250376 19004 ?        Sl   Apr18  23:35 java -jar /bin/sensorParser.jar bt
root     17320  0.0  0.2   2968   640 pts/0    S+   09:50   0:00 grep sensorParser.jar
Any idea why the timestamp is giving an error? I got another Meshlium setup to the same external database, which is synchronising without any problems.

libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

Re: Meshlium stopped syncing with external database

Post by libelium-dev » Fri Apr 21, 2017 10:50 am

Hi JeffreyArts,

Please can you tell us which version of manager system do your Meshliums have? Do Meshliums have the same version of Manager System?


Regards

JeffreyArts
Posts: 35
Joined: Thu Sep 01, 2016 4:39 pm

Re: Meshlium stopped syncing with external database

Post by JeffreyArts » Fri Apr 21, 2017 11:31 am

Hey libelium-dev,

Both of the meshliums are updated to the latest version: 3.2.7.

JeffreyArts
Posts: 35
Joined: Thu Sep 01, 2016 4:39 pm

Re: Meshlium stopped syncing with external database

Post by JeffreyArts » Fri Apr 21, 2017 11:48 am

Hey libelium-dev,

I checked the 'Time Synchronization' in both the Meshliums.
The working Meshlium seems to be using:

Code: Select all

Fri Apr 21 11:31:10 CEST 2017
Where as the non-functional Meshlium is using the following 'Time Synchronization' settings:

Code: Select all

Fri Apr 21 11:40:01 UTC 2017
I tried setting the timezone of the latter Meshlium to 'CEST' but it does not appear to be in the list. Which option should be selected in order for it to use the 'CEST' timezone?

libelium-dev
Posts: 27967
Joined: Mon Sep 28, 2009 1:06 pm

Re: Meshlium stopped syncing with external database

Post by libelium-dev » Fri Apr 21, 2017 12:02 pm

Hi JeffreyArts,

You can synchronize your time with this command:

Code: Select all

ntpdate pool.ntp.org
Please, tell us your toughts.

Regards

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest