Issue on /home on bamboo

HPC Support HPC issues
1

Hi,
It seems that there is an error with the /home on bamboo. When I ssh I get:

Could not chdir to home directory /home/users/d/delislel: Communication error on send
-bash: /home/users/d/delislel/.bash_profile: Communication error on send
(bamboo)-[delislel@login1 /]$

If I try using on demand:

Home directory not found

Your home directory appears to be missing. The home directory mount may be unavailable, or your home directory may need to still be created. Please contact support for help and attempt to restart your web server by clicking below when the problem has been fixed.

Thanks

1 Like
Remote error on Bamboo
2

This is fixed now, I don’t know if you solved it or if it was a temporary issue.

3

thanks for the post, I was just wondering why all my batches crashed around 9am :sweat_smile:

1 Like
4

Although the access to /home seems to be working, I still get an error message when trying to access the scratch via FileZilla though

Commande : cd “/home/users/c/clairis/scratch”
Erreur : Directory /home/users/c/clairis/scratch: received failure with description ‘Failure’
Erreur : Impossible de récupérer le contenu du dossier

and same when trying via Putty:

cd scratch
-bash: cd: scratch: Communication error on send

5

Indeed, I have the same problem in command lines:

(bamboo)-[delislel@login1 ~]$ ls scratch
ls: cannot access 'scratch': Communication error on send 
(bamboo)-[delislel@login1 ~]$ ls /srv/beegfs/scratch/users
ls: cannot access '/srv/beegfs/scratch/users': Communication error on send
1 Like
6

This is now solved for me.

1 Like
7

thanks for warning! looks ok here as well indeed, weirdly they didn’t say anything yet so I hope it’s stable

8

Dear Users,

You can follow all issue in the post [2025] Current issues on HPC Cluster - #21 by Yann.Sagon

Best regards

9

yes I know and I was watching, but it was marked as solved while we still had the issue with the access to scratch :sweat_smile: Is it solved now?

10

Yes it’s should work :wink:

1 Like
11

sorry about that, we figured out after the reboot of the server that a service didn’t started as expected, but yes, I confirm it is now running as expected. We contacted the vendor to have some insight to try to fix the root cause.

1 Like
12

ok great thanks for the update and confirmation that it works! :slight_smile: fingers crossed for no more crashing then