Announcements - HBP Wiki

(% class="wikigeneratedid" %)

=== **Infrastructure issues (2022-07-13)** ===

Several services on our EBRAINS OpenShift server running at CSCS was detected as having issues. This issue is causing the Collaboratory Lab service running on CSCS to no longer function, please use the Julich instance for now instead. Other services may also be affected by this outage.

5

6

We are working with the CSCS team to reactivate the service ASAP.

7

8

The bucket service (aka data proxy) is intermittently down due to an issue with the Swift archive/object storage at the infrastructure level at CSCS

9

10

=== **HBP and EBRAINS websites issue (2022-06-29)** ===

11

12

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.

13

14

The issue was resolved in the afternoon shortly after our provider confirmed their service had returned to nominal status.

15

16

=== **Issue with the Bucket service (2022-06-27)** ===

17

18

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.

19

20

We apologize for the inconvenience.

21

22

=== **Maintenance of the Drive (2022-04-14)** ===

23

24

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.

25

26

We apologize in advance for the interruption and thank you for your understanding.

27

28

The maintenance is done.

29

30

=== **Issue with the Drive (2022-02-05)** ===

31

32

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.

33

34

=== **Issue with OpenShift (2022-01-17)** ===

35

36

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.

37

38

The issue was resolved by the infrastructure team. The server at fault is running again. All services are up and accessible again.

39

40

=== **Issue with the Collaboratory like/favourite feature (2022-01-13)** ===

41

42

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.

43

44

=== **Issue on the OpenShift server at CSCS (2021-12-28)** ===

45

46

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:

* Collaboratory Lab,

* image service,

* atlas viewers,

* simulation services (NEST desktop, TVB, Brain Simulation Platform)

52

53

We are working with the CSCS team to reactivate the service ASAP.

54

55

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.

56

57

=== **Issue on the Forum service (2021-12-27)** ===

58

59

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.

60

61

The Forum was unavailable for a few hours on Monday. There was not perceptible effect on the services running on OpenShift.

62

63

=== **Issue on the OpenShift server at CSCS (2021-11-24)** ===

64

65

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:

* Collaboratory Lab,

* image service,

* atlas viewers,

* simulation services (NEST desktop, TVB, Brain Simulation Platform)

71

72

We are working with the CSCS team and RedHat (provider of the OpenStack solution on which OpenShift runs) to reactivate the service ASAP.

73

74

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.

75

76

(% style="color:#16a085" %)The root cause seems to be at the infrastructure level and RedHat is involved in analyzing that.

77

78

We will keep updating this page with more information as it comes in.

79

80

=== **Maintenance of multiple services (2021-11-11 to 2021-11-19)** ===

81

82

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.

83

84

Please contact [[support>>https://ebrains.eu/support]] about any new issues you identify on our services.

85

86

The services which were migrated during this maintenance include:

87

88

* Collaboratory Bucket (% style="color:#2ecc71" %)**DONE**

89

* Knowledge Graph Search and API (% style="color:#2ecc71" %)**DONE**

90

* OpenShift servers which includes: (% style="color:#2ecc71" %)**DONE**

91

** Collaboratory Lab, (% style="color:#2ecc71" %)**DONE**

92

** image service, (% style="color:#2ecc71" %)**DONE**

93

** atlas viewers,

94

** simulation services (NEST desktop, TVB, Brain Simulation Platform)

95

96

* EBRAINS Docker registry, (% style="color:#2ecc71" %)**DONE**

97

* the Forum linked from the Collaboratory Wiki, (% style="color:#2ecc71" %)**DONE** (may have login issues)

98

* the Education website. (% style="color:#2ecc71" %)**DONE**

99

100

We apologize for the inconvenience and thank you for your understanding.

101

102

=== **Technical difficulties on the Drive (2021-11-03)** ===

103

104

The Drive has experienced some technical difficulties over the past weeks caused by multiple issues.

105

106

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//.

107

108

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.

109

110

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:

111

112

* Review of the backup procedures on the Drive server which will be extended to all EBRAINS services which we manage.

113

* Request notification from the underlying infrastructure when service accounts reach the limit imposed by their storage quota.

114

* Improve the identification of production servers to reduce the risk of the operations team misidentifying which servers are running production service.

115

* Improve our procedure for communication about such incidents.

116

117

(% 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.**

118

119

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.

120

121

=== **Maintenance on 2021-10-19** ===

122

123

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.

124

125

=== **Infrastructure failure on 2021-10-04** ===

126

127

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].

128

129

We apologize for the inconvenience and thank all users for their understanding.

130

131

=== **SSL Certificates expiring September 30th** ===

132

133

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 :

134

135

* [[https:~~/~~/letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/>>url:https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/]]

136

* [[https:~~/~~/letsencrypt.org/certificates/>>url:https://letsencrypt.org/certificates/]]

137

138

As mentioned in the above links, if you are using one of our APIs, you should take the following steps to prevent issues:

139

140

* You must trust ISRG Root X1 (not just DST Root CA X3)

141

* If you use OpenSSL, you must have version 1.1.0 or later

142

143

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/]]

144

145

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/]].

146

147

=== **Collaboratory 1 shutdown (2021-09-02)** ===

148

149

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.

150

151

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.

152

153

NOTE: You are currently viewing Collaboratory 2, which will not be shut down.

154

155

=== **Openshift issues (2021-07-09) (Resolved)** ===

156

157

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.

158

159

**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.

160

161

**UPDATE 2021-07-12: **The Openstack issue has been fixed. Services should be back up and running. Thank you for your patience.

162

163

=== **Collaboratory Lab restart (2021-06-15)** ===

164

165

The Collaboratory lab will be restarted for the purpose of changing a few background configurations.

166

167

=== **Collaboratory User Group (UG) meeting** ===

168

169

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/]]

170

171

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]].

172

173

174

=== **Drive issue (Resolved 2021-06-14)** ===

175

176

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.

177

\\We apologise for any inconvenience this causes.

178

179

180

=== **Drive issue (Solved)** ===

181

182

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.

183

184

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.

185

186

**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.

187

188

**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.

189

190

This issue has been resolved, please let support know if you encounter any issues with the lab. Thank you for your understanding.

191

192

We apologise for any inconvenience this has caused

193

194

=== OnlyOffice license issue (Resolved) ===

195

196

We are aware that some users are getting issues when trying to use OnlyOffice similar to the following image~:

197

198

[[image:1613726704318-340.png]].

199

200

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.

201

202

203

=== SSL certificates (2020-12-04) (Resolved) ===

204

205

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.

206

207

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.

208

209

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]].

210

211

212

=== Files locked in the Drive (2020-09-30) (Resolved) ===

213

214

A few users have reported issues in saving OnlyOffice edits to the Drive of a collab.

215

216

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.

217

218

We are actively trying to correct the problem as promptly as possible.

219

220

==== The temporary workaround ====

221

222

When you open a file in OnlyOffice:

223

224

1. check if other users are editing the same file. The count appears at the top right corner.