Google cloud platform Google云启动器:单节点文件服务器部署失败
我正在尝试部署单节点文件服务器,如以下说明所述: 当我按照说明操作时,该实例看起来运行正常,但NFS似乎没有运行。当我尝试使用从另一个实例装载时Google cloud platform Google云启动器:单节点文件服务器部署失败,google-cloud-platform,nfs,google-cloud-launcher,Google Cloud Platform,Nfs,Google Cloud Launcher,我正在尝试部署单节点文件服务器,如以下说明所述: 当我按照说明操作时,该实例看起来运行正常,但NFS似乎没有运行。当我尝试使用从另一个实例装载时 sudo mount-t nfs jupyterhub文件管理器vm:/jupyterhub/mnt 我明白了 mount.nfs:连接超时 当我从计算引擎UI()检查文件服务器实例时,我看到 文件显示 gcloud compute ssh--ssh flag=-L3000:localhost:3000--project=workpop dev--zo
sudo mount-t nfs jupyterhub文件管理器vm:/jupyterhub/mnt
我明白了
mount.nfs:连接超时
当我从计算引擎UI()检查文件服务器实例时,我看到
文件显示
gcloud compute ssh--ssh flag=-L3000:localhost:3000--project=workpop dev--zone us-east1-d jupyterhub文件管理器vm
然后在浏览器中访问localhost:3000
,以访问性能仪表板。ssh命令将我连接到实例,但浏览器返回ERR\u EMPTY\u响应
,在ssh会话中我看到
通道4:打开失败:连接失败:连接被拒绝
在ssh会话中,我尝试
$ps-e | grep nfs
它什么也不返回
$cat/etc/exports
返回仅包含注释的默认文件
因此,我查找带有$sudo find/-name“jupyterhub*”
的磁盘,但它没有返回任何内容。再翻一翻,我看到/opt/c2d/setup.log
,它的末尾有以下几行:
VIRTUAL_IP =
+ readonly ZFS_KERNEL_CONFIG=/etc/modprobe.d/zfs.conf
+ ZFS_KERNEL_CONFIG=/etc/modprobe.d/zfs.conf
+ networks=(10.0.0.0/8 127.0.0.1)
+ readonly networks
+ readonly DISK_PREFIX=/dev/disk/by-id/google
+ DISK_PREFIX=/dev/disk/by-id/google
+ readonly DATA_DEVICE=/dev/disk/by-id/google-jupyterhub-filer-vm-data
+ DATA_DEVICE=/dev/disk/by-id/google-jupyterhub-filer-vm-data
+ [[ xfs = \z\f\s ]]
+ [[ -n '' ]]
+ case "${FILE_SYSTEM}" in
+ mkfs.xfs -L jupyterhub /dev/disk/by-id/google-jupyterhub-filer-vm-data
/dev/disk/by-id/google-jupyterhub-filer-vm-data: No such file or directory
Usage: mkfs.xfs
/* blocksize */ [-b log=n|size=num]
/* metadata */ [-m crc=0|1,finobt=0|1]
/* data subvol */ [-d agcount=n,agsize=n,file,name=xxx,size=num,
(sunit=value,swidth=value|su=num,sw=num|noalign),
sectlog=n|sectsize=num
/* force overwrite */ [-f]
/* inode size */ [-i log=n|perblock=n|size=num,maxpct=n,attr=0|1|2,
projid32bit=0|1]
/* no discard */ [-K]
/* log subvol */ [-l agnum=n,internal,size=num,logdev=xxx,version=n
sunit=value|su=num,sectlog=n|sectsize=num,
lazy-count=0|1]
/* label */ [-L label (maximum 12 characters)]
/* naming */ [-n log=n|size=num,version=2|ci,ftype=0|1]
/* no-op info only */ [-N]
/* prototype file */ [-p fname]
/* quiet */ [-q]
/* realtime subvol */ [-r extsize=num,size=num,rtdev=xxx]
/* sectorsize */ [-s log=n|size=num]
/* version */ [-V]
devicename
<devicename> is required unless -d name=xxx is given.
<num> is xxx (bytes), xxxs (sectors), xxxb (fs blocks), xxxk (xxx KiB),
xxxm (xxx MiB), xxxg (xxx GiB), xxxt (xxx TiB) or xxxp (xxx PiB).
<value> is xxx (512 byte blocks).
虚拟IP=
+只读ZFS_内核_配置=/etc/modprobe.d/ZFS.conf
+ZFS_KERNEL_CONFIG=/etc/modprobe.d/ZFS.conf
+网络=(10.0.0.0/8127.0.0.1)
+只读网络
+只读磁盘前缀=/dev/DISK/by id/google
+磁盘前缀=/dev/DISK/by id/google
+只读数据\u设备=/dev/disk/by id/google jupyterhub文件管理器vm DATA
+DATA\u DEVICE=/dev/disk/by id/google jupyterhub文件管理器vm DATA
+[[xfs=\z\f\s]]
+[-n'']]
+中的案例“${FILE_SYSTEM}”
+mkfs.xfs-L jupyterhub/dev/disk/by id/google jupyterhub文件管理器vm数据
/dev/disk/by id/google jupyterhub filer vm data:没有这样的文件或目录
用法:mkfs.xfs
/*blocksize*/[-b log=n | size=num]
/*元数据*/[-m crc=0 | 1,finobt=0 | 1]
/*数据子卷*/[-d agcount=n,agsize=n,文件,名称=xxx,大小=num,
(sunit=value,swidth=value | su=num,sw=num | noalign),
sectlog=n | sectsize=num
/*强制覆盖*/[-f]
/*inode size*/[-i log=n | perblock=n | size=num,maxpct=n,attr=0 | 1 | 2,
项目32位=0 | 1]
/*不丢弃*/[-K]
/*log subvol*/[-l agnum=n,内部,大小=num,logdev=xxx,版本=n
sunit=value | su=num,sectlog=n | sectsize=num,
延迟计数=0 | 1]
/*标签*/[-L标签(最多12个字符)]
/*命名*/[-n log=n | size=num,version=2 | ci,ftype=0 | 1]
/*仅限无操作信息*/[-N]
/*原型文件*/[-p fname]
/*安静的*/[-q]
/*实时子卷*/[-r extsize=num,size=num,rtdev=xxx]
/*sectorsize*/[-s log=n | size=num]
/*版本*/[-V]
设备名称
除非给出-d name=xxx,否则为必填项。
是xxx(字节)、xxx(扇区)、xxxb(fs块)、xxxk(xxx KiB),
xxxm(xxx MiB)、xxxg(xxx GiB)、xxxt(xxx TiB)或xxxp(xxx PiB)。
是xxx(512字节块)。
此时,我确信出现了问题,但我不知道如何修复。有人能帮忙吗?磁盘名有问题 尝试使用默认值:Storage Name=data
(它为我完成了安装,没有出现错误,并且localhost:3000正在正确加载。我不确定它以后是否会在实验室中产生错误。)如果它对任何人都有帮助,那么在仅供参考时,实验室文档也会被更新为“Storage Name=data”。自定义存储名称支持可能会在将来的更新中提供。
VIRTUAL_IP =
+ readonly ZFS_KERNEL_CONFIG=/etc/modprobe.d/zfs.conf
+ ZFS_KERNEL_CONFIG=/etc/modprobe.d/zfs.conf
+ networks=(10.0.0.0/8 127.0.0.1)
+ readonly networks
+ readonly DISK_PREFIX=/dev/disk/by-id/google
+ DISK_PREFIX=/dev/disk/by-id/google
+ readonly DATA_DEVICE=/dev/disk/by-id/google-jupyterhub-filer-vm-data
+ DATA_DEVICE=/dev/disk/by-id/google-jupyterhub-filer-vm-data
+ [[ xfs = \z\f\s ]]
+ [[ -n '' ]]
+ case "${FILE_SYSTEM}" in
+ mkfs.xfs -L jupyterhub /dev/disk/by-id/google-jupyterhub-filer-vm-data
/dev/disk/by-id/google-jupyterhub-filer-vm-data: No such file or directory
Usage: mkfs.xfs
/* blocksize */ [-b log=n|size=num]
/* metadata */ [-m crc=0|1,finobt=0|1]
/* data subvol */ [-d agcount=n,agsize=n,file,name=xxx,size=num,
(sunit=value,swidth=value|su=num,sw=num|noalign),
sectlog=n|sectsize=num
/* force overwrite */ [-f]
/* inode size */ [-i log=n|perblock=n|size=num,maxpct=n,attr=0|1|2,
projid32bit=0|1]
/* no discard */ [-K]
/* log subvol */ [-l agnum=n,internal,size=num,logdev=xxx,version=n
sunit=value|su=num,sectlog=n|sectsize=num,
lazy-count=0|1]
/* label */ [-L label (maximum 12 characters)]
/* naming */ [-n log=n|size=num,version=2|ci,ftype=0|1]
/* no-op info only */ [-N]
/* prototype file */ [-p fname]
/* quiet */ [-q]
/* realtime subvol */ [-r extsize=num,size=num,rtdev=xxx]
/* sectorsize */ [-s log=n|size=num]
/* version */ [-V]
devicename
<devicename> is required unless -d name=xxx is given.
<num> is xxx (bytes), xxxs (sectors), xxxb (fs blocks), xxxk (xxx KiB),
xxxm (xxx MiB), xxxg (xxx GiB), xxxt (xxx TiB) or xxxp (xxx PiB).
<value> is xxx (512 byte blocks).