• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Php-fpm logs everything as errors

Scheduled Pinned Locked Moved General pfSense Questions
4 Posts 2 Posters 1.3k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P
    pedymaster
    last edited by Aug 4, 2015, 10:41 AM

    Hi,

    We have two pfsenses which sends their logs to syslog servers and we noticed that everything from php-fpm is logged as error:

    
    2015-08-03T11:48:12+00:00 some.domain.eu err php-fpm[25791]: /rc.filter_synchronize: XMLRPC sync successfully completed with https://w.x.y.z:443.
    2015-08-03T11:48:23+00:00 some.domain.eu err php-fpm[24264]: /xmlrpc.php: ROUTING: setting default route to w.x.y.z
    
    

    Some messages has "emerg" instead of "err" like:

    
    2015-08-03T11:47:11+00:00 some.domain.eu emerg php-fpm: /index.php: Successful login for user 'blahbla' from: w.x.y.z
    
    

    Is it a bad settings on my side which I overlooked or is it really implemented this way? If so, should I report a bug somewhere?

    Note: For example charon from the same pfsense node is sending log levels as it should.

    Thanks for the answer!
    Pedy

    1 Reply Last reply Reply Quote 0
    • D
      doktornotor Banned
      last edited by Aug 4, 2015, 7:39 PM

      There is no setting anywhere.

      1 Reply Last reply Reply Quote 0
      • P
        pedymaster
        last edited by Aug 6, 2015, 7:32 AM

        @doktornotor:

        There is no setting anywhere.

        I thought so. Should I file a bug then somewhere?

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned
          last edited by Aug 6, 2015, 7:38 AM

          Shrug; will probably sit there for ages… I essentially gave up on any remote syslogging - unless you have all servers running pretty much the same OS, you always end up with messy crap. Plus, the syslog daemon on pfSense is not exactly a masterpiece when it comes to remote logging (#1940 and others.

          1 Reply Last reply Reply Quote 0
          4 out of 4
          • First post
            4/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received