ubuntu中出现sh:0:Can't open   并且无法使用open in terminal打开该文件，用的是jupyterlab 文件夹是有这个文件的，但就是无法打开 想请教各位大佬给点建议

答完这套题你就知道了。。。。 http://www.gtalent.cn/exam/interview?token=3448af9f01a7b622851f91d0328f3a9e 如果进去手都下不了，说明你还在山底下。。。

我使用KubeSphere部署了一个示例应用，使用浏览器可以访问部署出来的东西，但是使用Xshell 在k8s的主机上curl却访问超时 爆出的错误为 curl https://productpage.test.172.23.253.31.nip.io:31447 curl: (7) Failed connect to productpage.test.172.23.253.31.nip.io:31447; Connection timed out 希望大神们帮我找好原因

如图： 红线里的分别是啥意思

安装sitewhere过程中，有几个pod一直重启 kubectl describe pod发现找不到grpc_health_probe 请问有遇到类似的情况的吗 版本信息： k8s:1.15.1 istio:1.3.2 helm:3.0.0

远程管理12台服务器， 同样的配置， 2016windows系统， 开通了远程桌面， 机器有技术员远程进去安装程序，1-2个月进去升级一次，用什么方式，技术员进入了，能快速修改12台机器登录密码？ 或者给个安全隔离的办法 请给个简单的方法

你好，有个问题想咨询您，我做一个统计面积的代码，然后我用的是那个group， var dict = ee.Image.pixelArea() .addBands(result) . reduceRegion({ reducer: ee.Reducer.sum().group({ groupField:1, groupName:"type", }), geometry:geometry, scale:30, maxPixels:1e13 }) print("dict-change"+year,dict)，我想获取groups里的sum的数值总是提取不出来，报错sum不是ee.Number的参数，这个怎么解决呢

有啥子好用的云盘比较好用容量大的。求推荐？

web浏览器调用URL_Protocol方式调用远程一些window的.exe文件（调用的exe文件带有图像化界面，如qq），知道远程的ip地址（云平台），想问下如何实现，网上只看见本地的实现方法 或者有其他方法可以实现吗，十分感谢

1.以root身份登录系统，新建用户组test01和test02；新建用户user01 默认主组为test01,家目录为：/home/userhome01,uid为1234，账号永不过期；新建用户user02,主组为test02,账号过期后立即禁用， 2.设置user01的用户口令为：usr12345 ;设置user02口令为空（passwd -d ），并强迫用户下次登录时必须更改口令(passwd -f )；锁定user02;解锁user02; 指定user02最长存活期60天，口令到期前3天警告，口令到期后3天停用账号； 3.修改user01的账户到期时间为2021－05－01，显示口令属性的各个值；变更主组为test02，uid为：8888；变更家目录为user01,并将原家目录的数据转移过来。 4.进入user02的家目录，并将文件/etc/passwd 、/etc/shadow复制到当前目录分别改名为passwd.bak shadow.bak 5.同时查看passwd.bak和shadow.bak文件内容，标注行号，并将全部内容存入文件pash.bak中 6.翻页查看pash.bak文件，从第10行开始，每页仅显示12行 7.分页查看pash.bak文件，要求能够向前翻页 8.查看passwd.bak的前5行内容；查看shadow.bak的前50个字符； 9.查看passwd.bak的前末5行内容；查看shadow.bak的最后50个字符； 10.创建目录/home/test01/temp01和/home/test01/temp02；将目录/home/user02备份到/home/test01/temp01/user02.tar;将目录/home/user02压缩备份到/home/test01/temp01/user02.tar.gz 11.删除用户user02，包括与其相关的记录和目录；12.新建用户user03,user04,user05 并将他们全部加入到test02组中；指派user03为组的管理员； 13.以文件名查找/home/test01目录中的所有文件，并将查询结果存入findtest01.txt文件中。 14.以长格式查看文件findtest01.txt;将文件所有者改为user03,属组改为test02 15.更改findtest01.txt的权限：属主为rw，属组为rw,其它无任何权限 16.为findtest01.txt建立硬链接dfindtext01 ,软链接sfindtext01 17.筛选出文件findtest01.txt中带s的行，并将结果存入greps.txt 18.更改目录test01中文件的默认权限为：属主为rwx，属组为rx,其它无任何权限; 19.查看文件findtest01.txt的隐藏属性（lsattr[-adR]） 设置文件隐藏属性chattr (了解） a:只能追加不能删改 b：不更新最后存取 c：压缩后存放 d：文件不可操作 i：不得改动 s：保密性删除 S：即时更新 u：预防意外删除最重要的是+a和+i 20.文件访问控制列表 setfacl setfacl -Rm u:用户名：rwx 目录或者文件 －－－－R递归，m普通文件，b删除权限 设置了ACL的，文件读写权限最后面的好个‘.’变成‘+’ getfacl

.以root身份登录系统，新建用户组test01和test02；新建用户user01 默认主组为test01,家目录为：/home/userhome01,uid为1234，账号永不过期；新建用户user02,主组为test02,账号过期后立即禁用，2.设置user01的用户口令为：usr12345 ;设置user02口令为空（passwd -d ），并强迫用户下次登录时必须更改口令(passwd -f )；锁定user02;解锁user02; 指定user02最长存活期60天，口令到期前3天警告，口令到期后3天停用账号；3.修改user01的账户到期时间为2021－05－01，显示口令属性的各个值；变更主组为test02，uid为：8888；变更家目录为user01,并将原家目录的数据转移过来。4.进入user02的家目录，并将文件/etc/passwd 、/etc/shadow复制到当前目录分别改名为passwd.bak shadow.bak5.同时查看passwd.bak和shadow.bak文件内容，标注行号，并将全部内容存入文件pash.bak中6.翻页查看pash.bak文件，从第10行开始，每页仅显示12行 7.分页查看pash.bak文件，要求能够向前翻页；8.查看passwd.bak的前5行内容；查看shadow.bak的前50个字符；9.查看passwd.bak的前末5行内容；查看shadow.bak的最后50个字符；10.创建目录/home/test01/temp01和/home/test01/temp02；将目录/home/user02备份到/home/test01/temp01/user02.tar;将目录/home/user02压缩备份到/home/test01/temp01/user02.tar.gz11.删除用户user02，包括与其相关的记录和目录；12.新建用户user03,user04,user05 并将他们全部加入到test02组中；指派user03为组的管理员；13.以文件名查找/home/test01目录中的所有文件，并将查询结果存入findtest01.txt文件中。14.以长格式查看文件findtest01.txt;将文件所有者改为user03,属组改为test02 更改findtest01.txt的权限：属主为rw，属组为rw,其它无任何权限16.为findtest01.txt建立硬链接dfindtext01 ,软链接sfindtext0117.筛选出文件findtest01.txt中带s的行，并将结果存入greps.txt18.更改目录test01中文件的默认权限为：属主为rwx，属组为rx,其它无任何权限;19.查看文件findtest01.txt的隐藏属性（lsattr[-adR]） 设置文件隐藏属性chattr (了解） a:只能追加不能删改 b：不更新最后存取 c：压缩后存放 d：文件不可操作 i：不得改动 s：保密性删除 S：即时更新 u：预防意外删除最重要的是+a和+i 20.文件访问控制列表 setfacl setfacl -Rm u:用户名：rwx 目录或者文件 －－－－R递归，m普通文件，b删除权限 设置了ACL的，文件读写权限最后面的好个‘.’变成‘+’ getfacl

我想通过应用虚拟化，将应用程序安装在云上或者windows-server版上，通过浏览器点击启动云上的应用，并显示在本地机器上，这个怎么实现，最好可以提供代码demo，万分感谢

我是在apicloud平台做的一个小程序用的语言是javascript，想把这个程序和AWS IoT通过mqtt.js连接到一起。出错的代码部分如下 var options = { clientId: a random String, endpoint: the endpoint of AWS IoT Core, accessKey: I generate this from IAM - > Dashboard - > My access Key - > Access key, secretKey: I generate this from IAM - > Dashboard - > My access Key - > Access key, regionName: i find this from endpoint, debug: true }; var client = mqtt.connect('wss://' + endpoint + '/mqtt', options); //var client = mqtt.connect('mqtt://test.mosquitto.org'); client.on('connect', function() { alert("MQTT connected"); client.subscribe('topic_1') client.publish('topic_1', 'Hello mqtt2') }) client.on('message', function(topic, message) { // message is Buffer alert(message.toString()) client.end() }) 我使用的AWS IoT policy是 { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "iot:*", "Resource": "*" } ] } 在我跑代码的时候，他会先等一段时间然后出现WebSocket connection to 'wss:// + endpoint + '/mqtt' failed: Error during WebSocket handshake: net::ERR_CONNECTION_ABORTED 其中mqtt.connect的URL是根据这个网址写的https://docs.aws.amazon.com/iot/latest/developerguide/protocols.html 在将URL改成 'wss:// + endpoint + ':443/mqtt'后会出现WebSocket opening handshake timed out的错误  

maven配置好了，但rebuild index时，立刻就好了，但相应的jar包没有下载过来只有一个.cache文件夹 <?xml version="1.0" encoding="UTF-8"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <!-- | This is the configuration file for Maven. It can be specified at two levels: | | 1. User Level. This settings.xml file provides configuration for a single user, | and is normally provided in ${user.home}/.m2/settings.xml. | | NOTE: This location can be overridden with the CLI option: | | -s /path/to/user/settings.xml | | 2. Global Level. This settings.xml file provides configuration for all Maven | users on a machine (assuming they're all using the same Maven | installation). It's normally provided in | ${maven.conf}/settings.xml. | | NOTE: This location can be overridden with the CLI option: | | -gs /path/to/global/settings.xml | | The sections in this sample file are intended to give you a running start at | getting the most out of your Maven installation. Where appropriate, the default | values (values used when the setting is not specified) are provided. | |--> <settings xmlns="http://maven.apache.org/SETTINGS/1.2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 http://maven.apache.org/xsd/settings-1.2.0.xsd"> <!-- localRepository | The path to the local repository maven will use to store artifacts. | | Default: ${user.home}/.m2/repository--> <localRepository>E:\maven\repository</localRepository> <!-- interactiveMode | This will determine whether maven prompts you when it needs input. If set to false, | maven will use a sensible default value, perhaps based on some other setting, for | the parameter in question. | | Default: true <interactiveMode>true</interactiveMode> --> <!-- offline | Determines whether maven should attempt to connect to the network when executing a build. | This will have an effect on artifact downloads, artifact deployment, and others. | | Default: false <offline>false</offline> --> <!-- pluginGroups | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e. | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list. |--> <pluginGroups> <!-- pluginGroup | Specifies a further group identifier to use for plugin lookup. <pluginGroup>com.your.plugins</pluginGroup> --> </pluginGroups> <!-- proxies | This is a list of proxies which can be used on this machine to connect to the network. | Unless otherwise specified (by system property or command-line switch), the first proxy | specification in this list marked as active will be used. |--> <proxies> <!-- proxy | Specification for one proxy, to be used in connecting to the network. | <proxy> <id>optional</id> <active>true</active> <protocol>http</protocol> <username>proxyuser</username> <password>proxypass</password> <host>proxy.host.net</host> <port>80</port> <nonProxyHosts>local.net|some.host.com</nonProxyHosts> </proxy> --> </proxies> <!-- servers | This is a list of authentication profiles, keyed by the server-id used within the system. | Authentication profiles can be used whenever maven must make a connection to a remote server. |--> <servers> <!-- server | Specifies the authentication information to use when connecting to a particular server, identified by | a unique name within the system (referred to by the 'id' attribute below). | | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are | used together. | <server> <id>deploymentRepo</id> <username>repouser</username> <password>repopwd</password> </server> --> <!-- Another sample, using keys to authenticate. <server> <id>siteServer</id> <privateKey>/path/to/private/key</privateKey> <passphrase>optional; leave empty if not used.</passphrase> </server> --> </servers> <!-- mirrors | This is a list of mirrors to be used in downloading artifacts from remote repositories. | | It works like this: a POM may declare a repository to use in resolving certain artifacts. | However, this repository may have problems with heavy traffic at times, so people have mirrored | it to several places. | | That repository definition will have a unique id, so we can create a mirror reference for that | repository, to be used as an alternate download site. The mirror site will be the preferred | server for that repository. |--> <mirrors> <!-- mirror | Specifies a repository mirror site to use instead of a given repository. The repository that | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used | for inheritance and direct lookup purposes, and must be unique across the set of mirrors. | <mirror> <id>mirrorId</id> <mirrorOf>repositoryId</mirrorOf> <name>Human Readable Name for this Mirror.</name> <url>http://my.repository.com/repo/path</url> </mirror> --> <mirror> <id>maven-default-http-blocker</id> <mirrorOf>external:http:*</mirrorOf> <name>Pseudo repository to mirror external repositories initially using HTTP.</name> <url>http://0.0.0.0/</url> <blocked>true</blocked> </mirror> <mirror> <id>alimaven</id> <mirrorOf>central</mirrorOf> <name>aliyun maven</name> <url>http://maven.aliyun.com/nexus/content/repositories/central/</url> </mirror> </mirrors> <!-- profiles | This is a list of profiles which can be activated in a variety of ways, and which can modify | the build process. Profiles provided in the settings.xml are intended to provide local machine- | specific paths and repository locations which allow the build to work in the local environment. | | For example, if you have an integration testing plugin - like cactus - that needs to know where | your Tomcat instance is installed, you can provide a variable here such that the variable is | dereferenced during the build process to configure the cactus plugin. | | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles | section of this document (settings.xml) - will be discussed later. Another way essentially | relies on the detection of a system property, either matching a particular value for the property, | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'. | Finally, the list of active profiles can be specified directly from the command line. | | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact | repositories, plugin repositories, and free-form properties to be used as configuration | variables for plugins in the POM. | |--> <profiles> <!-- profile | Specifies a set of introductions to the build process, to be activated using one or more of the | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/> | or the command line, profiles have to have an ID that is unique. | | An encouraged best practice for profile identification is to use a consistent naming convention | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc. | This will make it more intuitive to understand what the set of introduced profiles is attempting | to accomplish, particularly when you only have a list of profile id's for debug. | | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo. --> <profile> <id>jdk-1.7</id> <activation> <jdk>1.7</jdk> </activation> <repositories> <repository> <id>jdk17</id> <name>Repository for JDK 1.7 builds</name> <url>http://www.myhost.com/maven/jdk17</url> <layout>default</layout> <snapshotPolicy>always</snapshotPolicy> </repository> </repositories> </profile> <!-- | Here is another profile, activated by the system property 'target-env' with a value of 'dev', | which provides a specific path to the Tomcat instance. To use this, your plugin configuration | might hypothetically look like: | | ... | <plugin> | <groupId>org.myco.myplugins</groupId> | <artifactId>myplugin</artifactId> | | <configuration> | <tomcatLocation>${tomcatPath}</tomcatLocation> | </configuration> | </plugin> | ... | | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to | anything, you could just leave off the <value/> inside the activation-property. | <profile> <id>env-dev</id> <activation> <property> <name>target-env</name> <value>dev</value> </property> </activation> <properties> <tomcatPath>/path/to/tomcat/instance</tomcatPath> </properties> </profile> --> </profiles> <!-- activeProfiles | List of profiles that are active for all builds. | <activeProfiles> <activeProfile>alwaysActiveProfile</activeProfile> <activeProfile>anotherAlwaysActiveProfile</activeProfile> </activeProfiles> --> </settings>  

ssh进程过一段时间就自动停止。 经过：我安装了ssh，之后试了下连接成功，刚开始我的ssh能用，我就没管它，开机开了一天，发现再连上的时候ssh没了，只能重新启动ssh进程，有什么办法能保活ssh呢？

    早上看日志发现，凌晨4点左右有大量的恶意ip请求同一个域名的不同uri，请求的uri都是我服务器上不存在的，所以产生了大量的404日志，请问这种恶意攻击应该怎么防范，能通过接入WAF防火墙来抵挡吗？

用云模型来做综合评价时侯，建立的云评价标准怎么确定熵、超熵啊

START RequestId:72e459e1-8ec6-4afb-b5e1-c49a8c85b145 ERROR RequestId:72e459e1-8ec6-4afb-b5e1-c49a8c85b145 Result:{"errorCode":-1,"errorMessage":"Traceback (most recent call last):\n  File \"/var/runtime/python3/bootstrap.py\", line 133, in init_handler\n    func_handler = get_func_handler(file.rsplit(\".\", 1)[0], func)\n  File \"/var/runtime/python3/bootstrap.py\", line 160, in get_func_handler\n    return getattr(mod, fname)\nAttributeError: module 'index' has no attribute 'main_handler'","statusCode":443} END RequestId:72e459e1-8ec6-4afb-b5e1-c49a8c85b145 Report RequestId:72e459e1-8ec6-4afb-b5e1-c49a8c85b145 Duration:0ms Memory:256MB MemUsage:0.000000MB

按照默认的选项，一路配置好S3. 然后，按照https://blog.csdn.net/weixin_39636079/article/details/111662504?utm_medium=distribute.pc_relevant.none-task-blog-2%7Edefault%7EOPENSEARCH%7Edefault-6.control&dist_request_id=1332042.12507.16192617880043773&depth_1-utm_source=distribute.pc_relevant.none-task-blog-2%7Edefault%7EOPENSEARCH%7Edefault-6.control 的步骤进行挂载，最终挂载失败，查不到挂载目录。显示 Transport endpoint is not connected. 于是，重来输出日志信息如下：  求大佬赐教！

Mac电脑键盘锁住不能打字怎么办，有没有大佬知道啊？？？

awk '{a[$1]+=$3}END{for(i in a)print i,a[i]}' test.txt 里面的最后a[i]代表什么意义具体是做什么的

ceph集群初始时有9个osd，其中六个0.5T，三个0.9T，使用70%后扩容加入六个osd，都是3.6T，调整过pg及pgp，集群恢复之后，新的数据并不多往大磁盘的osd写，导致前面使用率已经很高的osd很快又濒临写满，导致整个集群空间利用率很低，通过批量调节reweight后，数据并没有明显往后几个大osd迁移，只是在前几个小osd来回迁移，并且pg会出现大量misplaced状态，请问如何提高后加入的大osd的空间使用率？多谢！

题目要求：不准交叉感染 提示：二分算法    

Mounting command: systemd-run Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/ba256654-269e-4a75-89fe-04a86a8caf9a/volumes/kubernetes.io~nfs/hadoop-config-nfs-pv --scope -- mount -t nfs 192.168.195.139:/home/nfs/data/hadoop-config /var/lib/kubelet/pods/ba256654-269e-4a75-89fe-04a86a8caf9a/volumes/kubernetes.io~nfs/hadoop-config-nfs-pv Output: Running scope as unit run-3784.scope. mount: 文件系统类型错误、选项错误、192.168.195.139:/home/nfs/data/hadoop-config 上有坏超级块、        缺少代码页或助手程序，或其他错误        (对某些文件系统(如 nfs、cifs) 您可能需要        一款 /sbin/mount.<类型> 助手程序)        有些情况下在 syslog 中可以找到一些有用信息- 请尝试        dmesg | tail  这样的命令看看。

前些天刚入手的Mac电脑，已经整的差不多了，现在就想知道Mac电脑需要安装什么必备的软件，比较好用又简单的？坐等哦～在线急！

最近研究锂电池的在线参数辨识及SOC估计。在阅读文献过程中，发现在参数辨识这一块遇到些无法理解的地方，希望有懂的大神给指点一下哈。 疑问地方： 电池在工作时我们能得到它的外部参数（不考虑温度的话），只有输出电流 I ,和输出电压UL。 可是我在别人的论文中经常看到如下 经过Z变换再离散化得到： 也就是说辨识用到的数据E(k)是 电池端工作电压UL(k) 与 开路电压Uocv(k) 之间的差值，UL(k)可以实时测量得到，虽然有Uocv--SOC的对应曲线，但是当前的Uocv(k)不知道是多少呀，那这个E(k)是怎么得到的呢？（不理解的地方）

目前有主备两台机器搭建nginx高可用。主备两台的nginx服务均可以访问。 我在主配置文件的优先级明明高于备配置文件，为什么虚拟ip会跑到备上面呢？ 另外虚拟ip可以ping通，但是无法访问，停止备上面的keepalived也无法ip漂移。 主keepalived配置文件： global_defs { notification_email { acassen@firewall.loc failover@firewall.loc sysadmin@firewall.loc } notification_email_from Alexandre.Cassen@firewall.loc smtp_server 117.50.2.19 smtp_connect_timeout 30 router_id LVS_DEVEL # 访问的主机地址 #vrrp_strict } vrrp_script chk_nginx { script "/root/nginx_check.sh" # 检测文件的地址 interval 2 # 检测脚本执行的间隔 weight 2 # 权重 } vrrp_instance VI_1 { state MASTER # 主机MASTER、备机BACKUP interface eth0 # 网卡 virtual_router_id 50 # 同一组需一致 priority 100 # 访问优先级，主机值较大，备机较小 advert_int 1 authentication { auth_type PASS auth_pass 1111 } virtual_ipaddress { 192.168.25.51 # 虚拟ip } 网卡： 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1452 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:3c:e0:8e brd ff:ff:ff:ff:ff:ff inet 10.9.136.234/16 brd 10.9.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe3c:e08e/64 scope link valid_lft forever preferred_lft forever 备keepalived配置文件： global_defs { notification_email { acassen@firewall.loc failover@firewall.loc sysadmin@firewall.loc } notification_email_from Alexandre.Cassen@firewall.loc smtp_server 128.1.136.60 smtp_connect_timeout 30 router_id LVS_DEVEL # 访问的主机地址 #vrrp_strict } vrrp_script chk_nginx { script "/root/nginx_check.sh" # 检测文件的地址 interval 2 # 检测脚本执行的间隔 weight 2 # 权重 } vrrp_instance VI_1 { state BACKUP # 主机MASTER、备机BACKUP interface eth0 # 网卡 virtual_router_id 51 # 同一组需一致 priority 90 # 访问优先级，主机值较大，备机较小 advert_int 1 authentication { auth_type PASS auth_pass 1111 } virtual_ipaddress { 192.168.25.51 # 虚拟ip } } 网卡： 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1452 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:18:4d:87 brd ff:ff:ff:ff:ff:ff inet 10.7.186.157/16 brd 10.7.255.255 scope global eth0 valid_lft forever preferred_lft forever inet 192.168.25.51/32 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe18:4d87/64 scope link valid_lft forever preferred_lft forever  

在公网环境下一切正常，在公司内网（已经配置了代理）连接MNS获取回执消息，报如下错误： MNSClientNetworkException  ("NetWorkException", "local variable 'msg' referenced before assignment")  ；   但是获取token或调用语音呼叫接口均没有问题