500 error with loc_longitude

  • Resolved sebs42

    (@sebs42)


    8 years, 1 month ago

    Hi Pierre,

    I ran into another problem:

    Event log reports an error 500 (is this http 500?):

    Inconsistent data to insert in data table: Array
(
    [device_id] => yy:00:00:00:00:01
    [device_name] => Merkur
    [module_id] => 00:00:00:00:00:01
    [module_type] => NAComputed
    [module_name] => [Computed Values]
    [measure_timestamp] => 2017-02-01 09:08:38
    [measure_type] => loc_longitude
    [measure_value] => 
)

    Here’s my realtime.txt: https://www.schwarzwaldgeier.de/realtime.txt

    01/02/2017 08:02:01 4.5 78.98 0 0 0 0 0.0 0.0 1018.84 N 0 km/h C hPa mm 0.0 +0.0 0.0 0.0 0.0 20.0 50 4.5 +0.0 4.5 08:02 4.5 08:02 0 08:02 0 08:02 1024.25 08:02 1024.25 08:02 1.8.7 819 0 0 0 0 0 0 0 0 0 1 0 N 1700 m 4.5 1 420.1 1

    it still contains a lot of fake/placeholder data, as it is work in progress. But it should be valid, as far as I can tell.

    According to the realtime.txt specifications I could find, the file doesn’t include a longitude anyway.

    So I checked the add/edit station dialog. No matter which format I try, on saving, it floors latitude and longitude to their integer values, i.e. 48.764444, 8.280556 becomes 48 and 8. (which is quite a bit off). I tried most of the formats on https://goo.gl/0PzlQH, with no success.

    How do I add the coordinates the right way? Or is ist a realtime.txt problem? Or something else?

    Thanks in advance and sorry for opening yet another ticket, I just thought it might be easier to search that way for others.

    • This topic was modified 8 years, 1 month ago by sebs42. Reason: formatting
Viewing 14 replies - 1 through 14 (of 14 total)
  • Pierre Lannoy

    (@pierrelannoy)

    Hello!

    And thanks for the detection of this issue. You’re right there’s something wrong with coordinates management for realtime-based stations: it must not be truncated, but for now it is (OMG, how could I let such a bullshit in my code?).
    I will do the fix this afternoon and publish it as new version (3.0.11). I’ll keep you informed as soon as it is available for download. In any case, it will be before 23:00 UTC…

    The error (Inconsistent data to insert in data table) is more strange. The error number is not http code – it’s internal convention so it does not matter too much, especially in this case. For a reason I don’t know, the Weather Collector subsystem try to insert a null value. Of course, I can reassure you, the error is stopped before corrupting the database (hence the reason for this event).
    What is strange for me is I set your station on my server and I have not this error. Do you have modified your txt file since you see this error?

    PS: for coordinates, you’re right, it’s a dot for decimal separator.
    PS2: sorry again for this beginner error on truncated coordinates :-/

    Pierre Lannoy

    (@pierrelannoy)

    Actually, I had time to do it. The update is available. Tell me if it solves your truncated coordinates issue…

    Thread Starter sebs42

    (@sebs42)

    Hey, thank you so much! This solved the coordinates issue.

    I’m still stuck with the 500 error. It doesn’t seem to be a server config thing, I tried all variants like https, local file etc.

    I have modified the file since my last post, replacing more placeholders with actual values etc., but no change in the event log.

    That said, since the only problem is the log pollution, I can live with it. Everything else works as it should. If the issue is important to you, I’ll give you any information you need, just ask. If not, I’ll just set another log level.

    And please, do not apologize! Bugs just happen, and this is probably the first time ever I open an issue and get a fix within hours.

    I’m very grateful for the plugin since I’m now beginning to grasp its power. Not just for output, I had always tried to find some way to connect our dated hardware to modern services like wunderground, and thanks to you this is now possible by creating a simple text file.

    • This reply was modified 8 years ago by sebs42.
    Pierre Lannoy

    (@pierrelannoy)

    Thanks to you, I am always very happy when the plugin can be used for a use to which I had not thought;)

    For the error 500, I have not a beginning of explanation ??
    Here is what we will do: in about 20-22 days (maximum), I will publish 3.1.0 version which have many new features. I will incorporate it some special routines to (try to) find from where the issue come from. And if that is not enough, then we will see how to do otherwise.
    In all cases, for now, the only pollution will be that of the events log. Also, no big worries to have.

    I let opened this topic, and we will try to close it when 3.1.0 will be deployed ??

    Thread Starter sebs42

    (@sebs42)

    Sure! Please drop a note here when 3.1.0 is deployed, I have too many plugins and might miss it.

    • This reply was modified 8 years ago by sebs42.
    Thread Starter sebs42

    (@sebs42)

    Update: I added a nearby wunderground station to my site, and she gets the same error. This means the error isn’t caused by my realtime.txt. I suspect it has to do with my server config, but I haven’t found anything yet.

    Pierre Lannoy

    (@pierrelannoy)

    Hello!

    Did you know your PHP version and the OS “stack” of your server?

    Thread Starter sebs42

    (@sebs42)

    PHP 7.0.13-0ubuntu0.16.04.1, Apache, Ubuntu 16.04.1 LTS Server.

    Hello sebs42.

    I think I’ve found a reason (and a solution) for your issue.
    Could you confirm me that the problem only appears for coordinates (latitude and/or longitude)?

    Thread Starter sebs42

    (@sebs42)

    Hi Pierre,

    I can confirm that. The log flooding errors are all lat/long related, as in the example in my first post. Thanks for looking into the issue!

    Great!
    The 3.1 version of the plugin will fixe this issue.
    I plan to release it at the end of this week or the beginning of the next week. I keep you informed when it’s done.

    Thanks again.
    Pierre

    Hello.
    The new release is available for update… Could you try if it solve your issue?

    Thanks
    Pierre

    Thread Starter sebs42

    (@sebs42)

    Hi Pierre,

    Yes, I can confirm the update fixed the issue for me. The log flooding stopped right after the update related entries.

    Thank you!
    Sebastian

    Hi Sebastian!

    Thank you for this great news!
    And don’t hesitate to come back if you have any other issue… And if you’re happy with Weather Station, don’t hesitate to review it https://www.ads-software.com/support/plugin/live-weather-station/reviews/ ??

    Thanks for all.
    Pierre

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘500 error with loc_longitude’ is closed to new replies.