error [pimatic]: 502 Bad Gateway

Fabian

Hi there,

since some days i got a lot of errors which look all the same and show something like

error [pimatic]: { [StatusCodeError: 504 - <html>
<head><title>504 Gateway Time-out</title></head>

This errors are occuring at irregular times but allways at full hours, half past, quater past, or quater bevor.
And the error is repeated nearly 15 times.

Perhaps someone has an idea to solve this problem. Thank you very much!

Is it possible that these errors are caused by some variables where i have activated the discrete option?

error [pimatic]: { [StatusCodeError: 502 - <html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.10.0 (Ubuntu)</center>
</body>
</html>
]
  name: 'StatusCodeError',
  statusCode: 502,
  message: '502 - <html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body bgcolor="white">\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx/1.10.0 (Ubuntu)</center>\r\n</body>\r\n</html>\r\n',
  error: '<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body bgcolor="white">\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx/1.10.0 (Ubuntu)</center>\r\n</body>\r\n</html>\r\n',
  options: 
   { uri: 'http://api.pimatic.org/plugins?version=0.9.39',
     callback: undefined,
     transform: undefined,
     simple: true,
     resolveWithFullResponse: false },
  response: 
   IncomingMessage {
     _readableState: 
      ReadableState {
        objectMode: false,
        highWaterMark: 16384,
        buffer: [],
        length: 0,
        pipes: null,
        pipesCount: 0,
        flowing: true,
        ended: true,
        endEmitted: true,
        reading: false,
        sync: true,
        needReadable: false,
        emittedReadable: false,
        readableListening: false,
        resumeScheduled: false,
        defaultEncoding: 'utf8',
        ranOut: false,
        awaitDrain: 0,
        readingMore: false,
        decoder: null,
        encoding: null },
     readable: false,
     domain: null,
     _events: 
      { end: [Object],
        close: [Object],
        data: [Function],
        error: [Function] },
     _eventsCount: 4,
     _maxListeners: undefined,
     socket: 
      Socket {
        _connecting: false,
        _hadError: false,
        _handle: null,
        _parent: null,
        _host: 'api.pimatic.org',
        _readableState: [Object],
        readable: false,
        domain: null,
        _events: [Object],
        _eventsCount: 8,
        _maxListeners: undefined,
        _writableState: [Object],
        writable: false,
        allowHalfOpen: false,
        destroyed: true,
        _bytesDispatched: 82,
        _sockname: null,
        _pendingData: null,
        _pendingEncoding: '',
        server: null,
        _server: null,
        parser: null,
        _httpMessage: [Object],
        read: [Function],
        _consuming: true,
        _idleNext: null,
        _idlePrev: null,
        _idleTimeout: -1 },
     connection: 
      Socket {
        _connecting: false,
        _hadError: false,
        _handle: null,
        _parent: null,
        _host: 'api.pimatic.org',
        _readableState: [Object],
        readable: false,
        domain: null,
        _events: [Object],
        _eventsCount: 8,
        _maxListeners: undefined,
        _writableState: [Object],
        writable: false,
        allowHalfOpen: false,
        destroyed: true,
        _bytesDispatched: 82,
        _sockname: null,
        _pendingData: null,
        _pendingEncoding: '',
        server: null,
        _server: null,
        parser: null,
        _httpMessage: [Object],
        read: [Function],
        _consuming: true,
        _idleNext: null,
        _idlePrev: null,
        _idleTimeout: -1 },
     httpVersionMajor: 1,
     httpVersionMinor: 1,
     httpVersion: '1.1',
     complete: true,
     headers: 
      { server: 'nginx/1.10.0 (Ubuntu)',
        date: 'Wed, 03 May 2017 18:45:02 GMT',
        'content-type': 'text/html',
        'content-length': '182',
        connection: 'close' },
     rawHeaders: 
      [ 'Server',
        'nginx/1.10.0 (Ubuntu)',
        'Date',
        'Wed, 03 May 2017 18:45:02 GMT',
        'Content-Type',
        'text/html',
        'Content-Length',
        '182',
        'Connection',
        'close' ],
     trailers: {},
     rawTrailers: [],
     upgrade: false,
     url: '',
     method: null,
     statusCode: 502,
     statusMessage: 'Bad Gateway',
     client: 
      Socket {
        _connecting: false,
        _hadError: false,
        _handle: null,
        _parent: null,
        _host: 'api.pimatic.org',
        _readableState: [Object],
        readable: false,
        domain: null,
        _events: [Object],
        _eventsCount: 8,
        _maxListeners: undefined,
        _writableState: [Object],
        writable: false,
        allowHalfOpen: false,
        destroyed: true,
        _bytesDispatched: 82,
        _sockname: null,
        _pendingData: null,
        _pendingEncoding: '',
        server: null,
        _server: null,
        parser: null,
        _httpMessage: [Object],
        read: [Function],
        _consuming: true,
        _idleNext: null,
        _idlePrev: null,
        _idleTimeout: -1 },
     _consuming: true,
     _dumped: false,
     req: 
      ClientRequest {
        domain: null,
        _events: [Object],
        _eventsCount: 5,
        _maxListeners: undefined,
        output: [],
        outputEncodings: [],
        outputCallbacks: [],
        outputSize: 0,
        writable: true,
        _last: true,
        chunkedEncoding: false,
        shouldKeepAlive: false,
        useChunkedEncodingByDefault: false,
        sendDate: false,
        _removedHeader: {},
        _contentLength: 0,
        _hasBody: true,
        _trailer: '',
        finished: true,
        _headerSent: true,
        socket: [Object],
        connection: [Object],
        _header: 'GET /plugins?version=0.9.39 HTTP/1.1\r\nhost: api.pimatic.org\r\nConnection: close\r\n\r\n',
        _headers: [Object],
        _headerNames: [Object],
        _onPendingData: null,
        agent: [Object],
        socketPath: undefined,
        method: 'GET',
        path: '/plugins?version=0.9.39',
        _ended: true,
        parser: null,
        res: [Circular] },
     request: 
      Request {
        domain: null,
        _events: [Object],
        _eventsCount: 5,
        _maxListeners: undefined,
        uri: [Object],
        readable: true,
        writable: true,
        _qs: [Object],
        _auth: [Object],
        _oauth: [Object],
        _multipart: [Object],
        _redirect: [Object],
        _tunnel: [Object],
        _rp_resolve: [Function],
        _rp_reject: [Function],
        _rp_promise: [Object],
        _rp_callbackOrig: undefined,
        callback: [Function],
        _rp_options: [Object],
        headers: {},
        setHeader: [Function],
        hasHeader: [Function],
        getHeader: [Function],
        removeHeader: [Function],
        method: 'GET',
        localAddress: undefined,
        pool: {},
        dests: [],
        __isRequestRequest: true,
        _callback: [Function: RP$callback],
        proxy: null,
        tunnel: false,
        setHost: true,
        originalCookieHeader: undefined,
        _disableCookies: true,
        _jar: undefined,
        port: 80,
        host: 'api.pimatic.org',
        path: '/plugins?version=0.9.39',
        httpModule: [Object],
        agentClass: [Object],
        agent: [Object],
        _started: true,
        href: 'http://api.pimatic.org/plugins?version=0.9.39',
        req: [Object],
        ntick: true,
        response: [Circular],
        originalHost: 'api.pimatic.org',
        originalHostHeaderName: 'host',
        responseContent: [Circular],
        _destdata: true,
        _ended: true,
        _callbackCalled: true },
     toJSON: [Function: responseToJSON],
     caseless: Caseless { dict: [Object] },
     read: [Function],
     body: '<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body bgcolor="white">\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx/1.10.0 (Ubuntu)</center>\r\n</body>\r\n</html>\r\n' } }

mwittig

@Fabian said in error [pimatic]: 502 Bad Gateway:

Perhaps someone has an idea to solve this problem. Thank you very much!

Seems like nginx is bailing out when web service is taking too long to respond. I could reproduce it on the first call, but subsequent call succeeded. We’ll certainly look into this.

Did you already try to restart pimatic? Possibly the error will disappear at your end for some time after restarting pimatic.

sweetpi

Hi Fabian,

I will investigate further. You said, that the error repeates? Does this happen after a user interaction with pimatic, (i.e. checking for updates) or without user interaction?

The error typically mean, there is something wrong with our update server and not with your pimatic installation.

Fabian

Thank you. @mwittig yes, I already restarted pimatic for some times. However, I tried it again this morning, but at least I have 112 errors by now.

@sweetpi perhaps this is this the right hint. I have implemented some devices since theses errors occur. The devices are some update notifications like shown on this page

https://forum.pimatic.org/topic/1502/update-notification-and-changelog-for-pimatic-and-homeduino/3

Perhaps it is a request which is initiated by this device.

{
      "class": "iframeDevice",
      "id": "plugin-update-display",
      "name": "Plugins for update",
      "url": "http://admin:PASSWORD@IP-TO-YOUR-PIMATIC/files/home/pi/plugins.log",
      "width": 600,
      "height": 100,
      "border": 0,
      "scrolling": "yes",
      "scale": 1,
      "reload": 30
    },

But i do not have any idea what should be the probleme with this device because i also have some other working devices to get the update notifcation of pimatic itself. And they are working for a long time without Problems.

Jens

@Fabian Hallo.

I have the self error on my Pimatic Server since 2- 3 months. A restart of pimatic help for 1- 2 days, then comming the errors. I have 14 plugins installed, i have 14 messages and search the error in my config and installation.

My Server is a raspi 3, homeduino, update and upgrade, pimatic up to date, network over cable.------> bad gateway

Test PI is a raspi B+, no homeduino, update and upgrade, pimatic with the conf.js from the raspi 3, network over cable------> only errors of not installed hardware, no bad gateway

The network is okay. With “mtr api.pimatic.org” is all okay.

Idea? Format /c

Fabian

@Jens Hi,
I also did a update, upgrade and a full restart of the system yesterday, but at least the errors are still occurring.

I’ll now try to identify the problem by reconfiguring my config to the last stable state. My problem is that I do not have a backup, so I have to try it step by step.

My actual guess is that any requests of a ShellSensor/iframeDevice like

curl -s https://github.com/pimatic…
http://admin:password@YOUR-PIMATIC-IP-HERE/files/home/pi/… .log
cat /usr/local/pimatic-app/node_modules/pimatic/package.json | grep version\": |awk {‘print $2’}|sed ‘s/,//g’ |sed ‘s/"//g’"

is the reason. Or it might also be a bad user configuration.

I am actually using 3 users
with only 2 different roles
one of the user has a password which is equal to the username

I really don’t know by now what could be wrong. But these are the things I have changed in the last time.

Today, I also have recognized that my pimatic isn’t reachable any more over the Internet by dyndns. Perhaps there is something wrong with the https server.

Perhaps @Jens you can check what of these things you are also using.

From my side, in comparison to your config I do not use homeduino!

Jens

Hi.
I testing/ change networkcable, powersupply, new sd- card with fresh installation with my raspi3. 5- 10 h is he working fine and then coming the “bad gateways”. The next test is working mit raspi B+. This machine work with the self config over 1 week without gateway-errors.
My question: Who and why going in the web to http://api.pimatic.org/plugins?version=0.9.39 every 15 min? Can i stop this?
Okay…i go with the raspberry3 offline (no DNS) an look for the messages.

Fabian

Hi @Jens,
I’m using a rule to get the current update information/notification for outdated plugins. (https://forum.pimatic.org/topic/1502/update-notification-and-changelog-for-pimatic-and-homeduino/3) If I deactivate the following rule from my config then I don’t get the errors anymore.

    {
      "id": "check-plugin-update-api",
      "name": "Check Plugin update API",
      "rule": "if every 15 minute then execute \"curl -s http://admin:PASSWORD@IP-TO-YOUR-PIMATIC/api/outdated-plugins | grep plugin | sed 's/\\\"//g' | sed 's/,//g' |  sed 's/plugin: //g' | sed 's/ //g' > /home/pi/plugins.log\"",
      "active": true,
      "logging": true
    },

I haven’t manage to get rid of the errors while using this rule. But deactivating is solving the problem for me.

The rules for pimatic update information in contrary are working fine. Just the plugins update information is a problem by now.

@Jens: are you also looking for updates with pimatic? If you don’t do it by rule or something else perhaps pimatic itself checks for outdated plugins every 15 min. But I don’t know this. Perhaps anyone of the @developer can answer this.

Jens

Hi. This rule have i delete. No change of errors. In the moment i look in gui Pimatic/ Homeduino Version/ Request and Changelog. The errors are present without input from me. I change the

"messageLogging": [
        {
          "level": "*",
          "tags": [],
          "expire": "12h"
        },
        {
          "level": "debug",
          "tags": [],
          "expire": "1h"
        }
      ]

It is okay. I can`t read over 100 messages in the gui.

Thanks for your time and ideas.

Fabian

Since some days I have reactivated the rule to get the notification for updates again and by now no errors occur. So perhaps it has been a problem with the update server itself.

How about you @Jens ?

Jens

Hi. I life with this error messages. With manual search i haven`t errors. In the log coming over the day same errors. For comfort read have i a Pimatic Log iframe device create. I think, the update server, the raspi3(to speedy) or my vodafone i- net(VDSL50/ Dresden) is buggy.

Jens

Hi,
my pi is in self- healing!!!
Version Pimatic 0.9.42 or my i-net provider (VDSL Vodafone) or, or …
My Pimatic run perfect!