Start a Conversation

Unsolved

2 Posts

1034

March 10th, 2020 00:00

error retrieving local vdc : ECS CE:3.1.23

Hello Everyone,

I just pulled in the ECS image from github and wanted to try it out. Thus far I've been able to create a varray, datastore successfully.

I went ahead and tried to create a bucket, but for that i needed an objectvpool to be created.
However the creation of the objectvpool fails with the following error.

URI: /vdc/data-services/varrays

method: GET

body is None

-----------------------------------------------------------------------------

JMC: [{'isColdStorageEnabled': False, 'name': 'pmavarray', 'isProtected': False, 'warningAlertAt': -1, 'criticalAlertAt': -1, 'errorAlertAt': -1, 'id': 'urn:storageos:VirtualArray:c5709b3f-701e-4fe1-b465-33f5546b271a'}]

URI: /object/vdcs/vdc/list

method: GET

body is None

-----------------------------------------------------------------------------

Error: Failed to create object vpool

Reason:'HTTP code: 500, Server Error [ECS internal server error. Error details: An error occurred in the API service. Cause: error retrieving local vdc.]'

I'm not sure which logs to paste or look at to figure out the issue. It would be helpful to know any details around this.

I looked at whatever logs i could see showing some errors

in file ssm.log i see:
ERROR_NO_STORAGE_DEVICE_FOUND sleep 5000 millis before retry

in file objcontrolsvc.log: i see the following trace

2020-03-09T15:13:41,964 [qtp235460721-366-ac120601:170bf70dbbb:f4:0] ERROR ZoneInfoAPIImpl.java (line 124) listAllZones failed with
com.emc.storageos.objcontrol.object.exception.ObjectAccessException: Hit an exception while getting handleListZoneInfo
at com.emc.storageos.objcontrol.object.exception.ObjectAccessException.createExceptionForAPI(ObjectAccessException.java:437)
at com.emc.storageos.data.object.ipc.protocol.impl.ObjectAccessExceptionParser.parseFrom(ObjectAccessExceptionParser.java:61)
at com.emc.storageos.data.object.ipc.protocol.impl.ObjectAccessExceptionParser.parseFrom(ObjectAccessExceptionParser.java:1)
at com.emc.storageos.data.object.ipc.protocol.DefaultExceptionHandler.parseFrom(DefaultExceptionHandler.java:51)
at com.emc.storageos.ipc.ClientLib.client.impl.AbstractBasicAPIClient.sendRequestAndWait(AbstractBasicAPIClient.java:64)
at com.emc.storageos.ipc.ClientLib.zone.impl.ZoneInfoAPIImpl.sendRequest(ZoneInfoAPIImpl.java:202)
at com.emc.storageos.ipc.ClientLib.zone.impl.ZoneInfoAPIImpl.listAllZones(ZoneInfoAPIImpl.java:113)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:698)
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:804)
at java.lang.Thread.run(Thread.java:748)
2020-03-09T15:13:41,965 [qtp235460721-366-ac120601:170bf70dbbb:f4:0] ERROR ExceptionTranslator.java (line 75) exception code ERROR_INTERNAL with arguments []
2020-03-09T15:13:41,970 [qtp235460721-366-ac120601:170bf70dbbb:f4:0] WARN ServiceCodeExceptionMapper.java (line 92) Responding to internal 7000 with HTTP Internal Server Error; Caused by An error occurred in the API service. Cause: error retrieving local vdc.

 

I dont know which errors are ok, which ones are not or in general which logs to follow.. any help would be really great.

Moderator

 • 

7.1K Posts

March 10th, 2020 11:00

Hello wrapster15,

I would call into support so that we can pull some logs and have a deeper look into your issue.

Please let us know if you have any other questions.

2 Posts

March 10th, 2020 22:00

Can you please let me know what you mean by 'call in to support' ?

is there a DL i need to mail or what should i do?

In anycase, If it helps,

I looked at the cm-error.log and found this.

com.emc.storageos.data.object.exception.ObjectControllerException: Can't find enough storage devices for 1 segments, [] devices blacklisted, [f443f12e-604c-11ea-abb4-0242c625ecd6] devices do not have capacity info
at com.emc.storageos.data.chunkmanager.SsSelector.placementCheck(SsSelector.java:602)
at com.emc.storageos.data.chunkmanager.utils.Allocator.placementCheck(Allocator.java:631)
at com.emc.storageos.data.chunkmanager.utils.Allocator.allocateBlocks(Allocator.java:552)
at com.emc.storageos.data.chunkmanager.utils.Allocator.allocateBlocks(Allocator.java:387)
at com.emc.storageos.data.chunkmanager.utils.Allocator.allocateBlocks(Allocator.java:362)
at com.emc.storageos.data.chunkmanager.utils.Allocator.allocateBlocks(Allocator.java:349)
at com.emc.storageos.data.chunkmanager.utils.Allocator.allocateBlocks(Allocator.java:338)
at com.emc.storageos.data.chunkmanager.ChunkServer.createChunk(ChunkServer.java:755)
at com.emc.storageos.data.chunkmanager.RequestProcessor.handleChunkCreateRequest(RequestProcessor.java:258)
at com.emc.storageos.data.chunkmanager.RequestProcessor.call(RequestProcessor.java:2101)
at com.emc.storageos.data.chunkmanager.RemoteRequestProcessorCm.handleRequest(RemoteRequestProcessorCm.java:60)
at com.emc.storageos.data.object.communicator.AbstractRequestProcessor.handleRemoteRequest(AbstractRequestProcessor.java:226)
at com.emc.storageos.data.object.communicator.impl.RemoteOperationProcessor$RequestProcessor.run(RemoteOperationProcessor.java:327)
at com.emc.storageos.data.object.communicator.impl.RemoteOperationProcessor$RequestProcessor.call(RemoteOperationProcessor.java:305)
at com.emc.storageos.data.object.communicator.impl.RemoteOperationProcessor$RequestProcessor.call(RemoteOperationProcessor.java:295)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at com.emc.storageos.data.object.impl.BlockingThreadPoolExecutor$2.run(BlockingThreadPoolExecutor.java:98)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

 

Not sure what it means in this context? 

As it stands i have 2 LUNs provided in the deploy.yml
1. 100G lun for the storageos itself as required.
2. 40G lun for the VDC - (Though this step is optional).

So i'm not sure which storage is being referred to here.It would be helpful if it could be triaged.

Moderator

 • 

7.1K Posts

March 17th, 2020 11:00

Hello wrapster15,

Looking at the part of the log you posted I am not able to find what the issue is that is prevent what you are trying to do.  That is why I stated it is best to call into support so that you can get a EMC ECS tech to look into this issue.

Please let us know if you have any other questions.

No Events found!

Top