Changes for page Troubleshooting

Last modified by kindler on 2025/05/14 16:54
From version 51.1
edited by kindler
on 2025/05/14 16:54
Change comment: There is no comment for this version
To version 37.1
edited by kindler
on 2022/01/27 09:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,29 +4,8 @@
4 4  (% class="wikigeneratedid" %)
5 5  For more information on the Collaboratory, please seee the [[documentation of the EBRAINS Collaboratory environment>>https://wiki.ebrains.eu/bin/view/Collabs/the-collaboratory/]].
6 6  
7 -== Temporary problems ==
8 -
9 -Currently none known.
10 -
11 11  == Jupyter notebook environment ("Lab") related ==
12 12  
13 -=== Error message "RuntimeError: EBRAINS kernel mismatch. Expected: EBRAINS-24.04 Actual: EBRAINS-25.02. Please select the appropriate kernel." ===
14 -
15 -The BrainScaleS notebooks intended to be used with one of the "stable release" kernels in the EBRAINS Jupyter environment check for a specific kernel version (e.g. for EBRAINS-24.04). When a newer docker image is deployed on the EBRAINS application servers (like e.g. on 14 May 2025) several old kernels are not available in that new environment (e.g. due to incompatibilities with a newer Jupyter version). Then the BrainScaleS notebooks from the stable release branch in git can not run.
16 -
17 -Options to fix this:
18 -
19 -* use the notebooks from the "experimental" release branch of the BrainScaleS notebooks. These notebooks check for the "experimental" kernel name. They are also usually the recommended-for-use-of-BrainSclaeS one, as we frequently add features and fix problems for BrainScaleS. 
20 -To get the newest version of the experimental release ones use this git clone command in the Terminal (can be started via File > New > Terminal inside the Lab): 
21 -//git clone https:~/~/github.com/electronicvisions/brainscales2-demos.git ~-~-branch jupyter-notebooks//
22 -
23 -* or get a fresh copy of the stable release BrainScaleS notebooks from the git repository by using (this does only help after the repository has been updated after a change of the docker image):
24 -//git clone https:~/~/github.com/electronicvisions/brainscales2-demos.git ~-~-branch jupyter-notebooks-experimental//
25 -
26 -* or change the name, the notebooks test for by hand (note: if there is an incompatible change in a kernel just changing the expected kernel name will of course not help. It will then only create an error further down in the execution).
27 -** in the directory, where the notebook is stored, find the _static/common sub-directory
28 -** in that open the file collab_helpers.py and change the check (around line 19)
29 -
30 30  === Error message "Error in Authenticator.pre_spawn_start: ... 401: Unauthorized" ===
31 31  
32 32  When a new user accesses the Lab in a new collab for the first time, it is possible, that the JuypterLab is not starting and instead shows a "...401 Unauthorized" message.
... ... @@ -35,13 +35,13 @@
35 35  
36 36  === No example notebooks in the Jupyter notebook environment ("Lab") ===
37 37  
38 -When starting the Jupyter notebook environment for the first time it can take a bit (without visible "in progress" indication) until the example files appear in the file-chooser. Until then the list is just empty. So the fix here is "have a minute patience", then click the "Lab" link again.
17 +When starting the Jupyter notebook environment for the first time it takes about a minute (without visible "in progress" indication) until the example files appear in the file-chooser. Until then the list is just empty. So the fix here is "have a minute patience", then click the "Lab" link again.
39 39  
40 40  [[image:NoFiles.png]]
41 41  
42 42  === Timeout when starting the Jupyter notebook environment ("Lab") ===
43 43  
44 -It is possible, that accessing the "Lab" link results in a "timeout" message. This can happen, when the lab environment is started for the first time on one of the virtual machines providing the service, as the very first start per machine takes some time (in the order of 2 minutes). Accessing the "Lab" link again after a few minutes usually works.
23 +It is possible, that accessing the "Lab" link results in a "timeout" message. This can happen, when the lab environment is started for the first time on one of the virtual machines providing the service, as the very first start per machine takes quite some time (in the order of 2 minutes). Accessing the "Lab" link again after a few minutes usually works.
45 45  
46 46  === Lab error message "Cannot open - Could not find path..." ===
47 47  
... ... @@ -54,21 +54,20 @@
54 54  [[image:1623846323177-898.png||height="287" width="350"]]
55 55  
56 56  
57 -=== Error message: "Could not identify EBRAINS kernel " ===
36 +=== Test jobs make problems at Jülich ===
58 58  
59 -If your notebook shows "RuntimeError: Could not identify EBRAINS kernel (probably too old version). Please select the appropriate kernel EBRAINS_experimental_release.": Please check, whether an EBRAINS kernel has been selected as kernel for the notebook execution.  In the example screenshot below the "Python 3 (ipykernel)" has been used, as shown in the upper right hand corner of the tab with the notebook.
38 +Since August 2021 accessing the "Lab" link in the left hand navigation menu brings up a site selection menu:
60 60  
61 -[[image:1666184857320-440.png]]
40 +[[image:Screenshot 2021-08-30 at 19.00.59.png||height="252" width="300"]]
62 62  
42 +Via choosing a different lab execution site it is be possible to choose a specific site, if there are specific needs for the created Jupyter virtual machine for a given task (e.g. a large memory requirement). Currently all the examples do not need any site specific features, so you can select in principle any site. The "safe choice" is to use CSCS as the primary execution site.
63 63  
64 -Fix: click the current kernel name to get the kernel selection dialog box and select the "EBRAINS_experimental_release" kernel (blue highlight in the screenshot shown below):
65 65  
66 -[[image:image-20221019150927-1.png]]
45 +=== ===
67 67  
68 -=== Import error for hbp_service_client ===
69 69  
70 -The hbp_service_client was needed for the now not-existing-any-longer Collaboratory version 1. The import line can be deleted from scripts.
71 71  
49 +
72 72  == BrainScaleS-2 specific ==
73 73  
74 74  The [[BrainScaleS external user chat>>https://chat.bioai.eu/external-users/channels/town-square]] has service announcements (e.g. when a system is down due to maintenance) and is also a good place to ask general questions.
... ... @@ -110,10 +110,6 @@
110 110  
111 111  The [[BrainScaleS external user chat>>https://chat.bioai.eu/external-users/channels/town-square]] has service announcements (e.g. when a system is down due to maintenance) and is also a good place to ask general questions.
112 112  
113 -=== Jobs for wafer 33 fail with "Slurm execution failed with state CANCELLED by 0" ===
114 -
115 -Wafer 33 is currently (August 2023) not available for use from the EBRAINS Collaboratory via the NMPI batch system. Please use wafer 30 instead.  The copy template for the example job has been updated to use wafer 30.
116 -
117 117  === //PyMarocco.None// needs to be changed to //PyMarocco.Without (Nov 2021)// ===
118 118  
119 119  November 2021: //marocco.backend = PyMarocco.None// had to be changed to //marocco.backend = PyMarocco.Without// due to the move to Python3, which has None as a reserved keyword. See also [[this FAQ entry in the guidebook>>https://electronicvisions.github.io/hbp-sp9-guidebook/pm/using_pm_newflow.html#rename-pymarocco-none-to-pymarocco-without]].
... ... @@ -127,8 +127,4 @@
127 127  
128 128  There are also some additional Python3 related changes in the brainscales_system_chain_test.py example. Please find a [[working example script>>https://lab.ch.ebrains.eu/user-redirect/lab/tree/shared/NMC%20Collab%20copy%20template/BrainScaleS/BrainScaleS_01_Chain.ipynb]] in our [[copy-template Drive>>https://wiki.ebrains.eu/bin/view/Collabs/nmc-collab-copy-template/Drive]] (for copying into users collabs).
129 129  
130 -==== ====
131 -
132 -== Spikey ==
133 -
134 -Support for the use of spikey via the EBRAINS RI has been removed in fall 2024. We recommend to use the much more versatile BrainScaleS-2 interactive instead.
104 +==== ====
1666184857320-440.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kindler
Size
... ... @@ -1,1 +1,0 @@
1 -80.1 KB
Content
image-20221019150927-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kindler
Size
... ... @@ -1,1 +1,0 @@
1 -85.0 KB
Content