Hi guys, just to let you know that for the last few days since starting to setup OSI PI using the documentation, documentation very seldomly loads, I am constantly facing the following scenario even after many page refreshes, this is on both Windows and Mac.
In addition in developer console you can see many errors, unsure if entirely related but believe it is.
Hope this information helps you resolve the issue.
Oct 9, 2018 12:59 PM
Hi Adam, I agree, sometimes this does happen. It was covered but the problem is persisting.
Oct 9, 2018 1:28 PM
I just emailed the team responsible for Live Library. Thanks for reporting that the issue is persisting!
Seb
Oct 9, 2018 1:37 PM
Thanks for the images, particularly the 2nd one. The issue also affects us OSIsoft employees, so we are all in the same boat here.
Nice, i just noticed that when i have my developer tools open in Chrome, the LiveLibrary is much more responsive! It does throw the errors mentioned, but i have not been able to reproduce a failed load of an item...
Always nice, issues that disappear while debugging!
Now i did manage to capture an issue during Developer mode:
So that appears to generate internal server error (GET returns 500)
Oct 11, 2018 3:10 PM
Thanks everyone for reporting back your experiences.
We have been working with our network team and are making some adjustments to our load balancer at 9am EST on Friday, 2018-10-12.
We'd love to hear your feedback to see if there is any change in the situation after that time.
It appears more reliable and a bit quicker, but still some 500 errors now and then:
Failed to load resource: the server responded with a status of 500 ()
AND
Refused to connect to 'http://livelibrary.osisoft.com/LiveLibrary/web/ui.xql?action=html&resource=publist_home.html' because it violates the following Content Security Policy directive: "connect-src 'self' *.osisoft.com *.test.osisoft.int api-osisoft.db-ip.com ".
AND
Oct 12, 2018 7:37 AM
Hi Roger,
Please note that Timothy Martin announced the load balancer maintenance as future event: 9am EST on Friday, 2018-10-12
I didn't expect any change at the current time but am happy you already recognize an improved behavior
Ah, i skipped over the missing C in EST.... One small letter, one huge difference in time!
...and now started writing a loadtesting script to capture proper results...
Hi guys, I am still finding the issue also and issues within dev console still remain:
