Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
czinu
Contributor

show-task failure with "no scope found for client session"

Hello,

 

can anyone point me to the place where I could find what might have gone wrong?

 

{'tasks': [{'task-id': '01234567-89ab-cdef-867c-f49dd86d35a1', 'task-name': 'Publish operation', 'status': 'failed', 'progress-percentage': 100, 'suppressed': False, 'task-details': [{'fault-message': 'no scope found for client session J1_jQ1Rj6Yq48BzZ6dYR4pUO_aQO0nv_zaKACyBKuRc'}]}]}

 

Thanks in advance.

0 Kudos
15 Replies
_Val_
Admin
Admin

Other than the error message, any context? What are you doing, what is failing?

the_rock
Champion
Champion

@_Val_ asked you a good question...what exactly are you trying to do here? if you give us bit more context/description, we can try point you in right direction.

0 Kudos
czinu
Contributor

This message appears randomly after simple "add-host". Can you suggest any place in the logs which I can find some useful information?

thx

0 Kudos
_Val_
Admin
Admin

Hi, "randomly" here is very unlikely. 

You can check $FWDIR/log/api.elg (troubleshooting) and $FWDIR/log/api.csv (calls and results) for details of an issue. 

0 Kudos
czinu
Contributor

is it the same on the MDS as I cannot see such files?

0 Kudos
_Val_
Admin
Admin

Depends on the environment you are connected to.

If it is a specific CMA, "mdsenv [<Name or IP address of Domain Management Server>]", then the same files as stated above. If on the global context, do not change the environment.

 

0 Kudos
_Val_
Admin
Admin

Here is en example:

[Expert@MyMDS:0]# mdsstat
+-----------------------------------------------------------------------------------------------------+
|                                      Processes status checking                                      |
+------+--------------------+-----------------+-------------+-------------+-------------+-------------+
| Type | Name               | IP address      | FWM         | FWD         | CPD         | CPCA        |
+------+--------------------+-----------------+-------------+-------------+-------------+-------------+
| MDS  |          -         | 192.168.3.51    | up 10086    | up 11422    | up 5427     | up 11440    |
+------+--------------------+-----------------+-------------+-------------+-------------+-------------+
| CMA  | MyDomain_Server    | 192.168.3.240   | up 10891    | up 8199     | up 7670     | up 9536     |
+------+--------------------+-----------------+-------------+-------------+-------------+-------------+
| Total Domain Management Servers checked: 1     1 up   0 down                                        |
| Tip: Run mdsstat -h for legend                                                                      |
+-----------------------------------------------------------------------------------------------------+
[Expert@MyMDS:0]#
[Expert@MyMDS:0]# mdsenv MyDomain_Server
[Expert@MyMDS:0]#
[Expert@MyMDS:0]# echo $FWDIR
/opt/CPmds-R81.10/customers/MyDomain_Server/CPsuite-R81.10/fw1
[Expert@MyMDS:0]#

 

0 Kudos
czinu
Contributor

[Expert@CP-MDS-8040:0]# mdsstat
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Processes status checking |
+------+--------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+-------------+-------------+-------------+
| Type | Name | IP address | FWM | FWD | CPD | CPCA |
+------+--------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+-------------+-------------+-------------+
| MDS | - | 192.168.1.49 | up 10333 | up 10331 | up 5163 | up 10515 |
+------+--------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+-------------+-------------+-------------+
| CMA | CP-MS-8040 | 192.168.1.50 | up 8890 | up 8901 | up 8684 | up 9231 |
+------+--------------------------------------------------------------------------------------------------------------------------------+-----------------+-------------+-------------+-------------+-------------+
| Total Domain Management Servers checked: 1 1 up 0 down |
| Tip: Run mdsstat -h for legend |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
[Expert@CP-MDS-8040:0]# mdsenv CP-MS-8040
[Expert@CP-MDS-8040:0]# ls $FWDIR/log/ | grep api
[Expert@CP-MDS-8040:0]# echo $FWDIR
/opt/CPmds-R80.40/customers/CP-MS-8040/CPsuite-R80.40/fw1

 

Am I missing something in the config that nothing is logged?

0 Kudos
_Val_
Admin
Admin

Let's try on MDS level first

 

0 Kudos
czinu
Contributor

Only api references I can find are those:

 

[Expert@CP-MDS-8040:0]# find / -name api
/var/tmp/api
/opt/CPsuite-R80.40/fw1/api
/opt/CPsuite-R80.40/fw1/bin/api

0 Kudos
_Val_
Admin
Admin

Logs should be there. Open a TAC call then.

0 Kudos
_Val_
Admin
Admin

And I believe for "find" command, you need to use api*. Search /var/log/ partition and not root

0 Kudos
czinu
Contributor

or even *api*  - thx for this suggestion : )

 

[Expert@CP-MDS-8040:0]# find / -name *api*

(...)

/var/log/opt/CPsuite-R80.40/fw1/log/api_sh.elg
/var/log/opt/CPsuite-R80.40/fw1/log/api.csv
/var/log/opt/CPsuite-R80.40/fw1/log/api.json
/var/log/opt/CPsuite-R80.40/fw1/log/api.elg.1
/var/log/opt/CPsuite-R80.40/fw1/log/api.elg

(...)

 

Let me analyze logs and get back with solution or additional question(s) : )

_Val_
Admin
Admin

Cool. Looking forward to hearing the results.

0 Kudos
czinu
Contributor

I was off for some time, but I have an update.

What we were actually doing is getting results of several "show task" calls in a loop and then logout.

Looks like a timing issue. After setting additional 2 sec of time.sleep to logout api call issue is gone. Previously when logout was called straight after last 'show task' all of them were failing with the same "no scope" message. I am attaching output, maybe you can find something interesting here or it will be useful for someone in the future. I have another issue, but I will open separate post for that.

0 Kudos