Results 1 to 5 of 5

Thread: per DBI under APACHE2 can not connect to postgresql after upgrade to 13.1

  1. #1

    Default per DBI under APACHE2 can not connect to postgresql after upgrade to 13.1

    AH01215: DBI connect('dbname=name','passw',...) failed: could not connect t
    AH01215: \tIs the server running locally and accepting
    AH01215: \tconnections on Unix domain socket "/tmp/.s.PGSQL.5432"? at /srv/www
    End of script output before headers: page.pl


    1.postgresql running and socket exist and have permission 777
    2.sudo -uwwwrun /srv/www/cgi-bin/page.pl run without problem and error.
    3.problem exist when running script under apache2.

  2. #2

    Default Re: per DBI under APACHE2 can not connect to postgresql after upgradeto 13.1

    Could AppArmor be protecting you by preventing Apache from doing weird
    things like making connections to odd sockets? As a test, turn off the
    AppArmor service and see if that works.

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...

  3. #3

    Default Re: per DBI under APACHE2 can not connect to postgresql after upgrade to 13.1

    Nothing change after clear checkbox Enable AppArmor in Yast.

  4. #4

    Default Re: per DBI under APACHE2 can not connect to postgresql after upgradeto 13.1


  5. #5

    Default Re: per DBI under APACHE2 can not connect to postgresql after upgradeto 13.1

    now problem resolved by edit

    /usr/lib/systemd/system/apache2.service

    set PrivateTmp=false


    and run

    systemctl daemon-reload
    systemctl restart apache2



    But i have one question: where is tmp folder place when PrivateTmp=true?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •