How can I view Symfony log information in Cloudbees?

1
votes

I've created a symphony based PHP application. I'm trying to run my application on Cloydbees. Couldbees doesn't natively support symfony so I've also created my own clickStack.

When I load up the web page All it says is:

Oops! An Error Occurred

The server returned a "500 Internal Server Error".

Something is broken. Please e-mail us at [email] an>d let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.

Since this is running on Cloudbees as far as I'm aware there's no file system access. So how Can I configure PHP/Symfony to log in such a way that it will be picked up so it will get displayed in the Log tab in the web interface?

EDIT

Symfony-Clickstack

According to: How to use logback on Cloudbees
It looks like in order to write to the error log I need to print to StdOut and/or StdErr

I've tried configuring monolog
I've Tried:

Here's the Logging Section of my config.yml

# Insert application logging   
monolog:
  handlers:
    syslog:
      type: syslog
      level: info  
    console:
      type:  console
      level: info
      verbosity_levels:
        VERBOSITY_NORMAL: NOTICE
    error_log:
            type:  stream
            level: info
3
phpsymfonycloudbees

3 Answers

1
votes

The current PHP ClickStack on CloudBees doesn´t support Symfony at this moment.

PHP is a part of the Community Stacks, so it is not officially maintained by CloudBees team. However, this ClickStack could be updated adding Simfony in the near future.

Current GitHub repository, where you can see the way in which the stack is developed is available here. If you would like to contribute, all the details are available on the Wiki for Developers.

0
votes

Check the app/logs directory. In it must be dev.log and prod.log files with errors, depending on what environment you use.

0
votes

So Thanks to another Question I was able to get logging to work and I've now moved on to a new set of issues :)

The relevant MonoLog configuration is: 

    stdout:
        type:  stream
        path:  "php://stdout"
        level: debug