Article ID: 119246, created on Dec 20, 2013, last review on May 9, 2014

  • Applies to:
  • Operations Automation 5.5

Symptoms

In CCP in Autoscale section after enabling Autoscale, selecting new RAM/CPU parameters and clicking 'Save changes' nothing happens. No errors are shown. Autoscale still shown as not enabled.

PACI-im.log contains the following error message:

[im1], step 1 (VE autoscale rules delivery), mode: EXEC, state:CALLBACK] - invoked callback for reqId 138
2013-12-12 01:20:05,109 (2056eb26-336f-4760-95fa-86b034f63601) DEBUG Pipeline [Shared executor thread #2 @1] - Running pipeline #7564 [(AUTOSCALE_RULE_DELIVERY for: VeId [customerId=1009684, name=sapphire]), created at node [im1], step 1 (VE autoscale rules delivery), mode: EXEC, state:CALLBACK]
2013-12-12 01:20:05,109 (2056eb26-336f-4760-95fa-86b034f63601) ERROR AutoscaleRulesManagementTask [Shared executor thread #2 @1] -  AutoscaleRuleDeliveryTask.error(17, Not writable)

Cause

Parallels Dispatcher crashed, but after it was started snmpd cannot work with it, or snmpd hanged.

Resolution

The behavior of snmpd will be improved in scope of the request #CCU-7262.

For now please restart snmpd on the problem node if you face such issue. After that it will be possible to enable Autoscale.

~# service snmpd restart
Stopping snmpd:[  OK  ]
Starting snmpd:[  OK  ]

Please also contact your account manager regarding CCU-7262.

Search Words

17, Not writable

PACI

Autoscale

5b048d9bddf8048a00aba7e0bdadef37 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF