# Swan002 unhealthy?

**URL:** <https://swan-community.web.cern.ch/t/swan002-unhealthy/86>\
**Category:** General chat\
**Created:** [June 7, 2019, 6:52am UTC](https://swan-community.web.cern.ch/t/swan002-unhealthy/86 "2019-06-07T06:52:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pfeiffer](https://swan-community.web.cern.ch/user_avatar/swan-community.web.cern.ch/pfeiffer/32/23_2.png) [@pfeiffer](https://swan-community.web.cern.ch/u/pfeiffer)\
**Post date:** [June 7, 2019, 6:52am UTC](https://swan-community.web.cern.ch/t/swan002-unhealthy/86/1 "2019-06-07T06:52:00Z")

</div>

Hi SwanOps,

swan002 seems a bit sick this morning, I get:

 ![image](https://swan-community.web.cern.ch/uploads/default/original/1X/ce55c10043209d0adfa68d72d91b49ac8a11cecd.png)

when connecting via swan.cern.ch (or directly) – using explicitly swan003 works OK … maybe you can bring it to a doc … 🙂

Thanks,  
cheers, andreas

---

<div class="post-metadata">

**Author:** ![pmrowczy](https://swan-community.web.cern.ch/letter_avatar_proxy/v4/letter/p/c5a1d2/32.png) [@pmrowczy](https://swan-community.web.cern.ch/u/pmrowczy)\
**Post date:** [June 7, 2019, 7:20am UTC](https://swan-community.web.cern.ch/t/swan002-unhealthy/86/3 "2019-06-07T07:20:42Z")

</div>

Ok, sorry, I noticed that when you went directly it worked. Misunderstood with another issue.

For me, swan.cern.ch works correctly. I will look into your issue

---

<div class="post-metadata">

**Author:** ![pfeiffer](https://swan-community.web.cern.ch/user_avatar/swan-community.web.cern.ch/pfeiffer/32/23_2.png) [@pfeiffer](https://swan-community.web.cern.ch/u/pfeiffer)\
**Post date:** [June 7, 2019, 7:43am UTC](https://swan-community.web.cern.ch/t/swan002-unhealthy/86/4 "2019-06-07T07:43:15Z")

</div>

Hi Piotr,

sorry for being a bit ambiguous. ☹ I had the problem when I went to swan.cern.ch and got redirected to swan002.cern.ch from there, then I tried explicitly swan003.cern.ch which worked OK and went back to 002 which still failed. So I guess something is wrong with that machine (swan002).

HTH,  
cheers, andreas

---

<div class="post-metadata">

**Author:** ![pmrowczy](https://swan-community.web.cern.ch/letter_avatar_proxy/v4/letter/p/c5a1d2/32.png) [@pmrowczy](https://swan-community.web.cern.ch/u/pmrowczy)\
**Post date:** [June 7, 2019, 8:06am UTC](https://swan-community.web.cern.ch/t/swan002-unhealthy/86/5 "2019-06-07T08:06:33Z")

</div>

swan002 is healthy, there are many people working in there. I am investigating why you failed.

---

<div class="post-metadata">

**Author:** ![pmrowczy](https://swan-community.web.cern.ch/letter_avatar_proxy/v4/letter/p/c5a1d2/32.png) [@pmrowczy](https://swan-community.web.cern.ch/u/pmrowczy)\
**Post date:** [June 7, 2019, 8:45am UTC](https://swan-community.web.cern.ch/t/swan002-unhealthy/86/6 "2019-06-07T08:45:36Z")

</div>

@pfeiffer I can see you are not the only one having this issue in that instance, I will escalate

Jun 7 08:46:55 swan-proto4 66a21bd481e6: [W 2019-06-07 08:46:55.070 pfeiffer log:158] 403 GET /user/pfeiffer/oauth\_callback?code=[secret]&state=[secret] (@::1) 57.36ms  
Jun 7 08:46:56 swan-proto4 66a21bd481e6: [W 2019-06-07 08:46:56.965 pfeiffer auth:866] oauth state ‘some-hash’ != None  
Jun 7 08:46:56 swan-proto4 66a21bd481e6: [W 2019-06-07 08:46:56.966 pfeiffer web:1667] 403 GET /user/pfeiffer/oauth\_callback?code=some-hash&state=some-hash (::1): oauth state does not match. Try logging in again.
