1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Expand operation manager keeps failing

Discussion in 'Plesk Expand 2.3 Troubleshooting Issues' started by wsani, Jan 29, 2009.

  1. wsani

    wsani Silver Pleskian

    28
    40%
    Joined:
    Mar 4, 2005
    Messages:
    509
    Likes Received:
    0
    For some reason the operation manager will arbitrarily fail. I haven't been able to figure out the issue yet but has anyone else experienced this?
     
  2. gold

    gold Regular Pleskian

    25
    57%
    Joined:
    Jan 8, 2008
    Messages:
    307
    Likes Received:
    0
    To determine the problem you need to set to debug level logs of the operation manager in '/usr/local/expand/conf/expand.conf' file
    Code:
    expandom_level = DEBUG
    
    then restart the Expand
    Code:
    /etc/init.d/expand restart
    
    After fail of the operation manager save and post to this thread the '/usr/local/expand/var/log/expandom.log' file.

    If the Parallels Plesk Expand is installed in Parallels Virtuozzo Container please check the 'failcnt' column in '/proc/user_beancounters' file and increase failed resources for this container.
     
  3. JosefV

    JosefV New Pleskian

    15
    55%
    Joined:
    Apr 1, 2011
    Messages:
    2
    Likes Received:
    0
    Hi

    We're experiencing the same problem here:
    Notice the expandom stopped regularly at 23:00 because of a backup.

    After the expandom stopped, the log showed the following:

    Mar 31 2011 23:00:22 [:23800] DEBUG: Schema 'pleskagent/protocol/1.5.1.0/agent_output.xsd' requested
    Mar 31 2011 23:00:22 [:23794] NOTICE: Signal SIGHUP received
    Mar 31 2011 23:00:22 [:23794] DEBUG: pool: Sending SIGINT to all processes.
    Mar 31 2011 23:00:22 [:23794] DEBUG: pool: Sending message '1' to child #23798.
    Mar 31 2011 23:00:22 [:23794] DEBUG: pool: Sending message '1' to child #23800.
    Mar 31 2011 23:00:22 [:23794] DEBUG: pool: Sending message '1' to child #23802.
    Mar 31 2011 23:00:22 [:23794] DEBUG: pool: Sending message '1' to child #23803.
    Mar 31 2011 23:00:22 [:23794] DEBUG: pool: Sending message '1' to child #23814.
    Mar 31 2011 23:00:22 [:23794] DEBUG: pool: Sending message '1' to child #23816.
    Mar 31 2011 23:00:22 [:23798] DEBUG: Control socket has incoming data
    Mar 31 2011 23:00:22 [:23798] DEBUG: Message: 1
    Mar 31 2011 23:00:22 [:23798] INFO: pool: Exiting.
    Mar 31 2011 23:00:22 [:23802] DEBUG: Control socket has incoming data
    Mar 31 2011 23:00:22 [:23802] DEBUG: Message: 1
    Mar 31 2011 23:00:22 [:23802] INFO: pool: Exiting.
    Mar 31 2011 23:00:22 [:23803] DEBUG: Control socket has incoming data
    Mar 31 2011 23:00:22 [:23803] DEBUG: Message: 1
    Mar 31 2011 23:00:22 [:23803] INFO: pool: Exiting.
    Mar 31 2011 23:00:22 [:23814] DEBUG: Control socket has incoming data
    Mar 31 2011 23:00:22 [:23814] DEBUG: Message: 1
    Mar 31 2011 23:00:22 [:23814] INFO: pool: Exiting.
    Mar 31 2011 23:00:22 [:23816] DEBUG: Control socket has incoming data
    Mar 31 2011 23:00:22 [:23816] DEBUG: Message: 1
    Mar 31 2011 23:00:22 [:23816] INFO: pool: Exiting.
    Mar 31 2011 23:00:22 [:23794] DEBUG: Reading socket
    Mar 31 2011 23:00:22 [:23794] DEBUG: Control socket closed.
    Mar 31 2011 23:00:22 [:23794] DEBUG: Reading socket
    Mar 31 2011 23:00:22 [:23794] DEBUG: Control socket closed.
    Mar 31 2011 23:00:22 [:23794] DEBUG: Reading socket
    Mar 31 2011 23:00:22 [:23794] DEBUG: Control socket closed.
    Mar 31 2011 23:00:22 [:23794] DEBUG: Reading socket
    Mar 31 2011 23:00:22 [:23794] DEBUG: Control socket closed.
    Mar 31 2011 23:00:22 [:23794] DEBUG: Reading socket
    Mar 31 2011 23:00:22 [:23794] DEBUG: Control socket closed.
    Mar 31 2011 23:00:22 [:23794] ERR: pool: Process 23798 exited with status 0.
    Mar 31 2011 23:00:22 [:23794] DEBUG: Stat: 5 total, 0 free
    Mar 31 2011 23:00:22 [:23794] ERR: pool: Process 23802 exited with status 0.
    Mar 31 2011 23:00:22 [:23794] DEBUG: Stat: 4 total, 0 free
    Mar 31 2011 23:00:22 [:23794] ERR: pool: Process 23803 exited with status 0.
    Mar 31 2011 23:00:22 [:23794] DEBUG: Stat: 3 total, 0 free
    Mar 31 2011 23:00:22 [:23794] ERR: pool: Process 23814 exited with status 0.
    Mar 31 2011 23:00:22 [:23794] DEBUG: Stat: 2 total, 0 free
    Mar 31 2011 23:00:22 [:23794] ERR: pool: Process 23816 exited with status 0.
    Mar 31 2011 23:00:22 [:23794] DEBUG: Stat: 1 total, 0 free
    Mar 31 2011 23:00:23 [:23800] DEBUG: Schema 'pleskagent/protocol/1.5.1.0/agent_output.xsd' requested

    …
    -> (lots of these messages here)

    Mar 31 2011 23:03:47 [:23800] DEBUG: Schema 'pleskagent/protocol/1.5.1.0/agent_output.xsd' requested
    Mar 31 2011 23:03:47 [:23800] DEBUG: Schema 'pleskagent/protocol/1.5.1.0/agent_output.xsd' requested
    Mar 31 2011 23:03:47 [:23800] DEBUG: xml: Result composed.
    Mar 31 2011 23:03:47 [:23800] DEBUG: xml: XML outputted.
    Mar 31 2011 23:03:47 [:23800] INFO: pool: Job finished.
    Mar 31 2011 23:03:47 [:23800] DEBUG: Message: 1
    Mar 31 2011 23:03:47 [:23800] INFO: Control socket closed, exiting
    Mar 31 2011 23:03:47 [:23800] INFO: pool: Exiting.

    Thanks for your help!
     
  4. MajooshM

    MajooshM New Pleskian

    10
    85%
    Joined:
    Jun 7, 2012
    Messages:
    11
    Likes Received:
    0
    am seeing the exact same issue.. for now I added a cron job to restart the expand if it is failing in the server. Also turned on the expand debug.. will post if I find anything
     
Loading...