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

Too many actions failed per hour

Discussion in 'Plesk Expand 2.2 Troubleshooting Issues' started by youp, Mar 31, 2008.

  1. youp

    youp Guest

    0
     
    Hello, Default Administrator.
    The number of action files created per hour: 185 ('auto'), It means that there are some problems in your system.

    in log "operator.log" i see this :


    Mar 31 2008 16:44:04 [247275:11686] INFO: Request to operator 'plesk_ev_wd'
    Mar 31 2008 16:44:04 [247275:11686] INFO: ... action_id=247275
    Mar 31 2008 16:44:04 EvWDOp[247275:11686] NOTICE: Command 'process_log' requested
    Mar 31 2008 16:44:04 [247275:11686] INFO: Locking object(s) #2 in the 'plesk_server' table - state 'updating', action #247275.
    Mar 31 2008 16:44:04 [247275:11686] INFO: Object(s) #2 have been successfully locked in state 'updating' by action #247275 - 1 row(s) affected.
    Mar 31 2008 16:44:04 [247275:11686] INFO: Processing server #2 event log.
    Mar 31 2008 16:44:04 [247275:11686] INFO: PleskAgent system reports 'error' <status>.
    Mar 31 2008 16:44:04 [247275:11686] ERR: PleskAgent system result is 'error': (1002) [PleskAgent - GENERAL] Unknown or general internal error. MySQL query failed:.
    Mar 31 2008 16:44:04 [247275:11686] ERR: Server #2 event log processing failed: (2102) [Transport] PleskAgent internal system error. (1002) [PleskAgent - GENERAL] Unknown or general internal error. MySQL query failed:
    Mar 31 2008 16:44:04 [247275:11686] INFO: Unlocking object(s) #2 in the 'plesk_server' table.
    Mar 31 2008 16:44:04 [247275:11686] INFO: Object(s) #2 have been unlocked - 1 row(s) affected.
    Mar 31 2008 16:44:05 [247275:11686] INFO: Locking object(s) #3 in the 'plesk_server' table - state 'updating', action #247275.
    Mar 31 2008 16:44:05 [247275:11686] INFO: Object(s) #3 have been successfully locked in state 'updating' by action #247275 - 1 row(s) affected.
    Mar 31 2008 16:44:06 [247275:11686] INFO: Processing server #3 event log.
    Mar 31 2008 16:44:06 [247275:11686] INFO: PleskAgent system reports no errors.
    Mar 31 2008 16:44:06 [247275:11686] INFO: <event/id> object id node not found: parsing 'id' as 0.
    Mar 31 2008 16:44:06 [247275:11686] INFO: Server #3 reports no events.
    Mar 31 2008 16:44:06 [247275:11686] INFO: Unlocking object(s) #3 in the 'plesk_server' table.
    Mar 31 2008 16:44:06 [247275:11686] INFO: Object(s) #3 have been unlocked - 1 row(s) affected.
    Mar 31 2008 16:44:08 [247275:11686] INFO: Locking object(s) #4 in the 'plesk_server' table - state 'updating', action #247275.
    Mar 31 2008 16:44:08 [247275:11686] INFO: Object(s) #4 have been successfully locked in state 'updating' by action #247275 - 1 row(s) affected.
    Mar 31 2008 16:44:08 [247275:11686] INFO: Processing server #4 event log.
    Mar 31 2008 16:44:09 [247275:11686] INFO: PleskAgent system reports no errors.
    Mar 31 2008 16:44:09 [247275:11686] INFO: <event/id> object id node not found: parsing 'id' as 0.
    Mar 31 2008 16:44:09 [247275:11686] INFO: Server #4 reports no events.
    Mar 31 2008 16:44:09 [247275:11686] INFO: Unlocking object(s) #4 in the 'plesk_server' table.
    Mar 31 2008 16:44:09 [247275:11686] INFO: Object(s) #4 have been unlocked - 1 row(s) affected.
    Mar 31 2008 16:44:09 [247275:11686] INFO: Result code: 0
    Mar 31 2008 16:44:16 [247276:11686] INFO: Request to operator 'plesk_backup'
    Mar 31 2008 16:44:16 [247276:11686] INFO: ... action_id=247276
    Mar 31 2008 16:44:16 BackupOp[247276:11686] NOTICE: Command 'update_processes' requested
    Mar 31 2008 16:44:16 BackupOp[247276:11686] INFO: Plesk server #2 supports API 1.5.1.0
    Mar 31 2008 16:44:16 [247276:11686] INFO: PleskAgent system reports 'error' <status>.
    Mar 31 2008 16:44:16 [247276:11686] ERR: PleskAgent system result is 'error': (1002) [PleskAgent - GENERAL] Unknown or general internal error. MySQL query failed:.
    Mar 31 2008 16:44:16 BackupOp[247276:11686] INFO: Plesk server #4 supports API 1.5.1.0
    Mar 31 2008 16:44:16 [247276:11686] INFO: PleskAgent system reports no errors.
    Mar 31 2008 16:44:17 [247276:11686] INFO: PleskAgent system reports no errors.
    Mar 31 2008 16:44:17 [247276:11686] INFO: Result code: 21


    how to find the error ???

    other think, i have two server plesk , one in winsows , and the second in linux, the scheduler backup in expand does not work with Windows ...

    best regards
     
  2. Bers

    Bers Basic Pleskian Staff Member

    23
    70%
    Joined:
    Jul 31, 2001
    Messages:
    73
    Likes Received:
    0
    Hello,

    please check your Plesk server with ID #2. Seems to be it has some problems with the MySQL database.

    Plesk for Windows has some issue which blocks backup management via API RPC in Expand. Please wait for the nearest release of Plesk for Windows.

    Best Regards,
     
  3. youp

    youp Guest

    0
     
    yes, is true , the mysql on server #2 does not restart , db corrupt :(
     
  4. Christian Lund

    Christian Lund New Pleskian

    22
    73%
    Joined:
    Feb 27, 2009
    Messages:
    23
    Likes Received:
    0
    I get email notifications that say:

    Hello, Default Administrator.
    The number of action files created per hour: 240 ('auto'), It means that there are some problems in your system.

    Where do I find the operator.log?
     
  5. gold

    gold Regular Pleskian

    25
    57%
    Joined:
    Jan 8, 2008
    Messages:
    307
    Likes Received:
    0
    The operator.log file is located in '/usr/local/expand/var/log/' directory.

    You can look the failed actons on the 'Server > System Health > Operations' page.
     
  6. Christian Lund

    Christian Lund New Pleskian

    22
    73%
    Joined:
    Feb 27, 2009
    Messages:
    23
    Likes Received:
    0
    Indeed. I had overlooked the server menu item (Server > System Health > Operations).

    It seems my problem is related to DNS setup. The centralized DNS server has allowed host set to a domain that does not yet resolve. Hopefully this is fixed when corresponding name servers are registered.

    Thanks for the feedback.
     
Loading...