Re: XenServer Agent is not coming up after upgrading from 7.1 to 8.2

2022-06-01 Thread Harikrishna Patnala 
Hi Vivek,

Please check the CloudStack detected Xenserver version in either UI or database.

You may try an option to reinitialize the Xenserver host by clearing the tags 
on the host and try reconnecting from CloudStack UI.
Run the following command on Xenserver and reconnect the host.

# for host in $(xe host-list | grep ^uuid | awk '{print $NF}') ; do xe 
host-param-clear uuid=$host param-name=tags; done;

Hope this helps.

Regards,
Harikrishna

From: Suresh Anaparti 
Sent: Wednesday, June 1, 2022 3:07 PM
To: users@cloudstack.apache.org 
Subject: Re: XenServer Agent is not coming up after upgrading from 7.1 to 8.2

Hi Vivek,

This discussion thread might provide you some inputs: 
https://lists.apache.org/thread/7q6yybm3qcms21qcd8945kvrygpr1v86

Also, check the docs here: 
http://docs.cloudstack.apache.org/en/4.16.1.0/installguide/hypervisor/xenserver.html#upgrading-xenserver-versions,
 and see if you have missed any upgrade step.


Regards,
Suresh

On 01/06/22, 2:17 PM, "Vivek Kumar"  wrote:

Hello Guys,


We have recently upgraded our XenServer  from 7.1 to 8.2. We are using 
CloudStack 4.16.1. But after the upgradation my status of host is showing 
alert. I have gone through the logs getting below error. Can someone help me 
out for this.



—



rZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw&command=listSystemVms&response=json&signatureVersion=3&expires=2022-06-01T08%3A43%3A33%2B&signature=x7KQg4LW2XPtTf%2BHHVn0Fm599xA%3D
2022-06-01 14:00:51,613 DEBUG [c.c.u.s.SSHCmdHelper] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Executing cmd: rm -f 
/opt/xensource/sm/hostvmstats.py 
/opt/xensource/bin/copy_vhd_to_secondarystorage.sh 
/opt/xensource/bin/copy_vhd_from_secondarystorage.sh 
/opt/xensource/bin/create_privatetemplate_from_snapshot.sh 
/opt/xensource/bin/vhd-util /opt/cloud/bin/copy_vhd_to_secondarystorage.sh 
/opt/cloud/bin/copy_vhd_from_secondarystorage.sh 
/opt/cloud/bin/create_privatetemplate_from_snapshot.sh /opt/cloud/bin/vhd-util
2022-06-01 14:00:52,750 DEBUG [c.c.a.ApiServlet] 
(qtp1850777594-19:ctx-5c391d12) (logid:fb2dbf4b) ===START===  172.31.29.44 -- 
GET  
listall=True&apiKey=W0EWPYRPQu51YPDQ8s_0b4wDDuSqrZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw&command=listVpnConnections&response=json&signatureVersion=3&expires=2022-06-01T08%3A43%3A35%2B&signature=TBKYjvgMLESFTna9iXeGTJdKtc0%3D
2022-06-01 14:00:52,756 DEBUG [c.c.a.ApiServer] 
(qtp1850777594-19:ctx-5c391d12 ctx-9cd12123) (logid:fb2dbf4b) CIDRs from which 
account 'Acct[0d808973-19be-11eb-9555-005056961200-admin] -- Account {"id": 2, 
"name": "admin", "uuid": "0d808973-19be-11eb-9555-005056961200"}' is allowed to 
perform API calls: 0.0.0.0/0,::/0
2022-06-01 14:00:52,761 DEBUG [c.c.a.ApiServlet] 
(qtp1850777594-19:ctx-5c391d12 ctx-9cd12123 ctx-6326bb8c) (logid:fb2dbf4b) 
===END===  172.31.29.44 -- GET  
listall=True&apiKey=W0EWPYRPQu51YPDQ8s_0b4wDDuSqrZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw&command=listVpnConnections&response=json&signatureVersion=3&expires=2022-06-01T08%3A43%3A35%2B&signature=TBKYjvgMLESFTna9iXeGTJdKtc0%3D
2022-06-01 14:00:52,862 INFO  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Host 172.31.21.5 
OpaqueRef:d1a2d70a-25bd-37b3-c581-2249ccf88fc0: Host 172.31.21.5 is already 
setup.
2022-06-01 14:00:52,868 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) callHostPlugin failed for cmd: 
setIptables with args  due to The requested plugin could not be found.
2022-06-01 14:00:52,869 WARN  [c.c.h.x.r.w.x.CitrixSetupCommandWrapper] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Unable to setup
com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for 
cmd: setIptables with args  due to The requested plugin could not be found.
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:367)
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.setIptables(CitrixResourceBase.java:4706)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixSetupCommandWrapper.execute(CitrixSetupCommandWrapper.java:63)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixSetupCommandWrapper.execute(CitrixSetupCommandWrapper.java:45)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWrapper.execute(CitrixRequestWrapper.java:122)
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:1758)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(

Re: XenServer Agent is not coming up after upgrading from 7.1 to 8.2

2022-06-01 Thread Suresh Anaparti 
Hi Vivek,

This discussion thread might provide you some inputs: 
https://lists.apache.org/thread/7q6yybm3qcms21qcd8945kvrygpr1v86 

Also, check the docs here: 
http://docs.cloudstack.apache.org/en/4.16.1.0/installguide/hypervisor/xenserver.html#upgrading-xenserver-versions,
 and see if you have missed any upgrade step.


Regards,
Suresh

On 01/06/22, 2:17 PM, "Vivek Kumar"  wrote:

Hello Guys,


We have recently upgraded our XenServer  from 7.1 to 8.2. We are using 
CloudStack 4.16.1. But after the upgradation my status of host is showing 
alert. I have gone through the logs getting below error. Can someone help me 
out for this.



—



rZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw&command=listSystemVms&response=json&signatureVersion=3&expires=2022-06-01T08%3A43%3A33%2B&signature=x7KQg4LW2XPtTf%2BHHVn0Fm599xA%3D
2022-06-01 14:00:51,613 DEBUG [c.c.u.s.SSHCmdHelper] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Executing cmd: rm -f 
/opt/xensource/sm/hostvmstats.py 
/opt/xensource/bin/copy_vhd_to_secondarystorage.sh 
/opt/xensource/bin/copy_vhd_from_secondarystorage.sh 
/opt/xensource/bin/create_privatetemplate_from_snapshot.sh 
/opt/xensource/bin/vhd-util /opt/cloud/bin/copy_vhd_to_secondarystorage.sh 
/opt/cloud/bin/copy_vhd_from_secondarystorage.sh 
/opt/cloud/bin/create_privatetemplate_from_snapshot.sh /opt/cloud/bin/vhd-util
2022-06-01 14:00:52,750 DEBUG [c.c.a.ApiServlet] 
(qtp1850777594-19:ctx-5c391d12) (logid:fb2dbf4b) ===START===  172.31.29.44 -- 
GET  
listall=True&apiKey=W0EWPYRPQu51YPDQ8s_0b4wDDuSqrZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw&command=listVpnConnections&response=json&signatureVersion=3&expires=2022-06-01T08%3A43%3A35%2B&signature=TBKYjvgMLESFTna9iXeGTJdKtc0%3D
2022-06-01 14:00:52,756 DEBUG [c.c.a.ApiServer] 
(qtp1850777594-19:ctx-5c391d12 ctx-9cd12123) (logid:fb2dbf4b) CIDRs from which 
account 'Acct[0d808973-19be-11eb-9555-005056961200-admin] -- Account {"id": 2, 
"name": "admin", "uuid": "0d808973-19be-11eb-9555-005056961200"}' is allowed to 
perform API calls: 0.0.0.0/0,::/0
2022-06-01 14:00:52,761 DEBUG [c.c.a.ApiServlet] 
(qtp1850777594-19:ctx-5c391d12 ctx-9cd12123 ctx-6326bb8c) (logid:fb2dbf4b) 
===END===  172.31.29.44 -- GET  
listall=True&apiKey=W0EWPYRPQu51YPDQ8s_0b4wDDuSqrZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw&command=listVpnConnections&response=json&signatureVersion=3&expires=2022-06-01T08%3A43%3A35%2B&signature=TBKYjvgMLESFTna9iXeGTJdKtc0%3D
2022-06-01 14:00:52,862 INFO  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Host 172.31.21.5 
OpaqueRef:d1a2d70a-25bd-37b3-c581-2249ccf88fc0: Host 172.31.21.5 is already 
setup.
2022-06-01 14:00:52,868 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) callHostPlugin failed for cmd: 
setIptables with args  due to The requested plugin could not be found.
2022-06-01 14:00:52,869 WARN  [c.c.h.x.r.w.x.CitrixSetupCommandWrapper] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Unable to setup
com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for 
cmd: setIptables with args  due to The requested plugin could not be found.
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:367)
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.setIptables(CitrixResourceBase.java:4706)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixSetupCommandWrapper.execute(CitrixSetupCommandWrapper.java:63)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixSetupCommandWrapper.execute(CitrixSetupCommandWrapper.java:45)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWrapper.execute(CitrixRequestWrapper.java:122)
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:1758)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at 
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$S

XenServer Agent is not coming up after upgrading from 7.1 to 8.2

2022-06-01 Thread Vivek Kumar 
Hello Guys,


We have recently upgraded our XenServer  from 7.1 to 8.2. We are using 
CloudStack 4.16.1. But after the upgradation my status of host is showing 
alert. I have gone through the logs getting below error. Can someone help me 
out for this.



—


rZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw&command=listSystemVms&response=json&signatureVersion=3&expires=2022-06-01T08%3A43%3A33%2B&signature=x7KQg4LW2XPtTf%2BHHVn0Fm599xA%3D
2022-06-01 14:00:51,613 DEBUG [c.c.u.s.SSHCmdHelper] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Executing cmd: rm -f 
/opt/xensource/sm/hostvmstats.py 
/opt/xensource/bin/copy_vhd_to_secondarystorage.sh 
/opt/xensource/bin/copy_vhd_from_secondarystorage.sh 
/opt/xensource/bin/create_privatetemplate_from_snapshot.sh 
/opt/xensource/bin/vhd-util /opt/cloud/bin/copy_vhd_to_secondarystorage.sh 
/opt/cloud/bin/copy_vhd_from_secondarystorage.sh 
/opt/cloud/bin/create_privatetemplate_from_snapshot.sh /opt/cloud/bin/vhd-util
2022-06-01 14:00:52,750 DEBUG [c.c.a.ApiServlet] 
(qtp1850777594-19:ctx-5c391d12) (logid:fb2dbf4b) ===START===  172.31.29.44 -- 
GET  
listall=True&apiKey=W0EWPYRPQu51YPDQ8s_0b4wDDuSqrZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw&command=listVpnConnections&response=json&signatureVersion=3&expires=2022-06-01T08%3A43%3A35%2B&signature=TBKYjvgMLESFTna9iXeGTJdKtc0%3D
2022-06-01 14:00:52,756 DEBUG [c.c.a.ApiServer] (qtp1850777594-19:ctx-5c391d12 
ctx-9cd12123) (logid:fb2dbf4b) CIDRs from which account 
'Acct[0d808973-19be-11eb-9555-005056961200-admin] -- Account {"id": 2, "name": 
"admin", "uuid": "0d808973-19be-11eb-9555-005056961200"}' is allowed to perform 
API calls: 0.0.0.0/0,::/0
2022-06-01 14:00:52,761 DEBUG [c.c.a.ApiServlet] (qtp1850777594-19:ctx-5c391d12 
ctx-9cd12123 ctx-6326bb8c) (logid:fb2dbf4b) ===END===  172.31.29.44 -- GET  
listall=True&apiKey=W0EWPYRPQu51YPDQ8s_0b4wDDuSqrZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw&command=listVpnConnections&response=json&signatureVersion=3&expires=2022-06-01T08%3A43%3A35%2B&signature=TBKYjvgMLESFTna9iXeGTJdKtc0%3D
2022-06-01 14:00:52,862 INFO  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Host 172.31.21.5 
OpaqueRef:d1a2d70a-25bd-37b3-c581-2249ccf88fc0: Host 172.31.21.5 is already 
setup.
2022-06-01 14:00:52,868 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) callHostPlugin failed for cmd: 
setIptables with args  due to The requested plugin could not be found.
2022-06-01 14:00:52,869 WARN  [c.c.h.x.r.w.x.CitrixSetupCommandWrapper] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Unable to setup
com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for cmd: 
setIptables with args  due to The requested plugin could not be found.
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:367)
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.setIptables(CitrixResourceBase.java:4706)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixSetupCommandWrapper.execute(CitrixSetupCommandWrapper.java:63)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixSetupCommandWrapper.execute(CitrixSetupCommandWrapper.java:45)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWrapper.execute(CitrixRequestWrapper.java:122)
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:1758)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
2022-06-01 14:00:52,869 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Seq 1-2294302535168557057: 
Response Received:
2022-06-01 14:00:52,

Ubuntu 22.04 Release

2022-06-01 Thread Loth 
Hello Users,

Has any work been done regarding testing Cloudstack with Ubuntu 22.04,
and if so, which versions?

Thanks for any news.

Re: NPE while listing Snapshots

2022-06-01 Thread Suresh Anaparti 
Hi Antoine,

Thanks for the update, good to know that no more issues with snapshots listing.

The query result confirms why the snapshot location for the volume ids 110 and 
112 exists, these volumes are not yet removed.

Regards,
Suresh

From: Antoine Boucher 
Reply to: "users@cloudstack.apache.org" 
Date: Friday, 27 May 2022 at 10:09 PM
To: users 
Subject: Re: NPE while listing Snapshots

Hello Suresh,

I did your 2 commands on all 4 ids and I have no more issues on the listing the 
Snapshot from the webUI.

Here is the result of the query you requested:

mysql> SELECT id, uuid, name, account_id, pool_id, path, size, volume_type, 
state, removed FROM cloud.volumes WHERE id IN (110, 111, 112, 155);
+-+--+--++-+--+--+-+--+-+
| id  | uuid | name | account_id | pool_id 
| path | size | volume_type | state
| removed |
+-+--+--++-+--+--+-+--+-+
| 110 | 390198b4-45d4-425e-87c3-d0f11ef2ca11 | ROOT-109 | 16 |   4 
| 390198b4-45d4-425e-87c3-d0f11ef2ca11 |  42949672960 | ROOT| Ready
| NULL|
| 111 | NULL | ROOT-110 | 16 |   5 
| da585fd4-b10f-480b-9287-45ecb28b6355 |  85899345920 | DATADISK| Expunged 
| 2022-04-19 01:29:08 |
| 112 | 285140e4-555e-4cac-a2ec-afb4bd6921a8 | ROOT-111 | 16 |   3 
| 285140e4-555e-4cac-a2ec-afb4bd6921a8 |  53687091200 | ROOT| Ready
| NULL|
| 155 | da585fd4-b10f-480b-9287-45ecb28b6355 | ROOT-110 | 16 |  17 
| 4f29b0d2-a1e2-45bc-932a-31d67fd3c572 | 128849018880 | ROOT| Ready
| NULL|
+-+--+--++-+--+--+-+--+-+
4 rows in set (0.00 sec)


Thank you for all your help.

Regards,
Antoine

Antoine Boucher
antoi...@haltondc.com
[o] +1-226-505-9734
www.haltondc.com

“Data security made simple and affordable”


[cid:image001.png@01D875B3.631C6270]




Confidentiality Warning: This message and any attachments are intended only for 
the use of the intended recipient(s), are confidential, and may be privileged. 
If you are not the intended recipient, you are hereby notified that any review, 
retransmission, conversion to hard copy, copying, circulation or other use of 
this message and any attachments is strictly prohibited. If you are not the 
intended recipient, please notify the sender immediately by return e-mail, and 
delete this message and any attachments from your system.





 

On May 20, 2022, at 4:56 AM, Suresh Anaparti 
mailto:suresh.anapa...@shapeblue.com>> wrote:

Hi Antoine,

Thanks for sharing these details. The delete snapshot cmd failed with NPE, as 
the underlying primary storage doesn't exists.

Usually, when a snapshot is deleted, the backed up snapshot file is removed 
from the secondary storage, the status in the cloud.snapshots table for that 
snaphshot is marked as Destroyed, and the state in the cloud.snapshot_store_ref 
table marked as Destroyed for the entries of that snapshot (both, for 
store_role Primary and Image). Later, the storage garbage collector (when 
enabled), sets the removed date in cloud.snapshots table and removes the 
entries in cloud.snapshot_store_ref table.

You can manually update the DB with the same behavior, first try with one 
snapshot (117) and if no issues, apply it to others (109,127,138).

Sample sqls for snapshot id=117 below.

- UPDATE cloud.snapshots SET status = 'Destroyed', removed = now() WHERE id = 
117;

- DELETE FROM cloud.snapshot_store_ref WHERE snapshot_id = 117;


'111' corresponds to volume id, in the snapshot location 
'snapshots/16/111/66210b31-7445-4586-89ea-52a37f5b1ab5'. I see the record with 
volume id 111 is expunged (migrated to new id) from the email thread, not sure 
about volume ids 110 and 112. What's the output of the sql below.

- SELECT id, uuid, name, account_id, pool_id, path, size, volume_type, state, 
removed FROM cloud.volumes WHERE id IN (110, 111, 112, 155);


Regards,
Suresh

On 17/05/22, 4:36 AM, "Antoine Boucher" 
mailto:antoi...@haltondc.com>> wrote:

Hi Suresh,

Here ids the logs of Cmk delete snapshot id=117 and similar for id=109,127,138


2022-05-16 18:18:49,667 DEBUG [c.c.a.ApiServer] 
(qtp515715487-147449:ctx-9470efda ctx-7b642401) (logid:dc836839) CIDRs from 
which account 'Acct[2cee75f9-8bc4-11ec-9c43-001e67fd4838-admin] -- Account 
{"id": 2, "name": "admin", "uuid": "2cee75f9-8bc4-11ec-9c43-001e67fd4838"}' is 
allowed to perform API