Wiki source code of Announcements

Version 216.1 by mmorgan on 2023/08/31 16:52
Hide last authors
mmorgan 216.1 1 (% class="wikigeneratedid" %)
2 === **Collaboratory Drive issue (2023-08-31)** ===
3
4 Renaming an Office file in the Collaboratory Drive while that file is open in an Office session for collaborative editing can cause data loss. Before renaming a file, users should:
5
6 * open the file in Office
7 * wait to be the only user in the Office session (see the list of users at top right)
8 * click on the disk icon to force a save (icon is at top left)
9 * in the Drive, rename the file checking no user enters the Office session
10 * close the Office session checking no user enters the Office session
11
12 We are looking into how this issue can be fixed.
13
mmorgan 214.1 14 === **Collaboratory Lab issue (2023-08-22) (Resolved)** ===
15
16 The Collaboratory Lab had an issue with its instance running at CSCS. EBRAINS users are invited to select the JSC server instead when starting up the Lab.
17
mmorgan 215.1 18 The Lab was restored at CSCS. The issue was due to a storage problem that affected one of the key services that participate in providing the Lab service.
mmorgan 214.1 19
mmorgan 213.1 20 === **Collaboratory Office issue (2023-08-21) (Resolved)** ===
mmorgan 212.1 21
22 The Collaboratory Office service had an issue this morning. It seems the issue is caused by an automatic renewal of an SSL certificate that failed. We are looking to recover the service ASAP.
23
24 Please note that Collaboratory Office uses the open standard docx, xlsx, and pptx formats. The files can be downloaded to be read and possibly edited in MS Office and other clone alternatives. Users editing documents online should coordinate with others to avoid forking the document into multiple branches due to editing outside of a collaborative edition service.
25
mmorgan 208.1 26 === **Collaboratory issue (2023-07-04)** ===
hbpadmin 206.1 27
28 (% class="wikigeneratedid" %)
mmorgan 208.1 29 Some users may experience slow response times when accessing a service the first time in the day. We are working on resolving this ASAP. 
30 \\**Update 2023-07-10: **The issue has been identified. We are working to resolve this and, in the meantime, we will be performing some maintenance to help alleviate the issue. A maintenance window will be set for tomorrow.
hbpadmin 206.1 31
mmorgan 208.1 32 (% class="wikigeneratedid" %)
chaney08 210.1 33 **Update 2023-07-11: **Maintenance was performed to increase performance while we continue working on the underlying issue. 
chaney08 211.1 34 \\Due to the previous maintenance, we believe the issue has been alleviated. Although investigation will continue to prevent this issue from re-occurring, users should not get the timeout issue anymore. If you do, please contact support at [[https:~~/~~/ebrains.eu/support>>https://ebrains.eu/support]], thank you.
chaney08 209.1 35
36 (% class="wikigeneratedid" %)
mmorgan 208.1 37 This section will continue to be updated as we have more information.
38
hbpadmin 205.1 39 === **Collaboratory Lab issue (2023-05-31) (Resolved)** ===
chaney08 204.1 40
41 This morning, the Lab at CSCS went down due to an internal JupyterHub issue. This issue was resolved following a re-deployment of the Collaboratory Lab to CSCS.
42 \\We will continue investigating the root cause of this issue.
43
mmorgan 203.1 44 === **Collaboratory Drive issue this morning (2023-05-08) (resolved)** ===
45
46 This morning, the Collaboratory Drive server encountered an out of memory issue. The issue has been resolved. This should not have affected any data.
47
mmorgan 198.1 48 === **Collaboratory Drive & Lab work (2023-04-09)** ===
mmorgan 182.1 49
mmorgan 202.1 50 We are announcing a down time for the Collaboratory Drive this coming Sunday April 9 from noon CEST lasting potentially all day. --This will allow us to activate a secondary Drive server, mirror copy of the primary server, which we intend to use for backups only.--
mmorgan 197.1 51
52 During the coming days, we will also be tentatively deploying and exercising new policies in the Drive.
53
54 1. We will limit or disable the creation of [[core dumps>>https://en.wikipedia.org/wiki/Core_dump]] in the Drive by the Lab. An important number of large core dumps have recently been filling up the Drive, which has caused the disk full situation earlier this week much faster than would have happened otherwise.
55 1. We will limit the maximum file size that can be generated by the Lab, both in the Drive and in the local file system of the user's Lab container. This file size will be aligned with the maximum upload size limit to the Drive which is currently 1 GB. The reasons for this are:
56 11. In the Drive: the alignment of the policy of upload of files and Lab creation of files. The Drive is not intended for very large files. Collabs have a Bucket storage which is optimized for this purpose.
57 11. In the local file storage of Lab containers: each Lab container is only accessible to a single user, but the storage resource is shared at the OpenShift level by all the pods running on a same worker node. A Lab container therefore has the possibility of causing a disk full condition on the other users' containers. The file size limit will reduce this risk. Users are reminded that stress testing any resources provided on the EBRAINS RI is strictly forbidden without the explicit authorization from EBRAINS Technical Coordination.
58 1. We will "move" (copy and delete) files larger than the 1 GB limit from the Drive to the Bucket of the same collab. Files that are "moved" will be deleted from the Drive and a file with the same name extended with "_moved.txt" will be put in its place. This file will inform users to check the Bucket for their file. Example: the file **//MyTalk.mp4//** will be deleted and replaced by a file //**MyTalk.mp4_moved.txt**.//
59
60 The new policies are not technically releases but they will be announced in The Collaboratory [[Releases>>doc:Collabs.the-collaboratory.Releases.WebHome]] page.
61
mmorgan 199.1 62 Check this space for the announcement of the end of the work.
63
mmorgan 197.1 64 === **Collaboratory Drive issue (2023-04-04) (Resolved)** ===
65
chaney08 195.1 66 Some users are still experiencing issues while trying to access the Drive. We are investigating the issue and will update this announcement as soon as we have more information.
hbpadmin 194.1 67
mmorgan 196.1 68 The issues on the drive have been resolved.
hbpadmin 194.1 69
mmorgan 196.1 70 We are still looking to recover files that were lost due to the disk full condition earlier this week. It appears that there were no files lost that were older than Thursday March 30. If you identify any such file, please contact EBRAINS Support.
71
mmorgan 197.1 72 Update: We have looked into all our options for recovering lost data from the event earlier this week. We're sorry to have to announce that no more data will be recoverable. We are however going to reattempt a continuous backup strategy to limit the risk and potential extent of data loss.
73
mmorgan 196.1 74 === **Collaboratory Drive repair (2023-04-03) (Resolved)** ===
75
mmorgan 185.1 76 (% class="wikigeneratedid" %)
mmorgan 193.1 77 After resizing the Drive to address the issue mentioned in the previous announcement, we noticed that the drives of specific collabs have entered into an unstable state. Users may experience issues while trying to access these drives. We are currently repairing these issues and this page will be updated once fully repaired.
platform 189.1 78
mmorgan 193.1 79 (% class="wikigeneratedid" %)
80 The Drives of problematic collabs have been repaired. The repair process has unfortunately not been able to recover a few files. We are still looking whether recovery is possible.
81
mmorgan 192.1 82 === **Collaboratory Drive has filled up (2023-04-03) (Resolved)** ===
platform 189.1 83
84 (% class="wikigeneratedid" %)
mmorgan 185.1 85 We monitor the Drive usage to make sure that there is always enough space for users. It seems that a user has bypassed our limitations and created one or more extremely large files in the Drive filling up the Drive storage space. We are in the processing of adding space. We will also be looking to identify the user that filled up the Drive.
86
87 (% class="wikigeneratedid" %)
mmorgan 192.1 88 We have added additional disk space to the Drive. It seems the Drive was filled with a large number of core dumps generated over the past days. The reports we received suggested the Drive had enough spare space to run 2 more weeks. we are investigating that issue.
mmorgan 185.1 89
mmorgan 188.1 90 (% class="wikigeneratedid" %)
91 We will look into limiting the capability of generating core dumps in the Lab and automatically deleting core dumps after a limited time (e.g. a week). This will be discussed in the TC Weekly call on April 4 at 15:00 CET.
92
mmorgan 185.1 93 === **Openshift is down at CSCS (2023-03-23) (Resolved)** ===
94
mmorgan 184.1 95 The Openshift service at CSCS has failed overnight. We are working to identify the issue and recover the service ASAP.
mmorgan 182.1 96
97 The services affected are all those running on the OpenShift service at CSCS including:
98
99 * Collaboratory Lab at CSCS (users can use the Lab running at JSC by visiting [[lab.de.ebrains.eu>>https://lab.de.ebrains.eu]]),
100 * atlas viewers,
101 * simulation services (NEST desktop, TVB, Brain Simulation Platform)
102
mmorgan 186.1 103 The Openshift server has been restarted.
mmorgan 182.1 104
mmorgan 185.1 105 === **Collaboratory Lab at JSC is down (2023-03-08) (Resolved)** ===
hbpadmin 176.1 106
mmorgan 180.1 107 The Collaboratory Lab servers are currently down at JSC. The servers were initially down due to a power outage. However, power has been restored to JSC but the servers have not yet been restored. More information to be provided soon. In the meantime, Lab users still have access to the servers at CSCS.
hbpadmin 179.1 108
hbpadmin 181.1 109 Update: The servers at JSC have been restored.
110
mmorgan 180.1 111 === **Maintenance to Openshift (2023-02-21) (Resolved)** ===
hbpadmin 179.1 112
hbpadmin 177.1 113 Services that use the NFS filesystem on Openshift will be down today from 17:15 CET for up to 30 minutes. This includes the Collaboratory Lab.
hbpadmin 176.1 114
mmorgan 178.1 115 === **Collaboratory Office changing Docker image (2023-01-31) (Resolved)** ===
mmorgan 172.1 116
mmorgan 175.1 117 We are operating a change of the Docker image used for the Office service. A change of the image was operated last week when we had a license issue.
118
119 === **Collaboratory Office licensing issue (2023-01-24) (Resolved)** ===
120
mmorgan 172.1 121 (% class="wikigeneratedid" %)
122 The Collaboratory Office service uses the OnlyOffice software. The license file that we were using has expired. This greatly restricts the number of users that can use the service in edit mode simultaneously.
123
124 (% class="wikigeneratedid" %)
125 Our team has been trying to contact OnlyOffice to resolve the issue as quickly as possible. Responsiveness at OnlyOffice this week has been challenging.
126
mmorgan 173.1 127 (% class="wikigeneratedid" %)
128 In the meantime, users can download - edit - upload files but obviously this does not allow simultaneous edits by multiple users. Please check the history of files to make sure that you do not overwrite someone else's edits when uploading  your updated file.
129
mmorgan 174.1 130 (% class="wikigeneratedid" %)
131 **Resolved**: it seems the issue has been resolved
132
hbpadmin 171.1 133 === **Collaboratory Lab at JSC is not working (2022-12-13) (Resolved)** ===
hbpadmin 167.1 134
mmorgan 169.1 135 The JSC cloud infrastructure is experiencing issues which cause services running there to become unreliable. As such, the Lab instance at JSC is not usable. We are in contact with the JSC team and monitoring the situation. In the meantime, please select the CSCS site when starting a new Lab session.
hbpadmin 167.1 136
hbpadmin 171.1 137 **Resolved**: This issue was resolved by rebooting the worker node that was causing the issue.
138
mmorgan 173.1 139 === **Collaboratory Bucket is currently full** **(2022-11-03)(Done)** ===
hbpadmin 165.1 140
mmorgan 170.1 141 The quota for the Collaboratory Bucket is currently full. We are in the process of increasing this limit and will restore service as soon as possible. In the meantime, you still have read access to files that are stored in collab Buckets.
142 \\Update: Quota has been increased and full service has been restored.
hbpadmin 165.1 143
mmorgan 164.1 144 === **Six EBRAINS services will experience a short downtime (2022-10-27) (Done)** ===
mmorgan 163.1 145
146 The following 6 services will experience a short downtime today in order for us and the infrastructure team at CSCS to consolidate the status of the corresponding servers. We plan to stop the services one after the other for an estimated 5 minutes each during a 30-minute window (see banner). The services are:
147
148 1. Collaboratory IAM: authentication of users
149 1. Knowledge Graph Search
150 1. Neuroglancer: for the 3D visualisation of brain images
151 1. PLUS: an HBP internal project coordination tool
152 1. An internal tool for monitoring the EBRAINS platform which is not user facing
153 1. A deprecated service which we are maintaining to improve the user experience of a few users
154
mmorgan 164.1 155 The maintenance on each of these services has been completed.
mmorgan 163.1 156
hbpadmin 159.1 157 === **EBRAINS infrastructure causing issues with the Drive (2022-10-19) (Fixed)** ===
mmorgan 146.1 158
mmorgan 156.1 159 The Drive is currently down due to another issue at CSCS. We are working on getting this resolved as soon as possible. We will be checking with CSCS on their root cause analysis and see that steps are taken to avoid the recurrence of such an issue.
hbpadmin 149.1 160
hbpadmin 160.1 161 (% style="color:#3498db" %)Update 2022-10-19 18:30 CEST(%%): We again have access to the filesystem which hosts the files of the Drive. Unfortunately, the Drives of a few collabs have been corrupted(% style="color:#e74c3c" %) (%%)amid the multiple outages today. We are recovering the contents of the Drives of those collabs at least to their status last night. We are hoping that we might recover some of the modifications to files in the Drive (uploads and edits) today but it may be that they have been lost. We apologize for the inconvenience.
mmorgan 156.1 162
mmorgan 157.1 163 (% style="color:#3498db" %)Update 2022-10-19 23:00 CEST(%%): The verification/repair of the filesystem is still running. It should be finished by tomorrow morning. We will make the Drive service available first thing in the morning if the repair does not identify any blocking points.
mmorgan 156.1 164
hbpadmin 162.1 165 (% style="color:#3498db" %)Update 2022-10-20 10:00 CEST(%%): The verification/repair of the filesystem has finished. The Drive is now available for use again. (% style="color:#e74c3c" %)**Some data loss**(%%) has occurred for content uploaded or edited yesterday and we apologise for the inconvenience this has caused.
hbpadmin 158.1 166
mmorgan 150.1 167 === **EBRAINS infrastructure was down this morning (2022-10-19) (Fixed)** ===
hbpadmin 149.1 168
mmorgan 146.1 169 The cloud infrastructure at that hosts most EBRAINS services had at the [[Swiss National Computing Center (CSCS)>>https://cscs.ch]] experienced some downtime this morning from 9:25 to 10:15 CEST. This interrupted access to the storage of most of our services making them unavailable to end users. Service is up again.
170
171 We will update this page with more information when we receive information about the root causes.
172
173 We apologize to EBRAINS users for the down time. Please [[contact Support>>https://ebrains.eu/support]] if you still experience issues with any service.
174
mmorgan 152.1 175 === **Drive is currently down (2022-10-17) (Fixed)** ===
hbpadmin 142.1 176
mmorgan 143.1 177 The Drive is currently down and not usable. This is due to infrastructure issues and service will be restored as soon as possible.
hbpadmin 142.1 178
mmorgan 145.1 179 Update 2022-10-17 21:30 CEST: CSCS and RedHat are still debugging the issue.
mmorgan 143.1 180
mmorgan 151.1 181 2022-10-18: The issue has been resolved and the Drive is now accessible again. The issue was caused by the restart of an Openstack hypervisor with an inconsistent status of volumes in Openstack. This locked the VM running the Collaboratory Drive in a shutoff state.
chaney08 144.1 182
mmorgan 153.1 183 === **Unable to save files to Drive (2022-10-04) (Fixed)** ===
hbpadmin 139.1 184
185 The file system that the Drive runs on is currently full. Unfortunately, our detection of the file system being nearly full did not work. As such users cannot upload files nor save any changes to their files in the Drive. Due to another, unrelated issue, it is not possible for us to simply expand the file system. For this reason, we are currently in the process of moving the Drive data to a bigger volume. This is causing the delay. We will update this page as soon as we are finished with the move.
hbpadmin 140.1 186 \\Please note that as most services run off the Drive, this also affects the Lab, although you can run Notebooks and even modify notebooks, any changes you make will not be saved.
hbpadmin 139.1 187
mmorgan 143.1 188 NOTE: We transferred everything from the affected volume to a larger volume, the service is now usable again.
hbpadmin 141.1 189
mmorgan 153.1 190 === **No uploads allowed to Data-proxy (2022-08-31) (Fixed)** ===
hbpadmin 135.1 191
hbpadmin 138.1 192 At the moment uploads are not permitted due to the data-proxy exceeding its quota allowance. We are working to solve this as soon as possible. 
193 \\**Fixed: **Quota was increased, files can no be uploaded again.
hbpadmin 137.1 194
195 === **Collaboratory Drive maintenance (2022-08-19) (Completed)** ===
196
hbpadmin 136.1 197 The Drive was meant to be taken down for routine maintenance to increase the available space available for Drive storage this afternoon. That operation has had to be rescheduled due to technical issues on the storage infrastructure.
hbpadmin 135.1 198
chaney08 134.1 199 === **Intermittent issues with the Bucket (data-proxy) (Solved)** ===
200
201 As reported by the main banner, there had been intermittent issues with the Bucket occasionally going down for a short amount of time. This has been resolved by the maintenance performed at CSCS on August 10th. If you encounter any further issues related to the Bucket, please open a ticket to support.
202
mmorgan 133.1 203 === **Storage and Cloud service maintenance (2022-08-10) (Completed)** ===
mmorgan 129.1 204
mmorgan 131.1 205 This maintenance was shifted from August 3 to August 10 due to an incident on another server managed by the ETHZ central IT services.
206
mmorgan 130.1 207 A maintenance operation at CSCS requires that some HBP/EBRAINS services be stopped Wednesday August 3 morning. The services affected are those using NFS storage volumes on the Castor cloud service. EBRAINS service providers that migrate their VMs to CEPH storage ahead of that date can keep their services running during the maintenance.
mmorgan 129.1 208
mmorgan 130.1 209 **__Timeline__**: all times CEST
mmorgan 129.1 210
mmorgan 130.1 211 * **08:00**: Service providers shutdown services running on OpenStack or OpenShift at CSCS
212 * **08:30**: Maintenance start by CSCS team
213 * **12:00**: Planned maintenance end by CSCS team. Service providers check that services have come back online.(% style="color:#95a5a6" %) (% style="color:#1abc9c" %)Check this page for updates
chaney08 132.1 214 * (% style="color:#1abc9c" %)15:20: Maintenance ended at 15:20 CEST time.
mmorgan 129.1 215
mmorgan 130.1 216 The storage back-end used by HBP/EBRAINS services has been causing some issues which have had repercussions on access to the object storage and OpenStack cloud service and thereby on HBP/EBRAINS services which run on this infrastructure. The issue has been identified and CSCS is ready to deploy a patch on the storage back-end. This will require that services running on OpenStack at CSCS be stopped for the duration of the maintenance.
mmorgan 129.1 217
mmorgan 130.1 218 There is never a good time for maintenance. We’re heading into a few weeks when more users will be on vacation, and some of the service providers may also be away. Hopefully this will impact as few people as possible. We apologize in advance for any inconvenience the downtime may cause.
mmorgan 129.1 219
mmorgan 128.1 220 === **Infrastructure issues at CSCS (2022-08-01)** ===
mmorgan 127.1 221
mmorgan 129.1 222 The infrastructure at CSCS on which EBRAINS services run has failed over the weekend. August 1 was a bank holiday in Switzerland where CSCS is located. The situation was recovered before 10:00 CEST on Tuesday August 2.
mmorgan 127.1 223
mmorgan 129.1 224 The services affected were all those running on the OpenShift service at CSCS including:
mmorgan 127.1 225
mmorgan 128.1 226 * Collaboratory Lab at CSCS (please choose the JSC site when starting the Lab),
227 * image service,
228 * atlas viewers,
229 * simulation services (NEST desktop, TVB, Brain Simulation Platform)
mmorgan 127.1 230
mmorgan 128.1 231 The planned maintenance listed below is expected to prevent the recurring issues that have been experienced over the past months.
mmorgan 127.1 232
mmorgan 128.1 233 We apologize for the inconvenience.
mmorgan 127.1 234
hbpadmin 121.1 235 === **Infrastructure issues (2022-07-13)** ===
236
mmorgan 125.1 237 Several services on our EBRAINS **OpenShift **server running at CSCS were detected as having issues.
hbpadmin 121.1 238
mmorgan 125.1 239 These issues may potentially affect services running on that OpenShift server including:
hbpadmin 121.1 240
mmorgan 125.1 241 * Collaboratory Lab at CSCS (please choose the JSC site when starting the Lab),
242 * image service,
243 * atlas viewers,
244 * simulation services (NEST desktop, TVB, Brain Simulation Platform)
hbpadmin 121.1 245
mmorgan 126.1 246 The OpenShift situation has been resolved. Some services may need to be restarted. Please contact [[Support>>https://ebrains.eu/support]] if you identify a problem.
247
mmorgan 125.1 248 The Collaboratory **Bucket **service (aka data proxy) has been intermittently down over the past several days due to an issue with the Swift archive/object storage at the infrastructure level at CSCS.
249
mmorgan 126.1 250 We are working with the CSCS team to identify the cause of the issues with the Bucket service and we are having the infrastructure restarted any time issues occur. You can notify [[Support>>https://ebrains.eu/support]] if you identify any down time.
mmorgan 125.1 251
mmorgan 119.1 252 === **HBP and EBRAINS websites issue (2022-06-29)** ===
253
mmorgan 120.1 254 The HBP and EBRAINS main websites are down because of an issue with the .io top level domain DNS. This issue is preventing our websites from rendering images, CSS files, and other files referenced from the HTML of the web pages. The issue is not internal to our infrastructure nor to that of our cloud provider. We have decided to bring down the two websites for the time being.
mmorgan 119.1 255
mmorgan 120.1 256 The issue was resolved in the afternoon shortly after our provider confirmed their service had returned to nominal status.
257
mmorgan 117.1 258 === **Issue with the Bucket service (2022-06-27)** ===
259
mmorgan 118.1 260 The bucket service (aka data proxy) is down due to an issue with the Swift archive/object storage at the infrastructure level at CSCS. The issue has been resolved. It was caused by the high availability load balancers located in front of the Swift storage at CSCS.
mmorgan 117.1 261
262 We apologize for the inconvenience.
263
mmorgan 114.1 264 === **Maintenance of the Drive (2022-04-14)** ===
265
mmorgan 115.1 266 The drive service will be down for maintenance on Thursday April 14 from 18:00 CEST for an estimated 2 to 3 hours. We are performing a routine garbage collection on the storage. During the downtime, users will not have access to the Drive: no reading/downloading of files, no adding/modifying files. This in turn means the Lab will not be usable either.
mmorgan 114.1 267
268 We apologize in advance for the interruption and thank you for your understanding.
269
mmorgan 116.1 270 The maintenance is done.
271
mmorgan 112.1 272 === **Issue with the Drive (2022-02-05)** ===
273
mmorgan 113.1 274 The Drive server had an issue starting Saturday Feb 5 from 5 AM CET. The service was brought back online and was operational on Saturday. The issue was related to a disk full on the server caused by logs which then had other issues rebooting. No data was lost and backups were not affected.
mmorgan 112.1 275
mmorgan 110.1 276 === **Issue with OpenShift (2022-01-17)** ===
277
mmorgan 111.1 278 One of the NGINX servers running in front of our OpenShift service is down due to a problem at the infrastructure level. We are in communication with the infrastructure team to get the issue resolved as quickly as possible.
mmorgan 110.1 279
mmorgan 111.1 280 The issue was resolved by the infrastructure team. The server at fault is running again. All services are up and accessible again.
281
hbpadmin 108.1 282 === **Issue with the Collaboratory like/favourite feature (2022-01-13)** ===
283
hbpadmin 109.1 284 The feature to like/favourite a collab was down for a day due to a change in the deployment of the Wiki service. This issue has been resolved without data loss. We apologise for any inconvenience caused by this issue.
hbpadmin 108.1 285
mmorgan 107.1 286 === **Issue on the OpenShift server at CSCS (2021-12-28)** ===
hbpadmin 105.1 287
288 The EBRAINS OpenShift server running at CSCS was detected as having come down. This issue affects all the services running on that OpenShift server including:
289
290 * Collaboratory Lab,
291 * image service,
292 * atlas viewers,
293 * simulation services (NEST desktop, TVB, Brain Simulation Platform)
294
295 We are working with the CSCS team to reactivate the service ASAP.
296
mmorgan 106.1 297 The service was reestablished at around 14:15 CET. The infrastructure team will continue looking into the potential causes of the problem with RedHat. The suspected cause lies in network access to the storage.
hbpadmin 105.1 298
mmorgan 107.1 299 === **Issue on the Forum service (2021-12-27)** ===
mmorgan 106.1 300
301 The Forum service went down over the weekend along with one of the redundant OpenShift servers. The issue was due to a problem at the infrastructure level.
302
303 The Forum was unavailable for a few hours on Monday. There was not perceptible effect on the services running on OpenShift.
304
mmorgan 107.1 305 === **Issue on the OpenShift server at CSCS (2021-11-24)** ===
mmorgan 99.1 306
307 The EBRAINS OpenShift server running at CSCS was detected as having come down at 16:00 CEST. This issue affects all the services running on that OpenShift server including:
308
309 * Collaboratory Lab,
310 * image service,
311 * atlas viewers,
312 * simulation services (NEST desktop, TVB, Brain Simulation Platform)
313
mmorgan 102.1 314 We are working with the CSCS team and RedHat (provider of the OpenStack solution on which OpenShift runs) to reactivate the service ASAP.
mmorgan 99.1 315
mmorgan 104.1 316 The issue affected the central VM node of the OpenShift service. Restarting the VM required that we resolve multiple issues including restarting at the same IP address and unlocking the storage volumes of that VM. (% style="color:#16a085" %)The central node has now been restarted. The same issue has occurred on three other instances of OpenShift VMs. They have been restarted too. OpenShift is up and running again. The DNS redirection(s) to the maintenance page is being removed. The services should be operational again.
mmorgan 102.1 317
mmorgan 104.1 318 (% style="color:#16a085" %)The root cause seems to be at the infrastructure level and RedHat is involved in analyzing that.
319
mmorgan 100.1 320 We will keep updating this page with more information as it comes in.
321
mmorgan 91.1 322 === **Maintenance of multiple services (2021-11-11 to 2021-11-19)** ===
323
mmorgan 98.1 324 We are migrating the last of our services away from an old cloud infrastructure. The production services were taken down on Wednesday November 17 and are now all back online. We will continue working on the non-production services, to return the services to the redundancy level prior to the migration, and various final tweaks.
mmorgan 93.1 325
mmorgan 98.1 326 Please contact [[support>>https://ebrains.eu/support]] about any new issues you identify on our services.
mmorgan 93.1 327
mmorgan 95.1 328 The services which were migrated during this maintenance include:
mmorgan 91.1 329
mmorgan 94.1 330 * Collaboratory Bucket (% style="color:#2ecc71" %)**DONE**
mmorgan 96.1 331 * Knowledge Graph Search and API (% style="color:#2ecc71" %)**DONE**
mmorgan 97.1 332 * OpenShift servers which includes: (% style="color:#2ecc71" %)**DONE**
333 ** Collaboratory Lab, (% style="color:#2ecc71" %)**DONE**
334 ** image service, (% style="color:#2ecc71" %)**DONE**
mmorgan 91.1 335 ** atlas viewers,
336 ** simulation services (NEST desktop, TVB, Brain Simulation Platform)
337
mmorgan 94.1 338 * EBRAINS Docker registry, (% style="color:#2ecc71" %)**DONE**
mmorgan 95.1 339 * the Forum linked from the Collaboratory Wiki, (% style="color:#2ecc71" %)**DONE** (may have login issues)
mmorgan 94.1 340 * the Education website. (% style="color:#2ecc71" %)**DONE**
mmorgan 91.1 341
mmorgan 98.1 342 We apologize for the inconvenience and thank you for your understanding.
mmorgan 92.1 343
mmorgan 87.1 344 === **Technical difficulties on the Drive (2021-11-03)** ===
345
346 The Drive has experienced some technical difficulties over the past weeks caused by multiple issues.
347
348 A reboot of the Drive server due to a hardware failure revealed an issue in the communication between the Lab and the Drive. A container is started for each Lab user who opens the Lab in their browser to run their notebooks. That container remains active by default well beyond the end of the execution of the notebook and the closing of the browser tab running the Lab, unless the users explicitly stop their container. Those containers were causing unusually high traffic to the Drive. We identified the problem and found a solution with an upgrade of the tool which the Drive is based on. We have had to shift the deployment date for this fix multiple times but we will be announcing the deployment date ASAP. In the meantime **we ask Lab users to kindly stop their servers** from the JupyterLab menu when they are not actively working in the Lab. This is done from the JupyterLab menu: //File > Hub control panel > Stop my server//.
349
350 The cloud infrastructure that the Drive is running on is being upgraded and the Drive service had to be moved to the newer servers. An incorrect management command of the server caused the migration of the data to be launched twice, with the second transfer overwriting production data dated Nov 2 with stale data from Oct 20. Several backup issues stacked on top of this problem. We have been able to recover a backup which was made on the night of Sunday Oct 31 to Monday Nov 1. We are verifying that we cannot identify issues with this data before we reopen access to the Drive. **Some data loss is expected** for data stored on the Drive after that backup and before we put up a banner asking users, as a precaution, not to add new data to the Drive on Tuesday Nov 2 around noon. Many countries had a bank holiday on Nov 1 so for many users, the data loss should be of a few hours on Nov 2.
351
352 We sincerely apologize for the problems incurred. We appreciate that the service we provide must be trustworthy for our users. We are taking the following actions to ensure that similar problems do not happen again:
353
354 * Review of the backup procedures on the Drive server which will be extended to all EBRAINS services which we manage.
355 * Request notification from the underlying infrastructure when service accounts reach the limit imposed by their storage quota.
356 * Improve the identification of production servers to reduce the risk of the operations team misidentifying which servers are running production service.
mmorgan 90.1 357 * Improve our procedure for communication about such incidents.
mmorgan 87.1 358
mmorgan 89.1 359 (% style="color:#16a085" %)**The Drive service is up again. We have recovered all the data that we could. The Drive is working normally again. We will be performing a Drive upgrade ASAP. check the Wiki banner for more information.**
mmorgan 87.1 360
361 Additionally, the Collaboratory team will be looking into mirroring services onto more than one Fenix site to reduce down time when incidents occur. This task will be more challenging for some services than for others; it might not be materially feasible for some services, but we will be analysing possibilities for each Collaboratory service.
362
hbpadmin 86.1 363 === **Maintenance on 2021-10-19** ===
364
365 Due to migration to new hardware, various EBRAINS services will be down for up to 1 hour while these services and their data are migrated. Please See our [[Releases >>doc:Collabs.the-collaboratory.Releases.WebHome]]page for more information on our release.
366
mmorgan 84.1 367 === **Infrastructure failure on 2021-10-04** ===
368
mmorgan 85.1 369 A failure on the Openstack infrastructure at the Fenix site which hosts most of our services has brought down many EBRAINS service this morning before 9 AM CEST. A second event later in the morning at the same Fenix site brought down most other EBRAINS services. The infrastructure was brought back online in the afternoon and we have been reactivating services as quickly as possible. Some issues are still being addressed at the infrastructure level [17:00 CEST].
mmorgan 84.1 370
371 We apologize for the inconvenience and thank all users for their understanding.
372
chaney08 83.1 373 === **SSL Certificates expiring September 30th** ===
374
375 Our SSL certificates are produced by Let's Encrypt. One of their root certificates is expiring on September 30. This may cause issues for access to API services, especially from older browsers. You can find more information about these changes at the following links :
376
377 * [[https:~~/~~/letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/>>url:https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/]]
378 * [[https:~~/~~/letsencrypt.org/certificates/>>url:https://letsencrypt.org/certificates/]]
379
380 As mentioned in the above links, if you are using one of our APIs, you should take the following steps to prevent issues:
381
382 * You must trust ISRG Root X1 (not just DST Root CA X3)
383 * If you use OpenSSL, you must have version 1.1.0 or later
384
385 If you access our services via a browser, please ensure that you are using a modern browser,  you can find more information here : [[https:~~/~~/letsencrypt.org/docs/certificate-compatibility/>>url:https://letsencrypt.org/docs/certificate-compatibility/]]
386
387 If you are using an older device, you may no longer be able to access our services correctly, for a list of non-compatible devices please see [[https:~~/~~/letsencrypt.org/docs/certificate-compatibility/>>url:https://letsencrypt.org/docs/certificate-compatibility/]].
388
mmorgan 80.1 389 === **Collaboratory 1 shutdown (2021-09-02)** ===
hbpadmin 79.1 390
chaney08 81.1 391 Collaboratory 1 is shutting down Wednesday September 8th. As such, please ensure you have [[migrated>>https://wiki.ebrains.eu/bin/view/Collabs/collaboratory-migration/Tutorial/Migrate%20your%20data/]]  your data to Collaboratory 2. You can view our [[handy guide>>https://wiki.ebrains.eu/bin/view/Collabs/collaboratory-migration/Tutorial/Overview/]] on what data is migrated by our tools, as well as what is not covered by the semi-automated tools.
hbpadmin 79.1 392
393 If you follow the above links, you will also find recorded migrathons, where you can find a lot of information to help you migrate your data. If you encounter any issues or problems while migrating your data, please contact [[EBRAINS support>>https://ebrains.eu/support/]] and we will get back to you as soon as possible.
394
chaney08 82.1 395 NOTE: You are currently viewing Collaboratory 2, which will not be shut down.
396
mmorgan 80.1 397 === **Openshift issues (2021-07-09) (Resolved)** ===
hbpadmin 72.1 398
mmorgan 76.1 399 The Openshift service has gone down. As the Collaboratory Lab and the Image service both rely on this service, they are currently unavailable. We are investigating this issue and it will be resolved as soon as possible. We apologise for any inconvenience caused.
hbpadmin 72.1 400
mmorgan 80.1 401 **UPDATE 2021-07-12: **The issue seems to be with the Openstack servers. It is also affecting a few more VMs aside from the Openshift service. The infrastructure team is looking into it.
chaney08 75.1 402
mmorgan 80.1 403 **UPDATE 2021-07-12: **The Openstack issue has been fixed. Services should be back up and running. Thank you for your patience.
chaney08 77.1 404
mmorgan 80.1 405 === **Collaboratory Lab restart (2021-06-15)** ===
hbpadmin 67.1 406
hbpadmin 69.1 407 The Collaboratory lab will be restarted for the purpose of changing a few background configurations.
408
hbpadmin 70.1 409 === **Collaboratory User Group (UG) meeting** ===
hbpadmin 27.1 410
hbpadmin 28.1 411 The UG meeting is a great way to stay informed about recent and upcoming changes to the Collaboratory as well as making your voice and ideas heard directly by the developers. If you are interested in attending this meeting, or know someone who is interested, please feel free[[ to join these meetings>>https://wiki.ebrains.eu/bin/view/Collabs/collaboratory-user-group/Joining%20the%20group/]]
hbpadmin 27.1 412
chaney08 59.1 413 If you would like to see new features or feel certain functionality is required to improve the Collaboratory, please [[join the Collaboratory user group>>https://wiki.ebrains.eu/bin/view/Collabs/collaboratory-user-group/Joining%20the%20group/]], once joined, please do not hesitate to [[make your suggestions>>https://drive.ebrains.eu/lib/aac38e36-4bd9-48ee-9ae6-b876a65028aa/file/Collaboratory%20User%20Group%20-%20Suggestion%20box.docx]].
mmorgan 18.1 414
415
mmorgan 80.1 416 === **Drive issue (Resolved 2021-06-14)** ===
hbpadmin 70.1 417
418 There is currently an issue that prevents the Drive option from appearing in new collabs. Although you can still create new collabs and can access all of the other functionality provided, you will not have access to the Drive by default. You can request a Drive be manually added to your collab via support.
419 \\We apologise for any inconvenience this causes. 
420
421
chaney08 59.1 422 === **Drive issue (Solved)** ===
mmorgan 18.1 423
chaney08 59.1 424 Users have reported issues trying to access the drive. This is something we are aware of and trying to fix as soon as possible. This issue seems to be an Openshift problem.
hbpadmin 20.1 425
chaney08 59.1 426 Until this is resolved, users will have issues accessing any functionality that requires Drive access. This mainly concerns the Lab and to a less extant, any service that requires access to the drive.
hbpadmin 22.1 427
chaney08 59.1 428 **Potential fix: **We believe we have identified the issue and will be bringing the Lab service down for up to an hour at 10pm CEST on April 28th as we attempt to deploy this fix. All current Notebooks will be killed during this downtime. - Unfortunately this fix has not worked and we are looking at other solutions at the moment.
mmorgan 18.1 429
chaney08 59.1 430 **Potential fix 2: **We have another small release that should fix the issue at 13:30 CEST Today. All currently running notebooks will be killed during this downtime.
mmorgan 18.1 431
chaney08 59.1 432 This issue has been resolved, please let support know if you encounter any issues with the lab. Thank you for your understanding.
mmorgan 18.1 433
chaney08 59.1 434 We apologise for any inconvenience this has caused
hbpadmin 17.1 435
chaney08 59.1 436 === OnlyOffice license issue (Resolved) ===
437
hbpadmin 17.1 438 We are aware that some users are getting issues when trying to use OnlyOffice similar to the following image~:
439
mmorgan 18.1 440 [[image:1613726704318-340.png]].
hbpadmin 17.1 441
442 We are working on this issue and will have it fixed as soon as possible, thank you for your patience and we apologise for any inconvenience caused.
443
444
chaney08 59.1 445 === SSL certificates (2020-12-04) (Resolved) ===
hbpadmin 12.2 446
mmorgan 9.1 447 Our SSL Certificate provider (Let's Encrypt) has been using new certificates to sign our SSL certificates as described on their [[website>>https://letsencrypt.org/certificates]]. This requires updates on our servers and on your web browsers. The updates on your web browsers often go unnoticed by the user but in some cases your browser may inform you that it needs to fetch a new certificate. You can accept this safely; most browsers don't even mention it to the user.
mmorgan 7.1 448
449 Note that this is not the same as accepting an exception in your browser because of a bad certificate. Accepting such exceptions can put your data and credentials at risk of a person-in-the-middle attack.
450
451 We believe we have addressed all the issues that may arise from this change in SSL certificates. If you experience any issue, especially when accessing EBRAINS APIs, don't hesitate to contact [[support>>https://ebrains.eu/support]].
452
453
chaney08 59.1 454 === Files locked in the Drive (2020-09-30) (Resolved) ===
mmorgan 1.1 455
mmorgan 4.1 456 A few users have reported issues in saving OnlyOffice edits to the Drive of a collab.
mmorgan 1.1 457
mmorgan 4.1 458 We are looking into this. At the time being, it seems that a small number of files are locked by the Drive which prevents OnlyOffice to update these files when they are edited online.
mmorgan 1.1 459
mmorgan 4.1 460 We are actively trying to correct the problem as promptly as possible.
mmorgan 1.1 461
mmorgan 4.1 462 ==== The temporary workaround ====
mmorgan 2.1 463
mmorgan 4.1 464 When you open a file in OnlyOffice:
mmorgan 1.1 465
mmorgan 4.1 466 1. check if other users are editing the same file. The count appears at the top right corner.
467 1. perform a trivial edit and save
468 1. if you are the only user with that file open, you can trust the presence/absence of a warning message from OnlyOffice
469 1. if multiple users have the file open simultaneously, you can:
470 11. choose to trust the first user who opened it to have checked, or
471 11. check in the Drive the timestamp of the file that you just saved
mmorgan 1.1 472
mmorgan 4.1 473 OnlyOffice will notify you when you try to save a file and the save fails. If that happens:
mmorgan 1.1 474
mmorgan 4.1 475 1. read the message
476 1. use File > Download as ... > docx or pptx or xlsx to save the file to your computer
477 1. close OnlyOffice. (% style="color:#e74c3c" %)**DO NOT KEEP LOCKED FILES OPEN IN ONLYOFFICE.**(%%) It would mislead others.
478 1. rename the file by adding (% style="color:#3498db" %)//**_UNLOCKED**//(%%) at the end of the filename, before the extension
479 1. upload the file with its new name
480 1. work on this new file
mmorgan 1.1 481
mmorgan 4.1 482 We apologize for the inconvenience and thank you for your understanding.
483
484 The Collaboratory team