google-compute-engine"/>
  • 14
name

A PHP Error was encountered

Severity: Notice

Message: Undefined index: userid

Filename: views/question.php

Line Number: 191

Backtrace:

File: /home/prodcxja/public_html/questions/application/views/question.php
Line: 191
Function: _error_handler

File: /home/prodcxja/public_html/questions/application/controllers/Questions.php
Line: 433
Function: view

File: /home/prodcxja/public_html/questions/index.php
Line: 315
Function: require_once

We have a GCE (europe-west-2b) server sending logs into Papertrail that can only come from our custom binaries and has been doing so for over twelve hours. BUT it is not listed in the developer console or from an API call. It is an instance that must have been started by an autoscaling group.

It is also inaccessible from the internet (which it would not be if configured correctly).

Anybody got any ideas how to address this without paying for support?

      • 2
    • Thanks Carlos. No definitely not there. We only run two projects. Still sending app specific logs now on 5th Feb. IP is 35.197.250.193 , only port open is 443 which is not how it would be if our application and 35.197.250.193 shows a page that is definitely not ours. We use Azure and AWS too, but whois shows it as a google cloud range.
    • Apologies, I have figured it out. At some stage since it started up the public ip address changed. For reasons I don't understand the daemon we run for service discovery (including setting the public ip address in things like syslog formats) couldn't bind itself to a port - I guess something to do with the VM migration. So logs were not really coming from 35.197.250.193 despite papertrail thinking they were.

Apologies, I have figured it out. At some stage since it started up the public ip address changed. For reasons I don't understand the daemon we run for service discovery (including setting the public ip address in things like syslog formats) couldn't bind itself to a port - I guess something to do with the VM migration. So logs were not really coming from 35.197.250.193 despite papertrail thinking they were. I will build some error checking in and terminate the rogue instance in future.

  • 1
Reply Report

Warm tip !!!

This article is reproduced from Stack Exchange / Stack Overflow, please click

Trending Tags