Announcement

Collapse
No announcement yet.

DirectAdmin plugin error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • DirectAdmin plugin error

    Hello!

    Sometimes, some DirectAdmin administrators use php-cli with open_basedir or safemode and prohibit some functions like passthru() in global php.ini. But DirectAdmin plugin relies on it and also can correctly diagnose its prohibition.

    Solution:
    add php.ini without safe_mode, disabled_functions and open_basedir to /usr/local/directadmin/plugins/lvemanager;
    change shebang of all .html and .raaw files of plugin to #!/usr/local/bin/php -c /usr/local/directadmin/plugins/lvemanager/

  • #2
    Also, there is a kind of hangup in the plugin:
    [root@server lvemanager]# netstat -ntp|grep 127.0.0.1:2222
    tcp 0 0 127.0.0.1:2222 127.0.0.1:51117 SYN_RECV -
    tcp 0 0 127.0.0.1:51107 127.0.0.1:2222 ESTABLISHED 648/php
    tcp 0 0 127.0.0.1:51106 127.0.0.1:2222 ESTABLISHED 637/php
    tcp 0 0 127.0.0.1:51109 127.0.0.1:2222 ESTABLISHED 650/php
    tcp 0 0 127.0.0.1:51108 127.0.0.1:2222 ESTABLISHED 649/php
    tcp 0 0 127.0.0.1:51110 127.0.0.1:2222 ESTABLISHED 657/php
    tcp 0 0 127.0.0.1:51113 127.0.0.1:2222 ESTABLISHED 662/php
    tcp 0 0 127.0.0.1:51112 127.0.0.1:2222 ESTABLISHED 661/php
    tcp 0 0 127.0.0.1:51115 127.0.0.1:2222 ESTABLISHED 665/php
    tcp 0 0 127.0.0.1:51114 127.0.0.1:2222 ESTABLISHED 664/php
    tcp 0 212 127.0.0.1:51117 127.0.0.1:2222 ESTABLISHED 672/php
    tcp 212 0 ::ffff:127.0.0.1:2222 ::ffff:127.0.0.1:51112 ESTABLISHED -
    tcp 212 0 ::ffff:127.0.0.1:2222 ::ffff:127.0.0.1:51113 ESTABLISHED -
    tcp 212 0 ::ffff:127.0.0.1:2222 ::ffff:127.0.0.1:51114 ESTABLISHED -
    tcp 212 0 ::ffff:127.0.0.1:2222 ::ffff:127.0.0.1:51115 ESTABLISHED -
    tcp 212 0 ::ffff:127.0.0.1:2222 ::ffff:127.0.0.1:51106 ESTABLISHED -
    tcp 212 0 ::ffff:127.0.0.1:2222 ::ffff:127.0.0.1:51107 ESTABLISHED -
    tcp 212 0 ::ffff:127.0.0.1:2222 ::ffff:127.0.0.1:51108 ESTABLISHED -
    tcp 212 0 ::ffff:127.0.0.1:2222 ::ffff:127.0.0.1:51109 ESTABLISHED -
    tcp 212 0 ::ffff:127.0.0.1:2222 ::ffff:127.0.0.1:51110 ESTABLISHED -
    [root@server lvemanager]# ps aux | grep php
    admin 637 0.0 0.1 95588 11792 ? S 14:28 0:00 /php
    admin 648 0.0 0.1 95588 11792 ? S 14:28 0:00 /php
    admin 649 0.0 0.1 95588 11792 ? S 14:28 0:00 /php
    admin 650 0.0 0.1 95588 11792 ? S 14:28 0:00 /php
    admin 657 0.0 0.1 95588 11792 ? S 14:28 0:00 /php
    admin 661 0.0 0.1 95588 11792 ? S 14:28 0:00 /php
    admin 662 0.0 0.1 95588 11796 ? S 14:28 0:00 /php
    admin 664 0.0 0.1 95588 11796 ? S 14:28 0:00 /php
    admin 665 0.0 0.1 95588 11796 ? S 14:28 0:00 /php
    admin 672 0.0 0.1 95588 11792 ? S 14:28 0:00 /php

    But I can understand, where does the script query directadmin.

    Comment


    • #3
      Thanks a lot. We should detect open_basedir, and tell that it is incompatible. Ill ask developers to fix that.

      Comment


      • #4
        And what can you say about lockup of the plugin and the panel?
        DirectAdmin has a limited number of processes (10 in that case) and the plugin recursively blocks them all.

        Comment


        • #5
          I thought it is side-effect of openbasedir. If not -- I will check.

          Comment


          • #6
            > Igor Seletskiy wrote:
            > I thought it is side-effect of openbasedir. If not -- I will check.

            No, it is not. I you need, I can give you access to the server.

            Comment


            • #7
              Hi there.

              This should be fixed ASAP. This is the main reason why the DirectAdmin refuses to work in our environment. Any status regarding this issue?

              Comment


              • #8
                We cannot fix it. We have to run those commands to get data out.

                Comment


                • #9
                  Hi!

                  Are there any news with the problem I described? Do you need access to the server to investigate it?

                  Comment


                  • #10
                    Which problem? That fact that we need safe_mode off?

                    Comment


                    • #11
                      The fact that with safe_mode off the plugin still hangs and doesn work.

                      Comment


                      • #12
                        Boris,

                        That will be addressed. Ill check if we need access or we need can replicate it inhouse.

                        Comment


                        • #13
                          Hello, Boris!

                          Can you create ticket describing the problem in helpdesk.cloudlinux.com with server access parameters? I need to investigate it.

                          Comment

                          Working...
                          X