GVM升级后启动异常处理

article/2025/11/10 16:23:56

目录

1.  Kali升级

2. 升级完成后，启动GVM（OpenVas）发现打不开：

3. 按照要求检测原因：

4. 查看PID文件

5. 重新检测安装

6. 执行兼容处理后，再次检测安装：

7. 查找安装路径，修改配置文件：

8. 重新安装：

9. 再次检测安装：

10. 启动成功：

11. 页面打开：

1.  Kali升级

apt-get update

apt-get dist-upgrade

2. 升级完成后，启动GVM（OpenVas）发现打不开：

oot@Fkali:~# gvm-start
[*] Please wait for the GVM / OpenVAS services to start.
[*]
[*] You might need to refresh your browser once it opens.
[*]
[*]  Web UI (Greenbone Security Assistant): https://127.0.0.1:9392

Job for gvmd.service failed because a timeout was exceeded.
See "systemctl status gvmd.service" and "journalctl -xe" for details.

3. 按照要求检测原因：

oot@Fkali:~# systemctl status gvmd.service
● gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)
     Loaded: loaded (/lib/systemd/system/gvmd.service; disabled; vendor preset: disabled)
     Active: activating (start) since Thu 2021-08-05 16:42:08 HKT; 31s ago
       Docs: man:gvmd(8)
    Process: 10055 ExecStart=/usr/sbin/gvmd --osp-vt-update=/run/ospd/ospd.sock (code=exited, status=0/SUCCESS)
      Tasks: 0 (limit: 12492)
     Memory: 4.0K
        CPU: 14ms
     CGroup: /system.slice/gvmd.service

Aug 05 16:42:08 Fkali systemd[1]: Starting Greenbone Vulnerability Manager daemon (gvmd)...
Aug 05 16:42:08 Fkali systemd[1]: gvmd.service: Can't open PID file /run/gvm/gvmd.pid (yet?) after start: Operation not permitted

4. 查看PID文件

查看PID文件，发现没有上面的路径：

root@Fkali:~# cd /run/gvm/
root@Fkali:/run/gvm# ls

5. 重新检测安装

oot@Fkali:/run/gvm# sudo gvm-check-setup
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
gvm-check-setup 21.4.1
  Test completeness and readiness of GVM-21.4.1
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Step 1: Checking OpenVAS (Scanner)... 
        OK: OpenVAS Scanner is present in version 21.4.1.
        OK: Server CA Certificate is present as /var/lib/gvm/CA/servercert.pem.
Checking permissions of /var/lib/openvas/gnupg/*
        OK: _gvm owns all files in /var/lib/openvas/gnupg
        OK: redis-server is present.
        OK: scanner (db_address setting) is configured properly using the redis-server socket: /var/run/redis-openvas/redis-server.sock
        OK: redis-server is running and listening on socket: /var/run/redis-openvas/redis-server.sock.                                                                                                            
        OK: redis-server configuration is OK and redis-server is running.                                                                                                                                         
        OK: _gvm owns all files in /var/lib/openvas/plugins                                                                                                                                                       
        OK: NVT collection in /var/lib/openvas/plugins contains 58045 NVTs.                                                                                                                                       
Checking that the obsolete redis database has been removed                                                                                                                                                        
        OK: No old Redis DB                                                                                                                                                                                       
        OK: ospd-OpenVAS is present in version 21.4.1.                                                                                                                                                            
Step 2: Checking GVMD Manager ...                                                                                                                                                                                 
        OK: GVM Manager (gvmd) is present in version 21.4.2.                                                                                                                                                      
Step 3: Checking Certificates ... 
        OK: GVM client certificate is valid and present as /var/lib/gvm/CA/clientcert.pem.
        OK: Your GVM certificate infrastructure passed validation.
Step 4: Checking data ... 
        OK: SCAP data found in /var/lib/gvm/scap-data.
        OK: CERT data found in /var/lib/gvm/cert-data.
Step 5: Checking Postgresql DB and user ... 
        OK: Postgresql version and default port are OK.
 gvmd      | _gvm     | UTF8     | en_HK.UTF-8 | en_HK.UTF-8 | 
Database is wrong version.
        ERROR: Database is wrong version. You have installed a new gvmd version
        FIX: Run 'sudo runuser -u _gvm -- gvmd --migrate'

 ERROR: Your GVM-21.4.1 installation is not yet complete!

Please follow the instructions marked with FIX above and run this
script again.

6. 执行兼容处理后，再次检测安装：

root@Fkali:/run/gvm# sudo gvm-check-setup
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
gvm-check-setup 21.4.1
  Test completeness and readiness of GVM-21.4.1
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Step 1: Checking OpenVAS (Scanner)... 
        OK: OpenVAS Scanner is present in version 21.4.1.
        OK: Server CA Certificate is present as /var/lib/gvm/CA/servercert.pem.
Checking permissions of /var/lib/openvas/gnupg/*
        OK: _gvm owns all files in /var/lib/openvas/gnupg
        OK: redis-server is present.
        OK: scanner (db_address setting) is configured properly using the redis-server socket: /var/run/redis-openvas/redis-server.sock
        OK: redis-server is running and listening on socket: /var/run/redis-openvas/redis-server.sock.
        OK: redis-server configuration is OK and redis-server is running.
        OK: _gvm owns all files in /var/lib/openvas/plugins
        OK: NVT collection in /var/lib/openvas/plugins contains 58045 NVTs.
Checking that the obsolete redis database has been removed
        OK: No old Redis DB
        OK: ospd-OpenVAS is present in version 21.4.1.
Step 2: Checking GVMD Manager ... 
        OK: GVM Manager (gvmd) is present in version 21.4.2.
Step 3: Checking Certificates ... 
        OK: GVM client certificate is valid and present as /var/lib/gvm/CA/clientcert.pem.
        OK: Your GVM certificate infrastructure passed validation.
Step 4: Checking data ... 
        OK: SCAP data found in /var/lib/gvm/scap-data.
        OK: CERT data found in /var/lib/gvm/cert-data.
Step 5: Checking Postgresql DB and user ... 
        OK: Postgresql version and default port are OK.
 gvmd      | _gvm     | UTF8     | en_HK.UTF-8 | en_HK.UTF-8 | 
        OK: At least one user exists.
Step 6: Checking Greenbone Security Assistant (GSA) ... 
Oops, secure memory pool already initialized
        ERROR: Greenbone Security Assistant too old or too new: 21.4.1~dev1
        FIX: Please install Greenbone Security Assistant >= 21.04.

 ERROR: Your GVM-21.4.1 installation is not yet complete!

Please follow the instructions marked with FIX above and run this
script again.
 

7. 查找安装路径，修改配置文件：

root@Fkali:/run/gvm# whereis gvm-check-setup

root@Fkali:/run/gvm# sed -i"" 's/GSA_MAJOR="21.04"/GSA_MAJOR="21.4"/g' $^Cusr/bin/gvm-check-setup

8. 重新安装：

root@Fkali:/run/gvm# gvm-setup
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Creating openvas-scanner's certificate files
sh: 0: getcwd() failed: No such file or directory

[>] Creating database
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
could not identify current directory: No such file or directory
createuser: error: creation of new role failed: ERROR:  role "_gvm" already exists
could not identify current directory: No such file or directory
createdb: error: database creation failed: ERROR:  database "gvmd" already exists
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
could not identify current directory: No such file or directory
could not identify current directory: No such file or directory
psql: fatal: could not find own program executable
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
could not identify current directory: No such file or directory
could not identify current directory: No such file or directory
psql: fatal: could not find own program executable
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
could not identify current directory: No such file or directory
could not identify current directory: No such file or directory
psql: fatal: could not find own program executable
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
could not identify current directory: No such file or directory
could not identify current directory: No such file or directory
psql: fatal: could not find own program executable
[>] Migrating database
[>] Checking for admin user
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
could not identify current directory: No such file or directory
could not identify current directory: No such file or directory
psql: fatal: could not find own program executable
[*] Define Feed Import Owner
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
[>] Updating OpenVAS feeds
[*] Updating: NVT
sh: 0: getcwd() failed: No such file or directory
sh: 0: getcwd() failed: No such file or directory
rsync: [Receiver] getcwd(): No such file or directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at util.c(1088) [Receiver=3.2.3]
[>] Uploading plugins in Redis
[*] Updating: GVMD Data
sh: 0: getcwd() failed: No such file or directory
rsync: [Receiver] getcwd(): No such file or directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at util.c(1088) [Receiver=3.2.3]
[*] Updating: Scap Data
sh: 0: getcwd() failed: No such file or directory
rsync: [Receiver] getcwd(): No such file or directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at util.c(1088) [Receiver=3.2.3]
[*] Updating: Cert Data
sh: 0: getcwd() failed: No such file or directory
rsync: [Receiver] getcwd(): No such file or directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at util.c(1088) [Receiver=3.2.3]
[*] Checking Default scanner
08b69003-5fc2-4037-a479-93b440211c73  OpenVAS  /var/run/ospd/ospd.sock  0  OpenVAS Default

[+] Done
 

9. 再次检测安装：

root@Fkali:/run/gvm# sudo gvm-check-setup
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
gvm-check-setup 21.4.1
  Test completeness and readiness of GVM-21.4.1
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Step 1: Checking OpenVAS (Scanner)... 
        OK: OpenVAS Scanner is present in version 21.4.1.
        OK: Server CA Certificate is present as /var/lib/gvm/CA/servercert.pem.
Checking permissions of /var/lib/openvas/gnupg/*
        OK: _gvm owns all files in /var/lib/openvas/gnupg
        OK: redis-server is present.
        OK: scanner (db_address setting) is configured properly using the redis-server socket: /var/run/redis-openvas/redis-server.sock
        OK: redis-server is running and listening on socket: /var/run/redis-openvas/redis-server.sock.
        OK: redis-server configuration is OK and redis-server is running.
        OK: _gvm owns all files in /var/lib/openvas/plugins
        OK: NVT collection in /var/lib/openvas/plugins contains 58045 NVTs.
Checking that the obsolete redis database has been removed
        OK: No old Redis DB
        OK: ospd-OpenVAS is present in version 21.4.1.
Step 2: Checking GVMD Manager ... 
        OK: GVM Manager (gvmd) is present in version 21.4.2.
Step 3: Checking Certificates ... 
        OK: GVM client certificate is valid and present as /var/lib/gvm/CA/clientcert.pem.
        OK: Your GVM certificate infrastructure passed validation.
Step 4: Checking data ... 
        OK: SCAP data found in /var/lib/gvm/scap-data.
        OK: CERT data found in /var/lib/gvm/cert-data.
Step 5: Checking Postgresql DB and user ... 
        OK: Postgresql version and default port are OK.
 gvmd      | _gvm     | UTF8     | en_HK.UTF-8 | en_HK.UTF-8 | 
        OK: At least one user exists.
Step 6: Checking Greenbone Security Assistant (GSA) ... 
Oops, secure memory pool already initialized
        OK: Greenbone Security Assistant is present in version 21.4.1~dev1.
Step 7: Checking if GVM services are up and running ... 
        OK: ospd-openvas service is active.
        Starting gvmd service
        Waiting for gvmd service
        OK: gvmd service is active.
        Starting greenbone-security-assistant service
        Waiting for greenbone-security-assistant service
        OK: greenbone-security-assistant service is active.
Step 8: Checking few other requirements...
        OK: nmap is present in version 21.4.1~dev1.
        OK: ssh-keygen found, LSC credential generation for GNU/Linux targets is likely to work.
        WARNING: Could not find makensis binary, LSC credential package generation for Microsoft Windows targets will not work.
        SUGGEST: Install nsis.
        OK: xsltproc found.
        WARNING: Your password policy is empty.
        SUGGEST: Edit the /etc/gvm/pwpolicy.conf file to set a password policy.

It seems like your GVM-21.4.1 installation is OK.
 

10. 启动成功：

root@Fkali:/run/gvm# gvm-start
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
[*] Please wait for the GVM / OpenVAS services to start.
[*]
[*] You might need to refresh your browser once it opens.
[*]
[*]  Web UI (Greenbone Security Assistant): https://127.0.0.1:9392

● greenbone-security-assistant.service - Greenbone Security Assistant (gsad)
     Loaded: loaded (/lib/systemd/system/greenbone-security-assistant.service; disabled; vendor preset: disabled)
     Active: active (running) since Thu 2021-08-05 17:30:51 HKT; 7ms ago
       Docs: man:gsad(8)
             https://www.greenbone.net
    Process: 12680 ExecStart=/usr/sbin/gsad --listen=127.0.0.1 --port=9392 (code=exited, status=0/SUCCESS)
   Main PID: 12681 (gsad)
      Tasks: 3 (limit: 12492)
     Memory: 2.1M
        CPU: 10ms
     CGroup: /system.slice/greenbone-security-assistant.service
             ├─12681 /usr/sbin/gsad --listen=127.0.0.1 --port=9392
             └─12682 /usr/sbin/gsad --listen=127.0.0.1 --port=9392

Aug 05 17:30:51 Fkali systemd[1]: Starting Greenbone Security Assistant (gsad)...
Aug 05 17:30:51 Fkali gsad[12680]: Oops, secure memory pool already initialized
Aug 05 17:30:51 Fkali systemd[1]: Started Greenbone Security Assistant (gsad).

● gvmd.service - Greenbone Vulnerability Manager daemon (gvmd)
     Loaded: loaded (/lib/systemd/system/gvmd.service; disabled; vendor preset: disabled)
     Active: active (running) since Thu 2021-08-05 17:30:46 HKT; 5s ago
       Docs: man:gvmd(8)
    Process: 12653 ExecStart=/usr/sbin/gvmd --osp-vt-update=/run/ospd/ospd.sock (code=exited, status=0/SUCCESS)
   Main PID: 12655 (gvmd)
      Tasks: 1 (limit: 12492)
     Memory: 73.2M
        CPU: 296ms
     CGroup: /system.slice/gvmd.service
             └─12655 gvmd: Waiting for incoming connections

Aug 05 17:30:45 Fkali systemd[1]: Starting Greenbone Vulnerability Manager daemon (gvmd)...
Aug 05 17:30:45 Fkali systemd[1]: gvmd.service: Can't open PID file /run/gvm/gvmd.pid (yet?) after start: Operation not permitted
Aug 05 17:30:46 Fkali systemd[1]: Started Greenbone Vulnerability Manager daemon (gvmd).

● ospd-openvas.service - OpenVAS Wrapper of the Greenbone Vulnerability Management (ospd-openvas)
     Loaded: loaded (/lib/systemd/system/ospd-openvas.service; disabled; vendor preset: disabled)
     Active: active (running) since Thu 2021-08-05 17:30:45 HKT; 5s ago
       Docs: man:ospd-openvas(8)
             man:openvas(8)
    Process: 12645 ExecStart=/usr/bin/ospd-openvas --unix-socket /run/ospd/ospd.sock --pid-file /run/ospd/ospd-openvas.pid --log-file /var/log/gvm/ospd-openvas.log --lock-file-dir /var/lib/openvas (code=exited, status=0/SUCCESS)
   Main PID: 12647 (ospd-openvas)
      Tasks: 4 (limit: 12492)
     Memory: 20.2M
        CPU: 194ms
     CGroup: /system.slice/ospd-openvas.service
             ├─12647 /usr/bin/python3 /usr/bin/ospd-openvas --unix-socket /run/ospd/ospd.sock --pid-file /run/ospd/ospd-openvas.pid --log-file /var/log/gvm/ospd-openvas.log --lock-file-dir /var/lib/openvas
             └─12649 /usr/bin/python3 /usr/bin/ospd-openvas --unix-socket /run/ospd/ospd.sock --pid-file /run/ospd/ospd-openvas.pid --log-file /var/log/gvm/ospd-openvas.log --lock-file-dir /var/lib/openvas

Aug 05 17:30:45 Fkali systemd[1]: Starting OpenVAS Wrapper of the Greenbone Vulnerability Management (ospd-openvas)...
Aug 05 17:30:45 Fkali systemd[1]: Started OpenVAS Wrapper of the Greenbone Vulnerability Management (ospd-openvas).

[*] Opening Web UI (https://127.0.0.1:9392) in: 5... 4... 3... 2... 1... 
 

root@Fkali:~/Desktop# ospd-openvas

11. 页面打开：


http://chatgpt.dhexx.cn/article/HdMtTNsc.shtml

相关文章

golang多版本管理工具g（gvm）使用(windows)

golang多版本管理工具g（gvm）使用(windows)

文章目录 前言1、下载地址2、设置环境变量1）设置镜像2）设置g的工作目录3）配置GOROOT 3、配置5、配置 go 全局变量4、使用 前言 gvm与g有什么区别? 同一个项目。只不过因为gitee要求仓库名字符数必须>2,因此将项目重命名为gvm。 1、下载…
阅读更多...
golang版本管理gvm

golang版本管理gvm

今天小土带来一篇关于Go版本管理器gvm的小短文。废话不多说，开始安装。 安装 如果你使用的mac，mac 需要先安装xcode-select，没安装过的同学可以按照如下命令进行执行安装，这里不做太多说明了。 xcode-select --installbrew update…
阅读更多...
QPS.TPS.PV.UV.IP.GVM常用名词解释

QPS.TPS.PV.UV.IP.GVM常用名词解释

QPS 全名 Queries Per Second，意思是“每秒查询率”，是一台服务器每秒能够响应的查询次数，是对一个特定的查询服务器在规定时间内所处理流量多少的衡量标准。 简单的说，QPS req/sec 请求数/秒。它代表的是服务器的机器的性能最…
阅读更多...
golang多版本管理工具g使用(windows)

golang多版本管理工具g使用(windows)

1、下载地址 https://github.com/voidint/g/releases2、设置环境变量 G_MIRROR 值为 https://golang.google.cn/dl/由于国内无法自由访问Golang官网，导致查询及下载go版本都变得困难，因此可以通过该环境变量指定一个镜像站点。 G_HOME 值为 E:\gvm设…
阅读更多...
ShuffleNet 系列(2): ShuffleNet v2 理论讲解

ShuffleNet 系列(2): ShuffleNet v2 理论讲解

ShuffleNet V2 概述 论文：ShuffleNet V2: Practical Guidelines for Efficient CNN Architecture Design shuffleNet v2这篇论文比较硬核，提出了不少新的思想，推荐大家可以看看论文原文。主要思想包括： 模型的计算复杂度不能只…
阅读更多...
ShuffleNet_v1论文阅读

ShuffleNet_v1论文阅读

ShuffleNet: An Extremely Efficient Convolutional Neural Network for Mobile Devices 2017年 原文地址：https://arxiv.org/pdf/1707.01083.pdf 声明：文章仅作知识整理、分享，如有侵权请联系作者删除博文，谢谢！ …
阅读更多...
shufflenetv1详解

shufflenetv1详解

shufflenetv1 知识的搬运工又来了 论文地址：shufflenetv1论文地址 ShuffleNet: An Extremely Efficient Convolutional Neural Network for Mobile Devices。 shufflenet是一篇关于降低深度学习计算量的论文，其可以运行在手机等移动设备端，发…
阅读更多...
ShuffleNet 系列(1): ShuffleNet v1 理论讲解

ShuffleNet 系列(1): ShuffleNet v1 理论讲解

ShuffleNet V1 概述 论文：ShuffleNet:An Extremely Efficient Convolutional Netural Network for Mobile Devices ShuffleNet跟MobileNet一样也是一种轻量化网络，ShuffleNet V1.0版本中作者有提出Channel shuffle的概念。在ShuffleNet Block当中使用的…
阅读更多...
ShuffleNet心得

ShuffleNet心得

channel shuffle： 1）利用group ，再组间进行深度卷积。 优点：1）极大减小计算量（FLOPS） 由于每个filter不再是和输入的全部feature map做卷积，而是仅仅和一个group的feature map做卷…
阅读更多...
ShuffleNet V2

ShuffleNet V2

原文链接： ShuffleNet V2 论文阅读笔记​blog.csdn.net 论文链接： Practical Guidelines for Efficient CNN Architecture Design​arxiv.org 我自己基于 caffe 框架的复现： anlongstory/ShuffleNet_V2-caffe​github.com 本文主要是对目…
阅读更多...
【CV】ShuffleNet：通过 GroupConv 和 ChannelShuffle 实现轻量化 CNN 架构

【CV】ShuffleNet：通过 GroupConv 和 ChannelShuffle 实现轻量化 CNN 架构

论文名称：ShuffleNet: An Extremely Efficient Convolutional Neural Network for Mobile Devices 论文下载：https://arxiv.org/abs/1707.01083 论文年份：2017 论文被引：3925（2022/05/11） 论文代码&#xf…
阅读更多...
shufflenet_v1

shufflenet_v1

本文使用的是轻量级模型shufflenet，使用keras框架进行训练。 参考链接（模型详解）：https://blog.csdn.net/zjn295771349/article/details/89704086 代码如下： 1.data_process.py（数据处理：这里…
阅读更多...
ShuffleNet V1

ShuffleNet V1

论文：https://arxiv.org/abs/1707.01083 1 问题提出 当前的CNN发展趋势是网络越大，性能越好。但是，在计算能力有限的应用场景下(无人机、机器人及智能手机上)，因为内存和计算能力的限制，无法部署大规模的神经网络。虽…
阅读更多...
ShuffleNet 算法的介绍

ShuffleNet 算法的介绍

引言 ShuffleNet是旷视科技最近提出的一种计算高效的CNN模型，其和MobileNet和SqueezeNet等一样主要是想应用在移动端。所以，ShuffleNet的设计目标也是如何利用有限的计算资源来达到最好的模型精度，这需要很好地在速度和精度之间做平衡。Shuf…
阅读更多...
ShuffleNet网络学习笔记

ShuffleNet网络学习笔记

目录 ShuffleNet V1 论文 介绍 Channel Shuffle ShuffleNet v1 单元 ShuffleNet v2 论文 介绍 高效模型的设计准则 ShuffleNet V2结构 ShuffleNet v2和DenseNet 总结 ShuffleNet V1 论文 ShuffleNet: An Extremely Efficient Convolutional Neural Network for M…
阅读更多...
shuffleNet系列

shuffleNet系列

目录 分组卷积 分组卷积的矛盾——计算量 分组卷积的矛盾——特征通信 channel shuffle ShuffleNet V1 ShuffleNet基本单元 ShuffleNet网络结构 对比实验 ShuffleNet V2 设计理念 网络结构 对比实验 分组卷积 Group convolution是将输入层的不同特征图进行分组&a…
阅读更多...
Shufflenet解读

Shufflenet解读

论文：ShuffleNet: AnExtremely Efficient Convolutional Neural Network for Mobile Devices 论文提到模型加速的方法为： 1） 修剪网络，减少分支（pruningnetwork connections）。 2） 对于一个…
阅读更多...
ShuffleNet模型解读

ShuffleNet模型解读

原文链接：：https://arxiv.org/abs/1707.01083 Abstract 论文提出了一种计算效率极高的卷积神经网络结构——ShuffleNet，它是专门为计算能力有限的移动平台设计的。这个新结构用来两个新操作——逐渐群卷积(pointwise group convulution)和通…
阅读更多...
ShuffleNet

ShuffleNet

ShuffleNetV2 的构建模块。首先，卷积步长为 1 的瓶颈块中，先将输入特征按通道一分为二，化成两个分支来 代替原先的分组卷积结构，并且每个分支中的卷积层都 是保持输入输出通道数相同。其中一个分支不采取任何操作以减少参数量和计…
阅读更多...
轻量级网络——ShuffleNetV2

轻量级网络——ShuffleNetV2

文章目录 1.ShuffleNetV2的介绍2.ShuffleNetV2的四条实用指南G1) Equal channel width minimizes memory access cost (MAC)G2) Excessive group convolution increases MACG3) Network fragmentation reduces degree of parallelismG4) Element-wise operations are non-negli…
阅读更多...
推荐文章

Copyright @ 2022~2023